Introduction

Metrics which show the same value for different machines and machine types should have the same signal key for the purpose of a unified data analysis. Especially the data transferring and analysis according to the AEMP and ISO 15143-3 standard need standardized metrics to work properly and without an unnecessary complexity. These metrics are required for an automatic transforming of the values according to the ISO 15143-3 standard so that third-party client software is able to operate with these data sets. Which AEMP signals are currently implemented is described in the AEMP API documentation.

Syntax definition

alphanumeric = "0" | "1" | ... | "9" | "a" | "b" | ... | "z" | "A" | "B" | ... | "Z" ;
dot = "." ;
string = alphanumeric { alphanumeric } ;
custom_string = string  { dot string } ;
network = custom_string ; (*Remark: "network" is optional, in our case only used by automatically generated signal keys for J1939 metrics in case of reception from two physical CAN interfaces*)

component_name = custom_string ;
signal_group = custom_string ;
signal_name = custom_string ;
unit_name = custom_string ;

oem_name = "common" | "custom" | custom_string; ("common" is reserved for Proemion predefined signals)

(*signal key syntax:*)
signal_key = "value" dot oem_name [ dot "network" ] dot component_name dot [ signal_group dot ] signal_name ;

(*signal name syntax:*)
signal_name =  /^value.custom\.[a-zA-Z0-9_-]+(\.[a-zA-Z0-9_-]+)*$/;

(*unit key syntax:*)
unit_key = "unit" dot oem_name dot unit_name ;

(*label key syntax:*)
label_key = "label" dot signal_key | "label" dot unit_key;