PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

Final Report PRE-DRIVE C2X 29.9.2010
Conflicts with non-performing partners such as INRETS were handled very
effectively, and a good solution was worked out which all the remaining partners
supported. The former partner announced their withdrawal from the project and did
not claim any funding. The work allocated to INRETS was reallocated to partners
who were willing to take over parts of those tasks.
In M07 one of the project management partners had to withdraw from the
consortium. The remaining partners redistributed the responsibilities, tasks and
resources and managed successfully to handle the required tasks.
A delay was caused in WP3000 when milestone MS3 “Functionally verified
prototype system available” could not be achieved in time as the development of the
software components was delayed. This had direct impact on WP5000, which was
highly dependent on WP3000 because WP3000 was delivering the software and
hardware components necessary for test demonstration. However, setting strict
deadlines and installing a joint task force for testing and demonstration consisting of
members of WP3000 and 5000 has helped considerably to overcome these
problems. All hardware and software components were available well in time
according to the new project plan.
As challenges were identified early due to effective internal controlling and steering
processes, they could be solved successfully.
However, the fact that the Consortium Agreement was still not agreed and signed
by all partners by M25 surely is a learning experience and countermeasures will be
implemented at coordinators side and on the side of the consortium to avoid this for
future projects.
4.4 Use of resources
4.4.1 Human resources for all partners
Figure 65: Human resources for all partners
Deliverable D0.3 Version 1.0 94
Final Report