WRAP TSS Detail_EPA_12_6_07finalversion
Download
Report
Transcript WRAP TSS Detail_EPA_12_6_07finalversion
WRAP Technical Support System for Air
Quality Planning, Tracking, & Decision Support
Tom Moore | Western Governors’ Association
Shawn McClure | Cooperative Institute for Research in the Atmosphere
December 6, 2007
Acknowledgments
• Based on WRAP work 1997-2007
– Experience with §309 Haze SIPs submitted 12/03
– Need to distill key information for haze planning across wide variety of
air programs in the West
• Thanks to:
– WRAP Forums and Workgroups - Too many individuals to list all
•
•
•
•
•
Attribution of Haze – Steve Arnold (CO) & Bob Kotchenruther (EPA-R10)
Implementation & Planning – Tina Anderson (WY) & Mike Edwards (ID)
Modeling – John Vimont (NPS), Mary Uhl (NM), Kevin Briggs (CO)
Monitoring & Data Analysis – Marc Pitchford (NOAA)
100s involved – feds, tribes, states, industry, enviros
– TSS Development Team – Shawn McClure (CIRA), Joe Adlhoch (Air
Resource Specialists), Gerry Mansell (ENVIRON) & others
– EPA funding
– In-kind staff work from many agencies & organizations - 1,000s of hours
• Purpose of talk is to report out progress to date and plans for
the future
WRAP TSS permits integration of monitoring,
emissions, source apportionment, and modeling results
for current and future air quality planning.
• Why?
• What?
• How?
– Review data, outputs, tools
• Where?
• Future plans
Why does the TSS exist?
What makes it different from from other “web-based data systems”?
• Designed to be a true decision support system addressing
regulatory requirements of Regional Haze Rule
• Brings comprehensive and consistent regional data and
analysis results to planners for each Class I area
• Presents information required for regional haze planning, as
defined by air quality planners
• Integrates multiple datasets from regional analyses
(monitoring, emissions, source apportionment, modeling) into
displays and formats suitable for air quality planning
• Provides documentation and summary explanations of
technical results
• Data are derived from projects and data support systems
developed by WRAP members
What is the TSS?
• http://vista.cira.colostate.edu/TSS/
• A decision support system for regional haze planning in the
West, expandable to other air quality indicators and/or to
additional geographic areas
• The TSS provides analytical results from data support
systems and display tools for regional haze implementation
plans (to improve visibility for the 118 Class I areas in the
WRAP region).
• The TSS is a one-stop-shop for access, visualization,
analysis, and retrieval of the technical data and regional
analytical results - consolidating information about air
quality monitoring, emissions inventories and models,
source apportionment results, and gridded air
quality/visibility regional modeling simulations.
VIEWS / TSS Overview
Decision Support System (TSS)
Architectural Goals:
Guidance, Analyses, and Results
·
·
·
·
·
Data Support System (VIEWS)
Data, Resources, and Infrastructure
Policies, Procedures, Guidance, Expertise
Software Infrastructure
Data
Database Web/FTP
File
Build Upon Existing Efforts
Incorporate Lessons Learned
Add Value to Current Resources
Incorporate New Features
Expand Our Future Vision
Metadata
Spatial
GIS
Hardware and Network Infrastructure
Database Infrastructure
VIEWS / TSS Architectural Components
VIEWS / TSS Vision
End-to-end Air Quality Data and Decision Support
Data
Applications
Decisions
Visualization
Analysis
Exploration
Search
Source Apportionment
Modeling
•
•
•
•
•
•
TSS Website
TSS Databases
•
•
•
•
•
•
Acquisition
Import
Unification
Management
Manipulation
Retrieval
•
•
•
•
•
•
Assessment
Interpretation
Planning
Controls
Regulation
Tracking
Integrated System Solution Chart
VIEWS / TSS Future Vision
Goals and Development Plans
• Provide comprehensive comparison and analysis of monitored,
modeled, and emissions data with an integrated suite of tools
• Enhance and expand decision support applications
• Enable providers to upload manage their own data & metadata
• Promote an open, extensible, service-oriented architecture
• Provide services, components, and tools to air quality developers
• Incorporate satellite and meteorological data
• Investigate climate change and epidemiological applications and
perspectives
• Facilitate collaboration and development between organizations
TSS Development (How? & Who?)
Colorado State University –
Cooperative Institute for Research in
the Atmosphere (CIRA)
• Contractor for
operations/development
• Tool design/implementation
• Project host
• Integrated with:
• Fire Emissions Tracking System
(FETS) – Air Sciences, Inc. as
subcontractor
• Visibility Information Exchange
Web System (VIEWS) – collocated
with IMPROVE at NPS-CIRA
Air Resource Specialists
(ENVIRON as subcontractor)
• Data analysis, design, training, & content
development
• Direct support for interpretation of
monitoring, emissions, source
apportionment, and modeling results for
haze planning purposes
• Separate feeder data support systems:
• Emissions Data Management System
(EDMS)
• WRAP Regional Modeling Center (RMC)
• Causes of Haze Assessment (CoHA)
project
Coordination & management by WRAP Forums/Workgroups and staff
Where does TSS fit in?
• Now (2007-08)
– Source of planning data & results for western
haze plans
– Implementation support
• Review and approval by EPA
• Annual data update cycle to track progress
– Emissions
– Monitoring
– Periodic source apportionment, modeling, and control
strategy analyses
• Basis of 60-year RHR program – states set goals, EPA
partners with states to verify progress
• Version control to make TSS data use transparent
Future plans for TSS
• Future (2009 and onward)
– Source of visibility progress/tracking data & analysis
results for western haze plans
– Development to support one-atmosphere air quality
planning and regional control strategies
• Continuing haze plan implementation
• Regional contribution analyses and results for Ozone and PM
NAAQS issues, supporting state and local planning efforts
• Analyses of mercury and nitrogen deposition
• Continuing annual data update cycle to track progress
– Emissions
– Monitoring
– Periodic source apportionment, modeling, & control strategy analyses
• Integration of additional data (satellite, control costs, changes in
energy supply, et cetera)
• Continuing version control to make TSS data use transparent
WRAP 2008 Workshops
• Members of WRAP Committees, Forums, and
Workgroups, as well as members of additional
organizations not currently active in the
regional haze effort will meet to:
– Identify strengths and weaknesses of existing data
and analysis tools;
– Determine uses and limitations of those data and
tools;
– Develop coordination efforts needed with ongoing
and planned State/Tribal/Federal projects;
– Discuss timing, effort, activities, and any needed
changes in future projects by WRAP contractors
– Document results for work planning purposes &
next steps
WRAP 2008 Workshops, cont.
• Monitoring Data Analysis Workshop
– 2-day workshop, targeted for April will address monitoring
methods, network operations, and data analysis activities for
Ozone, PM, haze, mercury, and N deposition data
• Emissions & Modeling Analysis Workshop
– 2-day workshop, targeted for July will address emissions and
modeling studies related to Ozone, PM, haze, mercury, and N
deposition
• Technical Data Needs for Air Quality Planning Workshop
– 2-day workshop, targeted for September will bring forward
technical data and analysis capabilities from the earlier workshops
to address 2009-12 air quality control and management planning
needs for:
• Haze plan implementation – how/what to do
• Defining data, studies, & results needed for air quality planning ozone, PM, mercury, N deposition
WRAP 2009-12 Activities
• Track, report, and conduct needed analyses of progress for
regional haze;
• Determine regional contributions to Ozone and PM health
and welfare standards’ nonattainment issues at various
scales;
• Understand and analyze the nature and causes of mercury,
and nitrogen deposition/critical loads in the West;
• Assess air quality changes from emissions management
strategies and programs; and
• In concert with emerging efforts to manage and adapt to
climate change, fully integrate data for both energy supply
and use as well as greenhouse gas emissions into air quality
analyses.
Conclusions & Discussion
• Questions
• Where does TSS fit in with efforts by
states/EPA/other federal agencies?
• Are there obvious functional limitations of the TSS
or specific “smart” ideas that EPA would like the
WRAP to consider for future development?
Contacts
Tom Moore
Joe Adlhoch
WRAP – Air Quality Program
Manager, WGA
w/ 970.491.8837
e/ [email protected]
Air Resource Specialists – Vice
President/Project Manager
w/ 970.484.7941
e/ [email protected]
Shawn McClure
Gerry Mansell
CIRA – Software Engineer, Research
Associate III
w/ 970.491.8455
e/ [email protected]
ENVIRON - Senior Manager
w/ 415.899.0727
e/ [email protected]
VIEWS / TSS Data Import
Validation
Metadata Import System
Data
Acquisition
System
Data Import System
AIRDATA_SOURCE
AIRDATA_OLTP
Validation
·
·
·
·
·
Data Acquisition System
Metadata Import System
Emailed updates from data providers ·
Automatic HTTP extraction of source
·
data files
·
Database replication
Imports data “as-is” into the source
·
database
Technologies: ASCII text files, Excel
spreadsheets, Access databases, etc.
Facilitates the entry of new
metadata
Validates new metadata entries
Detects overlap with existing
metadata
Technologies: VB .Net, ASP .Net,
and SQL Server stored procedures
Data Import System
·
·
·
·
·
·
·
Extracts data from the source database
Scrubs data and performs conversions
Maps source metadata to integrated metadata
Transforms the data into an integrated schema
Verifies and validates imported data
Loads data into the back-end OLTP system
Technologies: Microsoft SQL Server DTS,
stored procedures, SQL scripts, and Visual
Basic routines
VIEWS / TSS Database Architecture
OLTP:
Data Warehouse Generation System:
Data Warehouse:
• Functions as the “back-end” database
• Fully relational and in 3rd normal form
• Used for data import, validation, and
management
• Technologies: Microsoft SQL Server
•
•
•
•
•
•
•
•
•
•
•
Extracts data from the OLTP
De-normalizes and transforms data
Loads data into the Data Warehouse
Builds table indexes
Archives “snapshots” of the database
Technologies: VB, stored procedures
Functions as the “front-end” database
Uses a de-normalized “star schema”
Used for querying and archiving data
Automatically generated from the OLTP
Technologies: Microsoft SQL Server
VIEWS / TSS Page Architecture
TSS GIS Server
3
2
1
ASP .NET page requests a map from the
mapping service on the GIS server, via
HTTP GET, SOAP, or similar protocol.
TSS web server executes (submits)
the appropriate ASP .NET page.
User visits a page on the TSS web site and
specifies map arguments using controls on
the web page (layers, centroid, zoom, etc.)
The mapping service assembles the requested layers into a map image
using the specified centroid and zoom, then returns the image to the page.
4
Mapping Service Call
Map Image
ASP .NET Page
Create Map
5
The page displays the image.
Chart Request
Create Chart
Page
Request
Chart Image
TSS Web Server
Display Raw Data
Database Query
Formatted Data
TSS Architectural Overview:
Displaying a Map
This example gives a very high-level description of the
procedural steps involved in requesting, creating, and
displaying a map using the proposed TSS mapping
component and/or web service.
TSS Database Server
10/4/2005
Modified:Created:
11/10/2007