Testing and Validation Kuvvet Atakan and the WP6 and WP7 Teams

ICS-TCS interactions Requirements elicitation process – TCS requirements on data, data products, software and services (DDSS) – TCS use cases – TCS assets Harmonisation process – Cross-checking the interoperability of various DDSS elements from all TCSs – Identifying those DDSS elements that needs to be harmonised User feedback processes – Approval of requirements and harmonisation processes before the implementation – User feedbacks during the ICS development and testing period ICS development process – Joint work by ICS and TCS – Continuous interactions Testing process – Testing the functionalities of ICS-C – Testing the interoperability of the DDSS from relevant TCSs – Testing the maturity of the various DDSS of TCSs Validation process – Approvals by ICS-development team and TCS teams – Approvals by SCB, IPC, BNSR and finally by BGR Further process during pre-operational phase

ICS-TCS interactions Requirements elicitation process – TCS requirements on data, data products, software and services (DDSS) – TCS use cases – TCS assets Harmonisation process – Cross-checking the interoperability of various DDSS elements from all TCSs – Identifying those DDSS elements that needs to be harmonised User feedback processes – Approval of requirements and harmonisation processes before the implementation – User feedbacks during the ICS development and testing period ICS development process – Joint work by ICS and TCS – Continuous interactions Testing process – Testing the functionalities of ICS-C – Testing the interoperability of the DDSS from relevant TCSs – Testing the maturity of the various DDSS of TCSs Validation process – Approvals by ICS-development team and TCS teams – Approvals by SCB, IPC, BNSR and finally by BGR Further process during pre-operational phase

University of Bergen / Department of Earth Science EPOS IP project Timeline Implementation Validation Pre-operation

EPOS-IP is a complex project with 46 partner institutions and 17 WPs

TCS requirements and DDSS for ICS Details of the TCS requirements will be collected including: – Requirements on data, data products, services and software (DDSS) to be included in EPOS ICS-C – Detailed description of use cases – Detailed description of TCS assets Priority list for DDSS implementation to be prepared by the TCS WPs TCS Road Maps for other remaining DDSS implementation Approval of the selected DDSS for implementation – i.e. concensus building by: – TCS DDSS providers – ICS-developers – SCB and IPC (+BNSR and BGR?)

Testing and Validation Testing and validation of the ICS-C technical development. This needs to be done by the developers and TCS user feedback groups. Testing and validation of various DDSS from all TCSs for their maturity for implementation. This requires a new timeline for those DDSS elements that are not found mature, as well as a plan for accession to entry (TCS Road Map) The outcome of testing and validation performed jointly by the ICS-developers and the TCS communities, should be brought at the BGR through the BNSR, after the approval of SCB and IPC.

Testing and validation criteria Adoption of coherent Data Policy and Data Management Plan Quantity and quality of DDSS accessible through research infrastructures Check services and their use Level of interoperability and coherency of metadata structure ICS functionality, system performance and robustness Reliable financial and governance models

Process of Testing and Validation Testing and validation of various DDSS from TCSs is a concensus building process which should be transparent and inclusive Building a concencus in the community is about representativeness of the community in the decision process to secure the legitimacy Starting the process with TCSs providing their own priority list of DDSS to be implemented gives confidence to the communities in concern Including the user feedback group evaluations in the decision process is another way of objective assessment of maturity

Computational Earth Science (CES) Integration of CES services require: – Availability of the dedicated software from the relevant TCSs – Access to HPC resources – Access to data storage facilities – Access to visualisation and processing tools Integrating CES requires a community effort and standardisation of the software and resources in addition to the ICS technical integration There are mature services associated with some of the TCSs CES applications related to some of the TCSs may need additional community effort

ICS-D integration ICS-D includes: – Access to HPC resources – Access to data storage facilities – Access to visualisation and processing services Technical integration process for the EPOS-IP ICS-D integration requires a formal process – Application procedure for interested technology and resource providers – Selection process for the relevant ICS-D – Formal agreements regulating the access to ICS-D resources – Financial aspects of ICS-D services Final integration and committments for the EPOS-OP

Take home messages Decisions on various DDSS for each TCS requires an open, inclusive and transparent process internally at each TCS community. A realistic estimate of the maturity for implementation of various DDSS for each TCS is needed. Harmonising the requirements and expectations from the TCSs with the requirements and standards of the ICS-C is essential. Each TCS needs to have a realistic timetable for deliveries for internal processes and developments taking into account the implementation, testing and validation processes. Each TCS needs to allocate sufficient human resources for the ICS- integration. Further plans are needed for those DDSS that may not be found mature for implementation before the pre-operational phase.

Thank you for your attention! University of Bergen / Department of Earth Science