As “go anywhere” automated vehicles are still a while away, level 3 and level 4 vehicles are much more in reach. For these vehicles we have to define an Operational Design Domain (ODD), e.g. the conditions in which these vehicles are to operate in. This includes weather, road surface and type and a myriad of other factors. This design domain has an impact on the design of the vehicle, its capabilities as well as their respective . For example the ODD and corresponding capabilities for an automated passenger shuttle at an airport would be significantly different to that of an automated logistic shuttle on the open road. validation
To date, there are many ways to describe an Operational Design Domain. This description should be closely coupled with the scenario definitions and the labels given to the scenarios. From the perspective of ASAM it is necessary to define the description mechanisms for such an ODD, namely the format and description guidelines. Furthermore, such a format should be independent of a taxonomy.
The outcome of such an ASAM project could be a format description capable of adapting the already existing approaches from e.g. BSI or . This outcome is expected to be aligned with the other OpenX activities in the ASAM ISO domain. simulation
For questions, please contact nicco.dillmann(at)asam.net
If you would like to be informed about future activites, please subscribe to our newseltter