What's the meaning and importance of the Operational Design Domain (ODD) in Connected, Automated Driving (CAD)?

The "Operational Design Domain" (ODD) is a frequently used term in the context of connected, automated driving. What is the meaning of it and why is a clear, machine- and human-understandable definition so important?

The "Operational Design Domain" (ODD) is the set of situations and operating conditions (OCs) for which a system (in this case, a system for connected, automated driving) is decidedly capable and can handle by design.

If you look at this definition strictly mathematically and interpret it in terms of set and measure theory, then the concept of ODD is a very powerful tool in the development, validation, assessment, and release of systems, subsystems and components, especially in automated and connected driving. However, the concepts behind the ODD are generally valid for any automation and control system. For a more detailed and in-depth description and interpretation, reference is made to the basic concepts of scenario management and the ODD paper.

One of the basic prerequisites for this is a (parameterized) description of the situations and operating conditions, so that the possibilities and instruments of set and measure theory can actually be applied. If this succeeds (compare the formal requirements in the ODD paper), then there are a number of use cases with added value for different stakeholders in the topic:

• Developers/suppliers of automated vehicles are given a sharp instrument for approval & acceptance by proving that the ODD covers at least the set of relevant operating and operating conditions.
  A benefit can be demonstrated to customers if the ODD covers a significant range of operating and operating conditions.
• If an operator/user can clearly describe which operating conditions are relevant to them, they can choose a vehicle that best meets their required operating conditions. If the ODD does not excessively exceed the relevant operating conditions, the result is cost-effective and efficient systems tailored to one's own requirements without "over-design".
  The operator and user are thus also able to avoid operating conditions that exceed the ODD and ensure safe operation.
• A regulatory authority has a tool to justify a minimum required set of operating conditions for public transport release by the manufacturer/developer demonstrating that the ODD is a superset of these minimum OCs.

For further, more in-depth details, please refer to the ODD paper.

The importance of the ODD thus does not only include the technocratic proof of system capabilities. If the description is suitable, it also serves to communicate the (necessary) system capabilities between the developers/providers, users/operators and authorities/certifiers.

Especially in the commercial sector, it is possible to find reduced, specific and economic system configurations in which ODD constellations with added value and benefits are already available without demanding the full universality of autonomous driving and having to fulfil all theoretical operating conditions of individual transport.