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