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 OPEN-SCS 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.

For the purposes of this document, the terms and definitions given in OPC 10000-1 and OPC 10000-3 as well as the following apply.

A collection of serialized child objects (such as bottles or cases) in a serialized parent object (such as a case, container, or pallet)

A printed label that is associated with a specific product or package.

An application or system which responds to a request for a service or information from an Information Requester or provides information to an Information Receiver. In this OPC UA implementation the Information Provider is an OPC UA Server.

An application or system which receives information from an Information Provider and may provide an acknowledgement. In this OPC UA implementation the Information Provider is an OPC UA Server.

An application or system which requests a service or information and receives responses from an Information Provider. In this OPC UA implementation the Information Requestor is an OPC UA client.

A serial number on a human and machine-readable label that is not yet associated with a specific package or aggregation.

A string of characters with a defined syntax used for purposes of establishing uniqueness between otherwise identical objects. Serial numbers may be numeric, alphanumeric and contain symbols.

A unique identifier (serial number) comprising of a string of characters within a defined format that is associated with a physical object such that no two physical objects are associated with the same string of characters. Abbreviated as SID, this could be an EPC according to the GS1 standard.

DAData Access

EPCElectronic Product Code

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.