GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot

1. GEO Architecture and Data CommitteeTask AR-07-02 Architecture Implementation Pilot George Percivall September 2008

2. GEO Task AR-07-02Architecture 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

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

4. Updates for each step Architecture Documentation Baseline AI Pilot Development Approach Participation AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Concept Development Participation Continuous interaction with external activities Call for Participation Participation Kick-off Workshop Participation Development Activities Participation Persistent Operations (AR-07-01) Operational Baseline and Lessons Learned for next evolutionary spiral

5. AIP Phase 2 - CFP (Call For Participation ) • CFP Main Document • Master Schedule • Themes 2008 • How to respond to CFP • Annex A: Development plan • Development phases; Communication Plan • Relationship to GCI task force • Annex B: Architecture CFP announced 30 June 2008 Responses for Kickoff 1 Sept 2008

6. AIP Phase 2 Priorities • Identify and register solutions that are available in GEOSS as complete application solutions used on a regular basis by a Community of Interest. • Underlying services and schemas are exposed in well-documented, ideally standard, ways and are demonstrated as consumable by other solutions (in the scenarios). • Coordination and integration activity through 'externality analysis' to relationships, dependencies and issues with related topics.

7. AIP Phase 2 Themes • Consolidate the GEOSS Common Infrastructure • Emphasize SBAs identified by UIC/ADC collaboration • Develop operational persistence; • "persistent exemplars” • Refine GEOSS AIP Architecture definition • Further open the AIP development process to all interested parties

8. Alerts/Feeds Servers Other Services Processing Severs Workflow Management Portrayal Servers Community Catalogues Community Portals Infrastructure Registries CFP Architecture – Component Types Client Tier GEO Web Portal GEO Web Site Client Applications Business Process Tier GEOSS Registries GEOSS Clearinghouse Components Services Standards Requirements Access Tier Product Access Services Sensor Web Services Model Access Services GEONETCast Other Services

9. CFP Architecture – Operational Persistence • Length of commitment • Upon registering a service, a service provider must specify the length of time for which the service will be offered (preferably ‘continuous operation’). • Consider multiple years • Level of service • services are expected to be available at least 99% of the time, except when otherwise required by the nature of the service. • This allows for approximately 7 hours of down time a month • Being achieved regularly by servers, Biggest problem is network provider • Performance (perhaps by specifying number of simultaneous connections) • Termination • GEO may “de-list” a server • non-functioning components of the Network will diminish the operational and marketing value of the Network in general for all participating organizations.

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

11. AIP-2 Kickoff Sessions • Societal Benefit Areas, Communities of Practice & Scenarios • Disaster Response • Biodiversity and Climate Change • Renewable Energy • Air Quality • Technology contributions: • Catalogues, Clearinghouse, Metadata • Data Product Access: service, schema, encoding • Sensors and Models Access: service, schema, encoding • Workflow for derived product and alert generation • Clients • Test Facility

12. Coordinating GEO Tasks in CFP Responses • DI-06-09 Use of Satellites for Risk management • DI-07-01 Risk management for floods • EC-07-01 Global Ecosystem Observation and Monitoring Network • DA-07-04 Sensor Web Enablement for In-Situ Observing Network • DA-07-06 Data Integration and Analysis System • DA-06-05 Basic Geographic Data • AR-07-03 Global Geodetic Reference Frames • AR-07-01 Enabling Deployment of a GEOSS Architecture

13. AIP Phase 2 Master Schedule • Architecture Workshop February 2008 • CFP announce 30 June 2008 • CFP Clarification Telecon 18 July 2008 • CFP Responses for Kickoff due 1 Sept 2008 • Kickoff workshop 25-26 Sept 2008 • Status & Interim results to GEO Plenary November 2008 • AIP-2 results transition to operations 1st quarter of 2009