Call for Offers

Service Provider for P2017-06 MC-3 Automation Access Protocol

Back to overview

Call for Offers:

P2019-03 ASAM OpenDRIVE Transfer Project

ASAM calls for offers to support an ASAM project group for transferring the specification OpenDRIVE to an ASAM public standard. Please send your offers for this project to thomas.thomsen(at)

Offers shall be submitted no later than April 23, 2019.


Change Log 

  • April 09, 2019: Full backward-compatibility to OpenDRIVE 1.5 is not required any longer. However, the new version of ASAM OpenDRIVE shall consider new features of 1.5 and maintain their individual backward-compatibility.



The public 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, the schema 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.

  • Participate at all project group meetings. Travelling to on-site meeting locations in central Europe is required.
  • Provide technical expertise about OpenDRIVE during project group discussions.
  • Assist the project leader in moderating and managing the group, primarily in technical matters.
  • Understand and document meeting results. Implement the results in the standard documentation and model.


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:

  • Introduction, including a description of areas of application for the standard, use-case definitions, and optionally a sub-chapter about limitations and open issues of the current version of the standard.
  • Relation to Other Standards
  • Terms and Definitions
  • Symbols and Abbreviated Terms
  • Bibliography
  • Appendix with figure and table directory

In accordance with the project proposal, this project also includes to clarify open issues and to fill specification 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 the UML 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.

  • Propose and agree with project group members on UML modeling guidelines.
  • Create the UML model from the existing schema-file. Ensure that the model is well formed, is easily readable, easily extensible and complete. Ensure that schema files (XSD) can be generated from the model. If decided so by the project group, annotate the UML model with semantical descriptions.
  • Carry out internal reviews of the documentation and UML model. Implement feedback as decided by the project group.
  • Produce diagrams from the UML model as illustrations for the standard document.


4.    Schema Code-Generation
The schema file(s) shall be automatically generated from the UML model.

  • Setup XSD code-generation.
  • Generate XSD file(s).


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. 

  • Validate the newly generated schema against OpenDRIVE 1.5 and 1.4 schema. The files do not have to look the same. However, both schemata shall have equivalent syntactical and structural rules. Deviations shall have a justification and shall be documented together with transformation rules for transforming old files to new files.
  • Provide beta-versions of the schema files to project group members. Obtain feedback. Implement changes, as decided by the project group.


The deliverables of this project from the service provider constitute the first version of OpenDRIVE from ASAM. 

  • Documentation: Standard and Style Guide
  • UML model
  • XSD schema file(s)
  • Example XODR files and accompanying images of the maps
  • Documented deviations and transformation rules



In order to be able to carry out the tasks, the service provider shall meet the following conditions:

  • Practical work experience in writing standards and technical detail specifications.
  • Good theoretical foundations in data modelling. Skilled and experienced in constructing data models.
  • Expertise in UML modelling, XML, XSD and XSD code generation.
  • Familiarity and practical work experience with Sparx Systems Enterprise Architect.
  • Expertise in mathematical description of geometries, such as spiral lines, cubic polynomials and parametric cubic curves.
  • Experience with OpenDRIVE, road network descriptions and driving simulators would be beneficial.  
  • High proficiency in English on CEFR level C2 in written and spoken language. Ability to guide and moderate technical meetings on this level. Access to a native speaker for editorial reviews of documents would be a plus.
  • Ability to travel to meetings within central Europe (Germany and neighboring countries, incl. UK and Sweden).


General Conditions

Please note the following general conditions for the project.

  • The project period is from April 2019 to October 2019.
  • The service provider must attend all project group meetings.
  • Offers have to be preferably fixed-price. The offer shall itemize the costs for the tasks, as described above.
  • In case of variable-price offers, please indicate upper limits for the costs.
  • In case a deliverable is found to be defective or not up to customary industry quality standards, the service provider will correct the deliverable without charging ASAM for the extra work. Not completed work is exempted from the service provider's warranty, i.e. if a deliverable is found to be incomplete, then its completion will be paid by ASAM. 
  • All work results of the project (including the sources to create them) will be handed over to ASAM and will become the exclusive property of ASAM. If the general terms & conditions of the service provider contain rules that are in conflict herewith, then they must be identified and explicitly declared as invalid for this offer.
  • Offers have to be submitted in writing to ASAM within the above stated bidding period, including a clear description of the provided services and deliverables, terms & conditions, time period and costs for the service.
  • Please note that offers will be reviewed by the members of the project group, the Technical Steering Committee of ASAM and the ASAM Office. The project group members will not receive pricing information. For this purpose, please put all pricing information on a separate page.


Back to overview

Project Details

Read more about the details and scope of the P2019-03 ASAM OpenDRIVE Transfer Project


Learn more

Stay informed! Subscribe to our Newsletter.