A Device Integration Hostis a Serverthat manages integration of multiple Devicesin an automation system and provides Clientswith access to information about Devicesregardless of where the information is stored, for example, in the Deviceitself or in a data store. The Devicecommunication is internal to the host and may be based on field-specific protocols.

The Information Modelspecifies 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 Servicesor proprietary configuration tools.

One of the main tasks of the Information Modelis to reflect the topology of the automation system. Therefore, it represents the Devicesof the automation system as well as the connecting communication networks including their properties, relationships, and the operations that can be performed on them.

Figure 25and Figure 26illustrate an example configuration and the configured topology as it will appear in the Server AddressSpace(details left out).

image028.png

Figure 25– Example of an automation system

The PC in Figure 25represents the Server(the Device Integration Host). The Servercommunicates with Devicesconnected to Network“A” via native communication, and it communicates with Devicesconnected to Network“B” via nested communication.

image029.png

Figure 26– Example of a Device topology

Coloured boxes are used to recognize the various types of information.

Entry points assure common behavior across different implementations: