1. Massimo Cocco & Joern Lauterjung EPOS PP Council Rome September 19 th 2013 The Technical architecture Material prepared by WG7

2. Technical (for the next 5 years) consolidated issues Mapping of national RIs (RIDE) ICS definition & functional architecture TCS design (role of pillars, and key data products & services) Metadata structure (3 layers) pending challenges/activities Metadata catalogue (demonstrator, FUTUREVOLC as proxies) ICS timeline for implementation Distributed ICS (definition & resources) TCS implementation (data products, data repository, i.e. rockypedia) Compatibility layer Use Case Technical description IAAA, DOI, PID

3. EPOS services The EPOS Integrated Core Services will provide access to multidisciplinary data, data products, synthetic data from simulations, processing and visualization tools,.... Not just data access but EPOS means to integrate, analyze, compare, interpret and present data and information about Solid Earth Thematic Core Services are infrastructures to provide data services to specific communities (they can be international organizations, such as ORFEUS for seismology) National Research Infrastructures and facilities provide services at national level and send data to the European thematic data infrastructures.

4. The National RIs MAP OF: - Seismic/GPS stations - Laboratories -- etc…. Diversity in data type and formats http://www.epos-eu.org/ride/ Research Infrastructure LIst 246 Research Infrastructures 138 Institutions 22 countries 2272 GPS receivers 4939 seismic stations 464 TB Seismic data 1.095 PB Storage capacity 828 instruments in 117 Laboratories

5. National RI & Thematic Services WG1 - Seismology WG2 - Volcanology WG3 – Geological Data WG4 – GNSS Data WG6 – Analytical and Experimental Laboratories WG8 – Satellite Data WG10 - Infrastructures for Georesources WG 9 – Geomagnetic Observ.

6. EPOS Board of Service Providers EPOS Seismology Products and Services (ESPS) … Other EPOS Communities HAZARD AND RISK Seismic hazard & risk products and services Structure: Distributed ~3 nodes, including EFEHR (EUCENTER & ETH nodes) Products (indicative list) Hazard: Fault maps & models; source zones; hazard maps & curves & disaggregation; GMPEs Risk: Inventories & inventory models; vulnerability functions; risk maps & scenarios Services (…) Tools for model building and visualization; product viewer; hazard & risk calculation software & infrastructure WAVEFORM DATA WAVEFORM DATA Ground motion recordings from seismic sensors (possible extension to infrasound) Structure: Distributed (ORFEUS umbrella) ~8 nodes, including ORFEUS & EIDA nodes, SISMOS, SMdB Products (indicative list) Continuous and event waveforms from permanent and temporary stations (broadband, short period, strong motion); historical waveform archive; synthetic waveform data; strong motion data (products) Services (…) Station information (metadata, site characterization…); data quality (control) information European Infrastructures Mobile pools, OBS pools… EPOS Volcanology e-Seismology & common services Seismological services for visualisation, discovery and access to portal (based on seismicportal.eu ) expert groups, standards EPOS Geology COMPUTATIONAL SEISMOLOGY High performance and high end computing, data intensive computing Structure: Distributed ~3 nodes (build upon VERCE) Products (indicative list) Tools for massive scale data applications (processing, mining, visualization,…) Services (…) Access to HPC resources; data staging; data massive applications; data simulation; model repository and model handling tools (large 3D velocity models, rupture models,…) EPOS Integrated Services Visualisation tool / discovery & access portal high performance and high end computing (may absorb E-Seismology) expert groups, standards Governance and coordination by Board of Service representatives, 4-6 members EARTHQUAKE PRODUCTS Parametric earthquake information and event- related additional information Structure: Distributed ~ 5 nodes, including EMSC & its key nodes, AHEAD Products (indicative list) Earthquake parameters & bulletins; earthquake catalogues (instrumental, macroseismic, historic, synthetic); moment tensors; source models Services (…) Rapid earthquake information dissemination (felt maps, ShakeMaps) Thematic Services: WG1 Seismological Observatories EPOS “COMPATIBILITY LAYER”

7. Functional Architecture EUDAT-EPOSEPOS-COOPEUS Arclink seiscomp EPOS “COMPATIBLITY LAYER”

8. EPOS interoperability 1.Metadata organization 2.Creation of a compatibility layer Thematic service etc. Properietary Metadata EPOS INTEGRATED SERVICES EPOS Metadata COMPATIBILITY LAYER

9. Distributed Centralized and Distributed ICS Centralized

10. Not only data discovery & mining Raw data Data Products Code, software, Models... Visualization Processing & Services Metadata System Manager

11. Discovery (DC) and (CKAN, eGMS) Contextual (CERIF metadata model) Detailed (community specific) Generate Point to Web portal, Spatio- Temporal Search Search for instruments, software, models... domain-specific data with detailed metadata domain specific - geographically distributed data Anticipates data.gov domains 3-layers metadata model Under discussion also in RDA  reccomendation W3C  standard Raw data Data Products Code, software, Models... Visualization Processing & Services Metadata System Manager

12. Data Taxonomy  Level 0: raw data, or basic data (example: seismograms, accelerograms, time series...)  Level 1: data products coming from nearly automated procedures (earthquake locations, magnitudes, focal mechanism, shakemaps,....)  Level 2: data products resulting by scientists’ investigations (crustal models, strain maps, earthquake source models, etc...)  Level 3: integrated data products coming from complex analyses or community shared products (hazards maps, catalogue of active faults, etc....)  New Level for software, codes & processing tools!

13. Technical (for the next 5 years) consolidated issues Mapping of national RIs (RIDE) ICS definition & functional architecture TCS design (role of pillars, and key data products & services) Metadata structure (3 layers) pending challenges/activities Metadata catalogue (demonstrator, FUTUREVOLC as proxies) ICS timeline for implementation Distributed ICS (definition & resources) TCS implementation (data products, data repository, i.e. rockypedia) Compatibility layer Use Case Technical description IAAA, DOI, PID

14. Thank You www.epos-eu.org/ride www.epos-eu.org WebSite R.I.D.E. Newsletter www.epos-eu.org/newsletter Epos Social facebookyoutube twitter

15. demonstrator/prototype Demonstrator: it is a virtual realization of a piece of the services dedicated to show and disseminate the added value and the features of the integrated core services. Users can play with the demonstrator to understand or perceive what the integrated core services will be. The Demonstrator is needed at the conclusion of the Design phase and during the Validation/Testing Phase. Prototype: It is the final deliverable of the preparatory phase. It contains the preliminary but quite complete instructions to build and operate the Integrated Core Services (it might also apply to some TCS). It contains a complete list of IT requirements, a check on their availability (existence in TCS) from data providers, a plan for retrieving missing info, the IT and e-science tools and solutions, strategies to build, and needed resources, validation and testing completed, and a designed engineering phase (how to construct) with mid-term sustainability. The prototype is expected at the end of the delivery phase (M48). GOAL to have a DEMONSTRATOR - Possibly a prototype

16. Thematic Services: an example Raw and standardized Data Data Products, analisys & visualization Processing and modeling EPOS “COMPATIBILITY LAYER”

17. Functional Architecture #1 IAAA Accounting & Citation Data loading / update / basic validation Data / software storage, PID, replication, preservation, versioning Access and Retrieval Validation Aggregation Analysis Mining Simulation Discovery Reporting Visualization User Request

18. High Level Use Cases (what the user is trying to achieve) Medium level Use Cases (steps to achieve) ICT Requirements (what the ICT system has to deliver) functional and non-functional USE CASES

19. EPOS Framework: Management Legal Governance Financial Data Users & Scientists Technical Data providers Stakeholders & outreach SERVICES TO USERS a complex machine