2nd Consortium Meeting, Edinburgh, 15-16 July 2004

1. Project status update: Work scheduled 3 6 9 12 15 18 D8 D2 D3 D6 D9 Net. Assess. D4 D1 D5 D7 SOA report Intermediate results SOA report Workplan Requir. 2nd CM 1st PR 3rd CM 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

2. Project status update: Work scheduled ‘Width’ WP4 SOA: Data 6.1 ‘Depth’ 6.2 6.3 ‘Width’ WP5 SOA: Tools 6.4 ‘Depth’ WP6 Workplan -> requirements • Elaborate a comprehensive SOA report with limited detail. • Identify ‘gaps’: possible new developments, possible extensions/adaptations. • Elaborate a working plan for pilots --> define requirements at ‘data’ and ‘tools’ levels. • Match requirements with ‘gaps’ to define further work in WP4 and WP5. 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

3. Project status update • Problems found: • Lack of mutual knowledge among partners. • Partners short description distribution, work plan visibility promoted to overcome Consortium ‘forming’ phase. Consortium expected to overcome ‘storming’ phase by month 9. • Too broad scope, lack of focus. Consortium meetings of limited use. • Dynamically applied contingency plans at kick-off (initiation teams) and scientific workshop (SOA reports; requirements) to allow for progressive narrowing of scope and to increase specificity of work to be tackled. • Consortium meetings to be executive, decision-oriented. Scientific discussions to be carried out in activity or WP-specific meetings to be freely arranged. • Lack of understanding of WPL/AL role. Confusion between WPL/AL roles. • Explain again. To be hopefully overcome as the internal review process raises awareness on responsibility and links between decision levels. • Communication not flowing smoothly. Lack of reaction to required information. • Implementation of monthly reports from month 7. Strict effort and budget allocation according to proved contribution. Raising awareness on the dangers of poor communication. • Possible change of reporting method from Leaders to partners? 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

4. Project status update: WPL / AL • From the contract: • WPL will have responsibility for day to day management of specific work related to individual work packages, assisted by the NMO for management, communication and financial matters. WPL will co-ordinate the implementation of the work package activities as defined in the JPA, implement solutions for problems, follow-up and co-ordinate participants involved (internal and external to the Network), produce the corresponding deliverables and deliver them to the NMO, identify risks as early as possible and follow them up, and report the progress achieved against that planned. • AL will co-ordinate the daily work of researchers participating in the activity in a similar way as WPL, but at the activity level. AL will report to the corresponding WPL and contribute to relevant deliverables. Moreover, and especially for activities related to pilot actions, AL will liase with external partners participating in pilot R&D projects, with the support of the NMO. 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

5. Project status update: WPL / AL • MANAGEMENT STRUCTURE Conflict resolution SC NSC Committees Approval Planning NMO Coordination WPL WPL AL AL AL AL Member Member Member Member Member External Work 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

6. Project status update: Communication • We have a tight time schedule, therefore Communication is key. • Communication must be easy and reliable • Email as main tool - distribution lists: technical, administrative? - Always consider distribution through Co-ordinator • Web site - project’s “intranet” repository of documents • Security systems for document exchange - tbd • Communication must be quick • Please respond promptly to any email… • … or at least acknowledge reception! • Communication must be effective • We must ensure there are no relevant issuesfor our work that remain unclear - check minutes and show discrepancies with any operative proposals in a timely fashion! • Use de facto standards for document formats (RTF, PDF) 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

7. R R R R R R R R R R R Project status update: Procedures • EC PROCEDURES Planning (JPA, contract) Payment (50% of budget first 18 months) Annual review (contract update) Cost justification Payment (according to work plan update and justification?) m0 m18 m36 • CONSORTIUM LEVEL Planning (effort -->budget assigned) Committed Planned Payment (70% of budget first 6 months) Internal review Planning (effort -->budget assigned) Committed Planned Payment (30% of budget first 6 months + 70% second six months) 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

8. Project status update: Effort first 6 months 2nd Consortium Meeting, Edinburgh, 15-16 July 2004

9. Project status update: Meeting objectives • Review progress achieved against that planned. Work has to be demonstrable. Results presentation. • Review of effort spent against that planned. Adjustments. • Approve plans for subsequent 6-month period. Discuss strategy/orientation. • Approve effort planned for subsequent 6-month period. • Discuss overall strategy and outstanding issues. Per WP & activity 2nd Consortium Meeting, Edinburgh, 15-16 July 2004