Standard System Metrics¶
Metrics which are used for standard Proemion services.
CAUTION
PDCs with System Metrics in Parsing Definition will not be accepted for upload.
The standard keys listed here are exclusively used by the DataPlatform for parsing Proemion standard data and must not be used in any <ParsingDefinition>. For more explanations on the Parsing Definitions please refer to the PDC Manual).
Note
When creating a new PDC manually, it is highly recommended to use the following PDC template containing the necessary elements: PDC Template. For a reference of the metrics to be used, Go to Download Center > 02_DataPlatform Documentation > 03_Data Transfer and InterpretationProemion_DemoConfig.pdc. For more information, see Migration Guide for the Signal Catalog.
Note
It is recommended to define the label key as the signal key prefixed with label (label.[Key]).
The reception of new metrics usually updates the machine's timestamps LastContact and LastDatapoint which can be also viewed in the DataPortal, see DataPortal User Manual → "Machines Overview". But the signal keys with the following namespaces don't have an influence on these timestamps as they are not produced by the device:
value.common.system.*
value.common.external.*
value.common.cu.* // except value.common.cu.sensors.*
| Key | Standard Unit (Prefix: predefined.unit.) |
|---|---|
value.common.cu.sim.traffic.month |
datavolume.BYTE |
value.common.cu.celloperator |
TEXT |
value.common.cu.config.date |
TEXT |
value.common.cu.config.version |
TEXT |
value.common.cu.hours.operation |
HOUR |
value.common.cu.mode |
NUMBER |
value.common.cu.signal.quality |
powerlevel.DECIBEL-MILLIWATTS |
value.common.cu.sim.id |
TEXT |
value.common.cu.version.hw |
TEXT |
value.common.cu.version.sw |
TEXT |
value.common.machine.geo.altitude |
length.METER |
value.common.machine.geo.heading |
geoposition.DECIMAL_DEGREE |
value.common.machine.geo.latitude |
geoposition.DECIMAL_DEGREE |
value.common.machine.geo.longitude |
geoposition.DECIMAL_DEGREE |
value.common.machine.geo.speed |
speed.KILOMETERS_PER_HOUR |
value.common.system.external.machine.weather.airpressure |
pressure.HECTOPASCAL |
value.common.system.external.machine.weather.humidity |
PERCENT |
value.common.system.external.machine.weather.precipitationrate |
length.MILLIMETER |
value.common.system.external.machine.weather.temperature |
temperature.CELSIUS |
value.common.system.external.machine.weather.uv.index |
NUMBER |
value.common.system.external.machine.weather.windspeed |
speed.METERS_PER_SECOND |
value.common.system.machine.platform.ft.traffic.delta |
datavolume.BYTE |
value.common.system.machine.platform.numberof.measurements.delta |
datavolume.BYTE |
value.common.system.machine.platform.rt.traffic.delta |
datavolume.BYTE |
value.common.system.machine.platform.traffic.delta |
datavolume.BYTE |
value.common.system.machine.platform.clf.traffic 1 |
datavolume.BYTE |
Note
1 The signal key value.common.system.machine.platform.clf.traffic must be added in the PDC, if you need to display it in the DataPortal. Otherwise, calling /timeseries is sufficient and an adaption of the PDC isn't required. Consider that in the API, the values will only show up in /timeseries reports where a time period is shown, i.e. upon timeseries queries, not on any measurements query where only the latest value is queried. Thus, it won't show up in the DataPortal where only the last value is shown.