Regulation (EU) 2018/858 of the European Parliament and of the Council of 30 May 2018 on the approval and market surveillance of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles, amending Regulations (EC) No 715/2007 and (EC) No 595/2009 and repealing Directive 2007/46/EC (Text with EEA relevance.)

• (2) Procedural requirements for storing information Vehicle manufacturers shall store the following information for each access granted to security-related repair and maintenance information:
• (a) the Vehicle Identification Number (VIN) of the vehicle for which the information was requested;
• (b) the date the request was made;
• (c) the vehicle registration number of the vehicle for which the information was requested, where available;
• (d) type variant of the vehicle for which the information was requested and the version of that vehicle, where available. Vehicle manufacturers shall store those data for 5 years.

Appendix 4

Conditions and procedure to access vehicle OBD information

• 1.Scope

• 1.1.This Appendix contains the conditions for access that the manufacturer shall only be allowed to set out and procedures that the vehicle manufacturer shall apply or shall only be allowed to require other parties to apply, while implementing the security measures for access to OBD information referred to in points 2.9.(a) and (b) of this Annex.

• 1.2.Any reference in this Appendix to independent operators or to manufacturer’s authorised partners, dealers and repairers, as well as to a vehicle manufacturer acting for repair and maintenance purposes in this Appendix shall include any person or operator acting on their behalf, such as a service provider performing remotely, as a service provided to the independent operator, the programming, fitting or activating of parts and equipment on a vehicle (remote service suppliers).

• 2.Obligations of the manufacturer

• 2.1.The vehicle manufacturer shall be responsible for ensuring that all technical prerequisites for the application of the procedures referred to in this Appendix are in place, including access credentials such as certificates or software tokens and necessary arrangements with diagnostic tool manufacturers.

• 2.2.The vehicle manufacturer shall demonstrate to the approval authority that the vehicle is designed to enable access to OBD information, in compliance with the requirements of this Appendix, using multi-brand diagnostic tools.

• 2.3.The vehicle manufacturer shall provide to the manufacturers of diagnostic tools the information referred to in point 11 of this Appendix.

• 2.4.The vehicle manufacturer shall ensure that its server used for the purpose of enabling access under point 2.9 of this Annex offers to independent operators, on a non-discriminatory basis, the same availability and performance of the information system as it offers to the vehicle manufacturer’s authorised partners, dealers and repairers or to the vehicle manufacturer using it for this purpose.

• Vehicle manufacturer shall ensure that any server used for the purpose of enabling access under point 2.9 of this Annex is accessible without interruption, except for exceptional and unforeseeable circumstances outside the vehicle manufacturer’s control and not attributable to negligence on its part, or as required for maintenance purposes of the information system. In case of maintenance, the period of unavailability shall not exceed the period of maintenance of any other server used by the manufacturer to enable access for the purposes referred to in point 2.9 of this Annex. The information of the planned maintenance shall be made available to the manufacturers of diagnostic tools sufficiently in advance.

• The vehicle manufacturer shall make yearly server availability statistics information available to the approval authority upon request. Cases of server unavailability shall be promptly reported by the vehicle manufacturer to the OBD Forum defined in point 12.

• 2.5.The vehicle manufacturer shall not restrict access to OBD information beyond the restrictions laid down in this Appendix unless specifically provided otherwise in this Regulation. Furthermore, the vehicle manufacturer shall not restrict access by independent operators to OBD information beyond the restrictions applicable to its authorised partners, dealers and repairers or to the vehicle manufacturer accessing the OBD information for repair and maintenance purposes.

• 2.6.The Vehicle manufacturer shall ensure that the cybersecurity measures they implement, including the compatibility requirements referred to in point 6.2, do not result in restricting or obstructing access to OBD information under this Appendix beyond what is necessary and proportionate to comply with Article 4.5(d) and Annex II line D4 of Regulation (EU) 2019/2144. Such measures may address future risks and threats where the vehicle manufacturer can demonstrate their impact and probability.

• 2.7.Any measures implemented by vehicle manufacturer to prevent emissions tampering and the odometer fraud shall not restrict or obstruct access to the OBD information beyond what is necessary and proportionate to comply with Articles 4(7) and 4(8) of Regulation (EU) 2024/1257 of the European Parliament and of the Council ([^E0055]).

• 3.Authentication

• 3.1.The vehicle manufacturer may, as a condition for issuing the access credentials, require authentication of the diagnostic tool manufacturer and the diagnostic tool used, except for the following repair and maintenance operations:

• (a) reading diagnostic trouble codes;

• (b) reading the vehicle VIN;

• (c) reading data and clearing diagnostic trouble codes where unrestricted access by means of a generic or OBD scan-tool is either required under Regulation (EU) 2017/1151 or Regulation (EU) 2024/1257; or provided for in UN Regulation No 49, UN Regulation No 83 ([^E0056]), UN Regulation No 168 ([^E0057]) or UN Regulation No 154.

• 3.2.Whenever access to OBD information involves changes to the vehicle, the vehicle manufacturer may, as a condition for issuing the access credentials, require authentication of the operator. In the case of devices used for monitoring purposes, where data is only read and autonomously reported to the diagnostic tool manufacturers server without any human interaction, the vehicle manufacturer shall not require authentication of the operator.

• 3.3.Where access to OBD information involves a change of the vehicle software or its configuration/its parameters consisting in reprogramming of the vehicle software code, resulting in alteration of the intended behaviour of the vehicle and persisting beyond the repair and maintenance operation, so that it can only be reversed or overwritten by the performance of an equivalent operation, the vehicle manufacturer may require authentication of the employee of the operator who is seeking to access OBD information, unless the manufacturer of the diagnostic tool attests to the vehicle manufacturer that, based on the result of an independent audit performed no earlier than 3 years before the request, the operator has a system in place allowing for unambiguous identification of the employee seeking such access.

• 3.4.Cases of access referred to in point 3.2 shall include such repair and maintenance operations as activation of actuators and functional test routines, clearing of diagnostic trouble codes, resetting of service lights, resetting of adaptive learning parameters, and replacement of parts including initialisation of non-smart component and reading data by identifier, except where it is used for the purposes of Periodic Technical Inspection with values comparable to the values defined in ISO20730-3, Annex B, provided that these values are available in the vehicle.

• 3.5.Cases of access referred to in point 3.2 shall include calibration, understood as a process of adjusting or aligning vehicle software and hardware parameters as prescribed by the vehicle manufacturer and without variant coding or modifying the vehicle software.

• 3.6.For the purposes of authentication referred to in points 3.1 to 3.3, the manufacturer of the tool used to access the OBD information may be required by the vehicle manufacturer to attest to the vehicle manufacturer the following:

• (a) the identity of the diagnostic tool;

• (b) where access to OBD information involves changes to the vehicle referred to in point 3.2, the identity of the diagnostic tool and pseudonymized identity of the operator and the compliance of the operator with the authorization requirements referred to in point 8.1;

• (c) where access to OBD information involves a change of the vehicle software or its configuration/its parameters consisting in reprogramming of the vehicle software code, resulting in alteration of the intended behaviour of the vehicle and persisting beyond the repair and maintenance operation, so that it can only be reversed or overwritten by the performance of an equivalent operation, as referred to point 3.3, the pseudonymised identity of the operator’s employee and the compliance of this employee with the authorisation requirements referred to in point 8.2.

• 3.7.In cases referred to in point 3.6, points (b) and (c), the identity of the operator and, where relevant, the employee of the operator and their compliance with the authorization requirements referred to in points 8.1 and 8.2 shall be verified by the manufacturer of the diagnostic tool used to access the OBD information or established based on an authorization certificate referred to in point 9.2.

• 3.8.No fees shall be required by the vehicle manufacturer for enabling access under point 2.9 of Annex X. However, vehicle manufacturer may charge justified and proportionate fees for the use of the remote facility referred to in point 2.9, point (c).

• 4.Connection requirements

• 4.1.Except for cases of access referred to point 3.1, points (a) to (c), the vehicle manufacturer may require one-time online connection from the diagnostic tool through diagnostic tool manufacturer’s server to vehicle manufacturer’s server to receive credentials. After the provision of access credentials, access shall not require online connection.

• 4.2.Whenever access to OBD information involves a change of the vehicle software or its configuration or its parameters resulting in alteration of the intended behaviour of the vehicle that persists beyond the repair and maintenance operation and that can only be reversed or overwritten by the performance of an equivalent operation, the vehicle manufacturer may require a continuous online connection at the time of performing the repair from the diagnostic tool to diagnostic tool manufacturer’s server as well as from the diagnostic tool manufacturer to the vehicle manufacturer server.

• 4.3.Cases of access referred to in point 4.2 shall include the following;

• (a) repair and maintenance operations as setting up a replacement component and customer preferences, identifying an Electronic Control Unit (ECU) and variant coding, initialising an ECU and a component, variant coding when replacing existing components, and variant coding when adding a new component;

• (b) repair and maintenance operations referred to in point 5.5.

• 4.4.Cases of access referred to in in point 4.2 shall not include repair and maintenance operations enumerated in points 3.4 and 3.5.

• 4.5.However, by way of derogation from the point 4.4., cases of access referred to in point 4.2 include repair and maintenance operations referred to in point 3.5 where it is necessary to validate calibration values which are subject to regulatory requirements or where calibration cannot be completed without individual component or separate technical unit specific data necessary to complete the repair process and retrieved from the manufacturer’s server as part of a variant coding process.

• 5.Traceability requirements

• 5.1.Except for cases of access referred to in points (a) to (c) of point 3.1, the vehicle manufacturer may require the diagnostic tool manufacturer to collect and store the vehicle VIN and the unique diagnostic tool identifier.

• 5.2.Whenever access to OBD information involves changes to the vehicle, the vehicle manufacturer may require the diagnostic tool manufacturer to collect and store information on all executed diagnostic jobs (e.g. service-ID and sub-function) and used parameters/attributes UTC date and time stamps for each interaction with the vehicle.

• 5.3.Cases of access referred to in point 5.2 shall include such repair and maintenance operations as those referred to in points 3.4, 3.5, 4.3 and 4.5.

• 5.4.Whenever access to OBD information involves a change of the vehicle software or its configuration/its parameters consisting in reprogramming of the vehicle software code, resulting in alteration of the intended behaviour of the vehicle and persisting beyond the repair and maintenance operation, so that it can only be reversed or overwritten by the performance of an equivalent operation, the vehicle manufacturer may require the diagnostic tool manufacturer to collect and provide the results of the vehicle network topology inspection, initial vehicle state upon connection, including hardware/software versions of all electronic control units installed in the vehicle, results of all module interaction and routines run (e.g. return parameters) and results of the post-repair final vehicle health check readout.

• 5.5.Cases of access referred to in point 5.4 shall include such repair and maintenance operations as pairing an original replacement part (including software and hardware compatible (as defined by the vehicle manufacturer) remanufactured or re-used part) or a vehicle manufacturer authorized replacement part to a vehicle by using an independent diagnostic tool and reprogramming a module by using original equipment vehicle software and original equipment programming software in accordance with the vehicle manufacturer’s instructions. It shall also include cases of decoupling or deregistering a part from a vehicle.

• 5.6.Cases of access referred to in in point 5.4 shall not include repair and maintenance operations enumerated in points 3.4, 3.5, 4.3 and 4.5.

• 6.Cybersecurity requirements applicable to diagnostic tool

• 6.1.Except for cases of access referred to in points (a) to (c) of point 3.1, the vehicle manufacturer may require that the diagnostic tool used to access the OBD information comply with the relevant requirements of Regulation (EU) 2024/2847 of the European Parliament and of the Council ([^E0058]) and that the diagnostic tool manufacturer comply with either Trusted Information Security Assessment Exchange (TISAX), to the level specified by the vehicle manufacturer in compliance with point 2.5, or ISO 27001.

• 6.2.Whenever access to OBD information involves changes to the vehicle referred to in point 3.2, the vehicle manufacturer may require that the diagnostic tool used to access the OBD information and the diagnostic tool manufacturer comply with the requirements of the vehicle manufacturer’s security implementation.

• 6.3.The requirements of the vehicle manufacturer’s security implementation shall not exceed the requirements imposed on vehicle manufacturer’s own diagnostic tool, tool suppliers and own organisation and shall be applied on a non-discriminatory basis.

• 6.4.The vehicle manufacturer may require the diagnostic tool manufacturer to perform tests to verify the compliance of the diagnostic tool with the specified requirements. A Service Level Agreement shall ensure that any verification of the results of these tests performed by the vehicle manufacturer is done in a timely manner. In case a diagnostic tool manufacturer’s compliance with the requirements of this section is not confirmed, a clear statement of the reasons for non-compliance shall be provided by the vehicle manufacturer, together with the required measures to be implemented by the diagnostic tool manufacturer.

• 6.5.Cases of access referred to in point 6.2 shall include such repair and maintenance operations as those referred to in points 3.4 and 3.5.

• 6.6.Whenever access to OBD information involves change of the vehicle software or its configuration/its parameters resulting in alteration of the intended behaviour of the vehicle persisting beyond the repair and maintenance operation, so that it can only be reversed or overwritten by the performance of an equivalent operation, the vehicle manufacturer may require that the diagnostic tool used to access the OBD information and the diagnostic tool manufacturer comply with the relevant requirements of the vehicle manufacturer’s Software Updates Management System (as defined in UN Regulation No 156 ([^E0059]) implementation. Those requirements shall not exceed the requirements imposed on the vehicle manufacturer’s own diagnostic tool, tool suppliers and own organisation and shall be applied on a non-discriminatory basis.

• 6.7.Cases of access referred to in point 6.6 shall include such repair and maintenance operations as those referred to in points 4.3, 4.5 and 5.5 and shall not include those referred to in points 3.4 and 3.5.

• 7.Access credentials

• 7.1.Where all the conditions referred to in sections 3, 4 and 6 are complied with, the vehicle manufacturer shall, without delay, provide the diagnostic tool manufacturer with access credentials sufficient to enable the access to the required OBD information.

• 7.2.Access credentials may be VIN-specific.

• 7.3.Access credentials shall be valid for at least 30 days from the time of provision.

• 7.4.However, whenever access to OBD information involves a change to the vehicle, the vehicle manufacturer may limit the validity of access credentials to 24 hours.

• 7.5.Cases of access referred to in point 7.4 shall include such repair and maintenance operations as those referred to in points 3.4, 3.5, 4.3, 4.5 and 5.5.

• 8.Authorisation criteria and authorization certificates

• 8.1.In cases referred to in point 3.2, the vehicle manufacturer may refuse to issue access credentials if the manufacturer of the diagnostic tool used to access the OBD information does not attest that the operator seeking access to OBD information:

• (a) has a valid liability insurance with a minimum amount of coverage of EUR 1 million for bodily injury and EUR 0,5 million for property damage;

• (b) pursues a legitimate business activity in the automotive sector as referred to in point 6.3 of this Annex.

• No other conditions for issuing access credentials shall be imposed by the vehicle manufacturer than those specified in points(a) and (b).

• 8.2.In cases referred to in point 5.4, where the vehicle manufacturer requires the authentication of the employee of the operator and unless the manufacturer of the diagnostic tool attests to the vehicle manufacturer, in compliance with the conditions set out in point 3.3, that the operator has a system in place allowing for unambiguous identification of the employee seeking such access, the vehicle manufacturer may refuse to issue access credentials if the manufacturer of the diagnostic tool used to access the OBD information does not attest, in addition to the conditions referred to in point 8.1, that the employee seeking access to OBD information holds an employment agreement with the operator seeking access to OBD information and that the employee concerned has a valid country specific identity card or an equivalent document.

• 8.3.To be eligible for the authentication procedure under this Appendix, the diagnostic tool manufacturer shall have committed in the general conditions of contracts with operators to accept on request by the independent operator, for the purpose of attesting the compliance with the requirements referred to in points 8.1 and 8.2, a certificate referred to in point 9.2 of this Appendix and issued not earlier than 60 months before the request for access. However, where the operator does not request to be authenticated based on such a certificate, the diagnostic tool manufacturer may, for the purpose of authentication, choose to verify the identity of the operator or the operator’s employee and the compliance with the authorization criteria by its own processes.

• 9.Conformity Assessment Body and Trust Centre

• 9.1.Certificates referred to in points 3.7 and 8.3 shall be issued by a Trust Centre referred to in point 2.1.6 of Appendix 3 based on the findings of a conformity assessment body as referred to in point 4.2.2 of Appendix 3 with regard to the circumstances referred to in point 9.2.

• 9.2.For the purpose of issuing the authorization certificates by a Trust Centre, the Conformity Assessment Body shall:

• (a) comply with the requirements referred to under points (a), (b), (d), (e), (f), (g), (h), (i), (k), (l), (n), and (p) of point 4.3.1 of Appendix 3 of Annex X;

• (b) inspect and confirm the circumstances referred to under (d) and (g) of point 4.3.3 of Appendix 3 of Annex X. In cases referred to in point 5.4, where the vehicle manufacturer requires the authentication of the employee of the operator, the inspection and confirmation of those circumstances shall refer to the employee of the operator.

• 9.3.For the purpose of issuing authorisation certificates in cases referred to in point 9.1, Trust Centre shall:

• (a) comply with the requirements of point 4.6 of Appendix 3;

• (b) provide all required information to the diagnostic tool manufacturer to implement the certificates into their diagnostic tools.

• 10.Vehicle manufacturer’s access to information concerning the operator

• 10.1.The vehicle manufacturer shall obtain, on request, from the manufacturer of the diagnostic tool access to the information regarding an individual repair or maintenance operation recorded in accordance with section 5 only where this is necessary in relation to repair or maintenance work carried out on an individual vehicle to:

• (a) react to a reasonable suspicion of serious misuse of access to the vehicle;

• (b) carry out investigations in case of product liability or warranty claims;

• (c) investigate cybersecurity or illegal tampering incidents, answer queries of the vehicle owner or a public authority.

• In cases referred to in points (b) and (c), this information shall include, where applicable, the information regarding the operator and/or its employees. In cases where the manufacturer of the diagnostic tool relied for the authentication on a certificate provided by the Trust Centre, the relevant CAB shall provide the required information based on its assessment of a documented request by the vehicle manufacturer.

• The vehicle manufacturer shall ensure that the information regarding an individual repair or maintenance operation accessed for the purposes referred to in points (a) to (c) shall not be used for any other purpose.

• 10.2.In cases referred to in point 10.1, the manufacturer of the diagnostic tool shall inform, without delay, the independent operator and, where relevant, the employee of the independent operator, about the access to the information regarding an individual repair or maintenance operation or to the information concerning the operator and/or its employees.

• 10.3.In cases referred to in points (a) and (c) of point 10.1 and where this is necessary and proportionate to prevent further misuse or address cybersecurity risk, the vehicle manufacturer may temporarily suspend or restrict access of the diagnostic tool concerned or request the involved manufacturer of the diagnostic tool to take immediate measures to temporarily restrict the access of the concerned operator, diagnostic tool, or employee to the OBD information concerning the vehicles of this manufacturer.

• 10.4.In exceptional cases, in response to a significant present or imminent cybersecurity incident a Vehicle Manufacturer may suspend access to the OBD information, at the most granular level possible, where it is necessary and proportionate to respond to the incident concerned.

• 10.5.In cases referred to in points 10.3 and 10.4, the vehicle manufacturer shall, at the same time, notify the suspension to the Approval Authority, together with the reasons for the suspension and all relevant evidence. The suspension shall be lifted when the incident is settled or if the Approval Authority requests the vehicle manufacturer to do so.

• The Approval Authority shall, within 10 days from the day of the notification, review the grounds for suspension and, if the suspension is manifestly unjustified or disproportionate, request the vehicle manufacturer or the involved manufacturer of the diagnostic tool to restore access.

• The Approval Authority may, at any time, request the vehicle manufacturer and the involved manufacturer of the diagnostic tool to restore access where it considers that the grounds for suspension ceased to exist.

• 11.Information to be provided to diagnostic tool manufacturers

• 11.1.The vehicle manufacturer’s RMI system shall display contact data and process-related information on how to obtain the requested information, as specified in points (a), (b), (c) and (d), concerning integration of diagnostic tool, at the time of the type-approval:

• (a) contact information for technical and commercial enquiries;

• (b) description of the integration process including indicative timeline;

• (c) general terms and conditions for integration of diagnostic tools by the diagnostic tool manufacturer;

• (d) schedule of fees for integration related services.

• 11.2.Subject to the conclusion of a non-disclosure agreement, the vehicle manufacturer shall make available, on request, the following information to any independent operator complying with TISAX, to the level specified by the vehicle manufacturer in compliance with point 2.5, or ISO 27001:

• (a) for reference, a model agreement on security integration, clearly indicating the terms intended to be included in all the vehicle manufacturer’s agreements with diagnostic tool manufacturers on this matter,

• (b) description of the requirements and processes for secure integration of the diagnostic tool including the indicative timeline.

• 11.3.The vehicle manufacturer shall provide the following information and make available the following services to the manufacturer of diagnostic tool, at the time of the conclusion of an agreement on the integration of diagnostic tool:

• (a) detailed and timely updated requirements, processes and technical specifications for secure integration of the diagnostic tool, including the security implementation requirements;

• (b) against reasonable remuneration, as referred to in point 2.3, instant response technical support for security integration and diagnostic tool verification.

• 11.4.The security implementation requirements referred to in point 11.3 shall be accompanied by the explanation of the reasons for this requirement. In exceptional cases the vehicle manufacturer may provide only the necessary requirements without detailed explanations where:

• (a) disclosing the specific objectives behind a requirement could compromise proprietary information or trade-secrets, or

• (b) the disclosure of the reasoning would reveal a broader cybersecurity strategy that must remain confidential to maintain the integrity of the system.

• 11.5.The information referred to in points 11.1 to 11.3 shall be provided together with the application for a type approval.

• 12.OBD Forum

• 12.1.The Forum on Access to Vehicle Information (OBD-Forum) shall be in charge for coordinating and monitoring the implementation of the procedures for:

• (a) authentication and authorisation of independent operators as described in point 3 and 8 of this Appendix, including the processes used by the manufacturers of diagnostic tools for verification of authorisation criteria, as described in point 3 of this Appendix;

• (b) issuing access credentials as described in point 7 of this Appendix including the fulfilment of traceability and connectivity requirements;

• (c) disclosing the information on access and suspension or restriction of access as described in point 10 of this Appendix.

• 12.2.The Forum shall:

• (a) advise the Commission on implementation of this Appendix;

• (b) advise the approval authorities on disputes concerning the interpretation and implementation of this Appendix;

• (c) advise the vehicle manufacturers, diagnostic tools manufacturers and independent operators on:
• (i) interpretation of the Appendix;
• (ii) practical aspects of the procedures referred to in points 12.1;
• (iii) guidance on resolving disputes concerning the implementation of the procedures referred to in point 12.1.

• 12.3.The members of the OBD-Forum shall be represented by vehicle manufacturers and independent operators engaged in the implementation and use of procedures and processes described in paragraph 12.1.

• 12.4.The OBD Forum shall operate under the common legal and organizational structure as the ‘Forum for Access to Security-Related Vehicle RMI. referred to in paragraph 2.1.12 of Appendix 3.

ANNEX XI

CORRELATION TABLE

1. Regulation (EC) No 715/2007

2. Regulation (EC) No 595/2009

3. Directive 2007/46/EC

[^E0001]: Regulation (EU) No 167/2013 of the European Parliament and of the Council of 5 February 2013 on the approval and market surveillance of agricultural or forestry vehicles (OJ L 60, 2.3.2013, p. 1).

[^E0002]: Regulation (EU) No 168/2013 of the European Parliament and of the Council of 15 January 2013 on the approval and market surveillance of two- or three-wheel vehicles and quadricycles (OJ L 60, 2.3.2013, p. 52).

[^E0003]: Directive 2006/42/EC of the European Parliament and of the Council of 17 May 2006 on machinery, and amending Directive 95/16/EC (OJ L 157, 9.6.2006, p. 24).

[^E0004]: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act) (OJ L, 2024/1689, 12.7.2024, ELI: http://data.europa.eu/eli/reg/2024/1689/oj).

[^E0005]: Council Directive 96/53/EC of 25 July 1996 laying down for certain road vehicles circulating within the Community the maximum authorized dimensions in national and international traffic and the maximum authorized weights in international traffic (OJ L 235, 17.9.1996, p. 59).

[^E0006]: Directive 2001/95/EC of the European Parliament and of the Council of 3 December 2001 on general product safety (OJ L 11, 15.1.2002, p. 4).

[^E0007]: Commission Regulation (EU) 19/2011 of 11 January 2011 concerning type-approval requirements for the manufacturer's statutory plate and for the vehicle identification number of motor vehicles and their trailers and implementing Regulation (EC) No 661/2009 of the European Parliament and of the Council concerning type-approval requirements for the general safety of motor vehicles, their trailers and systems, components and separate technical units intended therefor (OJ L 8, 12.1.2011, p. 1).

[^E0008]: Commission Regulation (EC) No 692/2008 of 18 July 2008 implementing and amending Regulation (EC) No 715/2007 of the European Parliament and of the Council on type-approval of motor vehicles with respect to emissions from light passenger and commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and maintenance information (OJ L 199, 28.7.2008, p. 1).

[^E0009]: Council Directive 80/181/EEC of 20 December 1979 on the approximation of the laws of the Member States relating to units of measurement and on the repeal of Directive 71/354/EEC (OJ L 39, 15.2.1980, p. 40).

[^E0010]: Commission Regulation (EU) 2017/1151 of 1 June 2017 supplementing Regulation (EC) No 715/2007 of the European Parliament and of the Council on type-approval of motor vehicles with respect to emissions from light passenger and commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and maintenance information, amending Directive 2007/46/EC of the European Parliament and of the Council, Commission Regulation (EC) No 692/2008 and Commission Regulation (EU) No 1230/2012 and repealing Commission Regulation (EC) No 692/2008 (OJ L 175, 7.7.2017, p. 1).

[^E0011]: Regulation (EU) No 510/2011 of the European Parliament and of the Council of 11 May 2011 setting emission performance standards for new light commercial vehicles as part of the Union's integrated approach to reduce CO2 emissions from light-duty vehicles (OJ L 145, 31.5.2011, p. 1).

[^E0012]: Commission Regulation (EU) No 1230/2012 of 12 December 2012 implementing Regulation (EC) No 661/2009 of the European Parliament and of the Council with regard to type-approval requirements for masses and dimensions of motor vehicles and their trailers and amending Directive 2007/46/EC of the European Parliament and of the Council (OJ L 353, 21.12.2012, p. 31).

[^E0019]: In the absence of a registration document, the competent authority may refer to available documented evidence of date of manufacture or documented evidence of first purchase.

[^E0022]: OJ L 135, 31.5.2018, p. 1.

[^E0023]: OJ L 346, 17.12.1997, p. 78.

[^E0024]: For subsequent amendments, see UNECE TRANS/WP.29/343.

[^E0048]: Regulation No 154 of the Economic Commission for Europe of the United Nations (UN/ECE) – Uniform provisions concerning the approval of light duty passenger and commercial vehicles with regards to criteria emissions, emissions of carbon dioxide and fuel consumption and/or the measurement of electric energy consumption and electric range (WLTP) [2021/2039] (OJ L 423, 26.11.2021, p. 1, ELI: http://data.europa.eu/eli/reg/2021/2039/oj).

[^E0049]: Regulation No 49 of the Economic Commission for Europe of the United Nations (UN/ECE) – Uniform provisions concerning the measures to be taken against the emission of gaseous and particulate pollutants from compression-ignition engines and positive ignition engines for use in vehicles [2023/64] (OJ L 14, 16.1.2023, p. 1, ELI: http://data.europa.eu/eli/reg/2023/64/oj).

[^E0050]: As defined in Article 2 of Commission Implementing Regulation (EU) 2023/138 of 21 December 2022 laying down a list of specific high-value datasets and the arrangements for their publication and re-use (OJ L 19, 20.1.2023, p. 43, ELI: http://data.europa.eu/eli/reg_impl/2023/138/oj).

[^E0051]: As defined in Article 3(10) of Regulation (EC) No 715/2007.

[^E0052]: As defined in Article 3(8) of Regulation (EC) No 595/2009.

[^E0053]: The requirements set out in this Appendix are based on those laid down in the ‘Scheme for accreditation, approval and authorization to Access Security-related Repair and Maintenance Information (RMI)’ validated on 19 May 2016 by the European cooperation for Accreditation (https://www.vehiclesermi.eu/).

[^E0054]: Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC (OJ L 257, 28.8.2014, p. 73).

[^E0055]: Regulation (EU) 2024/1257 of the European Parliament and of the Council of 24 April 2024 on type-approval of motor vehicles and engines and of systems, components and separate technical units intended for such vehicles, with respect to their emissions and battery durability (Euro 7), amending Regulation (EU) 2018/858 of the European Parliament and of the Council and repealing Regulations (EC) No 715/2007 and (EC) No 595/2009 of the European Parliament and of the Council, Commission Regulation (EU) No 582/2011, Commission Regulation (EU) 2017/1151, Commission Regulation (EU) 2017/2400 and Commission Implementing Regulation (EU) 2022/1362 (OJ L, 2024/1257, 8.5.2024, ELI: http://data.europa.eu/eli/reg/2024/1257/oj).

[^E0056]: Regulation No 83 of the Economic Commission for Europe of the United Nations (UN/ECE) – Uniform provisions concerning the approval of vehicles with regard to the emission of pollutants according to engine fuel requirements (OJ L 42, 15.2.2012, p. 1, ELI: http://data.europa.eu/eli/reg/2012/83/oj).

[^E0057]: Regulation No 168 of the Economic Commission for Europe of the United Nations (UN/ECE) – Uniform provisions concerning the approval of light duty passenger and commercial vehicles with regards to real driving emissions (RDE) [2024/211] (OJ L, 2024/211, 12.1.2024, ELI: http://data.europa.eu/eli/reg/2024/211/oj).

[^E0058]: Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements and amending Regulations (EU) No 168/2013 and (EU) 2019/1020 and Directive (EU) 2020/1828 (Cyber Resilience Act) (OJ L, 2024/2847, 20.11.2024, ELI: http://data.europa.eu/eli/reg/2024/2847/oj).

[^E0059]: Regulation No 156 of the Economic Commission for Europe of the United Nations (UN/ECE) – Uniform provisions concerning the approval of vehicles with regards to software update and software updates management system [2021/388] (OJ L 82, 9.3.2021, p. 60, ELI: http://data.europa.eu/eli/reg/2021/388/oj).