ASAM OpenSCENARIO V2.0

3. OpenSCENARIO Alignment & Looking Forward

A first outline of the plan for OpenSCENARIO looking into the mid to long term: What is ASAM doing to ensure the two development pipelines of 1.x and 2.0 converge in the future.

4. Summary :  ASAM OpenSCENARIO Concept Project

High level summary of the predecessor project

5.1. Technical Summary: Use Cases

A technical overview of the use cases and user stories defined in the 2.0 concept project

5.2. Technical Summary: Domain Model

A technical overview of the domain model and entities defined in the 2.0 concept project

5.3. Technical Summary: Language Concepts

A technical overview of the language concepts defined in the 2.0 concept project

5.4. Technical Summary: Measurement & Success Criteria

A brief technical summary of the concepts for observers and KPIs to evaluate scenarios, actors and code defined in the 2.0 concept project. This will be presented in more detail at a later date in the project

6. Proposal: A Modular Extendable OpenSCENARIO  

As OpenSCENARIO 2.0 is intended to have a very large scope it will not be implementable all at once by tool vendors. This proposal is to split OpenSCENARIO 2.0 into modular components possibly separated by featureset. Such a split would allow tool vendors to incrementally add support for OpenSCENARIO features as well as making it very clear what is supported and what isn’t.
→ Michael Kluge will prepare some text for this to include in the project proposal. This will include some examples of how a modular separation by featureset could work.

7. ASAM Contribution Workflow

• Some insights into how to contribute to the project proposal
• Getting setup with git and a text editor
• How to submit changes to the project proposal

8. Split discussion panels

Interactive sessions separated by workgroup to refine the technical content

• Start discussing the "how to implement"
• Goal: V2.0.0 release in Q2 2021
• Expected outcome: Action plan to progress from concept to standard (for each domain)

9.1. Enrollment

To enroll in the project, enter your details and resource committments (we recommend 25 man-days per company) in 3-2_committed_resources.adoc

9.2. Nomination of a Project Lead

A project leader will be elected in the final proposal meeting at the end of April. 
Tasks of the project leader:

• Coordination of the project group (meetings, technical content, milestone management)
• Interface between project and ASAM TSC (status updates, releases)
• (optional) Interface between project and ASAM Coordination Group:Simulation (alignment with other standards and activities). This can also be fulfilled by another project representative.

Submit of your candidacy for project lead by Apr 17, 2020:

• Email a short summary of your profile (1-2 slides) to benjamin.engel(at)asam.net (will be shared with the public for voting of the project lead)
• Each company committing resources has one vote (outliers that have significantly more or less commitment than others will be weighted accordingly - the details of this will be shared prior to the vote)
• The project will not be able to start until a project lead is defined.

Candidate to date: 

Gil Amid (Foretellix)

9.3. Nomination of the Change Control Board (CCB)

CCB members are effectively repository moderators with the necessary permissions on the OpenSCENARIO repository to:

• Push content to the protected project branches
• Accept merge requests from other project members

To nominate yourself as a moderator, please enter your details in Table 2 of 3-2_committed_resources.adoc

Candidates to date:

• Pierre Mai (PMSF)
• Luca Costantino (ANSYS)

Note: A minimum of two volunteers are expected to be named in the project proposal. The volunteers can change over the project runtime but 2 are always required.

9.4. Next Meetings

1. Full proposal group meeting to finalize the project proposal end of April (Date TBD and will be shared over ASAM Channels and with all registered participants of this workshop)

   • Final resource commitments by participants are expected by this meeting

   • Voting on repository administrators

   • Voting on Project Lead

2. Individual Workgroup meetings to continue refining list of issues in the coming 2-3 weeks

3. Additional Workgroup meeting for Usage and Pragmatics Workgroup in the coming week to continue assignments for the project propsal → These meetings will be shared with all as soon as they are created (early next week)