It is assumed that basic concepts of OPC UA information modelling are understood in this specification. This specification will use these concepts to describe the PackML object models. The concepts and terms used to describe the OPC UA information models are defined in other parts and listed in the following sections. Note that OPC UA terms and terms defined in this standard are italicized in the specification.

The following terms defined in OPC 10000-1 apply.

  • AddressSpace
  • Attribute
  • Client
  • Message
  • Node
  • NodeClass
  • Object
  • ObjectType
  • Profile
  • Reference
  • ReferenceType
  • Server
  • Variable
  • View

The following terms defined in OPC 10000-3 apply.

  • Hierarchical Reference
  • InstanceDeclaration
  • ModellingRule
  • OptionalPlaceholder
  • MandatoryPlaceholder
  • DataVariable
  • Property
  • SourceNode
  • TargetNode
  • TypeDefinitionNode
  • VariableType

The following terms defined in OPC 10000-8 apply.

  • AnalogItem
  • EngineeringUnits

The following term defined in OPC 10000-9 apply.

  • Operator

This standard adopts adding a PackML prefix to all PackML defined terms that are used in this standard that are also defined by OPC. The <Term> is the terminology defined by PackML. This allows the terminology used in PackML to be easily distinguished from terminology defined in OPC UA.

a concept that defines a collection of associated modules that can carry out one or more major processing activities.

Note: in PackML Unit and Machine are used to define the same thing and can at times be interchanged.

a concept that represents named data element that is used to command, read status, or provide administration of a unit.

a concept that represents a state model of the operational state of a unit.

a concept that represents the mode of operation of a unit, indicating which state model is currently active.

DAData Access

ACAlarm and Condition

HAHistorical access

PLCProgrammable Logic Controllers

DCSDistributed Control Systems

OCSOpen Control Systems

This standard uses the ModellingRules OptionalPlaceholder and MandatoryPlaceholder to define instance declarations, and defines a rule that the BrowseName of instance declarations having an OptionalPlaceholder or MandatoryPlaceholder ModellingRule be enclosed in angle brackets (<>). Originally, this rule is defined in OPC 10000-3 as a recommendation. This naming rule is also used in the description of a table. The BrowseName of a Node that has OptionalPlaceholder or MandatoryPlaceholder ModellingRule are described with angle brackets, which denotes that the name is not fixed. For example, BrowseName of Property is described as <PropertyName> in graphical notation and tables results in a Property that can have any name.