1 / 21

Dissemination and exploitation plan, KPIs and next steps

Dissemination and exploitation plan, KPIs and next steps. Internal Review, 25 April 2016. Outline. Catalogue of project results and exploitation plan KPIs N ext steps. Catalogue of project results and exploitation plan. Results and their exploitation.

coralie
Download Presentation

Dissemination and exploitation plan, KPIs and next steps

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. Dissemination and exploitation plan, KPIs and next steps • Internal Review, 25 April 2016

  2. Outline • Catalogue of project results and exploitation plan • KPIs • Next steps Conclusions

  3. Catalogue of project results and exploitation plan

  4. Results and their exploitation • Catalogue of project results and exploitation plan • http://go.egi.eu/egi-engage-results • Project results • Approach • Collection • Identification of Key Exploitable Results • For internal use • For commercial use Conclusions

  5. Identification of Project Results:Methodology • Training WP/task leaders on dissemination and exploitation • Periodic interviews • Analysis of plans for dissemination and exploitation linked to individual deliverables • Selection of relevant results Conclusions

  6. Identification of Project Results Conclusions

  7. Identification of Key Exploitable Results • Exploitation strategy seminar supported by the EC • Analysis performed with WP leaders • Prioritisation and selection • Exploitation: the use of results in • Developing/creating/marketing product/services/processes • Internal use within the EGI federation, EGI partners and/or commercial • Further activities other than project • Standardisation Conclusions

  8. Analysis • 86 results • 12 Key Exploitable Results • 35 different primary owners • 58 technologies integrated Conclusions

  9. List of Key Exploitable Results

  10. KPIs

  11. Key Performance Indicators

  12. Conclusions Next Steps

  13. NA2 Strategy, Policy and Communications • Communications • New reports: Research Infrastructures, Collection of case studies, Impact • Strategy and Governance • Update EGI 2020 Strategy and prepare an EGI impact report • Continue to support the work of the Open Science Policy Platform • Contribute to shaping the future EOSC through the OSPP • Service management • Successfully pass satellite audit to retain ISO9001/ISO20000 certification for EGI Foundation • Manage evolution of the EGI service portfolios • Business models • Focus on transitioning current discussions into concrete business agreements • Terradue, NUMECA, CloudSME, BlueBridge, ELIXIR • Earth Observation DataH • Ensure pay-for-use functionality is included in EGI Marketplace first release • Run webinar for NGIs called “How to engage SMEs/Industry” • Exploitation • Finalise the list of Key Exploitable Results for the project and for the EOSC Conclusions

  14. SA1 Operations TSA1.1: • Finalize the deployment in production of storage accounting • Ensure that the outputs of the JRA1 and JRA2 are deployed in production following the operational procedures • Further improve the quality of the cloud services with more uniform configuration and access workflows • Release CMD middleware for Open Nebula and complete the coverage of federated cloud software TSA1.2: • Review in detail more security threats identified in the risks assessment • Provide to SA1.1 the requirements to implement the mitigations for the most critical security risks • Finalize the review of all the incident response documentation where necessary based on the results • Run the Site Security Challenge and update the incident response documentation based on the results • Push Cloud-related security topics in the agenda of cross-infrastructure security initiatives TSA1.3 • Open LTOS for beta testing • Run ESA TEP and iMarine use cases in production and support their operations Conclusions

  15. SA2 Knowledge Commons • SA2.1: Training • Cloud tutorials at summer schools • RDA-ENVRIplusSummer School, EUDAT Summer School, CODATA-RDA Research Data Science Summer School • Applications On Demand Platform tutorial for NGIs • Further expansion of training portfolio • INDIGO solutions (Orchestration) • Improved/expanded Open Data Platform and DataHub tutorials • Support demonstrations and ‘small-group’ tutorials of CCs • SA2.2: Technical user support • Follow-up active use cases – focus on RIs: EMSOdev, ICOS, DANUBIUS, etc. • ‘Long-tail support’ • Applications on demand platform • Web service request form • Engage with additional communities • New opportunities from EOSCpilot demonstrators and EOSC-hub call (CCs, business pilots) Conclusions

  16. JRA1 – e-InfrastructureCommons 1/2 • TJRA1.1 - AAI • Finalisation of the LoAsupport • Finalisation of VO membership information connectors • Finalisation of OIDC client management UI • Integration of new SPs (including EGI tools and services – e.g. FedCloud) • TJRA1.2 & TJRA1.5 – Marketplace & e-GRANT • Move the prototype to pre-operations (beta) • Integration with the Application on demand platform • Customer dashboard • Orders registration • Term of reference Conclusions

  17. JRA1 – e-InfrastructureCommons2/2 • TJRA1.3 – Accounting • Second data accounting prototype • Support for accounting of long running VMs • New release of the portal • API to gather accounting data • New cloud view • Integration with CheckIn • Migration to the new messaging infrastructure • TJRA1.4 – Operations tools • Ops Portal: Integration with CheckIn and migration to the new messaging infra • GOCDB: writable REST API extension and GUI improvement • ARGO: probes management, integration with CheckIn and migration to the new messaging • Messaging: HTTP messaging service in production • Security Monitoring: automatic framework for VM image assessment integrated with AppDB. Conclusions

  18. JRA2.1Open Data Platform JRA2.1 • Improvement of Onedata scalability in terms of collection size and simultaneous users • Integration of further storage providers to the EGI DataHub • Provision of additional open data collections via EGI DataHub Conclusions

  19. JRA2.2Federated Cloud JRA2.2 • OCCI • Implement an ooi standalone service -> decouple from nova-api service • Integrate ooi in the OpenStack • FinaliseSynnefoimplementation • Authentication • Keystone: Move from V3 while maintaining V2 support • Accounting • Implement new version of accounting record to ease computation of long-running VMs. • CloudKeeper • Implement additional CMF modules • Information System • Finalize GLUE 2.1 implementation Conclusions

  20. JRA2.3, JRA2.4 JRA2.3 e-Infrastructure Integration • Complete EGI CheckIn based integration for OpenStack • Develop technical integration plan for commercial providers JRA2.4 Accelerated Computing • Support for accounting of GPGPU • Work with the STFC APEL team. The format of the accounting records needs to be finalized. • Support for publishing GPGPU information • GPGPU attributes has been added to GLUE 2.1 schema, but this needs to be deployed across the relevant FedCloud sites Conclusions

More Related