Table 116 defines the corresponding Conformance Units for the OPC UA Information Model for Devices.

Table 116 – Conformance Units for Devices

Category

Title

Description

Server

DI Information Model

Supports Objects that conform to the Device model of this document.

This includes in particular Objects of (subtypes of) ComponentType and FunctionalGroups.

Server

DI DeviceType

Supports Objects of DeviceType or a subtype.

Server

DI DeviceSet

Supports the DeviceSet object to aggregate Device instances.

Server

DI Nameplate

Supports Properties of the VendorNameplate Interface defined in 4.5.2.

Server

DI TagNameplate

Supports the TagNameplate Interface defined in 4.5.3.

Server

DI Software Component

Supports Objects of SoftwareType or a subtype.

Server

DI DeviceHealth

Supports the DeviceHealth Interface defined in 4.5.4.

Server

DI DeviceHealthProperty

Supports the DeviceHealth Property defined in 4.5.4.

Server

DI HealthDiagnosticsAlarm

Supports DeviceHealth Alarms defined in 4.12.

Server

DI OperationCounter Interface

Supports the OperationCounter Interface defined in 4.5.5.

Server

DI DeviceSupportInfo

Server provides additional data for its Devices as defined in 4.5.6.

Server

DI Documents as Files

Server provides documents as FileType instances.

Server

DI Identification

Supports the Identification FunctionalGroup for Devices.

Server

DI Protocol

Supports the ProtocolType and instances of it to identify the used communication profiles for specific instances.

Server

DI Blocks

Supports the BlockType (or subtypes respectively) and the Blocks Object in some of the instantiated Devices.

Server

DI Locking

Supports the LockingService for certain TopologyElements.

Server

DI BreakLocking

Supports the BreakLock Method to break the lock held by another Client.

Server

DI Network

Supports the NetworkType to instantiate Network instances.

Server

DI ConnectionPoint

Supports subtypes of the ConnectionPointType.

Server

DI NetworkSet

Supports the NetworkSet Object to aggregate all Network instances.

Server

DI ConnectsTo

Supports the ConnectsTo Reference to associate Devices with a Network.

Server

DI DeviceTopology

Supports the DeviceTopology Object as starting Node for the communication topology of the Devices to integrate.

Server

DI Offline

Supports offline and online representations of Devices including the Methods to transfer data from or to the Device.

Server

DI SU Software Update

The Address Space contains at least one instance of the SoftwareUpdateType as AddIn and provides the required Parameters of IVendorNamePlateType as defined in 8.4.1.

Server

DI SU DirectLoading

At least one instance of the SoftwareUpdateType supports the DirectLoadingType as Loading Object.

Server

DI SU CachedLoading

At least one instance of the SoftwareUpdateType supports the CachedLoadingType as Loading Object.

Server

DI SU FileSystem Loading

At least one instance of the SoftwareUpdateType supports the FileSystemLoadingType as Loading Object.

Server

DI SU PrepareForUpdate

At least one instance of the SoftwareUpdateType supports the PrepareForUpdate Object.

Server

DI SU Manual Power Cycle

At least one instance of the SoftwareUpdateType supports the PowerCycle Object.

Server

DI SU Update Parameter Backup

At least one instance of the SoftwareUpdateType supports the Parameters Object.

Server

DI SU UpdateStatus

At least one instance of the SoftwareUpdateType supports the UpdateStatus Variable.

Server

DI SU VendorErrorCode

At least one instance of the SoftwareUpdateType supports the VendorErrorCode Variable.

Server

DI SU Installation for Cached Loading

At least one instance of the SoftwareUpdateType supports the Installation Object.

The Method InstallSoftwarePackage is mandatory.

The Method InstallFiles shall not be available.

Server

DI SU Installation for File System

At least one instance of the SoftwareUpdateType supports the Installation Object of SoftwareUpdateType.

The Method InstallFiles is mandatory.

The Method InstallSoftwarePackage shall not be available.

Server

DI SU InstallationDelay

At least one instance of the InstallationStateMachineType supports the InstallationDelay Variable.

Server

DI SU Update Confirmation

At least one instance of the SoftwareUpdateType supports the Confirmation Object.

Server

DI SU FallbackVersion

At least one instance of the CachedLoadingType supports the FallbackVersion Object.

Server

DI SU UpdateKey

At least one instance of the SoftwareLoadingType supports the UpdateKey Variable.

Server

DI SU Installation PercentComplete

At least one instance of the InstallationStateMachineType supports the PercentComplete Variable.

Server

DI SU Resume Update

At least one instance of the PrepareForUpdateStateMachineType supports the Resume Method.

Server

DI SU Prepare for Update PercentComplete

At least one instance of the PrepareForUpdateStateMachineType supports the PercentComplete Variable.

Server

DI SU Update WriteBlockSize

At least one instance of a subtype of the PackageLoadingType supports the WriteBlockSize Variable.

Server

DI SU Update WriteTimeout

At least one instance of DirectLoadingType supports the WriteTimeout Variable.

Server

DI SU PatchIdentifiers

At least one instance of the SoftwareVersionType support the PatchIdentifiers Property. If implemented on a SoftwareUpdate Object, all supported versions (CurrentVersion, PendingVersion and FallbackVersion) shall support the Property.

Server

DI SU Update ReleaseDate

At least one instance of SoftwareVersionType of a SoftwareUpdate Object supports the ReleaseDate Property.

Server

DI SU ChangeLogReference

At least one instance of SoftwareVersionType of a SoftwareUpdate Object supports the ChangeLogReference Property.

Server

DI SU Update Hash

At least one instance of SoftwareVersionType of a SoftwareUpdate Object supports the Hash Property.

Server

DI SU ValidateFiles

At least one instance of the FileSystemLoadingType supports the ValidateFiles Method.

Server

DI LT Lifetime Base

The Server supports the Lifetime model and exposes at least one instance of the LifetimeVariableType.

Server

DI LT Time Indication

The Server supports lifetime for the time the entity has been in use or can still be used.

Server

DI LT Nb Of Parts Indication

The Server supports lifetime for the total number of parts that have been produced or can still be produced.

Server

DI LT Nb Of Usages Indication

The Server supports lifetime by counting the process steps the entity has been used or can still be used for.

Server

DI LT Length Indication

The Server supports lifetime for the abraded length.

Server

DI LT Diameter Indication

The Server supports lifetime for the abraded diameter.

Server

DI LT Substance Volume Indication

The Server supports lifetime for the volume of a substance.

Client

DI Client Information Model

Consumes Objects that conform to the Device model in this document.

This includes in particular Objects of (subtypes of) ComponentType and FunctionalGroups.

Client

DI Client DeviceSet

Uses the DeviceSet Object to detect available Devices.

Client

DI Client Nameplate

Consumes Properties of the VendorNameplate Interface defined in 4.5.2.

Client

DI Client TagNameplate

Consumes the VendorNameplate Interface defined in 4.5.3.

Client

DI Client Software Component

Consumes Objects of SoftwareType or a subtype.

Client

DI Client DeviceHealth

Uses the DeviceHealth Interface defined in 4.5.4.

Client

DI Client DeviceHealthProperty

Uses the DeviceHealth Property defined in 4.5.4.

Client

DI Client HealthDiagnosticsAlarm

Uses DeviceHealth Alarms defined in 4.12.

Client

DI Client DeviceSupportInfo

Uses available additional data for Devices as defined in 4.5.6.

Client

DI Client Identification

Consumes the Identification FunctionalGroup for Devices including the (optional) reference to supported protocol(s).

Client

DI Client Blocks

Understands and uses BlockDevices and their Blocks including FunctionalGroups on both Device and Block level.

Client

DI Client Locking

Uses the LockingService where available.

Client

DI Client BreakLocking

Support use of the BreakLock Method to break the lock held by another Client.

Client

DI Client Network

Uses the NetworkType to instantiate Network instances.

Client

DI Client ConnectionPoint

Uses subtypes of the ConnectionPointType.

Client

DI Client NetworkSet

Uses the NetworkSet Object to store or find Network instances.

Client

DI Client ConnectsTo

Uses the ConnectsTo Reference to associate Devices with a Network.

Client

DI Client DeviceTopology

Uses the DeviceTopology Object as starting Node for the communication topology of the Devices to integrate.

Client

DI Client Offline

Uses offline and online representations of Devices including the Methods to transfer data from or to the Device.

Client

DI SU Client SoftwareUpdate

Uses the IVendorNameplate and the SoftwareUpdate AddIn to perform a software update.

Client

DI SU Client DirectLoading

Can use the DirectLoadingType to update the software using Direct-Loading if supported by the server.

Client

DI SU Client CachedLoading

Uses the CachedLoadingType and InstallationStateMachineType to update the software using Cached-Loading if supported by the server.

Client

DI SU Client FileSystem Loading

Uses the FileSystemLoadingType and InstallationStateMachineType to update the software using FileSystem based Loading if supported by the server.

Client

DI SU Client PrepareForUpdate

Uses the PrepareForUpdate Object of SoftwareUpdateType if supported by the server.

Client

DI SU Client Manual Power Cycle

Uses the PowerCycle Object of SoftwareUpdateType if supported by the server.

Client

DI SU Client Update Parameter Backup

Uses the Parameters Object of SoftwareUpdateType if supported by the server.

Client

DI SU Client Update Confirmation

Can use the Confirmation Object of SoftwareUpdateType if supported by the server.

Client

DI SU Client FallbackVersion

Supports the installation of the Fallback Version if supported by the server.

Client

DI SU Client UpdateKey

Supports update of devices that need an UpdateKey if supported by the server.

Client

DI SU Client Resume Update

Can use the Resume Method on the PrepareForUpdate Object of SoftwareUpdateType if supported by the server.

Client

DI SU Client WriteBlockSize

Respects the WriteBlockSize of PackageLoadingType if supported by the server.

Client

DI SU Client Update Hash

Can provide the Hash value to the Install Method for verification.

Client

DI SU Client ValidateFiles

Uses the ValidateFiles Method of the InstallationStateMachineType if supported by the server.

Client

DI LT Client Lifetime

Uses the Lifetime model and any of the life time indications.

Profiles are named groupings of ConformanceUnits as defined in OPC 10000-7. The term Facet in the title of a Profile indicates that this Profile is expected to be part of another larger Profile or concerns a specific aspect of OPC UA. Profiles with the term Facet in their title are expected to be combined with other Profiles to define the complete functionality of an OPC UA Server or Client.

This specification defines Facets for Servers or Clients when they plan to support OPC UA for Devices. They are described in 11.2.3 and 11.2.4.

Table 117 lists all Profiles defined in this document and defines their URIs.

Table 117 – Profile URIs for Devices

Profile

URI

DI BaseDevice Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/BaseDevice

DI DeviceIdentification Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/DeviceIdentification

DI BlockDevice Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/BlockDevice

DI Locking Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/Locking

DI DeviceCommunication Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/DeviceCommunication

DI DeviceIntegrationHost Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/DeviceIntegrationHost

DI SU Software Update Base Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/SoftwareUpdateBase

DI SU Direct Loading Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/DirectLoading

DI SU Cached Loading Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/CachedLoading

DI SU FileSystem Loading Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/FileSystemLoading

DI Lifetime Server Facet

http://opcfoundation.org/UA-Profile/DI/Server/Lifetime

DI BaseDevice Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/BaseDevice

DI DeviceIdentification Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/DeviceIdentification

DI BlockDevice Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/BlockDevice

DI Locking Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/Locking

DI DeviceCommunication Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/DeviceCommunication

DI DeviceIntegrationHost Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/DeviceIntegrationHost

DI SU Software Update Base Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/SoftwareUpdateBase

DI SU Direct Loading Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/DirectLoading

DI SU Cached Loading Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/CachedLoading

DI SU FileSystem Loading Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/FileSystemLoading

DI Lifetime Client Facet

http://opcfoundation.org/UA-Profile/DI/Client/Lifetime

The following tables specify the Facets available for Servers that implement the Devices information model. Table 118 describes Conformance Units included in the minimum needed Facet. It includes the organisation of instantiated Devices in the Server AddressSpace.

Table 118 – DI BaseDevice Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Information Model

M

DI

DI DeviceSet

M

DI

DI DeviceType

O

DI

DI Nameplate

O

DI

DI TagNameplate

O

DI

DI OperationCounter Interface

O

DI

DI Software Component

O

DI

DI DeviceHealth

O

DI

DI DeviceHealthProperty

O

DI

DI HealthDiagnosticsAlarm

O

DI

DI DeviceSupportInfo

O

DI

DI Documents as Files

O

Table 119 defines a Facet for the identification FunctionalGroup of Devices. This includes the option of identifying the Protocol(s).

Table 119 – DI DeviceIdentification Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Identification

M

DI

DI Protocol

O

Table 120 defines extensions specifically needed for BlockDevices.

Table 120 – DI BlockDevice Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Blocks

M

Table 121 defines a Facet for the Locking AddIn Capability. This includes the option of breaking a lock.

Table 121 – DI Locking Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Locking

M

DI

DI BreakLocking

O

Table 122 defines a Facet for the support of the Device Communication model.

Table 122 – DI DeviceCommunication Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Network

M

DI

DI ConnectionPoint

M

DI

DI NetworkSet

M

DI

DI ConnectsTo

M

Table 123 defines a Facet for the support of the Device Integration Host model.

Table 123 – DI DeviceIntegrationHost Server Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI DeviceTopology

M

DI

DI Offline

M

Table 124 defines a Facet that describes the basic infrastructure for software update. It contains the common part of the Direct Loading, Cached Loading and FileSystem Loading Server Profiles.

Table 124 – DI SU Software Update Base Server Facet

Group

Conformance Unit / Profile Title

M / O

DI

DI SU Software Update

M

DI

DI SU PrepareForUpdate

O

DI

DI SU Resume Update

O

DI

DI SU Prepare for Update PercentComplete

O

DI

DI SU Manual Power Cycle

O

DI

DI SU Update Parameter Backup

O

DI

DI SU UpdateKey

O

Table 125 defines a Facet with additional Conformance Units for a Server that implements Direct-Loading.

Table 125 – DI SU Direct Loading Server Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Software Update Base Server Facet

M

DI

DI SU DirectLoading

M

DI

DI SU UpdateStatus

M

DI

DI SU Update WriteBlockSize

O

DI

DI SU Update WriteTimeout

O

DI

DI SU PatchIdentifiers

O

DI

DI SU Update ReleaseDate

O

DI

DI SU ChangeLogReference

O

DI

DI SU Update Hash

O

Table 126 defines a Facet with additional Conformance Units for a Server that implements Cached-Loading.

Table 126 – DI SU Cached Loading Server Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Software Update Base Server Facet

M

DI

DI SU CachedLoading

M

DI

DI SU Installation for Cached Loading

M

DI

DI SU UpdateStatus

M

DI

DI SU Installation PercentComplete

O

DI

DI SU InstallationDelay

O

DI

DI SU Update Confirmation

O

DI

DI SU FallbackVersion

O

DI

DI SU Update WriteBlockSize

O

DI

DI SU PatchIdentifiers

O

DI

DI SU Update ReleaseDate

O

DI

DI SU ChangeLogReference

O

DI

DI SU Update Hash

O

Table 127 defines a Facet with additional Conformance Units for a Server that implements File System based Loading.

Table 127 – DI SU FileSystem Loading Server Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Software Update Base Server Facet

M

DI

DI SU FileSystem Loading

M

DI

DI SU Installation for File System

M

DI

DI SU UpdateStatus

O

DI

DI SU Installation PercentComplete

O

DI

DI SU InstallationDelay

O

DI

DI SU Update Confirmation

O

DI

DI SU Validate Files

O

Table 128 defines a Facet for support of the Lifetime model.

Table 128 – DI Lifetime Server Facet

Group

Conformance Unit / Profile Title

M / O

DI

DI LT Lifetime Base

M

DI

DI LT Time Indication

O

DI

DI LT Nb Of Parts Indication

O

DI

DI LT Nb Of Usages Indication

O

DI

DI LT Length Indication

O

DI

DI LT Diameter Indication

O

DI

DI LT Substance Volume Indication

O

The following tables specify the Facets available for Clients that implement the Devices information model. Table 129 describes Conformance Units included in the minimum needed Facet.

Table 129 – DI BaseDevice Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client Information Model

M

DI

DI Client DeviceSet

M

DI

DI Client Nameplate

O

DI

DI Client Software Component

O

DI

DI Client DeviceHealth

O

DI

DI DeviceHealthProperty

O

DI

DI HealthDiagnosticsAlarm

O

DI

DI Client DeviceSupportInfo

O

Table 130 defines a Facet for the identification FunctionalGroup of Devices. This includes the option of identifying the Protocol(s).

Table 130 – DI DeviceIdentification Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client Identification

M

Table 131 defines extensions specifically needed for BlockDevices.

Table 131 – DI BlockDevice Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client Blocks

M

Table 132 defines a Facet for the Locking AddIn Capability. This includes the option of breaking a lock.

Table 132 – DI Locking Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client Locking

M

DI

DI Client BreakLocking

O

Table 133 defines a Facet for the use of the Device Communication model.

Table 133 – DI DeviceCommunication Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client Network

M

DI

DI Client ConnectionPoint

M

DI

DI Client NetworkSet

M

DI

DI Client ConnectsTo

M

Table 134 defines a Facet for the use of the Device Integration Host model.

Table 134 – DI DeviceIntegrationHost Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI Client DeviceTopology

M

DI

DI Client Offline

M

Table 124 defines a Facet that describes the basic features of a software update client. It contains the common part of the Direct Loading, Cached Loading and FileSystem Loading Client Profiles.

Table 135 – DI SU Software Update Base Client Facet

Group

Conformance Unit / Profile Title

M / O

DI

DI SU Client SoftwareUpdate

M

DI

DI SU Client PrepareForUpdate

O

DI

DI SU Client Resume Update

O

DI

DI SU Client Manual Power Cycle

O

DI

DI SU Client Update Parameter Backup

O

DI

DI SU Client UpdateKey

O

Table 125 defines a Facet with additional Conformance Units for a Client that supports Direct-Loading.

Table 136 – DI SU Direct Loading Client Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Software Update Base Client Facet

M

DI

DI SU Client DirectLoading

M

DI

DI SU Client WriteBlockSize

O

DI

DI SU Client Update Hash

O

Table 126 defines a Facet with additional Conformance Units for a Client that supports Cached-Loading.

Table 137 – DI SU Cached Loading Client Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Client SoftwareUpdate

M

DI

DI SU Client CachedLoading

M

DI

DI SU Client Update Confirmation

O

DI

DI SU Client FallbackVersion

O

DI

DI SU Client WriteBlockSize

O

DI

DI SU Client Update Hash

O

Table 127 defines a Facet with additional Conformance Units for a Client that supports File System based Loading.

Table 138 – DI SU FileSystem Loading Client Facet

Group

Conformance Unit / Profile Title

M / O

Profile

DI SU Client SoftwareUpdate

M

DI

DI SU Client FileSystem Loading

M

DI

DI SU Client Update Confirmation

O

DI

DI SU Client ValidateFiles

O

Table 139 defines a Facet for the use of the Lifetime model.

Table 139 – DI Lifetime Client Facet definition

Group

Conformance Unit / Profile Title

M / O

DI

DI LT Client Lifetime

M