Standards List

ASAM OpenODD (Operational Design Domain) is still a very young standardization initiative within the ASAM Simulation domain. The aim is to provide a format that is capable of representing a defined Operational Design Domain for connected automated vehicles (CAV).
An Operational Design Domain Definition (ODD) should be valid throughout the entire operating life of a vehicle and is part of its safety and operational concept. The ODD is used for the functional specification of connected automated vehicles. It specifies what environment parameters (static and dynamic) the CAV must be able to manage. They include all types of traffic participants, the weather conditions, the infrastructure, the location, the time of day and everything else that can have an impact on the driving situation.

ASAM OpenSCENARIO defines a file format for the description of the dynamic content of driving and traffic simulators. The primary use-case of ASAM OpenSCENARIO is to describe complex, synchronized maneuvers that involve multiple entities like vehicles, pedestrians and other traffic participants. The description of a maneuver may be based on driver actions (e.g. performing a lane change) or on trajectories (e.g. derived from a recorded driving maneuver). Other content, such as the description of the ego vehicle, driver appearance, pedestrians, traffic and environment conditions, is included in the standard as well.
The standard describes vehicle maneuvers in a storyboard, which is subdivided in stories, acts and sequences. A story can describe the driving maneuvers of one single vehicle or specify the dynamic behavior of several entities (e.g. vehicles perform a lane change once they reach a specific position). Stories consist of acts, which are triggered when a specific condition is met, such as exceeding a defined speed, reaching a defined distance to a vehicle ahead or going off-road. By using the notion of sequences, the standard allows to define the maneuvers of multiple vehicles in response to that. The maneuver of one car could be a lane change, overtaking another car or driving in a traffic jam while creating a corridor for emergency vehicles. The detailed driving behavior of the vehicle is described via events (i.e. when does it happen?) and actions (i.e. what happens?). Actions may be related to one vehicle and can include speed changes, lane changes or drive to a specified position. Routes and trajectories can be defined that the vehicle shall follow. Actions may also be related to the environment and can include the change of a traffic light or the occurrence of a traffic jam.
Maneuvers, actions, trajectories and other elements can be organized in catalogs and can be parameterized. Additionally, complete scenario descriptions support parameterization, which allows test automation without the need to create a large amount of scenario files.
The data for maneuver descriptions in ASAM OpenSCENARIO is organized in a hierarchical structure and serialized in an XML file format. The schema is provided with the standard. The XML file can be easily validated, edited, imported and exported by simulation tools and content editors. The format is technology and vendor independent.
Maneuver descriptions are an essential part in an effort to test, validate and certify the safety of driver assistance systems and autonomous driving cars. The industry, certification agencies and government authorities jointly work on the definition of maneuver libraries, which can be used to ensure the safe operation of such systems. A publicly developed and vendor-independent standard, such as ASAM OpenSCENARIO, is well suited for this purpose. However, despite the clear and unambiguous maneuver descriptions through a standardized format, it is common understanding that simulation results will not necessarily be the same on different simulators.
The standard is used together with road network descriptions from ASAM OpenDRIVE and can use road surface profiles from ASAM OpenCRG. The three standards complement each other and cover the static and dynamic content of in-the-loop vehicle simulation applications.

ASAM OpenX Ontology shall provide a foundation of common definitions, properties, and relations for central concepts of the ASAM OpenX standards, including OpenDRIVE, OpenSCENARIO, OpenLABEL and others.

This PAS provides requirements for the minimum hierarchical taxonomy for specifying an Operational Design Domain (ODD) to enable the safe deployment of an automated driving system (ADS). The ODD comprises the static and dynamic attributes within which an ADS is designed to function safely.
This PAS is applicable to Level 3 and Level 4 ADS.
This PAS is intended for trialling organizations developing safety cases for automated vehicle trials and testing, manufacturers and developers of Level 3 and Level 4 ADS and suppliers of components and subcomponents.
This PAS is also of interest to insurers, regulators, service providers, and national, local and regional government to enable them to understand possible ADS deployments and capabilities.

This SAE Information Report provides definitions and lexicon for describing operational safety metrics for quantifying the operational safety performance of ADS and ADS-operated vehicles. This document includes a literature review of operational safety metrics that have been proposed and, in some cases, used in previous studies. Characteristics of the identified metrics are listed, and include: 1. Definition, 2. Data Source, 3. Subjectivity (if applicable), 4. Observable Variables, 5. Formulation, 6. Subjective Assumptions and Thresholds, and 7. Origin. The commonalities between metrics are described where applicable, and a set of metrics that will provide input to an operational safety assessment methodology is proposed.

A systematic framework has been created that facilitates the definition of the requirements of simulation models for certain applications and driving manoeuvres in a standardized manner.
For this purpose, the proposed framework systematically divides the vehicle model into model classes and all model classes into different model types, corresponding to various model characteristics and common modelling methods. The vehicle dynamics manoeuvres have been additionally structured and clustered. Manoeuvres can be assigned to model classes and model types using an allocation and requirements table. This document thus also creates the basis for model recommendations relevant to vehicle dynamics with regard to advanced driver assistance systems and automated driving (ADAS/AD).
The application of the framework and the specification of the model requirements are the responsibility of the user. Alternatively, they may be determined by other regulations and standards. This document contains recommendations for selectable model characteristics in terms of adequate simulation quality with respect to performance tests and associated application patterns. The recommendations can be adapted accordingly to be applied to functional testing.

A systematic framework has been created that facilitates the definition of the requirements of simulation models for certain applications and driving manoeuvres in a standardized manner.
For this purpose, the proposed framework systematically divides the vehicle model into model classes and all model classes into different model types, corresponding to various model characteristics and common modelling methods. The vehicle dynamics manoeuvres have been additionally structured and clustered. Manoeuvres can be assigned to model classes and model types using an allocation and requirements table. This document thus also creates the basis for model recommendations relevant to vehicle dynamics with regard to advanced driver assistance systems and automated driving (ADAS/AD).
The application of the framework and the specification of the model requirements are the responsibility of the user. Alternatively, they may be determined by other regulations and standards. This document contains recommendations for selectable model characteristics in terms of adequate simulation quality with respect to performance tests and associated application patterns. The recommendations can be adapted accordingly to be applied to functional testing.

This document enables a structured approach for perception sensor model selection and provides a foundation for consistent sensor model comparison. The model classification is based on reproduced effects of the sensor and its environment as well as the necessary inputs and outputs of the model.
Note: no sign of the work item in the ISO database!

This document specifies a classification framework and terminology of tyre simulation models for automotive development use cases. It builds upon the overall framework defined in ISO 11010-1, which is applicable to vehicle dynamic models. This document focuses on the process of generating the tyre model parameter sets covering the definition of required input data for a certain standard application.
This document enables a structured exchange between tyre model users and tyre model providers to ensure that the tyre model parameter sets is suitable for the intended range of application.
The document provides structured template for the definition of requirements, to be filled in by the model users. It enables the model providers to ensure that all relevant model features are parameterized for the intended operating conditions.
The exchange information serve as additional meta data report for a tyre model parameter set.
Note: no sign of the workitem in the ISO database!!!!

This document specifies a method for comparing computer simulation results from a vehicle mathematical model to test data measured for an existing vehicle undergoing sine with dwell tests that are typically used to evaluate the performance of an electronic stability control (ESC) system. The comparison is made for the purpose of validating the simulation tool for this type of test when applied to variants of the tested vehicle.
It is applicable to passenger cars as defined in ISO 3833.