GOESR BAA Raytheon TIM

1
Opportunities for Industry in GEOSS Design and
Development
AMS Corporate Forum 10 March 2006
Carroll A. Hood GEOSS Chief Architect
2
Outline

• Background
• The GEOSS Challenge
• GEOSS Architecture
• GEOSS Value Streams
• GEOSS Complexity
• Opportunities for Industry
• Business Case
• Reference Architecture
• Integrating Legacy Assets
• Unexpected Consequences
• Line of Sight
• Implications of GEOSS Compliance
• Summary
• Key Enablers

3
Background
4
The GEOSS Challenge

• Enable existing Earth and environmental
  observations, data and information systems,
  products and services (assets) to be used for
  applications and activities beyond their primary
  (operational) mission
• Enable environmental and/or geospatial
  perspective to be incorporated into decision
  making for selected social and economic issues
  whenever and wherever it makes sense
• Encourage the development of a value-added market
  for Earth observations data and information
  products and services
• Support capacity building in developing countries
• Provide these capabilities at low marginal cost
  with minimal impact
• Remove unwanted duplication
• Provide an approach for the effective development
  and integration of new assets
• Methodology to identify and prioritize gaps
• Methodology for intelligent evolution of
  capabilities

Current economic climate dictates that we
leverage existing assets as much as practical
5
GEOSS Architecture
6
GEOSS Value Streams
Archive/ Manage Products
Collect Obs
Process Products
Transmit Telemetry
Conduct Primary Mission
Push Products
Information Creation (Supply Side)
Develop Algorithms
Employ R-to-O
Create/ Enable Services
Make Better Informed Decisions
Generate Predictions
Validate Models
Conduct Research
Develop Models
Public Domain/ Market- Driven
Stimulate Value-added Market
Research/ Modeling
Develop DST
Employ R-to-O
Stimulate Capacity Building
Exploit Decision Support Tools
Access (Pull) Products
Discover Products
Visualize Products
Impacts/ Outcomes
Information Exploitation (Demand Side)
7
GEOSS Value Streams (Archaic, Naive View)
Archive/ Manage Products
Collect Obs
Process Products
Transmit Telemetry
Conduct Primary Mission
Push Products
Information Creation (Supply Side)
Develop Algorithms
Employ R-to-O
Create/ Enable Services
Make Better Informed Decisions
Generate Predictions
Validate Models
Conduct Research
Develop Models
Public Domain/ Market- Driven
Stimulate Value-added Market
Research/ Modeling
Develop DST
Employ R-to-O
Stimulate Capacity Building
Exploit Decision Support Tools
Access (Pull) Products
Discover Products
Visualize Products
Impacts/ Outcomes
Information Exploitation (Demand Side)
Government
Academia
Private Sector
8
GEOSS Value Streams (Realistic View)
Archive/ Manage Products
Collect Obs
Process Products
Transmit Telemetry
Conduct Primary Mission
Push Products
Information Creation (Supply Side)
Develop Algorithms
Employ R-to-O
Create/ Enable Services
Make Better Informed Decisions
Generate Predictions
Validate Models
Conduct Research
Develop Models
Public Domain/ Market- Driven
Stimulate Value-added Market
Research/ Modeling
Develop DST
Employ R-to-O
Stimulate Capacity Building
Exploit Decision Support Tools
Access (Pull) Products
Discover Products
Visualize Products
Impacts/ Outcomes
Information Exploitation (Demand Side)
Government
Academia
Private Sector
9
GEOSS Complexity A System of Systems of Systems
IEOS
GOOS
Geographic Coverage
GEOSS Global Earth Observation System of
Systems IEOS Integrated Earth Observation
System GOOS Global Ocean Observing System IOOS
Integrated Ocean Observing System RCOOS
Regional Coastal Ocean Observing System SECOORA
Southeast Coastal Ocean Observing Regional
Association CARO-COOPS Carolinas Coastal Ocean
Observation and Prediction System
10
Opportunities for Industry
11
The Problem Space/Solution Space

• Given the GEOSS Problem Space
• Reliance on integrating legacy assets
• No clear cut way to delineate roles and
  responsibilities
• Added complexity of systems of systems of systems
• What is the best way forward???
• Some dimensions of the Solution Space
• Creating a Viable Business Case and Business
  Model
• Using Reference Architectures
• Designing a Flexible Methodology for Integrating
  Legacy or New Assets into an SOA
• Enabling Unexpected Consequences
• Understanding Line of Sight in an Outcome-based
  Initiative
• Addressing the Implications of GEOSS Compliance
  on System Development

12
Importance of a Business Case

• GEOSS is being sold on the basis of the
  socioeconomic value of improved decision making
  in key issues areas
• Recognizes the power of an integrated geospatial,
  environmental perspective
• Lots of anecdotes justification is harder to
  come by
• The economic impact of a secondary Value-added
  market has not received the same amount of
  attention
• Look at the Internet as an example
• GEOSS Evolution and Grand Convergence (Dr. C.
  Kennel, SIO)
• A global system will succeed best if these two
  benefits extend universally.
• Capacity Building key to developing traction
  internationally
• Who better than the Private Sector to assist in
  the development of viable Business Case and
  realistic Business Models?
• We can lead but shared ownership requires buy-in

Make Better Informed Decisions
Stimulate Value-added Market
Stimulate Capacity Building
Impacts/ Outcomes
Need Government (Service to Citizens) and Venture
(Value Added) Investment
13
Reference Architecture

• How do you influence the evolution of legacy
  assets or the development of new assets?
• Reference Architecture (RA) Abstraction of an
  architecture of a GEOSS asset with common
  characteristics and quality attributes
• Tailorable
• Reduces Risk
• Encourages Reuse
• What is it and how it fits into the larger
  picture NOT how to implement

RAs provide a blueprint for system evolution but
do not impact creativity and innovation in
implementation
14
Characteristics of an RA

• Structure
• Entities
• Internal/External Interfaces
• Behaviors
• Global Rules
• Standards
• Constraints

Alliance Workshop in Oct 2005 provided
Opportunity to Develop RAs for specific threads
in the GEOSS Value Steam http//www.strategies.org
/Alliance/GEOSS_Architecture/Presentations.html
15
Proposed GEOSS Standards

• Service Interface WSDL, ebXML, UML, CORBA
• Syntax XML, ASN.1
• Semantics ISO 11179
• Archiving WDCs
• Search ISO 23950
• Geospatial Services OGC (WMS,WCS, WFS)

16
Levels of Integration
Legacy Viewer 1
Legacy Viewer 2
Legacy Viewer 3
Web Portal
Refactored Legacy App
Native App
Level 4 New Application created within an SOA
Framework
Legacy App 1
Legacy App 2
Legacy App 3
RA
Workflow Manager
Legacy Store 1
Legacy Store 2
Legacy Store 3
Integration Framework
Security
Level 3 Isolated and Refactored Application
New Store
RA
RA
Legacy Store
Level 2 Application Resource Adapter
Level 0 ICD
Level 1 Data Resource Adapter
Integrating Assets One Size Does NOT fit
All (NWLON Example to Follow)
17
NWLON Baseline Configuration
GOES Satellite
NTP4 host
NOS Encoded Data
NWLON Database
NOS Encoded Data
Observations/ Predictions
NWS Gateway
NOS Encoded Data
TRANSFORM/QC host
CREX
NWS Gateway
SSMC II
CO-OPS Products
CO-OPS WWW Server
SSMC IV
CREX
NWLON Station
Wallops Island, VA
To DB
AWIPS
Request
National Water Level Observation Network
Query
Render
Product
18
Level 0 Integration Interface Description
GOES Satellite
NTP4 host
NWLON ICD
NOS Encoded Data
NWLON Database
NOS Encoded Data
Observations/ Predictions
NWS Gateway
NOS Encoded Data
TRANSFORM/QC host
CREX
NWS Gateway
SSMC II
CO-OPS Products
CO-OPS WWW Server
SSMC IV
CREX
NWLON Station
Wallops Island, VA
To DB
AWIPS
Request
National Water Level Observation Network
Query
Product
Render
19
Level 1 Integration Transparent Data
Discovery/Access
Web Portal
Services
GOES Satellite
Data Resource Adapter Ontology, SQL Query, XML
Schema manager
NTP4 host
RA
NOS Encoded Data
NWLON Database
NOS Encoded Data
Observations/ Predictions
NWS Gateway
NOS Encoded Data
TRANSFORM/QC host
CREX
NWS Gateway
SSMC II
CO-OPS Products
CO-OPS WWW Server
SSMC IV
CREX
NWLON Station
Wallops Island, VA
To DB
AWIPS
Query
Request
National Water Level Observation Network
Render
Product
20
Level 2 Integration Ubiquitous Application
Access
Application Resource Adapter QC Front End
Web Portal
Services
GOES Satellite
Data Resource Adapter Ontology, SQL Query, XML
Schema manager
NTP4 host
RA
NOS Encoded Data
NWLON Database
Observations/ Predictions
NOS Encoded Data
NWS Gateway
RA
NOS Encoded Data
TRANSFORM/QC host
CREX
NWS Gateway
SSMC II
CO-OPS WWW Server
CO-OPS Products
SSMC IV
CREX
To DB
NWLON Station
Wallops Island, VA
AWIPS
Query
Request
National Water Level Observation Network
Render
Product
21
Level 3 Integration Loosely Coupled SOA
Web Portal
Services
GOES Satellite
Refactored Application Ontology, SQL Query, XML
Schema Service
NTP4 host
NOS Encoded Data
NWLON Database
Observations/ Predictions
NOS Encoded Data
NWS Gateway
Refactored Application
Refactored Application
NOS Encoded Data
Refactored Application QC Service
TRANSFORM/QC host
CREX
NWS Gateway
SSMC II
CO-OPS Products
CO-OPS WWW Server
SSMC IV
CREX
NWLON Station
Wallops Island, VA
To DB
AWIPS
Query
Request
National Water Level Observation Network
Render
Product
22
LCCE Analysis Cost/Benefit Trade Space
Levels of Integration Enable Smart Decisions
Regarding IOOS Implementation
23
Building for Unexpected Consequences
Underscores the requirement for Rich
Metadata/Full Provenance
24
Line of Sight
Some aspects fall outside the enterprise (Not a
value judgment)
Goal
Product Development
Modeling/Simulation
Basic Research
Resource Adjudication
Societal Benefit
Enterprise Optimization
Local Sub-optimization
? Often Requires ?
25
Line of Sight (caveat)
Some aspects fall outside the enterprise (Not a
value judgment)
Goal
Product Development
Modeling/Simulation
Basic Research
Resource Adjudication
Societal Benefit
x
Line of Sight can Expand, but Expansion is not
Preordained!
26
Implications on System Development
27
Summary
28
Key Enablers

• Building the Infrastructure
• Business Case
• Stakeholder participation in evolution of assets
• Robust Systems Engineering Approach
• Reference Architectures
• Emphasis on the evolution and integration of
  legacy assets
• Enterprise Optimization (Line of Sight)
• Minimize Life Cycle Costs
• Syntactic/Semantic Interoperability (required to
  break down stovepipes)
• XML Schema
• Ontologies
• Information Assurance
• Multi-level Security
• Authentication
• QA/QC (known)
• Cost trade for different level of integration

• Exploitation of Information/Services
• Business Case
• Stakeholder participation in definition of
  services
• Focused RD (Line of Sight)
  (key R? O element)
• Algorithms
• Modeling
• Decision Support Tools
• Loosely Coupled SOA
• Services will be required to enable exploitation
  of integrated assets
• Public Domain (Service to Citizens)
• Value Added
• Rich Metadata and Orchestration of Services
  enable unexpected consequences
• Implications on System Development
• Robust Education, Outreach, In-reach

Key Enablers should define a Target Rich set of
Opportunities for the Private Sector
29
Summary

• Do not expect a single large procurement
• Opportunity to help existing assets to evolve
  toward GEOSS-level interoperability
• Selected new assets may be procured to fill key
  gaps
• System of systems evolution governed by
  enterprise architecture/systems engineering
  approach and constrained by legacy inertia
• Both top-down and bottoms-up forcing functions
• Industry needs to understand where and how its
  products and services fit within the GEOSS Value
  Streams
• Viable Business Case needed to stimulate
  investment
• Must understand cost/benefit trade for different
  levels of integration
• Must strive to facilitate unexpected
  consequences
• Must understand the concept of line of sight
• There is responsibility to make assets useful
  beyond their original intent
• Key enablers define areas ripe for near-term
  procurement activity