Proposal to amend UN R160:

• Amend definitions 2.8., 2.10., and 2.11. to clarify that automatically commanded steering function categories B2, D, and E are not part of a DCAS
• Delete definition 2.25.
• Amend definition 2.35. to simplify non-volatile memory
• Amend para. 2.45. to change service brake terminology
• Amend para. 2.51. to clarify time interval between events
• Amend para. 2.65. to abbreviate vulnerable road user
• Insert new definitions 2.71.–2.83. for rollover protection system, advanced emergency braking system, trigger activated, pre-event synchronization timer, blind spot monitoring system, emergency stop signal, turn signal, acceleration control for pedal error, advanced driver distraction warning system, driver drowsiness and attention warning system, driver control assistance system, and time to collision
• Restructure para. 5.3.1. to distinguish planar, VRU, and rollover events from AEBS events with specified triggers
• Amend para. 5.3.2. to clarify data locking conditions
• Restructure para. 5.3.3. to establish time zero for planar, VRU, rollover, and AEBS events
• Amend para. 5.4.3. to specify side and frontal collision tests
• Amend para. 6.1. to clarify post-crash acceleration measurement
• Insert transitional provisions 12.12.–12.16. providing that as from the official date of entry into force Contracting Parties shall not refuse type-approvals under the 03 series, as from 1 September 2031 or 2029 [date TBD] shall not accept type-approvals to preceding series first issued after that date, until 1 September 2033 shall continue accepting preceding series approvals first issued before 1 September 2031 or 2029 [date TBD], may grant approvals to preceding series, and shall grant extensions of existing approvals
• Amend Annex 4 Table 1 to split engine throttle and accelerator pedal data elements, increase sampling rates to 10 Hz, extend recording intervals for rollover events, add pre-event synchronization timer, trigger activated, ACPE status, ADDW status, DDAW status, blind spot monitoring status, turn signal status, DCAS status, DCAS driver monitoring system warnings, emergency stop signal status, and time to collision data elements, and modify footnotes accordingly

Proposal for a recording interval of 600 seconds prior to collision for driver drowsiness and attention warnings (DDAW), 240 seconds for advanced driver distraction warnings (ADDW), 240 seconds prior to collision for driver monitoring warnings from the driver-control assistance system (DCAS), triggers planar, VRU, Rollover, AEBS, AEBS for pedestrian, AEBS for bicycle, and AEBS for motor vehicle, and event data recording time-to-collision (TTC) range of 0 s to 5.0 s and resolution 0.1 s for AEBS events.

For vehicles equipped with an Automated Driving System, it shall be possible to retrieve DSSAD time-stamp data elements specified under paragraph 5.2. of Annex 8 of UN Regulation No. 185 recorded within at least the last 30 seconds prior to triggering of the respective EDR event, regardless of whether the DSSAD and the EDR are implemented as a single system or as separate systems. The time-stamp data elements retrievable from the DSSAD shall include the record for the last activation or deactivation of the feature used at the time of the event within the same power cycle. The data elements shall be retrievable in the format specified in Annex 8 of UN Regulation No. 185, though DSSAD location data may be omitted and dates and times recorded may be replaced with information representing the time elapsed between the recording of each DSSAD data element and the triggering of the EDR.

OICA presents research findings on direction indicator perceptibility when stop lamps activate simultaneously. Key findings indicate that spatial separation between functions, increased direction indicator intensity, and relative signal dominance improve perception. Research shows stop lamp luminance can reduce direction indicator recognition, particularly in near-field viewing. OICA concludes that minimum size requirements proposed in the German proposal exceed available evidence and may create unintended consequences without demonstrated safety benefits.

Proposal to add para. 3.2.3.1. requiring manufacturers to provide additional information on the Cyber Security Management System at request of the Approval Authority when the Certificate of Compliance for CSMS is issued by a different Approval Authority, add para. 5.1.5. allowing the Approval Authority to refuse type approval if insufficient information on the CSMS and its implementation was provided, and add para. 7.4.1.1. requiring all granting Approval Authorities to be included in reporting when different Approval Authorities are used for the Certificate of Compliance for CSMS and type approval of the vehicle type.

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.

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 insert new paras. 27 and 28 in Part C Guidance for the application of UN Regulation No. 155 to transformed vehicles. Para. 27 states the requirement that the Certificate of Compliance and type approval are issued by the same Approval Authority applies only within the scope of the type approval granted to the manufacturer concerned. Para. 28 states where a vehicle manufacturer modifies a vehicle with existing type approval and applies for new type approval covering the modification, they need not use the same type approval authority as was used by the original vehicle manufacturer.

OICA opposes introducing a regulatory requirement for horizontal adjustment of passing-beam/driving-beam and for AFS/ADB to the current SLR agenda. The proposal does not contribute to simplification of lighting regulations, no identified safety concern or ambiguity justifies this requirement, and it lacks a formal proposal from a Contracting Party, NGO, or other stakeholder. The SLR group is managing several longstanding unresolved issues, and introducing this topic risks further delaying progress. Harmonized requirements require comprehensive understanding of Periodic Technical Inspection specifications across all Contracting Parties, which are currently unavailable.

Proposal to amend UN R157, including Annex 4, paragraph 3.5.4, requiring manufacturers to monitor safety-relevant incidents and report critical incidents to type-approval authorities, a new paragraph 3.5.4.1 to require approval authorities to upload remedial action information to the DETA database within 14 days, and a new Annex 7 to provide guidance for authorities on using DETA to exchange incident information.