EGI-Engage:Deliverables and Milestones
Jump to navigation
Jump to search
Deliverables
Milestones
Deliverables
Code | Title | Delivery PM | Description |
---|---|---|---|
D1.1 |
Quality plan for Period 1 (R) |
M03 |
|
D1.2 |
Risk analysis and risk response for Period 1 (R) |
M08 |
|
D1.3 |
Report of quality status and quality plan for Period 2 (R) |
M14 |
|
D1.4 |
Risk analysis and risk response for Period 2 (R) |
M20 |
|
D1.5 |
Report of quality status for Period 2 (R) |
M29 |
Milestones
Milestone | Title | Related WP | Delivery PM | Means of verification |
---|---|---|---|---|
M 1.1 | Execution plan | WP 1 | M02 | Staff for each partner per each task is identified and communicated to the project office, the reporting lines, the project management and governance structures are defined and approved |
M 1.2 | First intermediate report | WP 1 | M08 | A quarterly report describing the status of each activity within the project (M01 – M07) is approved |
M 1.3 | Second intermediate report | WP 1 | M23 | A quarterly report describing the status of each activity within the project (M16 – M22) is approved |
M 2.1 | Website and templates | WP 2 | M01 | Project information is available on the Web and document/presentation templates are defined |
M 2.2 | Technical Forum 2015 is organised | WP 2 | M12 | The event took place and a report is published with the main indicators including user satisfaction |
M 2.3 | The EGI website is reviewed | WP 2 | M13 | The website is reviewed and a number of recommended changes have been applied |
M 2.4 | EGI Service management practices are audited | WP 2 | M15 | EGI service management practices are audited by an external FitSM consultant |
M 2.5 | Technical Forum 2016 is organised | WP 2 | M24 | The event took place and a report is published with the main indicators including user satisfaction |
M 2.6 | The EGI website is reviewed | WP 2 | M25 | The website is reviewed and a number of recommended changes have been applied |
M 2.7 | EGI Service management practices are audited | WP 2 | M29 | EGI service management practices are audited by an external FitSM consultants |
M 3.1 | Operational tools development roadmap agreed | WP 3 | M04 | The operational tools development roadmap is agreed |
M 3.2 | User requirements on data accounting collected | WP 3 | M12 | The user requirements on Data Accounting are agreed and documented |
M 3.3 | Operational tools development roadmap revised | WP 3 | M16 | The operational tools development roadmap is revised and documented |
M 3.4 | Pilot services and best practices to enable federated AAI solutions released | WP 3 | M16 | Pilot services and best practices to enable federated AAI solutions for EGI services are available for the VREs and CCs |
M 3.5 | The first version of the EGI Marketplace is demonstrated | WP 3, WP 2 | M18 | Demo showcased at EGI Technical Forum and made available online |
M 3.6 | The second version of the EGI Marketplace is demonstrated | WP 3, WP 2 | M26 | Demo showcased at EGI Technical Forum and made available online |
M 4.1 | Open Data Platform: requirements and implementation plans | WP 4 | M06 | Final selection of the technologies used to create Open Data Access Platform agreed. The report includes requirements and use cases from selected communities interested in open data |
M 4.2 | Launch of call for cross e-Infrastructure case studies | WP 4 | M15 | A call for participation for cross e-Infrastructure case studies is published |
M 4.3 | Open Data Platform in the Production | WP 4 | M30 | The Open Data Platform is released in the production environment |
M 5.1 | Platform for the long-tail of science is available | WP 5 | M10 | The services to enable easy access to EGI resources are production-ready. |
M 5.2 | e-CEO challenges run on EGI resources | WP 5 | M15 | The e-CEO tool for the ESA data challenge is using also EGI resources to run the data analysis tasks |
M 5.3 | VREs for the fishery and marine sciences community are deployed in production | WP 5 | M18 | Services for the fishery and marine sciences are available and production-ready on EGI resources |
M 6.1 | Joint training program for the first period is agreed | WP 6 | M03 | The plan is defined by the competence centres, the partner e-Infrastructures and partner projects of EGI-Engage |
M 6.2 | Security and privacy requirements and secure storage architectural design are agreed | WP 6 | M06 | Requirements are approved by the BBMRI Research Infrastructure community and the developers of the secure storage solution verified and accepted the design |
M 6.3 | Life science requirements analysis and driver use case(s) with implementation roadmap are agreed | WP 6 | M12 | Requirements are approved by the ELIXIR Research Infrastructure community |
M 6.4 | EPOS requirements analysis and outline of pilot use cases are agreed | WP 6 | M12 | Requirements and pilot use cases are approved by the EPOS Research Infrastructure community |
M 6.5 | Joint training program for the second period is agreed | WP 6 | M15 | The plan is endorsed by the competence centres, the partner e-Infrastructures and partner projects of EGI-Engage |