Automated driving system safety measurement part I :

Abstract

The safety of Automated Driving System (ADS) equipped vehicles and reliable methods for assessing that safety are critical for public acceptance of these engineered systems. This document presents a novel approach for developing an ADS safety measurement methodology, which came from the NIST Automated Driving System Safety Measurement (ADSSM) Technical Working Group. This document presents the concept of an Operating Envelope Specification (OES), a structured description of environmental factors or aspects that an ADS may encounter during operation and relates it to the Operational Design Domain (ODD) of ADS-equipped vehicles.Reasoning about the operating conditions of an ADS-equipped vehicle, using OES and during relevant scenarios or other modalities of test, can be classified as relating to specific engineering concerns such as functional, communications, or trustworthiness concerns and for purposes of providing an assurance case for each concern. One such classification is provided by the NIST Framework for Cyber-Physical Systems (CPS Framework) [1]. The CPS Framework provides a set of engineering concerns that can be used to sort or classify constraints on system behaviors, such as those provided by regulation or roadway design or those determined during system development. This methodology will be presented in future work.

Overview of the Operational Design Domain Monitoring for Safe Intelligent Vehicle Navigation

“…Attribute combinations associated with high risk are removed from the initial permissive ODD. In a NIST publication [27], the idea of measurable OD representation is developed through what they call an Operating Envelope Specification (OES). It focuses on the operational safety side of the ODD, with OD reasoning against and ODD (OD monitoring), but do not detail about how is should be done and formalized.…”

Autonomous Vehicle Emergency Obstacle Avoidance Maneuver Framework at Highway Speeds

“…The warnings can also be used to activate pre-collision safety measures, such as occupant safety belt pre-tensioners, airbag arming, and increased seat side and leg bolstering [33,34]. This EOAM framework should also embrace operational design domain (ODD) and dynamic driving task (DDT)-based architecture [28][29][30][31] that allows for specific domains to take care of unique tasks that occur less frequently than normal driving conditions; one of the domains could manage emergency maneuvers involving large-magnitude lateral dynamics with low processing and execution times.…”