Presentation is loading. Please wait.

Presentation is loading. Please wait.

GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR-07-02 Point of.

Similar presentations


Presentation on theme: "GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR-07-02 Point of."— Presentation transcript:

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

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

3 Slide 3 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”

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

5 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

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

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

8 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 AIP development process to all interested parties Slide 8

9 Phase 2 Goals Systematic registration of Components and Services Support of registered standards by offerings Quality and availability of services, particularly core services Integrating data /services towards additional SBA application domains Strengthening the use of the Web Portals to access and integrate all GEOSS resources Improving the interaction of the GEOSS Web Portals, Registries, and Clearinghouse Focus on limited set of “well-known” combinations and versions of protocols and content standards Developing a basic EO metadata record for GEOSS-wide use Adding Sensor Web protocols and data types Increasing support for workflows and event - notification handling Slide 9

10 GEO Web Site Client Tier Business Process Tier Access Tier GEO Web Portal 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

11 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 11

12 AIP-2 CFP Responses (33 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 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

13 AIP-2 Kickoff Sessions 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

14 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

15 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

16 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

17 AIP Phase 2 Master Schedule Architecture Workshop February 2008 CFP announced 30 June 2008 CFP Clarification Telecon 18 July 2008 CFP Responses for Kickoff due 1 Sept 2008 Kickoff workshop Sept 2008 Status to GEO Plenary November 2008 Transition to operations 1st quarter of 2009


Download ppt "GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall Open Geospatial Consortium Task AR-07-02 Point of."

Similar presentations


Ads by Google