1. Carolina Environmental Program 1 UNC Chapel Hill A New Control Strategy Tool within the Emissions Modeling Framework Alison M. Eyth Carolina Environmental Program University of North Carolina at Chapel Hill David Misenheimer, Darryl Weatherhead, Larry Sorrels, Marc Houyoux US EPA OAQPS October 17, 2006

2. Carolina Environmental Program 2 UNC Chapel Hill Background l EPA OAQPS is required to assess the costs and benefits of proposed new regulations as part of a Regulatory Impact Analysis l Part of this process is to prepare illustrative examples of control strategies that could be used to meet proposed standards in various geographic areas l The cost of the strategies must be estimated, along with the expected emission reductions

3. Carolina Environmental Program 3 UNC Chapel Hill Motivation to Develop New Software l 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) l Limitations of the AirControlNET Visual FoxPro platform made it difficult to expand and maintain – a more modern and scalable platform was desired l Inventory data had to be manually merged with control measures prior to use in the software l The attributes of the Control Measure data were not readily apparent to the user, nor could users add new control measures l Tracking of multiple strategy runs was desired

4. Carolina Environmental Program 4 UNC Chapel Hill Goals for the Control Strategy Tool 1. 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 analyses e.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

5. Carolina Environmental Program 5 UNC Chapel Hill Choosing Java as the Development Platform l Connects easily with relational databases l Object-oriented Java software is easy to extend l A full featured Graphical User Interface library is available, and many types of open source libraries l Applications run on Windows, Linux, etc. l Some existing emission inventory readers and other code could be reused l Interfacing with other EPA-developed Java software is facilitated

6. Carolina Environmental Program 6 UNC Chapel Hill Why Integrate Strategy Tool with Emissions Modeling Framework? l Once Java was selected, integration within the EMF seemed to be a natural choice l The EMF client-server architecture makes it easier for strategy developers and modelers to access the same inventories l The EMF Data Management system, including data importers, versioned Datasets, and the Sector Manager is useful for strategy development l New features added for each project benefit the other l The EMF can be deployed either on a single desktop machine or as a true client-server system

7. Carolina Environmental Program 7 UNC Chapel Hill EMF Architecture at EPA Data Management Case Management Quality Assurance Strategy Devel. 4 CPU Application & Database Server Clients Compute Cluster SMOKE input files Shared Disk imports & exports data starts runs

8. Carolina Environmental Program 8 UNC Chapel Hill 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 Control Data and Growth Factors Base Year Emissions Inv. 1 FY Base Inventory AQM Ready 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 inventory 3.The EMF imports the Future year base inventory and can uses this as a base for control strategy development 4.The EMF exports controlled inventories for input to SMOKE 5.SMOKE processes the inventories and exports AQM-ready emissions * This diagram does not include mobile emissions or EGU emissions and control data. SMOKE Cntlmat and Grwinven Emissions Modeling DB Controlled Inventory SMOKE 5 1b

9. Carolina Environmental Program 9 UNC Chapel Hill Support for Control Measures in EMF l 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 l Control Measure Editor – Supports specifying summary information for measure, Efficiency/Cost records, and SCCs to which the measure applies

10. Carolina Environmental Program 10 UNC Chapel Hill

11. Carolina Environmental Program 11 UNC Chapel Hill Control Measure Editor Summary tab l Summary information is set on the Summary tab

12. Carolina Environmental Program 12 UNC Chapel Hill Control Measure Editor Efficiencies tab l 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

13. Carolina Environmental Program 13 UNC Chapel Hill Adding Efficiency Records l A separate window is used to enter the efficiency record data

14. Carolina Environmental Program 14 UNC Chapel Hill Control Measure Editor SCCs tab l Measures are associated with SCCs so they can be matched with emission inventory sources

15. Carolina Environmental Program 15 UNC Chapel Hill Adding SCCs l SCCs can be added iteratively from a window that allows sorting and filtering to help identify SCCs of interest

16. Carolina Environmental Program 16 UNC Chapel Hill EMF Control Strategy Features l 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 l 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

17. Carolina Environmental Program 17 UNC Chapel Hill Control Strategy Manager l Used to create new, edit, remove, and copy strategies l Major attributes are shown in the table

18. Carolina Environmental Program 18 UNC Chapel Hill Control Strategy Editor Summary Tab l Specify high level summary attributes for the strategy on this tab; Click Run to run the strategy

19. Carolina Environmental Program 19 UNC Chapel Hill Control Strategy Editor Outputs Tab l Shows outputs created by the Strategy l Controlled inventories can also be created here

20. Carolina Environmental Program 20 UNC Chapel Hill Analyzing Strategy Results l Results can be sorted, filtered, and plotted in the Analysis Engine

21. Carolina Environmental Program 21 UNC Chapel Hill FY07 Control Strategy Plans l Add filters for inventories and control measures l Report cobenefits for other pollutants in results l Implement summaries of results and inventories l Compute overall percent reduction for strategy l Expand measures database to include additional information, including data for climate change gases l Add support for point sources (using cost per ton data first, and cost equations later) l Implement other types of analyses, such as least cost l Support 2007 Ozone NAAQS effort

22. Carolina Environmental Program 22 UNC Chapel Hill EMF Software Requirements l Java 1.4 or 1.5 l PostgreSQL 8.1 l Apache Tomcat l Tested on Linux and Windows l Should run on other operating systems that support Java and other required software

23. Carolina Environmental Program 23 UNC Chapel Hill Availability of EMF and Software Requirements l Public EMF release is not yet funded, but direct arrangements can be made l Code can be downloaded from SourceForge l An EMF training class may be held at the 2007 Emissions Inventory Conference l 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

24. Carolina Environmental Program 24 UNC Chapel Hill References l EMF and CoST Documentation http://www.cep.unc.edu/empd/projects/emf/ http://www.cep.unc.edu/empd/projects/emf/ l Carolina Environmental Program http://www.cep.unc.edu http://www.cep.unc.edu l Authors: eyth@unc.edu, Misenheimer.David@epamail.epa.goveyth@unc.edu Misenheimer.David@epamail.epa.gov