Commission Implementing Regulation (EU) 2025/1707 of 25 July 2025 laying down rules for the application of Regulation (EU) 2024/1257 of the European Parliament and of the Council as regards specific methods, requirements and tests, including compliance thresholds, for OBFCM devices and OBM systems, characteristics and performance of driver warning systems and inducement methods and methods to assess their operation, EVP format and data and methods of communication of EVP data of motor vehicles of categories M1 and N1

Article 1

Subject matter and scope

• (a) on-board monitoring (OBM) systems including their sensors and driver warning systems;

• (b) on-board fuel and electric energy consumption monitoring (OBFCM) devices;

• (c) the format and data and off-board communication methods for the environmental vehicle passport (EVP);

• (d) methods for in-vehicle display of environmental data about the vehicle type and the environmental performance of the individual vehicle;

• (e) methods and procedures to establish the absence of manipulation devices and manipulation strategies.

• (a) M1 and N1;

• (b) N2 designated as ‘Euro 7ext’ and ‘Euro 7Gext’ in accordance with Article 5 of Regulation (EU) 2024/1257.

Article 2

Definitions

For the purpose of this Regulation, the following definitions shall apply:

• (1) ‘OBM data’ means data produced by the ‘on-board monitoring system’ or ‘OBM system’, including battery durability data;

• (2) ‘OBM trip’ means each period of vehicle operation that starts with the activation of the propulsion system and ends with the deactivation of the propulsion system. For the purpose of determining the end of an OBM trip, sequences of engine shut-off events followed by an engine re-start commanded by the vehicle control system (as a result of the operation of stop-start systems, hybrid vehicle control or automatic stall recovery) shall not be considered a deactivation of the propulsion system;

• (3) ‘OBM trip data’ means OBM data that relate to a particular OBM trip;

• (4) ‘OBM hash function’ means a standard mathematical algorithm implemented on-board the vehicle that takes a set of OBM data and converts it into a string of characters with a fixed predetermined length, and whose properties can be used to randomly select OBM data to be transmitted over the air, or to verify the integrity of the transmission of OBM data while preserving their anonymous nature;

• (5) ‘OBM hash value’ means the output of the OBM hash function for a given input;

• (6) ‘OBM data schema’ means a fixed structure for data that are input to the OBM hash function;

• (7) ‘generic scan tool’ means an external test equipment used for standardised off-board communication with the vehicle’s electronic control systems;

• (8) ‘service tool’ means a specialised external test equipment used to perform manufacturer-defined service operations via communication with the vehicle’s electronic control systems;

• (9) ‘QR code’ means a machine-readable matrix code that links to information;

• (10) ‘Auxiliary Emission Strategy’ or ‘AES’ means an emission strategy that becomes active and replaces or modifies a BES for a specific purpose and in response to a specific set of ambient or operating conditions and only remains operational as long as those conditions exist;

• (11) ‘Base Emission Strategy’ or ‘BES’ means an emission strategy that is active throughout the speed and load operating range of the vehicle unless an Auxiliary Emission Strategy is activated.

Article 3

General requirements for OBM systems

Article 4

General requirements for the excess exhaust emissions driver warning system

• (a) assign the OBM monitoring status of NOx and particulate matter (PM) in accordance with Article 5;

• (b) provide driver warnings in accordance with Annex II as long as one or more of the exhaust emissions monitoring statuses is in ‘Error’ status;

• (c) if driver warnings referred to in point (b) are not acted upon within the period specified in Annex II, limit vehicle use through harmonised inducement methods described in that Annex until appropriate repairs are carried out.

Article 5

OBM monitoring status of exhaust emissions

• (a) ‘Normal’ status, which shall indicate that the emissions control systems installed on the vehicle are judged to be functioning adequately and the OBM system has high confidence in the accuracy of OBM monitoring;

• (b) ‘Intermediate’ status, which shall indicate that the OBM system is unable to make a conclusive assessment of the status of the relevant emissions control systems or that an increased uncertainty in OBM monitoring values may exist;

• (c) ‘Error’ status, which shall indicate that faults or tampering that prevent adequate emissions control or monitoring and justify a repair have been identified.

As an indicative target when designing the OBM system, the manufacturer shall ensure that if the OBM determines that the vehicle may be in a state where its exhaust emissions as evaluated via a real-driving emissions (RDE) or other applicable in-service conformity test would be equal or higher than 2,5 times the applicable emission limit, the ‘Error’ status shall be activated.

Article 6

Calculation of NOx emissions for each OBM trip

• (a) measurements performed by on-board sensors;

• (b) modelled data;

• (c) a combination of measurements performed by on-board sensors and modelled data.

Article 7

Calculation of other OBM data for each OBM trip

Article 8

Calculation of hash value and on-board processing of OBM data

Article 9

Over-the-air transmission of OBM data

Article 10

Access to OBM data via OBD port

Article 11

Submission of anonymous OBM data

Article 12

Requirements for emission type-approval

Article 13

In-service conformity checks of OBM systems

Measures to ensure in-service conformity of OBM systems shall be taken in accordance with the conformity of production arrangements as laid down in Article 31 of Regulation (EU) 2018/858, Annex IV to Regulation (EU) 2018/858 and Part A of Annex IV to this Regulation.

Article 14

OBM monitoring status and eligibility of vehicles for in-service conformity checks

• (a) the presence of one or more OBM monitoring statuses set to ‘Error’ as referred to in Article 5(1), point (c);

• (b) the presence of one or more ongoing OBD faults for which a malfunction indicator is active;

• (c) other faults that are apparent from a visual inspection of the vehicle prior to the trip.

Article 15

Market surveillance of OBM systems

Market surveillance authorities shall perform a verification of the compliance of OBM systems with the Articles 3 to 10 in accordance with part B of Annex IV.

Article 16

Requirements for OBFCM devices

Article 17

Environmental vehicle passport

Article 18

In-vehicle display of environmental data

The manufacturer shall ensure that the environmental data about the vehicle type and the environmental performance of individual vehicles listed in Annex VI are displayed inside the vehicle in accordance with that Annex.

Article 19

Manipulation devices and manipulation strategies

Article 20

Entry into force

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

This Regulation shall be binding in its entirety and directly applicable in all Member States.

LIST OF ANNEXES

ANNEX I	OBM data
Part A	Parameters and signals used by the OBM system
Part B	OBM hash function and on-board processing of OBM data
Part C	Over-the-air transmission of OBM data
Appendix 1	OBM parameters to support vehicle testing
Appendix 2	OBM trip parameters
Appendix 3	OBM lifetime parameters
Appendix 4	OBM outbox property parameters
Appendix 5	Battery durability parameters
Appendix 6	OBM data storage parameters
Appendix 7	OBM data schemas
Appendix 8	OBM data processing flowchart
ANNEX II	Driver warnings and inducement methods of the excess exhaust emissions driver warning system
Appendix 1	Schematic diagrams
ANNEX III	Declaration of compliance
Appendix 1	Manufacturer’s declaration of compliance with the OBM requirements for the purposes of type-approval
Appendix 2	Simple demonstration of the functioning of the OBM system. Workflow description and steps
ANNEX IV	Methods for in-service conformity checks and market surveillance of OBM systems
Part A	In-service conformity checks of OBM systems
Part B	Market surveillance of OBM systems
ANNEX V	Environmental vehicle passport
Appendix 1	Environmental vehicle passport parameters
ANNEX VI	In-vehicle display of environmental data
Appendix 1	Parameters to be displayed inside the vehicle
ANNEX VII	Manipulation devices and manipulation strategies

ANNEX I

OBM DATA REQUIREMENTS

This Annex describes the requirements related to OBM data. It provides the technical specification of the parameters produced by the OBM system, the requirements for on-board processing of OBM data and for its over-the-air transmission.

Detailed technical specification of certain OBM parameters is provided in Part A of this Annex. A comprehensive list of parameters with a basic technical specification is provided in Appendices 1 to 6.

The requirements for on-board processing and over-the-air transmission of OBM data are covered in Part B of this Annex. The OBM data schemas are defined in Appendix 7. Appendix 8 is an illustrative flowchart of the OBM trip data processing.

Part C of this Annex contains supplemental technical specifications for the over-the-air transmission of OBM data.

PART A

OBM parameters

The manufacturer shall make all parameters listed in Appendices 1 and 3 to 6 to this Annex available on demand through the serial port on the standardised data link connector according to the specifications in those Appendices.

Unless otherwise specified, manufacturers shall make available parameters encompassing their full useful value range, with a level of accuracy commensurate with the capabilities of the control systems.

1. OBM parameters to support vehicle testing

• 1.1.For those parameters where it is indicated in Appendix 1 that they are part of the instantaneous data stream, these shall be updated by the applicable control unit at a minimum frequency of 1 Hertz.

• 1.2.Parameters that are not applicable to the vehicle fuel type or powertrain technology may be omitted.

• 1.3. Exhaust mass flow-tailpipe (parameter 1.11)

• 1.3.1.The OBM system shall provide a parameter ‘Exhaust mass flow – tailpipe’ to indicate the total exhaust mass flow at the tailpipe.

• The parameter shall be calculated as the average mass of exhaust mass flow during the previous 1 second prior to being updated and shall be updated at least once per second.

• 1.4. Tailpipe NOx concentration (parameter 1.13)

• 1.4.1.The OBM system shall provide a parameter ‘Tailpipe NOx concentration’ to indicate the NOx emission concentration at the tailpipe. The parameter shall be provided for the whole duration of the OBM trip and may be based on sensor measurement, modelled data, or a combination thereof.

• 1.4.2.The parameter shall be calculated as the average concentration of NOx emissions during the previous 1 second prior to being updated and shall be updated at least once per second.

• 1.5. Modelled status (parameters 1.14 and 1.16)

• 1.5.1.The OBM system shall provide parameters ‘Tailpipe NOx concentration modelled status’ and ‘Tailpipe NOx mass flow modelled status’ to indicate how the tailpipe NOx concentration and mass flow concentration values are determined. Both parameters shall have either one of the following two statuses:

• [0]. indicates that the applicable parameter value is calculated with NOx sensor input.

• [1]. indicates that the applicable parameter value is calculated without NOx sensor input.

• 1.6. Tailpipe NOx mass flow (parameter 1.15)

• 1.6.1.The OBM system shall provide a parameter ‘Tailpipe mass flow’ to indicate the NOx emission mass flow at the tailpipe. The parameter shall be provided for the whole duration of the OBM trip and may be based on sensor measurement, modelled data, or a combination thereof.

• 1.6.2.The parameter shall be calculated as the average mass of NOx emissions during the previous 1 second prior to being updated and shall be updated at least once per second.

• 1.7. NOx to fuel mass ratios (parameters 1.19 - 1.27)

• 1.7.1.The OBM system shall provide separate parameters to calculate the ratio between NOx emissions and the fuel mass. This calculation process starts with all values of ‘NOx to fuel mass ratio (i)’ set to a default value of zero, and consists of the following three steps:

• 1.7.2.STEP 1: The following three parameters shall be calculated:

• (a) ‘Cumulative NOx – 100 km’ (g) (parameter 1.19). This parameter integrates the ‘tailpipe NOx mass flow’ (g/s). The parameter shall have a resolution of 0,0001g or any smaller mass, a minimum value of zero and a maximum value of at least 100 000  g.

• (b) ‘Cumulative fuel mass – 100 km’ (kg) (parameter 1.20). This parameter integrates the ‘Engine fuel flow’ (g/s), with a conversion from the unit grams into kilograms. The parameter shall have a resolution of 0,0000001 kg or any smaller mass, a minimum value of zero and a maximum value of at least 200 kg.

• (c) ‘Cumulative distance – 100 km’ (km) (parameter 1.21). This parameter integrates travelled distance by the vehicle. The parameter shall have a resolution of 0,01 km or any smaller distance, a minimum value of zero and a maximum value of at least 100 km.

• 1.7.2.1.These parameters shall be continuously integrated, except when at least one of the following conditions apply:

• (1) the engine is off;

• (2) the time after first engine start during the OBM trip is less than 800 seconds;

• (3) the parameter ‘Aftertreatment regeneration status’ (parameter 1.28) indicates that an active particulate filter regeneration is in progress;

• (4) the ambient temperature is below -7 °C or above 38 °C;

• (5) the vehicle speed is above 160 km/h;

• (6) the altitude is above 1 300  m above mean sea level;

• (7) a tracked auxiliary emission strategy (AES) monitored by OBM is active as defined in paragraph 2.8.2;

• (8) when the vehicle is in a long cooldown phase;

• (9) when at least one of ‘Monitoring status NOx’ or ‘Monitoring status generic’ is set to ‘Error’ or ‘Intermediate’. In this case, these parameters shall also be reset to zero;

• (10) when an input signal used to calculate any of the cumulated parameters above is deemed to be malfunctioning.

• 1.7.2.2.For the purposes of the integration of parameters 1.19 to 1.21, a ‘long cooldown phase’ shall be understood as covering the following periods:

• — For a period of continuous idling, any period exceeding the first 180 seconds.

• — The first 180 seconds after the vehicle reaches a speed above 1 km/h following a continuous idling period exceeding 180 seconds.

• — The first 180 seconds after a restart of the engine following a continuous engine-off period exceeding 180 seconds.

• 1.7.2.3.When the parameter ‘Cumulative distance – 100 km’ is equal or higher than 100 km, the following step shall be executed:

• 1.7.3.STEP 2:

• The value of ‘NOx to fuel mass ratio (3)’ shall be assigned to ‘NOx to fuel mass ratio (4)’

• The value of ‘NOx to fuel mass ratio (2)’ shall be assigned to ‘NOx to fuel mass ratio (3)’

• The value of ‘NOx to fuel mass ratio (1)’ shall be assigned to ‘NOx to fuel mass ratio (2)’

• The value of ‘NOx to fuel mass ratio (0)’ shall be assigned to ‘NOx to fuel mass ratio (1)’

• The following parameter shall be calculated:

Image omitted; see official source

• When ‘NOx to fuel mass ratio (0)’ has been calculated, the parameters ‘Cumulative NOx – 100 km’, ‘Cumulated fuel mass – 100 km’ and ‘Cumulated distance – 100 km’ shall all be reset to zero.

• Prior to first calculation of each ‘NOx to fuel mass ratio’ parameter since the manufacture of the vehicle, or if the ‘NOx to fuel mass ratio’ parameters are reset during a control unit reprogramming event, or by control unit replacement, a default value of 0xFF for each data byte shall be used.

• 1.7.4.STEP 3:

• The parameter ‘NOx to fuel mass ratio average’ (g/kg) (parameter 1.27) shall be calculated as follows:

Image omitted; see official source

• With n being the number of ‘NOx to fuel mass ratio (i)’ values not equal to 0xFFFF.

• 1.7.4.1.The parameters ‘Cumulative NOx – 100km’, ‘Cumulative fuel mass – 100 km’ and ‘Cumulative distance – 100km’ shall all be reset to zero, and the sequence is repeated from step 1.

• 1.7.4.2.The ‘NOx to fuel mass ratio (i)’ parameters and the ‘NOx to fuel mass ratio average’ parameter shall consist of 2 data bytes with a minimum value of zero and a maximum value of 200 g/kg.

• 1.7.4.3.The parameters ‘Cumulative NOx – 100 km’, ‘Cumulative fuel mass – 100 km’ and ‘Cumulative distance – 100 km’ shall be reset to zero when diagnostic trouble codes are reset by a generic scan tool or service tool These parameters may also be reset to zero in case of an ECU reprogramming event.

• 1.8. Aftertreatment operational status (parameter 1.31)

• 1.8.1.The OBM system shall provide a parameter ‘Aftertreatment operational status’ to indicate whether the aftertreatment system has reached and maintains the conditions to allow effective abatement of exhaust emissions monitored by the OBM system. This parameter shall have either one of the following two statuses:

• [0]. indicates that the actual conditions do not allow for effective abatement of exhaust emissions monitored by the OBM system.

• [1]. indicates that the actual conditions allow for effective abatement of exhaust emissions monitored by the OBM system.

• 1.8.2.Manufacturers shall provide a description in the type-approval documentation of thresholds and parameters used to calculate the status of this parameter.

• 1.9. OBM inducement system status (parameter 1.45)

• 1.9.1.The OBM system shall provide an ‘OBM inducement system status’ parameter to indicate that the OBM system has activated the vehicle inducement as described in Annex II paragraph 2.4. The parameter shall consist of 4 data bits with the following statuses:

• Bit 0: OBM inducement system is active (0 means FALSE, 1 means TRUE)

• Bit 1: Monitoring status NOx has triggered the OBM inducement system (0 means FALSE, 1 means TRUE)

• Bit 2: Monitoring status PM has triggered the OBM inducement system (0 means FALSE, 1 means TRUE)

• Bit 3: Monitoring status generic has triggered the OBM inducement system (0 means FALSE, 1 means TRUE)

• 1.10. Possible tampering status (parameter 1.46)

• 1.10.1.The OBM system shall provide a ‘Possible tampering status’ parameter to indicate the tampering detection level. This parameter shall have either one of the following three statuses:

• [0]. ‘Level 0 – No tampering detected’.

• [1]. ‘Level 1 – Possible tampering detected’, resulting in at least one of the exhaust emissions monitored by the OBM system having an expected increase, resulting in emissions of up to 2,5 times the applicable emission limit.

• [2]. ‘Level 2 – Possible tampering detected’, resulting in at least one of the exhaust emissions monitored by the OBM system having an expected increase resulting in emissions of more than 2,5 times the applicable emission limit.

• 1.10.2.Once the ‘Possible tampering’ status parameter has been set to level 1 or level 2 it shall not reset to a lower level unless reset by a generic scan tool or service tool.

• 1.11. Monitoring status (parameters 1.47 - 1.49)

• 1.11.1.The OBM system shall provide separate parameters for the ‘Monitoring status NOx’, the ‘Monitoring status PM’ and the ‘Monitoring status generic’ to indicate the OBM monitoring statuses as laid down in Article 4. For each of these monitors the parameter shall have one of the following three statuses as defined in Article 5.

• [0]. Normal status

• [1]. Intermediate status

• [2]. Error status

• 1.12. OBM OTA outbox overwrite counter (parameter 1.55)

• 1.12.1.The OBM system shall provide an ‘OBM OTA outbox overwrite counter’ parameter to reflect the number of times the ‘OBM OTA outbox’ has been overwritten.

• The ‘OBM OTA outbox overwrite counter’ shall increment by 1 if the previous ‘OBM OTA outbox’ data package has not been successfully transmitted as defined in paragraph 8.4. by the time new data have filled the ‘OBM OTA queue’.

• 1.12.2.The parameter shall be reset to zero when diagnostic trouble codes are reset by a generic scan tool or service tool. If the parameter reaches its maximum value, it shall freeze and not reset to zero until reset by a generic scan tool or service tool.

2. OBM trip parameters

• 2.1.OBM trip parameters are those parameters that refer to an OBM trip. They generally characterise the emissions that were generated during the OBM trip, the conditions during which it took place. Some trip parameters related to hashing are used to support the random selection of OBM trips for later over-the-air transmission.

• 2.2.Prior to first calculation of each applicable parameter since the manufacture of the vehicle, reset of stored data using a generic scan tool or service tool or if a parameter is reset due to a control unit reprogramming event, or control unit replacement, a default value of 0xFF for each data byte shall be adopted unless otherwise specified.

• 2.3.For parameters not required to be calculated based on powertrain type, a default value of 0xFF shall be adopted for each data byte.

• 2.4.In case of a malfunction preventing the calculation of an OBM trip parameter, a value of 0xFF for each applicable data byte may be reported where the OBM system is unable to provide a reasonable alternative estimated value through modelling or alternative signals. When 0xFF is provided due to malfunction, bit 2 of parameter 2.22 shall be set.

• 2.5. OBM trip odometer (parameters 2.1 and 2.2)

• 2.5.1.The OBM system shall provide a ‘Vehicle odometer value’ and an ‘OBM trip distance’ value to indicate both the total driven distance in the vehicle lifetime, as indicated to the driver and the total driven distance during the OBM trip at the end of the OBM trip. These odometer values shall use the same data source as the odometer value displayed to the driver.

• 2.6. Idle – time (parameter 2.4)

• 2.6.1.The OBM system shall provide a parameter ‘Idle – time’ to record the cumulated time of engine operation at idle during the OBM trip.

• 2.6.2.For the purpose of calculating this parameter, idle shall mean that the accelerator pedal is released by the driver and either the vehicle speed is less than or equal to one km per hour or engine speed is less than or equal to 200 rpm above normal warmed-up idle (as determined in the drive position for vehicles equipped with an automatic transmission).

• 2.7. Distance-specific NOx (parameter 2.5)

• 2.7.1.The OBM system shall provide a ‘Distance-specific NOx’ parameter to indicate the average mass emissions of NOx during the OBM trip.

• 2.7.2.The ‘Distance-specific NOx’ parameter shall be calculated as the total mass emissions of NOx during the OBM trip divided by the OBM trip distance at the end of the OBM trip. For OBM trips with a total driven distance during the OBM trip below 1 km, the total mass emissions of NOx during the OBM trip shall be divided by 1 km.

• 2.8. OBM trip ratios (parameters 2.9 - 2.22)

• 2.8.1.The OBM system shall provide various OBM trip ratios. Each ratio shall be calculated as the cumulative distance driven while meeting the conditions during the OBM trip, divided by the OBM trip distance.

• 2.8.2. Aftertreatment status and emission control system ratio (parameters 2.9 - 2.12)

• 2.8.2.1.The OBM system shall provide OBM trip aftertreatment status ratio parameters to reflect the percentage of the OBM trip distance driven with the emissions aftertreatment / control systems in specific conditions:

• (a) The parameter ‘Regeneration distance ratio’ (parameter 2.9) shall represent the percentage of the OBM trip distance where at least one aftertreatment regeneration process is ongoing;

• (b) The parameter ‘Monitored AES distance ratio’ (parameter 2.10) shall represent the percentage of the OBM trip distance where at least one monitored AES is active as indicated by the AES status parameter;

• (c) The parameter ‘Reagent inhibited ratio’ (parameter 2.11) shall represent the percentage of the OBM trip distance with reagent delivery to the exhaust aftertreatment system prevented due to environmental conditions;

• (d) The parameter ‘Modelled data ratio’ (parameter 2.12) shall represent the percentage of the OBM trip distance driven where the distance specific emissions data is calculated without active NOx sensor inputs.

• 2.8.3. Speed bin ratios (parameters 2.13 - 2.16)

• 2.8.3.1.The OBM system shall provide speed bin ratio parameters to reflect the percentage of the OBM trip distance driven in different speed bins during the OBM trip. The Speed bin ratio parameters are defined as:

• (a) ‘Speed – urban slow ratio’: vehicle speed lower than or equal to 30 km/h

• (b) ‘Speed – urban ratio’: vehicle speed greater than 30 km/h and lower than or equal to 60 km/h

• (c) ‘Speed – rural ratio’: vehicle speed greater than 60 km/h and lower than or equal to 90 km/h

• (d) ‘Speed – motorway ratio’: vehicle speed greater than 90 km/h

• 2.8.4. Distance EV ratio (parameter 2.17)

• 2.8.4.1.The OBM system shall provide a ‘Distance EV ratio’ parameter to reflect the percentage of the OBM trip distance driven without the use of the engine.

• 2.8.5. OBM trip condition ratios (parameters 2.18 - 2.21)

• 2.8.5.1.The OBM system shall provide OBM trip condition ratio parameters to reflect the percentage of the OBM trip distance driven in specific conditions:

• (a) the parameter ‘Ambient temperature – low ratio’ (parameter 2.18) shall represent the percentage of the OBM trip distance with ambient temperatures below 0 °C

• (b) the parameter ‘Ambient temperature – high ratio’ (parameter 2.19) shall represent the percentage of the OBM trip distance with ambient temperatures higher than 35 °C

• (c) the parameter ‘Altitude – high ratio’ (parameter 2.20) shall represent the percentage of the OBM trip distance at altitudes higher than 700 m above mean sea level

• (d) the parameter ‘Outside extended ambient conditions ratio’ (parameter 2.21) shall represent the percentage of the OBM trip distance, where one or more of the following conditions apply:
• — ambient temperature is lower than -7 °C or higher than 38 °C
• — the altitude is higher than 1 300  m above mean sea level

• 2.8.6. MI status (parameter 2.22)

• 2.8.6.1.The OBM system shall provide a ‘MI status (end of trip)’ parameter to indicate failure status during the OBM trip. The parameter shall consist of three data bits with the following statuses:

• Bit 0: Indicates MI status at the end of the OBM trip (0 means MI off, 1 means MI on)

• Bit 1: Indicates a malfunction was detected during this OBM trip that would normally activate the MI once the necessary consecutive detection criteria for MI activation are met (e.g., a pending fault code was stored). 0 means no faults detected, 1 means at least one applicable failure detected during an OBM trip

• Bit 2: Indicates a malfunction was detected during this OBM trip that resulted in at least 1 OBM trip parameter adopting a default value as defined in paragraph 2.4 (0 means no faults detected, 1 means at least one applicable failure detected during an OBM trip)

• In case the powertrain technology fitted to the vehicle does not support an MI status, bits 0 and 1 shall be reported as zero.

• 2.9. OBM Monitoring, OBM Inducement and Possible tampering statuses (end of trip) (parameters 2.25 – 2.29)

• 2.9.1.The OBM system shall provide OBM monitoring, OBM inducement and tampering detection level statuses to reflect the statuses of the monitors and inducement systems defined in paragraphs 1.9 to 1.11.

• 2.9.2. Manufacturer-reserved OBM trip parameters (parameter 2.30)

• 2.9.2.1.The OBM system shall provide ten ‘manufacturer-reserved’ parameters. These may be optionally employed by the manufacturer to report manufacturer-defined OBM data. Personal data shall not be included in these parameters. Unused data parameters shall be filled with zero values.

• 2.9.3. OBM trip hash validity status (parameter 2.31)

• 2.9.3.1.The OBM system shall provide a parameter ‘OBM trip hash validity status’ to indicate successful hashing of the OBM trip data package.

• [0]. indicates that computation of the ‘OBM trip hash value’ is incomplete.

• [1]. indicates that computation of the ‘OBM trip hash value’ has completed successfully and that the truncated hash value is saved to the applicable OBM trip data storage as defined in paragraph 9.6.

• 2.9.3.2.Prior to first calculation since the manufacture of the vehicle, reset of stored data using a generic scan tool or service tool or parameter reset due to a control unit reprogramming event, or control unit replacement, a default value of 0x00 for each data byte shall be adopted unless otherwise specified.

• 2.9.4. OBM trip hash value (parameter 2.32)

• 2.9.4.1.The OBM system shall provide a parameter ‘OBM trip hash value’ to record the OBM trip hash value resulting from the hash function defined in paragraph 9.6.

• 2.9.4.2.Until computation of the ‘OBM trip hash value’ of the applicable OBM trip data is completed each allocated data byte of the parameter shall adopt a value equal to 0xFF.

3. OBM lifetime parameters

• 3.1.All lifetime parameters listed in Appendix 3 shall be made available on demand through the serial port on the standardised data link connector of the OBM system.

• 3.2.For those parameters that are not applicable to the vehicle fuel type or powertrain technology, availability through the serial port on the standardised data link connector of the OBM system may be omitted.

• 3.3.By way of exemption from the reset conditions specified in the standards referred to in Part A, once the vehicle has entered into service, lifetime values shall be preserved.

• 3.4.In case of malfunctions affecting the values of lifetime counters, or replacement of the relevant control units, the counters may be frozen or reset simultaneously, as applicable, to ensure that the values remain fully synchronised.

• 3.5. NOx mass (lifetime) (parameter 3.1)

• 3.5.1.The OBM system shall provide parameter ‘NOx mass (lifetime)’ parameter to indicate the lifetime NOx mass emission of the vehicle. The value of this parameter shall be calculated by integration of parameter ‘Tailpipe NOx mass flow’ (parameter 1.15) at a time increment of 1 second.

• 3.6. Odometer value (parameter 3.5)

• 3.6.1.The OBM system shall provide a parameter ‘Odometer value’ to indicate the odometer value indicated to the vehicle user.

• 3.7. Total distance travelled – EV (lifetime) (parameter 3.6)

• 3.7.1.The OBM system shall provide parameter ‘Total distance travelled – EV (lifetime)’ to indicate the total distance that the vehicle has travelled in full electric mode, i.e., without the use of the engine.

• 3.8. Speed bin ratios – lifetime (parameter 3.11 - 3.15)

• 3.8.1.The OBM system shall provide speed bin ratio parameters to reflect the percentage of the OBM trip distance driven in different speed bins during the vehicle lifetime. The Speed bin ratio – lifetime parameters are defined as:

• (a) ‘Speed – urban slow ratio – lifetime’: vehicle speed lower than or equal to 30 km/h

• (b) ‘Speed – urban ratio – lifetime’: vehicle speed greater than 30 km/h and lower than or equal to 60 km/h

• (c) ‘Speed – rural ratio – lifetime’: vehicle speed greater than 60 km/h and lower than or equal to 90 km/h

• (d) ‘Speed – motorway ratio – lifetime’: vehicle speed greater than 90 km/h and lower than or equal to 145 km/h

• (e) ‘Speed outside extended – lifetime’: vehicle speed greater than 145 km/h

• 3.9. Total Distance Travelled - OBM (lifetime) (parameter 3.4)

• 3.9.1.The OBM system shall provide a parameter ‘Total distance travelled – OBM (lifetime)’ to indicate the odometer value associated with the parameter ‘NOx Mass (lifetime)’. The parameter shall include distance travelled during the lifetime of the vehicle both with the internal combustion engine running and when the vehicle is driven in full electrical mode.

4. OBM outbox property parameters

• 4.1.All ‘OBM OTA outbox’ parameters listed in Appendix 4 to this Annex shall be made available on demand through the serial port on the standardised data link connector of the OBM system.

• 4.2. OBM version number (parameter 4.1)

• 4.2.1.The OBM system shall provide an ‘OBM version number’ to indicate the version of the base OBM system and the manufacturer implementation version. The ‘OBM version number' parameter shall consist of 2 data bytes.

• 4.2.2.The base OBM system version shall be represented in a two-digit number ranging from 00 to 64. Vehicles complying to this Regulation shall have a base OBM system version number of 01, corresponding to the OBM data schema specified in Appendix 7.

• 4.2.3.The manufacturer implementation version number may be used by the manufacturer to designate specific schemes where the manufacturer defines data as described in paragraph 4.3. The manufacturer implementation version number shall be represented in a three-digit number ranging from 000 to 999.

• 4.2.4.The ‘OBM version number' shall be formed as a two bytes integer number by adding the base OBM system version number as the thousands integer (A) to the manufacturer implementation version number (B) as shown below.

• Image omitted; see official source

• 4.3. Manufacturer-reserved outbox parameters (parameter 4.2)

• 4.3.1.The OBM system may provide up to 10 ‘Manufacturer-reserved outbox’ parameters. These may be optionally employed by the manufacturer to report manufacturer-defined outbox metadata. Manufacturers shall clearly describe the data within the type-approval document package.

• 4.4. OBM transmission hash validity status (parameter 4.3)

• 4.4.1.The OBM system shall provide a parameter OBM transmission hash validity status to indicate successful hashing of the ‘OBM OTA outbox’ data package prior to transmission.

• [0]. indicates that computation of the ‘OBM transmission hash value’ is incomplete

• [1]. indicates that computation of the ‘OBM transmission hash value’ has completed successfully and that the hash value is saved to the applicable ‘OBM OTA outbox’ data storage as defined in paragraph 9.8

• 4.4.2.Prior to first calculation since the manufacture of the vehicle, reset of stored data using a generic scan tool or service tool or parameter reset due to a control unit reprogramming event, or control unit replacement, a default value of 0x00 for each data byte shall be adopted unless otherwise specified.

• 4.5. OBM transmission hash value (parameter 4.4)

• 4.5.1.The OBM system shall provide a parameter ‘OBM transmission hash value’ to record the hash value resulting from the hashing function defined in paragraph 9.8.

• 4.5.2.Until computation of the ‘OBM transmission hash value’ of the applicable ‘OBM OTA outbox’ is completed each allocated data byte of the parameter shall adopt a value equal to 0xFF.

5. Battery durability parameters

• 5.1.The values of all parameters listed in Appendix 5 to this Annex shall be made available on demand through the serial port on the standardised data link connector of the OBM system and be made available, for OTA transmission, to the ‘OBM OTA outbox’ defined in paragraph 8.4.

• 5.2.For those parameters that are not applicable to the vehicle fuel type or powertrain technology, availability through the serial port on the standardised data link connector of the OBM system may be omitted.

• 5.3. Current battery lifetime distance (parameter 5.3)

• 5.3.1.The OBM system shall provide a parameter ‘Current battery lifetime distance’ to indicate the distance travelled with the currently installed battery used for propulsion purposes.

• 5.3.2.For vehicles where the lifetime values were reset as described in paragraph 3, or in case that vehicles have battery swapping capabilities, the manufacturer shall fill the ‘Current battery lifetime distance’ value with a different value to best represent the actual distance travelled with the currently installed battery used for propulsion purposes.

• 5.4. Traction battery replacement status (parameter 5.12)

• 5.4.1.The OBM system shall provide a ‘Traction battery replacement status’ parameter to indicate if the battery system has been replaced, repaired or exchanged during the vehicle lifetime. The parameter shall consist of 4 bytes. If the ‘Traction battery replacement status’ parameter is supported by the applicable control unit, the following bits in byte A shall be set:

• Bit 0: shall indicate if battery replacement history is available:

• [0]. indicates battery replacement history is unavailable or unsupported

• [1]. indicates battery replacement history is available

• Bit 1: shall indicate if the battery has been replaced or exchanged:

• [0]. indicates that the battery has not been replaced or exchanged or, when no battery replacement history is available, that no data is available

• [1]. indicates that a battery system repair or exchange has occurred at least once during the vehicle lifetime

• Byte A bits 2-7 and byte B, C and D are reserved for future expansion.

• 5.4.2.If a traction battery replacement status indicator is not supported by the applicable control system a value of 0x00 for each data byte shall be reported.

6. OBM data storage parameters

• 6.1.The contents of the OBM system on board data storage used to record and manage OBM data shall be stored on the vehicle and made available on demand through the serial port on the standardised data link connector of the OBM system.

• 6.2.Where a data parameter specified in the OBM data schemas defined in Appendix 7 is not applicable to the vehicle powertrain type as indicated in the tables in Appendix 2 to Appendix 5, each unused data byte shall be filled with the value 0xFF.

• 6.3.Unused data bytes of manufacturer defined parameters and reserved data allocation shall be filled with the values 0x00.

• 6.4.Prior to first calculation of each applicable parameter since the manufacture of the vehicle, reset of stored data using a generic scan tool or service tool or if a parameter is reset due to a control unit reprogramming event, or control unit replacement a default values of 0xFF for each data byte shall be adopted unless otherwise specified.

• 6.5. OBM recent trips

• 6.5.1.The ‘OBM recent trips’ parameter shall represent the last [10] valid OBM trip data packages as defined in paragraph 8.2 and described in Appendix 6, table 6.1.

• 6.5.2.The data contents of each OBM trip data package shall be stored to maintain the layout and order of data parameters as used for OBM trip data hashing defined in paragraph 9.6.

• 6.6. OBM OTA queue

• 6.6.1.The ‘OBM OTA queue’ parameter shall represent up to [5] stored OBM trip data packages that have been selected for OTA data transmission as defined in paragraph 8.3. and described in Appendix 6 table 6.2.

• 6.6.2.The data contents of each OBM trip data package shall be stored to maintain the layout and order of data parameters as used for OBM trip data hashing defined in paragraph 9.6.

• 6.6.3.When OBM data are cleared using a generic scan tool or service tool the ‘OBM OTA queue’ shall not be reset.

• 6.7. OBM OTA outbox

• 6.7.1.The ‘OBM OTA outbox’ parameter shall represent the ‘OBM OTA outbox’ data package as defined in paragraph 8.4. and described in Appendix 6 table 6.3.

• 6.7.2.The data contents of the ‘OBM OTA outbox’ data package shall be stored to maintain the layout and order of data parameters as used for ‘OBM OTA outbox’ data hashing described in paragraph 9.8.

• 6.8. OBM last transmission

• 6.8.1.The ‘OBM last transmission’ parameter shall represent the stored ‘OBM last transmission’ as defined in paragraph 8.5. and described in Appendix 6 table 6.4.

• 6.8.2.By way of exemption from the reset conditions specified in the standards referred to in Part A, once the vehicle has entered into service, the content of the ‘OBM last transmission’ parameter shall be preserved and shall not be reset when vehicle data is reset using a generic scan tool or service tool.

• 6.9. OBM transmitted hash list

• 6.9.1.The data contents of the ‘OBM transmitted hash list’ parameter represent the contents of the stored ‘OBM transmitted hash list’ as defined in paragraph 8.6 and described in Appendix 6 table 6.5. The contents of the ‘OBM transmitted hash list’ shall be stored in non-volatile memory. Data bytes yet to be filled since the manufacture of the vehicle shall show a value of 0xFF.

• 6.9.2.By way of exemption from the reset conditions specified in the standards referred to in Part A, once the vehicle has entered into service, the content of the ‘OBM transmitted hash list’ parameter shall be preserved. Where technically feasible the stored values shall not reset after control unit software updates and shall not be reset when vehicle data is reset using a generic scan tool or service tool. Only in case of a replacement of the relevant control units, may the content of the ‘OBM transmitted hash list’ be reset to 0xFF.

PART B

On-board processing of OBM data

The on-board processing of OBM data includes the following aspects:

• — the calculation of OBM trip data parameters for every OBM trip and other OBM parameters;

• — the on-board storage and processing of OBM data across dedicated memory spaces on-board the vehicle;

• — OBM data hashing to calculate hash values for specific sets of OBM data. This supports the selection of OBM data for later over-the-air transmission and the verification of the integrity of OBM data.

These aspects are graphically summarised in a flowchart in Appendix 8.

7. Calculation of OBM parameters

• 7.1.The OBM system shall ensure that the parameters listed in Appendices 2 to 5 (other than those that represent static values) are calculated according to their technical specification and the requirements set out in this paragraph. Parameters that are not applicable to the vehicle powertrain technology may be omitted.

• 7.2. Calculation of OBM trip data parameters

• 7.3.Upon the conclusion of each OBM trip (trip end), the OBM system shall finalise the calculation and record all relevant trip parameters defined in Appendix 2.

• 7.4.The calculation of OBM trip data parameters may be omitted if any of the following conditions is met:

• — the ‘OBM trip distance’ (parameter 2.2) is less than 0,1 km at the end of the OBM trip.

• — the ‘OBM trip distance’ (parameter 2.2), ‘OBM trip time’ (parameter 2.3) or ‘Idle – time’ (parameter 2.4) reach their maximum values during the OBM trip.

• — a new OBM trip is started before the calculation of trip data parameters and hashing of the OBM trip data have been completed.

• 7.5.When the calculation of OBM trip data parameters has not been completed, data from the trip may be discarded and not be stored on-board the vehicle. Data from discarded trips shall be included in the update of OBM lifetime parameters as defined in paragraph 7.7.

• 7.6.When the calculation of trip data parameters is complete, the OBM system shall hash the OBM trip data according to paragraph 9.6. The calculation of OBM trip data parameters and hashing of the OBM trip data shall be completed at the latest 10 seconds after the end of the OBM trip.

• 7.7. Calculation of OBM lifetime parameters

• 7.8.At least once after the end of each OBM trip, the OBM shall update the OBM lifetime parameters defined in Appendix 3 in accordance with the specifications and reset rules set out in Appendix 3 and in paragraph 3.

8. On-board storage and processing of OBM data

• 8.1.The OBM system shall make use of the on-board memory spaces described in paragraphs 8.2 to 8.6 to support the processing of OBM data. The content of these memory spaces shall reflect the parameters described in paragraph 6.

• 8.2. OBM recent trips

• 8.2.1.The ‘OBM recent trips’ memory space shall store OBM trip data packages for the 10 most recent OBM trips.

• 8.2.2.OBM data for recent trips shall be managed on a rolling basis. When a new OBM trip data package is added to the ‘OBM recent trips’ memory space, the oldest OBM trip data package shall be deleted unless there are empty positions available.

• 8.3. OBM OTA queue

• 8.3.1.The ‘OBM OTA queue’ memory space shall store up to 5 OBM trip data packages that have been selected for over-the-air transmission as defined in paragraph 9.7.

• 8.3.2.Where an OBM trip data package has been selected for over the air transmission (OTA) according to paragraph 9.7, the OBM system shall copy that OBM trip data package to the ‘OBM OTA queue’.

• 8.3.3.The OBM system shall monitor whether the queue is full.

• — If it is not full, the OBM system shall continue adding subsequent OBM trip data packages until capacity is reached.

• — When the ‘OBM OTA queue’ is full the OBM system shall transfer the contents of the ‘OBM OTA queue’ to the ‘OBM OTA outbox’ and clear the contents of the ‘OBM OTA queue’.

• 8.4. OBM OTA outbox

• 8.4.1.The ‘OBM OTA outbox’ memory space shall be used to prepare OBM data for over-the-air transmission.

• 8.4.2.After transferring the contents of the ‘OBM OTA queue’, the OBM system shall append the following additional parameters to the ‘OBM OTA outbox’:

• — OBM lifetime parameters from Appendix 3;

• — OBM outbox properties parameters from Appendix 4;

• — Battery durability parameters from Appendix 5;

• — The contents of the ‘OBM transmitted hash list’ memory space.

• 8.4.3.The parameter values appended to the ‘OBM OTA outbox’ shall be the parameter values at the time that the ‘OBM OTA queue’ is copied to the ‘OBM OTA outbox’.

• 8.4.4.For parameters not required to be calculated based on powertrain type, a default value of 0xFF shall be adopted for each data byte.

• 8.4.5.After appending these additional data, the OBM system shall perform the hashing of the contents of the OBM OTA outbox according to paragraph 9.8. When a full ‘OBM OTA queue’ triggers the move of new OBM trip data packages to the ‘OBM OTA outbox’ before the ‘OBM OTA outbox’ transmission has completed and was subsequently cleared, the existing ‘OBM OTA outbox’ parameter values shall be deleted before copying in the contents of the more recent ‘OBM OTA queue’. In this case, the ‘OBM OTA outbox overwrite counter’ described in paragraph 1.12. shall be incremented by one.

• 8.5. OBM last transmission

• 8.5.1.The ‘OBM last transmission’ memory space shall store the ‘OBM OTA outbox’ data package corresponding to the most recent over-the-air transmission.

• 8.5.2.Following the successful transmission of the ‘OBM OTA outbox’, the OBM system shall copy the entire ‘OBM OTA outbox’ package to the ‘OBM last transmission’ memory space.

• 8.5.3.After verifying that the data package has been successfully stored in ‘OBM last transmission’ memory space, the OBM system shall clear the contents of the ‘OBM OTA outbox’.

• 8.6. OBM transmitted hash list

• 8.6.1.The ‘OBM transmitted hash list’ memory space shall store the ‘OBM transmission hash value’ parameter values from the 5 most recent transmitted ‘OBM OTA outbox’ data packages.

• 8.6.2.This memory space shall be managed on a rolling basis. When a new ‘OBM transmission hash value’ is added to the memory space, the oldest ‘OBM transmission hash value’ is deleted unless there are empty positions available.

• 8.6.3.Upon the successful transmission of the ‘OBM OTA outbox’, the OBM system shall save the ‘OBM transmission hash value’ in the ‘OBM transmitted hash list’.

• 8.6.4.By way of exemption from the reset conditions specified in the standards referred to in Part A, once the vehicle has entered into service, the content of the ‘OBM transmitted hash list’ shall be preserved as described in paragraph 6.9.

9. OBM data hashing

• 9.1.The OBM system shall apply the standard hash function described in paragraph 9.5. to compute the hash value of OBM trip data (according to paragraph 9.6.) and of the ‘OBM OTA outbox’ (according to paragraph 9.8.).

• 9.2.The OBM trip data hash value shall be used to select an OBM trip data package for later over-the-air transmission as defined in paragraph 9.7.

• 9.3.Hash values of ‘OBM OTA outbox’ data packages may be used to verify the integrity of the transmission of OBM data from vehicles to authorities.

• 9.4.Prior to hashing, OBM data must be structured according to the OBM data schemas provided in Appendix 7. For those data parameters defined within these OBM data schemas that are not applicable to the vehicle powertrain type, the OBM system shall fill each unused data byte with a default value of 0xFF.

• 9.5. OBM hash function

• 9.5.1.The OBM system shall implement a SHA-256 hashing process to support the hashing operations specified in this Annex. All hashing operations shall be carried out on-board the vehicle in compliance with internationally recognised cryptographic standards to ensure cryptographic robustness, data integrity, and resistance to unauthorised manipulation.

• 9.6. OBM trip data hashing

• 9.6.1.Following the calculation of OBM trip data parameters according to paragraph 7.2, the contents of the OBM trip data shall be hashed based on the OBM trip data schema layout specified in Appendix 7 for bytes 0 through to byte 58. The hash function shall be applied to OBM trip data on-board the vehicle only once. After calculation of the hash value for the OBM trip data, no modifications to the OBM trip data package shall be allowed. The ‘OBM trip hash validity status’ byte and ‘OBM trip hash value’ parameter shall not be included in the computation of the hash value.

• 9.6.2.All reserved data bytes shall be filled with zero values unless otherwise specified.

• 9.6.3.After calculation of the hash value for the OBM trip data, no modifications to the OBM trip data shall be allowed.

• 9.6.4.The resulting hash value shall be truncated, preserving the most significant 4 bytes.

• 9.6.5.Until the hash function computation is finalised, the ‘OBM trip hash value’ parameter shall store a placeholder value of 0xFFFFFFFF and, the ‘OBM trip hash validity status’ shall indicate the hash function computation is incomplete as defined in paragraph 2.9.3.

• 9.6.6.Once the hash computation is complete, the ‘OBM trip hash value’ shall be updated with the truncated hash value, and the ‘OBM trip hash validity status’ shall be set to indicate the computation of the ‘OBM trip hash value’ is complete. The completed OBM trip data together with the ‘OBM trip hash value’, in the layout specified in Appendix 7, shall be referred to as the OBM trip data package.

• 9.7. Criterion for OBM trip data selection for later over-the-air transmission (hash condition)

• 9.7.1.The criterion for OBM trip data package selection for later over-the-air transmission shall be based on the value of the least significant byte of the resulting, truncated ‘OBM trip hash value’. If this value is equal to either 00, 40, 80, or C0, the hash condition shall be considered as fulfilled.

• 9.7.2.Following the OBM trip data hashing according to paragraph 9.6, the OBM system shall determine whether the ‘OBM trip hash value’ satisfies the hash condition. If the condition is satisfied, the OBM trip data package is selected for OTA transmission.

• 9.8. OBM OTA outbox hashing

• 9.8.1.The contents of the ‘OBM OTA outbox’ shall be hashed based on the OBM OTA outbox data schema layout specified in Appendix 7 for bytes 0 through to byte [679]. The hash function shall be applied to the contents of the OBM OTA outbox on-board the vehicle only once. After calculation of the hash value for the OBM OTA outbox, no modifications to the OBM trip data package shall be allowed. The ‘OBM transmission hash validity status’ byte and ‘OBM transmission hash value’ parameter shall not be included in the computation of the hash value.

• 9.8.2.The resulting hash value shall not be truncated and shall be stored in its full length of 32 bytes.

• 9.8.3.Until the hash computation is finalised, the ‘OBM transmission hash value’ parameter shall store a placeholder value with each data byte set to a value of 0xFF and the ‘OBM trip hash validity status’ shall indicate the hash function computation is incomplete as defined in paragraph 4.4.

• 9.8.4.Once the hash computation is complete, the ‘OBM transmission hash value’ shall be updated with the calculated hash value, and the ‘OBM transmission hash validity status’ shall be set to indicate the computation of the ‘OBM transmission hash value’ is complete. The completed ‘OBM OTA outbox’ together with the ‘OBM transmission hash value’, in the layout specified in Appendix 7, shall be referred to as the ‘OBM OTA outbox’ data package.

PART C

Over-the-air transmission of OBM data

10. Over-the-air transmission of OBM data

• 10.1.When the ‘OBM OTA outbox’ hash computation is complete as defined in paragraph 9.8 the OBM system shall transmit the ‘OBM OTA outbox’ data package using OTA communication to the manufacturer’s server.

• 10.2.Data transmission may be delayed to such a time when suitable conditions are met to support data transmission. The vehicle may transmit the ‘OBM OTA outbox’ data package more than once to the manufacturer’s server to support successful transmission.

• 10.3.The ‘OBM OTA outbox’ data packages shall retain the structure and content of bytes 0 through [712] as defined in the ‘OBM OTA outbox’ data schema of Appendix 7 for anonymous transmission to the authority server and access through the OBD port.

• 10.4.Manufacturers shall clearly describe the ‘manufacturer-reserved’ OBM trip parameters, ‘manufacturer-reserved outbox’ parameters and definition of ‘OBM version number’, to the type-approval authority at time of type-approval. The same information shall be shared as part of the data communication process.

• 10.5.Prior to submission of OBM data to the authority server, the manufacturer shall append the family vehicle identifiers listed in table 10.1 to enable authorities to determine the vehicle type, variant, applicable family designations and supplementary information applicable to the vehicle type-approval.

Table 10.1

Vehicle family identifiers

Vehicle family identifier	Identifier
Vehicle type	CoC field 0.2.
Vehicle variant	CoC field 0.2.
Vehicle version	CoC field 0.2.
Whole-vehicle type-approval code	CoC field 0.11(b).
PEMS family	CoC field 0.2.3.3.
OBM family	Reserved
Battery durability family	Reserved
Date of manufacture	0.11.
Worst case energy consumption of part B family	Reserved
Part A family identifier	Reserved

• If any family identifier is not applicable to the vehicle type ‘NONE’ shall be stated.

Appendix 1

OBM parameters to support vehicle testing