For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7, OPC 10000-8, OPC 10000-14, OPC 10000-17, OPC 10000-18, OPC 10000-80, OPC 10000-100, OPC 10000-110 as well as the following apply.

All used terms are italicized in the specification as described in OPC 10000-1.

Server collecting information from underlying Servers and sourcing to higher-level Servers or applications

Note 1 to entry: AggregatingServers can add functionality to information that is collected as well as group or merge information.

QoSQuality of Service

LLDP Link Layer Discovery Protocol

SKSSecurity Key Service

In all type definitions, the “Other” column defines additional characteristics of the Node. Examples of characteristics that can appear in this column are shown in Table 1.

Table 1 – Examples of Other Characteristics

Name	Short Name	Description
Mandatory	M	The Node has the Mandatory ModellingRule.
Optional	O	The Node has the Optional ModellingRule.
MandatoryPlaceholder	MP	The Node has the MandatoryPlaceholder ModellingRule.
OptionalPlaceholder	OP	The Node has the OptionalPlaceholder ModellingRule.
ReadOnly	RO	The Node AccessLevel Attribute has the CurrentRead bit set but not the CurrentWrite bit.
ReadWrite	RW	The Node AccessLevel Attribute has the CurrentRead and CurrentWrite bits set.
WriteOnly	WO	The Node AccessLevel Attribute has the CurrentWrite bit set but not the CurrentRead bit.

If multiple characteristics are defined, they are separated by commas. Throughout this document, the short name is used.

Clause 6.3 defines an Asset to be an Object either derived from FxAssetType or an Object of any type which implements the required Interfaces. Asset (plural Assets) is used throughout this document to designate an instance of such an Object, regardless of whether derived from the type or implementing the Interfaces.

Clause 6.4 defines a FunctionalEntity to be an Object either derived from FunctionalEntityType or an Object of any type which implements the required Interface. FunctionalEntity (plural FunctionalEntities) is used throughout this document to designate an instance of such an Object, regardless of whether derived from the type or implementing the Interfaces.

In this document, the name of a type without the addition of “Type” is used to indicate an instance of the type. For example, the following phrase, “an instance of ConnectionConfigurationSetType,” can be replaced with “a ConnectionConfigurationSet”. The phrase “instances of ConnectionEndpointType” can be replaced with “ConnectionEndpoints”.

Each Node defined in this document references at least one ConformanceUnit (defined in OPC 10000-84). If a Server supports the ConformanceUnit, it shall expose the Nodes related to the ConformanceUnit in its AddressSpace. If two Nodes are exposed, all References between the Nodes defined in this document shall be exposed as well.

The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes, one row per ConformanceUnit.