GEO Task AR Architecture Implementation Pilot, Phase 2 (AIP-2) Kickoff Workshop NCAR Mesa Laboratory September 2008

AIP-2 Kickoff Opening Plenary TimeTopicSpeaker 9:00IntroductionGeorge Percivall 9:10Welcome to NCAR/UCARDr. Richard Anthes, UCAR President 9:20Context of AIP, GCI, CFP Process George Percivall 9:50End-to-end use caseDoug Nebert 10:30Refreshment Break 10:45Session synopsis *11Session leads 11:50logistics for breakouts 12:00Lunch

Welcome to NCAR/UCAR Dr. Richard Anthes UCAR President

Thank you NCAR! Richard Anthes Peter Backlund Carol Park

GEO Architecture and Data Committee Task AR Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR Point of Contact September 2008

Architecture Implementation Pilot AIP-1 Results The GEOSS Common Infrastructure AIP-2 Call for Participation Responses to the CFP Schedule for Phase 2

Slide 7 GEO Task AR 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 …support GEOSS Societal Benefit Areas

Slide 8 AI Pilot has broad international participation that could only have occurred with GEO. High interest & momentum supporting GEOSS vision. 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 Capability10 Demonstrations Prepared Architecture Implementation Report

GEOSS Common Infrastructure

AIP Phase 1 Results in Components & 75 Services registered (21 Nov 07) Interoperability Arrangement recommendations to the Standards and Interoperability Forum (SIF) User interfaces to services –GEO Web Portals: Compusult, ESA, ESRI –Community Portals (27) –Application Clients (13) Multiple organizations providing –GEOSS Clearinghouse –Community Catalogues –Data Services Slide 10

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. Services and schemas exposed in well-documented, ideally standard, ways and demonstrated as interoperable with other solutions (in the scenarios). Coordination and integration activity through 'externality analysis' to relationships, dependencies and issues with related topics. Slide 11

AIP Phase 2 Themes Augment the GEOSS Common Infrastructure Emphasize SBAs identified by UIC/ADC collaboration Develop operational persistence; –"persistent exemplars Refine GEOSS AIP Architecture definition –Service and Component types –Interoperability Arrangements Further open the AIP Development Process to all interested parties Slide 12

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

AIP-2 CFP Responses (34 to date) ACRF BKG Caribbean Flood Team CIESIN CNES and ERDAS Compusult EPA AirNow ERDAS Titan ESA ESIP AQ Cluster ESRI ESRI Canada EuroCryoClim GEO-Ukraine Giovanni ICAN ICT4EO INCOSE 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

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 Slide 15

GEOSS AIP-2 CFP Annex B Developers

CFP Annex B – Architecture Enterprise Viewpoint –Value of Earth Observations Information Viewpoint –Earth Observations schemas and encodings Computational Viewpoint –SOA services; broadcast; media distribution Engineering Viewpoint –Components types and interoperability arrangements Technology Viewpoint –Component Instances, Operational Criteria

GEOSS Enterprise Viewpoint GEOSS Information System

Enterprise Viewpoint GEO community objective: system of systems Societal benefit areas Data sharing principles Interoperability arrangements SBAs for the 2nd Phase of AIP-2 –Disaster Response –Air Quality and Health –Climate Change and Biodiversity –Renewable Energy

Information Viewpoint Maps, features, coverages, and observations Spatial Referencing; Coordinate Reference Systems Registry Model Metadata Encoding Formats Alerts and Feeds

Computational Viewpoint Service oriented architecture (SOA) –Publish-Find-Bind GEOSS Functions via SOA –Services for Discovery, Access, Processing, etc. –Events GEOSS Functions via broadcast –GEONETCast GEOSS Functions via Media

Definitions component: a part of GEOSS contributed by a GEO Member or Participating organization. Components may expose service interfaces to provide access to earth observation-related functions and/or data. Components are described in the GEOSS Component Registry. service: Functionality provided by a component through component system interfaces. Services communicate primarily using structured messages, based on the Services Oriented Architecture view of complex systems. Services are described, along with information about their operating organizations, in the GEOSS Service Registry.

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

GEOSS Components GEOSS Standards GEOSS Special Arrangements expose may become nominate GEO Members and Participating Organizations offer U.S.A. IEEE UDDIebRS OGC CSW Z39.50/ SRU Web UI SIF External Standards Bodies Subject Matter Experts JAXR Z39.50/ SRU GEOSS Component and Service Registry GEOSS Services GEOSS Standards Registry GEOSS Registries Interaction reference

Test Facility for Service Registration Provide a means for service operators and technology providers to get feedback on the efficacy of their interfaces and applications in implementing and using GEOSS Interoperability Arrangements Facility will also enable periodic checking as to the availability and reliability of registered components and services, To these ends, the Test Facility needs to be a permanent, sustainable resource.

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. Slide 26

AIP-2 CFP Responses (34 to date) ACRF BKG Caribbean Flood Team CIESIN CNES and ERDAS Compusult EPA AirNow ERDAS Titan ESA ESIP AQ Cluster ESRI ESRI Canada EuroCryoClim GEO-Ukraine Giovanni ICAN ICT4EO INCOSE 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

Goals for Participation in GEOSS AIP Better awareness of community interoperability efforts Better understanding and use of proposed GEOOS standards Standardization of intra- and inter-system data exchange Leveraging and reuse of existing resources through service-chaining Increased value of existing development investments Improved resource availability and decision-making for end users

Analysis of CFP Responses Analysis conducted by Doug Nebert, Josh Lieberman, Herve Caumont, Ingo Simonis, George Percivall Each CFP response reviewed by at least 2 persons Summarized contributions in categories –SBA/CoP/Scenarios –Transverse Technology topics For each category –Primary and Secondary Participants identified –Topics within the category Results posted on-line

AIP-2 Response Analysis Categories SBA, Communities of Practice, Scenario Sessions –Disaster Response –Biodiversity and Climate Change –Renewable Energy –Health - Air Quality Transverse Technology sessions: –Catalogues, Clearinghouse, Metadata –Data Product Access: service, schema, encoding –Sensors and Models Access: service, schema, encoding –Workflow for derived product and alert generation –Clients: portals and applications clients –Test Facility for Service Registration

AIP-2 SBA/CoP/Scenario session leaders Disaster Response SBA –Ron Lowther, Northrop Grumman; Didier Giacobbo, Spot Image; Stuart Frye, NASA; Health SBA: Air Quality –David McCabe, EPA; Frank Lindsay, NASA; Stefan Falke & Rudy Husar, Washington Univ. Biodiversity and Climate –Stefano Nativi, CNR Energy SBA –Thierry Ranchin, Mines Paris Tech; Ellsworth LeDrew, Univ Waterloo

AIP-2 Transverse session leaders Catalogues, Clearinghouse, Metadata –Doug Nebert, USGS; Josh Lieberman OGC/Traverse; Kengo Aizawa, JAXA Data Product Access –Herve' Caumont, OGC/ERDAS, Glenn Rutledge NOAA NOMADS, Hans Peter Plag Task AR Sensors and Models Access –Anwar Vahed, ICT4EO; Luis Bermudez SURA; Don Sullivan, NASA Workflow for products and alerts –Liping Di, GMU; Greg Yetman, CIESIN; Satoshi Sekiguchi, GEOGrid Clients: portals and application clients –Nadine Alameh, NASA-WW; Herve' Caumont, OGC/Erdas Test Facility for service registration –Doug Nebert, USGS; Jolyon Martin, ESA

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

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

AIP Phase 2 Master Schedule

Potential Milestones for AIP-2

Architecture Implementation Pilot AIP-1 Results The GEOSS Common Infrastructure AIP-2 Call for Participation Responses to the CFP Schedule for Phase 2

Thank you! NCAR hosting of the Kickoff –Richard Anthes, Peter Backlund, Carol Park OGC acknowledges sponsorship from –European Commission –European Space Agency –USGS –ERDAS –Northrop Grumman

AIP-2 Kickoff Opening Plenary TimeTopicSpeaker 9:00IntroductionGeorge Percivall 9:10Welcome to NCAR/UCARDr. Richard Anthes, UCAR President 9:20Context of AIP, GCI, CFP Process George Percivall 9:50End-to-end use caseDoug Nebert 10:30Refreshment Break 10:45Session synopsis *11Session leads 11:50logistics for breakouts 12:00Lunch