ASAM Standardization Process
ASAM standards ensure that tools and devices can be freely interconnected and data can be seamlessly exchanged. Standards define protocols, data models, file formats and application programming interfaces for the use in the development and testing of automotive electronic control units and automotive components.
The graphic below illustrates how the development process of an ASAM standard is structured and controlled to ensure highest quality.
How can I initiate the development or revision of a standard?
ASAM members define ideas for a standardization initiative and jointly develop a project proposal. One or several members can propose the development of a new standard or propose a new version of an existing standard. ASAM provides an issue proposal form that asks for the necessary information about the proposal, such as the purpose of the proposal, intended technical content, contributing companies, estimate of work hours and an initial milestone plan. The ASAM office publishes the proposal, asks other members for feedback and recruits further interested member companies for participation. The Technical Steering Committee (TSC) reviews and decides upon the proposal.
Not a member of ASAM? Click here for the benefits.
What are the prerequisites to develop a standard?
At least three companies need to commit their participation by sending a delegate to the project group with sufficient work time.
Who can participate?
Any ASAM member is allowed to send a delegate as a permanent member of the project group as long as the group has not started its work. During the term of a project group, new members can only be accepted by a 2/3-majority vote of the current project group members.
How does the collaboration in project groups work?
The development of standards is being carried out by project groups. The project group elects a project leader who is responsible for organizational and project controlling matters. The ASAM office assigns a maintenance project manager, who is responsible for all maintenance projects and carries out operative work with the project group. Throughout the project term, the project members work on the standard through regular meetings, phone conferences or individual off-line work. Project groups have a lot of leeway to organize themselves in a way that best fits their working style. The ASAM office supports the work via an IT infrastructure, templates and guidelines. Furthermore, ASAM contributes up to 25% of funds of the total project budget to pay for external contract work that supports the development of the standard. The project group reports to the TSC on a regular basis.
What tools are available for project groups?
ASAM provides the work infrastructure for project groups that consists of:
- an issue-tracking system (Bugzilla)
- a file repository and versioning system (Subversion)
- a conference system (Genesys)
- templates (Microsoft Word)
- support via the ASAM office
- on demand: generators for schema-, code- or document generaton
The tools used at ASAM are commonly used in the Automotive industry and most of its members shall already be familiar with them.
For more information on the tools, please see Information for Project Groups
How is a standard released by ASAM?
As soon as the standard is ready for release, the project team submits the standard for review to the Technical Steering Committee (TSC). Work results could be documents, schemata, interface codes, source code or templates. After release approval by the TSC, the ASAM office publishes the new standard version and provides the document for download on the ASAM website.
I found a problem in a standard. What shall I do?
If you found an issue in an ASAM standard, such as a mistake, an ambiguity or an unclear specification, you can report this to ASAM. As a member of a working group, you have access to the ASAM Bugzilla database, which is used for issue and change request tracking. If you do not have access to the database, you can contact the ASAM office via support(at)asam.net and describe the issue. The office will then enter the issue upon your behalf. The same process applies for change requests that propose additions, improvements or new features to an existing standard.