Change request to amend para. 4.1.6.2. to add a condition that an ADSF-1 shall execute a fallback to an MRC if there is insufficient time available for transition or if it has not been possible to complete a system-initiated deactivation procedure. The revision ensures that in situations where an ADSF-1 does not have time to safely transition to the fallback user, it should fallback to an MRC to avoid having a fallback user that is unprepared and unable to safely take back control.
Proposal to clarify para. 5.3.1.14 by replacing ‘end states’ with ‘possible vehicle resting positions’, adding examples of stopped in lane, stopped on shoulder, and stopped in parking spot, removing ‘feature’ from references to the ADS to provide flexibility, and adding requirement for the ADS to select a mitigated risk condition in addition to attempting to reach it.
Table to facilitate consideration of ADS Phase 2 work items and their integration into an ADS2 IWG plan for 2026-2028.
Document lists work items for phase 2 of the IWG on Automated Driving Systems, organized by categories: ADS requirements covering Dynamic Driving Task (remote assistance, connectivity, MRC, priority vehicles and road safety agents); interactions between ADS and its user(s) (external HMI, feature activation and deactivation, ADS to ADAS transitions, HMI commonality, resuming control by fallback user); other ADS requirements (software parameter adaptation, DSSAD, non-DDT related tasks); manufacturer requirements (ISMR, safety case, ODD description, leading metric considerations); items affecting UN Regulation or GTR only (separate technical units, communication document, mutual recognition of SMS); and other items (drafting and text improvements, system updates and thresholds, end-to-end AI ADS, items remaining from FRAV/VMAD integration document). Each item identifies lead parties, priority levels, and status.