A Device Integration Host is a Server that manages integration of multiple Devices in an automation system and provides Clients with access to information about Devices regardless of where the information is stored, for example, in the Device itself or in a data store. The Device communication is internal to the host and may be based on field-specific protocols.
The Information Model specifies the entities that can be accessed in a Device Integration Host. This standard does not define how these elements are instantiated. The host may use network scanning services, the OPC UA Node Management Services or proprietary configuration tools.
One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore it represents the Devices of the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them.
Figure 28 and Figure 29 illustrate an example configuration and the configured topology as it will appear in the Server AddressSpace (details left out).
Figure 28 – Example of an automation system
The PC in Figure 28 represents the Server (the Device Integration Host). The Server communicates with Devices connected to Network “A” via native communication, and it communicates with Devices connected to Network “B” via nested communication.
Figure 29 – Example of a Device topology
Coloured boxes are used to recognize the various types of information.
Entry points assure common behaviour across different implementations:
- DeviceTopology: Starting node for the topology configuration. See 7.2.
- DeviceSet: See 5.9.
- NetworkSet: See 6.6.