– Data repository for air emissions data used to create the NEI – Contains State, Local, Tribal and EPA submitted data – Can store multiple emissions values for the same unit/process – Can store annual, monthly, daily data (e.g., fires, events) – Data available via a password-protected web site
• EIS Gateway https://eis.epa.gov/eis-system-web/welcome.html
• National Emission Inventory (NEI) – Snapshot in time from EIS – Inventory version shared with the public – One emissions value per process selected – Annual emissions values
2
Presenter
Presentation Notes
The Emission Inventory System is the actual database which holds the State/Local/Tribal and EPA submitted emission data used to create the National Emission Inventory. The EIS is capable of holding multiple emission values for a single process and is reported, at a minimum, as annual. All data is available through the EIS Gateway to registered EPA and S/L/T users. The National Emission Inventory is a snapshot in time of the emissions data received for a specified inventory year, picking the ‘best’ of the emissions data choices. The NEI is shared with the public and contains one annual emissions value.
S/L/T Reporting Requirement • Air Emissions Reporting Rule (AERR)
http://www.epa.gov/ttn/chief/aerr/ – Complete criteria pollutant inventory every 3 years
• All point sources (100 tpy potential to emit threshold) • Nonpoint Sources • Onroad and Nonroad sources • Events (wildfires and prescribed fires) • 2011 Emissions due 12/31/2012, EIS window opens 6/1/2012
– Annual reporting for type A point source facilities – SO2, NOx, CO with potential to emit > 2,500 tpy – VOC, PM, NH3 with potential to emit > 250 tpy – Pb with potential to emit > 5 tpy (to be amended to agree with Lead
NAAQS level of > 0.5 tpy) – HAPs are submitted voluntarily by many S/L/Ts and are
encouraged as part of an integrated report 3
Presenter
Presentation Notes
The AERR pertains to criteria pollutants only which include SO2, NOx, CO, VOC, PM-10 and PM-2.5, ammonia and lead. Every three years, all sources meeting the > 100tpy threshold, are reported as well as nonpoint, onroad, nonroad, and events emissions. The AERR says that onroad and nonroad input submittals meet reporting requirements. HAPs are on a voluntary basis, but we receive HAP emissions from the majority of our submitters. EPA adds HAPs from other data sources to complete coverage for HAPs, but would prefer to have S/L/T estimates. It’s best when HAPs and CAPs come from one source and are in agreement, for example VOC HAPs are not greater than VOC.
• The NEI is one of the key inputs for : – Modeling of national rules - NAAQS reviews, CSAPR, etc – Non-attainment Designations – NATA Review – toxics risk modeling – Trends reports and analyses
4
Presenter
Presentation Notes
These analysis often require that we can project to future years, for example to evaluate the future with and without new rules.
Components of the EIS
• Six different data categories – Facility Inventory – Point Emissions – Nonpoint Emissions – Onroad Emissions – Nonroad Emissions – Event Emissions (wildfires and prescribed fires) – No biogenic emissions, although these are part of
EPA’s modeling files
5
Presenter
Presentation Notes
Today, we are discussing the Onroad Inventory. Onroad emissions come from vehicles used on roads for transportation of passengers or freight. Events is a data category designed to house day-specific, locale-specific large emissions events such as wildfires and prescribed fires. EPA supplies biogenic and doesn’t need from agencies.
Onroad Submissions
• Emissions in NEI must be from an EPA-approved model – MOVES – EMFAC (California)
• EPA strongly encourages submittals of MOVES County Database (CDB) tables rather than emissions
• Tribes and CA should submit emissions
6
Presenter
Presentation Notes
Onroad emissions typically come from emissions estimation models. Currently MOVES and Ca EMFAC models are approved for inventories for EPA regulatory work. These models can be run at varying levels of granularity (temporally and spatially). We need a standardized set of emissions built with similar assumptions and model parameters. MOVES CDB – “county database” files are the inputs required to run the MOVES model. Since CDB is county-based, it does not include tribes. EMFAC is California’s own onroad model
Why Inputs? • EPA prefers to receive activity data instead of emissions
as they allow for more in-depth analysis and consistent, integrated emissions in the NEI. If you do not submit onroad input data, EPA will generate emission estimates using national defaults.
• EPA will provide a set of default onroad inputs for agencies to review/ customize as desired
• Agencies may accept EPA defaults in lieu of submittals by sending a “support request” to EIS that states this.
• To the extent resources allow, EPA will assist agencies to build their submittals.
7
Presenter
Presentation Notes
Inputs allow for Future year projections built on the same input basis. There is no way to project submitted emissions to future years. Future year analysis are typical in regulatory analysis. HAPs and CAPs built on the same input data. No gap filling from EPA data that could create anomalies (e.g., VOC HAPs greater than VOC When/if MOVES model is updated/revised, inputs allow taking advantage of those model revisions; inputs provide dynamic emissions capability to meet inventory needs. CDB submittal process is new and under development. We plan to post instructions on the 2011 NEI website May 2011
Support Request
8
Presenter
Presentation Notes
If you want to let EPA know that your agency prefers to accept EPA values as your submittal, do so via a support request.
Summary of County Database (CDB) Submittal Steps
– Review instructions on the 2011 NEI web page – Pick up your draft default CDBs from EIS – Compile ONLY county CDBs with improvements – Repeatedly run QA script and address errors that are found until
there are no errors – Submit:
• 1. QA tool report • 2. Checklist • 3. Documentation • 4. CDB folders for each county CDB
– EACH SUBMITTAL IS A COMPLETE REPLACEMENT OF PREVIOUS SUBMITTALS!
• Thus an agency’s final submittal must include all counties they wish to submit
9
Presenter
Presentation Notes
We’ll go over each of these steps Please start early on CDB revisions. This is a new process. We’ve done our best to make a way for you to submit MOVES inputs in a manner that uses information you are already using, matching the format MOVES uses. We want to know early if there are problems and revise quickly. Instructions and tools are posted on 2011 NEI web page.
Pick up your draft default CDBs
10
Presenter
Presentation Notes
Onroad CDB and Nonroad NCD inputs are easier to find than before. Under View/Add/Edit. EPA defaults will be available by state under “EPA Default” CDBs are available by state. County agencies will need to extract their county CDB from their state. Each CDB is a county folder that includes the 24 tables that apply to that county.
Update Inputs Compile ONLY CDBs for Counties with
improvements Table Name Description countyyear Stage 2 program description emissionratebyage Alternate California standards sccroadtypedistribution Distribution of SCC vehicle classes to SCC road types auditlog Log of changes to the county database avft Alternate diesel sales fractions avgspeeddistribution Average speed distributions county County description dayvmtfraction Distribution of VMT to day types fuelformulation Description of fuels fuelsupply Market share of fuels by month fuelsupplyyear Year of fuel supply hourvmtfraction Distribution of VMT to hours of the day hpmsvtypeyear Annual VMT by HPMS vehicle class imcoverage Description of the I/M program monthvmtfraction Distribution of the VMT to months of the year roadtype Description of the road types roadtypedistribution Distribution of the VMT to road types sourcetypeagedistribution Distribution of vehicle population to vehicle age sourcetypeyear Vehicle populations state Description of the state year Year of evaluation zone Allocation of activity to zones zonemonthhour Temperature and humidity values zoneroadtype Allocation of vehicle operation to zones
11
Presenter
Presentation Notes
A CDB consist of 24 MySQL tables for a single county in a folder identified for that county. Only counties with CDB improvements over EPA defaults need be submitted. For example, if a state only does MOVES on urban counties, only those should be submitted. No representative county submittals If users create the county databases using the MOVES county database manager (CDM) (from scratch), the CDM will create 21 tables. They will be missing three tables: o EmissionRateByAge o SCCRoadTypeDistribution o CountyYear Running the QA script will create these tables in their county databases, but the tables will all have zero rows (empty). Leaving these tables empty will *not* cause the county databases to fail the script if it is run again (by them or us). Right now we will fail a database if it does not have these tables. If they create the county databases using the CDM, their initial run of the QA will turn up errors (missing tables). However, if they run the QA script again, the tables have been created by the previous check and the "missing tables" error will no longer appear in the report. They can send the second report (with no errors) to the EIS.
1. QA Report • PSC_QA_Report.txt
• QA tool is availablbe for download on the 2011 NEI website. MySQL tool checks CDB in their native format
• Users can run the QA tool script on all CDBs for submittal
• The QA tool checks CDB format, naming convention, ranges, sums, etc in each CDB table
• The QA tool generates a report for inclusion with EIS submittal
• If the tool finds any errors, they must be corrected before EIS will accept them: EIS will reject any submittal with a QA report that indicates errors.
12
Presenter
Presentation Notes
Time and resources did not allow a major update to EIS to incorporate MOVES inputs. So we built a tool that you run on your inputs. You make corrections, and submit the corrected CDB and the QA report. QA tool can be used to check any database you wish to run in MOVES, not just EIS submittals. File naming convention uses program system code (PSC)
Example QA Report Results
13
Presenter
Presentation Notes
In this example… The sum of the average speed fractions in the AvgSpeedDistribution table must add to 1.0 for every combination of SourceTypeID, RoadTypeID and HourDayID, even if the Source Type, Road Type or HourDayID do not have VMT associated with that combination. You can use the default distribution by leaving that combination out of the table. In this case, the submission has a distribution that adds to zero (0.0). This entry (all zeros) can inadvertently eliminate any VMT associated with that combination and cause an incorrect emissions result. A distribution of all zeros cannot be allowed. Also, EIS will check to see that a CDB exists for each county indicated as have records in the QA report
2. Check list
• PSC_Checklist.xls (or xlsx) • This checklist is available for download on the
2011 website • The checklist indicates
– Which tables in which counties contain updates to EPA defaults
– For which counties agencies accept EPA defaults • The checklist must be included in the EIS
submittal
14
Presenter
Presentation Notes
the checklist will help us match the data submitted to the documentation and help us focus our QA effort on the submitted data.
Example of Checklist
15
Presenter
Presentation Notes
Indicates which tables have been revised from EPA defaults. Check all tables if you are submitting a database you created without using the defaults. Column E indicates counties for which you are accepting EPA defaults rather than submitting a CDB. Note only 2 of the 3 Delaware counties are submitted. For the 3rd, Delaware accepts EPA defaults
3. Documentation
• PSC_Documentation.doc (or docx) • A word file that explains the source of SLT
provided input data. A .doc or .docx file is required
• Additional supporting files of any format are optional (e.g., .pdf or .xls)
16
4. CDB Folders • PSC_County_Database.zip • Zipped file containing individual folders for each county’s
CDB, and labeled with a creation date in the name (example “c10001y2011_20120601.”
• CDBs must include a minimum of the 24 tables listed in the summary checklist for each submitted county.
• The submitter does not need to submit CDBs for counties where he has no improvements over EPA defaults.
• There will be no representative county submittals. • Format is the same MySQL files that MOVES uses. • EACH CDB SUBMITTAL IS A COMPLETE
REPLACEMENT OF PREVIOUS SUBMITTALS
17
Presenter
Presentation Notes
cCCCCCy2011_YYYYMMDD where CCCCC is the FIPS code and YYYYMMDD is the modification date for the database. This example is for county FIP=10001, for the base year 2011. Creation date is June 1, 2012
Submittal Package
18
Presenter
Presentation Notes
Note naming convertion: cCCCCCy2011_YYYYMMDD where CCCCC is the FIPS code and YYYYMMDD is the modification date for the database. Note that the name of the zip file is imbedded in the xml Note that the naming convention for the files includes the program system code Inside the zip submittal, find, - the XML file that references the agency submittal file - the zipped CDBs - the checklist - documentation
Creating XML HEADER
• 2 ways
– Using staging tables • CERS and ExchangeHeader tables only --
currently under revision
– Edit XML available from 2011 NEI page
19
Presenter
Presentation Notes
The staging tables and bridge tool are being updated to allow for NCD and CDB submittals. When revised, you will be able to indicate these submittal types, instead of indicating “onroad” or “nonroad” as was used in 2008 NEI. We’ll go over the bridge tool use later in the presentation. You can also edit a sample xml file using notepad or other editor. Example XML will be posted with other onroad instructions.
Use note pad or other text editor to revise “Sample_CDB_File.zip” can be whatever your file is named. Property name “CDBDataFile” is new. Staging tables (covered later in this presentation) will include this too.
EIS Feedback
• EIS checks – Required files and folders are present – Naming conventions and formats are met – Counties in QA report match counties in CDB
folders – QA Report confirms there are no errors from
the QA tool checks
21
Presenter
Presentation Notes
Example feedback is not yet available In this case, the QA is mainly done on the inputs outside of EIS. EIS only makes checks that all files are present, in proper format
Feedback Report for CDBs Submittal
22
Presenter
Presentation Notes
This screen shot from features currently under development Just like feedback for other types of submittals: go to “Reports”, “Submission History”. Feedback will be available here. Note “request inventory developer assistance” link. EPA cannot see your qa submittal unless you click this. This screenshot is a view of a updates to EIS that are not yet employed.
What EPA will do with submittals
• Collect and compile submitted CDBs • Run QA tool again • Contact agencies with questions • Run latest available MOVES model for
CAP/HAP at monthly or finer level • Load emissions into EIS
23
Presenter
Presentation Notes
EPA may use a more sophisticated tool than what we post for submitters. MOVES model could change Currently plan to load annual emissions.
Emissions Submittals
• Agencies may submit emissions, but inputs are preferred
• Multiple emissions data are accessible in EIS. If an agency submits, EPA and SLT data will be present.
24
Presenter
Presentation Notes
Again, we strongly encourage inputs over emissions submittals
Onroad Emissions Submittals
• Requirements for submitting onroad emissions inventory – CERS – Exchange Header – Location – Emissions Process – Reporting Period – Emissions
• Optional – Excluded Location Parameter
25
Presenter
Presentation Notes
These are the ‘staging tables’ that you would need in order to create an onroad EMISSION submittal. Use the ‘bridge tool’ available from the EIS gateway, to create the empty tables. Then fill them in with your data.
Required - CERS
• Required – User ID (EIS login) – Program System Code – Emissions Year
• Optional – Model – Model Version – Emissions Creation Date – Submittal Comment
26
Presenter
Presentation Notes
Use “Model” and “Model Version” to include MOVES model details
27
Required: - AuthorName - OrganizationName - DocumentTitle (EIS) - DataFlowName (EIS_v1_0) - SubmissionType ("QA" or "Production") - PropertyName ("Data Category") - PropertyValue ("Onroad") Optional: - Keywords - Comments - PropertyName ("CDBDataFile" - required when submitting CDB data) - PropertyValue (the name of the CDB zip file being submitted - required when submitting CDB data)
Required - Exchange Header
Required - Location
• Required – State/County FIPS or Tribal Code
• Optional
– Census Tract Identifier – Shape Identifier – Location Comment
28
Required - Emissions Process
• Required – State/County FIPS or Tribal Code – Source Classification Code – Emissions Type Code
• Optional – Census Tract – Shape Identifier – Process Comment
29
Required - Reporting Period
• Required – State/County FIPS or Tribal Code – Source Classification Code – Emissions Type Code – Reporting Period Type Code – Calculation Parameter Type Code - Only Onroad (“I” for input) – Calculation Parameter Value and UOM – Only Onroad (VMT,
E3Mile) – Calculation Parameter Material Code – Only Onroad (“368” for
vehicle) • Optional
– Census Tract and Shape Identifier – Calculation Data Year – Only Onroad – Calculation Data Source – Only Onroad – Reporting Period Comment 30
Required - Emissions
• Required – State/County FIPS or Tribal Code – Source Classification Code – Emissions Type Code – Reporting Period type Code – Pollutant Code – Total Emissions and UOM
• Optional – Census Tract and Shape Identifier – Emissions Comment
31
Creating XML File via the Bridge Tool
Select the Data Category being converted.
Browse for Access file and select “Start”.
REMEMBER: The Bridge Tool works on Access 2003. If your file is saved as Access 2007 or later, you will need to do a “save as” to Access 2003 prior to using the Bridge Tool.
Presenter
Presentation Notes
Once you have completed your staging tables, it is time to convert your file to an xml compatible format using the EIS Bridge Tool. This Bridge Tool can be found on the EIS Gateway, under Reference Data, EIS Bridge. The file will install onto your desktop. When you open the Bridge Tool, first select the option to convert populated staging tables to CERS XML. Then select the data category that is being converted. Last select the Access staging table. It is important to remember that the Bridge Tool is based on Access2003. If you have a newer version of Access, you must save the file as Access 2003 prior to using the Bridge Tool.
Common Bridge Tool Errors
• Look at your xml file prior to zipping it using Note Pad or your web browser. Make sure you see all of the components.
Presenter
Presentation Notes
If your xml is successful, you should be able to see detail all the way to emissions in your xml. If the file is small in size, it’s probably broken. This error is generally tied to the use of EIS Identifiers. If the submitter uses the EIS Identifiers in one table they must be used in all tables. You can not submit the EIS ID for a process in one table and no process in another.
Submitting the zipped XML File • Two methods
– Node-to-node – CDX web client (most common method)
• https://nodewebrss.epa.gov/user/Login.aspx • Use Gateway login and password
• QA and Production Environment – QA is always open to check your data. Does not
change anything in the EIS – Production submission is your official submission
and will update the EIS – Recommend always sending to QA first
Presenter
Presentation Notes
There are two methods of submitting to EIS: 1) node-to-node and 2) cdx web client. We will talk about the CDX web client as this is the most common method used by SLTs. There are two different types of environments that you can send your data to; QA and Production. QA will not change anything in EIS, but will check your submission for any critical errors which may prevent some of your data from being accepted. The Production environment is your official submission and will update EIS.
Browse for your ZIPPED XML submission file. Then complete your email notification. This can be more then one email address. Then select “Submit”.
Presenter
Presentation Notes
Email addresses here are optional, since you will automatically get notification at your log in email address.
Email Notifications • First email, from “CDXNotification”, immediate
– Transaction Status: Pending
• Second email, also from “CDXNotification” , when EIS completes processing – Transaction Status: Completed. Feedback report is available at
EIS Gateway
• Third email, from “noreply” (EIS Gateway), on quarter hours – Status : Completed or Failed
• Wrong file submission error – Usually a zipped Access file is submitted instead of the xml file
• Window closed error – “User, agency, submission year not authorized”
• Completed might be for an XML file containing no data
• Go to EIS Gateway and read the Feedback Report and resolve any critical errors and Potential Duplicates
Presenter
Presentation Notes
You will receive three notifications from CDX and the EIS gateway itself with regard to your submission. The third one, from the EIS Gateway (sender shows “noreply”) is providing the only important information – Completed or FAILED.
39
The Feedback Report
• Summary Page – Name of submitter – What environment submissions was made to
• QA or Production – Data Category submitted
• Onroad – Total number of critical and warning errors.
Presenter
Presentation Notes
The first worksheet is the Summary page. This page give you the submitters id, submission date and time; the status of the submission; a CDX tracking ID; data category; total system, critical and warning errors.
Feedback Report Critical Errors
• The most important page of your feedback report
• All critical errors must be resolved prior to submitting to Production
Feedback
42
Presenter
Presentation Notes
Summary tab shows no errors or warnings
Feedback
43
Presenter
Presentation Notes
If you added emissions data, you should see statistics to show additions and updates. It’s a good idea to track number of records in each table and confirm they make sense. For example, each table should include the same number of locations (counties). Em processes and reporting periods should be equal. A CDB submittal will have zeros in this table since they are not emissions records.
When will my data show up in EIS?
• Onroad data on the Gateway is available immediately
• Reports available the next day
Presenter
Presentation Notes
Onroad data is available immediately after submission under the Nonpoint/Onroad/Nonroad Emissions link below the View/Add/Edit. The Emissions Summary by Geography report will be available the following day after an overnight system refresh.
Nonpoint/Onroad/Nonroad Emissions
Presenter
Presentation Notes
Under the Nonpoint/Onroad/Nonroad Emissions, filter on your agency and the nonpoint data category. This will result in a list of SCCs reported by your agency. If you click on a indivdual SCC… Can edit emissions here, but that’d be rare with onroad
Agency Submission History Report
Select the inventory year of interest
Presenter
Presentation Notes
The agency submission history report will give you a generalized report on what as been reported for your agency. First select the inventory year of interest and then select the data category. The date and time shown are the date and time of the last submission for that inventory year and that data category. NOTE: new categories are being added here to indicate MOVES_CDB and NONROAD_NCD input submittals Only the most recent submittal date shows up here.
How do I get data out of EIS?
Presenter
Presentation Notes
Getting data back out of EIS is done through the Request Reports section of the Gateway. We will get into more in depth information during our reports course, but main report that will be used for Nonpoint is the Emission Summary by Geography.
Report Downloads
Presenter
Presentation Notes
The report download sections shows all reports which have been requested from your agency. If you select the looking glass icon you can see the criteria for each report. This is helpful if someone else as already requested the report that you need. The red “x” indicates that the report is being processed. The download icon appears when your report is ready. These reports kick off every 20 minutes and are downloaded in .csv format.
How does EPA Check Your Data?
• Again, inputs are strongly preferred. We have QA to fix errors in advance of running MOVES
• Submitted emissions are compared to EPA’s for pollutants covered, disagreement between CAP/HAP, anomalous emis type/pol combinations, SCC coverage, etc.
Common Problems
• Overwriting previous submittals. Several submitters in trying to update/correct emissions values, submitted only one pollutant which overwrote previous submittal which contained many pollutants
• Poor use of emission type. For example, all emissions as evap does not make sense.
• Bad emis type/pollutant combinations (e.g., evap pm)
