Search

Scope: Core (OPC-10000-*) All specs

57 result(s) for ReferenceType s

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

3.3.2 Conventions for defining NodeClasses

extended by other parts of this series of standards. This document also defines ReferenceTypes , but ReferenceTypes may also be specified by a Server or by a client using the NodeManagement ... References identifying that any ReferenceType may be used for the NodeClass, including system specific ReferenceTypes . The NodeClass tables only specify how the NodeClasses can be used as SourceNodes of References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.1 Overview

concepts. Clause 6 defines details on the type model for ObjectTypes and VariableTypes . Standard ReferenceTypes , DataTypes and EventTypes are defined in Clauses 7 to 8.61 . The informative Annex A describes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.4.4 References

reference another Node with the same ReferenceType only once. Any subtypes of concrete ReferenceTypes are considered to be equal to the base concrete ReferenceTypes when identifying References ... subtypes of ReferenceTypes ). Figure 4 illustrates this model of a Reference . Figure 4 - Reference Model The TargetNode of a Reference may be in the same AddressSpace or in the AddressSpace
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.7.3 Event Categorization

Events . Event sources can also be organised into groups by using the Event ReferenceTypes described in 7.16 and 7.18 . For example, a Server may define Objects in the AddressSpace representing ... this case, two relationships would be established. Refer to the description of the Event ReferenceTypes for additional examples. Clients can select a category or categories of Events by defining content
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.3.1 General

NodeClass is used to represent References . This standard defines a set of ReferenceTypes provided as an inherent part of the OPC UA Address Space Model. These ReferenceTypes are defined ... representation in the AddressSpace is defined in OPC 10000-5 . Servers may also define ReferenceTypes . In addition, OPC 10000-4 defines NodeManagement Services that allow Clients to add ReferenceTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.3.2 Attributes

ReferenceType shall be unique in a Server . It is not allowed that two different ReferenceTypes have the same BrowseName . The IsAbstract Attribute indicates if the ReferenceType is abstract. Abstract ReferenceTypes ... ReferenceType is symmetric, the InverseName Attribute shall be omitted. Examples of symmetric ReferenceTypes are "Connects To" and "Communicates With". Both imply the same semantic coming from
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
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.3.3.2 HasProperty References

indicate the version of the ReferenceType . There are no additional Properties defined for ReferenceTypes in this standard. Additional parts this series of standards may define additional Properties for ReferenceTypes
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 ... spans a special hierarchy"). The DisplayName , and also the InverseName for non-symmetric ReferenceTypes , reflect the specialization. If a ReferenceType specifies some constraints (e.g. "allow no loops
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

However, restrictions may be defined by the ReferenceType excluding its use for Objects . Standard ReferenceTypes are described in Clause 7 . If the Object is used as an InstanceDeclaration
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.2 ObjectType NodeClass

However, restrictions may be defined by the ReferenceType excluding its use for ObjectTypes . Standard ReferenceTypes are described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

However, restrictions may be defined by the ReferenceType excluding its use for DataVariables . Standard ReferenceTypes are described in Clause 7 . A DataVariable is intended to be defined in the context
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.5 VariableType NodeClass

However, restrictions may be defined by the ReferenceType excluding its use for VariableTypes . Standard ReferenceTypes are described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

However, restrictions may be defined by the ReferenceType excluding its use for Methods . Standard ReferenceTypes are described in Clause 7 . A Method shall always be the TargetNode of at least
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.1 Overview

types. Subtyping can only occur between Nodes of the same NodeClass . Rules for subtyping ReferenceTypes are described in 5.3.3.3 . There is no common definition for subtyping DataTypes , as described
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.3.3 Overriding InstanceDeclarations

Node unless it needs to change it. The semantics of certain TypeDefinitionNodes and ReferenceTypes may impose additional restrictions with regard to overriding Nodes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.1 General

General This standard defines ReferenceTypes as an inherent part of the OPC UA Address Space Model. Figure 38 informally describes the hierarchy of these ReferenceTypes . Other parts of this series ... standards may specify additional ReferenceTypes . The remainder of 7 defines the ReferenceTypes . OPC 10000-5 defines their representation in the AddressSpace . Figure 38 - Standard ReferenceType Hierarchy
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.2 References ReferenceType

semantic associated with this ReferenceType . This is the base type of all ReferenceTypes . All ReferenceTypes shall be a subtype of this base ReferenceType - either direct or indirect. The main purpose
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.4 NonHierarchicalReferences ReferenceType

when trying to present a hierarchy. To distinguish Hierarchical and NonHierarchical References , all concrete ReferenceTypes shall inherit from either hierarchical References or Non-hierarchical References , either direct or indirect. There
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.7 HasComponent ReferenceType

used to relate complex Variable s or VariableTypes with their DataVariables . Like all other ReferenceTypes , this ReferenceType does not specify anything about the ownership of the parts, although it represents
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.7 Defining ReferenceTypes

Defining ReferenceTypes Defining new ReferenceTypes should only be done if the predefined ReferenceTypes are not suitable. Whenever a new ReferenceType is defined, the most appropriate ReferenceType should be used ... supertype. It is expected that Servers will have new defined hierarchical ReferenceTypes to expose different hierarchies, and new Nonhierarchical ReferenceTypes to expose relationships between Nodes in the AddressSpace
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.1 Background

stereotype <<TypeExtension>>. Those stereotyped UML objects represent DataTypes or ReferenceTypes . The domain model can contain user-defined ReferenceTypes and DataTypes , also marked as <<TypeExtension
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.3 Meta Model

standards can extend the OPC UA Meta Model by adding Attributes and defining new ReferenceTypes . The figures in the following clauses are not intended to be complete and therefore
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.3.2 ReferenceType

B.3.2 ReferenceType ReferenceType is shown in Figure B.5 and predefined ReferenceTypes in Figure B.6 . Figure B.5 - Reference and ReferenceType If Symmetric is "false" an InverseName shall be provided ... Figure B.6 - Predefined ReferenceTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.2 Simple notation

symmetric and asymmetric References are represented in general, and also defines shortcuts for some ReferenceTypes . Although it is recommended to use those shortcuts, it is not required. Thus, instead ... Nodes depending on the NodeClass ReferenceType Graphical Representation Comment Any symmetric ReferenceType Symmetric ReferenceTypes are represented as lines between Nodes with closed and filled arrows on both sides pointing
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.1 Description

Node from which the RelativePath is based. The RelativePath contains a sequence of ReferenceTypes and BrowseNames . One purpose of this Service is to allow programming against type definitions. Since BrowseNames
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.1 Overview

Variable Node using a Node in the type system and relative path constructed from ReferenceTypes and BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.5 SimpleAttributeOperand

only use AttributeOperand , however, the AttributeOperand can be replaced by a SimpleAttributeOperand whenever all ReferenceTypes in the RelativePath are subtypes of HierarchicalReferences and the targets are Object or Variable Nodes
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.2 Used type model

Object is provided in the box and a numeric instance NodeId in brackets. Standard ReferenceTypes use the OPC UA notation, custom ReferenceTypes are listed as a named Reference . For Properties
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables and not in the table itself, therefore they
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.2.8 ReferenceTypes

ReferenceTypes This standard Object is the browse entry point for ReferenceType Nodes . Figure 6 illustrates the organization of ReferenceTypes . Organizes References are used to define ReferenceTypes and Objects referenced ... ReferenceTypes " Object . The " ReferenceTypes " Object shall not reference any other NodeClasses . See Clause 11 for a discussion of the standard ReferenceTypes that appear beneath the " ReferenceTypes
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.15 Example

There are no rules for what is included. A useful guideline would include standard ReferenceTypes and DataTypes if they are referenced in the document. An Alias may be used
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.4.1 General

General This Clause defines ReferenceTypes that are needed beyond those already specified as part of 10000-3 and 10000-5 . This includes extending TwoStateVariableType state machines with sub states
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.2 EventNotifier and source hierarchy

linked together and with the included ConditionSources using the HasNotifier and the HasEventSource Reference Types . The Server Object shall be the root of this hierarchy. Figure 26 shows such ... used as Event notifier. See 10000-3 for the formal definition of these Reference Types . Figure 26 - Typical HasNotifier Hierarchy
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.1 Overview

longer used, until the tank is returned to service. This section describes ReferenceTypes that can be used by a StateMachine to indicate that a specific Effect on Alarm s caused
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.1 General

document describes the basic infrastructure to model state machines. It defines ObjectTypes , VariableTypes and ReferenceTypes and explains how they should be used. This document is an integral part of this
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes

4.1 Overview

Overview The following Figure 1 gives an overview of the ReferenceTypes defined in the following subsections. Figure 1 - Overview of ReferenceTypes
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes

5.1 Overview

information of a Reference is the SourceNode , the TargetNode , the ReferenceType and for asymmetric ReferenceTypes the direction (forward or inverse). Sometimes, it is desirable to add more information to such
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.4 SerializationScope and SerializationEntity

SerializationScope and the handling of metadata. Including or excluding Nodes referenced using certain ReferenceTypes , limiting the depth of the SerializationScope and settings which companion values like statusCodes shall be part
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

5.1 Example Serialize RIO Channel Groups

Objects configure the "SerializationScope 3" by including only Objects connected with HasRioOutputChannel ReferenceTypes to the "ChannelGroup" Object used as SerializationStartNode as shown in Figure 4 . Since
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.4 Include- and ExcludeReferenceTypes Properties

Include- and ExcludeReferenceTypes Properties These Properties allow to select which ReferenceTypes are followed to create the SerializationScope : The IncludeReferenceTypes Property contains an array of ReferenceType NodeIds . Any Reference of each
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.6 ConsiderSubElementSerializationProperties Property

will be considered. "Variable2" has such a SerializationEntity . This SerializationEntity sets the ReferenceTypes to select all hierarchical References but no HasComponent References . As result, "Property1
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.3 RIO Channel Process Values

SerializationEntity" referenced by the SerializationStartNode directs the SerializationProcess to follow only HasRioOutputChannel ReferenceTypes . Although the SerializationDepth is configured as "no limit" (see 6.3.5 ), the SerializationProcess would stop
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.2 AutomationComponent model

model, see the definition of FunctionalEntityType in 6.4 . For a description of the available ReferenceTypes in this Information Model , see 11.1 . Figure 1 - OPC UA FX Information Model overview
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.3.3 Asset model relationships

their own view of the Asset relationships. The asset model makes use of specific ReferenceTypes to represent these relationships. OPC 10000-5 and OPC 10000-23 define some base ReferenceTypes ... this document further extends the available list of ReferenceTypes (see 11.1 ). Figure 4 illustrates some possible views that an asset model can include. Some Assets could contain other Assets (blue
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.5 Relationships between FunctionalEntities and Assets

only link them (see Figure 7 for an illustration and 11.1 for details on ReferenceTypes ). Figure 7 - Relationships between FunctionalEntities and Assets Figure 7 also illustrates an AutomationComponent , which provides
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.1 Modelling of Asset relationships

used for modelling Assets . This list is extended by this document. The following ReferenceTypes will be illustrated in various examples in this annex: HasContainedComponent indicates that an Asset has another
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.2 Example single board computer model

features of a Raspberry Pi, but will be used to illustrate the available ReferenceTypes . This single-board computer could be modelled in many ways, and this illustrates just a possible
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.1 Overview

followed due to mismatches in the capabilities of OPC UA vs. AML. For instance, ReferenceTypes in OPC UA can be used to connect any two nodes in the UA AddressSpace
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.7 ReferenceType mapping

ReferenceType mapping OPC UA ReferenceTypes are modelled in AML as InterfaceClasses. All AML InterfaceClasses that represent OPC UA ReferenceTypes shall derive directly or indirectly from the Reference's InterfaceClass ... opcfoundation.org/UA/ InterfaceClassLibrary. OPC UA ReferenceTypes that are symmetric or have the same forward and inverse name shall be represented by a single AML InterfaceClass with the same name
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

B.1.3 UA InterfaceClass Library

opcfoundation.org/UA/" defines the InterfaceClasses that correspond to their equivalent OPC UA ReferenceTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

C.1.2 DI InterfaceClass Library

opcfoundation.org/UA/DI/" defines the InterfaceClasses that correspond to their equivalent OPC DI ReferenceTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

D.1.2 OPC UA FX InterfaceClass Libraries

opcfoundation.org/UA/FX/CM" define the InterfaceClasses that correspond to their equivalent OPC UA FX ReferenceTypes
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables and not in the table itself, therefore they
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

5.5 ConnectsTo and ConnectsToParent ReferenceTypes

ConnectsTo and ConnectsToParent ReferenceTypes The ConnectsTo ReferenceType is a concrete ReferenceType used to indicate that source and target Node have a topological connection. It is NonHierarchical and symmetric, because this ... Device ) of a Network . It is a subtype of the ConnectsTo ReferenceType . The two ReferenceTypes are illustrated in Figure 23 . Figure 23 - Type Hierarchy for ConnectsTo and ConnectsToParent References
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

14.2 Relations to other Assets

Typically, those References are non-hierarchical References . OPC 10000-23 defines several of those ReferenceTypes , Companion Specification may define additional ReferenceTypes . In Figure 18 , some examples are given. X:Asset1 ... References from the asset considering forward and backward direction. Clients may filter for specific ReferenceTypes
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.3 Companion Specifications

industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects