Evrest-project
Project schedule

E V R E S T Project Schedule

Electric Vehicle with Range Extender as a Sustainable Technology. The schedule shows the sequence of phases, the key milestones and the points at which decisions are taken.

Phases of the project

The project runs in sequential phases with overlaps where work packages depend on each other. Timings are expressed as project months so that the plan stays valid even if the official start date changes.

Months 1 to 6

Requirements and architecture

Vehicle requirements, duty cycles and the reference architecture are defined and agreed by all partners.

Months 7 to 18

Component development

The range extender, battery system and power electronics are designed, built and tested individually.

Months 19 to 30

Integration

Components are combined into a complete drivetrain and the energy management strategy is calibrated.

Months 31 to 40

Validation and evaluation

Test campaigns measure energy use, emissions and range against the targets defined at the start.

Months 41 to 48

Dissemination and closure

Final results are reported, shared with stakeholders and prepared for future exploitation.

Key milestones

Milestones mark the points where the project confirms that a phase has delivered its intended results. Passing a milestone allows the next phase to start with agreed inputs.

  • Architecture freeze after the requirements review
  • Prototype range extender accepted for integration
  • First complete vehicle running on the test rig
  • Final validation report approved by the consortium
Milestone-driven plan
Engineers reviewing a project plan

Testing and evaluation periods

Test activities are scheduled around the availability of prototypes and laboratory facilities. The images below show typical stages of the testing process.

Managing schedule risks

Each phase has identified risks and contingency actions. The schedule is reviewed at every reporting period.

If a prototype part arrives late, partners adjust the test sequence so that independent work can continue while the affected item is pending.

Integration tasks depend on finished components. Interface specifications are frozen early so that component teams can work in parallel.

Changes are documented, assessed for their effect on the milestones and approved through the project governance before they are applied.

Review the work packages

The schedule is built on the work package structure. Read how each package contributes to the overall plan.

Explore the work packages