The New Emissions Modeling Framework System

1
The NewEmissions Modeling FrameworkSystem
EMF

• Emissions Modeling Team
• Marc Houyoux, Madeleine Strum, Rich Mason, Norm
  Possiel
• David Misenheimer, Darryl Weatherhead, Larry
  Sorrels
• Bill Benjey, George Pouliot
• Contractor UNC Institute for the Environment
• Alison Eyth, Qun He, Alexis Zubrow, Darin Del
  Vecchio,Dongmei Yang

2
Overview

• Background
• Development status and benefits
• How EPA is using the EMF
• EMF Future
• EMF Demo

3
EMF Motivation

• Improve timeliness, quality, and transparency of
  emissions data used in air quality models

Air QualityModeling
EmissionsInventory
EmissionsModeling
Summariesand Analysis
Data handling SMOKE processing QA checks Standard
procedures Documentation Reproducibility
4
EMF Goals
?

• Make emissions modeling faster and more
  accessible
• Create and implement emissions modeling protocol
• Provide data/processing transparency tracking
• Data with versions, metadata, QA status
• Emissions modeling applications and associated
  data
• Data queries and summaries
• Meet needs for multi-pollutant modeling
• Create tools that can be used by EPA and others
  (e.g., RPOs, states)

?
?
?
?
5
EMF capabilities

• Data Manager
• Organizes/stores data
• Provides tracking of data changes using data
  versions
• Supports metadata
• QA Manager facilitates QA capabilities and
  tracking of QA steps, summaries, and queries
• Case Manager
• Organizes model steps, inputs, parameters
  (e.g., SMOKE)
• Runs Emissions Modeling steps at NCC, records
  history and registers outputs
• Control Strategy Tool (CoST)
• Stores database of control measures (practices
  and technologies)
• Supports user to create control strategies
  (multi-pollutant functionality)
• Applies controls to emission inventories for use
  in SMOKE
• All done in a multi-user environment
• SMOKE and other tools are run from EMF, but are
  not within EMF

6
EMF Development Statusand benefits
7
Timeline
Jan 06SurrogateTool EMF Beta-releaseinstal
led atEPA
Oct 07Case MgtRunsSpeciationTool
Oct 07CompleteEMFDatabaseat NCC(2TB disk)
Sep 07UpdatedSpeciationTool
Apr 05 CoST team decides to use EMF
Mar 06InitialSpeciationTool
Mar 07Initial EMF servermove to NCC
Oct 04Project start
2005
2006
2007
2008
Oct 06First Case InputsSetup (2002v2)
Sep 05Final DesignDocument
May 07 EMFTraining
May 06First productiondata loaded
Oct 072020cc EMF Demo nears completion
Design
Production
Development
Maintenance
Data Manager
Case Manager
EmisView
QA Manager
8
Major milestones met so far

• EMF-funded components all exist in working form
• Data Manager, including QA Manager
• Case Manager
• Control Strategy Tool (CoST)
• Spatial Surrogate Tool
• Speciation Tool
• Server obtained, installed, and running at NCC
• OAQPS using EMF for supporting ongoing projects
• EMF training module created and training held at
  2007 EPA Emission Inventory conference

(Create challenging SMOKE inputs)
9
How Data Manager helps EPA

• Stores data in a PostgreSQL database accessible
  by all. All team members can find the latest
  data. Others data changes shared. Access by
  staff other than emissions modelers.
• Supports multiple versions of datasets. We can
  access both old and current versions of data, for
  reproducibility and transparency.
• Users can edit data in a user interface to the
  database. Convenient.
• Automatically records metadata, such as who/when
  makes changes. Allows users to add what/why of
  changes and manual metadata entry. Eases our
  burden for keeping track of details other ways.
  Adds transparency after work is done.
• Exports SMOKE-ready files, including
  documentation in file headers. Saves us time
  prevents possible format errors.
• We can better focus on analysis and modeling
  needs.

10
How QA Manager helps EPA

• Stores QA steps, who/when steps performed, QA
  status along with the data. We can easily find
  QA status of data. We can see the overall QA
  status, what QA steps complete, who performed
  steps, and the results. Users can add steps as
  needed.
• Tracks QA steps by dataset version. We know what
  steps were performed on each version. Helps
  prevent skipping QA.
• Supports running SQL queries on the data to
  perform QA steps and summaries. Give us the
  flexibility and convenience of database queries.
  Runs within EMF and results stored for present
  and future use.
• Templates of QA steps (queries) can be created
  and reused. Helps ensure QA of data gets done,
  decreases learning curve for new emissions
  modelers.
• Tracks both automated (run by EMF) and external
  and/or manual QA steps. Gives us needed
  flexibility to get work done.

11
How Case Manager helps EPA

• Data in a Case (e.g., SMOKE run) linked to
  datasets in Data Manager. We have a single system
  to use for data handling and running SMOKE.
• Exports all SMOKE-ready files needed for a SMOKE
  run with a few mouse clicks. Saves time and
  prevents possible errors associated with manually
  writing out many data files formats from many
  other data sources.
• User interface for SMOKE. Reduces learning curve
  for new emissions modelers. We have a permanent
  record of SMOKE inputs, settings, and location of
  outputs.
• Submits SMOKE jobs, preprocessing, and
  postprocessing to a compute server (amber) or
  EMF server. Supports desktop access to data and
  SMOKE cases, while running at NCC compute cluster
  to meet computational needs.

12
How EPA is using the EMF
13
Uses to date

• Data Manager and Case Inputs functions used
  for
• 2002-based CAP platform v3 (2002, 2009, 2014,
  2020, 2030)
• 2002-based CAP/HAP platform v3 (2002)
• Ozone NAAQS Final Rule
• OTAQs Locomotive Marine Rule
• ORD 2005-based platform
• Detroit Multi-Pollutant Study
• Actually run using EMF Case Manager
• SMOKE 2020 base case to demonstrate we can
  replicate the old way of running SMOKE
• Speciation Tool runs for ORD to create
  SOA-enabled speciation profiles for SAPRC99 and
  CB05
• A few sectors on the 2002ae (v4 platform), in
  development

14
EMF in FY 2008

• In-house efforts to setup EMF for operational use
  
• EMF work assignment
• Support and maintenance
• Add quick and easy emissions sensitivity tool
  for AQMG
• CoST
• Completion of O3 NAAQS RIA Mobile Control
  Strategies
• NOx/SOx NAAQS RIA Control Strategies
• Manage SMOKE inputs
• OTAQs Bond Rule and SECA / IMO modeling
• Detroit Multi-Pollutant Study
• Upcoming runs of SMOKE with EMF
• 2002ae (v4) platform
• New base runs for 2003, 2004, 2005, 2006 for
  CDC/Phase, CMAQ evaluation, and Accountability

15
EMF future

• Ongoing work to refine Data Manager, QA Manager
  with a more robust protocol, Case Manager, CoST
• As part of OAQPSs daily operations, EMF is
  assisting us manage emissions modeling for 8
  projects simultaneously with few staff and high
  quality
• Possibility for adapting to meet data management
  and modeling needs of others in AQAD and EPA
• EMF could be Environmental Modeling Framework
• Readily adaptable to support other applications
  such as CMAQ

16
EMF demo