General Information¶
PDC Introduction¶
The PDC (Parsing Definition Configuration) contains the description of transmitted metrics. It also contains the CAN message structure of the logged data. For details on the data storage on DataPlatform and time series data handling, read Time Series Handling in the DataPortal User Manual.
The PDC is required to display the signals in the DataPortal.
The PDC is an XML file with the file extension .pdc and has a special format that can be edited with any text/source code editor application.
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.
A PDC can be assigned to both models and machines. The assignment to a machine has higher priority than the assignment to a model. If a model is assigned to PDC(a) and a specific machine (belonging to this model) is assigned to PDC(b), the model assignment for this machine is deactivated and PDC(b) is assigned. To reassign the device to its model PDC(a), the individual assignment to PDC(b) of the device must be deleted first.
Legend¶
| Term | Description |
|---|---|
| key="..." | The key is a unique reference within the PDC. |
| A key definition must always have a unique value in the file and is included so that later on this value can be referenced to. | |
Tags <tag> </tag> |
There is a start tag <tag> and an end tag </tag>. Within these tags there may be statements and/or attributes with values. |
| Attribute | The attributes are the central information for the definition of references, the interpretation of CAN messages and the displaying on the DataPortal. They are used in the PDC within the tags (e.g. key, lang, value, canId, format). |
| Contents | Content is the text that is displayed within the quotation marks. The content is also called attribute value. |
Proemion Standard Metrics¶
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.
For this, Proemion provides predefined signal keys which cover a large part of the usual machine data.
The signal designation (label) can be defined freely for the DataPortal. Analyses are only performed in the database using the signal keys.
In Standard Metrics you can find an example of how to use the Proemion Standard Metrics in your PDC.
Note
Especially the data transfer and analysis according to the AEMP API need standardized metrics to work properly and without an unnecessary complexity.
For more detailed information, go to Proemion Standard Metrics documentation. Or go to our website: Proemion > Customers > Help Center
Proemion System Metrics¶
Some of the mentioned Proemion Standard Metrics in Standard Metrics are reserved for Proemion Services. Those signals are not available for parsing machine data in OEM use cases. In the standard keys below, you can find a small choice of Proemion System Metrics which are exclusively used for Proemion Standard data.
| Key | Label | Description |
|---|---|---|
| value.common.cu.sim.traffic.month | label.[Key] |
Volume of SIM traffic |
| value.common.system.external.machine.weather.temperature | label.[Key] |
Temperature based on GPS-Position |
In chapter Data Consumption, you can find a detailed description of how to implement the SIM data consumption during the last month in the PDC.
Warning
These signals (keys) are not allowed to be used in <ParsingDefinition>.
For more detailed information, go to Proemion Standard Metrics documentation. Or go to our website: Proemion > Customers > Help Center
Depending on your hosting contract, not all system metrics are available or can be displayed with values in the DataPortal.