1. The GEOSS Interoperability Process Pilot Project Siri Jodha Singh Khalsa IEEE Committee on Earth Observations Standards Working Group

2. ADC-IV Tokyo # 2 Contents Scope and purpose of the IP3 The GEOSS Interoperability Process and the Standards and Interoperability Forum Description of use case scenarios Progress Report Schedule

3. ADC-IV Tokyo # 3 Origins of the IP3 The GEO ADC recognized the need to begin implementing the GEOSS infrastructure and testing the process for reaching interoperability. The concept for an “Interoperability Process Pilot Project” was presented, reviewed and endorsed by the ADC co-Chairs in July 2006. GEO Task AR-06-01 given task of developing a series of projects involving different SBA’s, leading up to a suite of demonstrations at the GEO Summit in November.

4. ADC-IV Tokyo # 4 GEOSS Implementation Plan "The success of GEOSS will depend on data and information providers accepting and implementing a set of interoperability arrangements, including technical specifications for collecting, processing, storing, and disseminating shared data, metadata, and products." GEOSS 10-Year Implementation Plan, 5.3 Architecture and Interoperability

5. ADC-IV Tokyo # 5 Differential Interoperability In GEOSS interoperability is not a goal unto itself –Different domains within GEOSS should pursue attainable improvements in interoperability on whatever time scale is appropriate to their separate needs and available resources Only a few functions (e.g, the Clearinghouse supporting searchable catalogs of services and data holdings) are required to encompass all parts of GEOSS Potential interconnections among components are almost endless –No "master data system" can encompass all parts –Systems must be built to serve particular needs, but should also be designed for interoperability.

6. ADC-IV Tokyo # 6 A Services Oriented Architecture Approach Any component of GEOSS can expose service interfaces intended to provide opportunities for other GEOSS components to “interoperate” The exposure of a component interface within GEOSS must be accomplished through a registered service interface that references a GEOSS-registered standard or a GEOSS Interoperability “Special Arrangement”.

7. ADC-IV Tokyo # 7 GEOSS Interoperability Strategy A Services Oriented Architecture (SOA) approach to interoperability –GEOSS is viewed as an assembly of independent components that offer “services” via interfaces –These communications must adhere to selected international standards –Interoperability not necessarily “automatic” –Within some domain interoperability based on ad hoc arrangements hinders other systems from joining

8. ADC-IV Tokyo # 8 “Interoperability Arrangements” When two GEOSS components conform to the same data description and transport standards, and are well- defined within the GEOSS registries, interoperability should be achievable with minimal effort Where two GEOSS components do not share common standards, or where the service definitions are not adequate, interoperability “Special Arrangements” will need to be made. This will be managed by the GEO “Standards and Interoperability Forum.”

9. ADC-IV Tokyo # 9 IP3 Development Phases Phase 1 – Populating the Component, Services and Interoperability Registers Phase 2 – Develop Cross-System Interoperability Scenarios, invoke SIF Phase 3 – Create Demonstrations Phase 4 – Work on Higher Levels of Interoperability Repeat process with new components and scenarios to address other SBAs

10. ADC-IV Tokyo # 10 Participating Systems and Principals Biodiversity –Hannu Saarenmaa & Stefano Nativi Seismology –Tim Ahern CEOP –Ryosuke Shibasaki WMO Information System - WIS –David Thomas

11. ADC-IV Tokyo # 11 Phase 1 – Populating the Registers Populate the GEOSS registers –Identify the standards, interface protocols and interoperability agreements in use –Provide information to the Clearinghouse as it is brought online Analyze successful data integration projects, showing –why and how interoperability arrangements were made and maintained –how the interoperability arrangements worked under the computer and network environment of the time –what the impacts were of these arrangements

12. ADC-IV Tokyo # 12 GEOSS Interoperability Process Component Contributor Register Component Reference registered standard Capture details of proposed GISA* Begin Service Registration Component has interface? Done Uses registere d standard ? Y Y N N Done Pass proposed GISA to SIF *GEOSS Interoperability Special Arrangement

13. ADC-IV Tokyo # 13 The Standards and Interoperability Forum A Standards and Interoperability Forum (SIF) is being formed to carry out impartial review of GEOSS interoperability issues and to recommend solutions. Helping to establish the SIF and refining its protocols and procedures is one of the key objectives of the IP3.

14. ADC-IV Tokyo # 14 Guiding Principles of the SIF The SIF will encourage broader use of existing standards as one factor in recommending interoperability arrangements. The SIF will consider existing international standards organizations and institutes as a focal point for the GEOSS interoperability objectives. In rare cases where no existing standard fulfills GEOSS needs, the SIF could identify appropriate Standards Development Organizations (SDOs) to carry out the standards development process.

15. ADC-IV Tokyo # 15 SIF Role in Phase 1 of IP3 During Service Registration, if the service does not use an existing “GEOSS Recognized Standard” (GRS) the contributor will enter details on proposed “GEOSS Interoperability Special Arrangements” (GISA). This information will be passed to the SIF, which will manage entries into the “Special Arrangements” register hosted by the IEEE. –Interoperability Register = Standards Register + Special Arrangements Register The SIF will also review and recommend promotion of GISAs to GRSs as appropriate.

16. ADC-IV Tokyo # 16 Phase 2 – Cross-System Interoperability Scenarios Develop scenarios that require the exchange of data and information between disparate systems which have not yet established a mechanism for such an exchange. –Address needs identified in one or more of the Societal Benefit Areas –Ensure relevancy and realism Demonstrate how the GEOSS architecture, data, and services have made it possible to realize benefits that would not have been easily achieved otherwise

17. ADC-IV Tokyo # 17 SIF Role in Phase 2 of IP3 The SIF will assist in management or creation of interoperability arrangements between systems –Seek the input of technical and discipline experts –Evaluate Special Arrangements as submitted at service registration –Analyze existing entries in the Interoperability Register for applicability

18. ADC-IV Tokyo # 18 Scenario Worksheet

19. ADC-IV Tokyo # 19 Extended Scenario Template 1.Plain Language Description 1.1.Short Definition 1.2.Purpose 1.3.Describe a scenario of expected use 1.4.Definition of Success 2.Formal Use Case Description 2.1.Use Case Identification 2.2.Revision Information 2.3.Definition 2.4.Successful Outcomes 2.5.Failure Outcomes 3.Use Case Elaboration 3.1.Actors 3.2.Schematic of Use case 3.3.Preconditions 3.4.Postconditions 3.5.Normal Flow (Process Model) 3.6.Alternative Flows 3.7.Special Functional Requirements 4.Non-Functional Requirements 4.1.Performance 4.2.Reliability 4.3.Scalability 4.4.Usability 4.5.Security 4.6.Other Non-functional Requirements 5.Selected Technology 5.1.Overall Technical Approach 5.2.Architecture 5.3.Technology A 5.3.1.Description 5.3.2.Benefits 5.3.3.Limitations 5.4.Technology B 5.4.4.Description 5.4.5.Benefits 5.4.6.Limitations 6.References

20. ADC-IV Tokyo # 20 IP3 Scenarios and Data Flows WIS GBIF FDSN CEOP Species Response to Climate Change Scenario Nativi Fault Lubrication Scenario Ahern Landslide Risk Scenario Thomas Flood Risk Scenario Burford Seismic Events from Glacier/Ice Sheet Disintegration Scenario Ahern Exotic event catalog Terminus retreat GLIMS Event catalog Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS) Seismic Trigger Precip, soil moisture (TIGGE) Climate data (NCAR) Species data DEM (DEMIS) Ancillary Meningitis Early Warning System Kelly Precip, soil moisture (TIGGE) Soil moisture, stream gage, etc.

21. ADC-IV Tokyo # 21 IP3 Scenarios and Data Flows WIS GBIF FDSN CEOP Species Response to Climate Change Scenario Nativi Fault Lubrication Scenario Ahern Landslide Risk Scenario Thomas Flood Risk Scenario Burford Seismic Events from Glacier/Ice Sheet Disintegration Scenario Ahern Exotic event catalog Terminus retreat GLIMS Event catalog Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS) Seismic Trigger Precip, soil moisture (TIGGE) Climate data (NCAR) Species data DEM (DEMIS) Ancillary Meningitis Early Warning System Kelly Precip, soil moisture (TIGGE) Soil moisture, stream gage, etc.

22. ADC-IV Tokyo # 22 WIS The World Meteorological Organization’s (WMO) Information System (WIS) Builds on the Global Telecommunications System Comprises many different systems and initiatives: –World Weather Watch Global Observing System - GOS –Global Atmosphere Watch - GAW –World Hydrological Cycle Observing System - WHYCOS –World Climate Programme - WCP –Global Climate Observing System - GCOS –Global Ocean Observing System - GOOS –Global Terrestrial Observing System - GTOS

23. ADC-IV Tokyo # 23 TIGGE Component being offered for IP3 is the THORPEX Interactive Grand Global Ensemble (TIGGE) –Global ensemble model atmospheric forecasts for short to medium term Data are collected and available at three centers –European Centre for Medium Range Weather Forecasting (ECMWF) –National Center for Atmospheric Research (NCAR) –China Meteorological Administration (CMA). Free public access through Internet under phase one Data formats being are GRIB-2 Message identification and switching through file names

24. ADC-IV Tokyo # 24 IP3 Scenarios and Data Flows WIS GBIF FDSN CEOP Species Response to Climate Change Scenario Nativi Fault Lubrication Scenario Ahern Landslide Risk Scenario Thomas Flood Risk Scenario Burford Seismic Events from Glacier/Ice Sheet Disintegration Scenario Ahern Exotic event catalog Terminus retreat GLIMS Event catalog Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS) Seismic Trigger Precip, soil moisture (TIGGE) Climate data (NCAR) Species data DEM (DEMIS) Ancillary Meningitis Early Warning System Kelly Precip, soil moisture (TIGGE) Soil moisture, stream gage, etc.

25. ADC-IV Tokyo # 25 Seismology Overview FDSN: International Federation of Digital Seismographic Networks The FDSN network consists of ~300 stations, ~200 of which contribute data to the FDSN Archive for Continuous data at the IRIS DMC.

26. ADC-IV Tokyo # 26 Seismology Standards and Interoperability Arrangements Seismology has a long tradition of sharing data The FDSN comprises a backbone network of globally distributed seismometers supplying real time data The FDSN also supports regional data centers that coordinate data concentration on a regional scale –Methods of accessing information from these varies greatly

27. ADC-IV Tokyo # 27 Data Format Standards and Interfaces Standard for Exchange of Earthquake Data (SEED) is the official standard developed and supported by the FDSN Interfaces include Email-based, Browser-based (forms), and other internet-based APIs New initiative Geoscience Web Services –http://www.geows.org/http://www.geows.org/ –Interdisciplinary (Marine Geology, UNAVCO, IRIS)

28. ADC-IV Tokyo # 28 Seismology Scenarios Do high rainfall rates or excess groundwater produce increased earthquake activity in areas of known faults? Can global seismic networks be used to monitor ice sheets and glacial activity and thus remotely sense effects of warming on a global scale? Can rainfall and seismic activity data be used to predict locations where hillsides are susceptible to collapse?

29. ADC-IV Tokyo # 29 Successes Component registration forms completed for FDSN, CEOP, WIS In addition to WIS, forms also completed for these subsystems: –World Weather Watch Global Observing System - GOS –Global Atmosphere Watch - GAW –World Hydrological Cycle Observing System - WHYCOS –World Climate Programme - WCP –Global Climate Observing System - GCOS –Global Ocean Observing System - GOOS –Global Terrestrial Observing System - GTOS

30. The GEOSS Interoperability Process Pilot Project Status Report Siri Jodha Singh Khalsa IEEE Committee on Earth Observations Standards Working Group

31. ADC-IV Tokyo # 31 Species Response to Climate Change Ecological Niche Modeling is applied to study the adaptation of butterflies in Canada and Alaska to various climate change scenarios. Requires interoperability between the GBIF (Global Biodiversity Information Facility) and components of the WIS (World Meteorological Organization Information System).

32. ADC-IV Tokyo # 32 Flood Risk Scenario A distributed surface run-off model provides data for flood warning and dam operation systems. Requires interoperability between CEOP (Coordinated Enhanced Observation Period) systems and components of the WIS.

33. ADC-IV Tokyo # 33 Landslide Risk Analysis to determine whether rainfall and seismic data be used to predict locations where hillsides are susceptible to collapse. Requires interoperability between the FDSN (International Federation of Digital Seismographic Networks), the WIS, and an interoperable landslide database network in Australia.

34. ADC-IV Tokyo # 34 Fault Lubrication Analysis to determine whether high rainfall rates or excess groundwater produce increased earthquake activity in areas of known faults. Requires interoperability between FDSN and WIS components.

35. ADC-IV Tokyo # 35 Seismic Events from Glacier/Ice Sheet Disintegration Analysis of seismic signals and a combination of remote sensing and in situ data for selected glaciers to determine whether global seismic networks can be used to monitor ice sheets and glacial activity and thus remotely sense effects of warming on a global scale. Requires interoperability between FDSN and databases at the National Snow and Ice Data Center.

36. ADC-IV Tokyo # 36 Scenario End Points Two of the scenarios (GBIF and Flood Risk) have substantial resources backing them –Schedule/critical path for these being worked –End point is live demo plus video or narrated slide show The scenarios involving FDSN may not evolve past conceptual stage due to lack of resources –End point is 2-page write up At least 2 of the scenarios will require “special arrangements” to be registered, thus ensuring involvement of the SIF.

37. ADC-IV Tokyo # 37 Phase 3 – Demonstrations Present results of Phase 2 to the Architecture and Data Committee and then with all GEO Members and Contributing Organizations –Prepare a briefing on the process –Include live demonstration of those infrastructure components that have been implemented The Interoperability Register and Registry Data and information exchange via the defined arrangements Two kinds of demonstrations –technical –social benefit demo for policy makers and senior managers –to illustrate interoperability process and its benefits

38. ADC-IV Tokyo # 38 Phase 4 – Higher Levels of Interoperability Develop higher levels of interoperability –Exercise more completely the capabilities of the protocols and interfaces identified –Address semantic interoperability Ensure the meaning of the data and information exchanged through the interfaces are intelligible to the recipient systems

39. ADC-IV Tokyo # 39 IP3 Status Component registration forms filled out for all components –Awaiting component registry to become operational Scenario sheets written, including service interface descriptions –Specifics being captured as service registry is used Standards registry is operational –Common international standards as initial content

40. ADC-IV Tokyo # 40 Schedule MilestoneDelivery Date Component registration forms completedFeb ‘07 Draft scenarios deliveredFeb ‘07 Standards Registry Availability AnnouncedMay 18 SIF Call for Participation ReleasedMay 25 Extended scenarios deliveredJune 1 Components and Standards registers populated w/ IP3 dataMay ‘07 Demonstration to ADCSept ‘07 Delivery of IP3 documentsNov ‘07

41. ADC-IV Tokyo # 41 Summary The Interoperability Process Pilot Projects are contributing to the development of the GEOSS architecture by exercising core GEOSS components and processes. The scenarios under development are fully compliant with, and representative of, the GEOSS process for reaching interoperability.

42. ADC-IV Tokyo # 42 Related Events GEOSS Architecture Implementation Pilot –GBIF Scenario submitted in response to CFP –Kickoff meeting: 5-6 June 2007 at ESA/ESRIN in Frascati (Rome), Italy IEEE GEOSS Workshop –The User and the GEOSS Architecture, GEOSS Interoperability and Applications to Biodiversity –22 July 2007, Barcelona, Spain