Search

200 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
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  6.3.1 General
  Semantic of CDT that is mapped to CC DataType may be defined in ObjectTypes or VariableTypes
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  6.1 General
  Information Model is a representation of the ISA-95 data model in OPC Methods , ObjectTypes , VariableTypes , DataTypes and ReferenceTypes . This model generates standard types. All ISA-95 types will ... ISA95" The following conventions apply to ObjectType , VariableType and DataType naming: All ObjectTypes include "ObjectType" as part of the name All DataTypes that are structures include
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  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-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  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-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  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. Vendor specific instances A Server provides
• OPC-10101 – OPC UA for WoT Binding
  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-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  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-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.4 Introduction to OPC UA Devices
  base for the IEC 61131-3 information model. The Devices information model specifies different ObjectTypes and procedures used to represent Devices and related components like the communication infrastructure ... Figure 8 - OPC UA Devices Example The SupportedTypes Folder can contain different subsets of ObjectTypes for different instances of the ModularControlerType depending on their current configuration since the list contains
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.3 Introductory Example
  body containing the algorithm to be executed. These data are represented by OPC UA ObjectTypes derived from the ObjectType CtrlFunctionBlockType (see Figure 11 ). To start
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  5 Use cases
  Configurations, Ctrl Resources, Ctrl Tasks, Ctrl Programs, Ctrl Function Blocks, Ctrl Variables , and their ObjectTypes represented in the OPC UA Server. Example 1: In a brewery, several tanks ... Resources, Ctrl Tasks, Ctrl Programs, Ctrl Function Blocks, Ctrl Functions, Ctrl Variables , and their ObjectTypes into the OPC UA Server. Example: The Ctrl Program of a machine tool shall
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  6 IEC 61131-3 Information Model overview
  Information Model overview Figure 13 depicts the main ObjectTypes of this specification and their relationships. The drawing is not intended to be complete. For the sake of simplicity only ... Information Model . Figure 13 - OPC UA IEC 61131‑3 ObjectTypes Overview The boxes in this drawing show the ObjectTypes used in this specification as well as some elements from other
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  10.1 DeviceSet as entry point for engineering applications (Mandatory)
  entry point for engineering applications (Mandatory) The full object component hierarchy based on Object Types defined in this specification shall be provided as components of the DeviceSet Object defined
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  10.2 CtrlTypes Folder for server specific Object Types (Mandatory)
  CtrlTypes Folder for server specific Object Types (Mandatory) The server specific ObjectTypes like vendor specific Ctrl Configuration types or user specific Ctrl Function Block types can be found
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.3 Companion Specifications
  companion specification for an industry specific vertical market describes an InformationModel by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market. Table 3 contains
• OPC-30020 – MDIS OPC UA Companion Specification
  6.1.16 MDISAggregateObjectType
  MDISAggregateObjectType The MDISAggregateObjectType (see 6.12.2 ) is an abstract type that all aggregate ObjectTypes shall be derived from. This ObjectType allows Clients to easily identify aggregate Objects . For more information about
• OPC-30020 – MDIS OPC UA Companion Specification
  6.2.1 Overview
  MDIS. This Object is intended to be the base object for all other MDIS ObjectTypes (see Figure 10 for an overview of inherited types) Figure 9 - MDISBaseObjectType Figure 10 - Base
• OPC-30020 – MDIS OPC UA Companion Specification
  6.12.1 Overview
  MDIS. This Object is intended to be the base object for all aggregate ObjectTypes . See section 10.5 for additional details on data aggregation. Figure 21 - MDISAggregateObjectType
• OPC-30020 – MDIS OPC UA Companion Specification
  9.1 HasInterlock ReferenceType
  subtype of MDISAggregateObjectType that is being used for aggregation or one of these ObjectTypes . Table 116 - HasInterlock Reference Attributes Value BrowseName HasInterlock InverseName InterlockOf Symmetric False IsAbstract False References NodeClass
• OPC-30020 – MDIS OPC UA Companion Specification
  10.5.2 Object Collection, Aggregation and Extension Definition
  minimise variability, when aggregating or extending objects only instances of the following VariableTypes and ObjectTypes shall be used: Standard MDIS Objects defined in section 6 . BaseDataVariableType DiscreteItemType (Variable) AnalogItemType (Variable ... MDIS parent No No 1) Define new ObjectType with any MDIS parent (subtyping MDIS ObjectTypes - MDISValveObjectType , MDISChokeObjectType , MDISElectricChokeObjectType, MDISMotorObjectType, MDISCIMVObjectType, MDISDigitalInstrumentObjectType , MDISInstrumentObjectType , MDISDiscreteInstrumentObjectType or any subtype of these types
• OPC-30020 – MDIS OPC UA Companion Specification
  10.5.3 Object Creation
  Object Creation ObjectTypes that are not an aggregated, extended or collection ObjectType can only be defined by the MDIS organisation. If a vendor (or group of vendors) determines that
• OPC-30020 – MDIS OPC UA Companion Specification
  14.2.2 Server
  Server supports aggregate Objects based on MDISAggregateObjectType . Server MDIS Extension The Server defines new ObjectTypes that are extensions of the existing MDIS ObjectTypes ( MDISValveObjectType , MDISChokeObjectType , MDISDigitalInstrumentObjectType , MDISDiscreteInstrumentObjectType , MDISInstrumentObjectType
• OPC-30020 – MDIS OPC UA Companion Specification
  15.2 Handling of OPC UA Namespaces
  Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this specification in a vendor-specific namespace. Optional Vendor specific instances A Server
• OPC-30020 – MDIS OPC UA Companion Specification
  B.1 Introduction
  Introduction The following section provides sample sequence diagrams for each of the MDIS ObjectTypes . These sample sequences are not mandated or the only valid variant
• OPC-30020 – MDIS OPC UA Companion Specification
  D.3 Signature File Transfer
  specified on a project basis. The items required are provided as part the individual ObjectTypes . This functionality is optional and covered in a separate profile
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  5.1 Modelling concepts
  logically grouped or a group of BACnet properties is used in different OPC UA ObjectTypes across the type hierarchy. Figure 5 shows an example for type hierarchies and inheritance used
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  5.2 Model Overview
  Model Overview Figure 8 depicts the main ObjectTypes of the OPC UA for BACnet information model and their relationship. The drawing is not intended to be complete. Figure 8 - BACnet ... Model Overview The boxes in this drawing show the ObjectTypes used in this specification as well as some elements from other specifications. The upper grey box shows
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.1.1 General
  General This ObjectType defines the super type for all OPC UA ObjectTypes representing BACnet object types in an OPC UA Address Space . It introduces two properties common for all BACnet ... types. Figure 10 shows an overview for the BACnetObjectType with its Properties and related ObjectTypes . It is formally defined in Table 8 . Figure 10 - BACnetObjectType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.3.1 General
  Device . Figure 11 shows an overview for the BACnetDeviceType with its Properties and related ObjectTypes . It is formally defined in Table 10 . Figure 11 - BACnetDeviceType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.4.1 General
  General This OPC UA ObjectType defines the super type for all OPC UA ObjectTypes that represent BACnet Analog object types in an OPC UA Address Space . Figure 13 shows ... overview for the BACnetAnalogType with its Properties and related ObjectTypes . It is formally defined in Table 12 . Figure 13 - BACnetAnalogType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.5.1 General
  system. Figure 14 shows an overview for the BACnetAnalogInputType with its Properties and related ObjectTypes . It is formally defined in Table 14 . Figure 14 - BACnetAnalogInputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.6.1 General
  signal. Figure 15 shows an overview for the BACnetAnalogOutput with its Properties and related ObjectTypes . It is formally defined in Table 15 . Figure 15 - BACnetAnalogOutputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.7.1 General
  Device . Figure 16 shows an overview for the BACnetAnalogValueType with its Properties and related ObjectTypes . It is formally defined in Table 16 . Figure 16 - BACnetAnalogValueType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.8.1 General
  General This OPC UA ObjectType defines the super type for all OPC UA ObjectTypes that represent BACnet Binary object types in an OPC UA Address Space . Figure 17 shows ... overview for the BACnetBinaryType with its Properties and related ObjectTypes . It is formally defined in Table 17 . Figure 17 - BACnetBinaryType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.9.1 General
  system. Figure 18 shows an overview for the BACnetBinaryInputType with its Properties and related ObjectTypes . It is formally defined in Table 18 . Figure 18 - BACnetBinaryInputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.10.1 General
  signals. Figure 19 shows an overview for the BACnetBinaryOutputType with its Properties and related ObjectTypes . It is formally defined in Table 20 . Figure 19 - BACnetBinaryOutputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.11.1 General
  states. Figure 20 shows an overview for the BACnetBinaryValueType with its Properties and related ObjectTypes . It is formally defined in Table 22 . Figure 20 - BACnetBinaryValueType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.12.1 General
  General This OPC UA ObjectType defines the super type for all OPC UA ObjectTypes that represent BACnet MultiState object types in an OPC UA Address Space . Figure 21 shows ... overview for the BACnetMultiStateType with its Properties and related ObjectTypes . It is formally defined in Table 24 . Figure 21 - BACnetMultiStateType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.13.1 General
  algorithm. Figure 22 shows an overview for the BACnetMultiStateInputType with its Properties and related ObjectTypes . It is formally defined in Table 25 . Figure 22 - BACnetMultiStateInputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.14.1 General
  defined. Figure 23 shows an overview for the BACnetMultiStateOutputType with its Properties and related ObjectTypes . It is formally defined in Table 27 . Figure 23 - BACnetMultiStateOutputType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.15.1 General
  defined. Figure 24 shows an overview for the BACnetMultiStateValueType with its Properties and related ObjectTypes . It is formally defined in Table 29 . Figure 24 - BACnetMultiStateValueType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.16.1 General
  specification. Figure 25 shows an overview for the BACnetCalendarType with its Properties and related ObjectTypes . It is formally defined in Table 31 . Figure 25 - BACnetCalendarType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.17.1 General
  effect. Figure 26 shows an overview for the BACnetScheduleType with its Properties and related ObjectTypes . It is formally defined in Table 32 . Figure 26 - BACnetScheduleType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.18.1 General
  loop. Figure 27 shows an overview for the BACnetLoopType with its Properties and related ObjectTypes . It is formally defined in Table 33 . Figure 27 - BACnetLoopType overview (example PID loop
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.19.1 General
  device. Figure 28 shows an overview for the BACnetEventEnrollmentType with its Properties and related ObjectTypes . It is formally defined in Table 35 . Figure 28 - BACnetEventEnrollmentType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.20.1 General
  value. Figure 29 shows an overview for the BACnetLogType with its Properties and related ObjectTypes . It is formally defined in Table 36 . Figure 29 - BACnetLogType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.21.1 General
  value. Figure 30 shows an overview for the BACnetTrendLogBaseType with its Properties and related ObjectTypes . It is formally defined in Table 38 . Figure 30 - BACnetTrendLogBaseType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.22.1 General
  Figure 31 shows an overview for the BACnetTrendLogType with its Properties and related ObjectTypes . It is formally defined in Table 39 . Figure 31 - BACnetTrendLogType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.23.1 General
  Figure 32 shows an overview for the BACnetTrendLogMultipleType with its Properties and related ObjectTypes . It is formally defined in Table 41 . Figure 32 - BACnetTrendLogMultipleType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.24.1 General
  retrieval. Figure 33 shows an overview for the BACnetEventLogType with its Properties and related ObjectTypes . It is formally defined in Table 42 . Figure 33 - BACnetEventLogType overview
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  14.2 Handling of OPC UA Namespaces
  Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this companion specification in a vendor-specific namespace. Vendor specific instances A Server
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.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. Table
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.1 General
  PackML information model is a representation of the PackML data model in OPC ObjectTypes , VariableTypes , DataTypes and ReferenceTypes . This model generates standard types. All PackML types will be defined ... this model. The following conventions apply to ObjectType , VariableType and DataType naming: All ObjectTypes include " ObjectType " as part of the name All StateMachines will end in "StateMachine
• OPC-30060 – OPC UA for Tobacco Machine Communication
  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-30060 – OPC UA for Tobacco Machine Communication
  14.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-30081 – OPC UA for Process Automation Devices - PA-DIM™
  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-30081 – OPC UA for Process Automation Devices - PA-DIM™
  12.2 Handling of OPC UA Namespaces
  types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  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-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  14.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-30100 – OPC UA for SERCOS Devices
  5.1 General
  General Figure 2 depicts the main ObjectTypes of the Sercos device model and their relationships. The drawing is not intended to be complete. For simplicity only a few components ... this drawing are according to the OPC UA symbol elements. Figure 2 shows the ObjectTypes used in this specification as well as some elements from other specifications that help understand
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  15.6 Handling of OPC UA namespaces
  types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific
• OPC-30140 – OPC UA for PROFINET
  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-30141 – OPC UA for PROFIenergy
  4.1.2 Standby Management
  time consuming. Standby Management is made available for OPC UA Clients with the ObjectTypes defined in chapter 8.1 " Standby Management ". Status information functionality of Standby Management provides information
• OPC-30141 – OPC UA for PROFIenergy
  4.1.3 Energy Measurement
  details). Energy Measurement is made available for OPC UA Clients with the ObjectTypes defined in chapter 8.2 " Energy Measurement
• OPC-30141 – OPC UA for PROFIenergy
  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-30141 – OPC UA for PROFIenergy
  8.1.1 EnergyStandbyManagementType
  EnergyStandbyManagementType The EnergyStandbyManagementType ObjectTypes provide access to the Standby Management functionality of one Standby Management Entity . Parallel access of Clients to the read only data shall be possible but write
• OPC-30141 – OPC UA for PROFIenergy
  13.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-30142 – OPC UA for PROFINET Remote IO
  4.3.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-30142 – OPC UA for PROFINET Remote IO
  6.2 OPC UA for RIO Channel Model
  analog Input Channels according to RIOforPA is RioPaAnalogInputConfigVariableType . Figure 9 shows all RIO Channel ObjectTypes , Process Value VariableTypes and configuration ObjectTypes which are defined in this specification to cover digital ... analog Input and Output for RIOforPA and RIOforFA. Figure 9 - RioChannel ObjectTypes The RIO Channel ObjectTypes provide additional components, Variables and configuration Properties available for access by the Client which
• OPC-30142 – OPC UA for PROFINET Remote IO
  13.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-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  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-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  6.3 Encoder Channel Configuration
  Figure 11 - Encoder Channel Configuration The "Configuration" sub-aspect contains different configuration ObjectTypes and associated Methods for configuration changes. The AxisConfig EncoderAxisConfigType Object contains configuration Properties belonging
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  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
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  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-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  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
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  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-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  6.1 Introduction to OPC UA for Drive Information Model
  Command Values", "Diagnosis" and "Axis Properties". The concrete ObjectTypes representing Axis type Drive Objects like VelocityDriveAxisType (see section 7.2 ) and FrequencyDriveAxisType (see section
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  7 OPC UA ObjectTypes
  ObjectTypes Figure 12 shows the organization of the ObjectTypes used to model Axis Objects . All Axis ObjectTypes are derived from the abstract DriveAxisType providing the functions common to all Axis ... ObjectTypes . Figure 12 - Axis ObjectTypes organization
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  7.1 DriveAxisType
  describing measurements of the Axis/DO which are of interest for monitoring (see derived Axis/DO ObjectTypes and Table 33 ) encoded as numeric data type. If the corresponding Standard Signal is configured ... motor current, torque, and the like. These limit Variables differ between concrete derived Axis ObjectTypes and are specified separately for each derived Axis ObjectType . For a description of the Variables
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  7.10 OPC UA Variable Mapping to Drive Properties
  drive properties represented by those Variables which are components of the drive ObjectTypes above. The Variables listed are components of a parent folder which belongs to the Axis Object
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  11.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-30200 – OPC UA for Commercial Kitchen Equipment
  3.4.1 Conventions for Node descriptions
  used in the ModellingRule column in the tables for the definition of ObjectTypes . Table 3 - Abbreviations for ModellingRule and AccessLevel Abbreviation Description O Modelling Rule Optional M Modelling Rule Mandatory
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  4.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-30200 – OPC UA for Commercial Kitchen Equipment
  22.3 Handling of OPC UA Namespaces
  Vendor specific types A Server may provide vendor-specific types like types derived from ObjectTypes defined in this specification in a vendor-specific namespace. Optional Vendor specific instances A Server
• OPC-30250 – OPC Unified Architecture for DEXPI
  5.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-30250 – OPC Unified Architecture for DEXPI
  12.2 Handling of OPC UA Namespaces
  types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific
• OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS
  6.1 General
  Information Model is a representation of the OPEN-SCS data model in OPC Methods, ObjectTypes , VariableTypes , DataTypes and ReferenceTypes . This model generates standard types. All OPEN-SCS types will ... OPENSCS" The following conventions apply to ObjectType , VariableType and DataType naming: All ObjectTypes include "ObjectType" as part of the name All DataTypes that are structures include
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  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-30270 – OPC UA for Asset Administration Shell (AAS)
  5.1 General rules for the mapping of the AAS metamodel to the OPC UA information model
  GenerateEvent ". Rules for Referables and Identifiables : For Referable and Identifiable separate OPC UA ObjectTypes are defined that are referenced from the corresponding ObjectTypes representing the concrete referables and identifiables ... from the predefined OPC UA IrdiDictionaryEntry or UriDictionaryEntry . This is why there are both ObjectTypes : "AASIrdiConceptDescriptionType" or "AASUriConceptDescriptionType" and not only one like for the other
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  5.3 Overview of AAS types which are directly inherited from OPC UA types
  types which are directly inherited from OPC UA types Table 8 collects all AAS ObjectTypes that are directly derived from OPC UA types. Table 8 - Basic ObjectTypes of the asset
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  6.3 AASReferenceType
  Objects of the AASReferenceType can reference another referable node instance. Instances of the following ObjectTypes can be referenced: AASAccessPermissionRuleType AASAnnotatedRelationshipElementType AASAssetAdministrationShellType AASAssetType 0:BaseEventType AASBlobType AASCapabilityType AASConceptDictionaryType AASCustomConceptDescriptionType AASFileType AASEntityType
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  6.9 Concept description
  predefined OPC UA IrdiDictionaryEntry or UriDictionaryEntry ( Figure 27 ) . This is why there are both ObjectTypes : "AASIrdiConceptDescriptionType" or "AASIriConceptDescriptionType" and not only one like for the other
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  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 companion specification in a vendor-specific namespace. O Vendor specific instances
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  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. The Cloud
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  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, as well
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  7.4.1 Overview
  Overview The following ObjectTypes are used to describe Functions of the LADS Device. LADS Device Functions can be divided into general functions, control functions (see 7.6 ) and Sensor functions
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  10.2 Handling of OPC UA Namespaces
  provide vendor-specific types in a vendor-specific Namespace , such as types derived from ObjectTypes defined in this document. Vendor-specific instances A Server provides vendor-specific instances
• OPC-34100 – OPC UA for Energy Consumption Management
  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-34100 – OPC UA for Energy Consumption Management
  6.3 Standby Management
  time consuming. Standby Management is made available for OPC UA Clients with the ObjectTypes defined in 7.2 . Status information functionality of Standby Management provides information about the current state
• OPC-34100 – OPC UA for Energy Consumption Management
  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
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  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-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  6.1 General Idea - Definition of Building Blocks
  exemplified in Figure 6 . On the right side of the figure, you can see ObjectTypes defining specific functionality like Identification. This includes the definition of a default BrowseName
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  6.3 Organization of Building Blocks
  defined in this specification are typically AddIns that can be applied to Objects or ObjectTypes representing Machines or components of Machines . The specification intentionally does not define an ObjectType representing ... domain-specific companion specification. It is to avoid that the Objects and ObjectTypes representing a MachineryItem become a large, hard to understand substructure and it is also to avoid having
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  8.1 Overview
  Figure 9 gives an overview. The Interface IMachineryItemVendorNameplateType and the ObjectType MachineryItemIdentificationType are generic ObjectTypes introduced to be used in other use cases. The AddIn MachineIdentificationType with the default name
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  18.1 Overview
  specific Objects for notifications. This specification does not define any specific EventTypes or other ObjectTypes for notifications but just the base infrastructure. Vendors or other companion specifications may define those
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  20.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-40001-2 – OPC UA for Machinery - Part 2: Process Values
  11.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-40001-3 – OPC UA for Machinery - Part 3: Job Management
  6.1 Overview
  This chapter gives an overview over the job management information model. In 6.2 , the ObjectTypes for managing job orders are described. 0 describes the integration into a MachineryItem
• OPC-40001-3 – OPC UA for Machinery - Part 3: Job Management
  11.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-40001-4 – OPC UA for Machinery - Part 4: Energy Management
  11.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-40001-101 – OPC UA for Machinery - Part 101: Result Transfer
  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
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  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-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  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. Optional Vendor specific instances A Server
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  B.10.5 Abstract example of a six-axis robot with master-slave axis and drive-slots
  slots Figure B.19 describes an example view on a server with the instances of ObjectTypes and references of a six-axis robot with master-slave axis and drive-slots described
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  B.10.6 Abstract example of a motion device system with three motion devices
  devices Figure B.20 describes an example view on a server with the instances of ObjectTypes and references of a motion device system consisting of a six-axis robot, a linear
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  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-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  7.1 CraneMotionDeviceSystemType ObjectType Definition
  organises the information model of a complete crane system using instances of the described ObjectTypes . Figure 10 - Overview CraneMotionDeviceSystemType The CraneMotionDeviceSystemType represents the entire crane and contains its various components
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  11.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-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems
  19.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-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  1 Scope
  transferred in which form is fixed in Companion Specifications. This recommendation defines common ObjectTypes for plastics and rubber machines. The intention is that ObjectTypes which can be used for several ... only once. For specific applications (e.g. connection of injection moulding machines to MES), these ObjectTypes are used by specific Companion Specifications (e.g. OPC 40077). NOTE: Not all machines will support
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  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-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  19 CycleParametersEventType
  specific namespace with vendor specific index). The specifications for specific machines provide some standardized ObjectTypes that can be included (e.g. MouldCycleParametersType as defined in 19.14 , InjectionUnitCycleParametersType as defined
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  37.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-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  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-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  13.4 Handling of OPC UA Namespaces
  types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  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-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  6 OPC Machine Vision Part 2 Information Model overview
  items (machines or components) that form it. Figure 6 - Relationship between the ObjectTypes of OPC MV Part 1 and Part 2 Figure 7 - OPC Machine Vision Part 2 Information Model ... behind this modelling approach is to enable the implementer to use instances of other ObjectTypes that are already defined in other companion specifications (future or current), when appropriate. The IVisionInfoType
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  14.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-40200 – OPC UA for Weighing Technology
  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-40200 – OPC UA for Weighing Technology
  6.2 Overview of generic Scales
  Overview of generic Scales Figure 10 shows an overview of the different ObjectTypes for the Weighing Technology devices and the references to the types from the Companion Specification for devices
• OPC-40200 – OPC UA for Weighing Technology
  13.2 Handling of OPC UA Namespaces
  types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific
• OPC-40210 – OPC UA for Geometric Measurement Systems
  5.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-40210 – OPC UA for Geometric Measurement Systems
  13.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