Presentation proposing an AI Management System (AIMS) as a complementary organizational layer to existing safety, cybersecurity, and software update management systems. AIMS would regulate AI through organizational processes rather than technical requirements, covering data lifecycle, model development, verification and validation, change control, and operational monitoring. The system is technology-neutral, lifecycle-based, and aligned with industry standards including ISO 26262, ISO 21448, and ISO/IEC 42001, avoiding the need for product-specific AI test procedures and re-approval of model updates.

Discussion of R.E.3. revision 8 adopted by WP.29 in November 2025, which allows vehicle manufacturers to apply for new approvals for software versions on registered vehicles. The Netherlands raised concerns about compatibility with type approval principles, the 1958 Agreement, and EU law, citing issues with traceability, multiple approvals for one type, approval requirements for non-production vehicles, and product marking. The document proposes distinguishing between ‘live’ approvals for new vehicles using normal type approval procedures and ‘legacy’ approvals for in-service vehicles using an updated revision concept, with updates to Schedule 3 of the 1958 Agreement and R.E.3. revision 9.

Status report on the EV/HFCV Retrofit Systems IWG activities. The group held six meetings since the last GRPE session and is currently focused on the EV part, with HFCV-specific issues deferred to a future series of amendments. Key discussion items include scope definition with agreement to exclude vehicles holding approvals according to UN R155 and UN R156, definition of Electric Powertrain Retrofit System, vehicle family notion, and type of EPRS. Experts from different GRs participate in discussions on electrical safety, EMC, braking, cybersecurity, and power determination. Benchmarking of existing national requirements for EV retrofit activities is ongoing. Regulation drafting continues on scope and type definition, with demonstrations of retrofitted vehicles expected at the 200th WP.29 session in November 2026.

Document outlining the 1st DETA/IWVTA Workshop held on 17 June 2026 in Flensburg, Germany. The workshop covered presentations on what DETA and IWVTA are, industry and government expectations, and issuance and acceptance of IWVTA certificates in the EU. Survey responses from 15 participants, including from Southeast Asian countries, indicated needs for more explanation on DETA access rights, onboarding processes for new Contracting Parties, and clearer guidance on how IWVTA can be modified to suit individual markets. Suggestions included developing supporting materials and guidelines on IWVTA application procedures and organizing a second workshop in Japan or Asia.

Minutes of the twelfth meeting of the IWG on EV/HFCV Retrofit Systems held 28 September 2026. The group adopted the provisional agenda and reviewed the work program, aiming to provide GRPE with a first draft of a future UN Regulation by 14–16 October 2026. The group focused on revising definitions in the draft UN Regulation, particularly EPRS definition, EPRS type, vehicle family, and installer provisions. Key unresolved issues include which components must remain identical within an approved type, alternative ways of grouping vehicles within a family, whether installer requirements should be included in the UN Regulation, and the scope regarding vehicles subject to UN Regulations Nos. 155 and 156.

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.