Search

200 result(s) for node

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.23 Node
  Node fundamental component of an AddressSpace
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.20 NodesToDelete
  type are defined in Table F.19 . Table F.19 - NodesToDelete Element Type Description Node NodeToDelete A Node to delete from the AddressSpace
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.16 EventNotifier
  EventNotifier special Attribute of a Node that signifies that a Client may subscribe to that particular Node to receive Notifications of Event occurrences
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.35 Reference
  Reference explicit relationship (a named pointer) from one Node to another Note 1 to entry: The Node that contains the Reference is the source Node , and the referenced Node ... target Node. All References are defined by ReferenceTypes
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.45 Variable
  Variable Node that contains a value
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  3.2 Specification parts
  manner of configuring and exposing an alternate well-defined name for any OPC UA Node in a Server or system. Part 18 ( OPC 10000-18 ) - Role-Based Security Part ... configure and expose a merged compact representation of the selected subtree of a root Node . Part 26 ( OPC 10000-26 ) - LogObject Part 26 specifies an OPC UA information model
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.2 Integrated AddressSpace model
  AddressSpace . The OPC UA AddressSpace represents its contents as a set of Node s connected by References . Primitive characteristics of Node s are described by Attributes . Attributes are the only ... have data values. Data types that define attribute values may be simple or complex. Node s in the AddressSpace are typed according to their use and their meaning. NodeClasses define
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.1 AddressSpace Nodes
  AddressSpace Nodes The AddressSpace is modelled as a set of Node s accessible by Clients using OPC UA Services (interfaces and methods). Node s in the AddressSpace are used
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.2 AddressSpace organization
  interconnected Nodes in a consistent manner. Servers are free to organize their Node s within the AddressSpace as they choose. The use of References between Node s permits Servers ... organize the AddressSpace into hierarchies, a full mesh network of Node s, or any possible mix. OPC 10000-5 defines OPC UA Nodes and References and their expected organization
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.3 AddressSpace Views
  View is a subset of the AddressSpace . Views are used to restrict the Node s that the Server makes visible to the Client , thus restricting the size of the AddressSpace ... entire AddressSpace . Servers may optionally define other Views . Views hide some of the Node s or References in the AddressSpace . Views are visible via the AddressSpace and Clients are able
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.4 Support for information models
  information models The OPC UA AddressSpace supports Information Models . This support is provided through: Node References that allow Objects in the AddressSpace to be related to each other. ObjectType Node ... that provide semantic information for real Objects (type definitions). ObjectType Node s to support subclassing of type definitions. Data type definitions exposed in the AddressSpace that allow industry specific data
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.5.1 MonitoredItems
  MonitoredItems MonitoredItems are entities in the Server created by the Client that monitor AddressSpace Node s and, indirectly, their real-world counterparts. When they detect a data change
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.6.2 Request/response Services
  Service Interface to perform a specific task on one or more Node s in the AddressSpace and to return a response
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.7.7 Alias Names
  user-assigned names are often referred to as "Tag Names". When a Node in a Server represents an entity with an assigned Tag Name, the Tag Name ... often used as the Name or Description attribute for that Node , but short of browsing all Nodes in all Servers , there is no easy way to find a Node with
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.6 View Service Set
  Services to create Client defined Views . The View Service Set allows Clients to discover Node s in a View by browsing. Browsing allows Clients to navigate up and down ... hierarchy, or to follow References between Node s contained in the View . In this manner, browsing also allows Clients to discover the structure of the View
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.1 AccessRestriction
  operation, such as a read, write or a call, can be performed on a Node Note 1 to entry: Operations can only be performed on a Node if the Client
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.34 Permission
  execute an operation, such as a read, write or a call, on a Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.8 EventType
  EventType ObjectType Node that represents the type definition of an Event
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.10 InstanceDeclaration
  InstanceDeclaration Node that is used by a complex TypeDefinitionNode to expose its complex structure Note 1 to entry: This is an instance used by a type definition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.14 SourceNode
  SourceNode Node having a Reference to another Node EXAMPLE: In the Reference "A contains B", "A" is the SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.16 TargetNode
  TargetNode Node that is referenced by another Node EXAMPLE: In the Reference "A contains B", "B" is the TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.17 TypeDefinitionNode
  TypeDefinitionNode Node that is used to define the type of another Node Note 1 to entry: ObjectType and VariableType Nodes are TypeDefinitionNodes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.18 VariableType
  VariableType Node that represents the type definition for a Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.1 Conventions for AddressSpace figures
  using figures. Figure 1 illustrates the conventions used in these figures. Figure 1 - AddressSpace Node diagrams In these figures, rectangles represent Nodes . Node rectangles may be titled with ... second line contains the BrowseName . When one line is used, it contains the BrowseName . Node rectangles may contain boxes used to define their Attributes and References . Specific names in these
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  optional (O). When mandatory the Attribute or Property shall exist for every Node of the NodeClass . For References it specifies the cardinality. The following values may apply
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.3 Object Model
  Model The elements of this model are represented in the AddressSpace as Nodes . Each Node is assigned to a NodeClass and each NodeClass represents a different element of the Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.1 General
  described by Attributes and interconnected by References . Figure 3 illustrates the model of a Node and the remainder of 4.3 discusses the details of the Node Model. Figure 3 - AddressSpace ... Node Model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.2 NodeClasses
  terms of the Attributes and References that shall be instantiated (given values) when a Node is defined in the AddressSpace . Attributes are discussed in 4.4.3 and References in 4.4.4 . Clause ... AddressSpace . These NodeClasses are referred to collectively as the metadata for the AddressSpace . Each Node in the AddressSpace is an instance of one of these NodeClasses . No other NodeClasses shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.3 Attributes
  defined for each NodeClass shall not be extended by Clients or Servers . When a Node is instantiated in the AddressSpace , the values of the NodeClass Attributes are provided. The mandatory/optional
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  visible in the AddressSpace and are defined using the ReferenceType NodeClass (see 5.3 ). The Node that contains the Reference is referred to as the SourceNode and the Node that ... TargetNode are used in OPC UA Services to uniquely identify References . Thus, each Node can reference another Node with the same ReferenceType only once. Any subtypes of concrete ReferenceTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  DataVariables and other Nodes . Properties differ from Attributes in that they characterise what the Node represents, such as a device or a purchase order. Attributes define additional metadata that ... Properties , the BrowseName of a Property shall be unique in the context of the Node containing the Properties (see 5.6.3 for details). A Node and its Properties shall always reside
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.1 General
  used to subscribe to Events . The EventNotifier Attribute of those Nodes identifies if the Node allows subscribing to Events . Clients subscribe to such Nodes to receive Notifications of Event occurrences ... Services defined in OPC 10000-4 to subscribe to the Event Notifications of a Node . Any OPC UA Server that supports eventing shall expose at least one Node as EventNotifier
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.8 Methods
  number of input arguments and return resultant arguments. Each Method is described by a Node of the Method NodeClass . This Node contains the metadata that identifies the Method's arguments
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.9.3 Evaluating Permissions with Roles
  Evaluating Permissions with Roles When a Client attempts to access a Node, the Server goes through the list of Roles granted to the Session and logically ORs the Permissions ... Role on the Node. If there are no Node specific Permissions then the default Permissions for the Role in the DefaultRolePermissions Property of the NamespaceMetadata for the namespace the Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  Server are either directly or indirectly accessible browsing HierarchicalReferences starting from this Node . Rules for the definition of Interfaces : Interface ObjectTypes shall be abstract subtypes of the BaseInterfaceType ObjectType . InstanceDeclarations ... fully-inherited InstanceDeclaration­Hierarchy of the Interface shall have for each BrowsePath a similar Node (see 6.2.4) with the ModellingRule Mandatory using the same BrowsePath in the fully-inherited InstanceDeclarationHierarchy
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.3 AddIn model
  model AddIns associate a feature or feature-set, represented by an ObjectType to the Node (an Object or ObjectType ) they are applied to. The Interface model is different than ... model in that it is based on composition. An AddIn is applied to a Node by adding a Reference to the AddIn instance. There are no restrictions for AddIn ObjectTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.3 NodeClass
  NodeClass The NodeClass Attribute identifies the NodeClass of a Node . Its data type is defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.4 BrowseName
  BrowseNames . A BrowseName should never be used to display the name of a Node . The DisplayName should be used instead for this purpose. Unlike NodeIds , the BrowseName cannot be used ... unambiguously identify a Node . Different Nodes may have the same BrowseName . Subclause 8.3 defines the structure of the BrowseName . It contains a namespace and a string. The namespace is provided
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.5 DisplayName
  DisplayName The DisplayName Attribute contains the localised name of the Node . Clients should use this Attribute if they want to display the name of the Node to the user. They
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.6 Description
  Description The optional Description Attribute shall explain the meaning of the Node in a localised text using the same mechanisms for localisation as described for the DisplayName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.7 WriteMask
  WriteMask Attribute exposes the possibilities of a client to write the Attributes of the Node . The WriteMask Attribute does not take any user access rights into account, that is, although
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.8 UserWriteMask
  UserWriteMask Attribute exposes the possibilities of a client to write the Attributes of the Node taking user access rights into account. It uses the AttributeWriteMask DataType which is defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.9 RolePermissions
  RolePermissions The optional RolePermissions Attribute specifies the Permissions that apply to a Node for all Roles which have access to the Node . The value of the Attribute is an array ... specified, the value of DefaultRolePermissions Property from the NamespaceMetadata Object associated with the Node shall be used instead. If the NamespaceMetadata Object does not define the Property or does
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.10 UserRolePermissions
  UserRolePermissions The optional UserRolePermissions Attribute specifies the Permissions that apply to a Node for all Roles granted to current Session . The value of the Attribute is an array of RolePermissionType ... Client reads the UserRolePermissions it shall ignore bits that are not valid for the Node . If not specified, the value of DefaultUserRolePermissions Property from the Namespace Metadata Object associated with
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.11 AccessRestrictions
  AccessRestrictions The optional AccessRestrictions Attribute specifies the AccessRestrictions that apply to a Node. Its data type is defined in 8.56 . If a Server supports AccessRestrictions for a particular Namespace ... Property to the NamespaceMetadata Object for that Namespace (see Figure 14 ). If a particular Node in the Namespace needs to override the default value the Server adds the AccessRestrictions Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.1 General
  specified in Table 9 . In contrast, a Reference is an inherent part of a Node and no NodeClass is used to represent References . This standard defines a set of ReferenceTypes ... NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  have constraints restricting its use. For example, it can specify that starting from Node A and only following References of this ReferenceType or one of its subtypes, it shall never
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  Nodes in the AddressSpace . The entire AddressSpace is the default View . Each Node in a View may contain only a subset of its References , as defined by the creator ... View . The View Node acts as the root for the Nodes in the View . Views are defined using the View NodeClass , which is specified in Table 10 . All Nodes contained
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  EventNotifier M EventNotifierType The EventNotifier Attribute is used to indicate if the Node can be used to subscribe to Events or the read / write historic Events . The EventNotifierType is defined ... NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted ... Node the Property belongs to. Attribute value changes do not cause the NodeVersion to change. Clients may read the NodeVersion Property or subscribe to it to determine when the structure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  never defined by themselves. A Variable is always part of at least one other Node , but may be related to any number of other Nodes . Variables are defined using ... NodeVersion Property is updated each time a Reference is added or deleted to the Node the Property belongs to. Attribute value changes except for the DataType , ValueRank and ArrayDimensions Attributes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.3 Properties
  Properties shall always be defined in the context of another Node and shall be the TargetNode of at least one HasProperty Reference . To distinguish them from DataVariables , they shall ... TargetNode of any HasComponent Reference . Thus, a HasProperty Reference pointing to a Variable Node defines this Node as a Property . The BrowseName of a Property is always unique
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted ... Node the Property belongs to. Attribute value changes except for the DataType , ValueRank and ArrayDimensions Attributes do not cause the NodeVersion to change. Clients may read the NodeVersion Property
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted ... Node the Property belongs to. Attribute value changes do not cause the NodeVersion to change. Clients may read the NodeVersion Property or subscribe to it to determine when the structure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  VariableTypes . Therefore each Variable and VariableType is pointing with its DataType Attribute to a Node of the DataType NodeClass as shown in Figure 17 . Figure 17 - Variables, VariableTypes and their ... DataTypes In many cases, the NodeId of the DataType Node - the DataTypeId - will be well-known to Clients and Servers . Clause 8 defines DataTypes and OPC 10000-6 defines their
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  AddressSpace . To expose the human-readable representation of an enumerated value the DataType Node may have the EnumStrings Property that contains an array of LocalizedText . The Integer representation ... Structured DataType . To expose the human-readable representation of an OptionSet the DataType Node shall have the OptionSetValues Property that contains an array of LocalizedText . In addition to the DataTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  NodeVersion O String The NodeVersion Property is used to indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted ... Node the Property belongs to. Attribute value changes do not cause the NodeVersion to change. Clients may read the NodeVersion Property or subscribe to it to determine when the structure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.4 DataTypeEncoding and Encoding Information
  DataTypeEncoding and Encoding Information If a DataType Node is exposed in the AddressSpace , it shall provide its DataTypeEncodings using HasEncoding References . These References shall be bi-directional. Figure 19 provides ... encode the DataType is provided in the Attribute DataTypeDefinition of the DataType Node . The content of this Attribute shall not be changed once it had been provided to Clients since
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.2 DataTypeRefinement Objects
  referenced using a HasDataTypeRefinement Reference (see 7.30 ) or subtype from exactly one DataType Node representing a Structured DataType that is being refined. For each field having a refinement, a Variable ... equality check with a field name. A DataTypeRefinement Object shall not reference any Node with a HasFieldDescription or subtype which is not representing a field of the DataType it refines
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.3 Usage of DataTypeRefinements
  Usage of DataTypeRefinements Each DataTypeRefinement Object shall be referenced from exactly one DataType Node using HasDataTypeRefinement or a subtype. DataTypeRefinements are expressed in an OPC UA information model, by using ... DataType , that is on a Variable . DataTypeRefinements shall not be used from any DataType Node , from any VariableType , or any InstanceDeclaration , only from concrete Variables . This does include Variables describing
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  SubtypeRestriction Object . Each SubtypeRestriction Object shall be referenced from exactly one DataType Node using a HasDataTypeRefinement Reference . A SubtypeRestriction Object is referencing Variables with an AllowedSubtype Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.2 Instances without ModellingRules
  Instances without ModellingRules If no ModellingRule exists then the Node is neither considered for instantiation of a type nor for subtyping. If a Node referenced by a TypeDefinitionNode does ... reference a ModellingRule it indicates that this Node only belongs to the TypeDefinitionNode and not to the instances. For example, an ObjectType Node may contain a Property that describes scenarios
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.4 Similar Node of InstanceDeclaration
  Similar Node of InstanceDeclaration A similar Node of an InstanceDeclaration is a Node that has the same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects ... TypeDefinitionNode or a subtype of it. In the case of a Method a similar Node of an InstanceDeclaration is a Node that also has the same arguments of the InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.2 Fully-inherited InstanceDeclarationHierarchy
  /B/J HasTypeDefinition - PropertyType /B HasComponent /B/H - /B/H HasTypeDefinition - BaseDataVariableType Multiple BrowsePaths to the same Node shall be treated as separate Nodes . An Instance may provide different Nodes for each BrowsePath
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  overriding an InstanceDeclaration it is necessary to provide hierarchical References that link the new Node back to the subtype (the References are used to determine the BrowsePath of the Node ... same type or a subtype of the type specified in the parent. The overriding Node may specify new values for the Node Attributes other than the NodeClass or BrowseName , however
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.1 Overview
  root of a hierarchy which mirrors the InstanceDeclarationHierarchy for the TypeDefinitionNode. Each Node in the hierarchy of the Instance will have a BrowsePath which may be the same ... TypeDefinitionNode. The InstanceDeclaration with the same BrowsePath is called the InstanceDeclaration for the Node . If a Node has an InstanceDeclaration then it shall have the same BrowseName and NodeClass
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . Standard ... ModellingRules are defined in 6.4.4.4 . The Node s within the newly created hierarchy may be copies of the InstanceDeclaration s, the InstanceDeclaration itself or another Node in the AddressSpace that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  Figure 28 . The instances A1 and A2 are allowed since B1 references the same Node with both References , whereas A3 is not allowed since two different Nodes are referenced. Note
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.1 Mandatory
  ModellingRule Mandatory means that for each existing BrowsePath on the instance a similar Node shall exist, but it is not defined whether a new Node is created or an existing ... Node is referenced. For example, the TypeDefinitionNode of a functional block "AI_BLK_TYPE" will have a setpoint "SP1". An instance of this type
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.2 Optional
  ModellingRule Optional means that for each existing BrowsePath on the instance a similar Node may exist, but it is not defined whether a new Node is created or an existing ... Node is referenced. In Figure 32 an example using the ModellingRules Optional and Mandatory is shown. The example contains an ObjectType Type_A and all valid combinations of instances named
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.3 HierarchicalReferences ReferenceType
  hierarchical-like way. HierarchicalReferences does not forbid loops. For example, starting from Node "A" and following HierarchicalReferences it may be possible to browse to Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.5 HasChild ReferenceType
  indicate that References of this type span a non-looping hierarchy. Starting from Node "A" and only following References of the subtypes of the HasChild ReferenceType it shall ... that following the References there may be more than one path leading to another Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.8 HasProperty ReferenceType
  subtype of the Aggregates ReferenceType . The semantic is to identify the Properties of a Node . Properties are described in 4.5.2 . The SourceNode of this ReferenceType can be of any NodeClass
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.9 HasOrderedComponent ReferenceType
  ReferenceType - besides the semantic of the HasComponent ReferenceType - is that when browsing from a Node and following References of this type or its subtype all References are returned
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.12 HasModellingRule ReferenceType
  Object of the ObjectType "ModellingRule" or one of its subtypes. Each Node shall be the SourceNode of at most one HasModellingRule Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.17 HasEventSource
  considered a source of Event Subscriptions. The TargetNode of this ReferenceType can be a Node of any NodeClass that can generate event notifications via a subscription to the reference source ... Starting from Node "A" and only following References of the HasEventSource ReferenceType or of its subtypes it shall never be possible to return
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.20 HasAddIn ReferenceType
  HasComponent ReferenceType . The semantic of this ReferenceType is to bind an AddIn to another Node that is the source of this Reference . The AddIn concept is described
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.21 IsDeprecated ReferenceType
  NonHierarchicalReferences ReferenceType . The semantic of this ReferenceType is to indicate that a Node has been deprecated from an information model. The SourceNode of this ReferenceType shall be a Node ... TargetNode shall be an Object which represents the information model version where the Node was first deprecated . The DisplayName and Description of the TargetNode should suggest the information model version
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.24 UsesDataTypeRefinement
  used as SourceNode for the UsesDataTypeRefinement to further refine the Structured DataType . Each Node shall be the SourceNode of at most one UsesDataTypeRefinement Reference . The TargetNode of this ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.28 UsesSubtypeRestriction
  used as SourceNode for the UsesSubtypeRestriction to further restrict the DataType . Each Node shall be the SourceNode of at most one UsesSubtypeRestriction Reference . The TargetNode of this ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.1 General
  General This Built-in DataType is composed of three elements that identify a Node within a Server . They are defined in Table 22 . Table 22 - NodeId Definition Name Type Description ... format and data type of the identifier (see 8.2.3 ). Identifier * The identifier for a Node in the AddressSpace of an OPC UA Server
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.3 IdType
  which they are defined. For certain types of NodeIds , NodeIds can uniquely identify a Node within a system, or across systems (e.g. GUIDs). System-wide and globally-unique identifiers allow
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.4 Identifier value
  element is used within the context of the first three elements to identify the Node . Its data type and format is defined by the IdType. Identifier values of IdType String ... Unicode C1 . Identifier values of IdType Opaque are restricted to 4096 bytes. A Node in the AddressSpace shall not have a null NodeId . However, many services defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.51 StructureField
  NamespaceIndex of the BrowseName shall be the same as the Structure DataType Node NamespaceIndex . OPC 10000-6 defines a number of DataEncodings which specify how to serialize Structure DataTypes . Some
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  with the OptionSetValues Property defined. It is used to define the permissions of a Node . The PermissionType is formally defined in Table 38 . Table 38 - PermissionType Definition Name Bit Description ... Browse 0 The Client is allowed to see the references to and from the Node . This implies that the Client is able to Read to Attributes other than the Value
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.56 AccessRestrictionType
  OptionSetValues Property defined. It is used to define the access restrictions of a Node . The AccessRestrictionType is formally defined in Table 39 . Table 39 - AccessRestrictionType Definition Name Bit Description SigningRequired ... Client can only access the Node when using a SecureChannel which digitally signs all messages. This does not apply to the Browse permission if the ApplyRestrictionsToBrowse is not set. EncryptionRequired
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.57 AccessLevelType
  This flag is set for Properties that define semantic aspects of the parent Node of the Property and where the Property Value , and thus the semantic, may change during operation
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.60 AttributeWriteMask
  OptionSetValues Property defined. It is used to define the Attribute access restrictions of a Node . The AttributeWriteMask is formally defined in Table ... means it is writeable. If a Node does not support a specific Attribute , the corresponding bit has to be set to 0. Table 44 - Bit mask for WriteMask and UserWriteMask
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.1 General
  change of the AddressSpace structure. The change may consist of adding or deleting a Node or Reference. Although the relationship of a Variable or VariableType to its DataType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.2 NodeVersion Property
  NodeVersion Property of Nodes . Every time a ModelChangeEvent is issued for a Node , its NodeVersion shall be changed, and every time the NodeVersion is changed, a ModelChangeEvent shall be generated
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.3 Views
  lead to several Events since it may affect different Views . If, for example, a Node was deleted from the AddressSpace , and this Node was also contained in a View ... context and another having the View "A" as context. If a Node would only be removed from View "A", but still exists in the AddressSpace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.6 GeneralModelChangeEventType
  GeneralModelChangeEventType . The GeneralModelChangeEventType is a subtype of the BaseModelChangeEventType . It contains information about the Node that was changed and the action that occurred to cause the ModelChangeEvent ... Node , delete a Node , etc.). If the affected Node is a Variable or Object , then the TypeDefinitionNode is also present. To allow Event compression, a GeneralModelChangeEvent contains an array
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.33.1 General
  change to the Value Attribute of a Property . The SemanticChangeEvent contains information about the Node owning the Property that was changed. If this is a Variable or Object , the TypeDefinitionNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  Attribute and have a value identifying their data type. They are composed of a Node which is either optional (0..1) or required (1), such as BrowseName to Base ... some special Attributes in OPC UA containing a NodeId and thereby referencing another Node . Those Attributes are represented as associations marked with the stereotype <<Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  DisplayName is shown, including the text used in the graphical representation of a Node . The BrowseName contains the NamespaceIndex and a String . Such a structure can be exposed ... BrowseName is shown, including the text used in the graphical representation of a Node . Instead of using the HasTypeDefinition reference to point from an Object or Variable to its ObjectType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.1 Description
  more Nodes into the AddressSpace hierarchy. Using this Service , each Node is added as the TargetNode of a HierarchicalReference to ensure that the AddressSpace is fully connected and that ... Node is added as a child within the AddressSpace hierarchy (see OPC 10000-3 ). When a Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  Nodes to add. All Nodes are added as a Reference to an existing Node using a hierarchical ReferenceType . This structure is defined in-line with the following indented items. parentNodeId ... Expanded NodeId ExpandedNodeId of the parent Node for the Reference . The ExpandedNodeId type is defined in 7.16 . If the server Index indicates that the parent Node is a remote Node
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.2 Parameters
  defined in-line with the following indented items. sourceNodeId NodeId NodeId of the Node to which the Reference is to be added. The source Node shall always exist ... Reference . The isForward parameter can be set to FALSE if the target Node is on the local Server and the source Node on the remote Server . referenceTypeId NodeId NodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.1 Description
  status code Bad_NodeIdUnknown is sent to the monitoring Client indicating that the Node has been deleted
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.2 Parameters
  defined in-line with the following indented items. nodeId NodeId NodeId of the Node to delete. deleteTargetReferences Boolean A Boolean parameter with the following values: TRUE delete References in TargetNodes ... that Reference the Node to delete. FALSE delete only the References for which the Node to delete is the source. The Server cannot guarantee that it is able to delete
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.5.1 Description
  Description This Service is used to delete one or more References of a Node . When any of the References deleted by an invocation of this Service are contained ... defined in-line with the following indented items. sourceNodeId NodeId NodeId of the Node that contains the Reference to delete. referenceTypeId NodeId NodeId of the ReferenceType that defines the Reference
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  requestedMax ReferencesPerNode Counter Indicates the maximum number of references to return for each starting Node specified in the request. The value 0 indicates that the Client is imposing no limitation ... defined in-line with the following indented items. nodeId NodeId NodeId of the Node to be browsed. If a view is provided, it shall include this Node. browseDirection Enum BrowseDirection
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.1 Description
  more browse paths to NodeIds . Each browse path is constructed of a starting Node and a RelativePath . The specified starting Node identifies the Node from which the RelativePath is based ... need to call this Service specifying the NodeId of "Boiler1" as starting Node and the BrowseName of the "HeatSensor" as browse path. The Service would return
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.2 Parameters
  defined in-line with the following indented items. startingNode NodeId NodeId of the starting Node for the browse path. relativePath RelativePath The path to follow from the startingNode . The last ... line with the following indented items. A Server may encounter a Reference to a Node in another Server which it cannot follow while it is processing the RelativePath . If this
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.5.2 Parameters
  return a numeric NodeIds for aliasing. In case no optimization is supported for a Node , the Server shall return the NodeId from the request
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.2 Parameters
  nodesToRead request parameter. There is one entry in this list for each Node contained in the nodesToRead parameter. diagnosticInfos [] DiagnosticInfo List of diagnostic information (see 7.12 for DiagnosticInfo definition ... nodesToRead request parameter. There is one entry in this list for each Node contained in the nodesToRead parameter. This list is empty if diagnostics information was not requested
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.1 Description
  visible in the AddressSpace . The AccessLevel Attribute defined in OPC 10000-3 indicates a Node 's support for historical values. Several request parameters indicate how the Server is to access ... underlying history data source. The EventNotifier Attribute defined in OPC 10000-3 indicates a Node 's support for historical Events . The continuationPoint parameter in the HistoryRead is used to mark
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.2 Parameters
  shall always include a timestamp. If the HistoryReadDetails is EVENTS: The NodeId of the Node whose Event history is to be read. If the Node does not support the requested ... access for historical values or historical Events the appropriate error response for the given Node shall be generated. indexRange NumericRange This parameter is used to identify a single element
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.1 Description
  different data sources and the internal Server logic. If an Attribute and Node combination is contained in more than one operation, the order of the processing is undefined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.2 Parameters
  defined in-line with the following indented items. nodeId NodeId NodeId of the Node that contains the Attributes . attributeId IntegerId Id of the Attribute . This shall be a valid Attribute ... indexRange is provided and writing of indexRange is not possible for the Node . value DataValue The Node 's Attribute value (see 7.11 for DataValue definition). If the indexRange parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.4 StatusCodes
  also used if writing of IndexRange is supported in general for a Node but the passed IndexRange cannot be written by the Server. Bad_IndexRangeNoData See Table ... such as just timestamp); than the Server shall not perform any write on this Node and shall return this StatusCode for this Node . It is also used if writing
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.5.2 Parameters
  line with the following indented items. statusCode StatusCode StatusCode for the update of the Node (see 7.38 for StatusCode definition). operationResults [] StatusCode List of StatusCodes for the operations ... performed on a Node . The size and order of the list matches the size and order of any list defined by the details element being reported by this result entry
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.2 Parameters
  Method . Independent of the methodId parameter, the RolePermissions are always verified with the Method Node that is the target of a HasComponent from the Node defined by objectId . inputArguments [] BaseDataType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  Subscription to use to send Notifications . The item to be monitored may be any Node Attribute . Notifications are data structures that describe the occurrence of data changes and Events . They ... this document (see 7.22.3 ) is used to determine if an Event received from the Node is sent to the Client . The filter also allows selecting fields of the EventType that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.6 Triggering model
  confused with the removal of the Attribute that it monitors. If the Node that contains the Attribute being monitored is deleted, the MonitoredItem generates a Notification with a StatusCode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.1 Description
  Publish response. It is possible that the MonitoredItem becomes valid again if the Node is added again to the AddressSpace and the MonitoredItem still exists. If a NodeId is known ... valid by a Server but the corresponding Node Attributes are currently not available, the Server may allow the creation of a MonitoredItem and return an appropriate Bad StatusCode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.2 RedundantServerSet Requirements
  long as all Servers in the RedundantServerSet will be updated with the same Node changes. All Servers in a RedundantServerSet shall be synchronized with respect to time. This may mean
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.3 FilterOperator
  operand. [1]: Any operand that resolves to a NodeId or ExpandedNodeId where the Node is of the NodeClass DataType . If there is any error in conversion ... applies to Strings and ByteStrings . Table 119 defines complex operators that require a target node (i.e. row) to evaluate. These operators shall be re-evaluated for each possible target node
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.1 Overview
  Literal Specifies a literal value. Attribute Specifies any Attribute of an Object or Variable Node using a Node in the type system and relative path constructed from ReferenceTypes and BrowseNames ... SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition and a relative path constructed from BrowseNames
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.4 AttributeOperand
  AttributeOperand type. Table 128 - AttributeOperand Name Type Description AttributeOperand structure Attribute of a Node in the AddressSpace . nodeId NodeId NodeId of a Node from the type system. alias String ... other locations in the filter structure. browsePath RelativePath Browse path relative to the Node identified by the nodeId parameter. See 7.30 for the definition of RelativePath . attributeId IntegerId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  SimpleAttributeOperand type. Table 129 - SimpleAttributeOperand Name Type Description SimpleAttributeOperand structure Attribute of a Node in the AddressSpace . typeDefinitionId NodeId NodeId of a TypeDefinitionNode . This parameter restricts the operand to instances ... evaluate the browsePath without considering the typeDefinitionId . browsePath [] QualifiedName A relative path to a Node . This parameter specifies a relative path using a list of BrowseNames instead of the RelativePath
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.16 ExpandedNodeId
  IdType Type of the identifier element of the NodeId . identifier * The identifier for a Node in the AddressSpace of an OPC UA Server (see NodeId definition
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.21 MonitoringParameters
  MonitoredItem . This id is used in Notifications generated for the list Node . The IntegerId type is defined in 7.19 . samplingInterval Duration The interval that defines the fastest rate at which
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.3 EventFilter
  supported by the Server and a path to an InstanceDeclaration . An InstanceDeclaration is a Node which can be found by following forward hierarchical references from the fully inherited EventType where ... Node is also the source of a HasModellingRule reference. EventTypes , InstanceDeclarations and Modelling Rules are described completely in OPC 10000-3 . In some cases the same SimpleAttributeOperand . browsePath will apply
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.2 DataChangeNotification parameter
  order of the monitoredItems parameter. There is one entry in this list for each Node contained in the monitoredItems parameter. This list is empty if diagnostics information was not requested
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.28 ReadValueId
  Identifier for an item to read or to monitor. nodeId NodeId NodeId of a Node . attributeId IntegerId Id of the Attribute . This shall be a valid Attribute id. The IntegerId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.29 ReferenceDescription
  defined in 7.16 . If the server Index indicates that the TargetNode is a remote Node , then the nodeId shall contain the absolute namespace URI. If the TargetNode is a local ... Node the nodeId shall contain the namespace index. browseName 1 QualifiedName The BrowseName of the TargetNode . displayName LocalizedText The DisplayName of the TargetNode . nodeClass 1 NodeClass NodeClass of the TargetNode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.30 RelativePath
  RelativePath . referenceTypeId NodeId The type of reference to follow from the current node. The current path cannot be followed any further if the referenceTypeId is not available on the Node ... included if this value is TRUE. targetName QualifiedName The BrowseName of the target node. The final element may have an empty targetName . In this situation all targets of the references
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.35 SessionAuthenticationToken
  subtype of the NodeId data type; however, it is never used to identify a Node in the AddressSpace . Servers may assign a value to the NamespaceIndex ; however, its meaning
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.38.2 Common StatusCodes
  requested operation. Bad_ViewIdUnknown The view id does not refer to a valid view Node. Bad_ViewTimestampInvalid The view timestamp is not available or not supported. Bad_ViewParameterMismatchInvalid The view ... specific reason is known. Bad_AttributeIdInvalid The attribute is not supported for the specified node. Bad_BrowseDirectionInvalid The browse direction is not valid. Bad_BrowseNameInvalid The browse name is invalid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.2.3 EncryptedSecret Format
  Format The EncryptedSecret uses an extensible format which has the TypeId of a DataType Node as a prefix as defined for the ExtensionObject encoding in OPC 10000-6 . The general ... Table 183 - EncryptedSecret layout Name Type Description TypeId NodeId The NodeId of the DataType Node . EncodingMask Byte This value is always 1. Length Int32 The length of the data that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.2.4 RsaEncryptedSecret DataType
  RsaEncryptedSecret structure Name Type Description TypeId NodeId The NodeId of the RsaEncryptedSecret DataType Node . EncodingMask Byte See Table 183 . Length UInt32 See Table 183 . SecurityPolicyUri String See Table 183 . Certificate
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.2.5 EccEncryptedSecret DataType
  EccEncryptedSecret Layout Name Type Description TypeId NodeId The NodeId of the EccEncryptedSecret DataType Node . EncodingMask Byte See Table 183 Length UInt32 See Table 183 SecurityPolicyUri String See Table 183 Certificate
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  A.2 BNF of RelativePath
  string that follows a '/', '.' or '>' symbol specifies the BrowseName of a target Node to return or follow. This BrowseName may be prefixed by its namespace index. If the namespace
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.1.1 Overview
  used (for a definition of this operand see 7.7.4 ): AttributeOperand: Refers to a Node, an Attribute of a Node or the Value Attribute of a Property associated with a Node
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.1 Overview
  same order as the Attributes that were passed into the Query . Query also supports Node filtering on the basis of Attribute values, as well as relationships between TypeDefinitionNodes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.2 Querying Views
  that Attribute value history may be accessed using Historical Access even if the Node is no longer in the current AddressSpace . Servers that support Query are expected to be able
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  filter. On the other hand, the Query can request data from instances of related Node types by specifying a RelativePath from an originating TypeDefinitionNode. In the filter, a separate ... defined in OPC 10000-6 . When matching instances are returned as the target node, the target node should be an instance of the specified type or subtype of the specified
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.5 QueryDataSet
  Table B.9 . Table B.9 - QueryDataSet Name Type Description QueryDataSet structure Data related to a Node returned in a Query response. nodeId ExpandedNodeId The NodeId for this Node description. typeDefinitionNode ExpandedNodeId ... NodeId for the type definition for this Node description. values [] BaseDataType Values for the selected Attributes. The order of returned items matches the order of the requested items. There
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.1 Overview
  Attribute operands (for a definition of these operands, see 7.7.4 ). AttributeOperand: Refers to a Node , an Attribute of a Node or the Value Attribute of a Property associated with ... Node . In the examples character names of ExpandedNodeId are used instead of an actual ExpandedNodeId , this also applies to Attribute Ids. The string representation of relative paths is used instead
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.3 Example Notes
  B.3.3 Example Notes For all of the examples in 7.7.4 , the type definition Node is listed in its symbolic form, in the actual call it would be the ExpandedNodeId assigned ... Node . The Attribute is the symbolic name of the Attribute , in the actual call they would be translated to the IntegerId of the Attribute . Also in all of the examples
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.4 Example 1
  example are described in Table B.10 . Table B.10 - Example 1 NodeTypeDescription Type Definition Node Include Subtypes QueryDataDescription Relative Path Attribute Index Range PersonType FALSE ".12:LastName" value ... included in the table. The Value column is returned as an array for each Node description, where the order of the items in the array would correspond to the order
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.12 Example 9
  NodeTypeDescription parameters used in the example. Table B.35 - Example 9 NodeTypeDescription Type Definition Node Include Subtypes QueryDataDescription Relative Path Attribute Index Range PersonType FALSE ".NodeId" value ... This is possible since the name referenced via the relative path and the root Node is in the View . Table B.37 - Example 9 QueryDataSets NodeId TypeDefinition NodeId RelativePath Value
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  Conventions for Node descriptions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value ... TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table, the Attributes of the composed Node are defined in the same
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  4.1 NodeIds
  symbolic names. OPC 10000-6 defines the actual NodeIds . The symbolic name of each Node defined in this standard is its BrowseName , or, when it is part of another Node ... BrowseName of the other Node , a ".", and the BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.1 General
  Table 3 shall be set as specified in Table 3 . Table 3 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each server shall provide the DisplayName identical ... BrowseName of the Node for the LocaleId "en". Whether the server provides translated names for other LocaleIds is server-specific. Description Optionally a server-specific description is provided
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.2 Objects
  specified in Table 4 . Table 4 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  Property provides the default permissions if a Server supports RolePermissions for the Namespace. A Node in the Namespace overrides this default by adding a RolePermissions Attribute to the Node ... provides the default user permissions if a Server supports UserRolePermissions for the Namespace. A Node in the Namespace overrides this default by adding a UserRolePermissions Attribute to the Node
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  return a StatusCode for the EventType indicating an error. The SourceNode Property identifies the Node that the Event originated from. If the Event is not specific to a Node ... using the default locale of the server, if the Event is specific to a Node, or some server-specific notation. Time provides the time the Event occurred. This value
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.3 AuditEventType
  BaseEventType defined in 6.4.2 , which means it inherits the InstanceDeclarations of that Node. HasProperty Variable ActionTimeStamp UtcTime PropertyType Mandatory HasProperty Variable Status Boolean PropertyType Mandatory HasProperty Variable ServerId String PropertyType ... used to describe the source of the AuditEvent. SubTypes of AuditEventType may define the Node to assign to the SourceNode Property , if not defined the SourceNode Property shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.25 AuditWriteUpdateEventType
  AuditUpdateEventType defined in 6.4.24 , which means it inherits the InstanceDeclarations of that Node. HasProperty Variable AttributeId UInt32 PropertyType Mandatory HasProperty Variable IndexRange NumericRange PropertyType Mandatory HasProperty Variable NewValue BaseDataType PropertyType ... AttributeId identifies the Attribute that was written. The SourceNode Property identifies the Node that was written. IndexRange identifies the index range of the written Attribute if the Attribute
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.31 BaseModelChangeEventType
  BaseEventType defined in 6.4.2 , which means it inherits the InstanceDeclarations of that Node. Conformance Units Base Info Model Change This EventType inherits all Properties of the BaseEventType . Their semantic ... this EventType . The SourceNode Property for Events of this type shall be the Node of the View that gives the context of the changes. If the whole AddressSpace
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.33 SemanticChangeEventType
  BaseEventType defined in 6.4.2 , which means it inherits the InstanceDeclarations of that Node. HasProperty Variable Changes SemanticChangeStructureDataType[] PropertyType Mandatory Conformance Units Base Info SemanticChange This EventType inherits all Properties ... defined in 6.4.2 . The SourceNode Property for Events of this type shall be the Node of the View that gives the context of the changes. If the whole AddressSpace
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.6 FolderType
  used to organise the AddressSpace into a hierarchy of Nodes . They represent the root Node of a subtree, and have no other semantics associated with them. However, the DisplayName
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.4 Objects
  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 ... 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.5 Types
  Types 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.6 ObjectTypes
  ObjectTypes 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 Clause ... 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.7 VariableTypes
  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 ... 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.10 EventTypes
  EventTypes 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 ... 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.11 InterfaceTypes
  InterfaceTypes This standard Object Node is the browse entry point for ObjectType Nodes that represent Interfaces . Figure 8 illustrates the structure beneath this Node showing some of the standard ObjectTypes ... 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 Interfaces because they
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.12 Locations
  Nodes which represent different types of locations. Figure 9 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects . Figure 9 - Locations organization The intent
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.16 ModelChangeStructureDataType
  ModelChangeStructureDataType Structure Name Type Description ModelChangeStructure DataType structure affected NodeId NodeId of the Node that was changed. The client should assume that the affected Node has been created or deleted ... DataType has changed as described by the verb . affectedType NodeId If the affected Node was an Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.17 SemanticChangeStructureDataType
  Table 256 - SemanticChangeStructureDataType Structure Name Type Description SemanticChangeStructureDataType structure affected NodeId NodeId of the Node that owns the Property that has changed. affectedType NodeId If the affected Node ... Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node . Otherwise it is set to null. Its representation in the AddressSpace is defined in Table
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  B.1 Overview
  simplified approach is now defined having a DataTypeDefinition Attribute on the DataType Node . It is required to only use the DataTypeDefinition Attribute approach . The deprecation of the DataTypeDictionary has eliminated
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.10 Decimal
  Structure then the DataTypeDefinition for the field shall specify the NodeId of the Decimal Node as the DataType . If a Server publishes an OPC Binary type description for the Structure
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.6 Structures
  structure Field Bytes Value Type Id 4 The identifier for the 'Type1' Binary Encoding Node Encoding 1 0x1 for ByteString Length 4 92 X 4 The value of field ... sequentially as described in 5.2.2.16 . The Value of the DataTypeDefinition Attribute for a DataType Node describing Type1 is shown in Table 30 . Table 30 - DataTypeDefinition for "Type1" from
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.7 Structures with optional fields
  fields Field Bytes Value Type Id 4 The identifier for the TypeA Binary Encoding Node Encoding 1 0x1 for ByteString Length 4 13 EncodingMask 4 0x02 ... EncodingMask defined for the parent. The Value of the DataTypeDefinition Attribute for a DataType Node describing TypeA is: Name Type Description defaultEncodingId NodeId NodeId of the "TypeA_Encoding_DefaultBinary
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.8 Unions
  value of Field1 The Value of the DataTypeDefinition Attribute for a DataType Node describing Type1 is: Name Type Description defaultEncodingId NodeId NodeId of the "Type1_Encoding_DefaultBinary" Node ... Field2" description LocalizedText Description of Field2 dataType NodeId NodeId of the Type2 DataType Node (e.g. "ns=3;s=MyType2") valueRank Int32 -1 (Scalar) arrayDimensions UInt32[] null maxStringLength
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  A.3 Numeric Node Ids
  Numeric Node Ids Clause A.3 defines the numeric identifiers for all of the numeric NodeIds defined by the OPC UA Specification. The identifiers are specified in a UTF8 encoded ... NodeClass> Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is numeric
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  specification. For example, the base NodeSet for this specification includes an unattached Property Node called "NodeVersion" which can be added to any Node . The Node in the NodeSet
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  NamespaceIndex refers to the NamespaceUris table. SymbolicName String A symbolic name for the Node that can be used as a class/field name in auto generated code. It should only ... Kept in schema for backward compatibility. AccessRestrictions AccessRestriction The AccessRestrictions that apply to the Node . This attribute is optional. If not specified the AccessRestrictions for the Model are applied. DisplayName
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.4 Reference
  Reference The Reference type specifies a Reference for a Node . The Reference can be forward or inverse. Only one direction for each Reference is required to be in a UANodeSet
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.5 RolePermission
  RolePermission The RolePermission type specifies the Permissions granted to Role for a Node . The fields in the RolePermission type are defined in Table F.4 . Table F.4 - RolePermission Element Type Description
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.6 UAType
  Table F.5 . Table F.5 - UANodeSet Type Nodes Subtype Description UAObjectType Defines an ObjectType Node as described in OPC 10000-3 . UAVariableType Defines a VariableType Node as described ... UADataType Defines a DataType Node as described in OPC 10000-3 . UAReferenceType Defines a ReferenceType Node as described
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.7 UAInstance
  detail below. Table F.6 - UANodeSet Instance Nodes Subtype Description UAObject Defines an Object Node as described in OPC 10000-3 . UAVariable Defines a Variable Node as described ... UAMethod Defines a Method Node as described in OPC 10000-3 . UAView Defines a View Node as described in OPC 10000-3 . Table F.7 - UAInstance Element Type Description
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.9 UAMethod
  UAMethod is a subtype of the UAInstance defined in F.7 . It represents a Method Node. The fields in the UAMethod type are defined in Table F.9 . Table F.9 - UAMethod Element ... Method Nodes that are a target of a HasComponent reference from a single Object Node . It is the NodeId of the UAMethod with the same BrowseName contained in the TypeDefinition
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.13 DataTypeField
  NodeId of the DataType for the field. This NodeId can refer to another Node with its own DataTypeDefinition . This field is not specified for Enumeration or OptionSet DataTypes . ValueRank Int32
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.14 Variant
  F.14 Variant The Variant type specifies the value for a Variable or VariableType Node . This type is the same as the type defined in 5.3.1.17 . As a result, the functions
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.15 Example
  /Alias> </Aliases> The BicycleType is a DataType Node that inherits from a DataType defined in another InformationModel (ns=2;i=314). It is assumed that any application ... ManufacturerName" DataType="String" /> </Definition> </UADataType> This Node is an instance of an Object TypeDefinition Node defined in another InformationModel
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.16 UANodeSetChanges
  single operation. This allows mandatory Nodes or References to be replaced by specifying a Node / Reference to delete and a Node / Reference
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.17 NodesToAdd
  AddressSpace . When adding Nodes , References can be specified as part of the Node definition or as a separate ReferencesToAdd . Note that References to Nodes that could exist are always allowed ... other words, a Node is never rejected simply because it has a reference to an unknown Node . Reverse References are added automatically when deemed practical by the processor
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.19 ReferenceToChange
  F.18 . Table F.18 - ReferencesToChange Element Type Description Source NodeId The identifier for the source Node of the Reference . ReferenceType NodeId The identifier for the type of the Reference . IsForward Boolean ... Reference is a forward reference. Target NodeId The identifier for the target Node of the Reference . References to Nodes that could exist are always allowed. In other words, a Reference
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.21 NodeToDelete
  F.21 NodeToDelete The NodeToDelete type specifies a Node to remove from an AddressSpace . The elements of the type are defined in Table F.20 . Table F.20 - ReferencesToChange Element Type Description Node ... NodeId The identifier for the Node to delete. DeleteReverseReferences Boolean If TRUE, then References to the Node are deleted as well
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.3.2 Using Dictionary References
  identifier ( SyntaxReferenceId ), see 6.3.3 When calling the Browse Service for a Quantity or Unit Node , the response includes the HasDictionaryEntry Reference together with the well-defined NodeId for the SyntaxReferenceEntryType
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.3 Item
  Server is used as the BrowseName and the DisplayName for the Node in the COM UA Wrapper. See also clause A.3.1.5 . The ItemId in the DA server is used ... part of the NodeId for the Node . See also clause A.3.1.5 . TimeZone property in the DA server is represented by a TimeZone Property. The Description property value
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.2 HasTrueSubState ReferenceType
  subtype of the NonHierarchicalReferences ReferenceType . The semantics indicate that the sub state (the target Node ) is a subordinate state of the True super state. If more than one state within
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.3 HasFalseSubState ReferenceType
  subtype of the NonHierarchicalReferences ReferenceType . The semantics indicate that the sub state (the target Node ) is a subordinate state of the False super state. If more than one state within
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.2 ConditionType
  identifies the ConditionSource . See 5.12 for more details. If the ConditionSource is not a Node in the AddressSpace, the NodeId is set to NULL. The SourceNode Property is the Node ... same as the InputNode for an Alarm , but it may be a separate node. For example, a motor, which is a Variable with a Value that
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.4 Disable Method
  ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . Since Condition instances are not required to be defined in the AddressSpace , the MethodId that is passed
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.5 Enable Method
  ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . If the Condition instance is not exposed, then it may be difficult for a Client to determine
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.6 AddComment Method
  ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . Signature AddComment( [in] ByteString EventId [in] LocalizedText Comment ); The parameters are defined in Table 15 Table ... specified ObjectId is not valid or that the Method was called on the ConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidArgument The Comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.3 Acknowledge Method
  ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node . Signature Acknowledge( [in] ByteString EventId [in] LocalizedText Comment ); The parameters are defined in Table 34 Table ... specified ObjectId is not valid or that the Method was called on the AcknowledgeableConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidArgument The Comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.4 Confirm Method
  ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node. Signature Confirm( [in] ByteString EventId [in] LocalizedText Comment ); The parameters are defined in Table 37 Table ... specified ObjectId is not valid or that the Method was called on the AcknowledgeableConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidArgument The Comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.5 Reset Method
  ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Reset(); This method has no arguments. Method result codes in Table 44 (defined in Call service ... specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidState The Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.6 Reset2 Method
  specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidState The Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.7 Silence Method
  ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Silence(); This method has no arguments. Method result codes in Table 49 (defined in Call service ... specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Comments If the instance
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.8 Suppress Method
  ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Suppress(); Method Result Codes in Table 51 (defined in Call Service) Table 51 - Suppress result codes ... specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Comments Suppress Method applies
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.9 Suppress2 Method
  specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidArgument The Comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.10 Unsuppress Method
  ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Unsuppress(); Method Result Codes in Table 56 (defined in Call Service). Table 56 - Unsuppress result codes ... specified ObjectId is not valid or that the Method was called on the AlarmConditionType Node . See 10000-4 for the general description of this result code. Comments Unsuppress Method applies