1. WP8 – EPOS Seismology F Haslinger and the EPOS Seismology Consortium

2. Three Services (and many on-going EC and national projects) Observatories and Research Facilities for European Seismology www.orfeus-eu.org European-Mediterranean Seismological Center www.emsc-csem.org European Facilities for Earthquake Hazard & Risk (EFEHR) www.efehr.org and a large number of past and present (infrastructure and research) projects are integrated within and contributing to EPOS (-Seismology) The landscape of European Seismology

3. 70 Seismological Infrastructures > 4000 seismic stations (incl. temporary) 70 Seismological Infrastructures > 4000 seismic stations (incl. temporary) … are declared in EPOS-RIDE The landscape of European Seismology

4. The Origin of the ‘Pillar’ Concept

5. 5 4 ‘service pillars’: reflecting established infrastructures & adding those that were so far missing. Group data, products, services into relevant structures that make sense from a technical & scientific viewpoint, and are appropriate for having their own respective governance (as they may be composed of various service nodes)

6. 6 Governance and coordination across EPOS-Seismology - all pillars adequately represented to provide internal coordination & strategic planning - Interacts with similar bodies of other TCS and with EPOS management to provide input to overall EPOS coordination & strategic planning (work plan & budget proposals, reporting, …)

7. EPOS-Seismology Vision  A limited set of centralized infrastructures that support / provide a framework for a large variety of services originating from different sources: a ‘federated’ model  Enabling continuous innovation and development  ‘innovation’ is not a one-time activity!  Manage information and strengthen interaction Implications for EPOS-IP:  Strong focus on structural developments  At the end (of EPOS-IP) have a sustainable framework that is: State-of-the-art Easy to use (input / output) Modular & distributed Well integrated in EPOS (governance & ICT)

8. EPOS-Seismology in context

9. Technical Tasks in EPOS-Seismology Building EPOS-Seismology: Components of the EPOS Implementation Phase 4 technical tasks, corresponding to each of the 4 pillars, with various sub-tasks: Next generation software architecture for the European Integrated Data Archive EIDA. EIDA-compliant services for strong motion and acceleration data distribution; integrate structural monitoring arrays. Integration of mobile (land) networks and OBS data; coordination policies of transnational access and multinational experiments A common collection and development platform for seismological products. Improved data exchange and web-services for the European Archive of Historical Earthquake Data AHEAD. Improved services for earthquake parameter and observation information. Partners: AFAD, CNRS, CSIC, ETH, GFZ, INGV, KNMI, KOERI, NOA Lead: KNMI (for ORFEUS) Partners: AFAD, CNRS, CSIC, EMSC, INGV, KNMI, NOA Lead: EMSC

10. Building EPOS-Seismology: Components of the EPOS Implementation Phase Technical Tasks in EPOS-Seismology Host the European Facilities for Earthquake Hazard and Risk EFEHR and its web-portal Maintenance and curation of the European Database of Seismogenic Faults Maintain and update the European Ground Motion Prediction Equations database Develop the European geotechnical engineering information database and web- services; including geological, geotechnical and site conditions inventories Improved and validated tools for analysis and interpretation of weak- and strong- motion data from buildings and infrastructures; integrate building records with damage observations to calibrate fragility functions. Establishment of engineering requirements for seismic hazard products; harmonizing exposure and vulnerability models for European infrastructures (partnership and coordination with GEM). Implement the 3D waveform modeling portal of VERCE as pilot for the EPOS computational earth science infrastructure. Together with community develop list of priority applications for implementation on HPC, grid, and cloud infrastructures. Lead: UNLIV Partners: CNRS, INGV, LMU, UNLIV Lead: ETH (for EFEHR) Partners: AFAD, AUTH, CNRS, ETH, EUCENTRE, GFZ, INGV, KOERI

11. Waveform ServicesDetails EIDA-Next Generation services (lead GFZ): develop the next generation software architecture for EIDA : EIDA-NG  use of FDSN web services  include QA and a mediator service  cover the specific needs of ocean bottom station (OBS) data and other seismological data in EPOS Integrate (persistent) identifiers & metadata (EPOS-compliant AND seismology relevant) Connect to TCS Volcanology (for seismological data) & TCS Near Fault Observatories (metadata needs, EIDA integration)

12. Waveform ServicesDetails Data services and coordination for mobile pools and OBS: EIDA integration of mobile networks (lead CSIC) and OBS (lead CNRS) seismological waveforms  data and metadata standards develop policies and implement mechanisms for coordination of transnational access and multinational experiments at available pools of OBS and mobile seismic stations. Strong motion data products and services (lead INGV): develop and implement EIDA-compliant services for strong motion and acceleration data distribution  including the SM-relevant extension of station metadata  and ’derived’ parameters relevant for engineering purposes Integrate the collection of structural monitoring arrays into EIDA

13. Waveform Services Basically station-centric services  discover,  select,  retrieve waveform data and related information (incl. station-specific) Event information as one subset of selection criteria

14. Seismological Products Services Details A common collection and development platform for seismological products (lead EMSC): collect and provide access to new products (& services) of scientific interest  e.g. source model database; site response modeling tool  solve ‘authoritativeness’ where required, offer ’varieties’ where appropriate use to benchmark new methods and develop product specific validation concepts Improved data exchange and web-services for the European Archive of Historical Earthquake Data AHEAD (lead INGV): enable efficient data exchange among participants & data discovery & distribution for users  finalize data exchange format  update web services implementation

15. Seismological Products Services Details Improved services for earthquake parameter and observation information (lead EMSC): Expand product collection, diversify collection and dissemination (federate it)  improve data quality checks & definitions  improve usability Increase service robustness Support (participating) observatories in developing ‘home-branded’ services  offer tools (e.g. smartphone app) and implementation support

16. Seismological Products Services largely event-centric services  discover,  select,  retrieve earthquake parametric and related information some service platform components added Federalized production of information Authoritativeness to be addressed where required

17. Seismic Hazard and Risk ServicesDetails Hosting the European Facilities for Earthquake Hazard and Risk EFEHR (lead ETH) Maintain and further develop the access platform and web services  access to software, models, data(bases) and best practice guidelines Provide access to connected specialized nodes of EFEHR Maintenance and curation of the European Database of Seismogenic Faults (lead INGV) Maintain, review, update and provide access to up-to-date fault information Maintain the European Ground Motion Prediction Equations database (lead GFZ) Maintain and update a region-specific logic tree of suitable GMPEs, validated against SM data and integrating new intensity measures

18. Seismic Hazard and Risk ServicesDetails Develop the European geotechnical engineering information database and web-services (lead AUTH) Geotechnical, geological and site conditions inventory; collect and harmonize national / regional data bases Tools for analysis and interpretation of strong-motion data from buildings and infrastructures (lead KOERI) Validation and improvement of tools to analyse and interpret building data as input for computing engineering demand parameters and to evaluate structural conditions. Establish engineering requirements for seismic hazard products (lead EUCENTER) Harmonize exposure and vulnerability models for European risk assessment for buildings and infrastructures

19. Seismic Hazard and Risk Services largely location (area) - specific services  discover,  select,  retrieve seismic hazard & risk information input data & models resulting data & models tools & services truly federated specialized services, brought together with a wrapper

20. Computational Seismology Services Details Implementing Computational Seismology tools and (lead UNLIV) Implement the 3D waveform modeling portal of VERCE  pilot for the EPOS computational Earth science infrastructure Together with community develop list of further priority applications for implementation on HPC, grid, and cloud Develop and set up a ‘training platform’ for computational seismology applications (urgent need identified)

21. Computational Seismology Services largely ??? centric / specific services - cross-domain relevance of 3D earth models (access to / easy comparison / transformation) and corresponding forward modeling tools very close interaction and collaboration with ICS Major challenge: access to HPC resources / centers (organizational / managerial issues)

22. Further considerations (4 more slides…)

23. Further considerations Timeliness of data & data products (access) In the past, lot of discussion on ‘near real time’ availability of data & information within EPOS-Seismology (with no clear decision) (actually very little scientific reason / justification for that) Timeliness issue largely driven by societal impact (e.g. earthquake information) and to some extent by scientific competition (the first to have access to data may be the first to publish) From a purely scientific perspective, other things are more important than speed

24. Further considerations Currently services are almost exclusively designed for federation For technical / operational purposes this may only be the 2 nd best solution (at least in some cases) … … but we don’t seem to have another option (politically) ? Having a ‘technical infrastructure’ (IT hardware) forever on the TCS level is probably not necessary (may move to ICS-c / -d at some point) … … but control over IT services must remain with the TCS (in their field)

25. Further considerations EPOS is not just an e-infrastructure ICT will become more and more standardized and useable (trivial) in future But scientific political / strategic / organizational issues need a structured and recognized framework for discussion, decision-making, and representation (data policies, authoritativeness, validation, quality control, (scientific) usability, international integration)

26. >4500 stns ~750 rt bb ˜ 300 TB Waveforms Seismological products Instrumental catalog historical catalog European hazard computational tools EPOS-Seismology one house in the EPOS village special models reference models The End The Beginning