Back to overview
Call for Offers:
P2019-01 ASAM OpenSCENARIO Transfer Project
ASAM calls for offers to support an ASAM project group for transferring the OpenSCENARIO to an ASAM public specification. Please send your offers for this project to standardthomas.thomsen(at)asam.net.
Offers shall be submitted no later than April 14, 2019.
The goal of this transfer project is to create the first version of ASAM OpenSCENARIO on a quality- and completeness-level that is expected from a public and from ASAM members. This also includes work on a technical level to complete and enhance the currently existing standard documents, to clarify open issues and to fill specification gaps, which might be brought up by project group members during the project term. specification
The transfer project shall lay a solid foundation for its further development of ASAM OpenSCENARIO. It is not the intention of this project to add new features or significantly change existing features of OpenSCENARIO.
The service provider is primarily responsible for creating the documentation (MS Word documents), the standard model and the UML files for ASAM OpenSCENARIO. The latter shall be automatically generated from the schema model to guaranty consistency between the UML and standard. schema
The current documentation of OpenSCENARIO primarily consist of a public mindmap and files. OpenSCENARIO is currently not documented in a style and technical detail-level as know from public standards. The original authors have created an online Wiki page ( schemahttps://tracking.vires.com/projects/openscenario/wiki/User_Manual, registration required), which can serve as a starting point for writing the documentation. So, the service provider has a crucial role in this project, since he is setting up the standard documentation for an ASAM standard from the beginning. standard
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 . Some meetings may be carried out remotely via WebEx. standard
- Participate at all project group meetings. Travelling to on-site meeting locations in central Europe is required.
- Provide technical expertise about OpenSCENARIO 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 and model.
2. Write the Standard Documentation
In accordance with the project proposal, a "User's Guide" and a "Programmer's Guide" shall be written. It is current understanding that the "User's Guide" is manually created (i.e. written) by the service provider. Most of the content of the "Programmer's Guide" shall be automatically generated from the model. Depending on the project progress, the partitioning and creation of content for both documents might change, as per project group decision. UML
- Write the User's Guide. The document currently does not exist, so it is created from scratch. ASAM provides a document template as a starting point. Some content already exists in an online Wiki (see link above), which is another starting point. Writing the document also includes an introduction, description of use-cases and requirements, relations to other standards, a glossary, and other formal chapters.
- Create the Programmer's Guide: The documentation is mostly auto-generated from the UML-model. Some additional text may be manually written for this document.
- Create final versions of XML example files for demonstrating standard-compliant OpenSCENARIO-files based on input from the project group.
- Carry out internal reviews. Implement feedback as decided by the project group.
3. Create the UML Model
The foundation for creating the model are the existing UML files for OpenSCENARIO. The exact extent of required backward-compatibility of the newly created schema with its predecessor will be part of the project discussions, aided by input from the service provider. So, while creating the schema model from the existing UML is mostly a re-engineering task, input on useful improvements to the schema, which might break backward-compatibility from the service provider is solicited and should be provided. The preferred tool for schema at ASAM is "Enterprise Architect" from Sparx Systems. UML
- Propose and agree with project group members on UML modeling guidelines.
- Create the UML model from the existing schema files. Consider the mind-map and Wiki. 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. Annotate the UML model with semantical descriptions as provided by the project group.
- Propose improvements to the UML model in terms of harmonization with ASAM common content, and improved modeling quality.
- Produce diagrams from the UML model as illustrations for the User's Guide.
4. Schema Code-Generation
The files shall be automatically generated from the schema model. UML
- Setup XSD code-generation.
- Generate XSD files.
5. Validation of the New Standard with the Predecessor Version
The first version of ASAM OpenSCENARIO should be backward-compatible with its predecessor version, except for agreed upon changes. It is not intended to add new features. The new schema might include necessary changes and additions to resolve formerly existing errors, standard gaps or ambiguities. specification
- Validate the newly generated schema against the predecessor 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 OpenSCENARIO from ASAM.
- Standard documentation, i.e. "User's Guide" and "Programmer's Guide"
- UML model
- XSD schema files
- Example XOSC files
- 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.
- Experience with OpenSCENARIO, vehicle maneuver 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).
Please note the following general conditions for the project.
- The project period is from April 2019 to December 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