BS EN 62541-3:2010 pdf free.OPC unified architecture Address Space Model.
BS EN 62541-3 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 the Property. Only this standard may define Attributes. Thus, all Attributes of the NodeClass are specified in the table and can only be extended by other parts of this series of standards.
This standard also defines Reference Types, but Reference Types can also be specified by a server or by a client using the NodeManagement Services specified in IEC 62541-4. Thus, the NodeClass tables contained in this standard can contain the base Reference Type called References identifying that any ReferenceType may be used for the NodeClass, including system specific Reference Types. The NodeClass tables only specify how the NodeClasses can be used as SourceNodes of References, not as TargetNodes. If a NodeClass table allows a ReferenceType for its NodeClass to be used as SourceNode, this is also true for subtypes of the ReferenceType. However, subclasses of the ReferenceType may restrict its SourceNodes.
This standard defines Properties， but Properties can be defined by other standard organizations or vendors and Nodes can have Properties that are not standardised.Properties defined in this standard 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 implementation will chose to use ModellingRules appropriate for them.The following subclauses define 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 ObjectTypes and VariableTypes. Standard Reference Types, DataTypes and EventTypes are defined in Clauses 7 to 9.
The informative Annex A describes general considerations 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 the OPC Binary Types Description System as a format to specify data type structures and the normative Annex D defines a graphical notation for OPC UA data.
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 ilustrates the model.BS EN 62541-3 pdf download.