Consider a conversation with your best friend explaining a dangerous situation you faced on the freeway earlier that day. You would probably tell them where, when and how it happened — in general. Plus, you’d include your version of what the traffic was like and how the other driver(s) behaved. This conversation would likely imply things that were not specifically mentioned, about traffic lanes, vehicle dynamics and the like.
Yet, even if you were able to explicitly account for these conditions, the description would still be a far cry from a simulation executable example. And the actual creation of such scenario descriptions is tedious and repetitive. Indeed, to create autonomous vehicle solutions, carmakers need to test against hundreds of thousands of scenarios (specified in textual form) and identify crucial combinations or gaps to ensure a sophisticated enough scenario coverage of the ODD¹.
On top of that, interdisciplinary teams have to work together for scenario specification — testing and debugging to avoid ambiguities. These activities are time consuming, will likely cause delays in product development and require deep domain knowledge. All this at a time when well-qualified experts are difficult to find.
To address the process of scenario specification and enable alignment across teams and organizations, the industry has accepted standards all developed by ASAM e.V.’s cross-industry initiative, such as ASAM OpenDRIVE®, ASAM OpenSCENARIO® DSL and ASAM OpenSCENARIO® XML.
And to manage the lack of qualified experts, large language models (LLMs) and generative AI are now mature enough to be used as a universal, scalable extension of labor forces.