GEOSS AIP Generic Smoke Scenario

From Earth Science Information Partners (ESIP)
Revision as of 18:20, January 28, 2008 by Rhusar (talk | contribs) (→‎Summary)

<Back to GEOSS AIP Pilot Scenario

(This page is based on the template provided by GEOSS Architecture Workgroup.) Example Scenario - Energy - Solar Scenario

Summary

Template: Provide a summary of the scenario and the community that the scenario supports.
The communities supported by the scenario are the General Public, Air Quality Regulators, and Atmospheric Scientist.
Template: Identify the specific decisions to be made.

  • Informing and advising the Public
    • General Public Information - Newspaper, TV...
    • Public Health - surface concentration, (American Lung Assoc.)
    • Public Safety - Road visibility (DOT), Aviation visibility (FAA)
  • Air Quality Regulatory Decision-Support
    • Exceptional Event Documentation (State, Regional, Federal)
    • Smoke Transport - Inter-Regional, International, Inter-Continental (LRTP, HTAP)
  • Atmospheric Science Decision Support
    • Smoke Emission Source Characterization
    • Transport Mechanisms, Distances, Spatial-Temporal pattern
    • Kinetic Processes

Template: Provide references for additional information.

All Del.icio.us links tagged Workspace:GEOSS_AIP_AQ_Scenario

<feed url="http://del.icio.us/rss/tag/Workspace:GEOSS_AIP_AQ_Scenario">

  • [{PERMALINK} {TITLE}]

{DESCRIPTION} </feed>

Context and pre-conditions

Template: Identify the actors in the scenario. Actors are any persons involved in the scenario.

  • Data Providers
  • Data Mediators and Processing Centers
  • Data Analysts
  • Decision-Makers: Public, Regulators, Scientists


Template: List, at a summary level, the specific information assumed to be available before the scenario begins.

  • Near-Real Time Monitoring Data from dedicated Surface, Upper Air and Satellite sensors
  • Semi-quantitative information on smoke harvested from Public information sources
  • Initial Model simulations of smoke emission, transport/transformation/removal
  • Integrated Datasets suitable for assimilation into forecast models for improving predictions


Template: List, at a summary level, the specific processing and collaboration functionality assumed needed in the scenario.

  • Identification and accessing the relavent monitoring data from dedicated Surface, Upper Air and Satellite sensors
  • Harvesting the data sources from "other" agencies/organizations, Public contributions of first-hand reports, images, videos...
  • Data sharing and integration functionality would need to include Standard-based, seamless (if possible) data access, registry for finding resources (data and metadata), workflow software for integrating Service Components
  • The Smoke Air Quality Community of Practice would need to be supported by a workspace where the communal resources on the specific smoke event (and smoke in general?) are assembled ... other Decision Support System functionality.
  • Ability to produce near-Realtime reports that characterize the smoke event

Scenario Events

Template: The scenario should be elaborated as a set of steps that result in the creation of decision support products developed in collaboration by the actors.
Template: Use the table to identify the main sequence of events in the scenario. In the course of the scenario you may identify an alternative branch step that could be taken, but then return to the main sequence steps.

  1. Designated and voluntary observers will use the web-based system to monitor the current aerosol situation over North America and beyond.
  2. The monitoring consists of scanning the spatial, temporal aerosol pattern on the Realtime satellite images, surface monitors, as well as the Public Media and private citizen coverage.
  3. Once an ‘interesting’ event appears, the observers will explore the pattern of other peripheral data such as weather pattern, trajectories and other monitors to ascertain the emergence of the natural event.
  4. Throughout the event’s emergence, the observers share their observations and views about the event, in particular the judgment whether the event is sufficiently large to warrant issuing trigger messages.
  5. Given a trigger decision, cascading trigger messages will be issued to different groups that may need to act or who are interested in observing/participating in the community action.
  6. In response to the trigger, more intense monitoring and analysis is initiated.
  7. As the smoke event evolves, a virtual workgroup of analysts summarizes the initial findings, including sources, transport, aerosol pattern and impact in a simple story and picture book (screencast).
  8. During the smoke event, a multiplicity of decisions and actions are executed for Public, Regulatory and Scientific decision makers.
  9. Following the smoke event, the event is evaluated for its impact, consequences and possible retrospective analysis.