Mapping Data to Tags

The way data is mapped to tags determines how received information is processed as well as the location of information to be read.

This page provides a brief introduction to the different mapping types, linking to specific pages where the individual property configurations are discussed.

In the Message Configuration object, individual mapping types are selected in the Mapping Type property located in the Message Description Properties.

The available mapping types are:

  • Direct Mapping: This mapping type maps the incoming data 1:1 onto tags. This mapping can either be included in this message configuration, or the central mapping can be used.

  • Group Mapping: This type of mapping addresses a group of similar devices with the same message configuration. This is very useful if the required equipment is selected during EBR execution. Therefore, only the equipment selector has to be changed.

  • Flexible Mapping: This mapping type is utilised to read realtime values using a predefined message format. Values are identified by an EquipmentId and Tag combination. This combination is mapped to a path by a mapping table.

  • Historian Mapping: This mapping type is used to read historical values with a predefined message format. Values are identified by an EquipmentId and Tag combination. Additionally, a parameter is given to identify the requested aggregation function for the historian read.

  • Function Mapping: This type of mapping executes a function from a library after receiving a corresponding message. An additional function, from the same library, is repeatedly called to check and compile the required outgoing data.

  • Custom Script Mapping: This type of mapping executes a custom Lua script after receiving a matching message. An additional custom script is called repeatedly to check and compile the required outgoing data.