Search

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

58 result(s) for Model

OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.2 UANodeSet

UANodeSet along with any dependencies these models have. ModelUri String The URI for the model. This URI shall be one of the entries in the NamespaceUris table. XmlSchemaUri String ... schema namespace used to serialize values of the DataTypes defined by the Model. The field is required if DataTypes are defined in the UANodeSet . The UA XML Encoding ( 5.3 ) rules
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.3 UANode

Node . This attribute is optional. If not specified the AccessRestrictions for the Model are applied. DisplayName LocalizedText [] A list of DisplayNames for the Node in different locales. There shall ... list is not specified or has zero length the default RolePermissions from the Model are used unless HasNoPermissions is TRUE. HasNoPermissions Boolean If TRUE, the UANode has no RolePermissions
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.16 UANodeSetChanges

existing Address Space. The UANodeSetChanges cannot be applied if the current version of the Model in the Address Space is higher. The RequiredModels sub-element (see Table F.1 ) specifies ... before the UANodeSetChanges file can be applied. When checking dependencies, the version of the Model in the existing Address Space must exactly match the required version. If a UANodeSetChanges file
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.14.1 General

expected from an OPC UA Server that is implementing the A & C Information Model . In particular this section describes specific behaviours that apply to various aspect ... Information Model
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

1 Scope

document is part of the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClass ... Historical Access, additional standard Properties , and other information and behaviour. The complete AddressSpace Model including all NodeClass es and Attributes is specified in OPC 10000-3 . The predefined Information Model
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.4 SerializationScope and SerializationEntity

SerializationScope and SerializationEntity A SerializationScope is a subset of Nodes in the Information Model which are mapped into the SerializationValue, and which shall take part in a SerializationProcess . A SerializationScope
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

FxAssetType is considered an Asset . Additional References are defined as part of the model to show relationships between Assets , within Assets , and between Assets and FunctionalEntities and the overall AutomationComponent ... model (see 11.1 ). The FxAssetType is formally defined in Table 29 . Table 29 - FxAssetType definition Attribute Value BrowseName 3:FxAssetType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.6 ConnectionManagerCapabilitiesType

ConnectionManager can support . MonitorsLocalConnectionEndpoints, when true, describes the capability of the ConnectionManager Information Model to report the status of all the Connections created by this ConnectionManager that have a ConnectionEndpoint ... this Server. If this capability is not provided, or false, the ConnectionManager Information Model does not report the current status of Connections. NOTE In some cases, this status might include
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.4 System integration

VLAN interfaces can be created if necessary. a As no OPC UA Information Model mechanism today allows the assignment of priority information for UA Client Server messages ... configured, the System Commissioner may update the PubSubCommunicationFlowConfiguration Variable in the ConnectionManager's Information Model to adapt the Connection configurations for QoS settings and network settings such as setting destination
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

5.2 Descriptor organization

kinds of files (see Figure 6 ). It contains a Descriptor manifest file and Information Model file(s) and can contain attachment files, embedded Descriptors, or Common Services . Figure 6 - Organization ... version number for the content and a version number for the format. The Information Model files contain AML representations of UAFX Information Models . A worked-out example of the configuration
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

7.5.2 Open Packaging Conventions Relationships

identifier of type xs:ID (see ISO/IEC 29500-2:2021 clause 6.5.3.4). All Information Model attachments and embedded Descriptors in a Descriptor shall be the target of a relationship reference ... Graph with the Root AML files as the starting points and with all Information Model , attachments, and embedded Descriptors in a Descriptor referenced from the Root AML files either directly
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.1 AutomationComponent modelling example

example This annex provides a worked-out example of the configuration of the Information Model of an AutomationComponent using the UAFX Information Model . This modelling process is described ... abstract way, without referencing tools or roles for the creation or editing of the model. In a concrete example, suitable or adapted engineering tools are expected to support the modelling
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.3.7 UAFX Station 2024 Facet

UAFX component implementation, including an IA-station and network interface representation in the Information Model and its default configuration. Table 40 - UAFX Station 2024 Facet Group Conformance Unit / Profile Title ... Optional IA-station Facet LLDP Information Facet Base Network Model BNM Ethernet Base Info False Base Network Model BNM IETF Interface Base Info False Base Network Model BNM Entry Points
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.4 UAFX SubscriberConfiguration Facet

information required for configuring the Subscriber of an information flow in the ConnectionManager Information Model . Table 43 - UAFX SubscriberConfiguration Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager UAFX ConnectionManager
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

HasProperty Variable 1:ManufacturerUri 0:String 0:PropertyType O 0:HasProperty Variable 1:Model 0:LocalizedText 0:PropertyType O 0:HasProperty Variable 1:ProductCode 0:String 0:PropertyType ... name; however, it can be a GUID or similar construct that ensures global uniqueness. Model provides the name of the product. ProductCode provides a unique combination of numbers and letters
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.8 SoftwareType

HasProperty Variable 1:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 1:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 1:SoftwareRevision 0:String 0:PropertyType M Conformance ... subtype of ComponentType which means it inherits all InstanceDeclarations . The Properties Manufacturer , Model , and SoftwareRevision inherited from ComponentType are declared mandatory for SoftwareType instances
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.11 AddIn model

AddIn model To support an individual software update for the devices of a Server AddressSpace the software update model is defined using the AddIn model as it is described ... AddIn instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware- or software-component the opportunity to support SoftwareUpdate . With this mechanism
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

Structure ProductCode 0:String ProductCode of the target Node on the device. False Model 0:String Model of the target Node on the device. False Table 123 - UpdateTarget definition Attribute
OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control

2 Normative References

Concepts http://www.opcfoundation.org/documents/10000-1/ OPC 10000-3, OPC Unified Architecture - Part 3: Address Space Model http://www.opcfoundation.org/documents/10000-3/ OPC 10000-4, OPC Unified Architecture - Part 4: Services http://www.opcfoundation.org/documents/10000-4/ ... Unified Architecture - Part 5: Information Model http://www.opcfoundation.org/documents/10000-5/ OPC 10000-6, OPC Unified Architecture - Part 6: Mappings http://www.opcfoundation.org/documents/10000-6/ OPC 10000-7, OPC Unified Architecture - Part 7: Profiles
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-30100 – OPC UA for SERCOS Devices

4.2 OPC UA

clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms ... Clients is referred to as its AddressSpace . The elements of the OPC UA Object Model are represented in the AddressSpace as a set of Nodes described by Attributes and interconnected
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

7.1.2 Overview

SerialNumber String PropertyType Optional HasProperty Variable 2:Manufacturer LocalizedText PropertyType Mandatory HasProperty Variable 2:Model LocalizedText PropertyType Mandatory HasProperty Variable 2:HardwareRevision String PropertyType Optional HasProperty Variable 2:SoftwareRevision String ... internally to the Vendor Name managed by the IO-Link Community. The Variable Model of DataType LocalizedText shall be mapped to ISDU Index 0x0012 (Product Name). As the name
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-30142 – OPC UA for PROFINET Remote IO

6.2 OPC UA for RIO Channel Model

Channel Model The "RIOChannel" Object in the functional aspect aggregates Process Value Objects optionally offering additional information like Process Value qualifiers associated with the IO data. Figure ... shows the basic channel model for an analog RIO Input Channel according to RIOforPA. Figure 8 - Analog Input Channel Model in Functional Aspect with RIOforPA The functional aspect with
OPC-30142 – OPC UA for PROFINET Remote IO

6.3 PROFINET Cyclic IO Telegram Model

PROFINET Cyclic IO Telegram Model Figure 10 shows the Cyclic IO Telegram model accessible from the PN Submodule in the PROFINET aspect of the Information Model . If provided ... provide additional information like provider status and consumer status. Figure 10 - PROFINET Telegram Model The Offset Property of the PnIoSignalType Object contains the position as byte offset of the signal
OPC-30142 – OPC UA for PROFINET Remote IO

6.4 Connection of PROFINET Aspect and Functional Aspect

Functional Aspect Figure 11 - 2 analog RIOforPA channels Figure 11 shows the Channel model for analog Input according to RIOforPA to illustrate the relationship between the different aspects. The Process ... functional aspect with two analog RIO Input Channels according to RIOforPA in the Information Model is shown in Figure 12 . Figure 12 - 2 analog RIOforPA Channels connected with Cyclic
OPC-30142 – OPC UA for PROFINET Remote IO

6.5 OPC UA for RIO Channel Groups

continuous bytes. Figure 15 - FA Channel Group Figure 15 shows the analog Output Channel model and a Channel Group according to RIOforFA. The qualifiers of the Output Process Values ... relates to the "OutputImageQualifiers" Variable in the functional aspect of the Information Model using a 0:RepresentsSameEntityAs Reference . The "SM1" PROFINET submodule Object connects
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

4.1 Introduction to PROFINET GSD Generic Model

Introduction to PROFINET GSD Generic Model The primary aim of PROFINET GSD Generic Model is to define a specification how Servers can create an Information Model for Devices which have ... profile (API=0) and therefore also no OPC UA companion specification defining an Information Model . It can be used also to extend the Information Model of a profile Device
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

5 Use cases

cases A proxy Server with access to the related PROFINET domain provides the Information Model of PROFINET Devices . These Devices are typically profile-less but may also support an application ... live" data in an Industrial Internet of Things ecosystem. Support standardized information model and data for digital twin Companies offering automation solutions in special domains want to offer their
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.1 Information Model Creation

Information Model Creation The following sequence of steps lays out a general procedure for the creation of a 'generic' Information Model for Devices the Server has access to by PROFINET ... ExpectedIdentificationData" records, the Server creates GsdGenSubmoduleApplicationType Objects in the Information Model accordingly (see 6.3 ). Missing Submodules (SubmoduleState.IdentInfo block contains "NoSubmodule") shall not be represented in the Information
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.2 Application Object

Application Object The GsdGenSubmoduleApplicationType is the root container for modelling of the Information Model belonging to one PN Submodule and relates to the PN Submodule Object with a 0:RepresentsSameFunctionalityAs ... elements found in the GSDML file. As specified in [ OPC RIO ], the Information Model is divided into a PROFINET aspect and a functional aspect. The PROFINET aspect offers detailed Telegram
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.3 IO Data

Data Figure 7 shows an IO Data model to demonstrate the basic principle of the relationships of the Objects in the PROFINET Aspect with the Objects and Variables representing ... Data in the Functional Aspect of the Information Model . Figure 7 - IO Data Organization The "Submodule 1" Object in the PROFINET Aspect relates to the GsdGenSubmoduleApplicationType Object using
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.4 IO Channel

Data" Sub-Aspect in the Functional Aspect of the Information Model. Figure 11 - IO Channel Organization The GsdGenIoDataType Objects relate to the associated GsdGenIoChannelType Objects using the 0:HasComponent ... Channel" elements and its child elements to Objects in the Information Model . Figure 13 - Mapping of XML elements describing Channel Data The BitOffset Property of the optional "Quality
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.5 IO Data Qualifier and StatusCode Relationship

StatusCode according to Table 17 . The Value of the representing Variable in the Information Model shall not contain the status bits. Table 17 - StatusCodes for embedded status bits Status Bits
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.6 Parameters

shows the "Parameters" sub-aspect in the Functional Aspect of the Information Model. Figure 14 - Parameters Organization The GsdGenParameterVariableType Variable represents one Parameter as part of a parameter ... elements contained in the "ApplicationProcess/RecordDataList" shall be represented in the Information Model . These "ParameterRecordDataItem" elements are referenced by "(Virtual)SubmoduleItem /RecordDataList/ParameterRecordDataRef" elements (see Figure
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.7 Data Objects

Data Objects" sub-aspect in the Functional Aspect of the Information Model. Figure 18 - Data Objects Organization This aspect contains additional data values modelled as Variables or Properties ... Object representing the Submodule offering Data Objects in the PROFINET aspect of the Information Model relates to the GsdGenSubmoduleApplicationType Object providing the Variables and Properties for these Data Objects using
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

11.1 Conformance Units

Conformance Units Table 50 defines the corresponding ConformanceUnits for the OPC UA Information Model for PROFINET GSD Generic Model. Table 50 - Conformance Units for PROFINET GSD Generic Model Category Title ... Server PNGSDGM Parameter Server provides the Parameter data of the Devices in the Information Model . Server PNGSDGM IO Data Server provides the IO Data of the Devices in the Information
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

C.1 RefMeta child elements

Server to obtain the actual display value in the Information Model . To be used in conjunction with the "opc:Gradient" Meta element, see below. O <Meta ... Server to obtain the actual display value in the Information Model . To be used in conjunction with the "opc:Offset" Meta element, see above. Regardless of the referenced
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

C.2 RecordMeta child elements

specify BMPs. The vendor specific options for the representation of BMPs in the Information Model are specified using a sequence of "RefMeta" elements (see Table 63 ), as shown ... Base Mode Parameter Access") identifying the parameter to be represented in the Information Model . M <Meta> opc:FunctionGroupName Path name for the OPC UA 2:FunctionalGroupType container
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.1.5 Drive Communication Model

Drive Communication Model Most PROFINET Drives still support the PROFIdrive profile. PROFIdrive offers an interoperable interface for the access to standard parameters and vendor specific parameters. This offers the possibility ... access to drive data via PROFINET and PROFIBUS. Nevertheless, the OPC UA information model of this specification is not limited to PROFIdrive devices, because the mandatory parts of the information
OPC-30200 – OPC UA for Commercial Kitchen Equipment

5.1.4 Model property

Model property The device designation is provided as freely definable text in the Model property
OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS

2 Normative References

Overview and Concepts OPC 10000-3, OPC Unified Architecture - Part 3: Address Space Model http://www.opcfoundation.org/UA/Part3/ OPC 10000-4, OPC Unified Architecture - Part 4: Services http://www.opcfoundation.org/UA/Part4/ ... Unified Architecture - Part 5: Information Model http://www.opcfoundation.org/UA/Part5/ OPC 10000-6, OPC Unified Architecture - Part 6: Mappings http://www.opcfoundation.org/UA/Part6/ OPC 10000-7, OPC Unified Architecture - Part 7: Profiles
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

3.4.1.1 Node Definitions

list of supported ConformanceUnits to select a subset of the Nodes in an Information Model . When a Node is selected in this way, all dependencies implied by the References
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

8.2 IMachineryItemVendorNameplateType

serial number is only given in the context of the manufacturer, and potentially the model. The value of this Property shall not change during the life-cycle of the MachineryItem ... serial number is unique within the manufacturer's scope, or a combination of model and serial number, if the serial number is only unique within a model. Examples
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

7.2.2 MotionDeviceType definition

HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:ProductCode 0:String 0:PropertyType ... device. This property is derived from ComponentType defined in OPC 10000-100. The Model property provides the name of the product. This property is derived from ComponentType defined
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

7.5.2 MotorType definition

HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:ProductCode 0:String 0:PropertyType ... device. This property is derived from ComponentType defined in OPC 10000-100. The Model property provides the name of the product. This property is derived from ComponentType defined
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

7.6.2 GearType definition

HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:ProductCode 0:String 0:PropertyType ... device. This property is derived from ComponentType defined in OPC 10000-100. The Model property provides the name of the product. This property is derived from ComponentType defined
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

7.18.2 ControllerType definition

HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M 0:HasProperty Variable 2:ProductCode 0:String 0:PropertyType ... device. This property is derived from ComponentType defined in OPC 10000-100. The Model property provides the name of the product. This property is derived from ComponentType defined
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

C.2 Identification and Finding Machines

Incorporation of Partly Completed Machinery according Machinery Directive 2006/42/EU for robots provides the Model and the SerialNumber for the robot and for the controller. Figure C. 21 - Example Finding
OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems

7.2 Identification and MachineryBuildingBlocks

provides basic information on a machine/device. For the InstanceDeclaration the ModellingRules of the Properties Model and DeviceClass are overridden to mandatory. The Object MachineryBuildingBlocks contains building blocks from ... Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Other 2:Identification 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M, RO 2:Identification 0:HasProperty Variable 2:DeviceClass 0:String
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

21.1.3 Model

Model The Model Property represents the name of the machine type (e.g. "KM 1000-2500", "Allrounder"). The Property is optional in OPC UA DI. Here
OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitions

6.3 Identification and MachineryBuildingBlocks

provides basic information on a machine/device. For the InstanceDeclaration the ModellingRules of the Properties Model and DeviceClass are overridden to mandatory and the Property ControllerName is added. The Object MachineryBuildingBlocks ... Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Other 2:Identification 0:HasProperty Variable 2:Model 0:LocalizedText 0:PropertyType M, RO 2:Identification 0:HasProperty Variable 2:DeviceClass 0:String
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

7.1 Localization

text part of a value of DataType LocalizedText , like the Manufacturer or the Model of a machine tool, is language neutral, i.e., it is the same in all languages
OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model

4.2.1 General

well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols ... clients can be directly integrated into devices and controllers. The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients . Objects in OPC UA terms
OPC-40560 – OPC UA for Mining - General

7.1.3 ObjectType Description

indicates the BrowseName of any instance of this ObjectType, if referenced using the AddIn-Model described in OPC 10000-5. The DeviceClass Variable indicates in which domain or for what ... however, it may be a GUID or similar construct that ensures global uniqueness. The Model variable provides the name of the product. The ProtocolSupport Object exposes protocol support files. They