Proposal to improve the list of examples of risk-management practices to support para. 8.1.6.1.

Proposal to improve the interpretation of para. 8.1.6.1.(d) concerning verification that the risk management activity covers and is performed over the entire lifecycle.

Proposal to improve the interpretation of para. 8.1.6.1.© concerning verification that the risk management activity includes risks from third parties.

Proposal to improve the interpretation of para. 8.1.6.1.(a) concerning verification that reactive and proactive practices for risk management are in place.

Proposal to modify para. 8.1.7.1.(h) to replace “aims to ensure that” with “focuses on”, replace “Assessment of how organizations coordinate” with “Assessment that organizations coordinate”, delete “and product reviews” from the list of change management triggers, and delete “the approach and output from various” before “monitoring procedures” and delete “including operational data, safety reports and performance indicator” from the examples of monitoring procedures.

Proposal to amend the interpretation of para. 8.1.5.1.(d) to replace “a key” with “an”, delete “effective”, and insert “processes” before “of the SMS”. The proposal streamlines guidance text on SMS safety policy to improve clarity in describing how safety policy demonstrates management commitment to safety through approval by the accountable executive and supports promotion of safety and continuous improvement of the SMS.

Proposal to improve guidance on para. 8.1.8.1. which focuses on aspects that support safety and safety culture such as people, competencies, and communication.

Proposal to revise guidance text in para. 8.1.6.1.(d) to delete the statement that the intention is to ensure safety promotion contributes to ongoing learning and improvement, reinforcing the adaptive nature of the SMS, and insert revised text stating that this point focuses on continued evaluation contributing to ongoing learning so that the SMS remains effective, allowing an adaptive nature through modification and adaptation supported by safety recordkeeping.

Proposal to add resources providing guidance on Safety Performance Indicators. The added resources include J3237, Dynamic Driving Task Assessment (DA) Metrics for Automated Driving Systems; AVSC00006202103, Automated Vehicle Safety Consortium (2021) Best Practice for Metrics and Methods for Assessing Safety Performance of Automated Driving Systems (ADS); AVSC00008202111, Automated Vehicle Safety Consortium (2021) AVSC Best Practice for Evaluation of Behavioural Competencies for ADS-Dedicated Vehicles (ADS-DVs); SAE J2944, Operational Definitions of Driving Performance Measures and Statistics; and SAE J3197, Automated Driving System Data Logger.

Based on ADS-21-68/Rev.1, amend para. 3.2.3.(b) to clarify that the regulation requires the safety level of ADS to be at least to the level of a competent and careful human driver as a general concept and technology-neutral comparator, that manufacturers should explain how they determine and apply this concept accounting for national specificities including those that might arise in relevant cases, that different approaches or combinations of approaches may be used varying depending on the safety concept, claims and argument structure, and approach to safety assessment, that no single approach is presumed better, that manufacturers may use more than one approach, that driver population reference data sets should be subject to appropriate selection, processing and interpretation, and to provide non-exhaustive examples of reference driver based approaches and behaviour-based approaches.

Proposal to revise the guidance text in para. 8.1.8.1.(c) by deleting “This element ensures the existence of effective communication channels, both internally and externally, to support awareness and information sharing.” and inserting “This point focuses on the existence of communication channels, both internal and external, to support awareness and information sharing.” The proposal follows comments received in the 18th ADS Workshop where discussion of the SMS section in a dedicated small drafting group was requested, and the current text aims at streamlining the text.

Proposal to delete the requirement that competence is expected to be actively developed and maintained through structured training and insert that this point focuses on the existence and maintenance of SMS training plans to support competence for the SMS management in para. 8.1.6.1.(b).

Proposal to improve the interpretation of para. 8.1.5.1.(e) the description of the means/approaches to engage people within the organisation in the culture of safety.

Proposal to improve the interpretation of para. 8.1.5.1.(c) concerning the organizational structure and the safety governance elements and their appropriateness for the needs of the organisation.

Proposal to improve the interpretation of para. 8.1.5.1.(b) concerning the general recognition of the inherent risks of ADS-related activities throughout their life cycle, including the risks of the parties involved.

Proposal to improve the interpretation of para. 8.1.5.1.(a) concerning the definition of the principles and objectives upon which the SMS is built, operated, and maintained.

Proposal to improve the interpretation of para. 8.1.5.1. concerning the scope and contents of the manufacturer’s SMS safety policy.

Proposal to amend Annex 4 Table 1 to modify the Vulnerable road user secondary safety system warning indicator status data element to record interval -1.1 to 0 sec, modify the VRU Accident emergency call system status data element to recording interval 0-300 ms or 0 to end of event time plus 30 ms whichever is shorter, add Advanced driver distraction warning (ADDW) status as mandatory with On and Off values for Planar, VRU, Rollover, and AEBS events, add ADDW time since warning issued as mandatory with 0 to 240 sec range and +/-1% accuracy at 1 sec resolution, add Driver control assistance system driver monitoring system time since disengagement warning issued as mandatory with 0 to 1000 sec or 0 to 240 sec range and +/-1% accuracy at 1 sec resolution, add Driver drowsiness and attention warning (DDAW) status as mandatory with On and Off values for Planar, VRU, Rollover, and AEBS events, and add DDAW time since warning issued as mandatory with 0 to 60 min or 0 to 600 seconds range, +/-1% accuracy, and 1 min or 1 sec resolution.

Document SG-EDR-47-02 and SG-EDR-47-03 were discussed. The group agreed to include definitions 2.8, 2.10, 2.11, and 2.20 with edits. Proposed definitions will be circulated by June 15 for review with comments due June 26. For data elements, disagreements on frequency rates between contracting parties and industry remain in square brackets. EDR for ADS will be addressed under GRVA and the ADS IWG. An October in-person meeting in Berlin is planned, pending WP.29 direction on integrating DSSAD into the ADS IWG.

Proposal to amend UN R160 definitions and event recording requirements:

• Amend definitions 2.8., 2.10., and 2.11. regarding Automatically Commanded Steering Function categories A, B1, and C,
• Amend definition 2.18. on “End of event time”,
• Amend definition 2.20. on “Engine throttle, percent full”,
• Delete definition 2.25.,
• Amend definition 2.35. on “Non-volatile memory”,
• Amend definition 2.45. on “Service brake status”,
• Amend definition 2.51. on “Time interval between current event and previous event”,
• Amend definition 2.65. on “VRU secondary safety system”,
• Insert new definitions 2.71. through 2.83.,
• Renumber para. 2.2. as 2.25.,
• Amend para. 5.3.1. to establish trigger conditions for planar, VRU, and rollover events separately from AEBS events with provision for events occurring within 300 ms overlap,
• Amend para. 5.3.1.1. through 5.3.1.5. to specify deployment triggers,
• Add new para. 5.3.1.2. for AEBS emergency braking demand trigger,
• Amend para. 5.3.2. and insert new para. 5.3.2.4. on rollover protection system deployment locking,
• Amend para. 5.3.3. to establish time zero for planar, VRU, and rollover events separately from AEBS events,
• Amend para. 5.4.3. to clarify crash test requirements as UN Regulations 95 and either 94 or 137,
• Amend para. 6.1. on acceleration measurement verification,
• Insert transitional provisions in new paras. 12.12. through 12.16. establishing entry into force of 03 series amendments, non-obligation to accept earlier series approvals as from 1 September 2031, and obligation to continue accepting earlier series approvals until 1 September 2033,
• Amend Annex 4 Table 1 data elements for recording intervals, sample rates, ranges, and new elements including Pre-Event Synchronization Timer, Trigger activated, ACPE, ADDW, DDAW, blind spot monitoring, turn signal, DCAS, emergency stop signal, and TTC.

Proposal to amend Paragraph B to insert new requirement 5.1.3 establishing that the Approval Authority or Technical Service shall refuse to grant type approval regarding cyber security where the vehicle manufacturer has not fulfilled requirements in paragraph 7.3., notably that the Certificate of Compliance for the Cyber Security Management System has not been issued by the same Approval Authority granting the type approval, add explanatory text clarifying that this ensures Article 2(2) of the 1958 Agreement compliance while permitting cooperation between Approval Authorities and acceptance of prior documentation, amend Paragraph K to remove existing guidance text in paragraphs 6.1 and 7.1 regarding Certificate of Compliance issuance and inter-Authority arrangements, and insert statement that no guidance is included regarding paragraph 6 requirements. These changes support proposal GRVA/2026/30.

This document presents a concept for approvals of electrical/electronic sub-assemblies (ESAs) as components according to UN R155, and the installation of such approved components on vehicles already holding UN R155 approval. The proposal removes the possibility of separate technical unit (STU) approvals as a first step, limiting coverage to components connected only to power and/or reading data through approved existing interfaces. The document restructures UN R155 into three parts: Part I covers vehicle type approvals; Part II covers ESA component approvals with cybersecurity requirements; Part III covers vehicle type approvals regarding installation of approved ESAs. Requirements include cybersecurity management systems, risk assessments, threat mitigations, and reporting provisions for development, production, and post-production phases.

Proposal to amend UN R160:

• Insert new paras. 12.12. to 12.17. establishing transitional provisions for the 03 series of amendments, including that:
  • from the official date of entry into force, no Contracting Party shall refuse type approvals under the amended Regulation,
  • from 1 September 2031, Contracting Parties shall not be obliged to accept type approvals to preceding series first issued after that date,
  • until 1 September 2033, Contracting Parties shall accept type approvals to the 02 series first issued before 1 September 2031,
  • from 1 September 2033, Contracting Parties shall not be obliged to accept type approvals to preceding series,
  • Contracting Parties may grant type approvals according to any preceding series,
  • and Contracting Parties shall continue to grant extensions of existing approvals to any preceding series,
• Amend Annex 4 Table 1 and footnotes 28, 29, and 30 regarding trigger activated recording, powertrain torque demand signals, AEBS target classification, and TTC calculation requirements.