The Road Vehicles (Type-Approval) (Amendment) (No. 3) Regulations 2025
Write the words of this act the way you think they should read. Solon shows your change as a redline against the published text and pins it to that exact text, so it can never be applied to wording you did not see.
Change 1
3 Amendment of Regulation (EU) 2020/683
(1) Commission Implementing Regulation (EU) 2020/683 is amended as follows. (2) In Article 8— (a) the existing text becomes sub-paragraph “1.”; (b) after that sub-paragraph, insert— 2 A certificate of conformity which is issued using the template provided for in Annex VIII as it has effect immediately before the coming into force of these Regulations, is to be treated as a GB certificate of conformity issued in accordance with Article 36(1) of Regulation (EU) 2018/858, if— (a) the vehicle to which it applies was manufactured before 1 June 2027; and (b) a valid GB type-approval granted in accordance with Regulation (EU) 2018/858 applies to the vehicle. . (3) In Annex I, in the template for an information document for the GB type-approval of vehicles, systems, components or separate technical units, after point 12.10.3.2, insert—— 12.11. [Intentionally blank] 12.12. [Intentionally blank] 12.13. [Intentionally blank] 12.14. Cyber security 12.14.1. General construction characteristics of the vehicle type, including: (a) the vehicle systems which are relevant to the cyber security of the vehicle type; (b) the components of those systems that are relevant to cyber security; (c) the interactions of those systems with other systems within the vehicle type and external interfaces ... 12.14.2. Schematic representation of the vehicle type: ... 12.14.3. The number of the Certificate of Compliance for cyber security management system: ... 12.14.4. Documents for the vehicle type to be approved describing the outcome of its risk assessment and the identified risks: ... 12.14.5. Documents for the vehicle type to be approved describing the mitigations that have been implemented on the systems listed, or to the vehicle type, and how they address the stated risks: ... 12.14.6. Documents for the vehicle type to be approved describing the protection of dedicated environments for aftermarket software, services, applications or data: ... 12.14.7. Documents for the vehicle type to be approved describing what tests have been used to verify the cyber security of the vehicle type and its systems and the outcome of those tests: ... 12.14.8. Description of the consideration of the supply chain with respect to cyber security: ... 12.15. Software update 12.15.1. General construction characteristics of the vehicle type: ... 12.15.2. The number of the Certificate of Compliance for software update management: ... 12.15.3. Security measures 12.15.3.1. Documents for the vehicle type to be approved describing that the update process will be performed securely: ... 12.15.3.2. Documents for the vehicle type to be approved describing that the update process will be performed securely: ... 12.15.4. Software updates over the air 12.15.4.1. Documents for the vehicle type to be approved describing that the update process will be performed safely: ... 12.15.4.2. Description of the means of informing vehicle users about an update before and after its execution: ... 12.15.5. Manufacturer’s declaration of compliance with the requirements for Software Update Management Systems . (4) In Annex VIII (certificate of conformity in paper format), in the Appendix (templates for the certificate of conformity in paper format)— (a) in Part I (complete and completed vehicles)— (i) in vehicle categories M1, M2, M3, N1, N2, and N3, in each case, after point 52, insert— 55. Vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. Vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (ii) in vehicle categories O1 and O2, and O3 and O4, in each case, after point 52, insert— 55. In the case of a vehicle approved to UN Regulation No 155, vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. In the case of a vehicle approved to UN Regulation No 156, vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (b) in Part 2 (incomplete vehicles)— (i) in vehicle categories M1, M2, M3, N1, N2, N3, in each case, after point 52, insert— 55. Vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. Vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (ii) in vehicle categories O1 and O2, and O3 and O4, in each case, after point 52, insert— 55. In the case of a vehicle approved to UN Regulation No 155, vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. In the case of a vehicle approved to UN Regulation No 156, vehicle certified in accordance with UN Regulation No 156: yes/no (4) .
3 Amendment of Regulation (EU) 2020/683
(1) Commission Implementing Regulation (EU) 2020/683 is amended as follows. (2) In Article 8— (a) the existing text becomes sub-paragraph “1.”; (b) after that sub-paragraph, insert— 2 A certificate of conformity which is issued using the template provided for in Annex VIII as it has effect immediately before the coming into force of these Regulations, is to be treated as a GB certificate of conformity issued in accordance with Article 36(1) of Regulation (EU) 2018/858, if— (a) the vehicle to which it applies was manufactured before 1 June 2027; and (b) a valid GB type-approval granted in accordance with Regulation (EU) 2018/858 applies to the vehicle. . (3) In Annex I, in the template for an information document for the GB type-approval of vehicles, systems, components or separate technical units, after point 12.10.3.2, insert—— 12.11. [Intentionally blank] 12.12. [Intentionally blank] 12.13. [Intentionally blank] 12.14. Cyber security 12.14.1. General construction characteristics of the vehicle type, including: (a) the vehicle systems which are relevant to the cyber security of the vehicle type; (b) the components of those systems that are relevant to cyber security; (c) the interactions of those systems with other systems within the vehicle type and external interfaces ... 12.14.2. Schematic representation of the vehicle type: ... 12.14.3. The number of the Certificate of Compliance for cyber security management system: ... 12.14.4. Documents for the vehicle type to be approved describing the outcome of its risk assessment and the identified risks: ... 12.14.5. Documents for the vehicle type to be approved describing the mitigations that have been implemented on the systems listed, or to the vehicle type, and how they address the stated risks: ... 12.14.6. Documents for the vehicle type to be approved describing the protection of dedicated environments for aftermarket software, services, applications or data: ... 12.14.7. Documents for the vehicle type to be approved describing what tests have been used to verify the cyber security of the vehicle type and its systems and the outcome of those tests: ... 12.14.8. Description of the consideration of the supply chain with respect to cyber security: ... 12.15. Software update 12.15.1. General construction characteristics of the vehicle type: ... 12.15.2. The number of the Certificate of Compliance for software update management: ... 12.15.3. Security measures 12.15.3.1. Documents for the vehicle type to be approved describing that the update process will be performed securely: ... 12.15.3.2. Documents for the vehicle type to be approved describing that the update process will be performed securely: ... 12.15.4. Software updates over the air 12.15.4.1. Documents for the vehicle type to be approved describing that the update process will be performed safely: ... 12.15.4.2. Description of the means of informing vehicle users about an update before and after its execution: ... 12.15.5. Manufacturer’s declaration of compliance with the requirements for Software Update Management Systems . (4) In Annex VIII (certificate of conformity in paper format), in the Appendix (templates for the certificate of conformity in paper format)— (a) in Part I (complete and completed vehicles)— (i) in vehicle categories M1, M2, M3, N1, N2, and N3, in each case, after point 52, insert— 55. Vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. Vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (ii) in vehicle categories O1 and O2, and O3 and O4, in each case, after point 52, insert— 55. In the case of a vehicle approved to UN Regulation No 155, vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. In the case of a vehicle approved to UN Regulation No 156, vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (b) in Part 2 (incomplete vehicles)— (i) in vehicle categories M1, M2, M3, N1, N2, N3, in each case, after point 52, insert— 55. Vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. Vehicle certified in accordance with UN Regulation No 156: yes/no (4) ; (ii) in vehicle categories O1 and O2, and O3 and O4, in each case, after point 52, insert— 55. In the case of a vehicle approved to UN Regulation No 155, vehicle certified in accordance with UN Regulation No 155: yes/no (4) 56. In the case of a vehicle approved to UN Regulation No 156, vehicle certified in accordance with UN Regulation No 156: yes/no (4) .
One line that says what changes, such as "Halve the dog tax".
Who it helps, what it costs, what it fixes. It is what persuades people to support it.
A proposal here is not law. Support on Solon is evidence that people want the change; the official route says what it takes to make it law.
Sign in to file your proposal. What you have written stays on this page.
Sign in to file itThink it through
Ask what your change would do, who would gain and who would bear a cost, and where something like it is already law. The assistant reads your draft as it stands, cites the law and the studies it finds, and takes no side. What you file stays yours.