Search

200 result(s) for Reference

• 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
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.9 Hierarchical Reference
  Hierarchical Reference Reference that is used to construct hierarchies in the AddressSpace Note 1 to entry: All hierarchical ReferenceTypes are derived from HierarchicalReferences
• 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.3.1 Conventions for AddressSpace figures
  TargetNode . References may also be shown by drawing an arrow that starts at the Reference name in the "References" box and ends at the TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  Data type of the Attribute Defines the Attribute References "Reference name" "1", "0..1" or "0..*" Not used Describes ... Reference by the NodeClass Standard Properties "Property name" "M" or "O" Data type of the Property Defines the Property The Name column contains
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  defined using the ReferenceType NodeClass (see 5.3 ). The Node that contains the Reference is referred to as the SourceNode and the Node that is referenced is referred ... 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 are considered
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  General OPC UA Servers shall provide type definitions for Objects and Variables . The HasTypeDefinition Reference shall be used to link an instance with its type definition represented by a TypeDefinitionNode ... TypeDefinitionNode (see 6.4 for details). In some cases, the NodeId used by the HasTypeDefinition Reference will be well-known to Clients and Servers . Organizations may define TypeDefinitionNodes that are well
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.4 Instantiation of complex TypeDefinitionNodes
  TYPE", called AI_BLK_1", has a HasTypeDefinition Reference to "AI_BLK_TYPE". It also contains a Variable "SP" having the same BrowseName ... constraints related to programming against the TypeDefinitionNode . A TypeDefinitionNode or an InstanceDeclaration shall never reference two Nodes having the same BrowseName using forward hierarchical References . Instances based on InstanceDeclarations shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  below. Rules for applying Interfaces : When an ObjectType references an Interface with a HasInterface Reference or a subtype, the following rules apply: Each mandatory InstanceDeclaration of the fully-inherited InstanceDeclaration­Hierarchy ... fulfilled (e.g. name collisions) the ObjectType cannot apply the Interface , i.e. it shall not reference the Interface with a HasInterface Reference of a subtype. The rules apply for each referenced
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.3 AddIn model
  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 and there is no special ... supertype for AddIns . To identify instances as an AddIn , the HasAddIn Reference or a subtype shall be used. The AddIn ObjectType shall include the definition of a default BrowseName using
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.1 General
  defined using the ReferenceType NodeClass as specified in Table 9 . In contrast, a Reference is an inherent part of a Node and no NodeClass is used to represent References . This ... boolean Attribute with the following values: TRUE it is an abstract ReferenceType , i.e. no Reference of this type shall exist, only of its subtypes. FALSE it is not an abstract
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  that all hierarchical References be instantiated as bidirectional to ensure browse connectivity. A bidirectional Reference is modelled as two separate References . As an example of a unidirectional Reference ... know its signal sink. The signal sink would have a "Sourced By" Reference to the signal source, without the signal source having the corresponding "Sourced
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.3 HasSubtype References
  used to define subtypes of ReferenceTypes . It is not required to provide the HasSubtype Reference for the supertype, but it is required that the subtype provides the inverse Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted to the Node the Property belongs to. Attribute value changes ... define additional Properties for Views . Views can be the SourceNode of any hierarchical Reference . They shall not be the SourceNode of any NonHierarchical Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Objects can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasTypeDefinition 1 The HasTypeDefinition Reference points to the type definition ... have exactly one type definition and therefore be the SourceNode of exactly one HasTypeDefinition Reference pointing to an ObjectType . See 4.6 for a description of type definitions. HasEventSource
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  HasSubtype 0..* HasSubtype References identify ObjectTypes that are subtypes of this type. The inverse Reference identifies the parent type of this type. GeneratesEvent 0..* GeneratesEvent References identify the type ... indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted to the Node the Property belongs to. Attribute value changes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.3 Standard ObjectType FolderType
  introduced for those Folder Objects , the Organizes ReferenceType . The SourceNode of such a Reference should always be a View or an Object of the ObjectType FolderType ; the TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.4 Client-side creation of Objects of an ObjectType
  ObjectType Objects are always based on an ObjectType , i.e. they have a HasTypeDefinition Reference pointing to its ObjectType . Clients can create Objects using the AddNodes Service defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Variables can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasProperty 0..* HasProperty References are used to identify the Properties ... complex DataVariables to identify their composed DataVariables . Properties are not allowed to use this Reference . HasTypeDefinition 1 The HasTypeDefinition Reference points to the type definition of the Variable. Each Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.3 Properties
  SourceNode of any hierarchical References . This includes the HasComponent or HasProperty Reference , that is, Properties do not contain Properties and cannot expose their complex structure. However, they ... SourceNode of any NonHierarchical References . The HasTypeDefinition Reference points to the VariableType of the Property . Since Properties are uniquely identified by their BrowseName , all Properties shall point to the PropertyType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  contain DataVariables . Therefore each DataVariable shall be the TargetNode of at least one HasComponent Reference coming from an Object , an ObjectType , a DataVariable or a VariableType . DataVariables shall ... TargetNode of any HasProperty References . Therefore, a HasComponent Reference pointing to a Variable Node identifies it as a DataVariable . The HasTypeDefinition Reference points to the VariableType used as type definition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  HasSubtype 0..* HasSubtype References identify VariableTypes that are subtypes of this type. The inverse Reference identifies the parent type of this type. GeneratesEvent 0..* GeneratesEvent References identify the type ... indicate the version of a Node . The NodeVersion Property is updated each time a Reference is added or deleted to the Node the Property belongs to. Attribute value changes except
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.6 Client-side creation of Variables of an VariableType
  VariableType Variables are always based on a VariableType , i.e. they have a HasTypeDefinition Reference pointing to its VariableType . Clients can create Variables using the AddNodes Service defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Methods can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). GeneratesEvent 0..* GeneratesEvent References identify the type of Events that ... HasArgumentDescription References are used to specify argument metadata. If the SourceNode of this Reference is defined on an InstanceDeclaration the TargetNode shall use the Mandatory ModellingRule . <other References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  HasSubtype References may be used to span a data type hierarchy. The inverse Reference identifies the parent type of this type. HasEncoding 0..* HasEncoding References identify the encodings ... Enumeration, and Simple DataTypes are not allowed to be the SourceNode of a HasEncoding Reference . Each concrete Structured DataType shall point to at least one DataTypeEncoding Object with the BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.2 DataTypeRefinement Objects
  subtype. A DataTypeRefinement Object shall always be referenced using a HasDataTypeRefinement Reference (see 7.30 ) or subtype from exactly one DataType Node representing a Structured DataType that is being refined ... field having a refinement, a Variable of BaseDataVariableType or subtype is referenced using a Reference of HasFieldDescription ReferenceType (see 7.25 ) or a subtype. The BrowseName of the Variable shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.3 Usage of DataTypeRefinements
  DataTypeRefinements are expressed in an OPC UA information model, by using the non-hierarchical Reference UsesDataTypeRefinement (see 7.24 ) or a subtype. Those References always starts from an instance
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  SubtypeRestriction Object is bound to a DataType by a HasDataTypeRefinement Reference from the DataType to the SubtypeRestriction Object . Each SubtypeRestriction Object shall be referenced from exactly one DataType Node using ... HasDataTypeRefinement Reference . A SubtypeRestriction Object is referencing Variables with an AllowedSubtype Reference (see 7.29 ), and thereby restricting that the DataType including ValueRank and ArrayDimensions of the Variable is allowed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.1 InstanceDeclaration
  InstanceDeclaration is an Object , Variable or Method that references a ModellingRule with a HasModellingRule Reference and is the TargetNode of a hierarchical Reference from a TypeDefinitionNode or another InstanceDeclaration . There ... shall be no two TypeDefinitionNodes referencing the same InstanceDeclaration with a hierarchical Reference, either directly or from another InstanceDeclaration of that TypeDefinitionNode , i.e. an InstanceDeclaration belongs to exactly one TypeDefinitionNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.5 BrowsePath
  sequence of BrowseNames used to describe a path between Nodes related w ith a Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.2 Fully-inherited InstanceDeclarationHierarchy
  have ModellingRules ). All InstanceDeclarations of the InstanceDeclarationHierarchy and all Nodes referenced with a NonHierarchical Reference from such an InstanceDeclaration are added to the table. Hierarchical References to Nodes without ... table so it does not need to be added. However, the HasNotifier reference from "/" to "/B" does not exist and was added. The Nodes and References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  first and then "J" can be overridden in a second step. A Reference is replaced if it goes between two overridden Nodes and has the same ReferenceType ... Reference defined in the supertype. The Reference specified in the subtype may be a subtype of the ReferenceType used in the parent type. Any NonHierarchical References specified for the overridden
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  initial values. An instance shall not be a SourceNode of a hierarchical Reference that has the same BrowsePath as an InstanceDeclaration of its TypeDefinition which has an optional or mandatory
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode as the InstanceDeclaration or a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.2 Optional
  similar to the InstanceDeclaration F, etc. If there would be a NonHierarchical Reference between E and F in the InstanceDeclaration­Hierarchy , it is not specified if it occurs in the instance ... hierarchy or not. In the case of A10, there could be a reference from E to one F but not to the other F, or to both or none
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.3 ExposesItsArray
  type. The Variable A having this ModellingRule shall be referenced by a forward hierarchical Reference from a VariableType B. B shall have a ValueRank value that is equal ... data that is managed in the array of B. Each instance of B shall reference one instance of A for each of its array elements. The used Reference shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  have a Folder for DeviceParameters, and the DeviceParameters should be connected with a HasComponent Reference . However, the names of the DeviceParameters are specific to the instances. The example is shown
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.2 References ReferenceType
  abstract ReferenceType ; only concrete subtypes of it shall be used as a Reference between Nodes in an OPC UA AddressSpace . There is no semantic associated with this ReferenceType . This
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.3 HierarchicalReferences ReferenceType
  only subtypes of it can be used and they shall be a non-symmetric Reference . The semantic of HierarchicalReferences is to denote that References of HierarchicalReferences span a hierarchy ... again. It is not permitted to have a Property as SourceNode of a Reference of any subtype of this abstract ReferenceType . It is not allowed that the SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.7 HasComponent ReferenceType
  Aggregates ReferenceType . The semantic is a part-of relationship. The TargetNode of a Reference of the HasComponent ReferenceType is a part of the SourceNode . This ReferenceType is used to relate ... relationship semantic. That is, it is not specified if the TargetNode of a Reference of the HasComponent ReferenceType is deleted when the SourceNode is deleted. The TargetNode of this ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.10 HasSubtype ReferenceType
  NodeClass as the SourceNode . Each ReferenceType shall be the TargetNode of at most one Reference of type HasSubtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.13 HasTypeDefinition ReferenceType
  VariableType . Each Variable and each Object shall be the SourceNode of exactly one HasTypeDefinition Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.18 HasNotifier
  Objects that are a source of Event Subscriptions . If the TargetNode of a Reference of this type generates an Event , then this Event shall also be provided in the SourceNode ... Reference . An example of a possible organization of Event References is represented in Figure 39 . In this example an unfiltered Event subscription directed to the "Pump" Object will
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.20 HasAddIn ReferenceType
  bind an AddIn to another Node that is the source of this Reference . The AddIn concept is described in 4.10.3 . The SourceNode of this ReferenceType shall be an Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.24 UsesDataTypeRefinement
  Structured DataType . Each Node shall be the SourceNode of at most one UsesDataTypeRefinement Reference . The TargetNode of this ReferenceType shall be an Object of DataTypeRefinementType SubtypeRestrictionType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.28 UsesSubtypeRestriction
  restrict the DataType . Each Node shall be the SourceNode of at most one UsesSubtypeRestriction Reference . The TargetNode of this ReferenceType shall be an Object of SubtypeRestrictionType or a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  References are represented as UML associations marked with the stereotype <<Reference>>. If a particular ReferenceType is used, its name is used as the role name, identifying ... direction of the Reference (e.g. Aggregates has the subtype HasComponent ). For simplicity, the inverse role name is not shown (in the example SubtypeOf ). When no role name is provided
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3.6 Variable and VariableType
  Variable shall not be the SourceNode of a HasProperty or any other HierarchicalReferences Reference. All Variables having "A" as the SourceNode of a HasProperty Reference shall have
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  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 or VariableType the name ... line. Figure C.2 gives an example, where "Node1" uses a Reference and "Node2" the shortcut in both notation variants. A figure can contain HasTypeDefinition References
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  definition). nodesToAdd [] AddNodesItem List of 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 ... 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.1 Description
  Nodes . The NodeClass is an input parameter that is used to validate that the Reference to be added matches the NodeClass of the TargetNode . This parameter is not validated ... Reference refers to a TargetNode in a remote Server . In certain cases, adding new References to the AddressSpace shall require that the Server add new Server ids to the Server
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.2 Parameters
  Header Common request parameters (see 7.32 for RequestHeader definition). referencesToAdd [] AddReferences Item List of Reference instances to add to the SourceNode . The targetNodeClass of each Reference in the list shall ... 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 in the Server
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.1 Description
  Nodes deleted by an invocation of this Service is the TargetNode of a Reference , then those References are left unresolved based on the deleteTargetReferences parameter. Servers may delete additional Nodes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.2 Parameters
  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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.5.1 Description
  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 to delete. isForward ... Boolean If the value is TRUE, the Server deletes a forward Reference. If the value is FALSE, the Server deletes an inverse Reference. targetNodeId ExpandedNodeId NodeId of the TargetNode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.2 Parameters
  defined in-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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.2 Parameters
  super type of that ObjectType shall be the source of a HasComponent Reference (or subtype of HasComponent Reference ) to the Method specified in methodId . In case of an ObjectType ... ObjectType shall be the source of a HasComponent Reference (or subtype of HasComponent Reference ) to the Method specified in methodId. In this case the Method shall not have a ModellingRule
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.3 FilterOperator
  related to a NodeId of the type defined in operand[1] by the Reference type defined in operand[2]. operand[0] or operand[1] can also point to an element ... Reference where the referred to element is another RelatedTo operator. This allows chaining of relationships (e.g. A is related to B is related to C), where the relationship is defined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.2 ElementOperand
  greater than the element index it is part of and it does not Reference a non-existent element. Clients shall construct filters in this way to avoid circular and invalid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.29 ReferenceDescription
  parameter are defined in Table 168 . Table 168 - ReferenceDescription Name Type Description ReferenceDescription structure Reference parameters returned for the Browse Service . referenceTypeId NodeId NodeId of the ReferenceType that defines ... Reference . isForward Boolean If the value is TRUE, the Server followed a forward Reference . If the value is FALSE, the Server followed an inverse Reference . nodeId Expanded NodeId NodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  A.2 BNF of RelativePath
  followed. A '!' in front of the BrowseName is used to indicate that the inverse Reference should be followed. The BrowseName may be qualified with a namespace index (indicated ... wildcard operation that matches all Nodes which are the target of the Reference specified by the path. & The & sign character is the escape character. It is used
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  related instances in the RelativePath , the Client can optionally ask for References . A Reference is requested via a RelativePath that only includes a ReferenceType . If all References are desired than ... list of instances of the Node type. dataToReturn [] QueryDataDescription Specifies an Attribute or Reference from the originating typeDefinitionNode along a given relativePath for which to return data. This structure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  described below. All Property values are assumed to be string unless otherwise noted New Reference types: "HasChild" derived from HierarchicalReference. "HasAnimal" derived from HierarchicalReference. "HasPet ... StreetAddress". HasProperty "City". HasProperty "ZipCode". May have HasChild reference to a node of type PersonType. May have HasAnimal reference to a node of type AnimalType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.8 Example 5
  Figure B.9 . Figure B.9 - Example 5 filter logic tree In this example, one Reference to PersonType is aliased to "Parent" and another Reference to PersonType is aliased
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.9 Example 6
  displaying part of the AddressSpace of the Server . This request includes listing a Reference as something that is to be returned. Example 6: Get PersonType.NodeId, AnimalType.NodeId, PersonType.HasChild Reference, PersonType.HasAnimal Reference ... example the browse name is provided in parentheses and in the case of Reference types on the browse name is provided. For the References listed in Table B.27 , the value
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.10 Example 7
  Query for information below this starting point. Example 7: Get PersonType.NodeId, AnimalType.NodeId, PersonType.HasChild Reference, PersonType.HasAnimal Reference where the person is in Area2 (Cleveland nodes) and the person has a child ... example the browse name is provided in parentheses and in the case of Reference types on the browse name is provided. For the References listed in Table B.31 , the value
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  symbolic name for a NodeId , i.e., the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying the symbolic ... rule in the ModellingRule column. In the AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object . If the NodeId of a DataType is provided
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  4.1 NodeIds
  case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.8 ReferenceTypes
  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 ... 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.16 ModelChangeStructureDataType
  client should assume that the affected Node has been created or deleted, had a Reference added or deleted, or the DataType has changed as described by the verb . affectedType NodeId ... added. NodeDeleted 1 Indicates the affected Node has been deleted. ReferenceAdded 2 Indicates a Reference has been added. The affected Node may be either a SourceNode or TargetNode . Note that
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  static UAInstances. The field shall not be specified for UAInstances that are InstanceDeclarations . References Reference [] The list of References for the Node . RolePermissions RolePermission [] The list of RolePermissions ... starting with the 'ListOf' prefix. A UANodeSet is expected to contain many UANodes which reference each other. Tools that create UANodeSets should not add Reference elements for both directions
• 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 ... other direction shall be added automatically during any import operation. The fields in the Reference type are defined in Table F.3 . Table F.3 - Reference Element Type Description NodeId NodeId
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.16 UANodeSetChanges
  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.18 ReferencesToChange
  type are defined in Table F.17 . Table F.17 - ReferencesToChange Element Type Description Reference ReferenceToChange A Reference to add to the AddressSpace
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.19 ReferenceToChange
  F.19 ReferenceToChange The ReferenceToChange type specifies a single Reference to add to or remove from an AddressSpace . The elements of the type are defined in Table 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 TRUE if the Reference
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.3.2 Using Dictionary References
  Using Dictionary References HasDictionaryEntry is used to define the relationship to a Syntax Reference by referencing from quantity or unit Nodes to an instance of a SyntaxReferenceEntryType . Each quantity ... instances of the SyntaxReferenceEntryType NodeId structure namespaceIndex UInt16 The NamespaceTable index for the Syntax Reference URI (see Table 38 ). IdType Enum String identifier * The Syntax Reference identifier ( SyntaxReferenceId
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.5.1 HasEngineeringUnitDetails
  TargetNode of this ReferenceType shall be an Instance of the ServerUnitType ObjectType . The Reference has to change if the value (the concrete EngineeringUnit ) is changing. Clients can subscribe
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.10 Condition instances in the AddressSpace
  AddressSpace as an instance of some temperature transmitter Object with a HasComponent Reference to an instance of a LimitAlarmType . The availability of instances allows Data Access Clients to monitor
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.11 Alarm and Condition auditing
  Events are supported by the Server . For example, the Disable Method has an AlwaysGeneratesEvent Reference to an AuditConditionEnableEventType . An Event of this type shall be generated for every invocation
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.2 Two-state state machines
  TypeDefinition Modelling Rule Subtype of the StateVariableType defined in 10000-16 . Note that a Reference to this subtype is not shown in the definition of the StateVariableType HasProperty Variable ... Read Service to get the values of the TrueState and FalseState Property . A HasTrueSubState Reference is used to indicate that the True state has sub states. A HasFalseSubState Reference
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.2 HasTrueSubState ReferenceType
  representation in the AddressSpace is specified in Table 3 . The SourceNode of the Reference shall be an instance of a TwoStateVariableType and the TargetNode shall be either an instance ... subtype of a StateMachineType . It is not required to provide the HasTrueSubState Reference from super state to sub state, but it is required that the sub state provides the inverse
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.3 HasFalseSubState ReferenceType
  representation in the AddressSpace is specified in Table 4 . The SourceNode of the Reference shall be an instance of a TwoStateVariableType and the TargetNode shall be either an instance ... subtype of a StateMachineType . It is not required to provide the HasFalseSubState Reference from super state to sub state, but it is required that the sub state provides the inverse
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.4 HasAlarmSuppressionGroup ReferenceType
  Table 5 This ReferenceType binds an AlarmSuppressionGroup to an Alarm . The SourceNode of the Reference shall be an instance of an AlarmConditionType or sub type. The TargetNode shall
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.5 AlarmGroupMember ReferenceType
  concrete ReferenceType that can be used directly. It is a subtype of the Organizes Reference Type. This ReferenceType is used to indicate the Alarm instances that are part ... representation in the AddressSpace is specified in Table 6 The SourceNode of the Reference shall be an instance of an AlarmGroupType or sub type of it. The TargetNode shall
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.6 AlarmSuppressionGroupMember ReferenceType
  representation in the AddressSpace is specified in Table 7 The SourceNode of the Reference shall be an instance of an AlarmGroupType or sub type of it. The TargetNode shall
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.2 EventNotifier and source hierarchy
  linked together and with the included ConditionSources using the HasNotifier and the HasEventSource Reference Types . The Server Object shall be the root of this hierarchy. Figure 26 shows such ... HasNotifier is a sub-type of HasEventSource . I.e. the target Node of a HasNotifier Reference (an Event notifying Object ) may also be a ConditionSource . The HasEventSource Reference is used
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.3 Adding Conditions to the hierarchy
  Adding Conditions to the hierarchy HasCondition is used to reference Conditions . The Reference is from a ConditionSource to a Condition instance or - if no instance is exposed by the Server ... first browsing for ConditionSources following HasEventSource References (including sub-types like the HasNotifier Reference ) and then browsing for HasCondition References from all target Nodes of the discovered References . Figure
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.5 Conditions in a VariableType
  since Variables (and VariableTypes ) are not allowed to be the source of a HasComponent Reference to an Object. Figure 29 provides an example of this use case. Note that there ... LvelMonitoring" Alarm . It is Server -specific whether and where they assign a HasComponent Reference . Figure 29 - Use of HasCondition in a VariableType
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.2 HasEffectDisable
  point from a Transition to an Alarm that will be disabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are disabled
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.3 HasEffectEnable
  point from a Transition to an Alarm that will be enabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are enabled
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.5 HasEffectUnsuppressed
  from a Transition to an Alarm that will no longer be suppressed. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.2 AddressSpace examples
  provided with Organizes and Aggregates References . Figure B.5 illustrates the use of the HasCondition Reference with Condition instances. Figure B.5 - HasCondition used with Condition instances In systems where Conditions ... available as instances, the ConditionSource can reference the ConditionTypes instead. This is illustrated with the example in Figure B.6 . Figure B.6 - HasCondition reference to a Condition type Figure B.7 provides
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  that depends on the UA Server . It is always the target of a HasNotifier Reference from the Server Node . The root Area allows multiple A&E COM Server ... combination of machine and COM Server . Each Area is the target of HasNotifier Reference from its parent Area. It may be the source of one or more HasNotifier Reference
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.2 Event sources
  SubscribeToEvents flag is True and the Source is a target of a HasNotifier Reference . If source filtering is not supported the SubscribeToEvents flag is False and the Source ... target of a HasEventSource Reference . The Sources are discovered by calling BrowseOPCAreas and the GetQualifiedSourceName Method s. The Source name returned by BrowseOPCAreas is used as the BrowseName and DisplayName
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.4 Event attributes
  Server are represented in the UA Server as Variables which are targets of HasProperty Reference s from the ObjectTypes which represent the Event Categories. The BrowseName and DisplayName
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.7 Browse mapping
  leaves. The A&E COM UA Proxy relies on the "HasNotifier" Reference to assemble a hierarchy of branches/areas such that each Object Node which contains a HasNotifier ... Reference and whose EventNotifier Attribute is set to SubscribeToEvents is considered an area. The root for the HasNotifier hierarchy is the Server Object . Starting at the Server Object , HasNotifier Reference
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.9.3 Filter by source
  Event s from sources which are not discoverable by following only HasNotifier and/or HasEventSource Reference s. Thus, source filters will only apply if the source string can be matched
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.1 Overview
  Program's state transitions. These Effects are Events. Each Transition shall have a HasEffect Reference to a ProgramTransitionEventType and can have an AuditProgramTransitionEventType. When the transition occurs, Event notifications
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.6.2 DomainDownloadType
  with the states of the base Program. Table A.8 - TransferStateMachineType Additional References Source Path Reference Type Is Forward Target Path ToSending ToState True Sending FromState True Opening HasCause True Start ... purpose. The ProgramTransitionEventType effect referenced by the SendingToSending state transition has an IntermediateResultData Object Reference . The IntermediateResultData Object serves to identify two Variables whose values are obtained each time
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  HistoricalConfiguration Object is added to or deleted from a Server or a Reference to a HistoricalConfiguration Object is added to or deleted from a Node , a GeneralModelChangeEvent shall be generated
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.3.2 HasHistoricalConfiguration ReferenceType
  that the target Node is "used" by the source Node of the Reference . Its representation in the AddressSpace is specified in Table 7 . Table 7 - HasHistoricalConfiguration ReferenceType Attributes
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.1 General
  point in their own information models and use the HasCurrentData or the HasCurrentEvent Reference to indicate the source node for the data or Event . Mirroring Variables is typically simple. Variables
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.2 HistoryServerCapabilitiesType
  ServerCapabilitiesType Objects for any OPC UA Server supporting Historical Access shall contain a Reference to a HistoryServerCapabilitiesType Object . The content of this BaseObjectType is already defined by its type definition
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.1 General
  used in processed data retrieval and in historical retrieval. This definition includes both standard Reference types and Object types
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.1 General
  definition. All Instances of the FolderType use the standard BrowseName of 'AggregateFunctions'. The HasComponent Reference is used to relate a ServerCapabilities Object and/or any HistoryServerCapabilitiesType Object to an AggregateFunction Object ... Conformance Units Historical Access Aggregates Each ServerCapabilities and HistoryServerCapabilitiesType Object shall reference an AggregateFunction Object . In addition, each HistoricalConfiguration Object belonging to a HistoricalDataNode may reference an AggregateFunction Object using
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.10.5 ActionMethods
  NodeId of a Method that is the target of a HasComponent Reference from the ObjectType of the Object . The namespace of the NodeId shall be added to the namespaces
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.6.6 HasPushedSecurityGroup
  Object of the ObjectType SecurityGroupType defined in 8.4.1 . Servers shall provide the inverse Reference that relates a SecurityGroup Object back to a PubSubKeyPushTargetType Object. The representation of the HasPushedSecurityGroup ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.6 HasPubSubConnection
  Object of type PubSubConnectionType defined in 9.1.5.2 . Servers shall provide the inverse Reference that relates a PubSubConnection Object back to the PublishSubscribe Object. The representation of the HasPubSubConnection ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.1 PublishedDataSetType
  DataSetWriter for the PublishedDataSet is removed from a group, the Reference to this DataSetWriter shall also be removed from this list. The group model is defined in 9.1.6 . The Property
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.5 DataSetToWriter
  defined in 9.1.7.1 . Each DataSetWriter Object shall be the TargetNode of exactly one DataSetToWriter Reference . Servers shall provide the inverse Reference that relates a DataSetWriter Object back to a PublishedDataSetType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.9 HasWriterGroup
  instance of the WriterGroupType defined in 9.1.6.3 . Servers shall provide the inverse Reference that relates a WriterGroup Object back to a PubSubConnectionType Object. The representation of the HasWriterGroup ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.10 HasReaderGroup
  instance of the ReaderGroupType defined in 9.1.6.6 . Servers shall provide the inverse Reference that relates a ReaderGroup Object back to a PubSubConnectionType Object. The representation of the HasReaderGroup ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.4 AddDataSetWriter Method (Deprecated)
  instance of the WriterGroup . A successful creation of the DataSetWriter shall also create a Reference from the related PublishedDataSet Object to the created DataSetWriter . The Client should be authorized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.5 RemoveDataSetWriter Method (Deprecated)
  before removing the Object . A successful removal of the DataSetWriter shall also delete the Reference from the related PublishedDataSetType Object to the removed DataSetWriter . The Client should be authorized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.6 HasDataSetWriter
  instance of the DataSetWriterType defined in 9.1.7.1 . Servers shall provide the inverse Reference that relates a DataSetWriter Object back to a WriterGroupType Object. The representation of the HasDataSetWriter ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.12 HasDataSetReader
  instance of the DataSetReaderType defined in 9.1.8.1 . Servers shall provide the inverse Reference that relates a DataSetReader Object back to a ReaderGroupType Object. The representation of the HasDataSetReader ReferenceType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.3 SubscribedDataSetMirrorType
  Conformance Units PubSub Model SubscribedDataSet Mirror An Object of this type shall reference a mirror Object with HasComponent where the name of the Object is based on the ParentNodeName ... used to set the SubscribedDataSet into the mirror mode. The mirror Object shall reference Variables for each DataSet field in the DataSetMetaData with HasComponent . The name, DataType , ValueRank and ArrayDimensions
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  this document. Because all SafetyProviders and SafetyConsumers on this Server contain a hierarchical Reference from this Object to themselves, it can be used to directly access all SafetyProviders and SafetyConsumers ... SafetyACSet is intended for safety-related purposes only. It should not reference non-safety -related items. See Table 3 for the definition of the SafetyACSet. Table 3 - SafetyACSet definition Attribute
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.5 Object SafetyPDUs
  ResponseSPDUDataType BaseDataVariableType Mandatory Placeholder Conformance units SafetyPDUs The Object SafetyPDUs shall contain exactly one Reference to a Variable of DataType RequestSPDUDataType and exactly one Reference to a Variable
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.6 FiniteStateMachineType
  Transition is a StateType Object which is the target of a FromState Reference . The final State for a Transition is a StateType Object which is the target of a ToState ... Reference . The FromState and ToState References shall always be specified. A Transition may produce an Event . The Event is indicated by a HasEffect Reference to a subtype of BaseEventType
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.9 StateType
  referenced from the ObjectType FiniteStateMachineType or one of its subtypes using a HasComponent Reference or a subtype of HasComponent and shall not have a ModellingRule as they are not applied
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.11 TransitionType
  referenced from the ObjectType FiniteStateMachineType or one of its subtypes using a HasComponent Reference or a subtype of HasComponent and shall not have a ModellingRule as they are not applied ... instances. Each valid Transition shall have exactly one FromState Reference and exactly one ToState Reference , each pointing to an Object of the ObjectType StateType . Each Transition can have
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.16 HasSubStateMachine
  subtypes. Each Object can be the TargetNode of at most one HasSubStateMachine Reference . The SourceNode (the state) and the TargetNode (the SubStateMachine ) shall belong to the same StateMachine . Therefore ... TargetNode shall be referenced from the same ObjectType , both using a HasComponent Reference or a subtype of HasComponent . The representation of the HasSubStateMachine ReferenceType in the AddressSpace is specified
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.2 StateMachineType with a SubStateMachine using inheritance
  representing a SubStateMachine . The "State1" references this Object with a HasSubStateMachine Reference , thus it is a SubStateMachine of "State1". Since "MySubMachine" is an Object
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.4 Example of a StateMachine having Transition to SubStateMachine
  used in several places, it is not possible to add a bi-directional Reference from one of the shared States of the SubStateMachine to another StateMachine . In this case ... SubStateMachine to a State of another sub-machine, both, the FromState and the ToState Reference , are handled uni-directional. A Client shall be able to handle the information
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.6.2 ChoiceStateType
  subtype) defined on any leaving Transition ( Transitions referencing the ChoiceState with the FromState Reference or a subtype). Table 20 - ChoiceStateType Attribute Value BrowseName ChoiceStateType IsAbstract False References NodeClass BrowseName DataType
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.6.4 GuardVariableType
  Only if the semantic is "True", the Transition connected via a HasGuard Reference can be used. The value of the GuardVariableType provides the semantic of the Guard
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.2 AliasNameType ObjectType Definition
  other locale shall be provided. This Object shall have at least one AliasFor Reference (or subtype of). A Client shall always ignore the namespace associated with an AliasName for comparison
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.3.1 Definition
  number of instances of AliasNameType. Each instance shall have at least one AliasFor Reference to a Node . Multiple < Alias > instances can point to the same Node. <SubAliasNameCategories
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.3 AliasNames in an aggregating Server
  exception that in the aggregating Server the target Nodes referenced by the AliasFor Reference could be in other Servers . Figure A.2 provides an illustration of an example aggregating Server
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.5 Client use of an AliasName Server
  FindAlias Method call returns a list of all ExpandedNodeIds that the AliasName has a Reference to. It is important to note that there could be more than one Node referenced
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  6.1 HasDictionaryEntry ReferenceType
  concrete ReferenceType and can be used directly. It is a subtype of NonHierarchicalReferences . The Reference to the dictionary entry for any Node is provided by HasDictionaryEntry . The SourceNode of this
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.3.1 Overview
  CertificateGroups Folder in the ServerConfiguration Object. In these cases, DCAs shall add a Reference from the ServerConfiguration CertificateGroups Folder to the CertificateGroup Object under the Application
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.4.2 Communication Folder
  formally defined in Table 51 . The Communication Object is referenced by an Organizes Reference from the Resources Object defined in 5.4.1 . The Communication Object can include the following subfolders: MappingTables
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.6.1 UsesPriorityMappingTable ReferenceType
  Type IetfBaseNetworkInterfaceType . Each Node shall be the SourceNode of at most one UsesPriorityMappingTable Reference . The TargetNode of this ReferenceType shall be an instance of PriorityMappingTableType . The UsesPriorityMappingTable ReferenceType is formally
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.7.2 Definition
  used directly. It is a subtype of NonHierarchicalReferences . It is a symmetric Reference , that is, it provides the same semantic in both directions. The semantic of this ReferenceType
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.8.2 Definition
  used directly. It is a subtype of NonHierarchicalReferences . It is a symmetric Reference , that is, it provides the same semantic in both directions. The semantic of this ReferenceType
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.9.2 Definition
  used directly. It is a subtype of HierarchicalReferences . It is a symmetric Reference , that is, it provides the same semantic in both directions The semantic of this ReferenceType
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.10.2 Definition
  used directly. It is a subtype of HierarchicalReferences . It is a symmetric Reference , that is, it provides the same semantic in both directions. The semantic of this ReferenceType
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.1 Overview
  References . This concept is intentionally a simple construct, where the only information of a Reference is the SourceNode , the TargetNode , the ReferenceType and for asymmetric ReferenceTypes the direction (forward ... inverse). Sometimes, it is desirable to add more information to such a Reference . The concept of a ReferenceDescription keeps the simple Reference unchanged, and creates a Variable which is used
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.2 Reference Refinement
  Reference Refinement Sometimes, a high-level Reference might be refined by more fine granular References , including a more detailed path. For example, DeviceA controls DeviceB (see Figure 3 , A)). This ... refined with ports and switches (see Figure 3 , D)). Figure 3 - Examples of Reference Refinements Without providing Reference refinement, there may be multiple paths possible (e.g., several switches, see Figure
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.3.1 ReferenceDescriptionVariableType
  BaseDataVariableType . It is used as container to expose additional information of a Reference . The Value contains the description of the Reference the Variable represents. The Reference as defined ... Variable . The IsForward field in the Value indicates the browsable direction of the Reference . It is not required that the opposite direction is browsable. The VariableType is formally defined
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.4.1 HasReferenceDescription
  link to a ReferenceDescription either from a Node directly participating in the Reference that is described in the ReferenceDescription (as SourceNode or TargetNode ), or from a Node somehow related ... Reference that is described (e.g. in the refinement of the Reference (being part of the refinement path)). The SourceNode of References of this type can be of any NodeClass
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.5.1 ReferenceDescriptionDataType
  ReferenceDescriptionDataType This structure contains the description of a Reference . The structure is defined in Table 16 . Table 16 - ReferenceDescriptionDataType Structure Name Type Description ReferenceDescriptionDataType structure SourceNode NodeId The SourceNode ... Reference. ReferenceType NodeId The ReferenceType of the Reference. IsForward Boolean The direction of the Reference. If TRUE in forward direction, if FALSE in inverse direction. For symmetric References it shall
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.5.2 ReferenceListEntryDataType
  ReferenceListEntryDataType This structure contains the description of a Reference without SourceNode . It can be used to list a path of References without repeating the SourceNode , like in the ReferenceRefinement Property ... Type Description ReferenceListEntryDataType structure ReferenceType NodeId The Node Id of the ReferenceType used as Reference. IsForward Boolean The direction of the Reference, if TRUE in forward direction, if FALSE
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  A.1 Overview
  Overview The ReferenceDescription defined in 0 keeps the simple construct of a Reference and adds a Variable to provide additional information. This approach allows to handle the References natively without
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  A.2 Alternative Approach: Intermediate Object
  Node . The disadvantage of the approach is, that a Client cannot natively follow the Reference to the target directly, but always gets to the intermediate Object first and from there ... original target. Therefore, the ReferenceDescription uses an approach, where the Reference directly connects both Nodes without the need to deal with an intermediate Object . Figure A.1 - Refinement of References
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.2 SerializedData Variable
  DataType Node including the DataTypeDefinition Attribute is dynamically created. It only has an inverse Reference to its supertype Structure . Clients must obtain the NodeId by reading the DataType Attribute
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.4 Include- and ExcludeReferenceTypes Properties
  create the SerializationScope : The IncludeReferenceTypes Property contains an array of ReferenceType NodeIds . Any Reference of each ReferenceType NodeId of the array including their subtypes is considered. The ExcludeReferenceTypes Property contains ... array of ReferenceType NodeIds . Any Reference of each ReferenceType NodeId of the array including their subtypes is removed from the results out of the IncludeReferenceType Property . The exclude rules determined
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.5 HasSerializationEntity ReferenceType
  subtype of the HierarchicalReferences ReferenceType. The semantic of this ReferenceType is to reference the serialized data of the SourceNode of the Reference . The SourceNode of this ReferenceType shall
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  6.2 LogRecord EventType Mapping
  event fields that are mapped to the LogRecordStructure . Any Object that has a Reference to one of these EventTypes shall generate LogRecords in the LogObject related to the defined BaseLogEventType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.6 FunctionalEntities and applications
  only to be changed by a specific entity or Role . Multiple ControlGroups might reference overlapping data. ControlGroups might be created dynamically or be pre-configured as part of an application ... more information, see the definition of the ControlGroupType in 6.5 . ControlGroups use a Controls Reference defined in OPC 10000-23 to indicate who owns the ControlGroup . Transportation of data between
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.9.2 PubSub
  PubSub configuration model is not exposed by this Server , this Reference may point to a Node that is not accessible. If the Reference cannot be created, an appropriate StatusCode shall ... SubscribedDataSet associated with the referenced DataSetReader for each element in ConnectionEndpointConfigurations having a ToDataSetReader Reference . If ExpectedSubscribedDataSetVersion MajorVersion is 0 (for the definition of MajorVersion
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.2 FxAssetType definition
  case or a user-specific naming scheme. This could be, for example, a reference to an electric scheme." " ComponentName is a user-writable name provided by the integrator ... multiple Assets . A connector provides more information about an Asset connection than a simple Reference can. For a formal definition of the AssetConnectorType, see 6.3.4 . Diagnostics is a FunctionalGroup ( Folder
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.5 SlotType definition
  Each Slot that has a module plugged into it shall have a HasPhysicalComponent Reference (see OPC 10000-23 ) or a subtype of it, or an IsPhysicallyConnectedTo Reference or a subtype
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.2 ControlGroupType definition
  this bit is set, the controlling entity can be determined by following the Controls Reference or by the information in the Lock Object (i.e., the Lock LockingClient ) in either ... long as the Status of the ConnectionEndpoint is different from Error . A Controls Reference (see OPC 10000-23 ) shall be added with a SourceNode of the ConnectionEndpoint and the TargetNode
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.3 EstablishControl method
  acquired, the Method shall set the IsControlled flag and create the Controls Reference . It is recommended that this Method be restricted to Client connections that have the well-known Role
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.4 ReleaseControl method
  shall create the appropriate parameters for the ExitLock Method . It shall remove the Controls Reference from the ControlGroup . It is recommended that this Method be restricted to Client connections that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.5 ReassignControl method
  ControlGroup in the ListToRestrict and ListToBlock . It shall reassign the SourceNode of the Controls Reference (see OPC 10000-23 ) to the controlling entity as defined by the LockContext . It shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.3 PubSubConnectionEndpointType definition
  PubSubConnectionEndpointModeEnum 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionEndpoint PubSub Table 76 - PubSubConnectionEndpointType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:ToDataSetReader True 0:Objects 0:Server 0:PublishSubscribe 0:<PubSubConnection ... shall require the following references: If Mode is PublisherSubscriber , a ToDataSetReader and a ToDataSetWriter Reference are required. If Mode is Publisher , a ToDataSetWriter Reference is required; there shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  BaseDataVariableType O, RO ConformanceUnits UAFX ConnectionManager Base Table 90 - ConnectionConfigurationSetType additional references SourceBrowsePath Reference Type IsForward TargetBrowsePath 4:<ServerAddress> 4:ToAutomationComponentConfiguration True 4:<AutomationComponentConfiguration ... details on how to update the value. The ToAutomationComponentConfiguration Reference is used to link a ServerAddress to AutomationComponentConfiguration (see 6.14 ). The ServerAddress provides the Connection information to address the referenced
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.13.3.2 PubSubCommunicationFlowConfigurationType definition
  following relations: Unicast Publishing ConnectionEndpointConfiguration , if specified, references the PubSubCommunicationFlowConfiguration Object using the ToOutboundFlow Reference . Subscribing ConnectionEndpointConfiguration , if specified, shall reference the single instance of the <SubscriberConfiguration> using ... ToInboundFlow Reference . Multicast Publishing ConnectionEndpointConfiguration , if specified, references the PubSubCommunicationFlowConfiguration Object using the ToOutboundFlow Reference . Subscribing ConnectionEndpointConfigurations , if specified, shall reference the < SubscriberConfiguration > Objects using the ToInboundFlow Reference
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.40 PortableRelativePathElement
  Subtype of Structure defined in OPC 10000-5 ReferenceTypeId 0:PortableNodeId The type of Reference to follow from the current node. The current path cannot be followed any further
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.2 ConnectedTo ReferenceType
  IsPhysicallyConnectedTo ReferenceType . The semantic of this ReferenceType is to link together Assets . This Reference indicates that the Asset the Reference points to is a part connected to the Asset , which ... starting point of the Reference by means of an electrical cable. Typically, the Assets are at different physical locations, even if the physical location is not a great distance
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.4 HasBuiltInAsset ReferenceType
  this ReferenceType is to link together Assets . It indicates that the Asset the Reference points to is an integral part of the Asset , which is the starting point ... Reference . Asset information is provided for spare part handling of Assets that are related to the source Assets . HasBuiltInAsset also means that the Target cannot be extracted from the source
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.15 HasPart ReferenceType
  HasContainedComponent ReferenceType . The semantic of this ReferenceType is to link together FxAssetType instances. This Reference indicates that the Asset the Reference points to is a removable part inside the Asset ... same physical location and, therefore, the same Asset location information. An example of this Reference is a PCI board plugged inside a PC. The PCI board is located inside
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.18 IsPartOfRedundantAssetSet ReferenceType
  ReferenceType is a concrete ReferenceType and can be used directly. It is a symmetric Reference and is a subtype of NonHierarchicalReferences ReferenceType . The semantic of this ReferenceType is to link ... Assets that are redundant. An Asset may have multiple IsPartOfRedundantAssetSet References . This Reference provides no additional information related to redundancy; it only indicates Assets that are part of a redundant
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.3.2 Extending an existing OPC UA model using AddIns
  model using AddIns Extending the type definition with AddIns is done by adding the Reference HasAddIn to the FunctionalEntityType and FxAssetType . During instantiation, this leads to the creation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.2.1 Modelling of Asset relationships
  between the Assets . In OPC UA, relationships can be modelled as References , where a Reference provides semantic information about the relationship. OPC UA has defined a number of References ... removed. HasAttachedComponent indicates that an Asset has physically/mechanically attached another Asset (this reference is a subtype of HasPhysicalComponent). IsPhysicallyConnectedTo (symmetric) indicates that two Assets are physically connected to each other
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.2.2 Example single board computer model
  resulting instance model. This figure only includes the instance information related to the ConnectedTo Reference ; it does not include all of the other mandatory items that would ... instance. The USB cable is represented by the ConnectedTo Reference . The Adaptor is its own Asset and might have its own configuration that is omitted here. Figure D.2 - MyRaspberryPiType Instance
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.2 Modelling of FunctionalEntity relationships
  symmetric) relates two entities which represent the same entity in the real world. This Reference can be used, for example, to relate a FunctionalEntity with its counterpart in the event ... related with RepresentsSameEntityAs. RepresentsSameFunctionalityAs (symmetric) relates two entities representing the same functionality. This Reference can be used, for example, to relate a FunctionalEntity with its counterpart in a companion specification
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.1 Overview
  this clause indicate "poor man's references" instead of an actual Reference . The line will indicate if the poor man's reference is using a NodeId
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.4.1 Raspberry Pi example
  FunctionalEntity example in D.3.3 for the SenseHat ( Figure D.19 ). It shows the IsExecutingOn Reference between the MyApplicationProgram FunctionalEntity and the MyRaspberryPiInstance Asset. Figure D.34 - AutomationComponent example Figure D.35 provides
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.4 ConnectionConfigurationSet and DataSetWriter
  derived from the ConnectionEndpointParameter and the PubSubCommunicationFlow . Figure E.28 - ConnectionConfigurationSet and DataSetWriter The ToDataSetWriter Reference can be derived from either the PreconfiguredPublishedDataSet or from a custom PublishedDataSet within the PubSubConfiguration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.5 ConnectionConfigurationSet and DataSetReader
  values are set to correspond to the Publisher of the DataSetMessage. The ToDataSetReader Reference can be derived from either the PreconfiguredSubscribedDataSet or from a custom SubscribedDataSet within the PubSubConfiguration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.2.1 References
  ServerAddress in the ConnectionConfigurationSetConfDataType . Indices are defined as Int32 ; a negative number indicates no Reference exists
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.2.5 UAFX FunctionalEntity
  ConformanceUnits . Server UAFX IFunctionalEntity InputData Supports InputData of the IFunctionalEntity Interface . This includes a Reference to at least one Variable . Server UAFX IFunctionalEntity OutputData Supports OutputData of the IFunctionalEntity Interface ... This includes a Reference to at least one Variable . Server UAFX IFunctionalEntity ConfigurationData Supports ConfigurationData of the IFunctionalEntity Interface . This includes a Reference to at least one Variable . Server UAFX
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying the symbolic ... rule in the ModellingRule column. In the AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object . If the NodeId of a DataType is provided
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.2 Additional References
  Table 4 is used. Table 4 - <some>Type Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined ... separate rows of a nested table. ReferenceType name True = forward Reference . TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.1 NodeIds
  case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.7 DeviceType
  DeviceType with the default value. Relevant Browse Service requests can then return a Reference to this Property on the type definition. That way, no extra Nodes are required
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  5.5 ConnectsTo and ConnectsToParent ReferenceTypes
  topological connection. It is NonHierarchical and symmetric, because this is natural for this Reference . The ConnectsTo Reference exists between a Network and the connected Devices (or their ConnectionPoint , respectively). Browsing ... Network returns the connected Devices ; browsing from a Device , one can follow the ConnectsTo Reference from the Device's ConnectionPoint to the Network . The ConnectsToParent ReferenceType is a concrete ReferenceType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.3.1 General
  that are schematically identical, i.e., there exist component Objects , FunctionalGroups, and so on. A Reference connects online and offline representations and allows to navigate between them. This is illustrated ... Online/Offline is supported, the main (leading) instance represents the offline information. Its HasTypeDefinition Reference points to the concrete configured or identified ObjectType . All Parameters of this instance represent offline data
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.3.2 IsOnline ReferenceType
  subtype of a ComponentType . Each Device shall be the source of at most one Reference of type IsOnline . The IsOnline ReferenceType is illustrated in Figure 28 . Its representation ... AddressSpace is specified in Table 52 . Figure 28 - Type hierarchy for IsOnline Reference Table 52 - IsOnline ReferenceType Attributes Value BrowseName 1:IsOnline InverseName OnlineOf Symmetric False IsAbstract False References NodeClass
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying the symbolic ... rule in the ModellingRule column. In the AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object . If the NodeId of a DataType is provided
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.2 Additional References
  Table 4 is used. Table 4 - <some>Type Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined ... separate rows of a nested table. ReferenceType name True = forward Reference . TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.1 NodeIds
  case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  7 Identification of Asset
  Object shall have the BrowseName 2: Identification and shall be referenced with a hierarchical Reference from the Object representing an asset. The ObjectType of the 2: Identification Object shall ... either a Property of the Object representing the asset or referenced with a hierarchical Reference from the 2: Identification Object . The Property value shall not be an empty String
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  9.6 Tracking of health information
  provide the information, when history tracking started, a HistoryDataConfiguration is referenced with a HasHistoricalConfiguration Reference (see OPC 10000-11 for details). When the Server wants to provide information for tracking
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.3 AddLink Method
  managed resource by adding a Variable according to the input arguments with a HasComponent Reference to the Object the Method is called on. The server shall manage the added link
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.3.3.1 General
  point HierarchicalLocations (see 13.3.3.2 ). Each Object referenced from the HierarchicalLocations Object with an Organizes Reference or a subtype represents the highest level of a location hierarchy. The ObjectType for those ... ObjectType . Companion specifications might further refine the ObjectType . These Objects may reference other Objects with hierarchical References , exposing deeper level of the hierarchy. The ReferenceType is not further restricted
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.3.3.2 HierarchicalLocations Object
  ObjectType 0:FolderType Conformance Units AMB Hierarchical Location Objects Objects referenced with an Organizes Reference or a subtype are considered to be the root of a location hierarchy. The HierarchicalLocations
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.4.3.1 General
  point OperationalLocations (see 13.4.3.2 ). Each Object referenced from the OperationalLocations Object with an Organizes Reference or a subtype represents the highest level of a hierarchy of operational locations. The ObjectType ... ObjectType . Companion specifications might further refine the ObjectType . These Objects may reference other Objects with hierarchical References , exposing deeper level of the hierarchy. The ReferenceType is not further restricted
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.4.3.2 OperationalLocations Object
  ObjectType 0:FolderType Conformance Units AMB Operational Location Objects Objects referenced with an Organizes Reference or a subtype are considered to be the root of a hierarchy of operational locations
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  14.1 Sub-Assets
  References is used. Sub-assets shall be referenced from the asset with a hierarchical Reference , preferable 0: HasComponent or a subtype of it. Assets may reference their sub-assets directly
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  14.2 Relations to other Assets
  given. X:Asset1 and X:Asset2 are related with the symmetric 0: PhysicallyConnectTo Reference . X:Subasset1.1 utilizes X:Subsubasset1.2.1 using the 0: Utilizes Reference . Figure 18 - Example of relations between
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  symbolic name for a NodeId , i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node . The ModellingRule of the referenced component is provided by specifying the symbolic ... rule in the ModellingRule column. In the AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object . If the NodeId of a DataType is provided
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.2 Additional References
  Table 4 is used. Table 4 - <some>Type Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined ... separate rows of a nested table. ReferenceType name True = forward Reference . TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.1 NodeIds
  case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique