Carolina Environmental Program 1 UNC Chapel Hill A New Control Strategy Tool within the Emissions Modeling Framework Alison M. Eyth Carolina Environmental

Carolina Environmental Program 1 UNC Chapel Hill

A New Control Strategy Tool within the

Emissions Modeling Framework

Alison M. EythCarolina Environmental Program

University of North Carolina at Chapel Hill

David Misenheimer, Darryl Weatherhead, Larry Sorrels, Marc Houyoux

US EPA OAQPS

October 17, 2006


Background EPA OAQPS is required to assess the costs

and benefits of proposed new regulations as part of a Regulatory Impact Analysis

Part of this process is to prepare illustrative examples of control strategies that could be used to meet proposed standards in various geographic areas

The cost of the strategies must be estimated, along with the expected emission reductions


Motivation to Develop New Software AirControlNET had been the main tool used by

EPA in recent years to estimate the cost of, and reductions obtained by, control strategies for criteria pollutants and precursors (e.g., VOC, PM)

Limitations of the AirControlNET Visual FoxPro platform made it difficult to expand and maintain – a more modern and scalable platform was desired

Inventory data had to be manually merged with control measures prior to use in the software

The attributes of the Control Measure data were not readily apparent to the user, nor could users add new control measures

Tracking of multiple strategy runs was desired


Goals for the Control Strategy Tool1. Support development of control strategies for

nonutility point and stationary area sources – Mobile and EGU may be supported later

2. Support national and regional scale analysese.g., 2007 Ozone NAAQS analysis

3. Estimate cost and emissions reductions (including co-benefits and disbenefits)

4. Enable users to load emission inventories and control measures on-the-fly

5. Provide clear and transparent Control Measure information to the user

6. Support several types of strategy analyses, including least-cost and broad scale analysis for a specific industry or sector

7. Provide outputs usable by SMOKE


Choosing Java as the Development Platform

Connects easily with relational databases Object-oriented Java software is easy to extend A full featured Graphical User Interface library is

available, and many types of open source libraries

Applications run on Windows, Linux, etc. Some existing emission inventory readers and

other code could be reused Interfacing with other EPA-developed Java

software is facilitated


Why Integrate Strategy Tool with Emissions Modeling Framework?

Once Java was selected, integration within the EMF seemed to be a natural choice

The EMF client-server architecture makes it easier for strategy developers and modelers to access the same inventories

The EMF Data Management system, including data importers, versioned Datasets, and the Sector Manager is useful for strategy development

New features added for each project benefit the other

The EMF can be deployed either on a single desktop machine or as a true client-server system


EMF Architecture at EPA

Data Management Case Management Quality Assurance

Strategy Devel.

4 CPU Application &

Database Server

ClientsCompute Cluster

SMOKE

SMOKE input files

Shared Disk

imports & exports data

starts runs


Development and Use of a Future Year Base Emissions Inventory within EMF

Air Quality Model

Control Programs

Information

ORL export of NEI DB

Emissions Modeling Framework

Control Measure and Cost

data

ControlData andGrowthFactors

Base Year Emissions Inv.

1

FY Base Inventory

AQMReady

Emissions

2 3 4

Creating a Future Year Base or Control Inventory:1. EMF imports a base year Emissions Inventory from ORL export

of NEI. The inventory is quality assured then exported.2. SMOKE applies the provided growth and control factors to create

the future year base inventory3. The EMF imports the Future year base inventory and can uses

this as a base for control strategy development4. The EMF exports controlled inventories for input to SMOKE5. SMOKE processes the inventories and exports AQM-ready

emissions

* This diagram does not include mobile emissions or EGU emissions and control data.

SMOKECntlmat and

Grwinven

Emissions Modeling DB

ControlledInventory

SMOKE5

1b


Support for Control Measures in EMF Control Measure Manager:

– Shows the list of control measures in the system and their major attributes

– Creates new and edits existing control measures

– Interface to import and export control measures from/to .csv files

– Shows efficiency and cost information for selected pollutant

– Converts cost data to consistent cost year Control Measure Editor

– Supports specifying summary information for measure, Efficiency/Cost records, and SCCs to which the measure applies



Control Measure Editor Summary tab

Summary information is set on the Summary tab


Control Measure Editor Efficiencies tab

For a measure, control efficiency, rule effectiveness, rule penetration and annualized cost per ton can be specified for multiple pollutants, locales (states or counties), and effective dates


Adding Efficiency Records

A separate window is used to enter the efficiency record data


Control Measure Editor SCCs tab

Measures are associated with SCCs so they can be matched with emission inventory sources


Adding SCCs

SCCs can be added iteratively from a window that allows sorting and filtering to help identify SCCs of interest


EMF Control Strategy Features Control Strategy Manager:

– Shows the list of control strategies in the system and their major attributes

– Creates new, removes, copies, and edits existing control strategies

Control Strategy Editor– Specifies summary information for a strategy

(e.g., target pollutant, algorithm to use, region)– Specifies filters on inventories and measures

to include in the strategy run– Shows outputs from the strategy


Control Strategy Manager

Used to create new, edit, remove, and copy strategies

Major attributes are shown in the table


Control Strategy Editor Summary Tab

Specify high level summary attributes for the strategy on this tab; Click Run to run the strategy


Control Strategy Editor Outputs Tab

Shows outputs created by the Strategy Controlled inventories can also be created here


Analyzing Strategy Results

Results can be sorted, filtered, and plotted in the Analysis Engine


FY07 Control Strategy Plans

Add filters for inventories and control measures Report cobenefits for other pollutants in results Implement summaries of results and inventories Compute overall percent reduction for strategy Expand measures database to include additional

information, including data for climate change gases

Add support for point sources (using cost per ton data first, and cost equations later)

Implement other types of analyses, such as least cost

Support 2007 Ozone NAAQS effort


EMF Software Requirements

Java 1.4 or 1.5 PostgreSQL 8.1 Apache Tomcat Tested on Linux and Windows Should run on other operating systems that

support Java and other required software


Availability of EMF and Software Requirements

Public EMF release is not yet funded, but direct arrangements can be made

Code can be downloaded from SourceForge An EMF training class may be held at the

2007 Emissions Inventory Conference Software Requirements:

– Java 1.4 or 1.5– PostgreSQL 8.1– Apache Tomcat– Tested on Linux and Windows– Should run on other operating systems that support

Java and other required software


References EMF and CoST Documentation

http://www.cep.unc.edu/empd/projects/emf/ Carolina Environmental Program

http://www.cep.unc.edu Authors: [email protected],

[email protected]

Documents

Carolina Environmental Program 1 UNC Chapel Hill A New Control Strategy Tool within the Emissions Modeling Framework Alison M. Eyth Carolina Environmental