ISA95 mode

The connector, when instructed to run in the ISA95 mode, makes a few assumptions about where to search for templates. The following explains the principle:

ISA95 templates

In the ISA95 mode, every OPC UA object that the connector replicates to PI AF is checked if it has the DefinedByEquipmentClass reference. If it does, the DisplayName of this reference is used as the template name for the resulting PI AF element. If there are more DefinedByEquipmentClass references (as in the screenshot above), the DisplayNames of all of them are concatenated and the PI AF template name is formed from them. If an object does not have such references, the connector falls back and checks the HasTypeDefinition reference deriving the PI AF template from that. That means that the logic for generating template names (for the objects without the DefinedByEquipmentClass reference) is exactly the same as in the Generic mode.