Presentation is loading. Please wait.

Presentation is loading. Please wait.

GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall September 2008.

Similar presentations


Presentation on theme: "GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall September 2008."— Presentation transcript:

1 GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall September 2008

2 Slide 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 …in support of 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 Initial results established in 2007 64 Components & 75 Services registered (21 Nov 07) –Process and components for registration; SIF User interfaces to services –GEO Web Portals (3), Community Portals (27) and Application Clients (13) Several organizations capable of providing –GEO Web Portal solutions –GEOSS Clearinghouse solutions

5 DevelopmentActivities Kick-offWorkshop Call for Participation ConceptDevelopment PersistentOperations(AR-07-01) Participation ArchitectureDocumentation Updates for each step Baseline AR-07-02 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

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

8 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

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

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.

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

14 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

15 AIP-2 Kickoff – SBA SCENARIOS Disaster Response SBA : –Ron Lowther Ronald.Lowther at ngc.com Northrop Grumman –Didier Giacobbo Didier.Giacobbo at spotimage.fr Spot Image –Stuart Frye Stuart.Frye at nasa.gov Caribbean Flood Team Health SBA: Air Quality : –David McCabe, McCabe.David at epamail.epa.gov ESIP AQ Team –Frank Lindsay, francis.lindsay-1 at nasa.gov ESIP AQ Team –Stefan Falke, stefan at wustl.edu ESIP AQ Team –Rudy Husar rhusar at me.wustl.edu ESIP AQ Team Biodiversity and Climate –Stefano Nativi nativi at imaa.cnr.it IP3 Response –One other Energy SBA –Thierry Ranchin thierry.ranchin at ensmp.fr Mines Paris Tech –Ellsworth LeDrew ells at watleo.uwaterloo.ca UIC Co-Chair

16 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 PlenaryNovember 2008 AIP-2 results transition to operations 1st quarter of 2009


Download ppt "GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot George Percivall September 2008."

Similar presentations


Ads by Google