Re-EngineeringOne Step at a Time

2

Some Ideas

• Rapid Inventory Development Pilot - Status

• Task Force of Stakeholders

• Review of Reporting Codes

• Collaborative National EIs by Sector

3

Rapid Inventory Development Pilot (1)

• Testing feasibility of developing inventory faster

• Complete inventory within 12 months– 10 months for State Data

Development– 2 months for EPA Process

• Direct web-based reporting from facilities as a tool

• 11 agency initial participation

4

Starting Points – Current Processes

• Data Collection Methods – Paper Forms– Electronic Spreadsheet– Custom distributed application– Custom web-based system

• Length of time to develop inventory– Most participants averaged 17 months

• Most resource intensive portion– Data review

• Agencies typically receive data from facilities during first quarter

Rapid Inventory Development Pilot (2)

5

Rapid Inventory Development Pilot (3)

• Pilot Schedule

• 11/04 Project started

• 1/05–5/05 Develop/test reporting

tools

• 5/05 – 10/05: S/Ls develop inventories

• 10/31/05: Submittal deadline

• 12/05: Complete pilot inventory

• 03/06: Evaluation of pilot

6

7

In order to create the emissions inventory, the user selects from the activity data, emission factors, and control data that have been imported or entered into NDMS.

8

Rapid Inventory Development Pilot – Wrap Up

• Experiences providing data quicker

– States

– EPA experiences

– Processing data

• Feedback on tools

– Point

– Nonpoint

• Overall feasibility

9

Creation of NEI Task Force

• Provide a more collaborative approach for decision-making and action

• Hear from multiple voices to define common goals

• Reach Consensus on which projects to pursue and implementation details

• How do we put this together?

10

Code Review (1)

• Review current select reporting codes and develop software to manage codes– Source Category Codes– Pollutant Codes– SIC/NAICs Codes– Others?

• Develop new codes

11

Code Review (2)

• Goals for the project– Source category codes that will meet

the requirements of future EI needs– Provide a software solution to

maintain codes– Collaborate with stakeholders on the

development of potential new codes– Facilitate an easy transition to the

new codes– Enable the new codes/software before

the 2008 emissions inventory cycle

12

Collaborative National Nonpoint Emission Inventory (1)

• All S/L/Ts agree on a core set of categories and pollutants

• Agree on sufficiently robust estimation methods and activity data sources

• Develop a web tool that:– Allows S/L/Ts to add additional (non-

core) pollutants or alternative activity levels

– Displays and exports inputs and emission results for both national method and alternatives

13

Collaborative National Nonpoint Emission Inventory (2)

• Software enforces pollutant coverage, HAP/CAP

integration, category detail and allows timely

access and comparison of alternative methods

• Could extend to integrate split Point/Nonpoint

categories by use of geo-referenced data sets:

– Gas stations, dry cleaners, graphic arts

– Landfills

– Airports

– Shipping lanes and ports

14

NEI Re-engineering

• Check out the project web site at http://www.epa.gov/ttn/chief/net/eis.html

• Contact Martin Husk at (919) 541-3621husk.martin@epa.gov

• We need your help to make this project a success

15

Discussion

• Clarifying Questions?

• Comments, Concerns?

• Brainstorming

16

Brainstorming Session

• Create a list of ideas for improvements to the emissions inventory process

• Review 2002 inventory process– Your role in the process– EPA’s role in the process

• Think forward to 2009…– What is the new process?– What improvements have been implemented?– What tools do you have as part of the

process?– What data are submitted?– How are data maintained?