GEO Task AR-07-02 Architecture Implementation Pilot, Phase 2 (AIP-2) Kickoff Workshop NCAR Mesa Laboratory 25-26 September 2008
Download ReportTranscript GEO Task AR-07-02 Architecture Implementation Pilot, Phase 2 (AIP-2) Kickoff Workshop NCAR Mesa Laboratory 25-26 September 2008
GEO Task AR-07-02 Architecture Implementation Pilot, Phase 2 (AIP-2) Kickoff Workshop NCAR Mesa Laboratory 25-26 September 2008 AIP-2 Kickoff Opening Plenary Time Topic Speaker 9:00 Introduction George Percivall 9:10 Welcome to NCAR/UCAR Dr. Richard Anthes, UCAR President 9:20 Context of AIP, GCI, CFP Process George Percivall 9:50 End-to-end use case Doug Nebert 10:30 Refreshment Break 10:45 Session synopsis *11 11:50 logistics for breakouts 12:00 Lunch Session leads 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-07-02 Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR-07-02 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 GEO Task AR-07-02 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 7 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. Slide 8 GEOSS Common Infrastructure AIP Phase 1 Results in 2007 • 64 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 AI Pilot Development Approach Participation AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Concept Development Participation Call for Participation Updates for each step Architecture Documentation Continuous interaction with external activities Participation Kick-off Workshop Participation Development Activities Baseline Operational Baseline and Lessons Learned for next evolutionary spiral Participation Persistent Operations (AR-07-01) 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. CFP Architecture – Component Types Client Tier GEO Web Site GEOWeb Web GEO GEO Web Portal Portal Portal Community Portals Business Process Tier GEOSS Registries Components Client Applications GEOSS Clearinghouse Services Alerts/Feeds Servers Portrayal Servers Workflow Management Infrastructure Registries Processing Severs Other Services Standards Requirements Best Practices Community Catalogues Access Tier GEONETCast Product Access Services Sensor Web Services Model Access Services Other Services GEOSS Registries Interaction UDDI ebRS Z39.50/ OGC JAXR SRU CSW Web UI Z39.50/ SRU Web UI GEOSS Standards Registry GEOSS Components offer GEOSS Component and Service Registry GEOSS Services expose GEOSS Standards reference may become nominate U.S.A. GEO Members and Participating Organizations GEOSS Special Arrangements External Standards Bodies IEEE SIF Subject Matter Experts 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-07-03 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-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 AI Pilot Development Approach Participation AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Concept Development Participation Call for Participation Updates for each step Architecture Documentation Continuous interaction with external activities Participation Kick-off Workshop Participation Development Activities Baseline Operational Baseline and Lessons Learned for next evolutionary spiral Participation Persistent Operations (AR-07-01) AIP Phase 2 Master Schedule Architecture Workshop CFP Release Announcement CFP Clarification Telecon CFP Responses for Kickoff due AIP-2 Kickoff Workshop Status & Interim results to GEO Plenary AIP-2 results transition to operations February 2008 26 June 2008 18 July 2008 1 September 2008 25-26 September 2008 November 2008 1st quarter of 2009 Potential Milestones for AIP-2 AIP-2 Kickoff Workshop 25-26 September 2008 Key design decisions complete: Some posted in Best Practice Wiki November 2008 Scenario storyboards developed December 2008 Service registration Complete Scenario Testing complete; Screen captures Operational baseline defined AIP-2 results transition to operations January 2009 February 2009 March 2009 1st quarter of 2009 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 Time Topic Speaker 9:00 Introduction George Percivall 9:10 Welcome to NCAR/UCAR Dr. Richard Anthes, UCAR President 9:20 Context of AIP, GCI, CFP Process George Percivall 9:50 End-to-end use case Doug Nebert 10:30 Refreshment Break 10:45 Session synopsis *11 11:50 logistics for breakouts 12:00 Lunch Session leads