Search Results

Per SAE J3016 (2021), the Operational Design Domain (ODD) for a driving automation system is defined as “Operating conditions under which a given driving automation system, or feature thereof, is specifically designed to function, including, but not limited to, environmental, geographical, and time-of-day restrictions, and/or the requisite presence or absence of certain traffic or roadway characteristics.”; in short the ODD defines the limits within which the driving automation system is designed to operate, and as such, will only operate when the parameters described within the ODD are satisfied.. This information Report serves to provide terminology, definitions and taxonomy for use in describing an ODD and respective elements for a driving automation system. This classification and definition of a harmonized set of ODD elements is based on the collection and analysis of existing information from multiple sources.

This document is a list with definitions of terms and taxonomies related to ADS V&V.

This document will provide a compendium of resources, ordered by type of disability (including combinations thereof), for engineers to use in the design and development of ADS-DV interfaces, safety systems, and mobility accommodations. These resources will range from documents issued by standards-development organizations, to relevant research reports, and the published results of expert interviews and focus groups conducted with persons with disabilities. It will also consider pre- and pick-up considerations, as well as drop-off and post-drop off considerations.

The terms and definitions in this document describe the functions performed within an ADS, as defined in SAE J3016. Where possible we have attempted to capture the language that is already in use within the automated driving development community. Where needed, we have added new terms and definitions, including clarifying notes to avoid ambiguity. SAE J3131 deals primarily with Level 4 and Level 5 ADS features.

This SAE Recommended Practice provides definitions, taxonomy, and characteristics for DA metrics used to quantify the driving performance of ADS-operated vehicles. Here, the primary focus is on the safety-related driving performance, which is considered to be related to completion of the dynamic driving task (DDT) . Driving performance is a subset of overall operational performance of ADS-operated vehicles. Thus, assessments of cybersecurity, maintenance, interactions with passengers, etc., while important, are out of scope for this document. Note that the DA metrics do not specify the actions and/or maneuvers to be executed by the subject vehicle. A literature review of DA metrics that have been proposed and, in some cases, used in previous studies was conducted. From this literature review, a set of DA metrics has been created with example usage. Evidence of prior research indicating that a metric has a relationship with safety outcome(s) is included where applicable.

This document describes best practices for developing and validating simulations in support of ADS for on-road motor vehicles, as well as validation of ADS models. However, this document will not address the various approaches and considerations for developing an ADS model as this topic is addressed primarily in SAE J2998. Similarly, this document will not specify types of simulations needed for a given system as this is dependent on the system developer as well as simulations where the ADS model (or parts thereof) can be utilized but are not the system under test. Conversely, this Information Report describes best practices related to taxonomies of ADS simulations (e.g., driver-in-the-loop, vehicle-in-the-loop, hardware-in-the-loop, etc.). In addition, ADS simulations referenced within this document can be utilized during different phases of a systems engineering lifecycle or product development lifecycle (e.g., design, development, testing, production, operations, maintenance).

This SAE Recommended Practice provides guidance for test facilities in identifying potential hazards, and safety risks, along with requirements and recommendations related specifically to testing of automated driving systems (ADS) and ADS-operated vehicles. Herein after, for the purposes of this document, utilization of the term “test facilities” implies those conducting testing of ADS or ADS-operated vehicles, unless otherwise noted. References made to safety within this recommended practice apply only to test method safety and driving safety on and during testing at an ADS test facility and do not apply to vehicle design or safety performance. Safety practices for on-road testing, operation, and related deployment are not covered within this document.

Expanded scope: This document provides safety-relevant guidance for the public road testing of prototype level ADS-operated vehicles encompassing safety management planning for the vehicle, vehicle operations and the organization. Included within the planning will be in-vehicle/remote fallback test driver selection and training, operational safety metrics, emergency action planning, interaction with First/Second Responders and hazard identification and risk mitigation. Original J3018 scope:This document provides preliminary 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.

This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways:Level 0: No Driving AutomationLevel 1: Driver AssistanceLevel 2: Partial Driving AutomationLevel 3: Conditional Driving AutomationLevel 4: High Driving AutomationLevel 5: Full Driving AutomationThese level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner.