Get documents about "Interoperable Information System of Systems for HTAP
Document Sample
Interoperable Information System of Systems
for
HTAP
Rudolf B. Husar and Rich Scheffe
With Erin Robinson
Presented at
HTAP Workshop, WMO, Geneva, January 26, 2006
Intercontinental Transport Events have
Influenced AQ Regulations ..and now Policy? –> Air Quality Management
Web-Based Collab. in Virtual Workgroups –> Science, the Process
Near-Real-Time Data Access & Integration –>Technologies and Tools
US-Daily Avg. PM25 Dust:
Seasonal + Events
HTAP Characteristics
• Stakeholders are autonomous countries, organizations
• Diverse perspectives on the issues, solutions
• Pollution sources and impacts are hemispheric
• Information integration is key to success
• Observations and models are ready for integration
The HTAP - GEOSS
• Stakeholders are autonomous countries, organizations
• Diverse perspectives on the issues, solutions
• Recognition of the need to understand, act
• Pollution sources and impacts are hemispheric
• Observations and models are ready for integration
• Information integration is key to success
Hence
GEOSS is a good system model for HTAP
HTAP is a suitable use case for GEOSS
Some Characteristics of System of Systems (SoS)
• Autonomous constituents managed independently
• Independent evolution of each constituent
• Displays emergent (novel, unpredictable) behavior
Summary
There is an „alignment of stars‟ for integrating heterogeneous HTAP data
• System of Systems architecture is suitable for integrating HTAP data
– Standard data access is a key interoperability protocol
– Heterogeneous data can be non-intrusively standardized by mediators
– Service-based software architecture delivers tailored products to diverse uses
• Federated data and shared web-based tools are in use
– DataFed already includes over 100 datasets (emissions, ground, satellite)
– The system has been applied to EPA regulatory development
• However,
– DataFed is just one of the many mediator nodes, but these need to be connected
– Much more data would need to be federated
– HTAP model-data comparison would be an attractive use case
WMO-GAW could be an effective neutral facilitator for global data integration
using GEOSS (system of systems) principles
GEOSS Architecture Framework - DSS for HTAP
HTAP Reports:
Models Model Estimates,
Obs. Evidence
Knowledge into
HTAP Knowledge
the Minds of
into the Minds of
AQ Analysts Policy Makers
HTAP Knowledge
Observations into the Minds of
Policy Analysts
Decisions
Decision Support System
GEOSS
Architecture
Framework
System of Systems: Interoperability
Connecting Machines and People
Interoperability Stack: Key concept of the Web
System components have to be interoperable at each layer
Amplify Individuals
Connect Minds
Open Architecture
Data Standards
Service Based
IP – Internet
Protocol
How do you agree on Interoperability?
Are WCS/WMS Space-Time- What few things must be the same so
Parameter queries that everything else can be different?
Server GetCapabilities Client Ap Ap Ap Ap
Std. Interface
Std. Interface
Capabilities, „Profile‟ p p p p
Back Where? When? What? Front
Which Format?
End End WCS/W
GetData
MS
Data
Query GetData Standards
Where? BBOX OGC, ISO
When? Time T1 T2 OGC, ISO
What? Temperature CF
Format netCDF, HDF.. CF, EOS, OGC
Convergence Protocols
Lets agree on
Space-Time-Parameter
Data Access Query
Protocol
From ‘Stovepipe’ to Federated Architectures
Data Providers Info System Info Users
AIRNow Public
AIRNow
Model Manager
Compliance
DAACs Scientist
Science
• Current info systems are project/program oriented and provide end-to-end solutions
• Part of the data resources of any project can be shared for re-use through DataFed
• Through the Federation, the data are homogenized into multi-dimensional cubes
• Data processing and rendering can then be performed through web services
• Each project/program can be augmented by Federation data and services
Web Services and Workflow for Loose Coupling
Obs. & Models Decision Support System
Std. Interface
Std. Interface
Control
Data Reports
Datasets Data Views Integrated Data Reports
Web Service Interaction Service Chaining & Workflow
Service
Broker
Service Bind Service
User Provider
Collaborative Reporting and Dynamic Delivery
Obs. & Models Decision Support System
Std. Interface
Std. Interface
Control
Data Reports
Datasets Data Views Integrated Data Reports
Analysis Reports: Co Writing -
Information supplied by many Wiki
Needs continuous program feedback
Report needs many authors
Wiki technologies are for collaborative writing
Dynamic Delivery: Screencast
Much of the content is dynamic
Animated presentations are compelling
Movies and screencasts are for dynamic delivery
Model-Data Comparison Workflow Software
VIEWS
Std
I/O
Chemical Data
Ft. Collins, CO Model-
Data Comparison
Workflow
AeroCom
Std
I/O
Chemical Models
Paris, FR
Workflow Flow Program
Lego-like assembly of component
WMS, WCS OGC
Services
Sample of Federated Datasets
• HTAP Model-Obs “Test/Benchmark”ed
– A virtual data center design to meet the needs of the TF HTAP
model intercomparison and evaluation
– Archives of key observations and model data
– Tools for model intercomaprison
Tools..
Analyst Console
User Layout
Imagine…More Shared Global Obs & Models
2007
Global Data & Models
2007++
More Global Data & Models
The Network Effect:
Less Cost, More Benefits through Data Reuse
Programs ask/get Data Orgs Develop Programs Public sets up Orgs
Data
Data
Program
Data Organization
Data Re-Use Program
Network Effect Public
Program Organization
Data
Data Program
Data
Pay only once Less Prog. Cost Less Soc. Cost
Richer content More Knowledge More Soc. Benefit
AeroCom CAPITA
Obs & Obs &
Services Models Model Services
Federated Information System Obs
Other VIEWS
Federations
Observations, Models, Services Models & Services
Agile Information System
Design Principles
Guiding Idea:
System of Systems
GEOSS
Domain of
Interaction
WMO/GAW & Stakeholders
Infrastructure: Methods, Tools:
Internet, Middleware, Standards, Use Cases
Web 2.0
Based on P. Senge et. al, 1994: Architecture of Learning Organizations(Link)
R. Scheffe
Apparent divergences?
Organizations have different missions
NPS
Protect ecosystems, NASA
AQ WQ Explore fundamental
USDA
Protect/optimize Ag Earth System Properties
and forest resources
EPA (Protect human health & envi.
Improve air, water, ecosystem
NOAA CDC
To understand and predict changes To promote health and
in the Earth‟s environment and … quality of life ….
R. Scheffe
Stars aligned?
Confluence again..
Observation technologies
{e.g., satellites}
Collaboration (culture) Computational power
empire building?
Alignment Science, talent
Budgets, agency collaboration {embodied in AQ models
resource/program accountability and young geniuses}
Accountability, ↓ regulatory Information technologies
assessments {e.g., NAS, CASAC} {e.g., data sharing protocols}
Summary
There is an „alignment of stars‟ for integrating heterogeneous HTAP data
• System of Systems architecture is suitable for integrating HTAP data
– Standard data access is a key interoperability protocol
– Heterogeneous data can be non-intrusively standardized by mediators
– Service-based software architecture delivers tailored products to diverse uses
• Federated data and shared web-based tools are in use
– DataFed already includes over 100 datasets (emissions, ground, satellite)
– The system has been applied to EPA regulatory development
• However,
– DataFed is just one of the many mediator nodes, but these need to be connected
– Much more data would need to be federated
– HTAP model-data comparison would be an attractive use case
WMO-GAW could be an effective neutral facilitator for global data integration
using GEOSS (system of systems) principles
Related docs
