Search

200 result(s) for Address Space

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.1 AddressSpace
  AddressSpace collection of information that a Server makes visible to its Clients Note 1 to entry: See OPC 10000-3 for a description of the contents and structure ... Server AddressSpace
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  3.2 Specification parts
  Address Space Model Part 3 describes the contents and structure of the Server's AddressSpace . Part 4 ( OPC 10000-4 ) - Services Part 4 specifies the Services provided by Servers . Part
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.3 Design goals
  Design goals OPC UA provides a consistent, integrated AddressSpace and service model. This allows a single Server to integrate data, Alarms and Events , and history into its AddressSpace ... 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 of the AddressSpace
• 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 ... types that define attribute values may be simple or complex. Node s in the AddressSpace are typed according to their use and their meaning. NodeClasses define the metadata
• 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
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.1 AddressSpace Nodes
  AddressSpace Nodes The AddressSpace is modelled as a set of Node s accessible by Clients using OPC UA Services (interfaces and methods). Node s in the AddressSpace are used
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.2 AddressSpace organization
  AddressSpace organization OPC 10000-3 contains the details of the meta model "building blocks" used to create an AddressSpace out of interconnected Nodes in a consistent manner. Servers ... free to organize their Node s within the AddressSpace as they choose. The use of References between Node s permits Servers to organize the AddressSpace into hierarchies, a full mesh
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.3 AddressSpace Views
  AddressSpace Views A View is a subset of the AddressSpace . Views are used to restrict the Node s that the Server makes visible to the Client , thus restricting the size ... AddressSpace for the Service requests submitted by the Client . The default View is the entire AddressSpace . Servers may optionally define other Views . Views hide some of the Node
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.4 Support for information models
  Support for information models The OPC UA AddressSpace supports Information Models . This support is provided through: Node References that allow Objects in the AddressSpace to be related to each other ... 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 groups can define how their
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.5.1 MonitoredItems
  MonitoredItems MonitoredItems are entities in the Server created by the Client that monitor AddressSpace Node s and, indirectly, their real-world counterparts. When they detect a data change
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.6.2 Request/response Services
  Interface to perform a specific task on one or more Node s in the AddressSpace and to return a response
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.6 View Service Set
  View Service Set Views are publicly defined, Server -created subsets of the AddressSpace . The entire AddressSpace is the default View , and therefore, the View Services are capable of operating ... entire AddressSpace . Future versions of this specification may also define Services to create Client defined Views . The View Service Set allows Clients to discover Node s in a View
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.7 Attribute Service Set
  defined by Clients or Servers . Attributes are the only elements in the AddressSpace permitted to have data values. A special Attribute , the Value Attribute is used to define the value
• 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.9 Hierarchical Reference
  Hierarchical Reference Reference that is used to construct hierarchies in the AddressSpace Note 1 to entry: All hierarchical ReferenceTypes are derived from HierarchicalReferences
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.1 Overview
  Overview The remainder of Clause 4 defines the concepts of the AddressSpace . Clause 5 defines the NodeClasses of the AddressSpace representing the AddressSpace concepts. Clause 6 defines details
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.2 URIs
  appear in UANodeSets (see OPC 10000-6 ) and in the NamespaceArray in a Server AddressSpace (see OPC 10000-5 ); ApplicationUris identify an OPC UA Application running on a particular Device
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.3 Object Model
  Object Model The primary objective of the OPC UA AddressSpace is to provide a standard way for Servers to represent Objects to Clients . The OPC UA Object Model has been ... Object Model The elements of this model are represented in the AddressSpace as Nodes . Each Node is assigned to a NodeClass and each NodeClass represents a different element
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.1 General
  that the OPC UA Server makes available to Clients is referred to as its AddressSpace . The model for Objects is defined by the OPC UA Object Model (see 4.3 ). Objects ... their components are represented in the AddressSpace as a set of Nodes described by Attributes and interconnected by References . Figure 3 illustrates the model of a Node and the remainder
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.2 NodeClasses
  References that shall be instantiated (given values) when a Node is defined in the AddressSpace . Attributes are discussed in 4.4.3 and References in 4.4.4 . Clause 5 defines the NodeClasses ... AddressSpace . These NodeClasses are referred to collectively as the metadata for the AddressSpace . Each Node in the AddressSpace is an instance of one of these NodeClasses . No other NodeClasses shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.3 Attributes
  NodeClass definitions in Clause 4.10 and, therefore, are not included in the AddressSpace . Each Attribute definition consists of an attribute id (for attribute ids of Attributes ... extended by Clients or Servers . When a Node is instantiated in the AddressSpace , the values of the NodeClass Attributes are provided. The mandatory/optional indicator for the Attribute indicates whether
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  References are defined as instances of ReferenceType Nodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass (see 5.3 ). The Node that contains the Reference ... Figure 4 - Reference Model The TargetNode of a Reference may be in the same AddressSpace or in the AddressSpace of another OPC UA Server . TargetNodes located in other Servers
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.3 DataVariables
  temperature values generated by three separate temperature transmitters that are also visible in the AddressSpace . In this case, this complex DataVariable could define HasComponent References from it to the individual
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  Therefore, Servers may use well-known NodeIds without representing the corresponding TypeDefinitionNodes in their AddressSpace . However, the TypeDefinition­Nodes shall be provided for generic Clients . These TypeDefinitionNodes may exist in another ... example, a setpoint parameter "SP" is represented as a DataVariable in the AddressSpace . This DataVariable is part of an Object not shown in the figure. To provide
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.2 Complex TypeDefinitionNodes and their InstanceDeclarations
  specification, if an instance is an InstanceDeclaration or not is only visible in the AddressSpace by following its References . Some instances may be shared and therefore referenced by TypeDefinitionNodes , InstanceDeclarations
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.1 General
  Event . 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 ... system is offline). Events may also be exposed through other Nodes anywhere in the AddressSpace . These Nodes (identified via the EventNotifier Attribute ) provide some subset of the Events generated
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.2 EventTypes
  defined in this part. The EventTypes supported by a Server are exposed in the AddressSpace of a Server . EventTypes are represented as ObjectTypes in the AddressSpace and do not have ... defined in this document are specified as abstract and therefore never instantiated in the AddressSpace . Event occurrences of those EventTypes are only exposed via a Subscription . Components of an EventType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.3 Event Categorization
  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 or functionality contained
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.9.1 Overview
  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
  5.1 Overview
  Overview Clause 5 defines the NodeClasses used to define Nodes in the OPC UA AddressSpace . NodeClasses are derived from a common Base NodeClass . This NodeClass is defined first, followed ... 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.2.4 BrowseName
  Attribute that is used as a non-localised human-readable name when browsing the AddressSpace to create paths out of BrowseNames . The TranslateBrowsePathsToNodeIds Service defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.1 General
  References are defined as instances of ReferenceType Nodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass as specified in Table 9 . In contrast ... Space Model. These ReferenceTypes are defined in Clause 7 and their representation in the AddressSpace is defined in OPC 10000-5 . Servers may also define ReferenceTypes . In addition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  does not specify how those constraints could or should be made available in the AddressSpace . Nevertheless, for the standard ReferenceTypes , some constraints are specified in Clause 7 . This standard does
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  They do not need, or want, to be burdened with viewing Nodes in the AddressSpace for which they have no interest. To address this problem, this standard defines the concept ... View . Each View defines a subset of the Nodes in the AddressSpace . The entire AddressSpace is the default View . Each Node in a View may contain only a subset
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.3 Standard ObjectType FolderType
  purpose is to provide Objects that have no other semantic than organizing of the AddressSpace . A special ReferenceType is introduced for those Folder Objects , the Organizes ReferenceType . The SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Variables are always defined as Properties or DataVariables of other Nodes in the AddressSpace . They are never defined by themselves. A Variable is always part of at least one other
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Call Service defined in OPC 10000-4 . Method invocations are not represented in the AddressSpace . Method invocations always run to completion and always return responses when complete. Methods are defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  always be available to the Server . Figure 18 illustrates the Nodes used in the AddressSpace to describe the structure of a DataType . The DataType points to an Object of type
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  differently regarding their encoding and according to whether this encoding is represented in the AddressSpace . Built-in DataTypes are a fixed set of DataTypes ... complete list of Built-in DataTypes ). They have no encodings visible in the AddressSpace since the encoding should be known to all OPC UA products. Examples of Built-in DataTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  DataType is abstract or not. Abstract DataTypes can be used in the AddressSpace , i.e. Variables and VariableTypes can point with their DataType Attribute to an abstract DataType . However, concrete values ... DataTypes . HasSubtype References may be used to expose a data type hierarchy in the AddressSpace . The semantic of subtyping is only defined to the point, that a Server may provide
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.4 DataTypeEncoding and Encoding Information
  DataTypeEncoding and Encoding Information If a DataType Node is exposed in the AddressSpace , it shall provide its DataTypeEncodings using HasEncoding References . These References shall be bi-directional. Figure 19 provides ... example how DataTypes are modelled in the AddressSpace . Figure 19 - Example of DataType Modelling The information on how to encode the DataType is provided in the Attribute DataTypeDefinition
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  copies of the InstanceDeclaration s, the InstanceDeclaration itself or another Node in the AddressSpace that has the same TypeDefinitionNode and BrowseName . If new copies are created, then the Attribute values
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.1 General
  define behaviour for NonHierarchical References between InstanceDeclaration as well. ModellingRules are represented in the AddressSpace as Objects of the ObjectType ModellingRuleType . There are some Properties defining common semantic of ModellingRules ... specifies the representation of the ModellingRule Objects, their Properties and their type in the AddressSpace . Subclause 6.4.4.3 defines how the ModellingRule may be changed when instantiating InstanceDeclarations with respect
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.3 ExposesItsArray
  each value of the array will also be exposed as a Variable in the AddressSpace . The ExposesItsArray ModellingRule can only be applied on InstanceDeclarations of NodeClass Variable that are part
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.1 General
  remainder of 7 defines the ReferenceTypes . OPC 10000-5 defines their representation in the AddressSpace . Figure 38 - Standard ReferenceType Hierarchy
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.2 References ReferenceType
  shall be used as a Reference between Nodes in an OPC UA AddressSpace . There is no semantic associated with this ReferenceType . This is the base type of all ReferenceTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.11 Organizes ReferenceType
  subtype of HierarchicalReferences . The semantic of this ReferenceType is to organise Nodes in the AddressSpace . It can be used to span multiple hierarchies independent of any hierarchy created with
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.1 General
  General The remainder of 8 defines DataTypes . Their representation in the AddressSpace and the DataType hierarchy is specified in OPC 10000-5 . Other parts of this series of standards
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.1 General
  type of the identifier (see 8.2.3 ). Identifier * The identifier for a Node in the AddressSpace of an OPC UA Server (see 8.2.4 ). See OPC 10000-6 for a description
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.2 NamespaceIndex
  NamespaceArray is a Variable that is part of the Server Object in the AddressSpace (see OPC 10000-5 for its definition). The URI for the OPC UA namespace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.2.4 Identifier value
  Identifier values of IdType Opaque are restricted to 4096 bytes. A Node in the AddressSpace shall not have a null NodeId . However, many services defined in OPC 10000-4 define
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.1 General
  General The remainder of 8.61 defines EventTypes . Their representation in the AddressSpace is specified in OPC 10000-5 . Other parts of this series of standards may specify additional EventTypes . Figure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.1 General
  General ModelChangeEvents are generated to indicate a change of the AddressSpace structure. The change may consist of adding or deleting a Node or Reference. Although the relationship of a Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.2 NodeVersion Property
  mechanisms. This relation also implies that only those Nodes of the AddressSpace having a NodeVersion shall trigger a ModelChangeEvent . Other Nodes shall not trigger a ModelChangeEvent
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.3 Views
  generated in the context of a View, including the default View where the whole AddressSpace is considered. Therefore the only Notifiers which report the ModelChangeEvents are View Nodes ... affect different Views . If, for example, a Node was deleted from the AddressSpace , and this Node was also contained in a View "A", there would be one Event
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.33.1 General
  SemanticChangeEvents are Events of SemanticChangeEventType that are generated to indicate a change of the AddressSpace semantics. The change consists of a change to the Value Attribute of a Property
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.3 ObjectTypes
  point of view Objects are used to group Variables and other Objects in the AddressSpace . Therefore ObjectTypes should be used when some common structures/groups of Objects and/or Variables should
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.4.3 Many Variables and / or Structured DataTypes
  first approach are that the complex structure of the data is visible in the AddressSpace . A generic Client can easily access the data without knowledge of user-defined DataTypes ... interpret the data. The structure of the data is not visible in the AddressSpace ; additional Properties describing the data structure cannot be added to the adequate places since they
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.5 Views
  Views Server -defined Views can be used to present an excerpt of the AddressSpace suitable for a special class of Clients , for example maintenance Clients , engineering Clients , etc. The View
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.7 Defining ReferenceTypes
  expose different hierarchies, and new Nonhierarchical ReferenceTypes to expose relationships between Nodes in the AddressSpace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.1 Background
  only the OPC UA Meta Model, but also defines some Nodes to organise the AddressSpace and to provide information about the Server as specified in OPC 10000-5 . Figure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  defines Services that allow the Client to add, modify and delete Nodes in the AddressSpace . Figure 4 - NodeManagement Service Set The View Service Set , illustrated in Figure 5 , defines Services ... that allow Clients to browse through the AddressSpace or subsets of the AddressSpace called Views . The Query Service Set allows Clients to get a subset of data from the AddressSpace
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.7.2.1 Description
  used to identify the Session in the audit logs and in the Server's AddressSpace . The second is the authenticationToken which is used to associate an incoming request with ... Applications with limited resources. The SoftwareCertificates are provided in the Server's AddressSpace as defined in OPC 10000-5 . A SoftwareCertificate identifies the capabilities of the Server and also contains
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.7.2.2 Parameters
  identifies the Session . The Server makes this name and the sessionId visible in its AddressSpace for diagnostic purposes. The Client should provide a name that is unique for the instance ... identifier is used to access the diagnostics information for the Session in the Server AddressSpace . It is also used in the audit logs and any events that report information related
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.1 Overview
  Overview This Service Set defines Services to add and delete AddressSpace Nodes and References between them. All added Nodes continue to exist in the AddressSpace even if the Client that ... disconnects from the Server . Calls to NodeManagement Services may result in changes to the AddressSpace in addition to the requested change. The actual behaviour is Server specific
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.1 Description
  Description This Service is used to add one or more Nodes into the AddressSpace hierarchy. Using this Service , each Node is added as the TargetNode of a HierarchicalReference to ensure ... that the AddressSpace is fully connected and that the Node is added as a child within the AddressSpace hierarchy (see OPC 10000-3 ). When a Server creates an instance
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.1 Description
  TargetNode in a remote Server . In certain cases, adding new References to the AddressSpace shall require that the Server add new Server ids to the Server 's ServerArray Variable
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.1 Description
  Description This Service is used to delete one or more Nodes from the AddressSpace . When any of the Nodes deleted by an invocation of this Service is the TargetNode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.1 Overview
  Clients use the browse Services of the View Service Set to navigate through the AddressSpace or through a View which is a subset of the AddressSpace . A View ... subset of the AddressSpace created by the Server . Future versions of this document may also define services to create Client -defined Views . See OPC 10000-5 for a description
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  browse (see 7.44 for ViewDescription definition). An empty ViewDescription value indicates the entire AddressSpace . Use of the empty ViewDescription value causes all References of the nodesToBrowse to be returned
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.1 Description
  Clients using this Service , although the historical values themselves are not visible in the AddressSpace . The AccessLevel Attribute defined in OPC 10000-3 indicates a Node 's support for historical
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  Properties of the base EventTypes and the representation of the base EventTypes in the AddressSpace are specified
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.1 Description
  returned in the Publish response. Monitored Nodes can be removed from the AddressSpace after the creation of a MonitoredItem . This does not affect the validity of the MonitoredItem ... that the MonitoredItem becomes valid again if the Node is added again to the AddressSpace and the MonitoredItem still exists. If a NodeId is known to be valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.2 Parameters
  line with the following indented items. itemToMonitor ReadValueId Identifies an item in the AddressSpace to monitor. To monitor for Events , the attributeId element of the ReadValueId structure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.2.1 Overview
  still responsible for managing and enforcing the Permissions assigned to Nodes in its Address Space . The clauses below discuss the use of an external Authorization Service in more detail
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.9 Auditing for Method Service Set
  audit Events for both successful and failed service invocations if the invocation modifies the AddressSpace , writes a value or modifies the state of the system (alarm acknowledge, batch sequencing ... Event of type AuditUpdateMethodEventType or subtypes of it. Methods that do not modify the AddressSpace , write values or modify the state of the system may generate events
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.2 RedundantServerSet Requirements
  RedundantServerSet Requirements OPC UA Servers that are part of a RedundantServerSet have certain AddressSpace requirements. These requirements allow a Client to consistently access information from Servers in a RedundantServerSet ... availability of Servers in the RedundantServerSet . Servers in the RedundantServerSet shall have an identical AddressSpace including: identical NodeIds identical browse paths and structure of the AddressSpace identical logic for setting
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.2 ServiceLevel
  Server is partially operational, but is experiencing problems such that portions of the AddressSpace are out of service or unavailable. An example usage of this ServiceLevel sub-range would
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.4 AttributeOperand
  Table 128 - AttributeOperand Name Type Description AttributeOperand structure Attribute of a Node in the AddressSpace . nodeId NodeId NodeId of a Node from the type system. alias String An optional parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  Table 129 - SimpleAttributeOperand Name Type Description SimpleAttributeOperand structure Attribute of a Node in the AddressSpace . typeDefinitionId NodeId NodeId of a TypeDefinitionNode . This parameter restricts the operand to instances
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.16 ExpandedNodeId
  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 the Server table ... identifier element of the NodeId . identifier * The identifier for a Node in the AddressSpace of an OPC UA Server (see NodeId definition
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.35 SessionAuthenticationToken
  NodeId data type; however, it is never used to identify a Node in the AddressSpace . Servers may assign a value to the NamespaceIndex ; however, its meaning is Server specific
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.1 Overview
  logical schema used for internal storage of the data. Knowledge of the AddressSpace is sufficient. An OPC UA Application is expected to use the OPC UA Query Services as part ... report. A Query defines what instances of one or more TypeDefinitionNodes in the AddressSpace should supply a set of Attributes . Results returned by a Server are in the form
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.2 Querying Views
  B.2.2 Querying Views A View is a subset of the AddressSpace available in the Server . See OPC 10000-5 for a description of the organization of Views in the AddressSpace ... View is returned. Data not included in the View but included in the original AddressSpace is not returned. The Query Services supports access to current and historical data. The Service
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  ContentFilter is discussed in 7.7 . If an empty filter is provided then the entire AddressSpace should be examined and all Nodes that contain a matching requested Attribute or Reference
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.9 Example 6
  request, one in which the Client is interested in displaying part of the AddressSpace of the Server . This request includes listing a Reference as something that is to be returned
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.10 Example 7
  illustration a request in which a Client wants to display part of the AddressSpace based on a starting point that was obtained via browsing. This request includes listing References
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.11 Example 8
  Example 8 The eighth example provides an illustration of a request in which the AddressSpace is restricted by a Server defined View . This request is the same ... type cat and has a feeding schedule) limited by the AddressSpace in View1. The NodeTypeDescription parameters used in the example are described in Table B.32 Table B.32 - Example 8 NodeTypeDescription
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.12 Example 9
  ninth example provides a further illustration for a request in which the AddressSpace is restricted by a Server defined View . This request is similar to the second example except that ... type cat and has a feeding schedule) limited by the AddressSpace in View1. Table B.35 describes the NodeTypeDescription parameters used in the example. Table B.35 - Example 9 NodeTypeDescription Type Definition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  1 Scope
  defines the Information Model .The Information Model describes standardised Nodes of a Server 's AddressSpace . These Nodes are standardised types as well as standardised instances used for diagnostics ... entry points to server-specific Nodes . Thus, the Information Model defines the AddressSpace of an empty OPC UA Server . However, it is not expected that all Servers will provide
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace , the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object ... ConformanceUnits defined in OPC 10000-7 that require the Node to be in the AddressSpace . If a Server supports a ConformanceUnit , it shall expose the Nodes related to the ConformanceUnit
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.3 ServerDiagnosticsType
  Property . Dynamic diagnostic Nodes (such as the Session Nodes ) will not appear in the AddressSpace . If the collection of diagnostic information is not supported, the EnabledFlag Property will be read
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.12 AddressSpaceFileType
  ServerType The ExportNamespace Method provides a way to export the namespace from the Server AddressSpace to the XML file represented by the AddressSpaceFileType . Value Attributes are only exported if they
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  Property provides a list of IdTypes used for static Nodes . All Nodes in the AddressSpace of the namespace using one of the IdTypes in the array shall be static Nodes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.1 General
  General This document defines standard EventTypes . They are represented in the AddressSpace as ObjectTypes . The EventTypes are already defined in OPC 10000-3 . The following subclauses specify their representation ... AddressSpace
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  BaseEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 25 . Table 25 - BaseEventType definition Attribute Value BrowseName BaseEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.3 AuditEventType
  AuditEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 26 . Table 26 - AuditEventType definition Attribute Value BrowseName AuditEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.4 AuditSecurityEventType
  AuditSecurityEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 27 . Table 27 - AuditSecurityEventType definition Attribute Value BrowseName AuditSecurityEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.5 AuditChannelEventType
  AuditChannelEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 28 . Table 28 - AuditChannelEventType definition Attribute Value BrowseName AuditChannelEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.6 AuditOpenSecureChannelEventType
  AuditOpenSecureChannelEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 29 . Table 29 - AuditOpenSecureChannelEventType definition Attribute Value BrowseName AuditOpenSecureChannelEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.7 AuditSessionEventType
  AuditSessionEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 30 . Table 30 - AuditSessionEventType definition Attribute Value BrowseName AuditSessionEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.8 AuditCreateSessionEventType
  AuditCreateSessionEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 31 . Table 31 - AuditCreateSessionEventType definition Attribute Value BrowseName AuditCreateSessionEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.9 AuditUrlMismatchEventType
  AuditUrlMismatchEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 32 . This Type has been deprecated and will be removed
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.10 AuditActivateSessionEventType
  AuditActivateSessionEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 33 . Table 33 - AuditActivateSessionEventType definition Attribute Value BrowseName AuditActivateSessionEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.11 AuditCancelEventType
  AuditCancelEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 35 . Table 35 - AuditCancelEventType definition Attribute Value BrowseName AuditCancelEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.12 AuditCertificateEventType
  AuditCertificateEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 36 . Table 36 - AuditCertificateEventType definition Attribute Value BrowseName AuditCertificateEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.13 AuditCertificateDataMismatchEventType
  AuditCertificateDataMismatchEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 37 . Table 37 - AuditCertificateDataMismatchEventType definition Attribute Value BrowseName AuditCertificateDataMismatchEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.14 AuditCertificateExpiredEventType
  AuditCertificateExpiredEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 38 . Table 38 - AuditCertificateExpiredEventType definition Attribute Value BrowseName AuditCertificateExpiredEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.15 AuditCertificateInvalidEventType
  AuditCertificateInvalidEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 39 . Table 39 - AuditCertificateInvalidEventType definition Attribute Value BrowseName AuditCertificateInvalidEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.16 AuditCertificateUntrustedEventType
  AuditCertificateUntrustedEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 40 . Table 40 - AuditCertificateUntrustedEventType definition Attribute Value BrowseName AuditCertificateUntrustedEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.17 AuditCertificateRevokedEventType
  AuditCertificateRevokedEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 41 . Table 41 - AuditCertificateRevokedEventType definition Attribute Value BrowseName AuditCertificateRevokedEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.18 AuditCertificateMismatchEventType
  AuditCertificateMismatchEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 42 . Table 42 - AuditCertificateMismatchEventType definition Attribute Value BrowseName AuditCertificateMismatchEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.19 AuditNodeManagementEventType
  AuditNodeManagementEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 43 . Table 43 - AuditNodeManagementEventType definition Attribute Value BrowseName AuditNodeManagementEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.20 AuditAddNodesEventType
  AuditAddNodesEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 44 . Table 44 - AuditAddNodesEventType definition Attribute Value BrowseName AuditAddNodesEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.21 AuditDeleteNodesEventType
  AuditDeleteNodesEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 45 . Table 45 - AuditDeleteNodesEventType definition Attribute Value BrowseName AuditDeleteNodesEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.22 AuditAddReferencesEventType
  AuditAddReferencesEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 46 . Table 46 - AuditAddReferencesEventType definition Attribute Value BrowseName AuditAddReferencesEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.23 AuditDeleteReferencesEventType
  AuditDeleteReferencesEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 47 . Table 47 - AuditDeleteReferencesEventType definition Attribute Value BrowseName AuditDeleteReferencesEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.24 AuditUpdateEventType
  AuditUpdateEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 48 . Table 48 - AuditUpdateEventType definition Attribute Value BrowseName AuditUpdateEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.25 AuditWriteUpdateEventType
  AuditWriteUpdateEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 49 . Table 49 - AuditWriteUpdateEventType definition Attribute Value BrowseName AuditWriteUpdateEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.26 AuditHistoryUpdateEventType
  AuditHistoryUpdateEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 50 . Table 50 - AuditHistoryUpdateEventType definition Attribute Value BrowseName AuditHistoryUpdateEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.27 AuditUpdateMethodEventType
  AuditUpdateMethodEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 51 . Table 51 - AuditUpdateMethodEventType definition Attribute Value BrowseName AuditUpdateMethodEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.28 SystemEventType
  SystemEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 52 . Table 52 - SystemEventType definition Attribute Value BrowseName SystemEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.29 DeviceFailureEventType
  DeviceFailureEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 53 . Table 53 - DeviceFailureEventType definition Attribute Value BrowseName DeviceFailureEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.30 SystemStatusChangeEventType
  SystemStatusChangeEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 54 . Table 54 - SystemStatusChangeEventType definition Attribute Value BrowseName SystemStatusChangeEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.31 BaseModelChangeEventType
  BaseModelChangeEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 55 . Table 55 - BaseModelChangeEventType definition Attribute Value BrowseName BaseModelChangeEventType IsAbstract True ... Node of the View that gives the context of the changes. If the whole AddressSpace is the context, the SourceNode Property is set to the NodeId of the Server Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.32 GeneralModelChangeEventType
  GeneralModelChangeEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 56 . Table 56 - GeneralModelChangeEventType definition Attribute Value BrowseName GeneralModelChangeEventType IsAbstract True
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.33 SemanticChangeEventType
  SemanticChangeEventType This EventType is defined in OPC 10000-3 . Its representation in the AddressSpace is formally defined in Table 57 . Table 57 - SemanticChangeEventType definition Attribute Value BrowseName SemanticChangeEventType IsAbstract True ... Node of the View that gives the context of the changes. If the whole AddressSpace is the context, the SourceNode Property is set to the NodeId of the Server Object
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.36 AuditClientEventType
  used for the categorization of Events generated by a Client . Its representation in the AddressSpace is formally defined in Table 60 . Table 60 - AuditClientEventType definition Attribute Value BrowseName AuditClientEventType IsAbstract
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.37 AuditClientUpdateMethodResultEventType
  allows Method calls issued by a Client to be audited. Its representation in the AddressSpace is formally defined in Table 61 . Table 61 - AuditClientUpdateMethodResultEventType definition Attribute Value BrowseName AuditClientUpdateMethodResultEventType IsAbstract
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.6 FolderType
  FolderType Instances of this ObjectType are used to organise the AddressSpace into a hierarchy of Nodes . They represent the root Node of a subtree, and have no other semantics associated
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.1 Overview
  Overview To promote interoperability of clients and Servers , the OPC UA AddressSpace is structured as a hierarchy, with the top levels standardised for all Servers . Figure 1 illustrates the structure ... AddressSpace . All Objects in this figure are organised using Organizes References and have the ObjectType FolderType as type definition. Figure 1 - Standard AddressSpace structure The remainder of this provides descriptions
• 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
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 Views
  View Nodes to the " Views " standard Object . All View Nodes in the AddressSpace shall be referenced by this Node , either directly or indirectly. That is, the " Views
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.4 Objects
  View Node can be used as entry point into a subset of the AddressSpace containing Objects and Variables and thus the " Objects " Object can also reference View Nodes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.9 DataTypes
  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 ... grouping purposes. The intent is that all DataTypes of the Server exposed in the AddressSpace are accessible following hierarchical References starting from the "DataTypes" Object . However, this
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.4.3 Optional
  Optional The ModellingRule Optional is defined in OPC 10000-3 . Its representation in the AddressSpace , the " Optional " Object, is formally defined in Table 115 . Table 115 - Optional definition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.4.4 OptionalPlaceholder
  OptionalPlaceholder The ModellingRule OptionalPlaceholder is defined in OPC 10000-3 . Its representation in the AddressSpace , the " OptionalPlaceholder " Object, is formally defined in Table 116 . Table 116 - OptionalPlaceholder definition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.4.5 MandatoryPlaceholder
  MandatoryPlaceholder The ModellingRule MandatoryPlaceholder is defined in OPC 10000-3 . Its representation in the AddressSpace , the " MandatoryPlaceholder " Object, is formally defined in Table 117 . Table 117 - MandatoryPlaceholder definition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  9.1 GetMonitoredItems
  context of the Session that owns the Subscription . Table 118 specifies the AddressSpace representation for the GetMonitoredItems Method . Table 118 - GetMonitoredItems Method AddressSpace definition Attribute Value BrowseName GetMonitoredItems References NodeClass
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  9.2 ResendData
  context of the Session that owns the Subscription . Table 119 specifies the AddressSpace representation for the ResendData Method . Table 119 - ResendData Method AddressSpace definition Attribute Value BrowseName ResendData References NodeClass
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  9.3 SetSubscriptionDurable
  context of the Session that owns the Subscription . Table 120 specifies the AddressSpace representation for the SetSubscriptionDurable Method . Table 120 - SetSubscriptionDurable Method AddressSpace definition Attribute Value BrowseName SetSubscriptionDurable References NodeClass
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  9.4 RequestServerStateChange
  InvalidState The requested state was not accepted by the server Table 121 specifies the AddressSpace representation for the RequestServerStateChange Method . Table 121 - RequestServerStateChange Method AddressSpace definition Attribute Value BrowseName RequestServerStateChange
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.1 References
  References This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 122 . Table 122 - References ReferenceType Attributes Value BrowseName References InverseName -- Symmetric
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.2 HierarchicalReferences
  HierarchicalReferences This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 123 . Table 123 - HierarchicalReferences ReferenceType Attributes Value BrowseName HierarchicalReferences InverseName InverseHierarchicalReferences
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.3 NonHierarchicalReferences
  NonHierarchicalReferences This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 124 . Table 124 - NonHierarchicalReferences ReferenceType Attributes Value BrowseName NonHierarchicalReferences InverseName -- Symmetric
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.4 HasChild
  HasChild This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 125 . Table 125 - HasChild ReferenceType Attributes Value BrowseName HasChild InverseName ChildOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.5 Aggregates
  Aggregates This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 126 . Table 126 - Aggregates ReferenceType Attributes Value BrowseName Aggregates InverseName AggregatedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.6 Organizes
  Organizes This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 127 . Table 127 - Organizes ReferenceType Attributes Value BrowseName Organizes InverseName OrganizedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.7 HasComponent
  HasComponent This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 128 . Table 128 - HasComponent ReferenceType Attributes Value BrowseName HasComponent InverseName ComponentOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.8 HasOrderedComponent
  HasOrderedComponent This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 129 . Table 129 - HasOrderedComponent ReferenceType Attributes Value BrowseName HasOrderedComponent InverseName OrderedComponentOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.9 HasProperty
  HasProperty This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 130 . Table 130 - HasProperty ReferenceType Attributes Value BrowseName HasProperty InverseName PropertyOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.10 HasSubtype
  HasSubtype This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 131 . Table 131 - HasSubtype ReferenceType Attributes Value BrowseName HasSubtype InverseName SubtypeOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.11 HasModellingRule
  HasModellingRule This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 132 . Table 132 - HasModellingRule ReferenceType Attributes Value BrowseName HasModellingRule InverseName ModellingRuleOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.12 HasTypeDefinition
  HasTypeDefinition This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 133 . Table 133 - HasTypeDefinition ReferenceType Attributes Value BrowseName HasTypeDefinition InverseName TypeDefinitionOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.13 HasEncoding
  HasEncoding This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 134 . Table 134 - HasEncoding ReferenceType Attributes Value BrowseName HasEncoding InverseName EncodingOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.14 HasEventSource
  HasEventSource This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 135 . Table 135 - HasEventSource ReferenceType Attributes Value BrowseName HasEventSource InverseName EventSourceOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.15 HasNotifier
  HasNotifier This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 136 . Table 136 - HasNotifier ReferenceType Attributes Value BrowseName HasNotifier InverseName NotifierOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.16 GeneratesEvent
  GeneratesEvent This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 137 . Table 137 - GeneratesEvent ReferenceType Attributes Value BrowseName GeneratesEvent InverseName GeneratedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.17 AlwaysGeneratesEvent
  AlwaysGeneratesEvent This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 138 . Table 138 - AlwaysGeneratesEvent ReferenceType Attributes Value BrowseName AlwaysGeneratesEvent InverseName AlwaysGeneratedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.18 HasArgumentDescription
  HasArgumentDescription This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 139 . Table 139 - HasArgumentDescription ReferenceType Attributes Value BrowseName HasArgumentDescription InverseName ArgumentDescriptionOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.19 HasOptionalInputArgumentDescription
  HasOptionalInputArgumentDescription This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 140 . Table 140 - HasOptionalInputArgumentDescription ReferenceType Attributes Value BrowseName HasOptionalInputArgumentDescription InverseName OptionalInputArgumentDescriptionOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.20 HasInterface
  HasInterface This standard ReferenceType is defined in OPC 10000-3. Its representation in the AddressSpace is specified in Table 141 . Table 141 - HasInterface ReferenceType Attributes Value BrowseName HasInterface InverseName InterfaceOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.21 HasAddIn
  HasAddIn This standard ReferenceType is defined in OPC 10000-3. Its representation in the AddressSpace is specified in Table 142 . Table 142 - HasAddIn ReferenceType Attributes Value BrowseName HasAddIn InverseName AddInOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.22 IsDeprecated
  IsDeprecated This standard ReferenceType is defined in OPC 10000-3. Its representation in the AddressSpace is specified in Table 143 . Table 143 - IsDeprecated ReferenceType Attributes Value BrowseName IsDeprecated InverseName Deprecates
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.23 HasStructuredComponent
  HasStructuredComponent This standard ReferenceType is defined in OPC 10000-3. Its representation in the AddressSpace is specified in Table 144 . Table 144 - HasStructuredComponent ReferenceType Attributes Value BrowseName HasStructuredComponent InverseName IsStructuredComponentOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.24 AssociatedWith
  AssociatedWith This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 145 . Table 145 - AssociatedWith ReferenceType Attributes Value BrowseName AssociatedWith InverseName -- Symmetric
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.25 HasKeyValueDescription
  Variable with the DataType KeyValuePair . The representation of the HasKeyValueDescription ReferenceType in the AddressSpace is specified in Table 146 . Table 146 - HasKeyValueDescription ReferenceType Attributes Value BrowseName HasKeyValueDescription InverseName KeyValueDescriptionOf Symmetric
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.26 UsesDataTypeRefinement
  UsesDataTypeRefinement This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 147 . Table 147 - UsesDataTypeRefinement definition Attributes Value BrowseName UsesDataTypeRefinement InverseName DataTypeRefinementUsedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.27 HasFieldDescription
  HasFieldDescription This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 148 . Table 148 - HasFieldDescription definition Attributes Value BrowseName HasFieldDescription InverseName FieldDescriptionOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.28 HasFieldDescriptionSetMandatory
  HasFieldDescriptionSetMandatory This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 149 . Table 149 - HasFieldDescriptionSetMandatory definition Attributes Value BrowseName HasFieldDescriptionSetMandatory InverseName FieldDescriptionSetMandatoryOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.29 IsDisabledOptionalField
  IsDisabledOptionalField This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 150 . Table 150 - IsDisabledOptionalField definition Attributes Value BrowseName IsDisabledOptionalField InverseName DisabledOptionalFieldOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.30 UsesSubtypeRestriction
  UsesSubtypeRestriction This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 151 . Table 151 - UsesSubtypeRestriction definition Attributes Value BrowseName UsesSubtypeRestriction InverseName SubtypeRestrictionUsedBy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.31 AllowedSubtype
  AllowedSubtype This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 152 . Table 152 - AllowedSubtype definition Attributes Value BrowseName AllowedSubtype InverseName AllowedSubtypeOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  11.32 HasDataTypeRefinement
  HasDataTypeRefinement This standard ReferenceType is defined in OPC 10000-3 . Its representation in the AddressSpace is specified in Table 152 . Table 153 - HasDataTypeRefinement definition Attributes Value BrowseName HasDataTypeRefinement InverseName DataTypeRefinementOf
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2 DataTypes defined in OPC 10000-3
  defines a set of DataTypes . Their representations in the AddressSpace are defined in the following subclauses
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.1 BaseDataType
  BaseDataType The representation in the AddressSpace of the BaseDataType DataType is defined in Table 154 . Table 154 - BaseDataType definition Attributes Value BrowseName BaseDataType IsAbstract TRUE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.2 Boolean
  Boolean The representation in the AddressSpace of the Boolean DataType is specified in Table 155 . Table 155 - Boolean definition Attributes Value BrowseName Boolean IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3 ByteString
  ByteString The representation in the AddressSpace of the ByteString DataType is defined in Table 156 . Table 156 - ByteString definition Attributes Value BrowseName ByteString IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.1 AudioDataType
  AudioDataType The representation in the AddressSpace of the AudioDataType DataType is defined in Table 157 . Table 157 - AudioDataType definition Attributes Value BrowseName AudioDataType IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.2 Image
  Image The representation in the AddressSpace of the Image DataType is defined in Table 158 . Table 158 - Image definition Attributes Value BrowseName Image IsAbstract TRUE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.3 ImageBMP
  ImageBMP The representation in the AddressSpace of the ImageBMP DataType is defined in Table 159 . Table 159 - ImageBMP definition Attributes Value BrowseName ImageBMP IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.4 ImageGIF
  ImageGIF The representation in the AddressSpace of the ImageGIF DataType is defined in Table 160 . Table 160 - ImageGIF definition Attributes Value BrowseName ImageGIF IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.5 ImageJPG
  ImageJPG The representation in the AddressSpace of the ImageJPG DataType is defined in Table 161 . Table 161 - ImageJPG definition Attributes Value BrowseName ImageJPG IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.3.6 ImagePNG
  ImagePNG The representation in the AddressSpace of the ImagePNG DataType is defined in Table 162 . Table 162 - ImagePNG definition Attributes Value BrowseName ImagePNG IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.4 DateTime
  DateTime The representation in the AddressSpace of the DateTime DataType is defined in Table 163 . Table 163 - DateTime definition Attributes Value BrowseName DateTime IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.4.1 UtcTime
  UtcTime The representation in the AddressSpace of the UtcTime DataType is defined in Table 164 . Table 164 - UtcTime definition Attributes Value BrowseName UtcTime IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.5 Enumeration
  Enumeration The representation in the AddressSpace of the Enumeration DataType is defined in Table 165 . Table 165 - Enumeration definition Attributes Value BrowseName Enumeration IsAbstract TRUE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.5.1 IdType
  IdType The representation in the AddressSpace of the IdType DataType is defined in Table 166 . Table 166 - IdType definition Attributes Value BrowseName IdType IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.5.2 NodeClass
  NodeClass The representation in the AddressSpace of the NodeClass DataType is defined in Table 167 . Table 167 - NodeClass definition Attributes Value BrowseName NodeClass IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.5.3 StructureType
  StructureType The representation in the AddressSpace of the StructureType DataType is defined in Table 168 . Table 168 - StructureType definition Attributes Value BrowseName StructureType IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.6 Guid
  Guid The representation in the AddressSpace of the Guid DataType is specified in Table 169 . Table 169 - Guid definition Attributes Value BrowseName Guid IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.7 LocalizedText
  LocalizedText The representation in the AddressSpace of the LocalizedText DataType is specified in Table 170 . Table 170 - LocalizedText definition Attributes Value BrowseName LocalizedText IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.8 NodeId
  NodeId The representation in the AddressSpace of the NodeId DataType is specified in Table 171 . Table 171 - NodeId definition Attributes Value BrowseName NodeId IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9 Number
  Number The representation in the AddressSpace of the Number DataType is defined in Table 172 . Table 172 - Number definition Attributes Value BrowseName Number IsAbstract TRUE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.1 Decimal
  Decimal The representation in the AddressSpace of the Decimal DataType is defined in Table 173 . Table 173 - Decimal definition Attributes Value BrowseName Decimal IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.2 Double
  Double The representation in the AddressSpace of the Double DataType is defined in Table 174 . Table 174 - Double definition Attributes Value BrowseName Double IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.3 Duration
  Duration The representation in the AddressSpace of the Duration DataType is defined in Table 175 . Table 175 - Duration definition Attributes Value BrowseName Duration IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.4 Float
  Float The representation in the AddressSpace of the Float DataType is defined in Table 176 . Table 176 - Float definition Attributes Value BrowseName Float IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.5 Integer
  Integer The representation in the AddressSpace of the Integer DataType is defined in Table 177 . Table 177 - Integer definition Attributes Value BrowseName Integer IsAbstract TRUE References NodeClass BrowseName DataType TypeDefinition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.2.9.6 Int16
  Int16 The representation in the AddressSpace of the Int16 DataType is defined in Table 178 . Table 178 - Int16 definition Attributes Value BrowseName Int16 IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition