Relationships between artifacts in AWF working groups

[ghost]

Please refer to the material: Relationships between artifacts in AWF.pdf

Related meeting: Open AD Kit WG Meeting 2022/03/24

In the last meeting, we talked about the ConOps and OpsCons of the AWF Bus ODD demo system, and there were some unclear points with regards to relationships between artifacts developed in AWF working groups. This material identifies the relationships, and also clarifies a relationship between the AWF Bus ODD demo system's ConOps and OpsCons and the Open AD Kit version 2.0's ones.

Page 2: relationships between artifacts in AWF

• First, concepts (i.e. the ConOps and OpsCons) are developed to identify how the system will achieve the user's mission and how the system interacts with others, like users and other systems.
• Then, the ConOps and OpsCons will be used as inputs to derive scenarios and hardware and software requirements.
• With regards to developing scenarios, the AWF ODD WG develops scenarios, simulates them, and derives ODDs.
• Other WGs define hardware and software requirements.
• Deriving the ODDs and defining the requirements proceed in cooperating with each other.
• Finally, we can develop the system and perform the demonstration.

This flow is ideal, and current activities, like developing the ConOps&OpsCons and scenarios, are working at the same time. Next time, I hope we will be able to proceed with this ideal process for more efficient work in the AWF.

Page 3: the relationship between the concepts of the Bus ODD demo system and of the Open AD Kit version 2.0

• The ConOps and OpsCons of the AWF Bus ODD demo system defines how the autonomous bus achieves the passenger transportation with the Open AD Kit 2.0 from the *user’s perspective.
• The ConOps and OpsCons of the Open AD Kit version 2.0 describes how the Open AD Kit 2.0 contributes to the software defined vehicle (SDV) development from the **user’s perspective.
  *transportation service operator
  ** SDV developer

Current version of the ConOps and OpsCons of the AWF Bus ODD demo system does not have any information about the Open AD Kit version 2.0. And also the concept of the Open AD Kit version 2.0 is not developed yet. It means that it is difficult for stakeholders to understand how the Open AD Kit version 2.0 contributes to the Bus ODD demo system and bring benefits to users. To overcome the current situation, I'm preparing the draft of the ConOps and OpsCons of the Open AD Kit version 2.0 and I'll post it on the GitHub discussion.

I would appreciate it if you could give me some feedback on it.

[ghost]

Please note that the closing date for comments on this proposal is April 14th.

[ghost]

Now that the scope for Open AD Kit 2.0 has been determined, and there were no objections to the approach suggested above, we can now continue with adoption of a ConOps/OpsCon approach to developing Open AD Kit 2.0.