Project Proposals

We have started enrollment for "Cross-channel object referencing with ASAM OSI trace files and ASAM OpenLABEL labels" - Enroll by Sep 21, 2026

ENROLL

All ASAM OpenX are currently in maintenance mode where small changes are constantly being implemented. To see, what is currently going on, to submit a change request and to participate in the development, please see the links below:

ASAM OpenX Proposals        Enroll here         Project calendar

This new A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard development approach aims to be more open, flexible, transparent, and collaborative. The key corner stones of this process are as follows: 

1. Proposal Submission:
   Anyone (members and non-members) can submit ideas, change requests, bug reports, and feature requests via GitLab   and link to relevant technical discussions. 
2. Proposal Review & Approval:
   We have installed a Change Control Board (CCB) for an initial assessment of new projects as well as a Coordination Group for alignments across different standards within the Simulation domain. The final approval remains with the Technical Steering Committee (TSC).
3. Project Development:
   Projects are designed to be shorter and more focused, addressing specific use cases, features or small maintenance fixes. Project participation is still requiring ASAM membership.
4. Standard release process: 
   When a project is feature-complete, it is shared with domain experts (sign up here   select 'Simulation') for review and submitted to the CCB for approval. When the CCB approves the developments, a project ends and the content is assigned to a release milestone for integration into the next release of the standard(s) it affects.
   When the CCB decides to release a new version, all assigned features are integrated into the release candidate. The release candidate then undergoes the regular public review process (rules of the regular development process apply) before it is finally approved by first the CCB, then the TSC.

With this new process, we expect standards development to become faster, foster stronger industry alignment, and increase collaboration. Additionally, this process shall encourage solution-driven proposals that reach across standards.

All stakeholders are invited to get involved: submit proposals, join the discussions, and track milestones.

Get more details on the process