GEO Architecture and Data Committee

Task AR-07-02 Architecture Implementation Pilot

George PercivallOpen Geospatial Consortium

Task AR-07-02 Point of Contact

September 2008

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

• …support GEOSS Societal Benefit Areas

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 Capability• Prepared “Architecture Implementation Report”

DevelopmentDevelopmentActivitiesActivities

Kick-offKick-offWorkshopWorkshop

Call for Call for ParticipationParticipation

ConceptConceptDevelopmentDevelopment

PersistentPersistentOperationsOperations(AR-07-01)(AR-07-01)

Participation

Participation

Participation

Participation

ParticipationArchitectureArchitecture

DocumentationDocumentation

Updates for each step

Baseline

AR-07-02 Architecture Implementation PilotEvolutionary Development Process

Operational Baseline and Lessons Learned for next evolutionary spiral

Continuous interaction with external activities

AI Pilot Development Approach

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

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

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

GEO Web Site

Client Tier

Business Process Tier

Access Tier

GEOWeb

Portal

GEOSSRegistries

Services

Components

Standards

GEONETCast OtherServices

ProductAccess

Services

ModelAccess

Services

CommunityPortals

Client Applications

RequirementsCommunityCatalogues

PortrayalServers

WorkflowManagement

ProcessingSevers

OtherServices

GEOSSClearinghouse

SensorWeb

Services

Alerts/FeedsServers

InfrastructureRegistries

CFP Architecture – Component Types

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

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

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

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

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 25-26 Sept 2008

• Status to GEO Plenary November 2008

• Transition to operations 1st quarter of 2009