IEC 62541-3-2020 pdf free.OPC unified architecture – Part 3: Address Space Model.
The Name column contains the name of the Attribute, the name of the ReferenceType used to create a Reference or the name of a Property referenced using the HasProperty Reference.
The Use column defines whether the Attribute or Property is mandatory (M) or optional (0).
When mandatory the Attribute or Property shall exist for every Node of the NodeClass.
The Data Type column contains the name of the Data Type of the Attribute or Property. It is not used for References.
The Description column contains the description of the Attribute, the Reference or tIie Property.
Only this document may define Attributes. Thus, all Attributes of the NodeClass are specified in the table and may only be extended by other parts of the IEC 62541 series.
This document also defines ReferenceTypes, but ReferenceTypes may also be specified by a Server or by a Client using the NodeManagement Services specified in IEC 62541-4. Thus, the NodeCiass tables contained in this document may contain the base Reference Type called References identifying that any Reference Type may be used for the NodeCiass. including system specific ReferenceTypes. The NodeCless tables only specify how the NodeClasses can be used as SourceNodes of References, not as TargetNodes. If a NodeClass table allows a Reference Type for its NodeClass to be used as SourceNode, this is also true for subtypes of the ReferenceType. However, subtypes of the Reference Type may restrict its SourceNodes.
This document defines Properties, but Properties can be defined by other standards organizations or vendors and Nodes can have Properties that are not standardized. Properties defined in this document are defined by their name, which is mapped to the BrowseName having the Namespacelndex 0, which represents the Namespace for OPC UA.
The Use column (optional or mandatory) does not imply a specific ModellingRule for Properties. Different Server implementations will choose to use ModellingRules appropriate for them.
4 AddressSpace concepts
4.1 Overview
Clause 4 defines the concepts of the AddressSpace. Clause 5 defines the NodeClasses of the
AddressSpace representing the AddressSpace concepts. Clause 6 defines details on the type
model for Object Types and Variable Types. Standard ReferenceTypes. Data Types and
EventTypes are defined in Clauses 7 to 9.
The informative Annex A describes general considerations on how to use the Address Space Model and the informative Annex B provides a UML Model of the Address Space Model. The normative Annex C defines a graphical notation for OPC UA data.
4.2 Object Model
The primary objective of the OPC UA AddressSpace is to provide a standard way for Servers to represent Objects to Clients. The OPC UA Object Model has been designed to meet this objective. It defines Objects in terms of Variables and Methods. It also allows relationships to other Objects to be expressed. Figure 2 illustrates the model.IEC 62541-3 pdf download.