Search
140 result(s) for TargetNode
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model3.1.16 TargetNodeTargetNode 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 Model3.1.7 DataVariableObjects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model3.1.13 PropertyProperty Variables that are the TargetNode for a HasProperty Reference Note 1 to entry: Properties describe the characteristics of a Node
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelarrow that passes through them begins at the SourceNode and points to the TargetNode . References may also be shown by drawing an arrow that starts at the Reference name ... References" box and ends at the TargetNode
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.4.4 ReferencesSourceNode and the Node that is referenced is referred to as the TargetNode . The combination of the SourceNode , the ReferenceType and the TargetNode are used in OPC UA Services ... ReferenceTypes ). Figure 4 illustrates this model of a Reference . Figure 4 - Reference Model The TargetNode of a Reference may be in the same AddressSpace or in the AddressSpace of another
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.6.3 Subtypinginterval. The vendor would do this by creating a new VariableType which is a TargetNode for a HasSubtype reference from the original VariableType and adding the new Property
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.10.2 Interface ModelTypeDefinitionNode . A BaseInterfaceType or any subtype of BaseInterfaceType shall not be the TargetNode of a HasTypeDefinition Reference . Figure 8 illustrates example Interfaces : ISerializeServiceType, an Interface to convert the Object
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.3.1 GeneralReferenceType is the same as seen from both the SourceNode and the TargetNode. FALSE the meaning of the ReferenceType as seen from the TargetNode is the inverse of that ... Reference , which is the meaning of the ReferenceType as seen from the TargetNode . References HasProperty 0..* Used to identify the Properties (see 5.3.3.2 ). HasSubtype 0..* Used to identify subtypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.3.2 AttributesContains" is used in References that specify that the SourceNode contains the TargetNode . The inherited DisplayName Attribute contains a translation of the BrowseName. The BrowseName of a ReferenceType shall ... meaning of the ReferenceType is the same for both the SourceNode and TargetNode . If a ReferenceType is symmetric, the InverseName Attribute shall be omitted. Examples of symmetric ReferenceTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelReference should always be a View or an Object of the ObjectType FolderType ; the TargetNode can be of any NodeClass . Organizes References can be used in any combination with HasChild
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.3 Propertiesshall 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 Model5.6.4 DataVariableObjectTypes and complex VariableTypes may also contain DataVariables . Therefore each DataVariable shall be the TargetNode of at least one HasComponent Reference coming from an Object , an ObjectType , a DataVariable ... VariableType . DataVariables shall not be the TargetNode of any HasProperty References . Therefore, a HasComponent Reference pointing to a Variable Node identifies it as a DataVariable . The HasTypeDefinition Reference points
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.7.1 Method NodeClassargument metadata. If the SourceNode of this Reference is defined on an InstanceDeclaration the TargetNode shall use the Mandatory ModellingRule . <other References> 0..* Methods may contain other References ... Methods . Standard ReferenceTypes are described in Clause 7 . A Method shall always be the TargetNode of at least one HasComponent Reference . The SourceNode of these HasComponent References shall
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelMethod NodeClass . The SourceNode of this ReferenceType shall be a Method and the TargetNode of this ReferenceType shall be a Variable
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.3 DataType NodeClassSourceNode of other types of References . However, they may be the TargetNode of other References
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.2.1 InstanceDeclarationVariable 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
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelsubtype of this abstract ReferenceType . It is not allowed that the SourceNode and the TargetNode of a Reference of the ReferenceType HierarchicalReferences are the same, that
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelsubtype of HasChild . The semantic is to indicate a part (the TargetNode ) belongs to the SourceNode . It does not specify the ownership of the TargetNode . There are no constraints defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelsubtype of the 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 ... represents a part-of 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
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modeldescribed in 4.5.2 . The SourceNode of this ReferenceType can be of any NodeClass . The TargetNode shall be a Variable . By using the HasProperty Reference , the Variable is defined as Property
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modeltype shall be an ObjectType , a VariableType , a DataType or a ReferenceType and the TargetNode shall be of the same NodeClass as the SourceNode . Each ReferenceType shall be the TargetNode
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelObject of the ObjectType FolderType or one of its subtypes (see 5.5.3 ). The TargetNode of this ReferenceType can be of any NodeClass
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelSourceNode of this ReferenceType shall be an Object , Variable or Method . The TargetNode shall be an Object of the ObjectType "ModellingRule" or one of its subtypes. Each Node
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelshall be an Object or Variable . If the SourceNode is an Object , then the TargetNode shall be an ObjectType ; if the SourceNode is a Variable , then the TargetNode shall
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelReferences of this type shall be a subtype of the Structure DataType . The TargetNode of this ReferenceType shall be an Object of the ObjectType DataTypeEncodingType or one of its subtypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.15 GeneratesEventthis type shall be an ObjectType , a VariableType or a Method InstanceDeclaration . The TargetNode of this ReferenceType shall be an ObjectType representing EventTypes , that is, the BaseEventType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.16 AlwaysGeneratesEventcall. The SourceNode of References of this type shall be a Method InstanceDeclaration . The TargetNode of this ReferenceType shall be an ObjectType representing EventTypes , that is, the BaseEventType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.17 HasEventSourcegenerates events. Note the ObjectType is not considered a source of Event Subscriptions. The TargetNode of this ReferenceType can be a Node of any NodeClass that can generate event notifications
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.18 HasNotifiernotifying Objects . It is a subtype of the HasEventSource ReferenceType defined in 7.16 . The TargetNode of this ReferenceType shall be Objects that are a source of Event Subscriptions ... TargetNode of a Reference of this type generates an Event , then this Event shall also be provided in the SourceNode of the Reference . An example of a possible organization
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelReferenceType shall be an Object or ObjectType . Interfaces shall not be a SourceNode . The TargetNode shall be of a subtype of the BaseInterfaceType . One SourceNode can refer to multiple Interfaces
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelSourceNode of this ReferenceType shall be an Object or ObjectType . The TargetNode shall be an Object . One SourceNode can refer to multiple AddIns
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelmodel. The SourceNode of this ReferenceType shall be a Node of any NodeClass . The 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 and other suggestions
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.22.1 OverviewStructure DataType . When the Value of the SourceNode is a scalar then the TargetNode shall be a Variable which represents a field of the Structure DataType. The BrowseName ... When the Value of the SourceNode is an array then the BrowseName of the TargetNode shall be <V[N]> where 'V' is the BrowseName of the Parent Node
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelthis ReferenceType is to provide some generic association between two Objects . The SourceNode and TargetNode of References of this type shall be Objects
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelDataType . Each Node shall be the SourceNode of at most one UsesDataTypeRefinement Reference . The TargetNode of this ReferenceType shall be an Object of DataTypeRefinementType SubtypeRestrictionType ... subtype. The DataType of the SourceNode and the DataType refined in the TargetNode shall be identical, no subtypes are allowed
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.25 HasFieldDescriptionReferences of this type shall be an Object of DataTypeRefinementType or a subtype. The TargetNode of this ReferenceType shall be a Variable of BaseDataVariableType or a subtype. The BrowseName
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelDataType . 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. The DataType ... SourceNode and the DataType restricted in the TargetNode shall be identical
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.29 AllowedSubtypeshall be an Object of SubtypeRestrictionType (see OPC 10000-5 ) or a subtype. The TargetNode of this ReferenceType shall be a Variable of BaseDataVariableType or a subtype. The DataType, ValueRank
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelDataType . The SourceNode of References of this type shall be a DataType . The TargetNode of this ReferenceType shall be a DataTypeRefinement Object or a subtype
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelB.2 Notationname of the Attribute is displayed as the role name of the TargetNode . The value of the OPC Attribute BrowseName is represented by the UML object name, for example
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelC.2.2 Simple notationbetween Nodes with a closed and filled arrow on the side pointing to the TargetNode . Near the line has to be a text containing the string-part of the BrowseName ... References shown on the left. The single hashed line has to be near the TargetNode . HasProperty The notation provides a shortcut for HasProperty References shown on the left. The double
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.2.1 DescriptionNodes 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 the Node
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.3.1 Descriptionused to validate that the Reference to be added matches the NodeClass of the TargetNode . This parameter is not validated if the Reference refers to a TargetNode in a remote
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.3.2 ParameterstargetNodeClass of each Reference in the list shall match the NodeClass of the TargetNode . This structure is defined in-line with the following indented items. sourceNodeId NodeId NodeId ... overrides the serverIndex in the targetNodeId . targetNodeId Expanded NodeId Expanded NodeId of the TargetNode . The ExpandedNodeId type is defined in 7.16 . If the server Index indicates that the TargetNode
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.4.1 DescriptionWhen any of the 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
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.5.1 Descriptionvalue is FALSE, the Server deletes an inverse Reference. targetNodeId ExpandedNodeId NodeId of the TargetNode of the Reference . 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. deleteBidirectional Boolean A Boolean parameter with
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.16 ExpandedNodeIdstring representation. serverIndex Index Index that identifies the Server that contains the TargetNode . This Server may be the local Server or a remote Server . This index is the index
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.29 ReferenceDescriptionFALSE, the Server followed an inverse Reference . nodeId Expanded NodeId NodeId of the TargetNode as assigned by the Server identified by the Server index. The ExpandedNodeId type is defined ... 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
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Modelvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model11.25 HasKeyValueDescriptionthat can be used directly. It is a subtype of the NonHierarchicalReferences ReferenceType . The TargetNode of this ReferenceType shall be a Variable representing a supported configuration property. The SourceNode
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelReference has been added. The affected Node may be either a SourceNode or TargetNode . Note that an added bidirectional Reference is reflected by two changes one with the affected Node ... being the SourceNode , and the second with the affected Node being the TargetNode . ReferenceDeleted 3 Indicates a Reference has been deleted. The affected Node may be either a SourceNode
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.15 Examplecould map the references onto another OPC UA Server by adding a ServerIndex to TargetNode NodeIds . The structure of the DataType is defined by the Definition element. This information
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data AccessSourceNode of References of this type shall be a Variable with EUInformation DataType . The TargetNode of this ReferenceType shall be an Instance of the ServerUnitType ObjectType . The Reference
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access6.5.2 HasQuantitythis type shall be a Variable with EUInformation DataType (typically the EngineeringUnits Property) . The TargetNode of this ReferenceType shall be an Instance of the QuantityType ObjectType . The HasQuantity is formally
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsSourceNode of the Reference shall be an instance of a TwoStateVariableType and the TargetNode shall be either an instance of a TwoStateVariableType or an instance of a subtype
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsSourceNode of the Reference shall be an instance of a TwoStateVariableType and the TargetNode shall be either an instance of a TwoStateVariableType or an instance of a subtype
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsReference shall be an instance of an AlarmConditionType or sub type. The TargetNode shall be an instance of an AlarmGroupType . Table 5 - HasAlarmSuppressionGroup ReferenceType Attributes Value BrowseName HasAlarmSuppressionGroup InverseName IsAlarmSuppressionGroupOf
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsReference shall be an instance of an AlarmGroupType or sub type of it. The TargetNode shall be an instance of an AlarmConditionType or a subtype of it. Table 6 - AlarmGroupMember
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsReference shall be an instance of an AlarmGroupType or sub type of it. The TargetNode shall be an instance of an AlarmConditionType or a subtype of it, or an instance
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionsshall be an ObjectType or VariableType Node or one of their InstanceDeclaration Nodes . The TargetNode shall be a Condition instance declaration or a ConditionType . The following rules for instantiation apply ... Type shall exist in instances of these Types as well. If the TargetNode in the Type definition is a ConditionType , the same TargetNode will be referenced on the instance. HasCondition
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.2 HasEffectDisableshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of an Object or AlarmType . The representation of the HasEffectDisable ReferenceType
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.3 HasEffectEnableshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectEnable ReferenceType in the AddressSpace
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionsshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectSuppressed ReferenceType in the AddressSpace
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionsshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectUnsuppressed ReferenceType in the AddressSpace
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub8.6.6 HasPushedSecurityGroupPubSubKeyPushTargetType or an ObjectType that is a subtype of PubSubKeyPushTargetType defined in 8.6.1 . The TargetNode of this ReferenceType shall be an Object of the ObjectType SecurityGroupType defined in 8.4.1 . Servers
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.3.6 HasPubSubConnectionReferences of this type shall be the PublishSubscribe Object defined in 8.3.2 . The TargetNode of this ReferenceType shall be an Object of type PubSubConnectionType defined in 9.1.5.2 . Servers shall provide
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.4.2.5 DataSetToWriterPublishedDataSetType or an ObjectType that is a subtype of PublishedDataSetType defined in 9.1.4.2.1 . The TargetNode of this ReferenceType shall be an Object of the ObjectType DataSetWriterType 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 Object. The representation
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.5.9 HasWriterGroupthis type shall be an instance of the PubSubConnectionType defined in 9.1.5.2 . The TargetNode of this ReferenceType shall be an instance of the WriterGroupType defined in 9.1.6.3 . Servers shall provide
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.5.10 HasReaderGroupthis type shall be an instance of the PubSubConnectionType defined in 9.1.5.2 . The TargetNode of this ReferenceType shall be an instance of the ReaderGroupType defined in 9.1.6.6 . Servers shall provide
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.6.6 HasDataSetWriterthis type shall be an instance of the WriterGroupType defined in 9.1.6.3 . The TargetNode of this ReferenceType shall be an instance of the DataSetWriterType defined in 9.1.7.1 . Servers shall provide
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.6.12 HasDataSetReaderthis type shall be an instance of the ReaderGroupType defined in 9.1.6.6 . The TargetNode of this ReferenceType shall be an instance of the DataSetReaderType defined in 9.1.8.1 . Servers shall provide
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.12 FromStateshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode of this ReferenceType shall be an Object of the ObjectType StateType
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.13 ToStateshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode of this ReferenceType shall be an Object of the ObjectType StateType
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.14 HasCauseshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasCause ReferenceType in the AddressSpace
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.15 HasEffectshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . If the TargetNode is an EventType , each time the Transition
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.16 HasSubStateMachineSourceNode of this ReferenceType shall be an Object of the ObjectType StateType . The TargetNode shall be an Object of the ObjectType StateMachineType or one of its subtypes. Each Object ... TargetNode of at most one HasSubStateMachine Reference . The SourceNode (the state) and the TargetNode (the SubStateMachine ) shall belong to the same StateMachine . Therefore, the SourceNode shall be referenced from
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.6.3 HasGuardshall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode shall be a Variable of the VariableType GuardVariableType or one of its subtypes. The representation
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesAliasName shall be listed in the AliasNames array multiple times, one for each TargetNode . It is not required for an AliasName Server to check the existence of external Nodes ... entry in the parallel arrays duplicates an existing AliasName entry (exact same AliasName , TargetNode and TargetServer ) or it appears more than once in the array it shall be ignored
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesSourceNode of References of this type shall be an Object of type AliasNameType . The TargetNode of this ReferenceType can be of any NodeClass. Figure 2 provides an illustration
-
OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Referenceprovided by HasDictionaryEntry . The SourceNode of this ReferenceType can be any Node . The TargetNode of this ReferenceType shall be an Object of DictionaryEntryType or one of its subtypes. Each Node
-
OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary ReferenceTwoStateDiscreteType can use HasDictionaryEntry References with SourceNode being the TrueState and FalseState Properties and TargetNode being the DictionaryEntry Nodes. EnumDictionaryEntries is a two-dimensional array of NodeIds . The first dimension
-
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network ModelIetfBaseNetworkInterfaceType . 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 defined
-
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network ModelSourceNode of this ReferenceType shall be an Object organized in the NetworkInterfaces folder. The TargetNode of this ReferenceType shall be an Object organized in the NetworkInterfaces folder. The HasLowerLayerInterface ReferenceType
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.2.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a software component. The TargetNode of References of this ReferenceType shall be an Object or ObjectType representing an execution environment
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.3.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a software component. The TargetNode of References of this ReferenceType shall be an Object or ObjectType representing an execution environment
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.4.2 Definitionrepresenting the controlling component, as for example a PLC or a software component. The TargetNode of References of this ReferenceType shall be an Object representing a component that is controlled ... TargetNode . Controls is formally defined in Table 3 . Table 3 - Controls Definition Attributes Value BrowseName Controls InverseName IsControlledBy Symmetric FALSE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of HierarchicalReferences defined
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.5.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a component that utilizes the TargetNode in order to work. The TargetNode of References of this ReferenceType shall be an Object
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.6.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a component that requires the TargetNode in order to work. The TargetNode of References of this ReferenceType shall be an Object
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.7.2 Definitionthis type shall be an Object or ObjectType representing a piece of hardware. The TargetNode of this ReferenceType shall be an Object representing a piece of hardware. IsPhysicallyConnectedTo is formally
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.8.2 Definitionworld. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode shall
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.9.2 Definitionhardware. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode shall
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.10.2 Definitionfunctionality. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode shall
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.11.2 DefinitionReferences of this ReferenceType shall be an Object or ObjectType representing some functionality. The TargetNode of References of this ReferenceType shall be an Object or ObjectType representing some hard
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.12.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a piece of hardware. The TargetNode of References of this ReferenceType shall be an Object representing a piece of hardware that
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.13.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a piece of hardware. The TargetNode of References of this ReferenceType shall be an Object representing a piece of hardware that
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.14.2 Definitionthis ReferenceType shall be an Object or ObjectType representing a piece of hardware. The TargetNode of References of this ReferenceType shall be an Object representing a piece of hardware that
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes5.1 Overviewsimple construct, where the only information of a Reference is the SourceNode , the TargetNode , the ReferenceType and for asymmetric ReferenceTypes the direction (forward or inverse). Sometimes, it is desirable ... Reference . Such a Variable can be referenced from the SourceNode and / or the TargetNode of such a Reference . Potentially, it can also be referenced by other Nodes to provide additional
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypesinstance of ReferenceDescriptionVariableType . Each entry in the array contains the ReferenceType , direction and TargetNode . The SourceNode of the first entry in the array is the SourceNode of the Value ... instance of ReferenceDescriptionVariableType . The SourceNode of all other entries is the TargetNode of the previous entry. The TargetNode of the last entry shall be the TargetNode of the instance
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes5.4.1 HasReferenceDescriptiondirectly participating in the Reference that is described in the ReferenceDescription (as SourceNode or TargetNode ), or from a Node somehow related to the Reference that is described ... path)). The SourceNode of References of this type can be of any NodeClass . The TargetNode of this ReferenceType shall be a Variable of VariableType ReferenceDescriptionVariableType or one of its subtypes
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization3.1.2 SerializationEntitySerializationEntity the TargetNode of the HasSerializationEntity ReferenceType. Note 1 to entry: The parent Object of the SerializedData Variable containing the SerializationValue and allows the configuration of the SerializationScope
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationSourceNode of this ReferenceType shall be an Object , ObjectType, Variable or VariableType. The TargetNode of this ReferenceType shall be an Object of SerializationEntityType or a subtype. The HasSerializationEntity is formally
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelshall be added with a SourceNode of the ConnectionEndpoint and the TargetNode of the ControlGroup . If the lock is assigned to the Client connection, the Controls Reference ... Object associated with the Client connection (see OPC 10000-100 ) and a TargetNode of the ControlGroup . The optional ReleaseControl Method calls the ExitLock Method on all established Locks and removes
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis ReferenceType shall be an instance of AssetConnectorType (or subtypes) or an Asset . The TargetNode of this ReferenceType shall be an instance of AssetConnectorType (or subtypes) or an Asset
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsubtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of AutomationComponentConfigurationType. The HasAutomationComponentConfiguration ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelmaintenance. The SourceNode of References of this type shall be an Asset . The TargetNode of this ReferenceType shall be an Asset . The HasBuiltInAsset ReferenceType is formally defined in Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent ReferenceType . The SourceNode of this ReferenceType shall be an instance of AutomationComponentConfigurationType . The TargetNode of this ReferenceType shall be an instance of AssetVerificationType . The HasAssetToVerify ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent ReferenceType . The SourceNode of this ReferenceType shall be an instance of AutomationComponentCapabilitiesType . The TargetNode of this ReferenceType shall be an instance of BaseDataVariableType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent ReferenceType . The SourceNode of this ReferenceType shall be an instance of AutomationComponentConfigurationType . The TargetNode of this ReferenceType shall be an instance of BaseDataVariableType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent ReferenceType . The SourceNode of this ReferenceType shall be an instance of ConnectionManagerCapabilitiesType . The TargetNode of this ReferenceType shall be an instance of BaseDataVariableType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsubtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of CommunicationFlowConfigurationType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsubtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of ConnectionConfigurationType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent ReferenceType . The SourceNode of this ReferenceType shall be an instance of ConnectionEndpointsFolderType . The TargetNode of this ReferenceType shall be an instance of ConnectionEndpointType . The HasConnectionEndpoint ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsubtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a FunctionalEntity . The TargetNode of this ReferenceType shall be an instance of ControlGroupType . The HasControlGroup ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelInputGroups . The SourceNode of this ReferenceType shall be an instance of InputsFolderType . The TargetNode of this ReferenceType shall be an instance of InputsFolderType . The HasInputGroup ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelOutputGroups . The SourceNode of this ReferenceType shall be an instance of OutputsFolderType . The TargetNode of this ReferenceType shall be an instance of OutputsFolderType . The HasOutputGroup ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model11.15 HasPart ReferenceTyperemoving the PC housing. The SourceNode of this ReferenceType shall be an Asset . The TargetNode of this ReferenceType shall be an Asset . The HasPart ReferenceType is formally defined in Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsubtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of ServerAddressType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis ReferenceType shall be an instance of FunctionalEntityType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of FunctionalEntityType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelIsPartOfRedundantAssetSet Reference example The SourceNode of this ReferenceType shall be an Asset . The TargetNode of this ReferenceType shall be an Asset . The IsPartOfRedundantAssetSet ReferenceType is formally defined in Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelNonHierarchicalReferences ReferenceType . The SourceNode of this ReferenceType shall be an instance of ServerAddressType . The TargetNode of this ReferenceType shall be an instance of AutomationComponentConfigurationType . The ToAutomationComponentConfiguration ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSourceNode of References of this type shall be an instance of AutomationComponentConfigurationType . The TargetNode of this ReferenceType shall be an instance of ConnectionEndpointConfigurationType . The ToConnectionEndpointConfiguration ReferenceType is formally defined
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis type shall be an instance of PubSubConnectionEndpointType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of DataSetReaderType (see OPC 10000-14 ). The ToDataSetReader
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis type shall be an instance of PubSubConnectionEndpointType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of DataSetWriterType (see OPC 10000-14 ). The ToDataSetWriter
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model11.23 ToFlow ReferenceTypethis ReferenceType shall be an instance of ConnectionEndpointConfigurationType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of CommunicationFlowConfigurationType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis ReferenceType shall be an instance of ConnectionEndpointConfigurationType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of SubscriberConfigurationType or a subtype
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelthis ReferenceType shall be an instance of ConnectionEndpointConfigurationType or a subtype of it. The TargetNode of this ReferenceType shall be an instance of PubSubCommunicationFlowConfigurationType or a subtype
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.1.1 Node definitionsvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... referenced Node , only applicable for Variables and Objects . Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel . NOTE Notes referencing footnotes of the table content. Components of Nodes
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesupdate client to find related components for compatibility checks (see 8.7.3 ). SourceNode and TargetNode of References of this type shall be objects that implement IVendorNameplateType . A server shall support browsing
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.6.2 CanUpdate ReferenceTypetarget of this ReferenceType is the component that can be updated. SourceNode and TargetNode of References of this type shall be objects that implement IVendorNameplateType . Table 119 - CanUpdate ReferenceType definition
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.5 Solution packagesPackageTarget 0:Structure TargetType 0:NodeId Install to all instances of that ObjectType . True TargetNode 0:NodeId Install to specific node on the server. True ProductInstanceUri 0:String Specific target ... targes that are subtypes of the specified ObjectType shall be updated. If a TargetNode is specified, only this node shall be updated. If a ProductInstanceUri is specified, only the target
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.1 Node definitionsvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... referenced Node , only applicable for Variables and Objects . Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel . NOTE Notes referencing footnotes of the table content. Components of Nodes
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics13.1.2 Contains ReferenceTypepart of a hierarchy referenced by the 0:Locations Object, directly or indirectly. The TargetNode of this ReferenceType shall be an Object contained in the location of the SourceNode . References
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics13.3.3.3 HierarchicalContains ReferenceTypepart of a hierarchy referenced by the HierarchicalLocations Object, directly or indirectly. The TargetNode of this ReferenceType shall be an Object contained in the location of the SourceNode . References
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics13.4.3.3 OperationalContains ReferenceTypepart of a hierarchy referenced by the OperationalLocations Object, directly or indirectly. The TargetNode of this ReferenceType shall be an Object contained in the location of the SourceNode . References
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.1 Node definitionsvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... referenced Node , only applicable for Variables and Objects . Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel . NOTE Notes referencing footnotes of the table content. Conformance Units Name
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automationvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... used. References NodeClass BrowseName DataType TypeDefinition Other ReferenceType name NodeClass of the TargetNode . BrowseName of the target Node . If the Reference is to be instantiated by the server, then
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation6.3.1 HasStatisticComponentObject or ObjectType implementing the IStatisticsType Interface , or one of its subtypes. The TargetNode of this ReferenceType shall be an Object or DataVariable . If an Object is referenced, the Object
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial AutomationNode using a reference measurement instrument, like for example instances of DynamicCalibrationTargetCategoryType. The TargetNode of this ReferenceType can be any Node representing a measurement instrument. The HasReferenceMeasurementInstrument is formally defined
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.1 Node definitionsvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... referenced Node , only applicable for Variables and Objects . Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel . NOTE Notes referencing footnotes of the table content. Components of Nodes
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.1 Node definitionsvalue. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined ... referenced Node , only applicable for Variables and Objects . Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel . NOTE Notes referencing footnotes of the table content. Conformance Units Name