1. GEOSS Architecture Implementation Pilot, Phase 2 (AIP-2) George Percivall, Open Geospatial Consortium GEO Task AR-09-01b Task POC 2 February 2009

2. GEOSS connects Observations to Decisions 2 2

3. Group on Earth Observations: GEO EO Summit: Ministers of countries; established GEO as an organization, endorsed GEOSS 10 year plan GEO Plenary: Members (national bodies and the EC) and Participating Organizations GEO Secretariat: Director and staff GEO Committees: Capacity Building (CBC), Architecture and Data (ADC), Science and Technology (STC), User Interface (UIC), and the C4 GEO Work Plan and Tasks

4. Operational Capability Operational Capability User Needs, Scenarios User Needs, Scenarios Design, Develop, Deploy Design, Develop, Deploy Architecture Implementation Pilot (AIP) Task AR-09-01b GEOSS Common Infrastructure (GCI) Task AR-09-01a support persistent implementation requirements SBA Tasks, UIC Elaboration of GEOSS Architecture

5. GEOSS Interoperability Arrangements - From the GEOSS 10 Year Plan Reference Document - Interoperability through open interfaces –Interoperability specifications agreed to among contributing systems –Access to data and information through service interfaces Open standards and intellectual property rights –GEOSS adopting standards; agreed upon by consensus, preference to formal international standards –GEOSS will not require commercial or proprietary standards –Multiple software implementations compliant with the open standards should exist –Goal is that at least one of the implementations should be available to all implementers "royalty-free"

6. Slide 6 GEO Task AR-09-01b Architecture Implementation Pilot Lead incorporation of contributed components consistent with the GEOSS Architecture… …using a GEO Web Portal and a GEOSS Clearinghouse search facility …to access services through GEOSS Interoperability Arrangements …in support of GEOSS Societal Benefit Areas

7. Slide 7 AI Pilot has broad international participation that could only have occurred with GEO. High interest & momentum to support GEOSS. AIP Phase 1 Results – Early 2008 Elements of the GEOSS Common Infrastructure (GCI) – Initial Operating Capability established Effective development process for GEO –CFP, Kickoff, Execution, etc. –Approximately 120 organizations participated –Methods for international coordination Prepared “Architecture Implementation Report” 10 Demonstrations of Initial Operating Capability10 Demonstrations

8. AIP Phase 2 Themes Augment the GEOSS Common Infrastructure Emphasize SBAs identified by UIC/ADC collaboration Develop "persistent exemplars” Elaborate GEOSS Architecture –Scenarios and Use Cases –Service and Component types –Interoperability Arrangements Slide 8

9. DevelopmentActivities Kick-offWorkshop Call for Participation ConceptDevelopment PersistentOperations(AR-07-01) Participation ArchitectureDocumentation Updates for each step Baseline AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Operational Baseline and Lessons Learned for next evolutionary spiral Continuous interaction with external activities AI Pilot Development Approach

10. AIP Phase 2 Master Schedule

11. AIP-2 CFP Responses (37 to date) ACRF BKG Caribbean Flood Team CIESIN CNES and ERDAS Compusult EPA AirNow ERDAS Titan ESA ESIP AQ Cluster ESRI ESRI Canada EuroCryoClim NOAA/NASA GOES-R and GMU CSISS NOAA IOOS NOAA NCDC NOAA SNAAP Noblis Northrop Grumman Spot Image SURA/NIMSAT/GoMO OS USGS VIEWS Washington University in St. Louis GEONETCast GEO Grid GEO-Ukraine Giovanni ICAN ICT4EO INCOSE IP3 ISPRA JAXA KDDI Mines Paris Tech NASA World Wind

12. AIP-2 Kickoff Workshop, September 2008 At NCAR Mesa Laboratory, Boulder, Colorado, USA 85 Participants 3 Plenary Sessions 12 Parallel Sessions based on CFP Responses Established Working Groups; and Development Plan

13. AIP-2 Working Groups (WGs) Community WGs –Disaster Response –Climate Change and Biodiversity –Renewable Energy –Air Quality Transverse Technology WGs: –Clearinghouse, Catalogues, Registries and Metadata –Access Services: products, sensors, models –Workflow and Alerts –Portals and Application Clients –Test Facility for service registration

14. AIP-2 Augmenting GCI GEOSS Clearinghouses GEO Web Portals GEOSS Common Infrastructure Components & Services Standards and Interoperability Best Practices Wiki User Requirements Registries Main GEO Web Site Registered Community Resources Community Portals Client Applications Client Tier Business Process Tier Community Catalogues Alert Servers Workflow Management Processing Servers Access Tier GEONETCast Product Access Servers Sensor Web Servers Model Access Servers Test Facility

15. AIP-2 Working Groups (WGs) Community WGs –Disaster Response –Climate Change and Biodiversity –Renewable Energy –Air Quality Transverse Technology WGs: –Clearinghouse, Catalogues, Registries and Metadata –Access Services: products, sensors, models –Workflow and Alerts –Portals and Application Clients –Test Facility for service registration

16. Community WG Leaders Disaster Response –Stuart Frye, NASA; –Didier Giacobbo, Spot Image Health SBA: Air Quality –David McCabe, EPA –Frank Lindsay, NASA; –Stefan Falke & Rudy Husar, Washington Univ. Biodiversity and Climate Change –Stefano Nativi, CNR; –Gary Geller, NASA/JPL Energy SBA –Thierry Ranchin & Lionel Menard, Mines Paris Tech; –Ellsworth LeDrew, Univ Waterloo;

17. Transverse Technology WG Leaders Catalogues, Clearinghouse, Registries and Metadata –Doug Nebert, USGS; –Ted Haberman, NOAA –Kengo Aizawa, JAXA; –Josh Lieberman OGC/Traverse; Workflow and Alerts –Satoshi Sekiguchi, AIST; –Eugene Yu, GMU; –Greg Yetman, CIESIN Test Facility for service registration –Mauro Semerano, ESA Portals and application clients –Nadine Alameh, OGC/MobileAps; –Herve' Caumont, OGC/ERDAS Access Services: products, sensors, models –Glenn Rutledge NOAA, –Herve' Caumont, OGC/ERDAS; –Hans Peter Plag, UNR; –Anwar Vahed, ICT4EO; –Luis Bermudez SURA;

18. Scenarios and Use Cases Transverse Use Cases support Community Scenarios Scenarios: end user view of the value of GEOSS –Focused on topics of interest to a community –Occur in a geographic Area of Interest (AOI) –Steps in a scenario are Use Cases –Scenarios developed by Community WGs Use Cases: reusable service oriented architecture –Use cases for discovery, data access, etc –Utilize Interoperability Arrangements –Use Cases developed by Transverse Technology WGs

19. AIP-2 Community Scenarios Air Quality and Health: Wildfire & Smoke –Policy-maker, AQ compliance manager, and the public Climate Change and Biodiversity –Pika Distribution –Polar Ecosystems –Arctic Food Chain Disasters –Flood Analysis –Disaster Management Renewable Energy: Facility Planner –Site selection process for solar and wind energy

20. AIP-2 Use Case Diagram 01 Register Resources 02 - Deploy Components & Services 03 - Publish, Harvest, & Query Metadata via Clearinghouse 04 - Client Search of Metadata 05 Presentation of Services & Alerts 06 Interact with Services 07 - Exploit Data Visually and Analytically 08 - Construct and Deploy Workflow 09 Test services 10 Register Interoperability Arrangements GEOSS Service Consumer GEOSS Service Provider Notes: - Summary list - Summary list of AIP-2 Use Case Diagram - Hyperlinks from Use Cases ellipses to AIP Google Site pages are to be added. - Relationships - Relationships between use cases may be one of four types – association, extends, includes, and inheritance

21. Phasing of Test, Integration and Demo Scenario Development Use Case Development Resource Registration Use Case testing – led by clients Scenario Testing Scenario Capture 1 st Call 2 nd Call Test Log ready Unit Test Period1 Unit Test Period 2 Scenario Testing Demo Capture Event Update Storyboards JANFEBMARAPRMAY

22. AIP-2 Deliverables – 2009 (GEO Task AR-09-01a) Demonstration –Demonstration of community Scenarios implemented through transverse Use Cases –Demonstrations to be recorded and made available via WWW Engineering Reports To be considered for GEOSS Best Practice Registry –Community Scenarios –Transverse Technology Use Cases –AIP-2 Summary Report Persistent Exemplars –Registered services (‘continuous operation’) with 99% availability (~7 hours down time a month); on a reliable network; plan for performance scaling –Nomination to operational task (AR-09-01a)

23. References GEO –earthobservations.orgearthobservations.org GEO Architecture Implementation Pilot –www.ogcnetwork.net/AIpilotwww.ogcnetwork.net/AIpilot GEOSS registries and SIF –geossregistries.infogeossregistries.info George Percivall percivall@myogc.org