Search

200 result(s) for Objects

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  3.2 Specification parts
  LogObject Part 26 specifies an OPC UA information model for a set of Objects and Events that can be used to collect diagnostic information in a system
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.3 Design goals
  model. OPC UA also allows Servers to provide Clients with type definitions for the Objects accessed from the AddressSpace . This allows Information Models to be used to describe the contents
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.2 Integrated AddressSpace model
  Integrated AddressSpace model The set of Objects and related information that the Server makes available to Clients is referred to as its AddressSpace . The OPC UA AddressSpace represents its contents
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.3 Integrated object model
  Object Model provides a consistent, integrated set of NodeClasses for representing Objects in the AddressSpace . This model represents Objects in terms of their Variables, Events and Methods , and their relationships ... with other Objects . OPC 10000-3 describes this model. The OPC UA object model allows Servers to provide type definitions for Objects and their components. Type definitions may be subclassed
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.4 Support for information models
  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 s that provide semantic information ... real Objects (type definitions). ObjectType Node s to support subclassing of type definitions. Data type definitions exposed in the AddressSpace that allow industry specific data types to be used. Industry
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.8 Method Service Set
  Method Service Set Methods represent the function calls of Objects . They are defined in OPC 10000-4 . Methods are invoked and return after completion, whether successful or unsuccessful. Execution times ... Services . Clients discover the Methods supported by a Server by browsing for the owning Objects that identify their supported Methods . Because Methods may control some aspect of plant operations, method
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  1 Scope
  Scope This specification describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects . This Part is the OPC UA meta model on which OPC UA information models are based
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.7 DataVariable
  DataVariable Variables that represent values of Objects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.3 Object Model
  AddressSpace is to provide a standard way for Servers to represent Objects to Clients . The OPC UA Object Model has been designed to meet this objective. It defines Objects ... terms of Variables and Methods . It also allows relationships to other Objects to be expressed. Figure 2 illustrates the model. Figure 2 - OPC UA Object Model The elements of this
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.1 General
  General The set of Objects and related information that the OPC UA Server makes available to Clients is referred to as its AddressSpace . The model for Objects is defined ... Object Model (see 4.3 ). Objects and their components are represented in the AddressSpace as a set of Nodes described by Attributes and interconnected by References . Figure 3 illustrates the model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  Properties Properties are Server -defined characteristics of Objects , DataVariables and other Nodes . Properties differ from Attributes in that they characterise what the Node represents, such as a device
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.3 DataVariables
  earliestStartTime". As another example, function blocks in control systems might be represented as Objects . The parameters of the function block, such as its setpoints, may be represented as DataVariables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  General OPC UA Servers shall provide type definitions for Objects and Variables . The HasTypeDefinition Reference shall be used to link an instance with its type definition represented by a TypeDefinitionNode ... such a base type if no more specialised type information is available. Objects and Variables inherit the Attributes specified by their TypeDefinitionNode (see 6.4 for details). In some cases
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.1 General
  Events defined in this document are not directly visible in the OPC UA AddressSpace . Objects and Views can be used to subscribe to Events . The EventNotifier Attribute of those Nodes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.3 Event Categorization
  Event ReferenceTypes described in 7.16 and 7.18 . For example, a Server may define Objects in the AddressSpace representing Events related to physical devices, or Event areas of a plant
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.9.1 Overview
  loopback address is only accessible from the same machine. OPC 10000-5 defines the Objects , Methods and DataTypes used to represent and manage these mapping rules in the Address Space
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  that represent a generic feature (functionality), assumed to be usable by different ObjectTypes or Objects . The Interface model specifies the rules and mechanisms to achieve this. The " InterfaceTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.1 Overview
  those used to organise the AddressSpace and then by the NodeClasses used to represent Objects . The NodeClasses defined to represent Objects fall into three categories: those used to define instances
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Object NodeClass Objects are used to represent systems, system components, real-world objects and software objects. Objects are defined using the Object NodeClass , specified in Table 11 . Table 11 - Object ... defined in 8.59 . References HasComponent 0..* HasComponent References identify the DataVariables , the Methods and Objects contained in the Object . HasProperty 0..* HasProperty References identify the Properties of the Object . HasModellingRule
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  ObjectType NodeClass ObjectTypes provide definitions for Objects . ObjectTypes are defined using the ObjectType NodeClass , which is specified in Table 12 . Table 12 - ObjectType NodeClass Name Use Data Type Description Attributes ... boolean Attribute with the following values: TRUE it is an abstract ObjectType , i.e. no Objects of this type shall exist, only Objects of its subtypes. FALSE
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.3 Standard ObjectType FolderType
  ObjectType FolderType is formally defined in OPC 10000-5 . Its purpose is to provide Objects that have no other semantic than organizing of the AddressSpace . A special ReferenceType is introduced ... those Folder Objects , the Organizes ReferenceType . The SourceNode of such a Reference should always be a View or an Object of the ObjectType FolderType ; the TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.4 Client-side creation of Objects of an ObjectType
  Client-side creation of Objects of an ObjectType Objects are always based on an ObjectType , i.e. they have a HasTypeDefinition Reference pointing to its ObjectType . Clients can create Objects using ... Object of this ObjectType . This Method may be useful for the creation of Objects where the semantic of the creation should differ from the default behaviour expected in the context
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  this type. HasEncoding 0..* HasEncoding References identify the encodings of the DataType represented as Objects of type DataTypeEncodingType . Only concrete Structured DataTypes may use HasEncoding References . Abstract, Built-in, Enumeration ... Default XML" having the NamespaceIndex 0. The BrowseName of the DataTypeEncoding Objects shall be unique in the context of a DataType , i.e. a DataType shall not point
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.4 Example of usage of DataTypeRefinements
  details of the DataTypeRefinements is not shown in the figure. There are two Objects of Z:SuperObjectType, both using DataTypeRefinements . Z:Object1 has the Property Z:Prop1 and the DataVariables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.4 Similar Node of InstanceDeclaration
  same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects the same TypeDefinitionNode or a subtype of it. In the case of a Method a similar
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  Reference but the new target shall have the same NodeClass and for Objects and Variables also the same type or a subtype of the type specified in the parent
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.1 Overview
  same BrowseName and NodeClass as the InstanceDeclaration and, in cases of Variables and Objects , the same TypeDefinitionNode or a subtype of it. Instances may reference several Nodes with the same
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  exists then the BrowseName and NodeClass shall match the InstanceDeclaration . In the case of Objects or Variables, also the TypeDefinitionNode shall either match or be a subtype of the original
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  Constraints on an Instance Objects and Variables may change their Attribute values after being created. Special rules apply for some Attributes as defined in 6.2.7 . Additional References may be added ... ModellingRules defined on the InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode as the InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.1 General
  NonHierarchical References between InstanceDeclaration as well. ModellingRules are represented in the AddressSpace as Objects of the ObjectType ModellingRuleType . There are some Properties defining common semantic of ModellingRules. This edition ... define additional Properties for ModellingRules . OPC 10000-5 specifies the representation of the ModellingRule Objects, their Properties and their type in the AddressSpace . Subclause 6.4.4.3 defines how the ModellingRule
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.7 HasComponent ReferenceType
  HasComponent ReferenceType is a part of the SourceNode . This ReferenceType is used to relate Objects or ObjectTypes with their containing Objects , DataVariables , and Methods . This ReferenceType is also used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.18 HasNotifier
  Object Nodes . The ReferenceType is used to establish a hierarchical organization of event notifying Objects . It is a subtype of the HasEventSource ReferenceType defined in 7.16 . The TargetNode of this ... ReferenceType shall be Objects that are a source of Event Subscriptions . If the TargetNode of a Reference of this type generates an Event , then this Event shall also be provided
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.23 AssociatedWith ReferenceType
  InverseName. The semantic of this ReferenceType is to provide some generic association between two Objects . The SourceNode and TargetNode of References of this type shall be Objects
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.2 NamespaceIndex
  identify the same Object . This enables Clients that connect to those Servers to recognise Objects that they have in common. Namespace URIs, like Server names, are identified by numeric values
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  UserAccessLevel Attribute . This Permission is only valid for Variables (for reading historical values), and Objects or Views (for reading historical events). InsertHistory 8 The Client is allowed to insert ... UserAccessLevel Attribute . This Permission is only valid for Variables (for inserting historical values), and Objects or Views (for inserting historical events). ModifyHistory 9 The Client is allowed to modify
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.3 ObjectTypes
  ObjectTypes Subclause 5.5.1 states: " Objects are used to represent systems, system components, real-world objects, and software objects." Therefore ObjectTypes should be used if a type definition ... those ObjectTypes is useful (see  A.2 ). From a more abstract point of view Objects are used to group Variables and other Objects in the AddressSpace . Therefore ObjectTypes should be used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.4.3 Many Variables and / or Structured DataTypes
  Create several simple Variables using simple DataTypes always reflecting parts of the simple structure. Objects are used to group the Variables according to the structure of the data. Create
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3.4 Object and ObjectType
  B.3.4 Object and ObjectType Objects and ObjectTypes are shown in Figure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  create, modify, and delete MonitoredItems used to monitor Attribut es for value changes and Objects for Events . These Notifications are queued for transfer to the Client by Subscriptions . The Subscription
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.1 Overview
  Overview Methods represent the function calls of Objects . They are defined in OPC 10000-3 . Methods are invoked and return only after completion (successful or unsuccessful). Execution times for Methods ... Services . Clients discover the Methods supported by a Server by browsing for the owning Objects References that identify their supported Methods . Because Methods may control some aspect of plant operations
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.2 Parameters
  Method shall not have a ModellingRule . See OPC 10000-3 for a description of Objects and their Methods . methodId NodeId NodeId of the Method to invoke. If the objectId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  change is large enough to cause a Notification to be generated for the Variable . Objects and views can be used to monitor Events . Events are only available from Nodes where
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.8 Durable Subscriptions
  Subscriptions MonitoredItems are used to monitor Variable Values for data changes and event notifier Objects for new Events . Subscriptions are used to combine data changes and events of the assigned
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  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 ... instances is shown in Figure B.4 . These instances include a type Reference for Objects . Properties also have type References , but the References are omitted for simplicity. The name
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId , i.e., the specified Node ... only applicable for Variables . TypeDefinition of the referenced Node , only applicable for Variables and Objects . Referenced ModellingRule of the referenced Object . NOTE Notes referencing footnotes of the table content. Conformance
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.2 Objects
  Objects For all Objects specified in NamespaceIndex 0, the Attributes named in Table 4 shall be set as specified in Table 4 . Table 4 - Common Object Attributes Attribute Value EventNotifier
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.1 ServerType
  This Object is required to be present even if there are no vendor-defined Objects beneath it. See 6.3.6 for its description. ServerRedundancy describes the redundancy capabilities provided ... none. See 6.3.7 for the description of ServerRedundancyType . Namespaces provides a list of NamespaceMetadataType Objects with additional information about the namespaces used in the Server . See 6.3.14 for the description
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  ModelVersion , however other older UANodeSets may not include ModelVersion . Programatic comparisions of NamespaceMetadata Objects shall use the following: When the ModelVersion is specified in both NamespaceMetadata Objects it is used
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.14 NamespacesType
  NamespacesType This ObjectType defines a list of NamespaceMetadataType Objects provided by the Server . It is formally defined in Table 23 . Table 23 - NamespacesType definition Attribute Value BrowseName NamespacesType IsAbstract False ... NamespaceMetadataType OptionalPlaceholder Conformance Units Base Info ServerType The ObjectType contains a list of NamespaceMetadataType Objects representing the namespaces in the Server . The BrowseName of an Object shall be derived from
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.10 OrderedListType
  OrderedListType The OrderedListType is a base type to manage an ordered list of Objects . It is formally defined in Table 67 . Table 67 - OrderedListType Definition Attribute Value BrowseName OrderedListType IsAbstract ... GeneralModelChangeEventType Conformance Units Base Info OrderedList The <OrderedObject> Object represents the ordered Objects managed by Instances of the OrderedListType . The order is provided by the HasOrderedComponent References
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.11 IOrderedObjectType Definition
  IOrderedObjectType Definition The IOrderedObjectType defines the Interface all Objects managed by an OrderedListType shall implement. It is formally defined in Table 69 . Table 69 - IOrderedObjectType Definition Attribute Value BrowseName IOrderedObjectType ... gaps, but that is not required and Clients shall not assume this. All Objects in the same list shall use the same concrete DataType for the property NumberInList . Two Objects
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.12 DataTypeRefinementType definition
  DataTypeRefinement Object shall be unique, i.e., there shall not be two DataTypeRefinement Objects in an OPC UA Server having the same BrowseName . The ObjectType is formally defined in Table
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.6 ServerStatusType
  HasComponent Variable SecondsTillShutdown UInt32 BaseDataVariableType Mandatory HasComponent Variable ShutdownReason LocalizedText BaseDataVariableType Mandatory NOTE Containing Objects and Variables of these Objects and Variables are defined by their BrowseName defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.13 SessionDiagnosticsArrayType
  having the SessionDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type in 6.3.5 . The VariableType is formally defined in Table 83 . Table
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.15 SessionSecurityDiagnosticsArrayType
  having the SessionSecurityDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type in 6.3.5 . The VariableType is formally defined in Table 85 . Since
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.1 General
  General Objects and 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.1 Overview
  levels standardised for all Servers . Figure 1 illustrates the structure of the AddressSpace . All Objects in this figure are organised using Organizes References and have the ObjectType FolderType as type
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.2 Root
  AddressSpace . It contains a set of Organizes References that point to the other standard Objects . The " Root " Object shall not reference any other NodeClasses . It is formally defined ... HasTypeDefinition ObjectType FolderType Defined in 6.6 Organizes Object Views Defined in 8.2.3 Organizes Object Objects Defined in 8.2.4 Organizes Object Types Defined in 8.2.5 Conformance Units Base Info Core Structure
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 Views
  either directly or 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.4 Objects
  Objects This standard Object is the browse entry point for Object Nodes . Figure 3 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects ... Objects " standard Object . A View Node can be used as entry point into a subset of the AddressSpace containing Objects and Variables and thus the " Objects " Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.5 Types
  illustrates the structure beneath this Node . Only Organizes References are used to relate Objects to the " Types " standard Object . The " Types " Object shall not reference
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.6 ObjectTypes
  standard ObjectTypes defined in Clause 6 . Only Organizes References are used to relate Objects and ObjectTypes to the " ObjectTypes " standard Object . The " ObjectTypes " Object shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.7 VariableTypes
  illustrates the structure beneath this Node . Only Organizes References are used to relate Objects and VariableTypes to the " VariableTypes " standard Object . The " VariableTypes " Object shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.8 ReferenceTypes
  illustrates the organization of ReferenceTypes . Organizes References are used to define ReferenceTypes and Objects referenced by the " ReferenceTypes " Object . The " ReferenceTypes " Object shall not reference
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.9 DataTypes
  from the "DataTypes" Object to the DataType Nodes or using additional Folder Objects for grouping purposes. The intent is that all DataTypes of the Server exposed
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.10 EventTypes
  standard EventTypes defined in Clause 6 . Only Organizes References are used to relate Objects and ObjectTypes to the " EventTypes " standard Object . The " EventTypes " Object shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.11 InterfaceTypes
  standard ObjectTypes defined in clause 6. Only Organizes References are used to relate Objects and Interfaces to the " InterfaceTypes " standard Object . The " InterfaceTypes " Object shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.12 Locations
  illustrates the structure beneath this Node . Only Organizes References are used to relate Objects . Figure 9 - Locations organization The intent of the " Locations " Object is an entry point
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.3.1 General
  General The Server Object and its containing Objects and Variables are built in a way that the information can be gained in several ways, suitable for different kinds of clients ... cons of the different approaches. Figure 10 gives an overview of the containing Objects and Variables of the diagnostic information of the Server Object and where the information
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.2 ServerType and Server Object
  name in OPC 10000-6 . Nevertheless, aggregating Servers may want to expose the Server Objects of the OPC UA Servers they are aggregating in their AddressSpace . Therefore, it is very ... Server Object is an Object , because it groups a set of Variables and Objects containing information about the Server . The ServerType is a complex ObjectType , because the basic structure
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.3 Typed complex Objects beneath the Server Object
  Typed complex Objects beneath the Server Object Objects beneath the Server Object used to group information, such as Server capabilities or diagnostics, are also typed because an aggregating Server
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.7 Redundant information
  information of the entries can also be accessed individually as components of the SessionDiagnostics Objects provided for each session by the SessionsDiagnosticsSummary Object . A client can either access the arrays ... parts of the arrays) directly or browse to the SessionDiagnostics Objects to get the information of the individual entries. Thus, the information provided is redundant, but the Variables containing
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.10 Extensibility mechanism
  Server ; in other scenarios this may be a useful way to add information. Add Objects containing Variables or add Variables to the Objects defined in this part. If, for example ... ServerVendorCapabilityType to add information about the server-specific capabilities on the ServerCapabilities Objects . Because this extensibility point is already defined in this part, clients will look there for additional information.Use
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.8 ExtensionObject
  array element. Server implementers should use namespace qualified numeric NodeIds for any DataTypeEncoding Objects they define. This will minimize the overhead introduced by packing Structured DataType values into an ExtensionObject
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.2 Quantities entry point
  their Units managed in the Server . It is formally defined in Table 37 . All Objects of the QuantityType defined in clause 6.4.1 , that are managed in the Server , shall
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.2.3 ServerUnitType ObjectType Definition
  CoherentUnit UnitType O Conformance Units Data Access Quantities Base The optional Object AlternativeUnits contains Objects of the AlternativeUnitsType . These explicitly specify the units into which the conversion can be made
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.2 Branch
  A.3.1.2 Branch DA Branches are represented in the COM UA Wrapper as Objects of FolderType . The top-level branch (the root) should be represented by an Object where the BrowseName
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.10 Condition instances in the AddressSpace
  exposes Condition instances they usually will appear in the AddressSpace as components of the Objects that "own" them. For example, a temperature transmitter that has a built
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.12 Alarms in a system
  recover that the alarm has a comment or that it was acknowledged. The individual Objects models provide details about Alarm states and recovery
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.3 Condition and branch instances
  Condition and branch instances Conditions are Objects which have a state which changes over time. Each Condition instance has a ConditionId as an identifier which uniquely identifies it within
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.2 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 of Operator responsibility. The definition
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  8.1 Overview
  direct References from the Object to the Alarm . Alarms might also be related to Objects that are nested under the Object . When the Object is represented in a graphic ... illustrated in Figure 31 Figure 31 - AlarmSummary Equipment Object Example All of these sub-objects might have unique alarms associated with them, such as limit alarms on the temperature
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  Server are represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . The EventNotifier Attribute for these Objects always has the SubscribeToEvents flag
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.2 Event sources
  Server are represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . If the A&E COM Server supports source filtering then
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.3.2 ProgramStateMachineType states
  ProgramStateMachineType states The state Objects are instances of the StateType defined in OPC 10000-16 . Each state is assigned a unique StateNumber value defined in Table 6 . Subtypes ... used to distinguish the nature of the termination. The Halted state references four Transition Objects , which identify the allowed state transitions to the Ready state and from the Ready, Running
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.2 DomainDownload states
  sequence of transfers occurs in the Sending state. When the transfer completes the Objects are closed in the Closing state. If the transfer is terminated before all of the data
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.1.2 Annotations Property
  Properties to have Properties , the Annotations Property is only available for DataVariables or Objects . The Annotations Property shall be present on every HistoricalDataNode that supports modifications, deletions, or additions
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.2 HistoricalDataConfigurationType
  This Object is required to be present even if it contains no Aggregate configuration Objects . Aggregates are defined in OPC 10000-13 . AggregateFunctions is an entry point to browse
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.4 Historical Data Configuration Object
  Second Collection", "Long Term Configuration", etc. All historical configuration Objects shall be referenced using the HasHistoricalConfiguration ReferenceType . Table 6 - Historical Access configuration definition Attribute Value BrowseName
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.4 HistoricalEventNode Attributes
  HistoricalEventNode Attributes The Attributes of Objects or Views that have importance for historical Events are specified in detail in OPC 10000-3 . The following Attributes are particularly important
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.1 General
  General OPC UA Servers can support several different functionalities and capabilities. The following standard Objects are used to expose these capabilities in a common fashion, and there are several standard ... defined concepts that can be extended by vendors. The Objects are outlined in OPC 10000-1 . Figure 7 - Server and HistoryServer Capabilities
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.1 Overview
  history database by specifying a filter and a time domain for one or more Objects or Views . See 6.5.2.1 . When this parameter is specified, the Server returns a HistoryEvent structure ... history database by specifying a filter and a time domain for one or more Objects or Views . See 6.5.2.1 . When this parameter is specified, the Server returns a HistoryEvent structure
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.1 ReadEventDetails structure details
  structure details Table 29 defines the ReadEventDetails structure. This parameter is only valid for Objects that have the EventNotifier Attribute set to TRUE (see OPC 10000-3 ). At least
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.3 ReadEventDetails2 structure details
  structure can be used for all event retrieval operations. ReadEventDetails2 is only valid for Objects that have the EventNotifier Attribute set to TRUE (see OPC 10000-3 ). At least
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.4.1 ReadProcessedDetails structure details
  also see AggregateConfiguration settings defined in OPC 10000-13 , and as described in HistorianConfiguration Objects (see 5.2.2 ). TreatUncertainAsBad Boolean As described in OPC 10000-13 . PercentDataBad Byte As described
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.2 Directory
  GlobalDiscoveryServer AddressSpace and it is the target of an Organizes reference from the Objects folder defined in OPC 10000-5 . It organizes the information that can be accessed into subfolders
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.3 DirectoryType
  Defined in 6.5.11 . Mandatory Conformance Units GDS Application Directory The Applications folder may contain Objects representing the Applications known to the GDS. These Objects may be organized into subfolders ... various criteria. A GDS is not required to expose its Applications as browsable Objects in its AddressSpace , however, each application shall have a unique NodeId which can be passed
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.1 CertificateGroupType
  CertificateGroupType This ObjectType is used for Objects which represent CertificateGroups in the AddressSpace . A CertificateGroup is a context that contains a TrustList and one or more CertificateTypes that
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.2 CertificateDirectoryType
  requested) are returned . The GetCertificateGroups Method returns a list of NodeIds for CertificateGroupType Objects that can be used to request Certificates or TrustLists for an application. The GetCertificates Method returns
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.1 Overview
  ServerConfiguration Object is used to manage the Server . The ManagedApplications Folder collects ApplicationConfiguration Objects for other applications which the Server is able to manage. For example, a Server may have
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.14 ApplicationConfigurationType
  configuration of another application. A Server acting as a proxy will add the Objects that represent the application it manages to the ManagedApplications Object (see 7.10.16 ). Table 98 - ApplicationConfigurationType Definition ... application. It is described in 8.6 . The AuthorizationServices Folder contains the AuthorizationServiceConfiguration Objects which the application supports. It is described in 9.7 . If ApplicationType is Client then the ApplicationsNames Property
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.2 KeyCredentialConfigurationFolderType
  KeyCredentialConfigurationFolderType This ObjectType is the TypeDefinition for an Folder Object that contains the KeyCredentialConfiguration Objects which may be accessed via the Server . Table 133 - KeyCredentialConfigurationFolderType Definition Attribute Value BrowseName
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.4 KeyCredentialConfiguration
  KeyCredentialConfiguration This Object is an instance of FolderType. It contains The Objects which may be accessed via the Server . It is the target of an HasComponent reference from the ServerConfiguration
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.1 Overview
  Server, such as a GDS , with AuthorizationService Capabilities may support one or more AuthorizationService Objects (see 9.6.4 ) which may represent an internal AuthorizationService or be an API to an external
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  E.3 LDAP
  LDAP LDAP Servers contain objects organized into hierarchies. Each object has an objectClass which specifies a number of attributes . Attributes have values which describe an object . Figure E.3 illustrates
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.1.1 Overview
  Overview OPC UA Servers can support several different functionalities and capabilities. The following standard Objects are used to expose these capabilities in a common fashion, and there are several standard
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.2.2 ReadProcessedDetails structure overview
  read. processingInterval Interval between returned Aggregate values. aggregateType[] The NodeIds of the AggregateFunction Objects . AggregateFunction Objects indicate the list of Aggregates to be used when retrieving processed history. aggregateConfiguration Aggregate
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.2.3 AggregateFilter structure overview
  period to calculate the Aggregate the first time. aggregateType The NodeIds of the AggregateFunction Objects that indicates the list of Aggregates to be used when retrieving processed data. processingInterval
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.1 General
  Information Model for PubSub configuration in Clause 9 specifies the standard Objects in an OPC UA AddressSpace used to create, modify and expose an OPC UA PubSub configuration. Figure
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.1 Overview
  Types overview The PublishSubscribe Object is the root node for all PubSub related configuration Objects . It is an instance of the PubSubKeyServiceType or the PublishSubscribeType and a component
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.2 PublishSubscribe Object
  provide interoperability between Publishers, Subscribers, Security Key Services and configuration tools, all PubSub related Objects shall be exposed through an Object called "PublishSubscribe" that is of the type
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.3.1 PubSubKeyServiceType definition
  concrete type and can be used directly. The SecurityGroups folder organizes the Objects representing the SecurityGroup configuration. The KeyPushTargets folder organizes the Objects representing the PubSubKeyPushTarget configuration
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.5.1 SecurityGroupFolderType definition
  concrete type and can be used directly. Instances of the SecurityGroupFolderType can contain SecurityGroup Objects or other instances of the SecurityGroupFolderType . This can be used to build a tree ... folder Objects used to organize the configured SecurityGroups . The SecurityGroup Objects are added as components to the instance of the SecurityGroupFolderType . A SecurityGroup Object is referenced only from one folder
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.7.1 PubSubKeyPushTargetFolderType definition
  Optional Conformance Units PubSub Model SKS Push Instances of the PubSubKeyPushTargetFolderType can contain PubSubKeyPushTarget Objects or other instances of the PubSubKeyPushTargetFolderType . This can be used to build a tree ... folder Objects used to organize the configured PubSubKeyPushTargets . The PubSubKeyPushTarget Objects are added as components to the instance of the PubSubKeyPushTargetFolderType . A PubSubKeyPushTargets is referenced only from one folder
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.1 General
  PublishSubscribeType with the name PublishSubscribe represents the root Object for all PubSub related Objects . It manages a list of PubSubConnectionType Objects and the PublishedDataSetType Objects through the PublishedDataSets folder ... product-specific configuration tools. The DataSetFolderType can be used to organize the PublishedDataSetType Objects in a tree of folders. Figure 43 shows an example configuration with the root Object PublishSubscribe
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.1 Overview
  Types overview The PublishSubscribe Object is the root node for all PubSub related configuration Objects . It is an instance of the PublishSubscribeType and a component of the Server Object
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.2 PublishSubscribeType
  this ObjectType represents the root Object for all PubSub related configuration and metadata Objects . The one instance of this ObjectType that represents the root Object is defined ... PublishSubscribeType ObjectType is a concrete type and can be used directly. The configured connection Objects are added as components to the instance of the PublishSubscribeType . Connection Objects may be configured
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.5 RemoveConnection Method (Deprecated)
  successful removal of the PubSubConnection Object removes all associated groups, DataSetWriter and DataSetReader Objects . Before the Objects are removed, their state is set to Disabled . The Client should be authorized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.6 CloseAndUpdate Method
  modification is only applied if the all changes can be applied to all objects. ConfigurationReferences References to the PubSub configuration elements in the written file that should be added, modified ... where a name and identifier was assigned. ConfigurationObjects NodeIds of the related Objects to referenced If NodeIds are returned, the length and order of the array shall match the ConfigurationReferences
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.1 DataSetFolderType
  instances of the DataSetFolderType . This can be used to build a tree of Folder Objects used to group the configured PublishedDataSets . The PublishedDataSetType Objects are added as components ... referenced only from one DataSetFolder . If the DataSetFolder is deleted, all referenced PublishedDataSetType Objects are deleted with the folder. PublishedDataSetType Objects may be configured with product-specific configuration tools
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.6 RemovePublishedDataSet Method
  DataSetFolderType Object . A successful removal of the PublishedDataSetType Object removes all associated DataSetWriter Objects . Before the Objects are removed, their state is changed to Disabled . The Client shall be authorized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.8 RemoveDataSetFolder Method
  parent DataSetFolderType Object . A successful removal of the DataSetFolderType Object removes all associated PublishedDataSetType Objects and their associated DataSetWriter Objects . Before the Objects are removed, their state is changed
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.2 PubSubConnectionType
  PubSubConnectionType This ObjectType is a concrete type for Objects representing PubSubConnections . A PubSubConnection is a combination of protocol selection, protocol settings and addressing information. The PubSubConnectionType is formally defined ... present if the transport protocol mapping defines specific parameters. The configured WriterGroup and ReaderGroup Objects are added as components to the instance of the PubSubConnectionType . PubSubGroup Objects may be configured
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.5 RemoveGroup Method (Deprecated)
  connection. A successful removal of the PubSubGroup Object removes all associated DataSetWriter or DataSetReader Objects . Before the Objects are removed, their state is set to Disabled . The Client should
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.8 ConnectionTransportType
  ConnectionTransportType This ObjectType is the abstract base type for Objects representing transport protocol mapping specific settings for PubSubConnections . The ConnectionTransportType is formally defined in Table 272 . Table 272 - ConnectionTransportType definition
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.2 PubSubGroupType
  PubSubGroupType This ObjectType is the abstract base type for Objects representing communication groupings for PubSub connections. The PubSubGroupType is formally defined in Table 275 . Table 275 - PubSubGroupType definition Attribute Value ... state machine for the status and the relation to other PubSub Objects like PubSubConnection , DataSetWriter and DataSetReader are defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.3 WriterGroupType
  Object shall be present if the message mapping defines specific parameters. The configured DataSetWriterType Objects are added as components to the instance of the group. DataSetWriterType Objects may be configured
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.7 WriterGroupTransportType
  WriterGroupTransportType This ObjectType is the abstract base type for Objects representing transport protocol mapping specific settings for WriterGroups . The WriterGroupTransportType is formally defined in Table 280 . Table 280 - WriterGroupTransportType definition
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.8 WriterGroupMessageType
  WriterGroupMessageType This ObjectType is the abstract base type for Objects representing message mapping specific settings for WriterGroups . The WriterGroupMessageType is formally defined in Table 281 . Table 281 - WriterGroupMessageType definition Attribute
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.9 ReaderGroupType
  ReaderGroupType This ObjectType is a concrete type for Objects representing DataSetReader groupings for PubSub connections. The ReaderGroupType is formally defined in Table 282 . Table 282 - ReaderGroupType definition Attribute Value BrowseName ... Deprecated Method described in 9.1.6.11 . Optional Conformance Units PubSub Model Base The configured DataSetReaderType Objects are added as components to the instance of the group. DataSetReaderType Objects may be configured
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.13 ReaderGroupTransportType
  ReaderGroupTransportType This ObjectType is the abstract base type for Objects representing transport protocol mapping specific settings for ReaderGroups . The ReaderGroupTransportType is formally defined in Table 286 . There is currently
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.14 ReaderGroupMessageType
  ReaderGroupMessageType This ObjectType is the abstract base type for Objects representing message mapping specific settings for ReaderGroups . The ReaderGroupMessageType is formally defined in Table 287 . There is currently no message
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.7.3 DataSetWriterTransportType
  DataSetWriterTransportType This ObjectType is the abstract base type for Objects defining protocol-specific transport settings of DataSetMessages . The DataSetWriterTransportType is formally defined Table 289 . Table 289 - DataSetWriterTransportType definition Attribute Value
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.7.4 DataSetWriterMessageType
  DataSetWriterMessageType This ObjectType is the abstract base type for Objects representing message mapping specific settings for DataSetWriters . The DataSetWriterMessageType is formally defined in Table 290 . Table 290 - DataSetWriterMessageType definition Attribute
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.3 DataSetReaderTransportType
  DataSetReaderTransportType This ObjectType is the abstract base type for Objects defining the transport protocol-specific parameters for DataSetReaders . The DataSetReaderTransportType is formally defined in Table 292 . Table 292 - DataSetReaderTransportType definition
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.4 DataSetReaderMessageType
  DataSetReaderMessageType This ObjectType is the abstract base type for Objects representing message mapping specific settings for DataSetReaders . The DataSetReaderMessageType is formally defined in Table 293 . Table 293 - DataSetReaderMessageType definition Attribute
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.4.5 RemoveDataSetFolder Method
  parent SubscribedDataSetFolderType Object . A successful removal of the SubscribedDataSetFolderType Object removes all associated StandaloneSubscribedDataSetType Objects and their associated DataSetReader Objects . Before the Objects are removed, their state is changed
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.2 PubSubDiagnosticsType
  PubSubDiagnosticsType The PubSubDiagnosticsType is the base type for the diagnostics objects and is formally defined in Table 310 . Table 310 - PubSubDiagnosticsType Attribute Value BrowseName PubSubDiagnosticsType IsAbstract True References Node Class ... Error . The SubError Variable indicates if any statistics Object of the next PubSub layer Objects shows a value > 0 in TotalError . The Object Counters contains all diagnostics counters
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.4 DiagnosticsLevel
  help in the discovery of potential faults. Depending on the situation, not all diagnostic Objects might be needed, and on the other hand providing them requires resources. As a result ... diagnostic objects are assigned to different diagnostic levels. Only diagnostic Objects belonging to the currently set diagnostic level or a more severe level shall be provided. This mechanism provides
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.1 General
  General Subclause  6.2 describes the identifiers, types and structure of the Objects and Methods that are used to implement the OPC UA mappers defined in this document. This implementation serves
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  SafetyACSet definition Attribute Value BrowseName SafetyACSet References NodeClass BrowseName Comment OrganizedBy by the Objects Folder defined in OPC 10000-5. HasTypeDefinition ObjectType FolderType Entry point for all SafetyProviders and SafetyConsumers ... received and sent shall be accessible by calling the Method ReadSafetyDiagnostics . Figure 3 - Server Objects for OPC UA Safety NOTE 3 For the input/output arguments of the Methods ReadSafetyData
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.2 Safety ObjectType definitions
  BrowseNames (i.e. name and Namespace ) are used to find Methods , the names of Objects and Properties shall be locally unique. The DataType of both Properties and MethodArguments shall be used
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  SPDUs 5.5 Requirements for CRC calculation RQ6.1 Singleton SafetyACSet Folder 6.2.2.1 SafetyACSet Object RQ6.2 Objects for SafetyProviders and SafetyConsumers 6.2.2.1 SafetyACSet Object RQ6.3a Usage of Call Service for Client/Server
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.9 StateType
  StateType States of a FiniteStateMachine are represented as Objects of the StateType. Each Object of the StateType or one of its subtypes shall be referenced from the ObjectType FiniteStateMachineType
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.11 TransitionType
  TransitionType Transitions of a FiniteStateMachine are represented as Objects of the ObjectType TransitionType formally defined in Table 11 . Each Object of the TransitionType or one of its subtypes shall
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.3 StateMachineType using containment
  also contains a StateMachine "MyStateMachine" of the type "MyStateMachineType". Objects of "MyObjectType" also contain such an Object representing the StateMachine and a Variable containing
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.1 Overview
  Overview The following standard Objects are defined for maintaining the hierarchical structure of AliasNameCategories in a Server . Server vendors are free to add additional instances of AliasNameCategoryType under this hierarchy
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.2 Aliases
  Aliases definition Attribute Value BrowseName Aliases References NodeClass BrowseName DataType TypeDefinition OrganizedBy by the Objects Folder defined in OPC 10000-5 HasTypeDefinition ObjectType AliasNameCategoryType Defined in 6.3 HasProperty Variable LastChange ... VersionTime PropertyType ConformanceUnits AliasName Hierarchy This is the root folder for all alias related Objects . It can contain instances of AliasNameType Objects and / or instances of AliasNameCategoryType Objects . The LastChange
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.3 TagVariables
  AliasNameType instances that contain an AliasFor reference to Variables. It can contain additional AliasNameCategoryType Objects , which could be used to create a hierarchy. A single instance of AliasNameType can exist
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  9.4 Topics
  ObjectType AliasNameCategoryType Defined in 6.3 ConformanceUnits AliasName Category Topics It can contain additional AliasNameCategoryType Objects , which could be used to create a hierarchy or other structure. A single instance
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.2 AliasNames used within a single Server
  Server . This sample includes multiple instances of AliasNameCategoryType . The figure illustrates that Objects could be referenced by more than one instance of AliasNameType . Figure A.1 - AliasNames in a Server example ... describes an information model for a well. This model contains a number of other Objects , which have Variables that are to be available via a standardized naming scheme. The model
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  B.1 Aggregating Server with a collection of Aggregates
  well-known AliasNameCategoryType instances. Some information models could define their own well-known AliasNameCategoryType Objects , which then also shall be merged. An aggregating Server could expose the same AliasName referencing
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  C.2 Register a Server
  shall provide a single merged tree list for any of the well-known AliasNameCategoryType Objects defined in 9.3 (i.e. TagVariables or Topics ). The organization of the actual structure
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.1 General
  possible Permissions and the representation as Node Attributes . Figure 1 depicts the ObjectTypes , Objects and their components used to represent the Role management. Figure 1 - Role management overview
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  5.1 General
  user list in the OPC UA Server. Figure 2 depicts the ObjectTypes , Objects and their components used to represent the user management. The ServerConfiguration Object is defined
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.1 DictionaryEntryType
  Concrete dictionary entry types shall inherit from the abstract DictionaryEntryType defining additional Properties and Objects as necessary and specified by the standard body (e.g. further definitions, versioning information
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.2 DictionaryFolderType
  DictionaryFolderType This ObjectType provides means to structure dictionary entry Objects . Multiple Objects of the DictionaryFolderType can be nested in order to create hierarchies. The DictionaryFolderType is formally defined in Table
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  6.1 HasDictionaryEntry ReferenceType
  Node can be the SourceNode of multiple HasDictionaryEntry References pointing to multiple dictionary entry Objects . The HasDictionaryEntry ReferenceType is specified in Table 5 . Table 5 - HasDictionaryEntry ReferenceType Attributes Value BrowseName
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  9 Examples (Informative)
  Figure 3 - DeviceType Property example The example in Figure 4 shows how OPC UA Objects could refer to classes in the IEC 61987 Common Data Dictionary and OPC UA Properties ... referenced classes Transmitter housing or Transmitter body of the parent OPC UA Objects . Figure 4 - Example with references to classes and properties The example in Figure 5 shows
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.3.1 FileDirectoryType
  Units Base Info FileDirectoryType Base Instances of the ObjectType contain a list of FileDirectoryType Objects representing the subdirectories of the file directory represented by the instance of this ObjectType . Instances ... ObjectType contain a list of FileType Objects representing the files in the file directory represented by the instance of this ObjectType
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.3.2 FileSystem Object
  structure shall have the BrowseName FileSystem . An OPC UA Server may have different FileSystem Objects in the AddressSpace . HasComponent is used to reference a FileSystem from aggregating Objects like ... Objects Folder or the Object representing a device
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.9 DeviceRegistrar
  DeviceRegistrarType defined in 9.2.2 . References Node Class BrowseName DataType TypeDefinition Modelling Rule OrganizedBy the Objects Object defined in OPC 10000-5 . Conformance Units Onboarding Registrar PullManagement
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.3.3 ProvisionableDeviceType
  ProvisionableDeviceType The ProvisionableDeviceType ObjectType defines Objects that support PushManagement described in 7.3 . The ObjectType is defined in Table 33 . Table 33 - ProvisionableDeviceType Definition Attribute Value BrowseName 0:ProvisionableDeviceType IsAbstract False ... which the Device can use to authenticate itself via PullManagement . The :<ApplicationName> Objects defines an API which represents the configuration of an Client or Server running
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.7 IIeeeBaseTsnStreamType Interface
  octet[n] of StreamID. The StreamId shall be provided in the TSN stream Objects for diagnostic reasons. Note: In the distributed configuration model the StreamId is typically generated
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.4.1 Resources Folder
  contain a set of Organizes References that point to other Objects representing specific resources. It is formally defined in Table 50 . Table 50 - Resources definition Attribute Value BrowseName Resources References
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.4.4 NetworkInterfaces Folder
  hold instances, which are of IetfBaseNetworkInterfaceType  or a subtype of it. However other Objects can be stored within this folder that implement the UA Interface IIetfBaseNetworkInterfaceType . All Objects of Type
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.1.1 Virtual Network Interfaces
  A.1.1 Virtual Network Interfaces A virtual interfaces configuration can be represented by Objects representing the virtual and the physical network interface instances. HasLowerLayerInterface References point from the Object(s) representing ... virtual interface(s) to the Object representing the physical interface. All Objects are of ObjectType IetfBaseNetworkInterfaceType . An example is shown in Figure A-1 . Note: The usage of the References
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.1.2 Link Aggregation
  A.1.2 Link Aggregation A link aggregation configuration can be represented by Objects representing the logical aggregation and the particular physical interface instances. HasLowerLayerInterface References point from the Object(s) representing ... aggregation interface to the Objects representing the physical interfaces. All Objects implement the IIetfBaseNetworkInterfaceType . An example is shown in Figure A-2 . Figure A-2 - Modelling example for link aggregation
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.8.1 Overview
  focused view on the port defined by an ObjectType in another companion specification. Both Objects may have distinguished information, but also provide some common information like the IP address, potentially
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.10.1 Overview
  representing the functionality of a drive. The ReferenceType can be used to related both Objects
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  4.11.1 Overview
  results in a non-functional functionality. A functionality Object might relate to several environment Objects , in that case all environment Objects are necessary to execute and run the functionality ... environment Object might be referenced by several functionality Objects . For example, the functionality to move an axis is hosted by the drive moving the axis. Another example is some analog
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  6.1 Overview
  CalendarType represent a globally defined set of dates that can be referenced by schedule Objects ; an instance of ScheduleType represent a schedule, that defines for specific dates or weekdays specific ... specification does not define any specific entry points where to find schedule or calendar Objects . It is expected that they are placed reasonable in the AddressSpace, for example as child
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.4 SerializationScope and SerializationEntity
  also possible (see 6.2 also). The SerializationStartNode refers to one or more SerializationEntity Objects with a HasSerializationEntity ReferenceType . Figure 3 shows the relationship of the SerializationStartNode , the SerializationEntity Object ... SerializationFieldDataType for the Variable is always a Structure DataType (see 6.4.3 ). The SerializationFieldDataType of Objects is the Structure DataType used to represent Objects and the child Nodes of these Objects
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.5 General Features
  Structure of the SerializationScope is preserved. This means that the relationship of the Objects and Variables contributing to the SerializationValue is preserved. Servers can provide different serializations by providing different
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.1 Example Serialize RIO Channel Groups
  Channel Groups OPC UA for PROFINET Remote IO (see [ OPC RIO]) defines Channel Group Objects aggregating the IO Data of subordinated IO Channel Objects and organizing the channel Objects representing ... single IO Channels themselves. Figure 4 shows a Channel Group containing two output channel Objects , a configuration Object and Process Values . Figure 4 - RIO Channel Group From the Clients' perspective
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.2 Example Serialization of PROFIenergy Data
  shown in Figure 5 comprises all MeasurementValueType Variables which are components of the EnergyMeasurementType Objects organized in the "EnergyManagement" Folder Object . The SerializationScope is configured to exclude ... Variable , a Client obtains all measurement values of all subordinated "Metering Point" Objects in one single read operation. This supports time consistency of the collection of measurement values
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.1 Overview
  Object Serialization provides a consistent, compact representation of the Variable Values in the SerializationScope . Objects or Variables that are the root of such a serialization are called SerializationStartNodes and have
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.4 SerializationFieldDataType of Objects with children
  SerializationFieldDataType of Objects with children The rules described above apply in the same way to Objects , with the exception that the Object level itself has no Value and therefore ... Variables with children are created according to chapter 6.4.3 Figure 14 - Serialization of Objects with children
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.3 RIO Channel Process Values
  Process Values Figure A.3 shows how Process Values (see OPC RIO) belonging to RioChannelType Objects are mapped into the SerializationValue DataType . The "SerializationEntity" referenced by the SerializationStartNode directs ... SerializationProcess would stop as soon as a RioChannelType Object is reached, since these Objects only have components referenced using the HasComponent ReferenceType . To include the components of the RioChannelType Objects
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.4 Energy Measurement Values
  Values Figure A.4 shows a SerializationScope configured to exclude the metadata Properties of the Objects and Variables reachable from the SerializationStartNode . The EnergyMeasurementType Object has a mandatory PeObjectNumber Property which
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.5 Semantic Property Metadata in PubSub Scenarios
  shown in A.4 , the SerializationConfiguration excludes the metadata Properties attached to the EnergyMeasurementType Objects as well as to the MeasurementValueType Variables . The metadata can be conveyed to a PubSub Subscriber
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  1 Scope
  versions of this Part. This document provides an Information Model for a set of Objects and Events that can be used to collect diagnostic information in a system. The LogObject
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.1 Overview
  Information Model . This clause conceptually describes the functionality provided in the overview of the Objects defined by the OPC UA FX Information Model
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.1 Overview
  part of the connection. Figure 28 provides a more detailed view of the Objects involved. Logical connections are configured using ConnectionConfigurationSets . The following types of logical connections are supported
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.5 Persistent and preconfigured objects
  Persistent and preconfigured objects Establishing logical connections can involve creating several Objects within the AutomationComponents . Persistence refers to the ability of AutomationComponents to store configuration, which allows these Objects ... marked for persistence (see IsPersistent in 6.6.2 ) . An AutomationComponent can provide preconfigured Objects (e.g., PublishedDataSet or ConnectionEndpoint ). An example might be a FunctionalEntity that includes a preconfigured PublishedDataSet that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.6 Health
  provide general health status and diagnostic conditions. This health status is aggregated from child objects to parent objects (e.g., from ConnectionEndpoints to the FunctionalEntity , from FunctionalEntities to the AutomationComponent ... health status is "good", a Client does not have to check other Objects in the tree. If a status other than "good" is reported, aggregated health
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.7 AliasNames and OPC UA FX
  defined in OPC 10000-17 ) that allows defining alternate names for Objects , Variables or Methods in an AddressSpace (see Figure 15 ). These names can be grouped into categories. The FindAlias ... ConnectionManager . AliasNames allow offline engineering tools to assign alternate names to Variables or Objects that are used in the configuration (see Figure 16 ). These alternate names could be assigned
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  least one entry in this Folder . For examples of Assets , see Annex D . Objects may be added/removed to/from the FunctionalEntities or Assets Folders during operation, in which case the Server
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.9.2 PubSub
  TRUE reference a DataSetReader and/or DataSetWriter which are persisted, including all parent Objects , i.e., WriterGroup , ReaderGroup , PubSubConnection and PublishSubscribe (see NotPersisted in OPC 10000-14 ). If the IsPersistent Property
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.10.1 General
  CommandMask EnableCommunicationCmd is set, the EstablishConnections implementation shall enable all communication model-specific Objects related to the ConnectionEndpoints in an atomic operation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.10.2 PubSub
  ToDataSetWriter References for each element in ConnectionEndpointConfigurations . It shall also ensure that the parent Objects ( WriterGroup , ReaderGroup , PubSubConnection , and PublishSubscribe ) are enabled. If enabling any communication model-specific Objects fails
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.11 Abort
  context of this Method Call shall be deleted. EnableCommunicationCmd All communication configuration Objects that were enabled in the context of this Method Call shall be disabled. The Method shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.5.1 CloseConnections signature
  Argument Description ConnectionEndpoints The list of Connections to be closed. Remove When TRUE, the Objects dynamically created for the Connection are removed. Results The results of closing the Connections identified
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.5.2 CloseConnections behaviour
  CloseConnections behaviour The Method implementation shall disable all communication model Objects for each element in ConnectionEndpoints in an atomic operation. For additional details on ConnectionEndpoints, see 6.6 , and PubSubConnectionEndpoints ... ToDataSetReader and/or ToDataSetWriter References if no further References from other ConnectionEndpoints exist. Their parent Objects ( WriterGroup , ReaderGroup , PubSubConnection , and PublishSubscribe ) shall be left in their current state. The behaviour
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.1 Overview
  other models will subtype the FunctionalEntityType . It can have SubFunctionalEntities and relationships to other Objects defined in this model or other models. A FunctionalEntity may be implemented using the IFunctionalEntityType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.2 FunctionalEntityType definition
  Variables that would exist in InputData , OutputData and ConfigurationData . The subtypes might also add Objects and Methods or define nested FunctionalEntityType instances. In addition, the information in the FunctionalEntityType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.2 ControlGroupType definition
  ControlGroups may result in a restriction on the grouped items. The restriction can include Objects (input and configuration Variables ) and Method invocations. The restriction can block all changes to Variables ... part of the ControlGroup that are not blocked or restricted (i.e., it is Objects , Variables , Methods ). A Variable , Method or Object shall not be included in more than
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.4 ReleaseControl method
  This Method Call shall release the ControlGroup and issue a Call to the Lock Objects in each Folder for the ExitLock Method (see OPC 10000-100 ). It shall create
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.2 ConnectionEndpointType definition
  persistent ConnectionEndpoint shall include: ConnectionEndpoint including references to ControlGroups and communication model Objects Established control on related ControlGroups Communication model Objects An AutomationComponent indicates support for persistent Connections ; see SupportsPersistence
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  Method provides several commands (see 10.23 ) to verify and create the individual Information Model Objects related to a Connection . Figure 36 illustrates the sequence of commands to a single AutomationComponent