Service Provider for P2017-06 MC-3 Automation Access Protocol
ASAM calls for offers to support an ASAM project group for transferring the thomas.thomsen(at)asam.net.specification OpenDRIVE to an ASAM public standard. Please send your offers for this project to
Offers shall be submitted no later than April 23, 2019.
Thepublic specification OpenDRIVE is primarily used for the definition of detailed road networks. OpenDRIVE exists since about 10 years and has established itself as the de-facto data exchange file format of road network descriptions for driving and traffic simulators. Members of ASAM have now proposed to transfer the OpenDRIVE specification to ASAM as a public standard.
The goal of this project is to create the first version of ASAM OpenDRIVE in the style of ASAM public standards and by applying advanced specification methods such as UML. This also includes work to complete and enhance the currently existing specification documents, to clarify open issues and to fill specification gaps, which might be brought up by project group members during the project term. The transfer project shall lay a solid foundation for the further development of ASAM OpenDRIVE.
Version 1.5 of OpenDRIVE has already been transferred to the ASAM document template. This is the starting point for the project. Furthermore, theschema file for this version exists, which was manually created and is supposed to match the version 1.5 specification document. There exists also a "Style Guide" document, which shall be transferred to ASAM as well within this project. It is not the intention of this project to add new features or significantly change existing features of OpenDRIVE.
The service provider is primarily responsible for creating additional content of the standard documentation and to enhance existing content. One major tasks of the service provider is furthermore to create the UML model from scratch and to generate the schema file(s) for ASAM OpenDRIVE from this model.
The tasks of the service are broken down into the following sub-tasks:
1. Project Group Meeting Participation and Support
The standardization committee work is mostly done in on-site meetings of the project group, consisting of domain experts for the standard. Some meetings may be carried out remotely via Webex.
2. Write the Standard Documentation
The service provider is the lead author for the standard's documentation during the term of this project. This includes the normative standard document and the informative style guide document.
The content of version 1.5 of OpenDRIVE has already been transferred into the ASAM standards template. ASAM requires some mandatory chapters, which do not exist in version 1.5 and which would have to be written from the beginning. Those chapters are:
In accordance with the project proposal, this project also includes to clarify open issues and to fillspecification gaps, which are brought up by project group members during the project term. The service provider shall incorporate those changes into the standard. Changes shall be backward-compatible to version 1.5. Exceptions to this rule shall be well justified and supported by the majority of the project group. It is not the intention and out-of-scope for this project to add new features or significantly change existing features of OpenDRIVE.
The service provider's work furthermore includes to update the existing XML examples for demonstrating standard-compliant OpenDRIVE-files and to finalize additional examples delivered by project group members. The service provider shall also extract partial XODR-examples (incomplete XML-files, aka "snippets") from the standard and transform them into schema-compliant XML-files.
3. Create the UML Model
The foundation for creating theUML model is the existing schema file and the specification document for OpenDRIVE. ASAM requires backward-compatibility of the newly created schema with OpenDRIVE 1.4 and new features of OpenDRIVE 1.5. So, creating the UML model from the existing schema is mostly a re-engineering task. The exact extent of required backward-compatibility of the newly created schema with its predecessor will be part of the project discussions. The group may decide to deviate from backward-compatibility in well-founded cases. The preferred tool for UML at ASAM is "Enterprise Architect" from Sparx Systems.
4. Schema Code-Generation
The schema file(s) shall be automatically generated from the UML model.
5. Validation of the New Version with Predecessor Versions
The first version of ASAM OpenDRIVE and the newly generated UML data model should be schema backward-compatible with OpenDRIVE versions 1.5 and 1.4. It is not intended to add new features. The new standard might include necessary changes and additions to resolve formerly existing specification gaps or ambiguities.
The deliverables of this project from the service provider constitute the first version of OpenDRIVE from ASAM.
In order to be able to carry out the tasks, the service provider shall meet the following conditions:
Please note the following general conditions for the project.
Read more about the details and scope of the P2019-03 ASAM OpenDRIVE Transfer Project
© 2019 ASAM e.V. All Rights Reserved