Unsettled Topics Concerning The Field Testing Of Automated Driving Systems

Unsettled Topics in Automated Vehicle Data Sharing for Verification and Validation Purposesdiscusses the unsettled issue of sharing the terabytes of driving data generated by Automated Vehicles (AVs) on a daily basis. Perception engineers use these large datasets to analyze and model the automated driving systems (ADS) that will eventually be integrated into future "self-driving" vehicles. However, the current industry practices of collecting data by driving on public roads to understand real-world scenarios is not practical and will be unlikely to lead to safe deployment of this technology anytime soon. Estimates show that it could take 400 years for a fleet of 100 AVs to drive enough miles to prove that they are as safe as human drivers. Yet, data-sharing can be developed - as a technology, culture, and business - and allow for rapid generation and testing of the billions of possible scenarios that are needed to prove practicality and safety of an ADS - resulting in lower research and development costs to the industry. Unsettled Topics in Automated Vehicle Data Sharing for Verification and Validation Purposes explores how this could lead to better regulation, insurance, public acceptance - and finally, shorter technology development cycles. Finding a business case and changing to an open data culture are not going to be easy tasks, but data sharing is the only way forward for the whole industry to move to the next phase of deployment after nearly a decade of intense research.

Comprehensive learning resource providing a framework for successful application of advanced transportation technologies in urban areas Smart Mobility: Using Technology to Improve Transportation in Smart Cities addresses the nature and characteristics of smart cities, providing a focus on smart mobility within urban areas and the opportunities and challenges associated with the application of advanced transportation technologies. The three highly qualified authors include an emphasis on decarbonization possibilities and the potential for smart mobility to reduce emissions and fuel consumption while optimizing modal use, along with risk identification and management using a structured approach. A focus is also placed on the need for end-to-end travel support from origin to ultimate destination, reflecting consumer needs for comprehensive decision support and travel support services. Overall, Smart Mobility provides a framework, planning, and KPIs for smart mobility success and explains how effective performance management can be enabled. Additional topics covered in this modern and thought-provoking work include: Policies and strategies associated with smart mobility, including a description of the organizational arrangements required to support smart mobility technologies The definition of appropriate institutional, funding, and commercial arrangements to assist interested practitioners to solve what is often their biggest challenge Coverage of smart mobility operational management, explaining the likely impact of smart mobility on transportation operations How to attain balance between transportation objectives and the avoidance of undesirable side effects such as congestion For public and private sector professionals in the smart mobility community, Smart Mobility is an essential and easy-to-understand learning resource that will help readers comprehend the state-of-the-art progress in the field and be prepared for future advancements in this important and rapidly-developing industry.

This document provides safety-relevant guidance for on-road testing of vehicles being operated by prototype conditional, high, and full (Levels 3 to 5) ADS, as defined by SAE J3016. It does not include guidance for evaluating the performance of post-production ADS-equipped vehicles. Moreover, this guidance only addresses testing of ADS-operated vehicles as overseen by in-vehicle fallback test drivers (IFTD).These guidelines do not address: 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.) Closed-course testing. Simulation testing (except for training purposes). Component-level testing. This document provides general safety-relevant guidance for testing prototype automated driving systems (ADS) equipped on test vehicles operated in mixed-traffic environments on public roads (hereafter, prototype ADS-operated vehicles). This document is being substantially updated in order to incorporate lessons-learned based on accumulated field experience in testing prototype ADS-operated vehicles on public roads, and to make it compatible with related SAE documents.It is assumed that the prototype ADS-operated vehicles that are the subject of this guidance have been developed using standardized methods for safer product development including, but not limited to: A systems engineering approach (i.e., V-model). Adherence to a recognized functional safety process, such as ISO 26262, 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).Prototype ADS-operated vehicles that are based on existing production vehicles rely on the existing vehicle's E/E architecture, as adapted for ADS. Prototype ADS technology provided via added hardware and software modules that are not integrated according to the vehicle manufacturer's specifications, should be checked to ensure that they do not interfere with base vehicle hardware or software systems. As such, they should abide by the following general principles: 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. All 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.Proper test program/operations management plays a key role in helping to maintain safety while conducting on-road testing of prototype ADS-operated vehicles. Unexpected behaviors (including incidents) should be reported accurately and consistently for later root-cause analysis and resolution. A manager in charge of prototype ADS-operated vehicle testers should explain to them the organization's specific rules about testing and documentation, as well as any hardware/software updates that impact the performance of the ADS-operated vehicles. Novice testers should be paired with more experienced testers to learn the appropriate reactions in various situations.Real-time calibration/tuning of ADS software during testing should be allowed only after evaluation by qualified personnel (e.g., development engineer, lead calibrator, and/or designated safety engineer), indicating that the change does not pose unacceptable risk for on-road testing.

Automated driving system (ADS) technology and ADS-enabled/operated vehicles - commonly referred to as automated vehicles and autonomous vehicles (AVs) - have the potential to impact the world as significantly as the internal combustion engine. Successful ADS technologies could fundamentally transform the automotive industry, civil planning, the energy sector, and more. Rapid progress is being made in artificial intelligence (AI), which sits at the core of and forms the basis of ADS platforms. Consequently, autonomous capabilities such as those afforded by advanced driver assistance systems (ADAS) and other automation solutions are increasingly becoming available in the marketplace. To achieve highly or fully automated or autonomous capabilities, a major leap forward in the validation of these ADS technologies is required. Without this critical cog, helping to ensure the safety and reliability of these systems and platforms, the full capabilities of ADS technology will not be realized. This paper explores the ADS validation challenge by reviewing existing approaches and examining the effectiveness of those approaches, presenting critical techniques required to bring safe and effective solutions to market, discussing unsettled topics, and suggesting next steps for industry stakeholders to consider as they work to advance the ADS ecosystem. NOTE: SAE EDGE(TM) Research Reports are intended to identify and illuminate key issues in emerging, but still unsettled, technologies of interest to the mobility industry. The goal of SAE EDGE(TM) Research Reports is to stimulate discussion and work in the hope of promoting and speeding resolution of identified issues. SAE EDGE(TM) Research Reports are not intended to resolve the issues they identify or close any topic to further scrutiny.

SAE EDGE Research Reports provide state-of-the-art and state-of-industry examinations of the most significant topics in mobility engineering. SAE EDGE contributors are experts from research, academia, and industry who have come together to explore and define the most critical advancements, challenges, and future direction in areas such as vehicle automation, unmanned aircraft, IoT and connectivity, cybersecurity, advanced propulsion, and advanced manufacturing.

The day will soon come when you will be able to verbally communicate with a vehicle and instruct it to drive to a location. The car will navigate through street traffic and take you to your destination without additional instruction or effort on your part. Today, this scenario is still in the future, but the automotive industry is racing toward the finish line to have automated driving vehicles deployed on our roads. ADAS and Automated Driving: A Practical Approach to Verification and Validation focuses on how automated driving systems (ADS) can be developed from concept to a product on the market for widescale public use. It covers practically viable approaches, methods, and techniques with examples from multiple production programs across different organizations. The author provides an overview of the various Advanced Driver Assistance Systems (ADAS) and ADS currently being developed and installed in vehicles. The technology needed for large-scale production and public use of fully autonomous vehicles is still under development, and the creation of such technology is a highly innovative area of the automotive industry. This text is a comprehensive reference for anyone interested in a career focused on the verification and validation of ADAS and ADS. The examples included in the volume provide the reader foundational knowledge and follow best and proven practices from the industry. Using the information in ADAS and Automated Driving, you can kick start your career in the field of ADAS and ADS.

This document provides preliminary1 safety-relevant guidance for in-vehicle fallback test driver training and for on-road testing of vehicles being operated by prototype conditional, high, and full (Levels 3 to 5) ADS, as defined by SAE J3016. It does not include guidance for evaluating the performance of post-production ADS-equipped vehicles. Moreover, this guidance only addresses testing of ADS-operated vehicles as overseen by in-vehicle fallback test drivers (IFTD).These guidelines do not address: 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.) Closed-course testing. Simulation testing (except for training purposes). Component-level testing.These guidelines also do not address prototype vehicle and IFTD performance data collection and retention. The collection of data invokes various legal and risk management considerations that users of this document should nevertheless bear in mind, such as: 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. This document provides safety-relevant guidance for in-vehicle fallback test driver training and for testing prototype automated driving systems (ADS) equipped on test vehicles operated in mixed-traffic environments on public roads (hereafter, prototype ADS-operated vehicles). This document is being substantially updated in order to incorporate content from Automated Vehicle Safety Consortium (AVSC) publication 00001201911: "AVSC Best Practice for In-Vehicle Fallback Test Driver Selection, Training, and Oversight Procedures for Automated Vehicles Under Test" and to re-classify this document as an SAE Recommended Practice, rather than an SAE Information Report.It is assumed that the prototype ADS-operated vehicles that are the subject of this guidance have been developed using standardized methods for safer product development including, but not limited to: 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).Prototype ADS-operated vehicles that are based on existing production vehicles rely on the existing vehicle's E/E architecture, as adapted for ADS. Prototype ADS technology provided via added hardware and software modules that are not integrated according to the vehicle manufacturer's specifications, should be checked to ensure that they do not interfere with base vehicle hardware or software systems. As such, they should abide by the following general principles: 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.Test program/operations management plays a key role in helping to maintain safety while conducting on-road testing of prototype ADS-operated vehicles. Unexpected behaviors (including incidents) should be reported accurately and consistently for later root-cause analysis and resolution. A manager in charge of prototype ADS-operated vehicle testers should explain to them the organization's specific rules about testing and documentation, as well as any hardware/software updates that impact the performance of the ADS-operated vehicles. Novice testers should be paired with more experienced testers to learn the appropriate reactions in various situations.Real-time calibration/tuning of ADS software during testing should be allowed only after evaluation by qualified personnel (e.g., development engineer, lead calibrator, and/or designated safety engineer), indicating that the change does not pose unacceptable risk for on-road testing.