Difference between revisions of "NASA ROSES08: Regulatory AQ Applications Proposal- Technical Approach"

From Earth Science Information Partners (ESIP)
Line 1: Line 1:
 
{{NASAROSES_AQ_Backlinks}}<br>
 
{{NASAROSES_AQ_Backlinks}}<br>
 +
 +
== Summary ==
 +
A description of the key, central objectives of the proposal in terms understandable to a nonspecialist;
 +
 +
A concise statement of the methods/techniques proposed to accomplish the stated research objectives; and
 +
 +
* Fan-in/Fan-out Architecture
 +
* Service Oriented Architecture
 +
* Application to primary and reused in secondary DSS's
 +
 +
 +
A statement of the perceived significance of the proposed work to the objectives of the solicitation and to NASA interests and programs in general.
 +
* Better air quality management decisions
 +
* Wider distribution of NASA products
 +
* Demonstration of GEOSS concept
 +
 +
 +
 
== Architecture ==
 
== Architecture ==
 
The design philosophy is of fan in-fan out. Any data is applicable to multiple benefit areas. Any benefit area needs multiple data.  
 
The design philosophy is of fan in-fan out. Any data is applicable to multiple benefit areas. Any benefit area needs multiple data.  

Revision as of 00:05, June 16, 2008

Air Quality Cluster > Applying NASA Observations, Models and IT for Air Quality Main Page > Proposal | NASA ROSES Solicitation | Context | Resources | Schedule | Forum | Participating Groups

Summary

A description of the key, central objectives of the proposal in terms understandable to a nonspecialist;

A concise statement of the methods/techniques proposed to accomplish the stated research objectives; and

  • Fan-in/Fan-out Architecture
  • Service Oriented Architecture
  • Application to primary and reused in secondary DSS's


A statement of the perceived significance of the proposed work to the objectives of the solicitation and to NASA interests and programs in general.

  • Better air quality management decisions
  • Wider distribution of NASA products
  • Demonstration of GEOSS concept


Architecture

The design philosophy is of fan in-fan out. Any data is applicable to multiple benefit areas. Any benefit area needs multiple data.

Primary Decision-Support Systems

  • DataFed - Husar - Exceptional Events. Fan in: 50 States -> 10 EPA Regions -> 1 Federal EPA. Each transmits different pieces of information and we need to determine those pieces.

Exceptional Events are distributed in space, need a wide variety of data and include a variety of people therefore they are good candidates for the modern decision-support systems. Because fan in - fan out data flow architecture is so broad it can help other decision support application areas.

Other Decision-Support Systems

Same fan in - fan out data flow architecture can be used for different decision-support systems.

  • VIEWS - Brett/Shawn - Regional Haze
  • BlueSky - Sean - Smoke
  • BAMS - McHenry - Air Quality Forecasting for the public
  • HTAP - Keating - Hemispheric Transport Policy

Information Sources

Generic Processing Routines and Tools

Exceptional Event DSS

Application to Other DSS's