Standard Metrics

The subsequent subchapters provide lists of Proemion Standard Metrics.

The chapter Standard Metrics Explanation below describes the specific keys.

The standard metrics should be used dependent on the use cases.

Consider that there are more metrics dedicated to different components of the machine, see the following subchapters.

Note

If there are standard signals missing that might be useful for other customers, too, you may request them via the Service and Support to make them available.

• Standard System Metrics are signals written by the system, but customers may declare those signals in the PDC within <ValueDefinition> in order to read and display them. The Standard System Metrics are reserved for being updated by Proemion services and are not available for parsing machine data, i.e. writing new values to the signals. Therefore, you must not reference the signals within <ParsingDefinition> as the values would be wrongly updated twice - by the system and through the CLF → PDC.

• Use System-Used Signals, if you want to use additional features e.g. the DataScience feature Fuel Guard (DataScience). Here, you must both declare and parse the necessary metrics in the PDC in order for the machines to provide the signals.

• For defining your own signal keys, adhere to Custom Metrics.

• All the signal keys, whether they are standard or custom metrics, should use the predefined units, see Units.