Formal ODD definition for autonomous truck

[diegoyabuki]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

Formal definition of the ODD for the Autonomous Truck use case.

Purpose

Create the ODD definition document based on the template defined in Phase 1.

Possible approaches

• Given the overlap of modules used in the Truck stack with that of the PoV Vision Pilot, the ODD definition of PoV can be used as a base for the Trucking use case.
• Organize sync meetings with the Truck WG to understand what are the differences in sensors and expected environment to be handled by the autonomy stack.
• Update the base document with the identified changes and merge it to the main branch of the repository.

Definition of done

• The ODD definition document for the Truck use case is created, reviewed and merged into the main branch.

[diegoyabuki]

The Vision Pilot ODD definition document is being adopted as the base for the Truck use case.
The next step is to organize meetings with the Truck WG members to identify potential differences in the application of both stacks.
The development for this task is being handled in the branch https://github.com/autowarefoundation/odd-usecase-scenario/tree/feat/truck-odd-definition.

[diegoyabuki]

An initial alignment was done with the Truck WG on 2026/02/05.
The following was decided:

• Two main use cases shall be considered for the Truck WG: lightweight truck and heavy-duty truck.
• The heavy-duty truck has a lower priority, so an initial ODD draft targeting highway driving is sufficient for now, as a placeholder.
• The lightweight truck will eventually target short distances in metropolitan areas, but the immediate focus is to reuse the models developed by the PoV working group. Therefore, the initial ODD will also start with a focus on the highway use case with eventual expansion once the automation stack reaches maturity.

The following action points on the ODD WG side were also raised in the discussion:

• ODD maintenance responsibility needs to be clarified with Core WG leaders.
• The main purpose of the ODD document shall also be clarified -- is it only for validation, or will it be also input in the design process? Related processes need to be defined.
• The process of updating the ODD definition needs to be clarified.

Next actions:

• @diegoyabuki will create a draft for both use cases of the Truck WG and invite for a round of reviews.

[diegoyabuki]

Created ODD draft for lightweight trucks: Github repo
Created placeholder ODD draft for heavy-duty trucks: Github repo

[diegoyabuki]

Next review sync planned for 2026/03/11 GMT