1. GEO Architecture and Data Committee Architecture Workshop Hosted by the European Commission At the Joint Research Centre February 2008 DRAFT

2. GEOSS Core Architecture Initial Operating Capability (IOC) Core Architecture –GEO Web Portal, Clearinghouse, and Registry –Process to register, discover and use services –GEOSS Interoperability Arrangements During 2007, GEO ADC guided development of IOC through its core tasks: –AR-07-01 - Enabling Deployment of Architecture –AR-07-02 - Architecture Implementation Pilot Results demonstrated at EO Summit and GEO-IV

3. GEO Task AR-07-02 GEO Architecture Implementation Pilot - 2007 Demonstrated effective development process: –CFP, Kickoff, Execution, etc. –Approximately 120 organizations Established effective communication methods –For international coordination –www.ogcnetwork.net/AIpilotwww.ogcnetwork.net/AIpilot Produced Screencasts of Initial Operating Capability –www.ogcnetwork.net/AIPdemoswww.ogcnetwork.net/AIPdemos Prepared “Core Architecture Implementation Report”

4. GEOSS Architecture Status Architecture validated through ADC core tasks Deployed, tested and demonstrated in 2007 Component types and interactions confirmed Recommendations for Interoperability Arrangements Consistent with GEOSS Strategic Guidance Document and Tactical Guidance Document

5. GEOSS Architecture Initial Operating Capability (IOC) established 64 Components & 75 Services registered (21 Nov 07) GEO Web Portals (3), Community Portals (27) and Decision Support Clients (13) for User access to services Several organizations capable of providing –GEO Web Portal solutions –GEOSS Clearinghouse solutions

6. GEOSS Architecture - Further Development Increase collaboration with GEO Committees, Communities of Practice and relevant GEO Tasks. Increase commitment to Operational requirements to support persistence – Portal, Clearinghouse and other services Add Sensor Component Types –Task, acquire and process observations –Inter-calibration scenario, e.g., CEOS Workflow for observation processing and decision support, e.g., Fed Earth Observation (FedEO) pilot

7. AR-07-02 Task Definition Task Sheet slightly revised at ADC-5, September 2007 Architecture Implementation Pilot emphasis retained: Portals, Clearinghouse, Catalogues, and Services –Including sensors interoperability services Two items added –Persistent Infrastructure for Service Integration –GEOSS User and Architecture Workshops

8. GEO Architecture Workshop February 4&5, 2008 –Co-located at JRC Ispra with ADC-6 Purpose: Consensus building in support of CFP Topics –Scenario candidates: interactions with UIC & CoP re scenarios –Begin refinement of the CFP-2007 architecture –Sustained operations for information architecture –Other Implementation Report topics

9. UIC/ADC Collaboration Ellsworth LeDrew GEO UIC Co-Chair Hello Dr LeDrew, I note from George Pecivall's schedule that you will be discussing the UIC/ADC Collaboration at the Ispra AIP workshop. Our air quality community appreciates that ADC and your UIC Committee (Gary Foley, yourself, Brendan Kelly, and others) is pursuing a strengthened UIC/ADC connection. The incorporation of an Air Quality scenario into the Pilot is an outstanding opportunity to contribute to that effort as part of a domain-specific Pilot. For your information, the self-organizing group that has prepared the AIP Pilot - Air Quality Scenario appears to be an emerging "Community of Practice" interested in Air Quality applications using the GEOSS Architecture and User Interface Committee principles. A slide from John White's presentation at Ispra has the relevant links. The Air Quality group is keenly interested in perusing and strengthening UIC/ADS link in this scenario through the continued development of the principles and methods for Communities of Practice - and testing those in this Air Quality Pilot. Input and guidance from Gary Foley, yourself, Brendan Kelly, George Percivall and others will be appreciated. Cordially, Rudy Husar

10. Breakout Sessions – Summary Findings I A spectrum of Users –End Users (Top level Decision/policy makers, managers) in need of user friendly information –Researchers more focused on source and quality of data –Accommodate different needs & level of expertise Users versus Providers –Encourage connectivity between the two and between models and data providers –Iterative, interactive feedback from users & ability to correct errors Models –Need for interoperable cross-domain models –Improved connection between modeling and observation communities

11. Breakout Sessions – Summary Findings III SoS Architecture key desired characteristics –Offer simple, seamless services –Supports high availability, reliability, security, authentication –Facilitate interoperability –Allows for technology evolution & new technology insertion Thoughts on interoperability Focus on connecting systems within a community Interfaces are abstracted in “wrappers” developed cooperatively by Providers & Users Include ontology in Interoperability registry Build a little, test a little: demonstrations, prototypes and pilots are essential

12. A look forward- Workshops for 2008 Accra, Ghana - 08 Water Security & Ecosystems Beijing, China-08 Air Quality & Health Kobe, Japan-08 Oceans & Water Quebec, Canada-08 Science Modeling & Data Policy Toronto, Canada-08 UIC workshop Boston, USA-08 Air Quality & coastal Ecosystems Spain-08 Architecture Of GEOSS Honolulu, Hawaii-08 Communications For disaster management So many workshops, so little time

13. Architecture Workshop Interactive meeting to develop requirements for GEOSS Architecture developments. Results will become part of a Call for Participation in 2008. Scenarios identified through collaboration of the GEO UIC and ADC Domain-specific GEO Tasks can utilize AIP (AR- 07-02) to utilize the GEOSS Core Architecture

14. AI Pilot Development Approach DevelopmentActivities Phase D Kick-offWorkshop Phase C Call for Participation Phase B ConceptDevelopment Phase A PersistentDeployment Phase E