310 likes | 444 Vues
Emissions Collection and Monitoring Plan System (ECMPS) Stakeholder Update May 12, 2009 St. Louis, Missouri By Laurel DeSantis Matthew Boze David Ward (Perrin Quarles Associates). Meeting Objectives. Project Update Results From ECMPS Reporting Lessons Learned
E N D
Emissions Collection and Monitoring Plan System (ECMPS) Stakeholder Update May 12, 2009 St. Louis, Missouri By Laurel DeSantis Matthew Boze David Ward (Perrin Quarles Associates)
Meeting Objectives • Project Update • Results From ECMPS Reporting • Lessons Learned • Access and Use of Previously Submitted Data • Resubmission Process • Client Tool Demonstration • ECMPS Resources • Technical Support Process • Questions and Answers • Wrap Up 2
Results From ECMPS Reporting • Successful practices of ECMPS users: • Uninstalled SecuRemote • Ensured PC has the minimum system requirements • Completed CROMERR requirements • Knew CBS/ECMPS user name and password • Assigned Agents early in the process • Corrected unit program dates by contacting EPA • Installed ECMPS software/updates as soon as available
Results From ECMPS Reporting • Successful practices of ECMPS users: • Used all resources provided before contacting tech support • Worked with a vendor to resolve data issues • Provided all necessary information when requesting tech support • Used the Request Tracker system (ecmps-support@pqa.com) • Began evaluating/correcting data early in the reporting month
Lessons Learned • Technical support systems • Modified password reset procedure to enable users to reset their own passwords • Upgraded tech support phone system to handle high volume during peak times • Upgraded technical support tracking software • Used third party service in order to distribute load of software downloads
Lessons Learned • Data Loading • Continued to improve data loading processes • Plan to archive older emissions data • Submission processing • Training materials • Continue posting FAQs to the ECMPS Support website • Improved search and increased FAQs
Lessons Learned • Communication • Continued improvements to ECMPS website and blog • Continued improvements on communicating known issues • Redesigning ECMPS web site in order to enhance navigation • Added a link to known EPA Host outages on ECMPS website • Continue to improve Reporting Instructions
Access and Use of Previously Submitted Data • Availability of Previously Submitted Data (2003 to 2008) • All MP and QA data are available for all sources • Historical EM data are available for all sources who transitioned in 2008 • Historical EM data for all other sources is schedule to be completed by the end of 2009
Access and Use of Previously Submitted Data • Use of Previously Submitted Data • Data are available for reference or resubmission purposes • Generally, there is no need to retrieve previously submitted data • Retrieval of previously submitted data can cause evaluation problems
Resubmission Process • General rules for Resubmission of data • Permission is required to resubmit QA and EM data • All MP and QA data should be resubmitted using the Client Tool
Resubmission Process • Loading of Historical Emissions Data • All historical emissions data (2003 through 2008) submitted via legacy systems are scheduled to be migrated to ECMPS • Currently, all historical emissions data from sources who transitioned to ECMPS in 2008 have been loaded • The historical emissions data for all other sources will be completed in calendar year 2009 (data from 2008 is scheduled to be completed in June 2009) • The process for migrating remaining historical emissions data will take place in stages in reverse chronological order, e.g., first 2008 then 2007 will be migrated
Resubmission Process • Emissions Resubmission Processes • Because historical EM data (2008 and earlier) have not been loaded for sources who transitioned to ECMPS in 2009, there are two processes for EM resubmission: • Sources who transitioned to ECMPS in 2008 should resubmit EM data using the Client Tool • All other sources who need to resubmit historical EM data (2008 and earlier) will need to use a temporary resubmission process -- technical support will guide sources through this process • Any source who needs to resubmit data should contact Technical Support and copy the source’s EPA Analyst
ECMPS Resources • There are many ECMPS resources available to stakeholders • You should review these resources before sending requests to the technical support staff • Resources include: • Tutorials • CAMD and PQA ECMPS websites • PQA ECMPS blog • Stakeholder Meeting presentations • Other resources (see ECMPS Resources handout)
ECMPS Resources • ECMPS Tutorials • http://ecmps.pqa.com/tutorials.shtml • Interactive, multimedia videos • Specific topics covered in approximately 10 minutes • Watch on the Web or download to CD • Closed captioning available • CAMD ECMPS web site • http://www.epa.gov/airmarkets/business/ecmps/index.html • PQA ECMPS web site • http://ecmps.pqa.com/
ECMPS Resources • PQA ECMPS blog • Provides a central location for up-to-date information about ECMPS Testing. • Presents answers to frequently asked technical support questions. • Includes information organized by category on how to use the Client Tool. • Allows users to receive regular ECMPS information via subscriptions. • http://ecmps.pqa.com/blog/ • Stakeholder meeting presentations are available on both the CAMD and PQA ECMPS web sites
Technical Support Process • Technical support questions are handled through a technical support request ticket management system • This system tracks each issue from its beginning to its resolution • System has been in place since July 2007, and has helped CAMD and PQA manage the high volume of support requests from industry • Enables CAMD and PQA to identify reoccurring problems, software bugs, application errors and areas of functionality that are not clear to users
Technical Support Process • In order to ensure your question will be answered quickly please: • Send your questions via email to ecmps-support@pqa.com • Provide as much detail and supporting information as possible • Attach relevant files (XML, PDFs of evaluation reports) • Provide screen shots when available • Please do not: • Send emails directly to a technical support person • Call specific technical support personnel unless you have been asked to do so
Technical Support Process • If the technical support staff has not heard back from you regarding an issue, they may close your existing ticket • You will receive an email indicating that your ticket has been closed • If your issue has not been resolved, simply reply to the ‘closed ticket’ email, and provide an update of the issue as it currently stands
Wrap Up • What is next? • Action items • If you would like to be added to the ECMPS Stakeholder Email group, contact Laurel DeSantis. 31