Dissemination and exploitation plan KPIs and next steps





















- Slides: 21
Dissemination and exploitation plan, KPIs and next steps Internal Review, 25 April 2016 www. egi. eu This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.
Outline • Catalogue of project results and exploitation plan • KPIs • Next steps 2/14/2022 Conclusions 2
Catalogue of project results and exploitation plan www. egi. eu This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.
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 2/14/2022 Conclusions 4
Identification of Project Results: Methodology 1. Training WP/task leaders on dissemination and exploitation 2. Periodic interviews 3. Analysis of plans for dissemination and exploitation linked to individual deliverables 4. Selection of relevant results 2/14/2022 Conclusions 5
Identification of Project Results General info • Name of the task/activity generating the output • Leading organisation • Contact person • Category • Result Name • Description • Status 2/14/2022 Exploitation info • Target Group(s) • How they will use the results (category) • How they will use the results (description) • IP protection approach • More information on IP protection • Concrete actions to make the results exploitable by the target groups • URL to project result Conclusions Dissemination info • Channels • Concrete actions to disseminate the availability of results to the target groups 6
Identification of Key Exploitable Results 1. 2. 3. Exploitation strategy seminar supported by the EC Analysis performed with WP leaders Prioritisation and selection Identification • Identify relevance for Project • Identify relevance for Policy domains as EOSC Characterization • Aggregation of project results • Analysis of Innovativeness Prioritization • Criteria: • Innovation • Exploitability • Impact 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 2/14/2022 Conclusions 7
Analysis • • 86 results 12 Key Exploitable Results 35 different primary owners 58 technologies integrated % EGI-Engage project results WP 6; 20 WP 2; 24 WP 5; 7 WP 3; 12 WP 4; 21 2/14/2022 Conclusions 8
List of Key Exploitable Results Category Name Commercial Exploitation Software and Services EGI service portfolio Software and Services Integrated services from collaborating partners Policies, Processes and Procedures Strategy, Planning and Evaluation Business Model Innovation Business Engagement Program and collaborations Software and Services Service Integration and Management, ISO certification Software and Services Federated Authentication & Authorisation ✓ Software and Services EGI Data. Hub ✓ Software and Services Federated Cloud Computing ✓ Stakeholder Engagement Established Competence Centres Policies, Processes and Procedures Security Policies Business Model Innovation Procurement study 2/14/2022 Know-How Training Programs ✓ ✓ 9
KPIs www. egi. eu This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.
Key Performance Indicators KPI no. Indicator Project Objective Cumulative / average / … KPI. 2. SA 1. Integration Number of RIs and e-Infrastructures integrated with EGI O 5 Cumulative KPI. 3. SA 1. Software Number of new registered software items and VM appliances O 3 Per period KPI. 4. SA 1. Cloud Number of providers offering compute and storage capacity accessible through open standard interfaces O 3 Cumulative KPI. 5. SA 2. Users Estimated total number of researchers served by EGI O 1 Cumulative KPI. 7. SA 2. Users Number of new research communities served O 2 Per period KPI. 8. SA 1. Users Number of VO SLAs established and number of long tail of science SLA (num 1/num 2) O 2 Cumulative KPI. 16. SA 2. Support Number of international support cases (for/with RIs, projects, industry) O 5 Cumulative KPI. 18. NA 2. Industry (New) Number of SME/Industry that successfully implemented a use case involving EGI services O 4 Cumulative KPI. 19. NA 2. Partnerships 2/14/2022 (New) Number of Paa. S providers that are EGI partners: EGI Marketplace partners/Technology partners (num 1/num 2) O 2 Value PY 1 15 Value PY 2 17 Target M 24 13 19 Software, 12 Software, 62 VA 29 VA 30 Software, 90 VA 21 24 25 46, 250 50, 700 48, 000 18 23 20 3/0 10 / 100 38 63 30 - 4 2 - 27 20 Cumulative 11
Next Steps www. egi. eu Conclusions This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.
NA 2 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 ISO 9001/ISO 20000 certification for EGI Foundation – Manage evolution of the EGI service portfolios • Business models – Focus on transitioning current discussions into concrete business agreements • Terradue, NUMECA, Cloud. SME, Blue. Bridge, ELIXIR – Earth Observation Data. H – 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 2/14/2022 Conclusions 13
SA 1 Operations TSA 1. 1: • Finalize the deployment in production of storage accounting • Ensure that the outputs of the JRA 1 and JRA 2 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 TSA 1. 2: • Review in detail more security threats identified in the risks assessment • Provide to SA 1. 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 TSA 1. 3 • Open LTOS for beta testing • Run ESA TEP and i. Marine use cases in production and support their operations 2/14/2022 Conclusions 14
SA 2 Knowledge Commons • SA 2. 1: Training • Cloud tutorials at summer schools – RDA-ENVRIplus Summer 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 Data. Hub tutorials – Support demonstrations and ‘small-group’ tutorials of CCs • SA 2. 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) 2/14/2022 Conclusions 15
JRA 1 – e-Infrastructure Commons 1/2 • TJRA 1. 1 - AAI – – Finalisation of the Lo. A support Finalisation of VO membership information connectors Finalisation of OIDC client management UI Integration of new SPs (including EGI tools and services – e. g. Fed. Cloud) • TJRA 1. 2 & TJRA 1. 5 – Marketplace & e-GRANT – – – 2/14/2022 Move the prototype to pre-operations (beta) Integration with the Application on demand platform Customer dashboard Orders registration Term of reference Conclusions 16
JRA 1 – e-Infrastructure Commons 2/2 • TJRA 1. 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 Check. In – Migration to the new messaging infrastructure • TJRA 1. 4 – Operations tools – Ops Portal: Integration with Check. In and migration to the new messaging infra – GOCDB: writable REST API extension and GUI improvement – ARGO: probes management, integration with Check. In and migration to the new messaging – Messaging: HTTP messaging service in production – Security Monitoring: automatic framework for VM image assessment integrated with App. DB. 2/14/2022 Conclusions 17
JRA 2. 1 Open Data Platform JRA 2. 1 • Improvement of Onedata scalability in terms of collection size and simultaneous users • Integration of further storage providers to the EGI Data. Hub • Provision of additional open data collections via EGI Data. Hub 2/14/2022 Conclusions 18
JRA 2. 2 Federated Cloud JRA 2. 2 • OCCI • • • Implement an ooi standalone service -> decouple from nova-api service Integrate ooi in the Open. Stack Finalise Synnefo implementation • Authentication • Keystone: Move from V 3 while maintaining V 2 support • Accounting • Implement new version of accounting record to ease computation of long-running VMs. • Cloud. Keeper • Implement additional CMF modules • Information System • 2/14/2022 Finalize GLUE 2. 1 implementation Conclusions 19
JRA 2. 3, JRA 2. 4 JRA 2. 3 e-Infrastructure Integration • Complete EGI Check. In based integration for Open. Stack • Develop technical integration plan for commercial providers JRA 2. 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 Fed. Cloud sites 2/14/2022 Conclusions 20
Thank you for your attention. Questions? www. egi. eu This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.