Search

200 result(s) for Object

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.27 Object
  Object Node that represents a physical or abstract element of a system Note 1 to entry: Objects are modelled using the OPC UA Object Model. Systems, subsystems, and devices ... examples of Objects. An Object may be defined as an instance of an ObjectType
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.20 Method
  Method callable software function that is a component of an Object
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.3 Integrated object model
  Integrated object model The OPC UA Object Model provides a consistent, integrated set of NodeClasses for representing Objects in the AddressSpace . This model represents Objects in terms of their Variables ... 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
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.8 Method Service Set
  defines the means to invoke Methods . A Method is always a component of an Object . Discovery is provided through the browse Services . Clients discover the Methods supported by a Server
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.11 Interface
  used to specify a feature or feature-set that shall be implemented by the Object or ObjectType where it is applied
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.3 DataVariables
  DataVariables DataVariables represent the content of an Object . For example, a file Object may be defined that contains a stream of bytes. The stream of bytes may be defined ... Properties may be used to expose the creation time and owner of the file Object . For example, if a DataVariable is defined by a data structure that contains two fields
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  represented as a DataVariable in the AddressSpace . This DataVariable is part of an Object not shown in the figure. To provide for a common setpoint definition that can be used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.1 General
  Server that supports eventing shall expose at least one Node as EventNotifier . The Server Object defined in OPC 10000-5 is used for this purpose. Events generated by the Server ... available via this Server Object . A Server is not expected to produce Events if the connection to the event source is down for some reason (i.e. the system is offline
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.8 Methods
  lightweight" functions, whose scope is bounded by an owning (see Note) Object , similar to the methods of a class in object-oriented programming or an owning ObjectType , similar ... client calls the Method and ends when the result is returned. NOTE The owning Object or ObjectType is specified in the service call when invoking the Method . While Methods
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.9.3 Evaluating Permissions with Roles
  they are not set the Server returns Bad_UserAccessDenied . Roles appear under the Roles Object in the Server Address Space . Each Role has mapping rules defined which appear as Properties ... Role Object (see OPC 10000-5 ). The examples shown in Table 3 illustrate how the standard mapping rules can be used to determine which Roles a Session has access
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  Interface model specifies the rules and mechanisms to achieve this. The " InterfaceTypes " Object (see OPC 10000-5 ) has been defined so that all Interfaces of the Server ... Interface if it was already applied to a super-type. When an Object references an Interface with a HasInterface Reference or a subtype, the following rules apply: The Interface shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.3 AddIn model
  associate a feature or feature-set, represented by an ObjectType to the Node (an Object or ObjectType ) they are applied to. The Interface model is different than the AddIn model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.9 RolePermissions
  Structure Specifies the Permissions for a Role roleId NodeId The NodeId of the Role Object . permissions PermissionType A mask specifying which Permissions are available to the Role . See 8.55 Servers ... RolePermissions Attribute . If not specified, the value of DefaultRolePermissions Property from the NamespaceMetadata Object associated with the Node shall be used instead. If the NamespaceMetadata Object does not define
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.10 UserRolePermissions
  Node . If not specified, the value of DefaultUserRolePermissions Property from the Namespace Metadata Object associated with the Node is used instead. If the NamespaceMetadata Object does not define the Property
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.11 AccessRestrictions
  supports AccessRestrictions for a particular Namespace it adds the DefaultAccessRestrictions Property to the NamespaceMetadata Object for that Namespace (see Figure 14 ). If a particular Node in the Namespace needs ... model for a Namespace, it does not add the DefaultAccessRestrictions Property to the NamespaceMetadata Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.3 HasSubtype References
  That is, if a ReferenceType "A" is not allowed to relate an Object with an ObjectType , this is also true for its subtypes. A ReferenceType shall have exactly
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  with Views for filtering purposes can, for example, handle a View Node like an Object of type FolderType (see 5.5.3 ). Table 10 - View NodeClass Name Use Data Type Description Attributes ... Events . A View that supports Events shall provide all Events that occur in any Object used as EventNotifier that is part of the content of the View . In addition
• 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 ... 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 0..1 Objects
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  contained in the ObjectType . If and how the referenced Nodes are instantiated when an Object of this type is instantiated, is specified in 6.4 . HasProperty 0..* HasProperty References identify ... Properties of the ObjectType . If and how the Properties are instantiated when an Object of this type is instantiated, is specified in 6.4 . HasSubtype 0..* HasSubtype References identify ObjectTypes that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.3 Standard ObjectType FolderType
  ReferenceType . The SourceNode of such a Reference should always be a View or an Object of the ObjectType FolderType ; the TargetNode can be of any NodeClass . Organizes References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.4 Client-side creation of Objects of an ObjectType
  Service defined in OPC 10000-4 . The Service requires specifying the TypeDefinitionNode of the Object . An Object created by the AddNodes Service contains all components defined by its ObjectType dependent ... components. However, the Server may add additional components and References to the Object and its components that are not defined by the ObjectType . This behaviour is Server dependent. The ObjectType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  unknown. References HasModellingRule 0..1 Variables can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). HasProperty 0..* HasProperty References are used ... ModellingRule , a Variable can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . If the Variable is created based on an InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  DataVariable DataVariables represent the content of an Object . DataVariables are defined using the Variable NodeClass , specified in Table 13 . DataVariables identify their Properties using HasProperty References . Complex DataVariables use HasComponent ... Clause 7 . A DataVariable is intended to be defined in the context of an Object . However, complex DataVariables may expose other DataVariables , and ObjectTypes and complex VariableTypes may also contain
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Method . HasModellingRule 0..1 Methods can point to at most one ModellingRule Object using a HasModellingRule Reference (see 6.4.4 for details on ModellingRules ). GeneratesEvent 0..* GeneratesEvent References identify the type ... ModellingRule , a Method can use at most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . GeneratesEvent References identify that Methods may generate an Event
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  AddressSpace to describe the structure of a DataType . The DataType points to an Object of type DataTypeEncodingType . Each DataType can have several DataTypeEncoding , for example "Default
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  HasEncoding Reference . Each concrete Structured DataType shall point to at least one DataTypeEncoding Object with the BrowseName "Default Binary" or "Default XML" having the NamespaceIndex ... permitted for two DataType Nodes to point to the same DataTypeEncoding Object using HasEncoding References . The DataTypeEncoding Node shall provide the inverse HasEncoding Reference to its DataType . An abstract DataType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.2 DataTypeRefinement Objects
  DataTypeRefinement Objects A DataTypeRefinement is represented by an Object of DataTypeRefinementType (see OPC 10000-5 ) or a subtype. A DataTypeRefinement Object shall always be referenced using a HasDataTypeRefinement Reference ... Client when performing an equality check with a field name. A DataTypeRefinement Object shall not reference any Node with a HasFieldDescription or subtype which is not representing a field
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.3 Usage of DataTypeRefinements
  Usage of DataTypeRefinements Each DataTypeRefinement Object shall be referenced from exactly one DataType Node using HasDataTypeRefinement or a subtype. DataTypeRefinements are expressed in an OPC UA information model, by using ... instance of a Variable , where the Structured DataType is used. They point to an Object of DataTypeRefinementType or a subtype, which contains the restrictions and meta data of the DataTypeRefinement
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  subset of all subtypes of a DataType . It is represented by an Object of SubtypeRestrictionType defined in OPC 10000-5 . A SubtypeRestriction Object is bound to a DataType ... HasDataTypeRefinement Reference from the DataType to the SubtypeRestriction Object . Each SubtypeRestriction Object shall be referenced from exactly one DataType Node using a HasDataTypeRefinement Reference . A SubtypeRestriction Object is referencing Variables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.1 InstanceDeclaration
  InstanceDeclaration An InstanceDeclaration is an Object , Variable or Method that references a ModellingRule with a HasModellingRule Reference and is the TargetNode of a hierarchical Reference from a TypeDefinitionNode or another
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  TypeDefinitionNode it shall create the same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . Standard ModellingRules are defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  OptionalPlaceholder For Object and Variable the intention of the ModellingRule OptionalPlaceholder is to expose the information that a complex TypeDefinition expects from instances of the TypeDefinition to add instances with
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.5 MandatoryPlaceholder
  MandatoryPlaceholder For Object and Variable the ModellingRule MandatoryPlaceholder has a similar intention as the ModellingRule OptionalPlaceholder . It exposes the information that a TypeDefinition expects of instances of the TypeDefinition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.7 HasComponent ReferenceType
  SourceNode is deleted. The TargetNode of this ReferenceType shall be a Variable , an Object or a Method . If the TargetNode is a Variable , the SourceNode shall be an Object ... HasComponent Reference , the Variable is defined as DataVariable . If the TargetNode is an Object or a Method , the SourceNode shall be an Object or ObjectType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.11 Organizes ReferenceType
  looping Aggregates References . The SourceNode of References of this type shall be an Object , ObjectType or a View. If it is an Object then it should be an Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.12 HasModellingRule ReferenceType
  NonHierarchicalReferences . The semantic of this ReferenceType is to bind the ModellingRule to an Object , Variable or Method . The ModellingRule mechanisms are described in 6.4.4 . The SourceNode of this ReferenceType shall ... Object , Variable or Method . The TargetNode shall be an Object of the ObjectType "ModellingRule" or one of its subtypes. Each Node shall be the SourceNode of at most
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.13 HasTypeDefinition ReferenceType
  subtype of NonHierarchicalReferences. The semantic of this ReferenceType is to bind an Object or Variable to its ObjectType or VariableType , respectively . The relationships between types and instances are described ... SourceNode of this ReferenceType shall be an Object or Variable . If the SourceNode is an Object , then the TargetNode shall be an ObjectType ; if the SourceNode is a Variable , then
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.14 HasEncoding ReferenceType
  subtype of the Structure DataType . The TargetNode of this ReferenceType shall be an Object of the ObjectType DataTypeEncodingType or one of its subtypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.17 HasEventSource
  notifying Nodes . In particular, the root notifier of a Server , the Server Object defined in OPC 10000-5 , is always capable of supplying all Events from a Server ... every event source in a Server . The SourceNode of this ReferenceType shall be an Object or View that is a source of Event Subscriptions . A source of Event Subscriptions
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.18 HasNotifier
  subtype of HasEventSource . The semantic of this ReferenceType is to relate Object Nodes that are notifiers with other notifier Object Nodes . The ReferenceType is used to establish a hierarchical organization ... this example an unfiltered Event subscription directed to the "Pump" Object will provide the Event sources "Start" and "Stop" to the subscriber. An unfiltered
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.19 HasInterface ReferenceType
  Interface concept is described in 4.10.2 . The SourceNode of this ReferenceType shall be an Object or ObjectType . Interfaces shall not be a SourceNode . The TargetNode shall be of a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.20 HasAddIn ReferenceType
  AddIn concept is described in 4.10.3 . The SourceNode of this ReferenceType shall be an Object or ObjectType . The TargetNode shall be an Object . One SourceNode can refer to multiple AddIns
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.24 UsesDataTypeRefinement
  link from a place where a Structured DataType is used to an Object of DataTypeRefinementType SubtypeRestrictionType (see OPC 10000-5 ), restricting the usage of the Structured DataType and adding meta ... most one UsesDataTypeRefinement Reference . The TargetNode of this ReferenceType shall be an Object of DataTypeRefinementType SubtypeRestrictionType (see OPC 10000-5 ) or a subtype. The DataType of the SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.25 HasFieldDescription
  subtype of HierarchicalReferences . The semantic of this ReferenceType is to link from a DataTypeRefinement Object refining a Structured DataType to a Variable representing a field of that Structured DataType , containing ... usage of the field. The SourceNode of References of this type shall be an Object of DataTypeRefinementType or a subtype. The TargetNode of this ReferenceType shall be a Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.28 UsesSubtypeRestriction
  NonHierarchicalReferences . The semantic of this ReferenceType is to link from a Variable to an Object of SubtypeRestrictionType , restricting the usage of subtypes on values of the Variable . The SourceNode ... most one UsesSubtypeRestriction Reference . The TargetNode of this ReferenceType shall be an Object of SubtypeRestrictionType or a subtype. The DataType of the SourceNode and the DataType restricted in the TargetNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.29 AllowedSubtype
  subtype of HierarchicalReferences . The semantic of this ReferenceType is to link from a SubtypeRestriction Object to a Variable defining one allowed subtype. The SourceNode of References of this type shall ... Object of SubtypeRestrictionType (see OPC 10000-5 ) or a subtype. The TargetNode of this ReferenceType shall be a Variable of BaseDataVariableType or a subtype. The DataType, ValueRank and ArrayDimensions
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.2 NamespaceIndex
  same underlying system to use the same identifier to identify the same Object . This enables Clients that connect to those Servers to recognise Objects that they have in common. Namespace ... into the NamespaceArray . The NamespaceArray is a Variable that is part of the Server Object in the AddressSpace (see OPC 10000-5 for its definition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  Client is allowed to call the Method if this bit is set on the Object or ObjectType Node passed in the Call request and the Method Instance associated with that ... Object or ObjectType . This bit affects the UserExecutable Attribute when set on Method Node . This Permission is only valid for Objects, ObjectType or Methods . AddReference 13 The Client is allowed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.58 AccessLevelExType
  changes in its Value trigger changes to the ConfigurationVersion Property of the NamespaceMetadata Object for the Namespace of the Variable . When this Field is 0 the Value of the Variable ... ConfigurationVersion Property (and the ConfigurationVersion Property shall be provided along with the parent NamespaceMetadata Object for the Namespace of the Variable ). Table 41 defines the combinations of Constant and NonVolatile
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.3 Views
  Therefore the only Notifiers which report the ModelChangeEvents are View Nodes and the Server Object representing the default View . Each action generating a ModelChangeEvent may lead to several Events since
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.6 GeneralModelChangeEventType
  Node , delete a Node , etc.). If the affected Node is a Variable or Object , then the TypeDefinitionNode is also present. To allow Event compression, a GeneralModelChangeEvent contains an array
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.33.1 General
  Node owning the Property that was changed. If this is a Variable or Object , the TypeDefinitionNode is also present. The SemanticChange bit of the AccessLevel Attribute of a Property indicates
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.6 Methods
  parameters. Global Methods , that is, Methods that cannot directly be assigned to a special Object , should be assigned to the Server Object defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.2 Simple notation
  Table C.1 - Notation of Nodes depending on the NodeClass NodeClass Graphical Representation Comment Object Rectangle including text representing the string-part of the DisplayName of the Object . The font shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  representation of a Node . Instead of using the HasTypeDefinition reference to point from an Object or Variable to its ObjectType or VariableType the name of the TypeDefinition can be added
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.1 Description
  TypeDefinitionNode it shall create the same hierarchy of Node s beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration . All Nodes with a ModellingRule of Mandatory
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  Node to add. This parameter shall be null for all NodeClasses other than Object and Variable in which case it shall be provided. If the server Index indicates that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.2 Parameters
  Session . Servers specify a max history continuation points per Session in the Server capabilities Object defined in OPC 10000-5 . A continuation point shall remain active until the Client passes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.1 Overview
  defines the means to invoke Methods . A Method shall be a component of an Object . Discovery is provided through the Browse and Query Services . Clients discover the Methods supported
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.2 Parameters
  with the following indented items. objectId NodeId The NodeId shall be that of the Object or ObjectType on which the Method is invoked. In case of an Object, the Object ... ObjectType of the Object or a super type of that ObjectType shall be the source of a HasComponent Reference (or subtype of HasComponent Reference ) to the Method specified in methodId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.4 StatusCodes
  this result code. Used to indicate that the specified objectId is not an Object or ObjectType . Bad_NodeIdUnknown See Table 179 for the description of this result code. Used ... MethodInvalid The method id does not refer to a Method for the specified Object . Bad_NoCommunication See Table 179 for the description of this result code. Bad_NotSupported See Table
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.2 Sampling interval
  determined by the Server . It returns this assigned interval to the Client . The ServerCapabilities Object defined in OPC 10000-5 identifies the minimum sampling interval supported by the Server ... sampling intervals, the intervals can be exposed using the SamplingIntervalDiagnosticsArray in the ServerDiagnostics Object defined in OPC 10000-5 . The Server may support data that is collected based
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.1 Description
  items operating normally that should not be interrupted. To resolve this situation, the Server Object provides a Method GetMonitoredItems that returns the list of Server and client handles
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.4 Server Failover modes
  Server Failover modes The Failover mode of a Server is provided in the ServerRedundancy Object defined in OPC 10000-5 . The different Failover modes for non-transparent Redundancy are described
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.5.1 General
  RedundantServerSet . The list is provided together with the Failover mode in the ServerRedundancy Object defined in OPC 10000-5 . To enable Clients to connect to all Servers in the list
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.7 Re-establishing connections
  each MonitoredItem . The data should be sent in the next regular PublishingInterval . The Server Object provides a Method ResendData that initiates resending of all data monitored items in a Subscription
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.1 Overview
  element. Literal Specifies a literal value. Attribute Specifies any Attribute of an Object or Variable Node using a Node in the type system and relative path constructed from ReferenceTypes ... BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition and a relative path constructed from BrowseNames
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  whenever all ReferenceTypes in the RelativePath are subtypes of HierarchicalReferences and the targets are Object or Variable Nodes and an Alias is not required . Table 129 defines the SimpleAttributeOperand type ... HierarchicalReferences ReferenceType . All Nodes followed by the browsePath shall be of the NodeClass Object or Variable . If this list is empty the Node is the instance of the TypeDefinition . attributeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.9 ContinuationPoint
  Session . Servers specify a maximum number of ContinuationPoints per Session in the ServerCapabilities Object defined in OPC 10000-5 . ContinuationPoints remain active until the Client retrieves the remaining results ... maximum number of ContinuationPoints per Session defined for the Service in the ServerCapabilities Object defined in OPC 10000-5 . A Client restarts an operation by passing the ContinuationPoint back
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.16 ExpandedNodeId
  Servers have indexes greater than 0. The Server table is contained in the Server Object in the AddressSpace (see OPC 10000-3 and OPC 10000-5 ). The Client may read
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.3 EventFilter
  evaluate the SimpleAttributeOperand.browsePath without considering the SimpleAttributeOperand.typeDefinitionId . Each InstanceDeclaration in the path shall be Object or Variable Node . The final Node in the path may be an Object Node ; however ... Object Nodes are only available for Events which are visible in the Server's AddressSpace . The SimpleAttributeOperand structure allows the Client to specify any Attribute ; however, the Server is only
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.4 AggregateFilter
  samplingInterval of the MonitoringParameters (see 7.21 ). aggregateType NodeId The NodeId of the AggregateFunctionType Object that indicates the Aggregate to be used when retrieving processed data ... This parameter allows Clients to override the Aggregate configuration settings supplied by the AggregateConfiguration Object on a per monitored item basis. See OPC 10000-13 for more information on Aggregate
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.1 Overview
  Table 149 - NodeAttributes parameterTypeIds Symbolic Id Description ObjectAttributes Defines the Attributes for the Object NodeClass . VariableAttributes Defines the Attributes for the Variable NodeClass . MethodAttributes Defines the Attributes for the Method
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.2 ObjectAttributes parameter
  parameter. Table 151 - ObjectAttributes Name Type Description ObjectAttributes structure Defines the Attributes for the Object NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.29 ReferenceDescription
  Type definition NodeId of the TargetNode . Type definitions are only available for the NodeClasses Object and Variable . For all other NodeClasses a null NodeId shall be returned. If the server
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.38.2 Common StatusCodes
  valid StatusCodes for the service. Bad_InvalidState The operation cannot be completed because the object is closed, uninitialized or in some other invalid state. Bad_InvalidTimestamp The timestamp is outside ... NotWritable The access level does not allow writing to the Node . Bad_ObjectDeleted The Object cannot be used because it has been deleted. Bad_OutOfRange The value
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  have type References , but the References are omitted for simplicity. The name of the Object is provided in the box and a numeric instance NodeId in brackets. Standard ReferenceTypes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object . If the NodeId of a DataType is provided, the symbolic name of the Node representing ... referenced Node , only applicable for Variables and Objects . Referenced ModellingRule of the referenced Object . NOTE Notes referencing footnotes of the table content. Conformance Units Name of conformance unit
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  4.1 NodeIds
  InstanceDeclarations would be identified as "ServerType.ServerCapabilities". Since this Object is complex, another InstanceDeclaration of the ServerType is "ServerType.ServerCapabilities.MinSupportedSampleRate". The Server Object defined in 8.3.2 is based
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.1 General
  ObjectType are fixed and can be extended by subtyping. However, since each Object of an ObjectType can be extended with additional components, this standard allows extending the standard ObjectTypes defined ... additional information in the type definition that would already be contained in each Object . Some ObjectTypes already provide entry points for server-specific extensions. However, it is not allowed
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.2 BaseObjectType
  BaseObjectType The BaseObjectType is used as type definition whenever there is an Object having no more concrete type definitions available. Servers should avoid using this ObjectType and use a more
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.1 ServerType
  Mandatory HasProperty Variable EstimatedReturnTime DateTime PropertyType Optional HasProperty Variable LocalTime TimeZoneDataType PropertyType Optional HasComponent Object ServerCapabilities 1 - ServerCapabilitiesType Mandatory HasComponent Object ServerDiagnostics 1 - ServerDiagnosticsType Mandatory HasComponent Object VendorServerInfo - VendorServerInfoType Mandatory ... HasComponent Object ServerRedundancy 1 - ServerRedundancyType Mandatory HasComponent Object Namespaces - NamespacesType Optional HasComponent Method GetMonitoredItems Defined in 9.1 Optional HasComponent Method ResendData Defined in 9.2 Optional HasComponent Method SetSubscriptionDurable Defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.2 ServerCapabilitiesType
  Optional HasProperty Variable MaxStringLength UInt32 PropertyType Optional HasProperty Variable MaxByteStringLength UInt32 PropertyType Optional HasComponent Object OperationLimits -- OperationLimitsType Optional HasComponent Object ModellingRules -- FolderType Mandatory HasComponent Object AggregateFunctions -- FolderType Mandatory HasComponent Object ... ModellingRules supported by the Server should be able to be browsed starting from this Object . AggregateFunctions is an entry point to browse to all AggregateFunctions supported by the Server
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.4 SessionsDiagnosticsSummaryType
  HasComponent Variable SessionDiagnosticsArray SessionDiagnosticsDataType[] SessionDiagnosticsArrayType Mandatory HasComponent Variable SessionSecurityDiagnosticsArray SessionSecurityDiagnosticsDataType[] SessionSecurityDiagnosticsArrayType Mandatory HasComponent Object <ClientName> -- SessionDiagnosticsObjectType Optional Placeholder Conformance Units Base Info ServerType SessionDiagnosticsArray provides an array with ... only to authorised users over encrypted channels. For each session of the Server , this Object also provides an Object representing the session, indicated by <ClientName> . The BrowseName could
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.6 VendorServerInfoType
  VendorServerInfoType This ObjectType defines a placeholder Object for vendor-specific information about the OPC UA Server . This ObjectType defines an empty ObjectType that has no components. It should be subtyped
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  provided by the Server . It is formally defined in Table 22 . Instances of this Object allow Servers to provide more information like version information in addition to the namespace ... Mandatory HasProperty Variable StaticNumericNodeIdRange NumericRange[] PropertyType Mandatory HasProperty Variable StaticStringNodeIdPattern String PropertyType Mandatory HasComponent Object NamespaceFile - AddressSpaceFileType Optional HasProperty Variable DefaultRolePermissions RolePermissionType[] PropertyType Optional HasProperty Variable DefaultUserRolePermissions RolePermissionType[] PropertyType Optional
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.14 NamespacesType
  BrowseName Data Type TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in 6.2 HasComponent Object <NamespaceIdentifier> - NamespaceMetadataType OptionalPlaceholder Conformance Units Base Info ServerType The ObjectType contains a list ... NamespaceMetadataType Objects representing the namespaces in the Server . The BrowseName of an Object shall be derived from the namespace represented by the Object . This can, for example, be done
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.5 AuditChannelEventType
  SourceNode Property for Events of this type shall be assigned to the Server Object . The SourceName for Events of this type shall be "SecureChannel/" and the Service that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.7 AuditSessionEventType
  TransferSubscriptions Service call, the SourceNode Property shall be assigned to the SessionDiagnostics Object that represents the session. The SourceName for Events of this type shall be "Session/TransferSubscriptions". Otherwise ... SourceNode Property for Events of this type shall be assigned to the Server Object . The SourceName for Events of this type shall be "Session/" and the Service
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.19 AuditNodeManagementEventType
  SourceNode Property for Events of this type shall be assigned to the Server Object . The SourceName for Events of this type shall be "NodeManagement/" and the Service that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.27 AuditUpdateMethodEventType
  Property for Events of this type shall be assigned to the NodeId of the Object that the Method resides on. The SourceName for Events of this type shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.31 BaseModelChangeEventType
  context, the SourceNode Property is set to the NodeId of the Server Object . The SourceName for Events of this type shall be the String part of the BrowseName
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.33 SemanticChangeEventType
  context, the SourceNode Property is set to the NodeId of the Server Object . The SourceName for Events of this type shall be the String part of the BrowseName
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.34 EventQueueOverflowEventType
  Events of this type shall be assigned to the NodeId of the Server Object . The SourceName for Events of this type shall be "Internal/EventQueueOverflow
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.35 ProgressEventType
  Events of this type shall be assigned to the NodeId of the Session Object where the operation was initiated. The SourceName for Events of this type shall be "Service
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.36 AuditClientEventType
  Property for Events of this type shall be assigned to the NodeId of the Object that is related to the action. If no Object is related, then the SourceNode Property ... shall be the NodeId of the Server Object . ServerUri provides the URI of the Server that the Client was accessing
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.37 AuditClientUpdateMethodResultEventType
  generate several Events of this type, one per Method called. ObjectId identifies the Object on which the Method was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.10 OrderedListType
  BaseObjectType defined in 6.2 i.e. inheriting the InstanceDeclarations of that Node. HasOrderedComponent Object <OrderedObject> BaseObjectType OP HasProperty Variable NodeVersion String PropertyType O GeneratesEvent ObjectType 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 to the Objects
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.11 IOrderedObjectType Definition
  Conformance Units Base Info OrderedList The mandatory Property NumberInList provides the position of the Object in a list, managed by an instance of the OrderedListType . Ideally, the numbering should start
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.12 DataTypeRefinementType definition
  represent a DataTypeRefinement and are given a unique name. Each BrowseName of a DataTypeRefinement Object shall be unique, i.e., there shall not be two DataTypeRefinement Objects ... Variable <FieldDescription> BaseDataType{Any} BaseDataVariableType MP Conformance Units Base Info DataTypeRefinement Each Object of DataTypeRefinementType shall have at least one Variable referenced with HasFieldDescription or a subtype
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.13 SubtypeRestrictionType definition
  represent a SubtypeRestriction and are given a unique name. Each BrowseName of a SubtypeRestriction Object shall be unique, i.e., there shall not be two SubtypeRestriction Objects ... Variable <FieldDescription> BaseDataType{Any} BaseDataVariableType MP Conformance Units Base Info SubtypeRestriction Each Object of SubtypeRestrictionType shall have at least one Variable referenced with AllowedSubtype or a subtype
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.2 Root
  Root This standard Object is the browse entry point for the AddressSpace . It contains a set of Organizes References that point to the other standard Objects . The " Root ... Object shall not reference any other NodeClasses . It is formally defined in Table 100 . Table 100 - Root definition Attribute Value BrowseName Root References NodeClass BrowseName Comment HasTypeDefinition ObjectType FolderType Defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 Views
  Views This standard Object is the browse entry point for Views . Only Organizes References are used to relate View Nodes to the " Views " standard Object . All View Nodes ... referenced by this Node , either directly or indirectly. That is, the " Views " Object may reference other Objects using Organizes References. Those Objects may reference additional Views . Figure
• 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
  Types This standard Object Node is the browse entry point for type Nodes . Figure 1 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects ... Types " standard Object . The " Types " Object shall not reference any other NodeClasses . It is formally defined in Table 103 . Table 103 - Types definition Attribute Value BrowseName Types
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.6 ObjectTypes
  ObjectTypes This standard Object Node is the browse entry point for ObjectType Nodes . Figure 4 illustrates the structure beneath this Node showing some of the standard ObjectTypes defined in Clause ... References are used to relate Objects and ObjectTypes to the " ObjectTypes " standard Object . The " ObjectTypes " Object shall not reference any other NodeClasses . Figure 4 - ObjectTypes organization
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.7 VariableTypes
  VariableTypes This standard Object is the browse entry point for VariableType Nodes . Figure 5 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects and VariableTypes ... VariableTypes " standard Object . The " VariableTypes " Object shall not reference any other NodeClasses . Figure 5 - VariableTypes organization The intent of the " VariableTypes " Object is that
• 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-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.9 DataTypes
  DataTypes This standard Object is the browse entry point for DataTypes that the Server wishes to expose in the AddressSpace . DataType Nodes should be made available using Organizes References pointing ... either directly from the "DataTypes" Object to the DataType Nodes or using 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
  EventTypes This standard Object Node is the browse entry point for EventType Nodes . Figure 7 illustrates the structure beneath this Node showing some of the standard EventTypes defined in Clause ... References are used to relate Objects and ObjectTypes to the " EventTypes " standard Object . The " EventTypes " Object shall not reference any other NodeClasses . Figure 7 - EventTypes organization
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.11 InterfaceTypes
  InterfaceTypes This standard Object Node is the browse entry point for ObjectType Nodes that represent Interfaces . Figure 8 illustrates the structure beneath this Node showing some of the standard ObjectTypes ... References are used to relate Objects and Interfaces to the " InterfaceTypes " standard Object . The " InterfaceTypes " Object shall not reference any other NodeClasses . Figure 8 - InterfaceTypes Organization
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.12 Locations
  Locations This standard Object is the browse entry point for Object Nodes which represent different types of locations. Figure 9 illustrates the structure beneath this Node . Only Organizes References ... relate Objects . Figure 9 - Locations organization The intent of the " Locations " Object is an entry point for different types of locations. The types of locations organize locations
• 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 ... overview of the containing Objects and Variables of the diagnostic information of the Server Object and where the information can be found. The SessionsDiagnosticsSummary Object contains one Object per session
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.3.2 Server Object
  Server Object This Object is used as the browse entry point for information about the Server . The content of this Object is already defined by its type definition ... formally defined in Table 111 . The Server Object serves as root notifier, that is, its EventNotifier Attribute shall be set providing Events . All Events of the Server shall be accessible
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.16 ModelChangeStructureDataType
  changed as described by the verb . affectedType NodeId If the affected Node was an Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node . Otherwise
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.17 SemanticChangeStructureDataType
  owns the Property that has changed. affectedType NodeId If the affected Node was an Object or Variable , affectedType contains the NodeId of the TypeDefinitionNode of the affected Node . Otherwise
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.36 UABinaryFileDataType
  base type for the UABinaryFileDataType Structure . If the file is provided through a FileType Object , the MimeType Property of the Object shall have the value application/opcua+uabinary. If the file
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.1 Overview
  needs. The following subclauses describe the design decisions made while modelling the Server Object . General DataTypes , VariableTypes and ObjectTypes such as the EventTypes described in this standard are not taken
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.2 ServerType and Server Object
  ServerType and Server Object The first decision is to decide at what level types are needed. Typically, each Server will provide one Server Object with a well-known NodeId ... AddressSpace . Therefore, it is very helpful to have a type definition for the Server Object . The Server Object is an Object , because it groups a set of Variables and Objects
• 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.4 Properties versus DataVariables
  provided, Properties are used. Examples of Properties are the NamespaceArray of the Server Object and the MinSupportedSampleRate of the ServerCapabilities Object . If complex data structures are used, DataVariables are used ... Examples of DataVariables are the ServerStatus of the Server Object and the ServerDiagnosticsSummary of the ServerDiagnostics Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.5 Complex Variables using complex DataTypes
  once in a transactional context. For example, the ServerStatus Variable of the Server Object is modelled as a complex DataVariable having the ServerStatusDataType providing all information about the Server status
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.7 Redundant information
  provided in two different locations. One location is the SubscriptionDiagnosticsArray of the ServerDiagnostics Object , providing the information for all subscriptions of the Server . The second location is the SubscriptionDiagnosticsArray ... each individual SessionDiagnosticsObject Object , providing only the subscriptions of the session. This is useful because some clients may be interested in only the subscriptions grouped by sessions, whereas other clients
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.10 Extensibility mechanism
  additional information.Use a subtype of the VendorServerInfoType to add server-specific information. Because an Object of this type is already defined in this part, clients will look there for server
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.8 ExtensionObject
  DataType . The DataEncodings available for any given Structured DataTypes are represented as a DataTypeEncoding Object in the Server AddressSpace . The NodeId for the DataTypeEncoding Object is the identifier stored
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.3.3 Enumerations
  enumeration value="Unspecified_0" /> <xs:enumeration value="Object_1" /> <xs:enumeration value="Variable_2" /> <xs:enumeration value ... this case, the corresponding numeric value is placed in the Variant (e.g. NodeClass Object would be stored
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.7 UAInstance
  described in detail below. Table F.6 - UANodeSet Instance Nodes Subtype Description UAObject Defines an Object Node as described in OPC 10000-3 . UAVariable Defines a Variable Node as described
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.9 UAMethod
  Method Nodes that are a target of a HasComponent reference from a single Object Node . It is the NodeId of the UAMethod with the same BrowseName contained in the TypeDefinition ... associated with the Object Node . If the TypeDefinition overrides a Method inherited from a base ObjectType then this attribute shall reference the Method Node in the subtype. Executable Boolean Indicates
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.15 Example
  /Definition> </UADataType> This Node is an instance of an Object TypeDefinition Node defined in another InformationModel (ns=2;i=341). It has a single Property which
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.4 Address Space model
  themselves. A simple example of a container for DataItems would be a "Folder Object" but it can be an Object of any other type. Figure 4 illustrates
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.2 Quantities entry point
  clause 6.4.1 , that are managed in the Server , shall be referenced directly from this Object with Organizes or a subtype of Organizes . Table 37 - Quantities definition Attribute Value BrowseName Quantities ... Description This Object is the entry point to quantities and their units managed in the Server . References NodeClass BrowseName DataType TypeDefinition OrganizedBy by the Server Object defined
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.2.3 ServerUnitType ObjectType Definition
  ServerUnitType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the UnitType HasComponent Object AlternativeUnits BaseObjectType O HasProperty Variable ConversionLimit ConversionLimitEnum PropertyType M HasComponent Object 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. The mandatory Property ConversionLimit
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.2 Branch
  Objects of FolderType . The top-level branch (the root) should be represented by an Object where the BrowseName is the Server ProgId. The OPC DA Address space hierarchy is discovered
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  3.1.9 ConditionSource
  Typically, it will be a Variable representing a process tag (e.g. FIC101) or an Object representing a device or subsystem. In Events generated for Conditions, the SourceNode Property (inherited from
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.10 Condition instances in the AddressSpace
  temperature Alarm would appear in the AddressSpace as an instance of some temperature transmitter Object with a HasComponent Reference to an instance of a LimitAlarmType . The availability of instances allows
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.3 Condition and branch instances
  Conditions and to perform analysis of them. A Condition instance may be an Object that appears in the Server Address Space . If this is the case the ConditionId shall ... NodeId for the Object . The state of a Condition instance at any given time is the set values for the Variable s that belong to the Condition instance
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.6 AddComment Method
  comment to a specific state of a Condition instance. Normally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.3 Acknowledge Method
  Condition instance state where AckedState is False. Normally, the NodeId of the object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition ... AcknowledgeableConditionType or MethodId does not refer to a Method for the specified Object or ConditionId . Bad_EventIdUnknown See Table 137 for the description of this result code. Bad_NodeIdInvalid Used
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.2 AlarmConditionType
  Mandatory HasComponent Variable SuppressedState LocalizedText TwoStateVariableType Optional HasComponent Variable OutOfServiceState LocalizedText TwoStateVariableType Optional HasComponent Object ShelvingState ShelvedStateMachineType Optional HasProperty Variable SuppressedOrShelved Boolean PropertyType Mandatory HasProperty Variable MaxTimeShelved Duration PropertyType Optional ... Optional HasProperty Variable OffDelay Duration PropertyType Optional HasComponent Variable FirstInGroupFlag Boolean BaseDataVariableType Optional HasComponent Object FirstInGroup AlarmGroupType Optional HasComponent Variable LatchedState LocalizedText TwoStateVariableType Optional HasAlarmSuppressionGroup Object <AlarmGroup> AlarmGroupType
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.5 Reset Method
  instance of an AlarmConditionType that exposes the LatchedState . Normally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.7 Silence Method
  instance of an AlarmConditionType that also exposes the SilenceState . Normally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.9.1 Overview
  defined in this document. Figure 23 - ConditionClass type hierarchy ConditionClasses are not representations of Object s in the underlying system and, therefore, only exist as Type Nodes in the Address
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.12 HasCondition Reference type
  found in B.2 . HasCondition References can be used in the Type definition of an Object or a Variable . In this case, the SourceNode of this ReferenceType shall be an ObjectType ... Type definitions. In this case the SourceNode of this ReferenceType shall be an Object , Variable or Method Node . The TargetNode shall be a Condition instance or a ConditionType . Table
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.1 General
  this Clause allows Clients to detect Conditions and ConditionSources . An additional hierarchy of Object Nodes that are notifiers may be established to define one or more areas; the Client
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.2 EventNotifier and source hierarchy
  expose the hierarchical organization of Event notifying Objects and ConditionSources . An Event notifying Object represents typically an area of Operator responsibility. The definition of such an area configuration is outside ... 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 a hierarchy. Note that
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.3 Adding Conditions to the hierarchy
  application of the HasCondition Reference in a HasNotifier hierarchy. The Variable LevelMeasurement and the Object "Device B" Reference Condition instances. The Object "Tank A" Reference
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.2 HasEffectDisable
  Transition to an Alarm that will be disabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are disabled, If the target ... AlarmType then all instances of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are disabled, If the target is an Alarm instance then the given Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.3 HasEffectEnable
  Transition to an Alarm that will be enabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are enabled, If the target ... AlarmType then all instances of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are enabled If the target is an Alarm instance then the given Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.4 HasEffectSuppressed
  Transition to an Alarm that will be suppressed. If the reference is to an Object then all Alarms in the EventNotifier hierarchy below that Object are suppressed, If the target ... AlarmType then all instance of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are suppressed, If the target is an Alarm instance then the given Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.5 HasEffectUnsuppressed
  Alarm that will no longer be suppressed. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are removed from being suppressed ... AlarmType then all instance of that AlarmType are no longer suppressed below the Object containing the StateMachine , if the target is an Alarm instance then the given Alarm instance
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  8.1 Overview
  Overview In a system an Object might have multiple Alarms associated with it. These Alarms might be directly Referenced by an Object or they might have no direct References from ... 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 in a plant
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  8.2 AlarmState Variable
  AlarmState Variable An instance of AlarmStateVariableType can be assigned to any Object or Variable . The instance will provide a summary of the Alarms associated with the parent Variable or Object
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  9.1 Overview
  multiple levels allowing a Server to collect metrics as needed. For example, an Object of this type might be added to the Server Object providing a summary of the Alarm ... performance for the entire Server . An instance might also be provided on an Object that includes a HasNotifier hierarchy, such as a tank Object . In this case, it would provide
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  9.2 AlarmMetricsType
  AlarmMetricsType This Object Type is used for metric information. The ObjectType is formally defined in Table 145 . Table 145 - AlarmMetricsType Definition Attribute Value BrowseName AlarmMetricsType IsAbstract False References NodeClass BrowseName ... Metrics An instance of AlarmMetricsType can be added, with a HasComponent reference, to any Object that has its "SubscribeToEvents" bit set within the EventNotifier Attribute. It will collect
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  9.4 Reset Method
  Reset Method is used reset all of the counters, rates and time in the Object Signature Reset(); Method Result Codes in Table 51 (defined in Call Service) Table 147 - Suppress ... this result code. Comments The Reset Method will clear all setting in the diagnostic object and initialize them to zero. Table 148 specifies the AddressSpace representation for the Reset Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  SubscribeToEvents flag set to True. The root Area is represented by an Object with a BrowseName that depends on the UA Server . It is always the target of a HasNotifier
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.5 Event subscriptions
  Server the first time a MonitoredItem is created for the Server Object or one of the Node s representing Areas. The Area filter is set based on the Node being ... could be omitted by some implementations. SourceNode szSource The NodeId of the corresponding Source Object Node . SourceName szSource - Time ftTime - ReceiveTime - Set when the Notification is received by the wrapper
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.1 General
  space of UA A & C Server into the appropriate COM Alarms and Event Object s. Subclauses D.3.2 through D.3.9 identify the design guidelines and constraints used to develop
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.2 Server status mapping
  Proxy reads the UA A & C Server status from the Server Object Variable Node . Status enumeration values that are returned in ServerStatusDataType structure can be mapped
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.7 Browse mapping
  HasNotifier" Reference to assemble a hierarchy of branches/areas such that each Object Node which contains a HasNotifier Reference and whose EventNotifier Attribute is set to SubscribeToEvents is considered ... area. The root for the HasNotifier hierarchy is the Server Object . Starting at the Server Object , HasNotifier Reference s are followed and each HasNotifier target whose EventNotifier Attribute
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.9.4 Filter by area
  Proxy will create a UA Subscription which contains just one MonitoredItem , the Server Object . In doing so, the A&E COM UA Proxy will receive Event s from
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  3.1.5 Program Invocation
  Program Invocation unique Object instance of a Program existing on a Server Note 1 to entry: A Program Invocation is distinguished from other Object instances of the same ProgramStateMachineType ... object node's unique browse path
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  4.2.10.1 Overview
  Client creatable, then the Client can add the Program to the Server . The Object Create Method defined in OPC 10000-3 , is used to create the Program instance. The initial
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.3.1 Overview
  Overview The ProgramStateMachineType components consist of a set of References to the Object instances of StateTypes , TransitionTypes , EventTypes and the Methods that collectively define the Program FiniteStateMachine. Figure 5 - Program
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.1 Overview
  Program Invocation may serve as the EventNotifier for these Events or an owning Object or the Server Object may provide the notifications . ProgramTransitionEventTypes provide the means for delivering result data
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.2 ProgramTransitionEventType
  Program transition. ToStateNumber identifies the state after the Program transition. The IntermediateResult is an Object that aggregates a set of Variables whose values are relevant for the Program
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.6.2 DomainDownloadType
  ProgramStateMachineType BrowseName DomainDownloadType IsAbstract False References NodeClass BrowseName Data Type TypeDefinition Modelling Rule HasComponent Object TransferStateMachine StateMachineType Mandatory HasComponent Object FinishStateMachine StateMachineType Mandatory HasComponent Variable ProgramDiagnostic ProgramDiagnostic2Type Mandatory HasComponent Object ... ReadyToRunning TransitionType HasComponent Object RunningToHalted TransitionType HasComponent Object RunningToSuspended TransitionType HasComponent Object SuspendedToRunning TransitionType HasComponent Object SuspendedToHalted TransitionType HasComponent Method Start Mandatory HasComponent Method Suspend Mandatory HasComponent Method Halt Mandatory
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.4 HistoricalNode
  HistoricalNode Object , Variable , Property or View in the AddressSpace where a Client can access historical data or Events Note 1 to entry: A HistoricalNode is a term used in this ... document to represent any Object , Variable, Property or View in the AddressSpace for which a Client can read and/or update historical data or Events . The terms " HistoricalNodes's history
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.6 HistoricalEventNode
  HistoricalEventNode Object or View in the AddressSpace for which a Client can access historical Events Note 1 to entry: " HistoricalEventNode's history" or "history of a HistoricalEventNode
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  HistoricalDataNodes is still required, but the HistoricalDataNodes is no longer historized, then the Object should be maintained in the AddressSpace , with the appropriate AccessLevel Attribute and Historizing Attribute settings ... optionally the HistoryWrite bits for HistoricalNodes (those with Historical data). If a HistoricalConfiguration Object is added to or deleted from a Server or a Reference to a HistoricalConfiguration Object
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.1.2 Annotations Property
  Annotations Property The DataVariable or Object that has Annotation data will add the Annotations Property as shown in Table 2 . Table 2 - Annotations Property Name Use Data Type Description Annotations ... NodeId in the NodesToRead parameter. Annotation data does not have a separate HistoricalDataConfigurationType object instance. The historical configuration defined on the parent node applies to the Annotations Property . As with
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.2 HistoricalDataConfigurationType
  Historical Access Data model extends the standard type model by defining the HistoricalDataConfigurationType. This Object defines the general characteristics of a Node that defines the historical configuration of any HistoricalDataNode ... definition Attribute Value BrowseName HistoricalDataConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule HasComponent Object AggregateConfiguration -- AggregateConfigurationType Mandatory HasComponent Object AggregateFunctions -- FolderType Optional HasProperty Variable Stepped Boolean PropertyType Mandatory HasProperty
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.4 Historical Data Configuration Object
  Historical Data Configuration Object This Object is used as the browse entry point for information about HistoricalDataNode configuration. The content of this Object is already defined by its type definition ... definition Attribute Value BrowseName HA Configuration References Node Class BrowseName DataType TypeDefinition ModellingRule HasTypeDefinition Object Type HistoricalDataConfigurationType Defined in Table
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.3.4 HasCurrentEvent ReferenceType
  this reference type shall be a HistoricalEventNode. The Target node shall be any Object or View that has the EventNotifier Attribute set to TRUE. Table 9 - HasCurrentEvent ReferenceType Attributes Value
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.3 HistoricalEventConfigurationType
  Historical Access Event model extends the standard type model by defining the HistoricalEventConfigurationType. This Object defines the general characteristics of a Node that defines the historical configuration of any HistoricalEventNode ... definition Attribute Value BrowseName HistoricalEventConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule HasComponent Object EventTypes -- FolderType Mandatory HasProperty Variable StartOfArchive UtcTime PropertyType Optional HasProperty Variable StartOfOnlineArchive UtcTime PropertyType Optional
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.1 General
  Events , the source of Events can be the Server Node or some higher level Object and replicating that Object or entire Server and the complex structure under it would
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.2 External Historical Event Node
  instance of this ObjectType shall include a HasCurrentEvent reference to the remote Server Object that is the source of the Events that are being collected. Table 12 - HistoricalExternalEventSourceType definition Attribute ... Mandatory ConformanceUnits Historical Access External Event Source All instances of HistoricalExternalEventSourceType shall set the Object Attributes bits as described in 5.4.4 . An instance of this ObjectType can also have
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.4 HistoricalEventNodes Address Space Model
  subset of the Events generated by the Server . Each HistoricalEventNode is represented by an Object or View with a specific set of Attributes. The HistoricalEventFilter Property specifies the fields available ... history. Not every Object or View in the AddressSpace can be a HistoricalEventNode . To qualify as HistoricalEventNode , a Node must contain historical Events . To see if historical Events are available
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.2 HistoryServerCapabilitiesType
  Server supporting Historical Access shall contain a Reference to a HistoryServerCapabilitiesType Object . The content of this BaseObjectType is already defined by its type definition in OPC 10000-5 . The Object ... Mandatory HasProperty Variable DeleteEventCapability Boolean PropertyType Mandatory HasProperty Variable InsertAnnotationCapability Boolean PropertyType Mandatory HasComponent Object AggregateFunctions -- FolderType Mandatory HasProperty Variable ServerTimestampSupported Boolean PropertyType Optional ConformanceUnits Historical Access Read Raw Historical
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.3 Default configuration
  provided for all nodes, the Historian shall expose a default instance under the Server Object. If HistoricalDataNodes exist without a referenced configuration, an Object with a BrowseName of " DefaultHAConfiguration ... shall be exposed. If HistoricalEventNodes exist without configuration, an object with a BrowseName of " DefaultHEConfiguration " shall be exposed. For any Node that does not have a referenced historical
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.4.2 Read processed functionality
  parameter allows a Client to override the Aggregate configuration settings supplied by the AggregateConfiguration Object on a per call basis. See OPC 10000-13 for more information on Aggregate configurations
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.2.1 UpdateDataDetails structure details
  details for insert, replace, and insert/replace history updates. nodeId NodeId Node id of the Object to be updated. performInsertReplace PerformUpdateType This enumeration determines which action of Insert, Replace, or Update
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.3.1 UpdateStructureDataDetails structure details
  Structure The details for Structured Data History updates. nodeId NodeId Node id of the Object to be updated. performInsertReplace PerformUpdateType Value determines which action of insert, replace, or update
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.1 UpdateEventDetails structure detail
  insert, replace, and insert/replace history Event updates. nodeId NodeId Node id of the Object to be updated. performInsertReplace PerformUpdateType Value determines which action of insert, replace, or update is performed
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.5.1 DeleteRawModifiedDetails structure detail
  delete raw and delete modified history updates. nodeId NodeId Node id of the Object for which history values are to be deleted. isDeleteModified Boolean TRUE for MODIFIED, FALSE
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.6.1 DeleteAtTimeDetails structure detail
  Structure The details for delete raw history updates. nodeId NodeId Node id of the Object for which history values are to be deleted. reqTimes [] UtcTime The entries define the specific
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.7.1 DeleteEventDetails structure detail
  delete raw and delete modified history updates. nodeId NodeId Node id of the Object for which history values are to be deleted. eventIds [] ByteString An array of EventIds to identify
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.4 Application Registration Workflow
  list of GDS managed CertificateGroups by browsing the CertificateGroups Folder of the Directory Object . If more than one CertificateGroup is returned, the user selects the relevant CertificateGroups used
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.2 Directory
  Directory This Object is the root of the GlobalDiscoveryServer AddressSpace and it is the target of an Organizes reference from the Objects folder defined in OPC 10000-5 . It organizes ... locations in an administrative domain. It is defined in Table 4 . Table 4 - Directory Object Definition Attribute Value BrowseName 2:Directory TypeDefinition 2:DirectoryType defined in 6.5.3 . References NodeClass BrowseName
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.6 Pull Management Workflow
  CertificateManager . The cycle time is defined by the UpdateFrequency on the related TrustList Object in the CertificateManager . Connect Create a connection for option (2). For the connection management with ... updates by calling the Method GetTrustList . The Method returns the NodeId of the TrustList Object for the CertificateGroup . The LastUpdateTime of TrustList Object indicates when the contents of the TrustList
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.1 TrustListType
  TrustList was last updated. The LastUpdateTime shall reflect changes made using the TrustList Object Methods . A TrustList Object in a CertificateManager shall also reflect changes made in other ways ... LastUpdateTime of a TrustList Object in a CertificateManager allows Clients using the PullManagement to know whether the TrustList has changed since the last time they accessed it. The LastUpdateTime
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.12 TrustListUpdateRequestedAuditEventType
  called It is raised when CloseAndUpdate, AddCertificate or RemoveCertificate Method on a TrustListType Object is called. Its representation in the AddressSpace is formally defined in Table 39 . Table 39 - TrustListUpdateRequestedAuditEventType
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.13 TrustListUpdatedAuditEventType
  successfully changed. This is the result of a CloseAndUpdate Method on a TrustListType Object or the result of a ApplyChanges Method on the ServerConfigurationType Object being called. It shall also ... defined in OPC 10000-5 . The TrustListId Property is the NodeId of the TrustList Object that was changed
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.1 CertificateGroupType
  TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasComponent Object 0:TrustList 0:TrustListType Mandatory 0:HasProperty Variable 0:CertificateTypes 0:NodeId[] 0:PropertyType Mandatory ... HasProperty Variable 0:Purpose 0:NodeId 0:PropertyType Optional 0:HasComponent Object 0:CertificateExpired 0:CertificateExpirationAlarmType Optional 0:HasCondition ObjectType 0:CertificateExpirationAlarmType 0:HasComponent Object 0:TrustListOutOfDate 0:TrustListOutOfDateAlarmType Optional
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.3 CertificateGroupFolderType
  Modelling Rule Subtype of the 0: FolderType defined in OPC 10000-5 . 0:HasComponent Object 0:DefaultApplicationGroup 0:CertificateGroupType Mandatory 0:HasComponent Object 0:DefaultHttpsGroup 0:CertificateGroupType Optional 0:HasComponent ... Object 0:DefaultUserTokenGroup 0:CertificateGroupType Optional 0:Organizes Object 0:<AdditionalGroup> 0:CertificateGroupType Optional Placeholder Conformance Units GDS Certificate Manager Pull Model Push Model for Global Certificate
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.4 CertificateGroupDataType
  record is the name portion of the BrowseName of the associated CertificateGroup Object in the AddressSpace . It may not be possible to delete CertificateGroups such as DefaultApplicationGroup . Note that when ... unique and not abstract. The set of permitted CertificateTypes is defined by the ApplicationConfigurationFileType Object (see 7.10.20 ). When the CertificateTypes list is updated, if an element already exists
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.1 ConfigurationFileType
  defines a FileType that can be used to access the configuration associated with an Object . The file is a stream containing an instance of UABinaryFileDataType serialized using ... shall automatically Close ConfigurationFiles if there are no calls to Methods on the ConfigurationFile Object within the time specified by the ActivityTimeout Property . The Size Property inherited from FileType
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.5 BaseConfigurationRecordDataType
  used when updating or deleting a single record. If the record corresponds to an Object in the AddressSpace then this shall be the Name portion of the BrowseName ... record does not have a matching Object, then Name is only unique within an instance of a configuration file. For these cases, the Server may generate new names each time
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.2 CertificateDirectoryType
  DataType TypeDefinition Modelling Rule Subtype of the 2: DirectoryType defined in 6.5.3 . 0:Organizes Object 2:CertificateGroups 0:CertificateGroup FolderType Mandatory 0:HasComponent Method 2:StartSigningRequest Defined in 7.9.3 . Mandatory ... CheckRevocationStatus Defined in 7.9.11 . Optional Conformance Units GDS Certificate Manager Pull Model The CertificateGroups Object organizes the CertificateGroups supported by the CertificateManager . It is described in 7.8.4.10 . CertificateManagers shall support
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.4 StartNewKeyPairRequest
  Certificate to return. The permitted values are specified by the CertificateTypes Property of the Object specified by the CertificateGroupId parameter. The SubjectName parameter is a sequence of X.500 name value