Devices - 10 Profiles

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 10.2 and 10.3.

10.2 Device Server Facets

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

Table 66 – BaseDevice_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Information Model	Supports Objects that conform to the types specified in the chapter Device model of this companion standard. This includes in particular Objects of (subtypes of) ComponentType and FunctionalGroups.	M
DI DeviceSet	Supports the DeviceSet object to aggregate Device instances.	M
DI Nameplate	Supports Properties of the VendorNameplate Interface defined in 5.5.2.	O
DI Software Component	Supports Objects of SoftwareType or a subtype.	O
DI DeviceHealth	Supports the DeviceHealth Property defined in 5.5.3.	O
DI DeviceSupportInfo	Server provides additional data for its Devices as defined in 5.5.5.	O

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

Table 67 – DeviceIdentification_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Identification	Supports the Identification FunctionalGroup for Devices.	M
DI Protocol	Supports the ProtocolType and instances of it to identify the used communication profiles for specific instances.	O

Table 68 defines extensions specifically needed for BlockDevices.

Table 68 – BlockDevice_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Blocks	Supports the BlockType (or subtypes respectively) and the Blocks Object in some of the instantiated Devices.	M

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

Table 69 – Locking_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Locking	Supports the LockingService for certain TopologyElements.	M
DI BreakLocking	Supports the BreakLock Method to break the lock held by another Client.	O

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

Table 70 – DeviceCommunication_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Network	Supports the NetworkType to instantiate Network instances.	M
DI ConnectionPoint	Supports subtypes of the ConnectionPointType.	M
DI NetworkSet	Supports the NetworkSet Object to aggregate all Network instances.	M
DI ConnectsTo	Supports the ConnectsTo Reference to associate Devices with a Network.	M

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

Table 71 – DeviceIntegrationHost_Server_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI DeviceTopology	Supports the DeviceTopology Object as starting Node for the communication topology of the Devices to integrate.	M
DI Offline	Supports offline and online representations of Devices including the Methods to transfer data from or to the Device.	M

10.3 Device Client Facets

The following tables specify the Facets available for Clients that implement the Devices companion standard. Table 72 describes Conformance Units included in the minimum needed Facet.

Table 72 – BaseDevice_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Client Information Model	Consumes Objects that conform to the types specified in the chapter Device model of this companion standard. This includes in particular Objects of (subtypes of) ComponentType and FunctionalGroups.	M
DI Client DeviceSet	Uses the DeviceSet Object to detect available Devices.	M
DI Client Nameplate	Consumes Properties of the VendorNameplate Interface defined in 5.5.2.	O
DI Client Software Component	Consumes Objects of SoftwareType or a subtype.	O
DI Client DeviceHealth	Uses the DeviceHealth Property defined in 5.5.3.	O
DI Client DeviceSupportInfo	Uses available additional data for Devices as defined in 5.5.5.	O

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

Table 73 – DeviceIdentification_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Client Identification	Consumes the Identification FunctionalGroup for Devices including the (optional) reference to supported protocol(s).	M

Table 74 defines extensions specifically needed for BlockDevices.

Table 74 – BlockDevice_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Client Blocks	Understands and uses BlockDevices and their Blocks including FunctionalGroups on both Device and Block level.	M

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

Table 75 – Locking_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Locking	Uses the LockingService where available.	M
DI BreakLocking	Support use of the BreakLock Method to break the lock held by another Client.	O

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

Table 76 – DeviceCommunication_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI Network	Uses the NetworkType to instantiate Network instances.	M
DI ConnectionPoint	Uses subtypes of the ConnectionPointType.	M
DI NetworkSet	Uses the NetworkSet Object to store or find Network instances.	M
DI ConnectsTo	Uses the ConnectsTo Reference to associate Devices with a Network.	M

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

Table 77 – DeviceIntegrationHost_Client_Facet definition

Conformance Unit	Description	Optional/ Mandatory
DI DeviceTopology	Uses the DeviceTopology Object as starting Node for the communication topology of the Devices to integrate.	M
DI Offline	Uses offline and online representations of Devices including the Methods to transfer data from or to the Device.	M