Naming Convention¶

The configuration process of a SMARTUNIFIER Instance involves the creation of configuration components such as Information Models, Communication Channels, Mappings, Device Types and the Communication Instances themselves. Each configuration component needs to have a group and a name as an identifier. The identifier helps to organize configuration components and build up a hierarchical structure.

Group

The group can be used to leverage the concept of paths, similar to those used in file systems, by concatenating logical entities together. In most cases, there is already a naming convention or a certain style of naming for equipment in place. This convention can be adopted when naming and organizing the configuration components.

Name

The name assigned to each configuration component should clearly reflect the entity being integrated. The following table provides examples of appropriate naming conventions for the specific configuration components:

Naming Examples¶

We recommend the following naming convention for improved comprehensibility.

Information Models & Communication Channels¶

Information Models and its associated Communication Channels should both have the same naming.

Mappings¶

Device Types¶

Communication Instances¶

The Communication Instance provides the connectivity between the physical equipment on the shopfloor and IT-systems. It is the most granular configuration component that is created.