GEO Task AR Architecture Implementation Pilot. George Percivall, OGC December 2008 GEOSS Workshop XXV

Transcription

1 GEO Task AR Architecture Implementation Pilot George Percivall, OGC December 2008 GEOSS Workshop XXV

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 in support of GEOSS Societal Benefit Areas Slide 2

3 Elaboration of GEOSS architecture SBA Tasks, UIC support User Needs, Scenarios requirements Design, Develop, Deploy AR-07-02, Architecture Implementation Pilot (AIP-I, -II) AR-07-01, GEOSS Common Infrastructure (GCI) Operational Capability persistent implementation

4 AIP Phase 1 results in 2007 Demonstrated effective development process: CFP, Kickoff, Execution, etc. Approximately 120 organizations Established organization communication methods For international coordination Produced Screencasts 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 4

5 AIP Phase 2 Themes Augment the GEOSS Common Infrastructure Emphasize SBAs identified by UIC/ADC collaboration Develop "persistent exemplars Elaborate GEOSS Architecture Scenarios and Use Cases Service and Component types Interoperability Arrangements Slide 5

6 AI Pilot Development Approach Participation AR Architecture Implementation Pilot Evolutionary Development Process Participation Participation Continuous interaction with external activities Updates for each step Participation Participation Baseline Operational Baseline and Lessons Learned for next evolutionary spiral

7 AIP Phase 2 Master Schedule AIP-2 CFP Announced 26 June 2008 CFP Responses for Kickoff due 1 September 2008 Kickoff Workshop at NCAR September 2008 Status to GEO Plenary November 2008 Scenario demonstration capture February 2009 AIP-2 results transition to operations 1st quarter of 2009

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

9 CFP response: Why participate in GEO AIP? Better awareness of community interoperability efforts Better understanding and use of proposed GEOSS 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 Slide originally from Shawn McClureCIRA, Colorado State University

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

11 AIP-2 Kickoff Workshop, September 2008 At NCAR Mesa Laboratory, Boulder, Colorado, USA 85 Participants 3 Plenary Sessions 12 Parallel Sessions based on CFP Responses Established Working Groups; and Development Plan

12 AIP-2 Working Groups (WGs) Community WGs Disaster Response Climate Change and Biodiversity Renewable Energy Air Quality Transverse Technology WGs: Clearinghouse, Catalogues, Registries and Metadata Access Services: products, sensors, models Workflow and Alerts Portals and Application Clients Test Facility for service registration

13 Community WG Leaders Disaster Response Stuart Frye, NASA; Didier Giacobbo, Spot Image Health SBA: Air Quality David McCabe, EPA Frank Lindsay, NASA; Stefan Falke & Rudy Husar, Washington Univ. Biodiversity and Climate Change Stefano Nativi, CNR; Gary Geller, NASA/JPL Energy SBA Thierry Ranchin & Lionel Menard, Mines Paris Tech; Ellsworth LeDrew, Univ Waterloo;

14 Transverse Technology WG Leaders Catalogues, Clearinghouse, Registries and Metadata Doug Nebert, USGS; Josh Lieberman OGC/ Traverse; Kengo Aizawa, JAXA; Ted Haberman, NOAA Workflow and Alerts Satoshi Sekiguchi, AIST; Eugene Yu, GMU; Test Facility for service registration Mauro Semerano, ESA Portals and application clients Nadine Alameh, OGC/ MobileAps; Herve' Caumont, OGC/ ERDAS Access Services: products, sensors, models Herve' Caumont, OGC/ ERDAS; Glenn Rutledge NOAA, Hans Peter Plag, UNR; Anwar Vahed, ICT4EO; Luis Bermudez SURA;

15 AIP Communication and Collaboration Telecons Plenary telecon Tuesdays WG telecons as defined by WG leaders list-servers One plenary list One list per work group Collaborative web sites Development process and cross WG topics on WG Workspaces on Google Sites

16 Scenarios and Use Cases Transverse Use Cases support Community Scenarios Scenarios provide end user view of the value of GEOSS Focused on topics of interest to a community Occur in a geographic Area of Interest (AOI) Steps in a scenario are Use Cases Scenarios developed by Community WGs Use Cases allow reuse of GEOSS service oriented architecture Use cases for discovery, data access, etc Utilize Interoperability Arrangements Use Cases developed by Transverse Technology WGs

17 Community Scenarios - Draft Air Quality and Health: Use of earth observations to inform three decision-makers: policy-maker, AQ compliance manager, and the public Disasters: Disaster cycle for Flooding events Biodiversity and Climate Change Polar scenario(s) CC impact on Pikas in North America; Protected areas monitoring; Renewable Energy Site selection process for solar and wind energy

18 Transverse Technology Use Cases - DRAFT Portals and Application Clients: Discovering, saving Context Discovery of components and services in clearinghouses Discovery and display of CAP alerts/rss feeds Semantic search for specific communities Authentication of users Referral from GeoPortal to community portal/client Visualization of EO products Ordering of products Workflow and Alerts: constructing a workflow executing a workflow Clearinghouse, Catalogue, Registers & Metadata Assess Resources Search Services Publish Metadata System Search Clearinghouse for Resources Harvest Metadata Registration Access Services accessing a dataset, accessing a model, accessing a sensor commanding a sensor Test Facility: registering a test tool testing a service

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

20 AIP-2 Development Schedule AIP-2 Kickoff Workshop September 2008 Community Scenarios - draft November 2008 Transverse Tech Use Cases - draft November 2008 Interim Design Review (Valencia Spain) 2 December 2008 Scenario storyboards developed 16 January 2009 Service registration Complete 16 January 2009 Scenario Testing complete; Screen captures February 2009 Engineering Reports Complete; post some as Best Practices March 2009 Operational baseline defined March 2009 AIP-2 results transition to operations 1st quarter of 2009

21 AIP Phase 2 Themes Augment the GEOSS Common Infrastructure Emphasize SBAs identified by UIC/ADC collaboration Develop "persistent exemplars Elaborate GEOSS Architecture Scenarios and Use Cases Service and Component types Interoperability Arrangements Slide 21