Document presents candidate amendments for ADS Regulation Phase 2 addressing Safety Management System and in-service monitoring and reporting. Proposes:

• An emergency recovery plan for fleet-level failures,
• Harmonization of SMS audit provisions and certificate mutual recognition,
• Split of operational and design responsibilities between operators and manufacturers,
• Refinement of occurrence classes with objective measurable criteria,
• Delta-V thresholds for all vehicle categories in scope,
• Extended reporting templates,
• Leading safety performance indicators,
• Confidentiality rules for ISMR data sharing,
• Explicit feedback loops from findings to corrective action and approval review.

Proposal for a new UN Regulation establishing uniform provisions for type approval of Electric Powertrain Retrofit Systems (EPRS) designed for conversion of vehicles of categories M and N to full electric propulsion. The regulation does not apply to vehicles holding approval under UN R155 or UN R156. It sets out requirements for EPRS manufacturers, installers, markings, approval procedures, general and specific technical requirements for retrofit systems, installer authorization and training, documentation to be provided by manufacturers, conformity of production, modification and extension of approvals, and penalties for non-conformity.

Minutes of the eleventh meeting of the IWG on EV/HFCV Retrofit Systems held on 9 September 2026. The group adopted the provisional agenda and reviewed the draft UN Regulation on EV/HFCV retrofit systems. Key discussions addressed the regulatory concept for approval of the Electric Powertrain Retrofit System combined with installation requirements and vehicle testing, vehicle scope including possible exclusion of older vehicles and those subject to UN Regulations Nos. 155 and 156, and confirmation that HFCV provisions would remain as placeholders for later development. The updated working document will be circulated before submission to GRPE in October 2026.

GRVA will continue to establish and maintain the United Nations regulatory framework for Automated Driving Systems, including UN R185 and GTR 26. GRVA will continue its work on cyber security, over-the-air software updates, and the Data Storage System for Automated Driving. GRVA will focus on implementation of ADS and development of provisions for the Exchange of Scenario-Relevant Information. GRVA will further elaborate requirements for Advanced Driver Assistance Systems, building on UN R79 and UN R171, and for Automated Emergency Braking Systems, building on UN R131 and UN R152.

Proposal to amend para. 5.1.3., insert new paras. 5.1.5. and 5.1.5.1. requiring the Approval Authority to refuse type approval unless the Certificate of Compliance for the Cyber Security Management System is issued by the same Approval Authority granting vehicle type approval, while permitting referencing of certificates from other Approval Authorities under specific conditions with documented agreements and clarified responsibilities, and insert new paras. 5.4. and 5.4.1. with equivalent requirements for the Software Update Management System Certificate of Compliance.

Document outlining GRVA’s priority activities for 2027 based on ECE/TRANS/WP.29/2026/1. GRVA will continue establishing and maintaining the United Nations regulatory framework for Automated Driving Systems, including UN R185 and GTR 26, with work on cyber security, over-the-air software updates, and the Data Storage System for Automated Driving. GRVA will focus on ADS implementation, provisions for Exchange of Scenario-Relevant Information, and elaboration of requirements for Advanced Driver Assistance Systems and Automated Emergency Braking Systems building on UN R79, 171, 131, and 152.

Proposal to amend Article 2, paragraph 2 to clarify that where a Certificate of Compliance required under a UN Regulation and issued by an Approval Authority of another Contracting Party is accepted by a Contracting Party, the Approval Authority granting the corresponding type approval shall remain responsible for all aspects of that type approval. The amendment addresses management systems and their Certificates of Compliance used in UN Regulations such as UN R155 and UN R156.

Proposal to renew the terms for the Informal Working Group on Cyber Security and Software Updates under GRVA. The IWG shall maintain official documents on cyber security and software updates, develop amendments to UN R155 and UN R156 including provisions on software identification, support application across Global Technical Regulations, and provide opportunities for participants to share implementation experience. The IWG will be chaired by the United Kingdom, United States, and Japan, with OICA providing technical secretariat, and will operate until November 2029.

Status report on activities of the IWG on CS/OTA since the 25th GRVA session. The IWG reviewed proposals for amendment of UN R155 and its interpretation document for multi-stage vehicles, proposals for approval-authority arrangements and Certificates of Compliance for UN R155 and R156, proposals integrating software identification and update text across several UNRs outlined in RE.3, component and STU approval concepts, and remote operation and automated driving systems. The IWG proposes updating regulatory text and interpretation documents for UN R155, revisions to software identification and update text across several regulations, and revised Terms of Reference for a mandate till November 2029.

Proposal to insert definitions for Software Identification Number, insert requirements for manufacturers to provide necessary information allowing the Technical Service to uniquely identify hardware and software configurations, insert provisions allowing vehicle manufacturers to apply for new approvals to differentiate software versions for registered versus new vehicles, amend production discontinuation provisions to clarify that cessation is not deemed definitive if the manufacturer intends to obtain subsequent extensions for software updates of vehicles already registered in the market, renumber and insert new items in approval communication annexes regarding software identification and software updates including RxSWIN, and insert provisions allowing vehicle manufacturers to obtain new approvals for software version differentiation across multiple UN Regulations (13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178).

The UN IWG on Cyber Security and OTA issues held its 39th session on 3 September 2026. The provisional agenda (TFCS-38-01/Rev.3) and minutes from the 38th session (TFCS-38-13) were adopted. Regarding R155 amendments: multistage vehicle proposals (GRVA/2026/28, GRVA/2026/29, TFCS-39-08) will be submitted as informal documents with a merged paragraph; component approval proposals (TFCS-39-04) had STU references removed and discussion continues; remote operation for ADS proposals were not discussed but participants are invited to consider a general refresh of Annex 5. RXWIN application proposals (TFCS-39-05, TFCS-39-06, TFCS-39-07, TFCS-39-08, TFCS-39-09, TFCS-39-10, TFCS-39-11, TFCS-39-12) were presented; items 1, 4, and 6 were agreed, item 5 was agreed in principle, and items 2 and 3 regarding R155 and R157 applicability require revised wording. Netherlands expressed concerns about vehicle discontinuation and multiple type approvals. Administrative provisions regarding Type Approval Authority for CSMS/SUMS (GRVA/2026/30, TFCS-39-02, TFCS-39-07) were discussed without consensus. Out-of-scope vehicle approvals (TFCS-38-03) discussion was deferred to a separate workshop. Two informal documents will be provided to GRVA.

Japan submitted comments on RXSWIN assignment at the 38th CS/OTA IWG. Q.1 asks whether, when a type approval is extended from UN R156-00 to UN R156-01, RXSWIN may be assigned at extension time, and if a UN Regulation refers to RE.3 Annex 7 through a supplementary amendment after UN R156-01 transitional provisions become applicable, whether RXSWIN is assigned at that time. Q.2 asks whether Approval Authorities other than the Authority granting approval are expected to have access to the OEM’s Auditable Register, as access information appears provided only to the Approval Authority concerned through paragraph 9.5.2. Q.3 asks whether software updates affecting type approval can be performed under Regulations that do not reference RE.3 Annex 7.

Proposal to amend para. 7.2.1.2.2. to delete, in cases where RXSWINs are not held on the vehicle, the requirement that the manufacturer shall declare the software version(s) of the vehicle or single ECUs with the connection to the relevant type approvals to the Approval Authority and that this declaration shall be updated each time the declared software version(s) is updated, and add that the link between the software version(s) and the RXSWINs shall be declared.

OICA, CLEPA, and CLCCR oppose the requirement in GRVA/2026/30 for a single Approval Authority to issue the Certificate of Compliance for CSMS/SUMS and vehicle type approval. They contend the approach would create multiple approvals of the same Management System, imposing administrative burden and creating unresolved legal consequences if a CoC is challenged. The organizations propose adding a new paragraph 5.1.5. instead of paragraph 5.1.3. e) to permit mutual agreement between Approval Authorities, allowing usage of a CoC issued by another Approval Authority, with such agreement documented in type approval documentation.

Proposal to amend GRVA/2026/27, which proposes amendments to UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R139, UN R140, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178:

• Throughout these regulations, amend references to the Consolidated Resolution on the Construction of Vehicles (R.E.3) as document ECE/TRANS/WP.29/78/Rev.8,
• insert new definitions for Software Identification Numbers referring to R.E.3 Annex 7 para. 2,
• amend requirements for software identification to require manufacturers provide necessary information allowing Technical Services to uniquely identify hardware and software configurations,
• insert new provisions allowing vehicle manufacturers to apply for new approvals differentiating software versions for vehicles already registered in the market from new vehicles,
• amend production discontinuation provisions to clarify production is not considered definitively discontinued if manufacturer intends to obtain subsequent extensions of approval for software updates of registered vehicles,
• insert new items in annexes regarding additional information on software identification and software updates including R_xSWIN identification, whether held on vehicle, how to read if not held on vehicle, and relevant parameters for vehicle identification.

Proposed changes to align RxSWIN provisions with the RxSWIN template adopted through WP.29-197-06, remove the proposed requirement to comply with UN R156/01 or later from R157 and R171, remove amendments to UN R155 as decided by the IWG CS/OTA, apply the RxSWIN amendments also to earlier series of amendments in R13, R13-H, R79, R131, R152, R157, and R171, update references to the latest version of R.E.3, ECE/TRANS/WP.29/78/Rev.8, in earlier series, and correct paragraph references and improve structure in R89, R139, R140, R155, R156, and R171.

The agenda includes adoption of the provisional agenda and minutes from the thirty-eighth session; proposals for amendments to R155 concerning multistage vehicles, separate technical units and component approval, and remote operation for automated driving systems; review of cyber and software requirements in the ADS Regulation; application of RXSWIN to R156; administrative provisions in R155 and R156 regarding Type Approval Authority for CSMS/SUMS and issuing approvals for out-of-scope vehicle types; and preparation of GRVA 26.

Proposal to insert provisions on Software Identification Numbers and software updates across UN R13, R13-H, R79, R89, R130, R131, R152, R155, R156, R157, R171, R175, and R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7 paragraph 2, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance with test reports, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered vehicles from new vehicles where type approval regulations are updated or hardware changes occur in series production with test duplication avoided where possible, clarifying that production is not considered definitively discontinued if manufacturers obtain subsequent extensions for software updates of registered vehicles, renumbering and inserting new items in approval communication annexes for R13SWIN, R13-HSWIN, R79SWIN, R89SWIN, R130SWIN, R131SWIN, R152SWIN, R155SWIN, R157SWIN, R171SWIN, R175SWIN, and R178SWIN information including whether held on vehicle and relevant parameter identification lists, and amending R157 and R171 to align software update requirements with R156 technical specifications and transitional provisions.