1. GEOSS Architecture Implementation Pilot, Phase 2 (AIP-2)
George Percivall,
Open Geospatial Consortium
GEO Task AR-09-01b Task POC
11 August 2009

2. GEOSS connects Observations to Decisions
DRAFT ver 14 09/04/07
GEOSS connects Observations to Decisions 2
DRAFT ver 14 2

3. GEOSS Interoperability Arrangements - From the GEOSS 10 Year Plan Reference Document -
Interoperability through open interfaces
Interoperability specifications agreed to among contributing systems
Access to data and information through service interfaces
Open standards and intellectual property rights
GEOSS adopting standards; agreed upon by consensus, preference to formal international standards
GEOSS will not require commercial or proprietary standards
Multiple software implementations compliant with the open standards should exist
Goal is that at least one of the implementations should be available to all implementers "royalty-free"

4. Elaboration of GEOSS Architecture
SBA Tasks,
UIC
User
Needs,
Scenarios
requirements
Design,
Develop,
Deploy
Architecture
Implementation
Pilot (AIP)
Task AR-09-01b
support
Operational
Capability
GEOSS Common
Infrastructure (GCI)
Task AR-09-01a
persistent
implementation
The architecture of the AIP is based on meeting the user needs and community scenario requirements as recommended by the SBA tasks of GEO and the UIC. One of the main outcomes of the pilot is then to feed into and augment the operational capability of the GEOSS Common Infrastructure, which in turn supports the operational needs of the users.
A Call for Participation (CFP) in the GEOSS Architecture Implementation Pilot, Phase 2 was announced by the GEO Secretariat on 30 June To date, 37 responses have been received.
The CFP remains open for the duration of AIP-2.
The KO was held in Boulder Colorado, USA, Sep Eighty five (85) persons attended the workshop over the two days.
The AIP-2 Development phase will be conducted in 9 wgs.
The 4 Community Working Groups will develop Scenarios that define the user objectives and the steps in the users decision process.
The 5 Transverse Technology Working Groups are developing Use Cases that define how GEOSS Interoperability Arrangements are used to support the steps in the user Scenarios.
AIP-2 plans to be completed in March 2009 with these results: 1) Demonstrations of the user scenarios; 2) Transition of select services to persistent operations, and 3) Select reports provided to the GEOSS Best Practices Registry.
AIP-2 CFP Responses (37 to date)
ACRF EuroCryoClim NASA World Wind
BKG GEONETCast NOAA/NASA GOES-R and GMU CSISS
Caribbean Flood Team GEO Grid NOAA IOOS
CIESIN GEO-Ukraine NOAA NCDC
CNES and ERDAS Giovanni NOAA SNAAP
Compusult ICAN Noblis
EPA AirNow ICT4EO Northrop Grumman
ERDAS Titan INCOSE Spot Image
ESA IP3 SURA/NIMSAT/GoMOOS
ESIP AQ Cluster ISPRA USGS
ESRI JAXA VIEWS
ESRI Canada Mines Paris Tech Washington University in St. Louis

5. GEO Task AR-09-01b 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
Consistent with that, Task AR 09-01b is defined as: highlighting the development and testing of contributed components in a pilot setting, the leveraging of the GEOSS Common Infrastructure portals and clearinghouses, doing that via interoperability arrangements and serving the SBAs.

6. AIP Phase 1 Results – Early 2008
Elements of the GEOSS Common Infrastructure (GCI) – Initial Operating Capability established
Effective development process for GEO
CFP, Kickoff, Execution, etc.
Approximately 120 organizations participated
Methods for international coordination
Prepared “Architecture Implementation Report”
10 Demonstrations of Initial Operating Capability
AI Pilot has broad international participation that could only have occurred with GEO.
High interest & momentum to support GEOSS.
Slide 6
The first AIP ended in early 2008 where approximately 120 organizations participated to contribute to the establishment of the Initial Operating Capability of the GEOSS Common Infrastructure which were demonstrated in ten videos available online and on dvds. 6

7. AIP Phase 2 Themes Augment the GEOSS Common Infrastructure
Emphasize SBAs identified by UIC/ADC collaboration
Promote "persistent exemplars”
Elaborate GEOSS Architecture
Scenarios and Use Cases
Service and Component types
Interoperability Arrangements
Slide 7
The augmentation of the GEOSS Common Infrastructure is based on meeting the needs of the SBAs identified by UIC/ADC collaboration. Some of those components will be nominated as persistent examplars. And finally to elaborate the GEOSS architecture.

8. AI Pilot Development Approach
Participation
AR-09-01b 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-09-01a)
Operational Baseline and Lessons Learned for next evolutionary spiral
The pilot development approach is a evolutionary spiral waterfall approach that relies heavily on community participation and feeds into task AR-09-01a and the next evolutionary spiral.

9. AIP Phase 2 Master Schedule
AIP-2 CFP Announced
June 2008
Kickoff Workshop at NCAR
September 2008
Scenarios and Use Cases defined
January 2009
Demo Capture Workshop
4-5 May 2009
Finalize AIP-2 deliverables
1st Half of 2009
AIP-2 results transition to operations
2nd Half of 2009
For Phase 2, the schedule was as follows

10. AIP-2 CFP Responses (37) 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
Transverse Tech WGs
Disaster Response
Climate Change and Biodiversity
Renewable Energy
Air Quality and Health
Portals & Application Clients
Clearinghouse, Catalogues, Registries and Metadata
Access Services: products, sensors, models
Workflow and Processing
Test Facility for Service Registration

13. SBA-to-SoA Process 1. SBA Scenarios 2. Enterprise Models 3.4.
Deployment
Plan 1.
SBA Scenarios 2.
Enterprise
Models 3.
Engineering
Design
Use Cases
Component Types
Information Objects
Optimize
Specify

14. SBA-to-SoA Process Artifacts

15. Scenarios and Use Cases
Transverse Use Cases support Community Scenarios
Scenarios: 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: reusable service oriented architecture
Use cases for discovery, data access, etc
Utilize Interoperability Arrangements
Use Cases developed by Transverse Technology WGs

16. SBAs for AIP-2 Scenarios
Energy SBA:
consulting company looking for the best place to sit a solar power plant on the other hand.
Health SBA:
Predict and analyze effect of smoke plumes on Air Quality
Biodiversity SBA:
Biodiversity change with climate change
Disaster Management SBA:
Forecasts, observations, and derived maps to support all phases of the disaster cycle

17. AIP-2 Use Case Diagram

18. AIP-2 Augmenting GCI
GEOSS
Clearinghouses
GEO
Web Portals
GEOSS Common
Infrastructure
Components
& Services
Standards and
Interoperability
Best Practices
Wiki
User Requirements
Registries
Main GEO
Web Site
Registered Community Resources
Community
Portals
Client
Applications
Client Tier
Business Process Tier
Catalogues
Alert
Servers
Workflow
Management
Processing
Access Tier
GEONETCast
Product Access
Sensor Web
Model Access
Test Facility
Mediation
So from a client tier perspective, augment the GCI via the contribution of community portals supporting specific communities of practice and stand-alone applications that can leverage the GCI. On the business Process level, we’ve focused on community catalogs (including WAFs) and workflow and processing services. And test facility which was used to test the services by the partipants. Finally various access tier components at the bottom.

19. Engineering Components and Interoperability Arrangements

20. Brokers Provide GEOSS Interoperability
Registries, Clearinghouse & Catalogues
Broker
Institutional
Data
Provider
Broker provides access when institutional policies and firewalls currently don’t use GEOSS Interoperability Arrangements

21. Phasing of Test, Integration and Demo
Scenario
Development
Update
Use Case
Development
Update
Resource
Registration
1st Call
2nd Call
Test Log ready
Use Case testing – led by clients
Unit Test Period1
Unit Test Period 2
Scenario
Testing
Storyboards
Scenario Testing
Scenario
Capture
Demo Capture Event
JAN
FEB
MAR
APR
MAY

22. AIP-2 Deliverables (GEO Task AR-09-01b)
Demonstrations
Demonstration of community Scenarios implemented through transverse Use Cases
Demonstrations to be recorded and made available via WWW
Persistent Exemplars
Registered services (‘continuous operation’) with 99% availability (~7 hours down time a month); on a reliable network; plan for performance scaling
Nomination to operational task (AR-09-01a)
Engineering Reports
To be considered for GEOSS Best Practice Registry
Community Scenarios
Transverse Technology Use Cases
AIP-2 Summary Report

23. AIP-2 Document Tree GEOSS 10 Year Plan
GEOSS 10 Year Plan Reference Document
Strategic & Tactical Guidance Documents
GCI IOC Task Force
Documents
AIP Architecture (CFP Annex B)
SIF
Documents
AIP-2 Summary
AIP-2 SBA Scenario
ERs
AIP-2 Unified Modeling ER
AIP-2 Use Cases ER
AIP-2 Transverse Technology ERs
SBA/CoP AIP Scenarios
SBA/CoP AIP Scenarios

24. Persistent Exemplars Criteria to be a persistent exemplar
Registered in Component and Service Registry (CSR) as “Continuously Operational”
Accessible through a GEOSS Interoperability Arrangement that is an international standard.
Level of Service: Available >99% of the time (~7 hours downtime/month); Adequate network bandwidth and hardware for performance
269 services met criterion #1 as of 2 July 2009,
Currently assessing criteria #2 and #3

25. AIP-2 Demonstration Videos on-line
AIP-2 Demonstration Videos on-line

26. References GEO earthobservations.org
GEO Architecture Implementation Pilot
GEOSS registries and SIF
geossregistries.info
George Percivall