Errata exists for this version of the document.

Objects and Variables described in the following subclauses can be extended by additional Properties or References to other Nodes, except where it is stated in the text that it is restricted.

To promote interoperability of clients and Servers, the OPC UA AddressSpace is structured as a hierarchy, with the top levels standardised for all Servers. Figure 1 illustrates the structure of the AddressSpace. All Objects in this figure are organised using Organizes References and have the ObjectType FolderType as type definition.

Figure 1 – Standard AddressSpace Structure

The remainder of this provides descriptions of these standard Nodes and the organization of Nodes beneath them. Servers typically implement a subset of these standard Nodes, depending on their capabilities.

This standard Object is the browse entry point for the AddressSpace. It contains a set of Organizes References that point to the other standard Objects. The “Root” Object shall not reference any other NodeClasses. It is formally defined in Table 79.

Table 79 – Root Definition

Attribute		Value
BrowseName		Root
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		FolderType	Defined in 6.6
Organizes	Object		Views	Defined in 8.2.3
Organizes	Object		Objects	Defined in 8.2.4
Organizes	Object		Types	Defined in 8.2.5

This standard Object is the browse entry point for Views. Only Organizes References are used to relate View Nodes to the “Views” standard Object. All View Nodes in the AddressSpace shall be referenced by this Node, either directly or indirectly. That is, the “Views” Object may reference other Objects using Organizes References. Those Objects may reference additional Views. Figure 2 illustrates the Views Organization. The “Views” standard Object directly references the Views “View1” and “View2” and indirectly “View3” by referencing another Object called “Engineering”.

Figure 2 – Views Organization

The “Views” Object shall not reference any other NodeClasses. The “Views” Object is formally defined in Table 80.

Table 80 – Views Definition

Attribute	Value
BrowseName	Views
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6

This standard Object is the browse entry point for Object Nodes. Figure 3 illustrates the structure beneath this Node. Only Organizes References are used to relate Objects to the “Objects” standard Object. A View Node can be used as entry point into a subset of the AddressSpace containing Objects and Variables and thus the “Objects“ Object can also reference View Nodes using Organizes References. The intent of the “Objects” Object is that all Objects and Variables that are not used for type definitions or other organizational purposes (e.g. organizing the Views) are accessible through hierarchical References starting from this Node. However, this is not a requirement, because not all Servers may be able to support this. This Object references the standard Server Object defined in 8.3.2.

Figure 3 – Objects Organization

The “Objects” Object shall not reference any other NodeClasses. The “Objects” Object is formally defined in Table 81.

Table 81 – Objects Definition

Attribute		Value
BrowseName		Objects
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		FolderType	Defined in 6.6
Organizes	Object		Server	Defined in 8.3.2

This standard Object Node is the browse entry point for type Nodes. Figure 1 illustrates the structure beneath this Node. Only Organizes References are used to relate Objects to the “Types” standard Object. The “Types” Object shall not reference any other NodeClasses. It is formally defined in Table 82.

Table 82 – Types Definition

Attribute	Value
BrowseName	Types
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6
Organizes		Object	ObjectTypes	Defined in 8.2.6
Organizes		Object	VariableTypes	Defined in 8.2.7
Organizes		Object	ReferenceTypes	Defined in 8.2.8
Organizes		Object	DataTypes	Defined in 8.2.9
Organizes		Object	EventTypes	Defined in 8.2.10

This standard Object Node is the browse entry point for ObjectType Nodes. Figure 4 illustrates the structure beneath this Node showing some of the standard ObjectTypes defined in 6. Only Organizes References are used to relate Objects and ObjectTypes to the “ObjectTypes” standard Object. The “ObjectTypes” Object shall not reference any other NodeClasses.

Figure 4 – ObjectTypes Organization

The intention of the “ObjectTypes” Object is that all ObjectTypes of the Server are either directly or indirectly accessible browsing HierarchicalReferences starting from this Node. However, this is not required and Servers might not provide some of their ObjectTypes because they may be well-known in the industry, such as the ServerType defined in 6.3.1.

This Object also indirectly references the BaseEventType defined in 6.4.2, which is the base type of all EventTypes. Thereby it is the entry point for all EventTypes provided by the Server. It is required that the Server expose all its EventTypes, so a client can usefully subscribe to Events.

The “ObjectTypes” Object is formally defined in Table 83.

Table 83 – ObjectTypes Definition

Attribute	Value
BrowseName	ObjectTypes
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6
Organizes		ObjectType	BaseObjectType	Defined in 6.2

This standard Object is the browse entry point for VariableType Nodes. Figure 5 illustrates the structure beneath this Node. Only Organizes References are used to relate Objects and VariableTypes to the “VariableTypes” standard Object. The “VariableTypes” Object shall not reference any other NodeClasses.

Figure 5 – VariableTypes Organization

The intent of the “VariableTypes” Object is that all VariableTypes of the Server are either directly or indirectly accessible browsing HierarchicalReferences starting from this Node. However, this is not required and Servers might not provide some of their VariableTypes, because they may be well-known in the industry, such as the “BaseVariableType” defined in 7.2.

The “VariableTypes” Object is formally defined in Table 84.

Table 84 – VariableTypes Definition

Attribute	Value
BrowseName	VariableTypes
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6
Organizes		VariableType	BaseVariableType	Defined in 7.2

This standard Object is the browse entry point for ReferenceType Nodes. Figure 6 illustrates the organization of ReferenceTypes. Organizes References are used to define ReferenceTypes and Objects referenced by the “ReferenceTypes” Object. The “ReferenceTypes” Object shall not reference any other NodeClasses. See Clause 11 for a discussion of the standard ReferenceTypes that appear beneath the “ReferenceTypes” Object.

Figure 6 – ReferenceType Definitions

Since ReferenceTypes will be used as filters in the browse Service and in queries, the Server shall provide all its ReferenceTypes, directly or indirectly following hierarchical References starting from the “ReferenceTypes” Object. This means that, whenever the client follows a Reference, the Server shall expose the type of this Reference in the ReferenceType hierarchy. It shall provide all ReferenceTypes so that the client would be able, following the inverse subtype of References, to come to the base References ReferenceType. It does not mean that the Server shall expose the ReferenceTypes that the client has not used any Reference of.

The “ReferenceTypes” Object is formally defined in Table 85.

Table 85 – ReferenceTypes Definition

Attribute	Value
BrowseName	ReferenceTypes
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6
Organizes		ReferenceType	References	Defined in 11.1

This standard Object is the browse entry point for DataTypes that the Server wishes to expose in the AddressSpace.

DataType Nodes should be made available using Organizes References pointing either directly from the “DataTypes” Object to the DataType Nodes or using additional Folder Objects for grouping purposes. The intent is that all DataTypes of the Server exposed in the AddressSpace are accessible following hierarchical References starting from the “DataTypes” Object. However, this is not required.

The “DataTypes” Object is formally defined in Table 86.

Table 86 – DataTypes Definition

Attribute		Value
BrowseName		DataTypes
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		FolderType	Defined in 6.6
Organizes	DataType		BaseDataType	Defined in 12.2

This standard Object Node is the browse entry point for EventType Nodes. Figure 7 illustrates the structure beneath this Node showing some of the standard EventTypes defined in Clause 6. Only Organizes References are used to relate Objects and ObjectTypes to the “EventTypes” standard Object. The “EventTypes” Object shall not reference any other NodeClasses.

Figure 7 – EventTypes Organization

The intention of the “EventTypes” Object is that all EventTypes of the Server are either directly or indirectly accessible browsing HierarchicalReferences starting from this Node. It is required that the Server expose all its EventTypes, so a client can usefully subscribe to Events.

The “EventTypes” Object is formally defined in Table 87.

Table 87 – EventTypes Definition

Attribute	Value
BrowseName	EventTypes
References		NodeClass	BrowseName	Comment
HasTypeDefinition		ObjectType	FolderType	Defined in 6.6
Organizes		ObjectType	BaseEventType	Defined in 6.4.2

The Server Object and its containing Objects and Variables are built in a way that the information can be gained in several ways, suitable for different kinds of clients having different requirements. Annex A gives an overview of the design decisions made in providing the information in that way, and discusses the pros and cons of the different approaches. Figure 8 gives an overview of the containing Objects and Variables of the diagnostic information of the Server Object and where the information can be found.

The SessionsDiagnosticsSummary Object contains one Object per session and a Variable with an array with one entry per session. This array is of a complex DataType holding the diagnostic information about the session. Each Object representing a session references a complex Variable containing the information about the session using the same DataType as the array containing information about all sessions. Such a Variable also exposes all its information as Variables with simple DataTypes containing the same information as in the complex DataType. Not shown in Figure 8 is the security-related information per session, which follows the same rules.

The Server provides an array with an entry per subscription containing diagnostic information about this subscription. Each entry of this array is also exposed as a complex Variable with Variables for each individual value. Each Object representing a session also provides such an array, but providing the subscriptions of the session.

The arrays containing information about the sessions or the subscriptions may be of different length for different connections with different user credentials since not all users may see all entries of the array. That also implies that the length of the array may change if the user is impersonated. Therefore clients that subscribe to a specific index range may get unexpected results.

Figure 8 – Excerpt of Diagnostic Information of the Server

This Object is used as the browse entry point for information about the Server. The content of this Object is already defined by its type definition in 6.3.1. It is formally defined in Table 88. The Server Object serves as root notifier, that is, its EventNotifier Attribute shall be set providing Events. All Events of the Server shall be accessible subscribing to the Events of the Server Object.

Table 88 – Server Definition

Attribute		Value
BrowseName		Server
References	Node Class		BrowseName	DataType	TypeDefinition	ModellingRule
HasTypeDefinition	Object Type		ServerType	Defined in 6.3.1

The ModellingRule ExposesItsArray is defined in OPC 10000-3. Its representation in the AddressSpace, the “ExposesItsArray” Object, is formally defined in Table 89.

Table 89 – ExposesItsArray Definition

Attribute		Value
BrowseName		ExposesItsArray
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		ModellingRuleType	Defined in 6.5
HasProperty	Variable		NamingRule	Value set to “Constraint”

The ModellingRule Mandatory is defined in OPC 10000-3. Its representation in the AddressSpace, the “Mandatory” Object, is formally defined in Table 90.

Table 90 – Mandatory Definition

Attribute		Value
BrowseName		Mandatory
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		ModellingRuleType	Defined in 6.5
HasProperty	Variable		NamingRule	Value set to “Mandatory”

The ModellingRule Optional is defined in OPC 10000-3. Its representation in the AddressSpace, the “Optional” Object, is formally defined in Table 91.

Table 91 – Optional Definition

Attribute		Value
BrowseName		Optional
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		ModellingRuleType	Defined in 6.5
HasProperty	Variable		NamingRule	Value set to “Optional”

The ModellingRule OptionalPlaceholder is defined in OPC 10000-3. Its representation in the AddressSpace, the “OptionalPlaceholder” Object, is formally defined in Table 92.

Table 92 – OptionalPlaceholder Definition

Attribute		Value
BrowseName		OptionalPlaceholder
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		ModellingRuleType	Defined in 6.5
HasProperty	Variable		NamingRule	Value set to “Constraint”

The ModellingRule MandatoryPlaceholder is defined in OPC 10000-3. Its representation in the AddressSpace, the “MandatoryPlaceholder” Object, is formally defined in Table 93.

Table 93 – MandatoryPlaceholder Definition

Attribute		Value
BrowseName		MandatoryPlaceholder
References	NodeClass		BrowseName	Comment
HasTypeDefinition	ObjectType		ModellingRuleType	Defined in 6.5
HasProperty	Variable		NamingRule	Value set to “Constraint”