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.

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 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).

Proposal to:

• Insert new Introduction paragraph 17 describing continuous review of DCAS based on technology development and monitoring data,
• Amend para. 2.11. to define ‘Target Lane’,
• Amend para. 5.3.5.1. to specify system boundary detection and assistance termination,
• Amend para. 5.3.7.1.4. to require warning signals when steering support diminishes,
• Amend para. 5.3.7.2.1.1. to require driver non-disengagement for 2 seconds before manoeuvre initiation,
• Insert para. 5.3.7.2.1.13. requiring manufacturer description of system behaviour if driver disengages during manoeuvre,
• Amend para. 5.3.7.2.3.1. to ensure sufficient driver confirmation time,
• Amend para. 5.3.7.3.1. to require compliance with 04 or later series of UN R79 Risk Mitigation Function,
• Amend para. 5.3.7.5.1.1.2. to require driver information on headway configuration below 2 seconds,
• Amend para. 5.5.3.1. to require ‘off’ mode at powertrain initiation,
• Amend para. 5.5.4.1.1. to add intended driver-confirmed manoeuvres to driver information,
• Renumber and amend para. 5.5.4.2.2.3. to prioritize simultaneous emergency assistance system warnings,
• Amend paras. 5.5.4.2.5.2. and 5.5.4.2.5.2.1. to define visual disengagement and re-engagement criteria,
• Amend para. 5.5.4.2.7. to add disengagement detection strategies,
• Amend para. 5.5.4.2.8.1. to disable system activation upon prolonged insufficient engagement,
• Amend para. 6.2.4.1. to specify deceleration limits for approaching vehicles,
• Amend para. 14.2. to exclude software update approvals from discontinuation determination,
• Delete Annex 3 paras. 2.15. and 2.16.,
• Amend para. 3.1.1. to specify documentation package retention periods of 10 years from production discontinuation,
• Renumber para. 3.5.7. to 3.4.5.,
• Insert new para. 3.5.5. on safety management during operation phase,
• Renumber former para. 3

Proposal to:

• Amend the introduction to clarify that the regulation is established based on current technology and limited vehicle data, with continuous review based on technology development and monitoring data,
• Amend the definition of ‘Target Lane’,
• Insert a definition of ‘Highway-like road’,
• Amend requirements for system boundary detection, steering support at boundaries, manoeuvre initiation conditions, lane change responses, driver unavailability response, and driver disengagement detection,
• Amend provisions for withholding of hands-on-requirements on highways and highway-like roads up to 130 km/h,
• Insert requirements for system behaviour when driver disengagement is detected during manoeuvres,
• Amend approaching vehicle deceleration requirements,
• Amend production discontinuation criteria,
• Insert documentation requirements for system information strategy and operation phase safety management,
• Amend Annex 4 testing provisions to include bicycle target testing and provisions for non-rule-based algorithms,
• Amend simulation tool criticality analysis requirements in Annex 5.

Proposal to amend footnote 25 to reduce the maximum number of recorded DCAS warnings from 15 to 10 per current ignition cycle. The justification presented cites data burden reduction while retaining information about habitual driver disengagement patterns. Supporting documentation references two autopilot collision cases—Florida 2016 and California 2018—where recorded warnings within existing data retention periods would have revealed repeated disengagement that current recording parameters miss, demonstrating that 10 warnings combined with extended recording duration enables identification of ineffective warning strategies.

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.

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.

Proposal to amend para. 3.5.1. in Annex 3 to require the manufacturer to demonstrate to the Type Approval Authority at least every three years that the safety management system continues to comply with requirements for software and hardware employed in the system to manage safety and continued compliance throughout the product lifecycle. This amendment resolves outstanding issues in the 01 series of amendments to UN Regulation No. 171.

Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information.

Proposal to amend ECE/TRANS/WP.29/2026/86:

• Renumber reference to para. 5.3.7.2.1.1.1. to 5.3.7.2.4.10.,
• amend para. 5.3.7.2.4.2. to replace “Further” with “The”,
• amend para. 5.3.7.2.5.3.1. to insert “or highway-like road”,
• amend para. 5.3.7.2.6.1. to delete maximum operating speed language and revise testing conditions,
• amend para. 6.4.2. to add “for more than 2 seconds immediately prior to the drive off”,
• amend Table 1 item 4.c in para. 7.2.3.1. to add “while the driver is detected to be disengaged”,
• replace “definitely” with “definitively” in para. 14.2. and Annex 3,
• insert new para. 16.2.3. establishing 1 September 2029 date for non-acceptance of type approvals,
• amend Annex 1 para. 6.4. to renumber and revise highway-like roads language,
• renumber reference in Annex 3 para. 3.5.7.,
• amend Appendix 2 of Annex 3 para. 2.3.2.,
• amend and delete multiple Annex 4 diagrams and test conditions,
• amend test execution requirements.

Proposal to:

• Amend Introduction para. 17 to clarify DCAS development based on current technology and data
• Amend para. 2.11 to delete “the” before “travel”
• Insert new para. 2.28.1. defining “Highway-like road” with characteristics including at least two lanes, designated speed limit of at least 80 km/h, physical separation dividing opposite traffic, and absence of at-grade pedestrian crossings, rail crossings, or road intersections
• Amend para. 5.3.5.1 to specify system shall leave active mode with exception of driver unavailability response
• Amend para. 5.3.7.1.4 to delete “the” before “front tyre”
• Amend para. 5.3.7.2.1.1 to change “detected” to “deemed” and specify disengagement duration of more than 2s
• Insert new para. 5.3.7.2.1.13 requiring manufacturer to describe system behaviour if driver detected disengaged during manoeuvre
• Amend para. 5.3.7.2.3.1 to delete requirements reference and require sufficient time for driver confirmation
• Amend para. 5.3.7.2.5.3.1 to add “or highway-like road” to highway operation requirements
• Delete para. 5.3.7.2.4.3 and renumber paras. 5.3.7.2.4.4 to 5.3.7.2.4.11 as 5.3.7.2.4.3 to 5.3.7.2.4.10
• Amend para. 5.3.7.3.1 to reference systems driver unavailability response and RMF requirements of 04 series UN R79
• Amend para. 5.3.7.3.3 to specify system capable of lane changes during driver unavailability response in compliance with RMF requirements
• Amend para. 5.5.4.2.2.3 to renumber and require warning strategies prioritize simultaneously activated emergency assistance systems
• Amend paras. 5.5.4.2.5.2 and 5.5.4.2.5.2.1 to specify visual disengagement criteria, dashboard consideration limited to 3 seconds, and visual re-engagement duration of at least 200 milliseconds
• Amend para. 5.5.4.2.6.5 to allow HOR withholding on highway-like roads at speeds up to 130 km/h and require verification of road characteristics for at least 500 m or 30 seconds, demonstration of safe cyclist operation, and HOR at least 7s before end of highway-like road
• Amend paras. 5.5.4.2.7 and 5.5.4.2.7.1 to add assessment of gaze direction changes and insert new para. 5.5.4.2.7.1
• Amend para. 6.2.4.1 to permit deviation from assessment at speeds up to 60 km/h with manufacturer explanation to Type Approval Authority
• Amend para. 14.2 to change “definitely” to “definitively”
• Amend Annex 1 to add para. 6.4.1 for system capability of withholding HORs on highway-like roads
• Delete Annex 3 paras. 2.15 and 2.16 defining “Highway” and “Non-Highway”
• Amend Annex 3 para. 3.1.1 to change “definitely” to “definitively”
• Renumber Annex 3 para. 3.5.7 to 3.4.5 and amend to require system information strategy

Proposal to amend GRVA/2026/16, based on GRVA-25-46. Insert new Introduction paragraph 17 regarding DCAS technology development and continuous review; amend paragraph 2.11. to define Target Lane; amend paragraph 5.3.5.1. to specify system boundary detection and feature transition requirements; amend paragraph 5.3.7.1.4. regarding steering support at boundary conditions; amend paragraph 5.3.7.2.1.1. to clarify driver disengagement detection timing; insert new paragraph 5.3.7.2.1.13. regarding manufacturer description of system behaviour during driver disengagement; amend paragraph 5.3.7.2.3.1. regarding driver confirmation time; amend paragraph 5.3.7.3.1. concerning risk mitigation function compliance; amend paragraph 5.3.7.5.1.1.2. regarding headway configuration notification; insert footnote 3 defining initiation of powertrain; amend paragraph 5.5.3.1. to clarify system off mode default status; amend paragraph 5.5.4.1.1. removing reference to system-initiated manoeuvres; amend paragraph 5.5.4.2.2.3. regarding warning escalation strategy; amend paragraphs 5.5.4.2.5.2. and 5.5.4.2.5.2.1. regarding visual disengagement assessment; amend paragraphs 5.5.4.2.7. and 5.5.4.2.7.1. regarding disengagement detection strategies; amend paragraph 5.5.4.2.8.1. regarding system activation disabling; amend paragraph 6.2.4.1. regarding approaching vehicle deceleration at speeds up to 60 km/h; amend paragraph 14.2. regarding production discontinuation; delete Annex 3 paragraphs 2.15. and 2.16. defining Highway and Non-Highway roads; amend Annex 3 paragraph 3.1.1. regarding documentation package retention; renumber Annex 3 paragraph 3.5.7. to 3.4.5. and insert new paragraph 3.4.5. regarding system information strategy; insert new paragraph 3.5.5. regarding safety management processes during operation phase; renumber former paragraphs 3.5.5. and 3.5.6. to 3.5.6. and 3.5.7. respectively; insert Annex 3 Appendix 2 with new definitions section; amend Annex 4 Introduction regarding test requirements and extended tests; amend paragraph 4.2.2.1. regarding longitudinal control distance; insert new paragraph 4.2.2.2. regarding non-repeatable outcomes; amend paragraphs 4.2.5.2.8.1.2., 4.2.5.2.10.1.1., and 4.2.5.2.12.1.1. regarding bicycle target specifications; delete paragraph 4.2.5.2.14.1.2.; amend paragraph 4.2.5.2.14.2.1. regarding test execution requirements; and amend Annex 5 paragraphs 3.4.8.2. and 3.5.5.1. regarding M&S data and simulation tool criticality assessment.

For the purposes of type approval under any UN Regulation requiring the verification of the timing of a system intervention, manufacturers shall provide to the approval authority or its designated technical service information on the method by which the initiation of any system intervention can be objectively identified and retrieved, including specific flags, status bits, event codes on in-vehicle networks, or visual indications on screens; clear instructions and all necessary tools for the Technical Service to extract, access and interpret the signal identifying the initiation; documented procedures including corresponding data sources, resolution, and timing accuracy appended to the type approval test report; and, where a visual indication displayed on a screen is used, documented latency between the earliest internal point at which the system initiates the function and the moment the visual indication becomes visible on the screen, expressed as a fixed value with associated uncertainty, with the documented latency value used to correct the observed timing of the screen indication appended to the type approval test report.

Proposal to amend GRVA/2026/14 and GRVA/2026/18: insert new paragraph 2.28.1. defining “Highway-like road” as a non-highway section with at least two lanes, designated speed limit of at least 80 km/h, no prohibition of pedestrians and cyclists, physical separation dividing opposite traffic, and no at-grade marked pedestrian crossings, rail crossings, or road intersections; amend paragraphs 5.3.7.2.3.1. and 5.5.4.2.6.5. to address highway-like road operation and withholding of HORs; insert new paragraph 4.2.5.2.16. to Annex 4. specifying testing for longitudinally moving bicycle targets; amend Annex 1. to add items 6.4. and 6.4.1. regarding withholding of HORs; and insert new paragraph 16.2.3. establishing that as from 1 September 2029 Contracting Parties shall not be obliged to accept type approvals issued to the preceding series of amendments for systems capable of withholding HORs on highway-like roads.

The document requests guidance on the legal basis for provisions within UN Regulations extending beyond the End-of-Production date and which authority such provisions address. Examples include UN R171 requirements for manufacturers to demonstrate safety management systems to the Type Approval Authority every three years and report annually on Driven Coded Auxiliary System operation until production is discontinued, and UN R155 requirements for Cyber Security Management Systems to apply to the post-production phase when vehicles remain operational but are no longer produced. The document poses an additional question regarding vehicle safety when manufacturers cease operations and cannot fulfill post-deployment safety provisions.

Proposal to amend the original version (GRVA/2026/15), insert para. 5.3.7.2.1.13. to require the manufacturer to describe in the safety concept the system behaviour in case the driver is detected to be disengaged during a manoeuvre; amend the original version and the 01 series (GRVA/2026/15 and GRVA/2026/17), amend para. 3.5.1. of Annex 3 to require the manufacturer to demonstrate to the Type Approval Authority at least every three years that the safety management system continues to comply with requirements; amend the 01 and 02 series (GRVA/2026/17 and WP.29/2026/86), amend para. 2.3.2. of Appendix 2 of Annex 3; amend the 02 series (WP.29/2026/86), amend para. 4.2.5.2.19.2.1. of Annex 4; and amend the original version, 01 series and 02 series (GRVA/2026/15, GRVA/2026/17 and WP.29/2026/86), amend para. 4.2.5.2.14.1.2. of Annex 4 and para. 4.2.5.2.14.2.1. of Annex 4.

Proposal to delete the draft “Reserved” paragraph 5.3.7.2.4.3. in GRVA/2026/18. Reserving paragraph 5.3.7.2.4.3. in the 01 series would mean that the subsequent paragraphs would be out of line with the numbering in the 02 series, making future amendments to UN R171 unnecessarily challenging.

Proposal to develop UN GTR for both assisted and automated parking. The document presents parking product classifications in China, including assisted parking (park-in/park-out, cruising capability, remote-control variants) and automated parking systems. Current UN Regulations lack specific technical requirements, test methods, and test scenarios for parking functions. China is developing national standards GB for parking combined driver assistance systems and automated parking systems, with approval expected by end of 2026 and early 2027 respectively. The proposal suggests establishing a Task Force to study applicability of current UN Regulations to parking products, then determining whether to establish an IWG or formulate new regulations.

Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R155, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information.

Since the 24th (January 2026) GRVA session, the ADAS task force held an online session on 3 March 2026. A 02 series of amendments to UN R171 (GRVA-24-17/Rev.2) was approved and submitted to WP.29 as WP.29/2026/86. Draft supplements and consolidated and extracted versions for 00 and 01 series were prepared (GRVA-24-18-A, GRVA-24-19-A, GRVA-24-18-B, GRVA-24-19-B). For the 25th GRVA session, editorial modifications and consolidated and extracted versions were submitted (GRVA/2026/14, GRVA/2026/15, GRVA/2026/16, GRVA/2026/17, GRVA/2026/18). The task force seeks guidance on provisions for DCAS use on highway-like roads and feedback on existing provisions following practical implementation of UN R171. The ADAS task force will be maintained with a break in activities pending stakeholder inputs and concrete proposals.

Proposal to amend UN R13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178 by introducing provisions on software identification and software updates. Amendments add new paragraphs referring to Software Identification Number definitions in Consolidated Resolution R.E.3, require manufacturers to provide Technical Services with information on hardware and software influencing performance, permit vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles while avoiding test duplication, and modify production discontinuation provisions to exclude cases where manufacturers seek approval extensions for software updates of registered vehicles.

Proposal to modify DCAS requirements:

• Address system-initiated manoeuvres in non-highway environments and during phases of withholding hands-on requests,
• Enhanced driver disengagement monitoring and warning strategies,
• Controllability requirements for complex operational scenarios,
• Speed limit assistance features,
• Safe headway assistance,
• System validation through multiple assessment pillars including physical tests and in-service monitoring,
• Comprehensive safety management system requirements for manufacturers,
• Monitoring of DCAS operation with mandatory reporting of safety-critical occurrences to approval authorities,
• Periodic reporting requirements with specific data collection metrics,
• Software identification and updating compliance with UN R156,
• Clarification that DCAS is only permitted to operate when a driver is in control,
• Clarification that vehicles of categories X and Y without driver control capability are not required to comply with the regulation.

Consolidated version based on WP.29/2025/7 as amended by WP.29-195-05, WP.29/2025/144, GRVA-24-18, and GRVA-24-19. See GRVA/2026/18 for the proposed amendments.

Proposal to clarify UN R171 on Driver Control Assistance Systems (DCAS):

• Clarifications to definitions, adding “Highway-like road” definition
• Clarifications to system boundary detection, manoeuvre initiation, and driver disengagement requirements
• Amendments permitting withholding of hands-on requests on highway-like roads up to 130 km/h
• Clarifications on Risk Mitigation Function terminology
• Amendments allowing alternative strategies for lower-speed lane changes
• Addition of operational phase safety management processes
• Clarifications on testing requirements and non-rule-based algorithm repeatability.

Proposal to amend UN R171 based on GRVA/2026/15:

• Insert new introduction paragraph 17 establishing the regulation on current technology with continuous review based on data
• Amend paragraphs on system boundaries, driver disengagement detection, manoeuvre initiation, and Risk Mitigation Function
• Clarify driver state monitoring and visual engagement assessment
• Update terminology for powertrain
• Delete duplicate definitions
• Add processes for safety management during operation phase
• Insert definition of “Evidence”
• Clarify base and extended test requirements
• Update language from “cyclist” to “bicycle” in test scenarios

Consolidated proposal to clarify provisions in the original version of the Regulation. See GRVA/2026/16 for the proposed amendments.

Proposal to amend UN R171 to modify paragraphs 5.5.4.2.8.2., 5.3.7.2.4.2., 5.3.7.2.6.1., 6.4.2., 7.2.3.1., 14.2., and Annexes 3 and 4. The amendments include clarifications regarding driver engagement determination, system boundary conditions, automatic acceleration in non-highway environments, system-initiated manoeuvres tracking, production discontinuation, documentation retention periods, supplier safety management arrangements, and test scenario specifications for bicycle and cyclist targets.

The ADAS task force reviewed draft amendments to UN Regulation No. 171. The task force agreed on editorial corrections to the 02 series of amendments for a formal submission to the June WP.29 session. CLEPA submitted three clarification proposals for the 02 series to be addressed via supplement if needed. Draft supplements to the original version and 01 series were introduced for GRVA consideration. The TF agreed to take a break before initiating Phase 4 development work and invited stakeholders to submit written proposals on future developments.

Proposal to establish a Supplement to the 01 series of amendments to UN Regulation No. 171 on Driver Control Assistance Systems. The amendments modify technical requirements for system boundaries, driver disengagement detection, manoeuvre initiation, and driver unavailability response. New definitions for “Target Lane” and “Highway-like road” are introduced. Changes address system behaviour at boundary conditions, visual engagement criteria, and hands-off request withholding on highway-like roads. Testing and documentation requirements are revised to clarify Type Approval Authority responsibilities and manufacturer safety management processes during the operation phase.

Proposal to modify provisions for system boundaries, driver disengagement detection, manoeuvre initiation, and risk mitigation functions. Changes include clarifications on visual engagement assessment, headway configuration warnings, and driver unavailability response procedures. Amendments address system behaviour at boundary conditions, lane change manoeuvre protocols, and documentation requirements. Test procedures are updated regarding bicycle target positioning and terminology. Manufacturing processes for safety management during vehicle operation are added. Documentation definitions and simulation model criticality assessments are clarified.

Proposal to amend Annex 4 – Data elements and format, Table 1, modifying Advanced driver distraction warning (ADDW) data elements to record status and time since warning issued instead of number of warnings and time elapsed since last warning, modifying Driver control assistance system (DCAS) driver monitoring system data elements to record time since disengagement warning issued and warning type instead of number of hands-on requests, eyes-on requests, direct control alerts, and time elapsed since last warning, and adding Driver drowsiness and attention warning (DDAW) status and time since warning issued data elements while removing number of warnings and time elapsed since last warning, with ADDW and DDAW elements listed up to five times for most recent warnings and DCAS warning type listed up to fifteen times for most recent warnings on current trip.

Consolidated version of the 02 series of amendments based on GRVA/2026/4 and including all amendments agreed during the 24th GRVA session.

Proposal to revise the transitional provisions and provisions on continued compliance with Safety Management Systems provisions.

Status report including supporting explanation of the 02 series amendment proposals.

Proposal to allow alternative strategies to be used for lower speed lane changes, clarify wording, and correct typographical errors.