Safety-Relevant Guidance for On-Road Testing of Prototype Automated Driving System (ADS)-Operated Vehicles
- Ground Vehicle Standard
Remote driving, including remote fallback test driving of prototype ADS-operated test vehicles in driverless operation. (Note: The term “remote fallback test driver” is included as a defined term herein and is intended to be addressed in a future iteration of this document. However, at this time, too little is published or known about this type of testing to provide even preliminary guidance.)
Testing of driver support features (i.e., Levels 1 and 2), which rely on a human driver to perform part of the dynamic driving task (DDT) and to supervise the driving automation feature’s performance in real time. (Refer to SAE J3016.)
Simulation testing (except for training purposes).
Maintaining auditable procedures and documentation.
Adhering to applicable privacy laws and principles.
Ensuring adequate data collection and recording integrity to support post-crash forensic analysis.
A systems engineering approach (i.e., V-model).
Adherence to a recognized system safety process(es) for identifying hazards and implementing strategies for mitigating them.
Implementation of an electrical/electronic (E/E) architecture (system/hardware/software levels) capable of implementing hazard mitigation concepts and strategies.
Analysis and testing of identified hazard mitigation strategies (hardware and software).
All hardware and software interfaces between production- and development-level hardware and software should be analyzed and tested for operational integrity, including analysis of failure modes and effects.
Developmental software added to a vehicle (including that equipped on added hardware modules) should be monitored and/or include self-diagnostics for safety-critical functions, which should be verified for efficacy prior to on-road testing. Alternatively, system-level approaches to ensuring developmental software safety (e.g., shadow mode testing) is also acceptable.
Data Sets - Support Documents
|Unnamed Dataset 1|
|Unnamed Dataset 2|
|Unnamed Dataset 3|
The On-Road Automated Driving (ORAD) committee reports to the Driver Assistance Systems Steering Committee of the Motor Vehicle Council. The ORAD committee is responsible for developing and maintaining SAE standards, recommended practices, and information reports related to motor vehicle driving automation system features across the full range of levels of driving automation. "On-road" refers to publicly accessible roadways that provide driving environments for the users of motor vehicles of all classes and all levels of driving automation. However, the ORAD committee will focus primarily on Automated Driving Systems (ADSs) as defined by SAE J3016, namely, levels 3-5 which are capable of performing the complete DDT on a sustained basis while engaged. This includes cooperative automation at these levels. While automated subsystems from other committees will be integrated with automated driving technology, the ORAD committee does not focus on specific subsystems like short-range communication, active safety such as electronic stability control and automated emergency braking or other driver assistance such as lane keeping assistance and cooperative adaptive cruise control. The ORAD committee will coordinate with and contribute to committees and task forces in these distinct areas of expertise.