1 / 10

WP8 - Project Management

WP8 - Project Management. 3 rd Amendment formalised Budget transfer request Time extension request (three months) 2 nd Cost Statement analysis in progress Bank transfer after the signature of the 3 rd Amendment Bank details from the Partners needed

lynley
Download Presentation

WP8 - Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP8 - Project Management • 3rd Amendment formalised • Budget transfer request • Time extension request (three months) • 2nd Cost Statement analysis in progress • Bank transfer after the signature of the 3rd Amendment • Bank details from the Partners needed • Read carefully EC comments (when available) for Final Cost Statement

  2. WP8 - Project Management • Two paper copies of the 3rd Amendment have been delivered to you today • Please mail by express courier the two copies duly signed by the authorised person and not dated, together with an accompanying letter where you declare: “We certify that we have not made any changes or alterations to the contract”

  3. WP8 - Project Management • Reporting • 9th QMR submitted on 03 February 2004 • 10th QMR (January – March 2004) in progress • Effort  actual vs. planned • Current figures compliant with the budget for all the Partners but EDC • Minor budget adjustments (transfer between different cost figures  20% budget) at the end of the project

  4. WP8 - Project Management Man-hours available to complete project activities UGDIE 394 h SCIRO 653 h IVU 575 h EDC – 20 h NTUA 1295 h SIGMA 420 h CP 560 h PI 386 h TOTAL 4263 h Cumulative effort to 31 March 2004

  5. Project completion – Milestone M5 on 30 September 2004 Deliverable D13 – Deliverable D15 – Deliverable D16 on 30 September 2004 WP4 completion – Milestone M4 – Deliverable D10 on 30 June 2004 WP5 completion – Deliverable D11.2 on 31 July 2004 WP8 - Project deadlines

  6. Mandatory deadlines

  7. Conclusions (1 of 4) • D10 – F-MAN functional prototype is set as “Prototype”. This means that the report to be issued by IVU should be regarded as an accompanying documentation to the SW tools (the same concept already applied for D7, D8 and D9). • D11.2 – Verification Report represents to date the bottle neck for D13 –Evaluation Results and both are highly strategic as far as the Final Review is concerned. Mandatory is the deadline set on July 31st for CP. • D13 – Evaluation results will be issued on the basis of the feedback from the on-the-field tests and the ROG. In such a context a final ROG meeting will have to be planned before the end of July.

  8. Conclusions (2 of 4) • D15 – Technological Implementation Plan will be prepared on the basis of the information provided by the whole partnership. The template to be adopted by each company will be provided in May and the feedback from each partner will have to be ready no later than June 30th. Such deadline is mandatory as the TIP will have to be submitted electronically by the Coordinator through the CORDIS Web site filling in the tables there available by a not trivial cut&paste procedure. • D16 – Final Report will have to collect the results/information deriving from all the Work Packages (technical and administrative) and so it will be possible to complete the document only once the activities will be fully over.

  9. Conclusions (3 of 4) • The redundant use of the term “mandatory” is only connected with the Damocle’s sword represented by the on-site Final Review. • As required by the PO, the Consortium has to propose when and where the review could be held and NO MODIFICATIONS will be allowed once the proposal will be accepted. • On that occasion the Consortium will have to give evidence of the full compliance between the expected and the actual achievements and the success of F-MAN will be based on what we will be able to transfer to the Reviewers in a very limited lap of time. • This means that a lot of preparatory activities will be needed in order to prepare a clear and effective presentation of the project results and the “F-MAN Demonstrator in action”.

  10. Conclusions (4 of 4) • Taking into account the previous considerations, a tentative date for the on-site Final Review could be planned for the end of November 2004. • This could allow the Coordinators to: • Provide the Reviewers with the overall project documentation according to the required procedures (at least one month before the meeting) • Coordinate and harmonise the presentation, included the delicate matters concerning the “F-MAN Demonstrator in action” IT IS EVIDENT THAT TO MAKE THIS PROPOSAL FEASIBLE, PROJECT ACTIVITIES SHOULD BE COMPLETED WITHIN THE SCHEDULED DEADLINES

More Related