Search

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

68 result(s) for ObjectTypes

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

4.4.3 Integrated object model

subclassed. They also may be common or they may be system-specific. ObjectTypes may be defined by standards organizations, vendors, or end-users. This model allows data, Alarms and Events
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

9.4.2 Certificate management for developers

manner; see OPC 10000-12 for additional details. OPC 10000-12 also describes other ObjectTypes that can be used to expose this configuration and manage the all aspect
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.1 Overview

AddressSpace representing the AddressSpace concepts. Clause 6 defines details on the type model for ObjectTypes and VariableTypes . Standard ReferenceTypes , DataTypes and EventTypes are defined in Clauses
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.6.3 Subtyping

subtyping of type definitions. The subtyping rules are defined in Clause 6 . Subtyping of ObjectTypes and VariableTypes allows: Clients that only know the supertype to handle an instance
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.7.2 EventTypes

Server are exposed in the AddressSpace of a Server . EventTypes are represented as ObjectTypes in the AddressSpace and do not have a special NodeClass associated to them
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.1 Overview

Overview OPC UA defines a type model supporting one object-oriented type hierarchy for ObjectTypes . Although the specification does not restrict those hierarchies to be single inheritance (i.e. a type
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.2 Interface Model

Interface Model Interfaces are ObjectTypes that represent a generic feature (functionality), assumed to be usable by different ObjectTypes or Objects . The Interface model specifies the rules and mechanisms to achieve ... accessible browsing HierarchicalReferences starting from this Node . Rules for the definition of Interfaces : Interface ObjectTypes shall be abstract subtypes of the BaseInterfaceType ObjectType . InstanceDeclarations on an Interface shall only have
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.3 AddIn model

adding a Reference to the AddIn instance. There are no restrictions for AddIn ObjectTypes and there is no special supertype for AddIns . To identify instances as an AddIn , the HasAddIn
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.2 ObjectType NodeClass

ObjectType NodeClass ObjectTypes provide definitions for Objects . ObjectTypes are defined using the ObjectType NodeClass , which is specified in Table 12 . Table 12 - ObjectType NodeClass Name Use Data Type Description Attributes ... this type is instantiated, is specified in 6.4 . HasSubtype 0..* HasSubtype References identify ObjectTypes that are subtypes of this type. The inverse Reference identifies the parent type of this type
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.4 Client-side creation of Objects of an ObjectType

shall exist for each Object of an ObjectType . In addition to the AddNodes Service ObjectTypes may have a special Method with the BrowseName " Create ". This Method is used
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

context of an Object . However, complex DataVariables may expose other DataVariables , and ObjectTypes and complex VariableTypes may also contain DataVariables . Therefore each DataVariable shall be the TargetNode of at least
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.1 Overview

Overview In the remainder of Clause 6 the type model of ObjectTypes and VariableTypes is defined regarding subtyping and instantiation
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.1 Overview

described in 5.8.3 . The remainder of 6.3 specify subtyping rules for single inheritance on ObjectTypes and VariableTypes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.5 Changing Type Definitions that are already used

already used There is no behaviour specified regarding subtypes and instances when changing ObjectTypes and VariableTypes . It is Server -dependent, if those changes are reflected on the subtypes and instances
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.7 HasComponent ReferenceType

part of the SourceNode . This ReferenceType is used to relate Objects or ObjectTypes with their containing Objects , DataVariables , and Methods . This ReferenceType is also used to relate complex Variable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.15 GeneratesEvent

semantic of this ReferenceType is to identify the types of Events instances of ObjectTypes or VariableTypes may generate and Methods may generate on each Method call. The SourceNode of References
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

A.3 ObjectTypes

ObjectTypes Subclause 5.5.1 states: " Objects are used to represent systems, system components, real-world objects, and software objects." Therefore ObjectTypes should be used if a type definition ... those ObjectTypes is useful (see A.2 ). From a more abstract point of view Objects are used to group Variables and other Objects in the AddressSpace . Therefore ObjectTypes should be used
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.1 Background

also marked as <<TypeExtension>>. In addition, the domain model contains ObjectTypes , VariableTypes etc. represented as UML objects (see Figure B.1 ). The OPC Foundation specifies not only
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

B.3.4 Object and ObjectType

B.3.4 Object and ObjectType Objects and ObjectTypes are shown in Figure
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.2 Used type model

this Figure, the OPC UA notation is used for all References to ObjectTypes , Variables , Properties and subtypes. Additionally, supported References are contained in an inner box. The actual references only
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.1 General

ObjectType can be extended with additional components, this standard allows extending the standard ObjectTypes defined in this document with additional components. Thereby, it is possible to express the additional information ... 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 to restrict the components
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.2 BaseObjectType

more specific type, if possible. This ObjectType is the base ObjectType and all other ObjectTypes shall either directly or indirectly inherit from it. However, it might not be possible
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
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 ... Only Organizes References are used to relate Objects and ObjectTypes to the " ObjectTypes " standard Object . The " ObjectTypes " Object shall not reference any other NodeClasses . Figure
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.2.10 EventTypes

EventTypes defined in Clause 6 . Only Organizes References are used to relate Objects and ObjectTypes to the " EventTypes " standard Object . The " EventTypes " Object shall not reference
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

8.2.11 InterfaceTypes

Interfaces . Figure 8 illustrates the structure beneath this Node showing some of the standard ObjectTypes defined in clause 6. Only Organizes References are used to relate Objects and Interfaces
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.1 Overview

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 into account
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

6.1 General

General This model supplements the information of EngineeringUnit Properties , providing comprehensive ObjectTypes for quantities and units and their linkage. See 5.6.4 how EngineeringUnit Properties reference instances of these ObjectTypes
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.3 Event categories

Server are represented in the UA Server as ObjectTypes which are subtypes of BaseEventType . The BrowseName and DisplayName of the ObjectType Node for Simple and Tracking Event Types are constructed
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.4 Event attributes

Server as Variables which are targets of HasProperty Reference s from the ObjectTypes which represent the Event Categories. The BrowseName and DisplayName are the description for the Event Attribute
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

4.1 General

these Functions . Together Methods and Programs complement the other OPC UA Services and ObjectTypes to facilitate the operation of an automation environment using a client-server hierarchy. Figure 1 - Automation
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.1 Overview

manage the keys for the NetworkMessages sent by this Publisher . Figure 41 depicts the ObjectTypes and their components used to represent the SKS functionality in the PublishSubscribe Object. Figure
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

General Figure 42 depicts the ObjectTypes of the message and transport protocol mapping independent part of the PubSub configuration model, their main components and their relations. Figure 42 - PubSub configuration ... used to subscribe one DataSet . Figure 44 depicts the information flow and the related ObjectTypes from the PubSub Information M odel. The boxes in the lower part of the figure
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.1 Overview

different source options and the parameters for sending of DataSetMessages . Figure 46 depicts the ObjectTypes of the published DataSet model and their components. Figure 46 - Published DataSet overview Instances
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.1 General

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

4.4.6 FiniteStateMachineType

FiniteStateMachineType may have sub-state-machines which are represented as instances of StateMachineType ObjectTypes . Each State shall have a HasSubStateMachine Reference to the StateMachineType Object which represents the child States
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

5 AliasNames Information Model overview

Information Model overview The AliasNames functionality (illustrated in Figure 1 ) defines a number of ObjectTypes , Methods , DataTypes and References . Figure 2 illustrates an example of the Object model defined
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

4.1 General

defines the possible Permissions and the representation as Node Attributes . Figure 1 depicts the ObjectTypes , Objects and their components used to represent the Role management. Figure 1 - Role management overview
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

5.1 General

management of a user list in the OPC UA Server. Figure 2 depicts the ObjectTypes , Objects and their components used to represent the user management. The ServerConfiguration Object is defined
OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference

4.1 General

reference external dictionaries like IEC Common Data Dictionary or ECLASS. It defines ObjectTypes , VariableTypes and a ReferenceType and explains how they should be used. The ObjectTypes are used to represent
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

4.2 Usage of OPC UA Interfaces

that a future version of the BNM will define a collection of network related ObjectTypes
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

6.1 Overview

Overview This specification defines two main ObjectTypes : an instance of CalendarType represent a globally defined set of dates that can be referenced by schedule Objects ; an instance of ScheduleType represent
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

10.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Vendor specific instances A Server provides
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

4.1 Overview

additional examples of LogObjects and possible Client uses and Server implementations. This specification defines ObjectTypes , EventTypes , ConditionClass and instances (see Figure 2 ). Not all of the illustrated types/instances are required
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

basic building blocks provided in OPC 10000-5 and utilises Interfaces and ObjectTypes described in OPC 10000-100 . This base Information Model can, in turn, be utilised and extended
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.1 Overview

conceptual overview of how Connections are established by a ConnectionManager and the main ObjectTypes used in this process, see 5.5 . This document defines the core functionality of a ConnectionManager with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.2 Generation, deployment, and modification

required data model for logical connection configuration information, represented by the ConnectionConfigurationSetType and additional ObjectTypes it utilises. The ConnectionManagerType (see 6.7 ) exposes configuration information related to the establishment of logical
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.1 OPC UA FX ObjectTypes overview

ObjectTypes overview This document defines several ObjectTypes that can be used to create an OPC UA FX Information Model . It also specifies a number of Interfaces that can be applied ... Information Models , see Annex B . For an overview of the main OPC UA FX ObjectTypes , see Figure 17 . Figure 17 - Overview of OPC UA FX Information Model Since
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

specific types A Server may provide vendor-specific types, such as types derived from ObjectTypes defined in this document in a vendor-specific namespace. Optional Vendor-specific instances A Server
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.2 Creating a new model based on OPC UA FX

illustrated in Figure B.1 . Objects can be derived from OPC UA FX base ObjectTypes to create new ObjectTypes . Figure B.1 - New Subtype model based on OPC UA FX model
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

B.1.5 UA SystemUnitClass Library

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

C.1.4 DI SystemUnitClass Library

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

D.1.3 OPC UA FX AttributeType Libraries

opcfoundation.org/UA/FX/Data " define the SystemUnitClasses that correspond to their equivalent OPC UA FX ObjectTypes and VariableTypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

E.4 Safety SystemUnitClass Library

opcfoundation.org/UA/Safety/" defines the SystemUnitClasses that correspond to their equivalent OPC UA Safety ObjectTypes and VariableTypes
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.1 General

General Figure 1 depicts the main ObjectTypes of the base device model and their relationship. The drawing is not intended to be complete. For the sake of simplicity only ... overall structure. Figure 1 - Device model overview The boxes in this drawing show the ObjectTypes used in this specification as well as some elements from other specifications that help understand
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

7.2 LockingServices Type

Properties with status information. This section describes the common semantic. The lock-owner ObjectTypes will often extend these semantics. Figure 31 shows the LockingServicesType definition. It is formally defined ... calling the InitLock Method and removed by calling the ExitLock Method . The lock-owner ObjectTypes can define mechanisms that automatically initiate and remove a lock. A lock request will
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

C.5 Guidelines on how to use functionality in companion specifications

software update in 8 , the companion specification is not required to derive from the ObjectTypes defined in this specification. Instead of, it can just implement the Interfaces ... AddIns in their ObjectTypes and build an ObjectType -Hierarchy independent of this specification. In Figure C.5 , an example is given. The companion specification defines an ObjectType hierarchy, and uses
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

have the TypeDefinition 2: ComponentType , 2: DeviceType , or a subtype of one of those ObjectTypes and thus containing the identification Properties defined in OPC 10000-100 . Usage of 2: IVendorNameplateType
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.5.2 DocumentationLinksType

DocumentationLinksType The DocumentationLinksType is an AddIn and should be applied to Objects or ObjectTypes representing Assets. It is formally defined in Table 29 . Table 29 - DocumentationLinksType Definition Attribute Value BrowseName
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

16.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Optional Vendor specific instances A Server
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

8.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Optional Vendor specific instances A Server
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.1.1 Overview

Variables are not predefined by the Interface , but added by the concrete Objects or ObjectTypes implementing the Interface . In Figure 10 , an example is given. The MyStatisticsType is implementing IStatisticsType
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.2 IAggregateStatisticsType

subtype of the IStatisticsType Interface . The statistical data managed by Objects or ObjectTypes implementing this Interface is not rolling over, i.e. all data from the start of tracking the statistical
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

6.2.3 IRollingStatisticsType

subtype of the IStatisticsType Interface . The statistical data managed by Objects or ObjectTypes implementing this Interface is rolling over, i.e. only a certain amount of data is considered for statistical
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

9.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Optional Vendor specific instances A Server
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

10.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Optional Vendor specific instances A Server
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.3 Companion Specifications

companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

12.2 Handling of OPC UA Namespaces

Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. Vendor specific instances A Server provides