1. George Percivall September 2008
GEO Architecture and Data Committee Task AR Architecture Implementation Pilot
George Percivall
September 2008

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. 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”
AI Pilot has broad international participation that could only have occurred with GEO.
High interest & momentum supporting GEOSS vision.

4. AI Pilot Development Approach
Participation
AR Architecture Implementation Pilot
Evolutionary Development Process
Concept
Development
Participation
Continuous interaction with external activities
Call for
Participation
Participation
Kick-off
Workshop
Architecture
Documentation
Updates for each step
Baseline
Participation
Development
Activities
Participation
Persistent
Operations
(AR-07-01)
Operational Baseline and Lessons Learned for next evolutionary spiral

5. 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  June 2008
Responses for Kickoff 1 Sept 2008

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

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

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

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

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

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

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

13. AIP Phase 2 Master Schedule
Architecture Workshop February 2008
CFP announce  June 2008
CFP Clarification Telecon July 2008
CFP Responses for Kickoff due Sept 2008
Kickoff workshop  Sept 2008
Status & Interim results to GEO Plenary November 2008
AIP-2 results transition to operations st quarter of 2009