1 / 12

Emissions Collection and Monitoring Plan System

Emissions Collection and Monitoring Plan System. VIM Technologies Users Group Meeting June 9, 2004 Martin W. Husk, EPA. Overview. What is the Emissions Collection and Monitoring Plan System (ECMPS)? Why do we need ECMPS? Vision for the project Status of the project

nelle-rocha
Download Presentation

Emissions Collection and Monitoring Plan System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Emissions Collection andMonitoring Plan System VIM Technologies Users Group Meeting June 9, 2004 Martin W. Husk, EPA

  2. Overview • What is the Emissions Collection and Monitoring Plan System (ECMPS)? • Why do we need ECMPS? • Vision for the project • Status of the project • Rethinking the current process

  3. Emissions Collection and Monitoring Plan System • ECMPS addresses the emissions and monitoring areas • Includes all of the current processes and legacy systems ž Monitoring PlanžETS-FTP ž Cert / RecertžMDC ž On-going QA ž Audit ž Emissions Submissionž True-up ž Petitionsž Assessment

  4. Why ECMPS? • Replaces multiple tools available to check data (ETS-FTP, ETS Mainframe, MDC Hourly, MDC-QR, MDC-FTP) • Replaces multiple tools needed to submit data (ETS-FTP, MDC-FTP) • Eliminates multiple sets of feedback (Instant feedback, Quarterly Review, BAF and OOC, Flow-to-load, ad-hoc reports)

  5. Vision for ECMPS • Create a single tool for ALL users • Ability for industry users to run all checks on desktop prior to submission • Identify and correct errors before submission • Provide one set of feedback • Seamless version updates of tool

  6. Vision for ECMPS (cont’d) • Maintain select data outside of the quarterly report process • Direct access to EPA data through data transfers • Move away from flat files and mainframe • Save time and money

  7. Projected Time Line • Develop applications in 2004 through 2005 • Test the process and system in 2006 • CAMD testers • Industry Beta testers • States and Regions • System to be deployed in First Quarter 2007

  8. Status of ECMPS • Developed vision for project • Proving the vision • Defining the submission processes • Defining data checks • Identifying areas of communication and tracking

  9. Rethinking the Current Process • New and innovative approach to complying with CAMD programs • Changes to the reporting requirements in 40 CFR part 75 • Changes to the Electronic Data Reporting (EDR) format and instructions • Allows gradual transition to a more flexible format for submissions

  10. Proposed Changes to40 CFR part 75 • Initial Monitoring plan to be submitted with certification test notice (21 days prior to testing instead of 45 days) • Monitoring plan no longer part of the quarterly emissions data file • Facility information no longer part of the quarterly emissions data file

  11. Proposed Changes to Reporting • Maintain data outside of the quarterly report process • Facility information • Unit characteristic information • Monitoring plan • Contact information • Some monitoring plan data removed or reported as other records • Other records moved into monitoring plan

  12. Recap of ECMPS • Create an improved process to maintain, check and submit monitoring and emissions related information • Develop a single tool to check and submit data • Change the regulation and reporting instructions to accommodate new process • Receive input from stakeholders throughout the process

More Related