Initial Operating Capability Task Force (IOCTF)

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

• Agenda
• Role of AIP to elaborate GEOSS Architecture
• Optimizing SoA through Scenarios, Use Cases,
  Components, and Interoperability Arrangements
• Deliverables Engineering Reports, Persistent
  Exemplars, Demonstration Videos

3
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
4
GEO Task AR-09-01bArchitecture 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 4
5
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 5
6
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 6
7
(No Transcript)
8
(No Transcript)
9
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

• 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

• GEONETCast
• GEO Grid
• GEO-Ukraine
• Giovanni
• ICAN
• ICT4EO
• INCOSE
• IP3
• ISPRA
• JAXA
• KDDI
• Mines Paris Tech
• NASA World Wind

10
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

11
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

12
(No Transcript)
13
SBA-to-SoA Process Artifacts
14
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

15
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

16
AIP-2 Use Case Diagram
17
(No Transcript)
18
Engineering Components and Interoperability
Arrangements
19
Brokers Provide GEOSS Interoperability
Registries, Clearinghouse Catalogues
Broker
Institutional Data Provider
Broker provides access when institutional
policies and firewalls currently dont use GEOSS
Interoperability Arrangements
20
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

21
AIP-2 Document Tree
GEOSS 10 Year Plan
GEOSS 10 Year Plan Reference Document
AIP Architecture(CFP Annex B)
Strategic Tactical Guidance Documents
GCI IOC Task Force Documents
SIF Documents
AIP-2Summary
AIP-2 Unified Modeling ER
AIP-2 SBA Scenario ERs
AIP-2Use Cases ER
AIP-2 Transverse Technology ERs
SBA/CoP AIP Scenarios
SBA/CoP AIP Scenarios
22
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 gt99 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

23
http//www.ogcnetwork.net/pub/ogcnetwork/GEOSS/AIP
2/index.html
AIP-2 Demonstration Videos on-line
24
References

• GEO
• earthobservations.org
• GEO Architecture Implementation Pilot
• www.ogcnetwork.net/AIpilot
• GEOSS registries and SIF
• geossregistries.info

George Percivall percivall_at_myogc.org