150 likes | 313 Views
Emissions Collection and Monitoring Plan System. EPRI CEMS Users Group Meeting May 4, 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 Rethinking the current process.
E N D
Emissions Collection andMonitoring Plan System EPRI CEMS Users Group Meeting May 4, 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 • Rethinking the current process
Emissions Collection and Monitoring Plan System • ECMPS addresses the emissions and monitoring areas • Includes all of the current processes and legacy systems Monitoring PlanETS-FTP Cert / RecertMDC On-going QA Audit Emissions Submission True-up Petitions Assessment
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)
Creating the Vision for ECMPS • How does CAMD want the new process to work? • What do affected sources want? • What new systems are needed to handle the new process?
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
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
Gathering Input • Used past comments and feedback • Presented project at 2003 EPRI CEMS Meeting in San Diego • Scheduling meetings to discuss project • Soliciting input from stakeholders
Defining Requirements • Areas of work are divided into modules • Submission Process • Checking Definition • Communication and Tracking • Work groups develop requirements for each module • Requirements are based on input from YOU and other stakeholders
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
Status of ECMPS • Developed vision for project • Proving the vision • Defining the submission processes • Defining data checks • Identifying areas of communication and tracking
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
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
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
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