Search

200 result(s) for References

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.2 Integrated AddressSpace model
  AddressSpace represents its contents as a set of Node s connected by References . Primitive characteristics of Node s are described by Attributes . Attributes are the only elements of a Server ... Node s in the AddressSpace are typically accessible via the hierarchy, they may have References to each other, allowing the AddressSpace to represent an interrelated network of Node
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.1 AddressSpace Nodes
  AddressSpace are used to represent real objects, their definitions and their References to each other
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.2 AddressSpace organization
  organize their Node s within the AddressSpace as they choose. The use of References between Node s permits Servers to organize the AddressSpace into hierarchies, a full mesh network ... Node s, or any possible mix. OPC 10000-5 defines OPC UA Nodes and References and their expected organization in the AddressSpace . Some Profiles will not require that
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.3 AddressSpace Views
  Servers may optionally define other Views . Views hide some of the Node s or References in the AddressSpace . Views are visible via the AddressSpace and Clients are able to browse
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.4 Support for information models
  models The OPC UA AddressSpace supports Information Models . This support is provided through: Node References that allow Objects in the AddressSpace to be related to each other. ObjectType Node
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.6 View Service Set
  browsing. Browsing allows Clients to navigate up and down the hierarchy, or to follow References between Node s contained in the View . In this manner, browsing also allows Clients
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.1 Conventions for AddressSpace figures
  Conventions for AddressSpace figures Nodes and their References to each other are illustrated using figures. Figure 1 illustrates the conventions used in these figures. Figure 1 - AddressSpace Node diagrams ... contains the BrowseName . Node rectangles may contain boxes used to define their Attributes and References . Specific names in these boxes identify specific Attributes and References . Shaded rectangles with rounded corners
• 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 ... mandatory the Attribute or Property shall exist for every Node of the NodeClass . For References it specifies the cardinality. The following values may apply: "0..*" identifies that there
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.1 General
  AddressSpace as a set of Nodes described by Attributes and interconnected by References . Figure 3 illustrates the model of a Node and the remainder of 4.3 discusses the details
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.2 NodeClasses
  NodeClasses NodeClasses are defined in terms of the Attributes and References that shall be instantiated (given values) when a Node is defined in the AddressSpace . Attributes are discussed ... References in 4.4.4 . Clause 5 defines the NodeClasses for the OPC UA AddressSpace . These NodeClasses are referred to collectively as the metadata for the AddressSpace . Each Node in the AddressSpace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  References References are used to relate Nodes to each other. They can be accessed using the browsing and querying Services defined in OPC 10000-4 . Like Attributes , they are defined ... fundamental components of Nodes . Unlike Attributes , References are defined as instances of ReferenceType Nodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.3 DataVariables
  also visible in the AddressSpace . In this case, this complex DataVariable could define HasComponent References from it to the individual temperature values that it is composed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.2 Complex TypeDefinitionNodes and their InstanceDeclarations
  Complex TypeDefinitionNodes and their InstanceDeclarations TypeDefinitionNodes can be complex. A complex TypeDefinitionNode also defines References to other Nodes as part of the type definition. The ModellingRules defined in 6.4.4 specify ... those Nodes are handled when creating an instance of the type definition. A TypeDefinitionNode references instances instead of other TypeDefinitionNodes to allow unique names for several instances of the same
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.3 Event Categorization
  devices, or Event areas of a plant or functionality contained in the Server . Event References would be used to indicate which Event sources represent physical devices and which ones represent ... some Server -based functionality. In addition, References can be used to group the physical devices or Server -based functionality into hierarchical Event areas. In some cases, an Event source
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.1 General
  Attributes of the Base NodeClass are specified in Table 7 . There are no References specified for the Base NodeClass . Table 7 - Base NodeClass Name Use Data Type Description Attributes NodeId ... RolePermissionType[] See 5.2.9 UserRolePermissions O RolePermissionType[] See 5.2.10 AccessRestrictions O AccessRestrictionType See 5.2.11 References No References specified for this NodeClass
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.1 General
  General References are defined as instances of ReferenceType Nodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass as specified in Table 9 . In contrast ... inherent part of a Node and no NodeClass is used to represent References . This standard defines a set of ReferenceTypes provided as an inherent part of the OPC UA Address
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  SourceNode . For example, the ReferenceType with the BrowseName "Contains" is used in References that specify that the SourceNode contains the TargetNode . The inherited DisplayName Attribute contains a translation ... from the SourceNode or the TargetNode . Therefore both directions are considered to be forward References. If the ReferenceType is non-symmetric the InverseName Attribute shall be set. The InverseName Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.1 General
  General HasSubtype References and HasProperty References are the only ReferenceTypes that may be used with ReferenceType Nodes as SourceNode . ReferenceType Nodes shall not be the SourceNode of other types ... References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.2 HasProperty References
  HasProperty References HasProperty References are used to identify the Properties of a ReferenceType and shall only refer to Nodes of the Variable NodeClass . The Property NodeVersion is used to indicate
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.3 HasSubtype References
  HasSubtype References HasSubtype References are 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 ... true for its subtypes. A ReferenceType shall have exactly one supertype, except for the References ReferenceType defined in 7.2 as the root type of the ReferenceType hierarchy. The ReferenceType hierarchy
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  default View . Each Node in a View may contain only a subset of its References , as defined by the creator of the View . The View Node acts as the root ... ContainsNoLoops M Boolean If set to TRUE this Attribute indicates that by following the References in the context of the View there are no loops, i.e. starting from a Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Events or the read / write historic Events . The EventNotifierType is defined in 8.59 . References HasComponent 0..* HasComponent References identify the DataVariables , the Methods and Objects contained in the Object . HasProperty ... HasProperty References identify the Properties of the Object . HasModellingRule 0..1 Objects can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  FALSE it is not an abstract ObjectType , i.e. Objects of this type can exist. References HasComponent 0..* HasComponent References identify the DataVariables , the Methods , and Objects contained in the ObjectType ... Object of this type is instantiated, is specified in 6.4 . HasProperty 0..* HasProperty References identify the Properties of the ObjectType . If and how the Properties are instantiated when an Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.3 Standard ObjectType FolderType
  Object of the ObjectType FolderType ; the TargetNode can be of any NodeClass . Organizes References can be used in any combination with HasChild References ( HasComponent , HasProperty
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.4 Client-side creation of Objects of an ObjectType
  ModellingRules specified for the components. However, the Server may add additional components and References to the Object and its components that are not defined by the ObjectType . This behaviour
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  this Attribute is not provided the information provided by these additional Fields is unknown. References HasModellingRule 0..1 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 of a DataVariable . Properties are not allowed to be the SourceNode of HasProperty
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  using the Variable NodeClass , specified in Table 13 . DataVariables identify their Properties using HasProperty References . Complex DataVariables use HasComponent References to expose their component DataVariables . The Property NodeVersion indicates ... suited for human users and for automated systems. DataVariables may use additional References to define relationships to other Nodes . No restrictions are placed on the types of References used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  FALSE it is not an abstract VariableType , i.e. Variables of this type can exist. References HasProperty 0..* HasProperty References are used to identify the Properties of the VariableType . The referenced ... instances of this type, depending on the ModellingRules defined in 6.4.4 . HasComponent 0..* HasComponent References are used for complex VariableTypes to identify their containing DataVariables . Complex VariableTypes can only
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.6 Client-side creation of Variables of an VariableType
  ModellingRules specified for the components. However, the Server may add additional components and References to the Variable and its components that are not defined by the VariableType . This behaviour
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  executable taking user access rights into account (FALSE means not executable, TRUE means executable). References HasProperty 0..* HasProperty References identify the Properties for the Method . HasModellingRule 0..1 Methods ... Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). GeneratesEvent 0..* GeneratesEvent References identify the type of Events that may be generated whenever the Method is called. AlwaysGeneratesEvent
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  EnumDefinition . The EnumDefinition DataType is defined in 8.49 . It is a subtype of DataTypeDefinition . References HasProperty 0..* HasProperty References identify the Properties for the DataType . HasSubtype 0..* HasSubtype References ... hierarchy. The inverse Reference identifies the parent type of this type. HasEncoding 0..* HasEncoding References identify the encodings of the DataType represented as Objects of type DataTypeEncodingType . Only concrete Structured
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.4 DataTypeEncoding and Encoding Information
  DataType Node is exposed in the AddressSpace , it shall provide its DataTypeEncodings using HasEncoding References . These References shall be bi-directional. Figure 19 provides an example how DataTypes are modelled
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.3 Usage of DataTypeRefinements
  model, by using the non-hierarchical Reference UsesDataTypeRefinement (see 7.24 ) or a subtype. Those References always starts from an instance of a Variable , where the Structured DataType is used. They
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  subtyping rules, etc. A SubtypeRestriction Object should have at least two AllowedSubtype References to Variables defining different variations of subtypes. Otherwise, a Variable using the SubtypeRestriction should just ... Number and therefore can be used by any Variable using the Number DataType . It references two Variables , Y:UInt32 with the DataType UInt32 , the ValueRank Scalar which does not allow
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.3 InstanceDeclarationHierarchy
  InstanceDeclarations that are directly or indirectly referenced from the TypeDefinitionNode using forward hierarchical References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.6 BrowseName within a TypeDefinitionNode
  within a TypeDefinitionNode A BrowsePath within a TypeDefinitionNode which include targets of forward hierarchical References shall have a BrowseName that is unique within the TypeDefinitionNode, this same restriction applies ... targets of forward hierarchical References from any InstanceDeclaration . This means that any InstanceDeclaration within the InstanceDeclarationHierarchy can be uniquely identified by a sequence of BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.1 Overview
  overridden they are not referenced by the subtype. InstanceDeclarations can be overridden by adding References , changing References to reference different Nodes , changing References to be subtypes of the original ReferenceType ... collected from all types that can be found by recursively following the inverse HasSubtype References from the subtype. This collection of InstanceDeclarations is called the fully-inherited InstanceDeclarationHierarchy
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.2 Fully-inherited InstanceDeclarationHierarchy
  table of Nodes identified by their BrowsePaths with a corresponding table of References . The InstanceDeclarationHierarchy for "BetaType" is described in Table 19 where the top half ... table is the table of Nodes and the bottom half is the table of References (the HasModellingRule references have been omitted from the table for the sake of clarity
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  specified in the supertype. When overriding an InstanceDeclaration it is necessary to provide hierarchical References that link the new Node back to the subtype (the References are used to determine ... subtype of the ReferenceType used in the parent type. Any NonHierarchical References specified for the overridden InstanceDeclaration are treated as new References unless the ReferenceType only allows a single Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  after being created. Special rules apply for some Attributes as defined in 6.2.7 . Additional References may be added to the Nodes , and References may be deleted as long ... InstanceDeclarations of the fully-inherited InstanceDeclarationHierarchy have been connected directly with several References , all those References shall connect the same Nodes . An example is given in Figure 28 . The instances
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.1 General
  ModellingRules defined in this standard do not define how to deal with NonHierarchical References between InstanceDeclarations , i.e. it is Server -specific if those References exist in an instance hierarchy ... Other ModellingRules may define behaviour for NonHierarchical References between InstanceDeclaration as well. ModellingRules are represented in the AddressSpace as Objects of the ObjectType ModellingRuleType . There are some Properties defining common
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.3 ExposesItsArray
  subtype of it. If there are more than one forward hierarchical References between A and B, then all instances based on B shall be referenced with all those References . Figure ... instance of Type_A having two entries in its value array. Therefore it references two instances of the same type as the InstanceDeclaration ArrayExpose. The BrowseNames of those instances
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  complex TypeDefinition expects from instances of the TypeDefinition to add instances with specific References without defining BrowseNames for the instances. For example, a Device might have a Folder for DeviceParameters ... provides useful information when exposing a TypeDefinition . When the InstanceDeclaration is complex, i.e. it references other InstanceDeclarations with hierarchical References , these InstanceDeclarations are not further considered for instantiating the TypeDefinition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.5 MandatoryPlaceholder
  TranslateBrowsePathsToNodeIds Service (see OPC 10000-4 ). When the InstanceDeclaration is complex, i.e. it references other InstanceDeclarations with hierarchical References , these InstanceDeclarations are not further considered for instantiating the TypeDefinition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.3 HierarchicalReferences ReferenceType
  shall be a non-symmetric Reference . The semantic of HierarchicalReferences is to denote that References of HierarchicalReferences span a hierarchy. It means that it may be useful to present Nodes ... related with References of this type in a hierarchical-like way. HierarchicalReferences does not forbid loops. For example, starting from Node "A" and following HierarchicalReferences
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.5 HasChild ReferenceType
  used. It is a subtype of HierarchicalReferences . The semantic is to indicate that References of this type span a non-looping hierarchy. Starting from Node "A" and only ... following References of the subtypes of the HasChild ReferenceType it shall never be possible to return to "A". But it is allowed that following the References there
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.9 HasOrderedComponent ReferenceType
  semantic of the HasComponent ReferenceType - is that when browsing from a Node and following References of this type or its subtype all References are returned in the Browse Service defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.10 HasSubtype ReferenceType
  other subtype hierarchies are specified in Clause 6 . The SourceNode of References of this type shall be an ObjectType , a VariableType , a DataType or a ReferenceType and the TargetNode shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.11 Organizes ReferenceType
  span multiple hierarchies independent of any hierarchy created with the non-looping Aggregates References . The SourceNode of References of this type shall be an Object , ObjectType or a View
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.14 HasEncoding ReferenceType
  reference DataTypeEncodings of a subtype of the Structure DataType . The SourceNode of References of this type shall be a subtype of the Structure DataType . The TargetNode of this ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.15 GeneratesEvent
  VariableTypes may generate and Methods may generate on each Method call. The SourceNode of References of this type shall be an ObjectType , a VariableType or a Method InstanceDeclaration . The TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.16 AlwaysGeneratesEvent
  types of Events Methods have to generate on each Method call. The SourceNode of References of this type shall be a Method InstanceDeclaration . The TargetNode of this ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.17 HasEventSource
  capable of supplying all Events from a Server and as such has implied HasEventSource References to every event source in a Server . The SourceNode of this ReferenceType shall ... subscription to the reference source. Starting from Node "A" and only following References of the HasEventSource ReferenceType or of its subtypes it shall never be possible to return
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.18 HasNotifier
  SourceNode of the 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 ... Event Reference Example A second example of a more complex organization of Event References is represented in Figure 40 . In this example, explicit References are included from the Server
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.23 AssociatedWith ReferenceType
  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 Model
  7.24 UsesDataTypeRefinement
  restricting the usage of the Structured DataType and adding meta data. The SourceNode of References of this type shall be a Variable having a Structured DataType . The Variable shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.25 HasFieldDescription
  additional metadata, that may potentially restrict the usage of the field. The SourceNode of References of this type shall be an Object of DataTypeRefinementType or a subtype. The TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.28 UsesSubtypeRestriction
  SubtypeRestrictionType , restricting the usage of subtypes on values of the Variable . The SourceNode of References of this type shall be a Variable . The Variable shall not be used as InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.29 AllowedSubtype
  from a SubtypeRestriction Object to a Variable defining one allowed subtype. The SourceNode of References of this type shall be an Object of SubtypeRestrictionType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.30 HasDataTypeRefinement
  Object that defines the allowed refinements of instances of a DataType . The SourceNode of References of this type shall be a DataType . The TargetNode of this ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.1 General
  relationship of a Variable or VariableType to its DataType is not modelled using References , changes to the DataType Attribute of a Variable or VariableType are also considered as model changes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  Attributes are shown (e.g. the NodeId of HasComponent ). Figure B.3 - Notation (II) OPC References are represented as UML associations marked with the stereotype <<Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.1 General
  structural data of OPC UA. Nodes , their Attributes including their current value and References between the Nodes including the ReferenceType can be exposed. The graphical notation provides no mechanism
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.2 Simple notation
  DisplayName of the View . The font shall not be set to italic. References are represented as lines between Nodes as exemplified in Figure C.1 . Those lines can vary in their ... Example of a Reference connecting two Nodes Table C.2 defines how symmetric and asymmetric References are represented in general, and also defines shortcuts for some ReferenceTypes . Although it is recommended
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  Node2" the shortcut in both notation variants. A figure can contain HasTypeDefinition References for some Nodes and the shortcut for other Nodes . It is not allowed that a Node ... permitted. Table C.3 defines how cardinality of Components with modelling rule are indicated on References. Table C.3 - Extended Notation of Reference Cardinality Representation Cardinality Modelling Rule Example Not Specified
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.1 Overview
  Overview This Service Set defines Services to add and delete AddressSpace Nodes and References between them. All added Nodes continue to exist in the AddressSpace even if the Client that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.1 Description
  Description This Service is used to add one or more References to one or more Nodes . The NodeClass is an input parameter that is used to validate that the Reference ... 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
  response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the References to add (see 7.38 for StatusCode definition). The size and order of the list matches ... referencesToAdd request parameter. diagnosticInfos [] Diagnostic Info List of diagnostic information for the References to add (see 7.12 for DiagnosticInfo definition). The size and order of the list matches the size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.1 Description
  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 and References like child
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.2 Parameters
  Node to delete. deleteTargetReferences Boolean A Boolean parameter with the following values: TRUE delete References in TargetNodes that Reference the Node to delete. FALSE delete only the References for which ... source. The Server cannot guarantee that it is able to delete all References from TargetNodes if this parameter is TRUE. Response responseHeader Response Header Common response parameters
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.5.1 Description
  Description This Service is used to delete one or more References of a Node . When any of the References deleted by an invocation of this Service are contained ... RequestHeader Common request parameters (see 7.32 for RequestHeader definition). referencesToDelete [] DeleteReferences Item List of References to delete. This structure is defined in-line with the following indented items. sourceNodeId NodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.1 Description
  Description This Service is used to discover the References of a specified Node. The browse can be further limited by the use of a View . This Browse Service also supports
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  ViewDescription value indicates the entire AddressSpace . Use of the empty ViewDescription value causes all References of the nodesToBrowse to be returned. Use of any other View causes only the References ... that View to be returned. requestedMax ReferencesPerNode Counter Indicates the maximum number of references to return for each starting Node specified in the request. The value 0 indicates that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.5 BrowseDirection
  BrowseDirection The BrowseDirection is an enumeration that specifies the direction of References to follow. The possible values are described in Table 112 . Table 112 - BrowseDirection values Name Value Description FORWARD ... Select only forward References . INVERSE 1 Select only inverse References . BOTH 2 Select forward and inverse References . INVALID 3 No value specified
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.6 BrowseResult
  status for the BrowseDescription. This value is set to Good if there are still references to return for the BrowseDescription . continuationPoint ContinuationPoint A Server defined opaque value that identifies ... continuation point. The ContinuationPoint type is defined in 7.9 . References [] ReferenceDescription The set of references that meet the criteria specified in the BrowseDescription . Empty, if no References met the criteria
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.2 ElementOperand
  existent element. Clients shall construct filters in this way to avoid circular and invalid References . Servers should protect against invalid indexes by verifying the index prior to using it. Table
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.30 RelativePath
  Table 169 . Table 169 - RelativePath Name Type Description RelativePath structure Defines a sequence of References and BrowseNames to follow. elements [] RelativePath Element A sequence of References and BrowseNames to follow ... available on the Node instance. If the referenceTypeId is null then all References are included and the parameter includeSubtypes is ignored. This is equal to use the base References ReferenceType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  A.2 BNF of RelativePath
  RelativePath A RelativePath is a structure that describes a sequence of References and Nodes to follow. This annex describes a text format for a RelativePath that can be used ... symbols specifies the BrowseName of a ReferenceType to follow. By default, any References of the subtypes the ReferenceType are followed as well. A '#' placed in front of the BrowseName indicates
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  When querying for 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 ... desired than the root ReferenceType is listed. These References are returned as part of the QueryDataSets . Query Services allow a special handling of the targetName field in the RelativePath
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  Figure B.3 . In this Figure, the OPC UA notation is used for all References to ObjectTypes , Variables , Properties and subtypes. Additionally, supported References are contained in an inner ... actual references only exist in the instances, thus, no connections to other Objects are shown in the Figure and they are subtypes of the listed Reference . A corresponding example
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.9 Example 6
  case of Reference types on the browse name is provided. For the References listed in Table B.27 , the value would be a ReferenceDescription which are described in 7.29 . Table B.28
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.10 Example 7
  based on a starting point that was obtained via browsing. This request includes listing References as something that is to be returned. In this case the Person Browsed to Area2 ... case of Reference types on the browse name is provided. For the References listed in Table B.31 , the value would be a ReferenceDescription which are described
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  providing the Attribute name and a value, or a description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass ... Nodes related to the ConformanceUnit in its AddressSpace . If two Nodes are exposed, all References between the Nodes defined in this specification shall be exposed as well. The relations between
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.2 BaseObjectType
  from it. However, it might not be possible for Servers to provide all HasSubtype References from this ObjectType to its subtypes, and therefore it is not required to provide this ... information. There are no References specified for this ObjectType . It is formally defined in Table 8 . Table 8 - BaseObjectType definition Attribute Value BrowseName BaseObjectType IsAbstract False References NodeClass BrowseName DataType
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.1 ServerType
  defined in Table 9 . Table 9 - ServerType definition Attribute Value BrowseName ServerType IsAbstract False References NodeClass BrowseName DataType / TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in 6.2 HasProperty Variable ... server names . They are used in OPC UA Services to identify TargetNodes of References that reside in remote Servers . Clients may read the entire table or they may read individual
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  StaticNumericNodeIdRange and StaticStringNodeIdPattern Properties . Table 22 - NamespaceMetadataType definition Attribute Value BrowseName NamespaceMetadataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in 6.2 HasProperty Variable ... string NodeIds then this Property is ignored. The Object NamespaceFile contains all Nodes and References of the namespace in an XML file where the Information Model XML Schema is defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.7 DataTypeEncodingType
  This ObjectType is used as type for the DataTypeEncodings . There are no References specified for this ObjectType . It is formally defined in Table 64 . Table 64 - DataTypeEncodingType definition Attribute Value ... BrowseName DataTypeEncodingType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined in 6.2 . Conformance Units Base Info Base Types
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.9 BaseInterfaceType
  super-type for Interfaces . All subtypes of BaseInterfaceType shall be abstract. There are no References specified for this ObjectType . It is formally defined in Table 66 . Table 66 - BaseInterfaceType definition ... Attribute Value BrowseName BaseInterfaceType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined in 6.2 . Conformance Units Address Space Interfaces
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.10 OrderedListType
  defined in Table 67 . Table 67 - OrderedListType Definition Attribute Value BrowseName OrderedListType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType defined in 6.2 i.e. inheriting ... Objects managed by Instances of the OrderedListType . The order is provided by the HasOrderedComponent References to the Objects . As not all Clients consider the order returned by the Browse Service
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.11 IOrderedObjectType Definition
  defined in Table 69 . Table 69 - IOrderedObjectType Definition Attribute Value BrowseName IOrderedObjectType IsAbstract True References Node Class BrowseName DataType TypeDefinition Other Subtype of the BaseInterfaceType defined in 6.9 , i.e. inheriting ... this Property . The order shall be identical to the order managed by the HasOrderedComponent References . Note that due to the nature of a list element, the NumberInList Property is bound
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.2 BaseVariableType
  only the PropertyType and the BaseDataVariableType directly inherit from this type. There are no References specified for this VariableType . It is formally defined in Table 72 . Table 72 - BaseVariableType definition ... Attribute Value BrowseName BaseVariableType IsAbstract True ValueRank -2 (-2 = Any) DataType BaseDataType References NodeClass BrowseName DataType TypeDefinition ModellingRule Conformance Units Base Info Base Types
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.3 PropertyType
  specialised type definition. It is not allowed to subtype this VariableType . There are no References specified for this VariableType . It is formally defined in Table 73 . Table 73 - PropertyType definition ... Attribute Value BrowseName PropertyType IsAbstract False ValueRank -2 (-2 = Any) DataType BaseDataType References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseVariableType defined in 7.2 . Conformance Units Base Info Base
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.4 BaseDataVariableType
  VariableTypes of DataVariables shall either directly or indirectly inherit from it. There are no References specified for this VariableType . It is formally defined in Table 74 . Table 74 - BaseDataVariableType definition ... Attribute Value BrowseName BaseDataVariableType IsAbstract False ValueRank -2 (-2 = Any) DataType BaseDataType References NodeClass BrowseName Comment Subtype of the BaseVariableType defined in 7.2 . Conformance Units Base Info Base Types
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.1 General
  Variables described in the following subclauses can be extended by additional Properties or References to other Nodes , except where it is stated in the text that it is restricted
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.1 Overview
  structure of the AddressSpace . All Objects in this figure are organised using Organizes References and have the ObjectType FolderType as type definition. Figure 1 - Standard AddressSpace structure The remainder
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.2 Root
  browse entry point for the AddressSpace . It contains a set of Organizes References that point to the other standard Objects . The " Root " Object shall not reference any other ... formally defined in Table 100 . Table 100 - Root definition Attribute Value BrowseName Root References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes Object Views Defined in 8.2.3 Organizes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 Views
  Views This standard Object is the browse entry point for Views . Only Organizes References are used to relate View Nodes to the " Views " standard Object . All View Nodes ... indirectly. That is, the " Views " Object may reference other Objects using Organizes References. Those Objects may reference additional Views . Figure 2 illustrates the Views organization. The " Views
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.4 Objects
  point for Object Nodes . Figure 3 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects to the " Objects " standard Object . A View Node ... thus the " Objects " Object can also reference View Nodes using Organizes References . The intent of the " Objects " Object is that all Objects and Variables that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.5 Types
  point for type Nodes . Figure 1 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects to the " Types " standard Object . The " Types ... formally defined in Table 103 . Table 103 - Types definition Attribute Value BrowseName Types References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes Object ObjectTypes Defined in 8.2.6 Organizes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.6 ObjectTypes
  this Node showing some of the standard ObjectTypes defined in Clause 6 . Only Organizes References are used to relate Objects and ObjectTypes to the " ObjectTypes " standard Object ... industry, such as the ServerType defined in 6.3.1 . This Object also indirectly references the BaseEventType defined in 6.4.2 , which is the base type of all EventTypes . Thereby
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.7 VariableTypes
  point for VariableType Nodes . Figure 5 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects and VariableTypes to the " VariableTypes " standard Object ... formally defined in Table 105 . Table 105 - VariableTypes definition Attribute Value BrowseName VariableTypes References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes VariableType BaseVariableType Defined in 7.2 Conformance
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.8 ReferenceTypes
  browse entry point for ReferenceType Nodes . Figure 6 illustrates the organization of ReferenceTypes . Organizes References are used to define ReferenceTypes and Objects referenced by the " ReferenceTypes " Object ... queries, the Server shall provide all its ReferenceTypes , directly or indirectly following hierarchical References starting from the " ReferenceTypes " Object . This means that, whenever the client follows a Reference
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.9 DataTypes
  wishes to expose in the AddressSpace . DataType Nodes should be made available using Organizes References pointing either directly from the "DataTypes" Object to the DataType Nodes or using ... that all DataTypes of the Server exposed in the AddressSpace are accessible following hierarchical References starting from the "DataTypes" Object . However, this is not required. The " DataTypes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.10 EventTypes
  this Node showing some of the standard EventTypes defined in Clause 6 . Only Organizes References are used to relate Objects and ObjectTypes to the " EventTypes " standard Object ... formally defined in Table 108 . Table 108 - EventTypes definition Attribute Value BrowseName EventTypes References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes ObjectType BaseEventType Defined in 6.4.2 Conformance
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.11 InterfaceTypes
  this Node showing some of the standard ObjectTypes defined in clause 6. Only Organizes References are used to relate Objects and Interfaces to the " InterfaceTypes " standard Object ... formally defined in Table 109 . Table 109 - InterfaceTypes definition Attribute Value BrowseName InterfaceTypes References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes ObjectType BaseInterfaceType Defined in 6.9 Conformance
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.12 Locations
  different types of locations. Figure 9 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects . Figure 9 - Locations organization The intent of the " Locations ... formally defined in Table 110 . Table 110 - Locations definition Attribute Value BrowseName Locations References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined in 6.6 Conformance Units Base Info Locations Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.2 HierarchicalReferences
  Table 123 - HierarchicalReferences ReferenceType Attributes Value BrowseName HierarchicalReferences InverseName InverseHierarchicalReferences Symmetric False IsAbstract True References NodeClass BrowseName Comment Subtype of the References ReferenceType defined in 11.1 . Conformance Units Base Info
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.3 NonHierarchicalReferences
  Table 124 - NonHierarchicalReferences ReferenceType Attributes Value BrowseName NonHierarchicalReferences InverseName -- Symmetric True IsAbstract True References NodeClass BrowseName Comment Subtype of the References ReferenceType defined in 11.1 . Conformance Units Base Info Base
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.25 HasKeyValueDescription
  this ReferenceType shall be a Variable representing a supported configuration property. The SourceNode of References of this type shall be a Variable with the DataType KeyValuePair . The representation ... Table 146 - HasKeyValueDescription ReferenceType Attributes Value BrowseName HasKeyValueDescription InverseName KeyValueDescriptionOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in 11.3 . Conformance Units Base Info HasKeyValueDescription
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.6 Complex Variables having an array
  entries should also be used for other purposes in the AddressSpace, such as having References or additional Properties or exposing their complex structure using DataVariables, it is useful to expose
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  root of the document. It defines a set of Nodes , their Attributes and References . References to Nodes outside of the document are allowed. The structure of a UANodeSet is shown ... instance of the NamespaceMetadataType ObjectType . See OPC 10000-5 for more information. Following the references in the RequiredModels field shall not result in circular dependencies. The XML schema file associated
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  base type for all Nodes . It defines the base set of Attributes and the References . There are subtypes for each NodeClass defined in OPC 10000-4 . Each of these subtypes ... 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
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.12 DataTypeDefinition
  inherited from a base DataType . When Applications ingest a UANodeSet they follow the HasSubtype References between DataType Nodes to collect all of the fields needed to fill in the DataTypeDefinition
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.16 UANodeSetChanges
  UANodeSet or a UANodeSetChanges element at the root. It provides a list of Nodes / References to add and/or a list Nodes / References to delete. The UANodeSetChangesStatus structure defined in F.22 ... Nodes to add to the AddressSpace . ReferencesToAdd ReferencesToChange A list of new References to add to the AddressSpace. NodesToDelete NodesToDelete A list of Nodes to delete from the AddressSpace . ReferencesToDelete
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.17 NodesToAdd
  UAObjectType UAVariableType UADataType UAReferenceType The Nodes to add to the AddressSpace . When adding Nodes , References can be specified as part of the Node definition or as a separate ReferencesToAdd . Note ... that References to Nodes that could exist are always allowed. In other words, a Node is never rejected simply because it has a reference to an unknown Node . Reverse References
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.18 ReferencesToChange
  F.18 ReferencesToChange The ReferencesToChange type specifies a list of References to add to or remove from an AddressSpace . The elements of the type are defined in Table F.17 . Table F.17
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.19 ReferenceToChange
  forward reference. Target NodeId The identifier for the target Node of the Reference . References to Nodes that could exist are always allowed. In other words, a Reference is never rejected ... Reference must exist in the AddressSpace or in UANodeSetChanges document being processed. Reverse References are added when deemed practical by the processor
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.21 NodeToDelete
  Node NodeId The identifier for the Node to delete. DeleteReverseReferences Boolean If TRUE, then References to the Node are deleted as well
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.2.2 BaseAnalogType
  BaseAnalogType definition Attribute Value BrowseName BaseAnalogType IsAbstract False ValueRank -2 (-2 = 'Any') DataType Number References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the DataItemType defined in 5.3.1 ; i.e. the Properties ... value (e.g., DEGC, hertz, seconds). The EUInformation type is specified in 5.6.4 . The NonHierarchical References HasQuantity (see 6.5.2 ) and HasEngineeringUnitDetail (see 6.5.1 ) can be used to expose further information
• 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 ... unit instance can have zero, one or more such references. Instances of SyntaxReferenceEntryType have a well-defined NodeId as defined in Table 39 . Table 39 - Definition of NodeId for instances
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.1 QuantityType ObjectType definition
  defined in Table 41 . Table 41 - QuantityType definition Attribute Value BrowseName QuantityType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType defined in OPC 10000-5 HasProperty ... physical quantity. The ServerUnits are of ServerUnitType which is described in 6.4.2 . Syntax References : Instances of the QuantityType can identify the physical quantity in a specific external reference work using
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.2.2 UnitType ObjectType Definition
  defined in Table 43 . Table 43 - UnitType definition Attribute Value BrowseName UnitType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType defined in OPC 10000-5 HasProperty ... units GAUSS Gaussian System of units FPS foot-pound-second system of units Syntax References : Instances of the UnitType can identify the unit in a specific external reference work using
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.5.1 HasEngineeringUnitDetails
  more detailed AddressSpace representation Instance of the ServerUnitType ObjectType . The SourceNode of References of this type shall be a Variable with EUInformation DataType . The TargetNode of this ReferenceType shall ... Table 49 - HasEngineeringUnitDetails definition Attributes Value BrowseName HasEngineeringUnitDetails InverseName EngineeringUnitDetailsOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in OPC 10000-5 . Conformance Units Data Access
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.5.2 HasQuantity
  Variable with EUInformation DataType to an Instance of the QuantityType ObjectType . The SourceNode of References of this type shall be a Variable with EUInformation DataType (typically the EngineeringUnits Property ... Table 50 - HasQuantity definition Attributes Value BrowseName HasQuantity InverseName QuantityOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in OPC 10000-5 . Conformance Units Data Access
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.2 Branch
  also clause A.3.1.5 . An OPC UA Folder representing a DA Branch uses the Organizes References to reference child DA Branches and uses HasComponent References for DA Leafs (Items
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.1 General
  machines in a similar fashion to the StateMachineType defined in 10000-16 . The TwoStateVariableType References will only exist when sub states are available. For example, if a TwoStateVariableType machine
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.2 HasTrueSubState ReferenceType
  Condition is a sub state of the same super state (i.e. several HasTrueSubState References exist for the same super state) they are all treated as independent sub states. The representation ... Table 3 - HasTrueSubState ReferenceType Attributes Value BrowseName HasTrueSubState InverseName IsTrueSubStateOf Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Basic
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.3 HasFalseSubState ReferenceType
  Condition is a sub state of the same super state (i.e. several HasFalseSubState References exist for the same super state) they are all treated as independent sub states. The representation ... Table 4 - HasFalseSubState ReferenceType Attributes Value BrowseName HasFalseSubState InverseName IsFalseSubStateOf Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Basic
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.24.3 SystemOffNormalAlarmType
  defined in Table 107 . Table 107 - SystemOffNormalAlarmType definition Attribute Value BrowseName SystemOffNormalAlarmType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule HasSubtype ObjectType CertificateExpirationAlarmType Defined in Clause 5.8.24.7 Subtype ... OffNormalAlarmType , i.e. it has HasProperty References to the same Nodes . ConformanceUnits A & C SystemOffNormal
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.11.2 RefreshStartEventType
  defined in Table 133 . Table 133 - RefreshStartEventType definition Attribute Value BrowseName RefreshStartEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the SystemEventType defined ... HasProperty References to the same Nodes . ConformanceUnits A & C Refresh A & C Refresh2
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.11.3 RefreshEndEventType
  defined in Table 134 . Table 134 - RefreshEndEventType definition Attribute Value BrowseName RefreshEndEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the SystemEventType defined ... HasProperty References to the same Nodes . ConformanceUnits A & C Refresh A & C Refresh2
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.11.4 RefreshRequiredEventType
  defined in Table 135 . Table 135 - RefreshRequiredEventType definition Attribute Value BrowseName RefreshRequiredEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the SystemEventType defined ... HasProperty References to the same Nodes . ConformanceUnits A & C Refresh A & C Refresh2 When a Server detects an Event queue overflow, it shall track if any Condition Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.12 HasCondition Reference type
  Various examples for the use of this ReferenceType can be found in B.2 . HasCondition References can be used in the Type definition of an Object or a Variable . In this ... Condition instance declaration or a ConditionType . The following rules for instantiation apply: All HasCondition References used in a Type shall exist in instances of these Types as well
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.2 EventNotifier and source hierarchy
  EventNotifier and source hierarchy HasNotifier and HasEventSource References are used to expose the hierarchical organization of Event notifying Objects and ConditionSources . An Event notifying Object represents typically an area
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.3 Adding Conditions to the hierarchy
  ConditionType . Clients can locate Conditions by first browsing for ConditionSources following HasEventSource References (including sub-types like the HasNotifier Reference ) and then browsing for HasCondition References from all target Nodes ... discovered References . Figure 27 shows the application of the HasCondition Reference in a HasNotifier hierarchy. The Variable LevelMeasurement and the Object "Device B" Reference Condition instances. The Object
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.4 Conditions in InstanceDeclarations
  Reference and the HasEventSource Reference in an InstanceDeclaration . They are used to indicate what References and Conditions are available on the instance of the ObjectType . The use of the HasEventSource
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  8.1 Overview
  Alarms might be directly Referenced by an Object or they might have no direct References from the Object to the Alarm . Alarms might also be related to Objects that
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.2 AddressSpace examples
  examples This Clause provides additional examples for the use of HasNotifier , HasEventSource and HasCondition References to expose the organization of areas and sources with their associated Conditions . This hierarchy ... additional to a hierarchy 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
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  F.2 SystemStateStateMachineType
  Figure F.2 - SystemStateStateMachineType Model Table F.1 - SystemStateStateMachineType definition Attribute Value BrowseName SystemStateStateMachineType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the F initeStateMachineType defined ... Maintenance . It supports 12 possible Transitions and 7 possible Methods . Table F.2 - SystemStateStateMachineType additional references SourceBrowsePath References IsForward TargetBrowsePath ShutdownToOperating FromState True Shutdown ToState True Operating HasCause True QuickStart OperatingToShutdown
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.3.1 Overview
  Overview The ProgramStateMachineType components consist of a set of References to the Object instances of StateTypes , TransitionTypes , EventTypes and the Methods that collectively define the Program FiniteStateMachine. Figure 5 - Program ... References Figure 5 illustrates the component References that define the associations between two of the ProgramStateMachineType's states, Ready and Running. The complementary ReferenceTypes have been omitted to simplify
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.3.3 ProgramStateMachineType transitions
  which also includes the definitions of the ToState, FromState, HasCause, and HasEffect references used. Table 7 specifies the transitions defined for the ProgramStateMachineType. Each transition is assigned a unique TransitionNumber ... defined in Table 6 . Table 7 - ProgramStateMachineType Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath HaltedToReady ToState True Ready FromState True Halted HasCause True Reset HasEffect True ProgramTransitionEventType HasEffect True
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.4.1 Overview
  Overview The ProgramStateMachineType includes references to the Causes of specific Program state transitions. These causes refer to Method instances . Programs that do not support a Program Control Method will omit ... Causes reference to that Method from the ProgramStateMachineType references. If a Method's Causes reference is omitted from the ProgramStateMachineType then a Client cannot cause the associated state transition
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.2 ProgramTransitionEventType
  that are specified for ProgramStateMachineTypes . Table 9 - ProgramTransitionEventType Attribute Value BrowseName ProgramTransitionEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the base TransitionEventType defined ... ObjectType for the IntermediateResult specifies the collection of Variables using a set of HasComponent References
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.2 AuditHistoryEventUpdateEventType
  defined in Table 16 . Table 16 - AuditHistoryEventUpdateEventType definition Attribute Value BrowseName AuditHistoryEventUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType defined ... HasProperty References to the same Nodes . HasProperty Variable UpdatedNode NodeId PropertyType Mandatory HasProperty Variable PerformInsertReplace PerformUpdateType PropertyType Mandatory HasProperty Variable Filter EventFilter PropertyType Mandatory HasProperty Variable NewValues HistoryEventFieldList [ ] PropertyType Mandatory
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.3 AuditHistoryValueUpdateEventType
  defined in Table 17 . Table 17 - AuditHistoryValueUpdateEventType definition Attribute Value BrowseName AuditHistoryValueUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType defined ... HasProperty References to the same Nodes . HasProperty Variable UpdatedNode NodeId PropertyType Mandatory HasProperty Variable PerformInsertReplace PerformUpdateType PropertyType Mandatory HasProperty Variable NewValues DataValue[] PropertyType Mandatory HasProperty Variable OldValues DataValue[] PropertyType Mandatory
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.4 AuditHistoryAnnotationUpdateEventType
  defined in Table 18 . Table 18 - AuditHistoryAnnotationUpdateEventType definition Attribute Value BrowseName AuditHistoryAnnotationUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType defined ... HasProperty References to the same Nodes . HasProperty Variable PerformInsertReplace PerformUpdateType PropertyType Mandatory HasProperty Variable NewValues Annotation[] PropertyType Mandatory HasProperty Variable OldValues Annotation[] PropertyType Mandatory ConformanceUnits Historical Access Annotation Audit Events
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.5 AuditHistoryDeleteEventType
  defined in Table 19 . Table 19 - AuditHistoryDeleteEventType definition Attribute Value BrowseName AuditHistoryDeleteEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType defined ... HasProperty References to the same Nodes . HasProperty Variable UpdatedNode NodeId PropertyType Mandatory HasSubtype ObjectType AuditHistoryRawModifyDeleteEventType HasSubtype ObjectType AuditHistoryAtTimeDeleteEventType HasSubtype ObjectType AuditHistoryEventDeleteEventType ConformanceUnits Historical Access Delete Raw Audit Events This EventType
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.6 AuditHistoryRawModifyDeleteEventType
  defined in Table 20 . Table 20 - AuditHistoryRawModifyDeleteEventType definition Attribute Value BrowseName AuditHistoryRawModifyDeleteEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryDeleteEventType defined in Table ... HasProperty References to the same Nodes . HasProperty Variable IsDeleteModified Boolean PropertyType Mandatory HasProperty Variable StartTime UtcTime PropertyType Mandatory HasProperty Variable EndTime UtcTime PropertyType Mandatory HasProperty Variable OldValues DataValue[] PropertyType Mandatory
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.7 AuditHistoryAtTimeDeleteEventType
  defined in Table 21 . Table 21 - AuditHistoryAtTimeDeleteEventType definition Attribute Value BrowseName AuditHistoryAtTimeDeleteEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryDeleteEventType defined in Table ... HasProperty References to the same Nodes . HasProperty Variable ReqTimes UtcTime[] PropertyType Mandatory HasProperty Variable OldValues DataValue[] PropertyType Mandatory ConformanceUnits Historical Access Audit Delete At Time This EventType inherits all Properties
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.8 AuditHistoryEventDeleteEventType
  defined in Table 22 . Table 22 - AuditHistoryEventDeleteEventType definition Attribute Value BrowseName AuditHistoryEventDeleteEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryDeleteEventType defined in Table ... HasProperty References to the same Nodes . HasProperty Variable EventIds ByteString[] PropertyType Mandatory HasProperty Variable OldValues HistoryEventFieldList PropertyType Mandatory ConformanceUnits Historical Access Audit Delete Events This EventType inherits all Properties
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.9 AuditHistoryConfigurationChangeEventType
  defined in Table 22 . Table 23 - AuditHistoryConfigurationChangeEventType definition Attribute Value BrowseName AuditHistoryConfigurationChangeEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditEventType defined ... HasProperty References to the same Nodes . ConformanceUnits Historical Access Audit Configuration Change Events This EventType inherits all Properties of the AuditEventType . Their semantic is defined
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.10 AuditHistoryBulkInsertEventType
  formally defined Table 24 . Table 24 - AuditHistoryBulkInsertEventType definition Attribute Value BrowseName AuditHistoryBulkInsertEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditEventType defined ... HasProperty References to the same Nodes . HasProperty Variable UpdatedNode NodeId PropertyType Mandatory HasProperty Variable StartTime UtcTime PropertyType Mandatory HasProperty Variable EndTime UtcTime PropertyType Mandatory ConformanceUnits Historical Access Audit BulkInsert Events
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.1 CertificateGroupType
  Table 41 . Table 41 - CertificateGroupType Definition Attribute Value BrowseName 0:CertificateGroupType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined ... specific TrustList instance generates the CertificateExpired or TrustListOutOfDate Alarms , the corresponding HasCondition References shall be specified on the instance. The GetRejectedList Method returns the list of Certificates that have been
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.6.6 HasPushedSecurityGroup
  used directly. It is a subtype of the HierarchicalReferences ReferenceType . The SourceNode of References of this type shall be an Object of ObjectType PubSubKeyPushTargetType or an ObjectType that ... Table 224 - HasPushedSecurityGroup ReferenceType Attributes Value BrowseName HasPushedSecurityGroup InverseName HasPushTarget Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HierarchicalReferences defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.6 HasPubSubConnection
  used directly. It is a subtype of the HasComponent ReferenceType . The SourceNode of References of this type shall be the PublishSubscribe Object defined in 8.3.2 . The TargetNode of this ReferenceType ... Table 237 - HasPubSubConnection ReferenceType Attributes Value BrowseName HasPubSubConnection InverseName PubSubConnectionOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HasComponent defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.5 DataSetToWriter
  used directly. It is a subtype of the HierarchicalReferences ReferenceType . The SourceNode of References of this type shall be an Object of ObjectType PublishedDataSetType or an ObjectType that ... Table 252 - DataSetToWriter ReferenceType Attributes Value BrowseName DataSetToWriter InverseName WriterToDataSet Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HierarchicalReferences defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.9 HasWriterGroup
  used directly. It is a subtype of the HasComponent ReferenceType . The SourceNode of References of this type shall be an instance of the PubSubConnectionType defined in 9.1.5.2 . The TargetNode ... Table 273 - HasWriterGroup ReferenceType Attributes Value BrowseName HasWriterGroup InverseName IsWriterGroupOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HasComponent defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.10 HasReaderGroup
  used directly. It is a subtype of the HasComponent ReferenceType . The SourceNode of References of this type shall be an instance of the PubSubConnectionType defined in 9.1.5.2 . The TargetNode ... Table 274 - HasReaderGroup ReferenceType Attributes Value BrowseName HasReaderGroup InverseName IsReaderGroupOf Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HasComponent defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.6 HasDataSetWriter
  used directly. It is a subtype of the HasComponent ReferenceType . The SourceNode of References of this type shall be an instance of the WriterGroupType defined in 9.1.6.3 . The TargetNode ... Table 279 - HasDataSetWriter ReferenceType Attributes Value BrowseName HasDataSetWriter InverseName IsWriterInGroup Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HasComponent defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.12 HasDataSetReader
  used directly. It is a subtype of the HasComponent ReferenceType . The SourceNode of References of this type shall be an instance of the ReaderGroupType defined in 9.1.6.6 . The TargetNode ... Table 285 - HasDataSetReader ReferenceType Attributes Value BrowseName HasDataSetReader InverseName IsReaderInGroup Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of HasComponent defined in OPC 10000-5 . Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.5 StandaloneSubscribedDataSetType
  defined in Table 306 . Table 306 - StandaloneSubscribedDataSetType definition Attribute Value BrowseName StandaloneSubscribedDataSetType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of BaseObjectType defined ... standalone SubscribedDataSet and the connected DataSetReader is provided in both directions through the inverse References from the SubscribedDataSet Object
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.12.2 Supported configuration properties
  properties Node with the HasKeyValueDescription ReferenceType defined in OPC 10000-5 . The SourceNode of References of this type shall be one of the following Nodes: ConfigurationProperties Property of the PublishSubscribeType
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  definition of the SafetyACSet. Table 3 - SafetyACSet definition Attribute Value BrowseName SafetyACSet References NodeClass BrowseName Comment OrganizedBy by the Objects Folder defined in OPC 10000-5. HasTypeDefinition ObjectType FolderType Entry ... used. A description of the graphical notation for the different types of Nodes and References (shown in Figure 3 , Figure 4 , and Figure 6 ) can be found
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.6 FiniteStateMachineType
  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 ... HasEffect Reference to a subtype of BaseEventType . The StateMachineType shall have GeneratesEvent References to the targets of a HasEffect Reference for each of its Transitions . A FiniteStateMachineType may define Methods
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.11 TransitionType
  Object of the ObjectType StateType . Each Transition can have one or more HasCause References pointing to the cause that triggers the Transition . Each Transition can have one or more HasEffect ... References pointing to the effects that occur when the Transition was triggered. Table 11 - TransitionType definition Attribute Value BrowseName TransitionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.13 ToState
  ReferenceType shall be an Object of the ObjectType StateType or one of its subtypes. References of this ReferenceType may be only exposed uni-directional. Sometimes this is required, for example ... Table 13 - ToState ReferenceType Attributes Value BrowseName ToState InverseName FromTransition Symmetric False IsAbstract False References NodeClass BrowseName Comment Conformance Units Base Info Finite State Machine Instance
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.4 Example of a StateMachine having Transition to SubStateMachine
  another StateMachine . In this case it is suitable to expose the FromState or ToState References uni-directional, that is, only pointing from the Transition to the State and not being ... able to handle the information of a StateMachine if the ToState and FromState References are only exposed as forward References and the inverse References are omitted. Figure 10 gives
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  5 AliasNames Information Model overview
  AliasNames functionality (illustrated in Figure 1 ) defines a number of ObjectTypes , Methods , DataTypes and References . Figure 2 illustrates an example of the Object model defined for AliasNames . Figure 1 - AliasNames
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  8.1 Overview
  Overview The following References are defined for the AliasNames model
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  8.2 AliasFor ReferenceType
  Nodes might not have a reference back to instance of AliasNameType. The SourceNode of References of this type shall be an Object of type AliasNameType . The TargetNode of this ReferenceType ... Table 21 - AliasFor Definition Attributes Value BrowseName AliasFor InverseName HasAlias Symmetric False IsAbstract False References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences ReferenceType defined in OPC 10000-5 ConformanceUnits AliasName Base
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.3 TagVariables
  AliasNameCategoryType . TagVariables shall restrict instances of AliasNameType to those that have an AliasFor References that point to Variables. The TagVariables instance is formally defined in Table 23 . Table 23 - TagVariables ... definition Attribute Value BrowseName TagVariables References NodeClass BrowseName DataType TypeDefinition OrganizedBy by the Aliases defined in 9.2 HasTypeDefinition ObjectType AliasNameCategoryType Defined in 6.3 ConformanceUnits AliasName Category Tags This
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.4 Topics
  instance of AliasNameCategoryType . Topics shall restrict instances of AliasNameType to only have AliasFor References that point to PublishedDataSetType (or subtypes) instances (PublishedDataSetType is defined in OPC 10000-14 ). The Topics ... formally defined in Table 24 . Table 24 - Topics definition Attribute Value BrowseName Topics References NodeClass BrowseName DataType TypeDefinition OrganizedBy by the Aliases defined in 9.2 HasTypeDefinition ObjectType AliasNameCategoryType Defined
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  C.3 Unregister a Server
  Servers that referenced it have been removed. The GDS shall remove any AliasFor References that point to the unregistered Server . The GDS shall delete the ServerUri of the unregistered Server
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.5.1.2 IetfBaseNetworkInterfaceType definition
  defined in Table 58 . Table 58 - IetfBaseNetworkInterfaceType definition Attribute Value BrowseName IetfBaseNetworkInterfaceType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType HasInterface ObjectType IIetfBaseNetwork­InterfaceType Applied from ... DisplayName: bit/s Description: bit per second - The components of the IetfBaseNetworkInterfaceType have additional References which are defined in Table 60 . Table 60 - IetfBaseNetworkInterfaceType Additional References SourceBrowsePath Reference Type Is Forward
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.1.1 Virtual Network Interfaces
  represented by Objects representing the virtual and the physical network interface instances. HasLowerLayerInterface References point from the Object(s) representing the virtual interface(s) to the Object representing the physical ... IetfBaseNetworkInterfaceType . An example is shown in Figure A-1 . Note: The usage of the References is following the YANG modelling approach which is using reference pointers in the YANG-interface
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.1.2 Link Aggregation
  represented by Objects representing the logical aggregation and the particular physical interface instances. HasLowerLayerInterface References point from the Object(s) representing the aggregation interface to the Objects representing the physical
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.2.2 Definition
  software is running in an environment, IsExecutingOn should be used. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a software component. The TargetNode ... References of this ReferenceType shall be an Object or ObjectType representing an execution environment for a software component, which might be a piece of hardware (e.g. Device) or some other
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.3.1 Overview
  relation between a software component and its execution environment it is currently executing on. References of this ReferenceType might be very dynamic and need to disappear as soon
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.3.2 Definition
  execution environment it is currently executing on (e.g. Hardware component, Task or Thread). References of this ReferenceType shall only be used when the software component is currently executed / running ... SourceNode of References of this 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
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.4.2 Definition
  controlling component to the components controlled by the controlling component. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing the controlling component, as for example ... software component. The TargetNode of References of this ReferenceType shall be an Object representing a component that is controlled by the TargetNode . Controls is formally defined in Table 3 . Table
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.5.1 Overview
  need each other in order to work. In that case, there would be two References , the first one pointing from one component to the other, and the second one vice
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.5.2 Definition
  components that are needed by the component in order to work. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a component that utilizes ... TargetNode in order to work. The TargetNode of References of this ReferenceType shall be an Object or ObjectType representing the required component. Requires is formally defined in Table 4 . Table
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.6.2 Definition
  component to other components it requires in order to work. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a component that requires the TargetNode ... order to work. The TargetNode of References of this ReferenceType shall be an Object representing the required component used by the SourceNode . Requires References shall not lead to loops, that
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.7.2 Definition
  physically connected, without one being a subcomponent of the other. The SourceNode of References of this type shall be an Object or ObjectType representing a piece of hardware. The TargetNode ... Table 6 - IsPhysicallyConnectedTo Definition Attributes Value BrowseName IsPhysicallyConnectedTo InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in OPC 10000-5 Conformance Units Base Info IsPhysicallyConnectedTo
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.8.1 Overview
  other; i.e., the Client should browse each of the Nodes checking for additional RepresentsSameEntityAs References
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.8.2 Definition
  Nodes that represent the same entity in the real world. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType ... Table 7 - RepresentsSameEntityAs Definition Attributes Value BrowseName RepresentsSameEntityAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in OPC 10000-5 Conformance Units Base Info RepresentsSameEntityAs
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.9.2 Definition
  ReferenceType is to relate two Nodes that represent the same hardware. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType ... Table 8 - RepresentsSameHardwareAs Definition Attributes Value BrowseName RepresentsSameHardwareAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of RepresentsSameEntityAs defined in 4.8 Conformance Units Base Info RepresentsSameHardwareAs
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.10.2 Definition
  ReferenceType is to relate two Nodes that represent the same functionality. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType ... Table 9 - RepresentsSameFunctionalityAs Definition Attributes Value BrowseName RepresentsSameFunctionalityAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of RepresentsSameEntityAs defined in 4.8 Conformance Units Base Info RepresentsSameFunctionalityAs
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.11.2 Definition
  Node to the hard- and software needed to provide the functionality. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing some functionality. The TargetNode ... References of this ReferenceType shall be an Object or ObjectType representing some hard- or software. IsHostedBy is formally defined in Table 10 . Table 10 - IsHostedBy Definition Attributes Value BrowseName IsHostedBy
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.12.2 Definition
  hardware component to its subcomponent, which is also a hardware component. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a piece of hardware ... TargetNode of References of this ReferenceType shall be an Object representing a piece of hardware that is a component of the SourceNode . HasPhysicalComponent is formally defined in Table 11 . Table
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.13.2 Definition
  hardware component to its subcomponent that is inside the component. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a piece of hardware. The TargetNode ... References of this ReferenceType shall be an Object representing a piece of hardware that is a component of the SourceNode . HasContainedComponent is formally defined in Table 12 . Table 12 - HasContainedComponent
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.14.2 Definition
  hardware component to its subcomponent that is attached to the component. The SourceNode of References of this ReferenceType shall be an Object or ObjectType representing a piece of hardware ... TargetNode of References of this ReferenceType shall be an Object representing a piece of hardware that is a component of the SourceNode . HasAttachedComponent is formally defined in Table 13 . Table
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.1 Overview
  Overview OPC UA relates Nodes using References . This concept is intentionally a simple construct, where the only information of a Reference is the SourceNode , the TargetNode , the ReferenceType ... other Nodes to provide additional information (see also 5.2 ). As Nodes can have several References , each ReferenceDescription Variable contains the unique definition of one Reference . An example is given
• 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 ... Property ReferenceRefinement is defined for the ReferenceDescriptionVariableType (see 5.3.1 ) allowing to make the refined References explicit. In Figure 5 , an example is given. The ReferenceDescription Variable containing the refinement
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.3.1 ReferenceDescriptionVariableType
  ReferenceDescriptionVariableType Definition Attribute Value BrowseName ReferenceDescriptionVariableType IsAbstract FALSE ValueRank -1 (-1 = Scalar) DataType ReferenceDescriptionDataType References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseDataVariableType defined in OPC 10000-5 HasProperty ... Conformance Units Base Info ReferenceDescription The optional Property ReferenceRefinement contains an array of References refining the original Reference represented by an instance of ReferenceDescriptionVariableType . Each entry in the array contains
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.4.1 HasReferenceDescription
  refinement of the Reference (being part of the refinement path)). The SourceNode of References of this type can be of any NodeClass . The TargetNode of this ReferenceType shall ... Table 15 - HasReferenceDescription Definition Attributes Value BrowseName HasReferenceDescription InverseName ReferenceDescriptionOf Symmetric FALSE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of HasChild defined in OPC 10000-5 Conformance Units Base Info
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.5.2 ReferenceListEntryDataType
  Reference without SourceNode . It can be used to list a path of References without repeating the SourceNode , like in the ReferenceRefinement Property in 5.3.1 . The structure is defined in Table ... Reference, if TRUE in forward direction, if FALSE, in inverse direction. For symmetric references it shall always be set to TRUE. TargetNode ExpandedNodeId The TargetNode of the Reference. Its representation
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  A.1 Overview
  adds a Variable to provide additional information. This approach allows to handle the References natively without the need to access the additional information. An alternative approach is described
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  A.2 Alternative Approach: Intermediate Object
  Alternative Approach: Intermediate Object One modelling construct to add information to References , is to provide an intermediate Object as proxy with additional information (see Figure A.1 ). The approach often makes ... Nodes without the need to deal with an intermediate Object . Figure A.1 - Refinement of References by Proxy Object
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.1 Example Serialize RIO Channel Groups
  limiting the Variables belonging to the SerializationScope to those connected with HasRioProcessVariable References to the SerializationStartNode. A Client only interested in the Channel Group configuration uses a compact representation