![[logo] US EPA](http://www.epa.gov/epafiles/images/logo_epaseal.gif){kind=logo}
Questions and Answers: Client Submission Tool
ECMPS Additional Information
New FAQs appear at the beginning of each section.
Q: Will the new ECMPS Client Tool automatically edit my data prior to submission if calculation errors are identified?
A: No. The ECMPS Client Tool will NOT automatically edit data prior to submission if calculation errors are identified. The ECMPS Client Tool will recalculate reported calculated values and test results from the primary measurement data, and will identify as an error any reported calculated values or reported test results that do not agree with EPA recalculated values (values that fall outside the acceptable tolerances). For hourly emission calculations, the ECMPS Client Tool will NOT have the capability for editing calculated values that fall outside the acceptable tolerances. These corrections must be made in the source's data acquisition and handling system (DAHS). For calculated test results, the ECMPS Client Tool will allow the user to replace their calculated result values with the EPA accepted value. The user may choose not to use this functionality, and instead correct the calculated results in their DAHS (or whatever software was used to create the electronic test record).
Q: Will I be required to correct all discrepancies between reported calculated values and EPA's recalculated values?
A: No. The only discrepancies that must be corrected are calculated values that fall outside of the acceptable tolerances. EPA will accept all calculated values that are within the established tolerance levels.
Q: Will the ECMPS Client Tool have an LME file generator?
A: Yes. The ECMPS Client Tool will give users the ability to generate files for LME units.
Q: Will the ECMPS Client Tool include a converter in order to be able to load old EDRs (as far back as 1993)?
A: It will not be necessary to import historical data because the ECMPS Client Tool is not designed to be a database for storing historical data. Primarily, the ECMPS Client Tool is a checking and submission tool which will only include the data necessary for checking and submitting new data. Users will be able to retrieve previously submitted data necessary for performing checks on future submissions. The data will only go back to 2003, which should be adequate for users who will begin to use the ECMPS Client Tool for official submissions in 2008.
Q: Will the Client Tool have functionality to allow users to back-up the SQL server database?
A: Yes, the Client Tool will have a backup and restore feature.
Q: For sources who submit EDRs generated at various plants from one corporate location, is a Client Tool required at each plant?
A: Whether a Client Tool is required at each plant depends on the source's business process. If the XML data files are generated at the plants and sent directly to one corporate location without being quality assured at the plant, then a Client Tool isn't necessarily needed at each plant. However, if the XML data files must be quality assured prior to being sent to the corporate location, then each plant will need to have a Client Tool.
EPA has developed agent types for the ECMPS process, one of which has the ability to download data from the CAMD Host System but cannot submit data to the CAMD Host System. This agent type could be used for sources who quality assure the data prior to providing it to the corporate office.
Q: Will the Client Tool have the ability to import XML data files from different plants?
A: Yes, the Client Tool will have the ability to import an XML data file for any plant.
Q: What type of schema validation is performed when files are imported by the client desktop application?
A: The import functionality checks the XML files using several criteria based on the XML schema. The first check is to ensure the file is indeed an XML file. Next, the file is checked to ensure that the file has a data type identifier which will denote whether the file contains monitoring plan, quality assurance and certification, or emissions data. The third item which is checked is whether the file contains a minimal amount of data which will allow for additional checks. For instance, the XML file must contain an ORISPL value. The final import check is against the appropriate XML schema. This check finds problems related to the various pieces of data in the file. For example, any invalid codes will be flagged as an import error.
Q: Will the Client Tool recalculate quality assurance and certification test results and submit the recalculated test results to the EPA database?
A: The Client Tool will recalculate quality assurance and certification test results. If the imported test results contain errors, results outside of accepted tolerance levels, the user will have three options. First, the user may correct the test results outside of the Client Tool and then import the corrected data. Second, the user may correct the test data in the Client Tool using edit functionality similar to the current version of EPA's MDC software. Finally, the Client Tool will also allow the user accept the EPA calculated results and use that data for submittal.
Note that the Client Tool's edit capability will allow the user to create the electronic test results by entering in the appropriate test data. This optional functionality will likely be used by sources that currently take advantage of this capability in the MDC software.
Q: Will the tables for the Client Tool database be published?
A: EPA will post on the ECMPS web site a series of Client Tool Database Design documents. Each document is specific to a category of data and will be released at the same time as the DRAFT XML schema for that category of data.
Q: Will I need other software tools besides the Client Tool to view my data?
A: The ECMPS Client Tool will include functionality to allow you to review imported data in an easy to view format. However, if you typically use third party software to view and analyze your data, the ECMPS Client Tool will allow you to export data in a format suitable for use with software that allows viewing of XML files.
Q: Will the new Client Tool use SecuRemote as the method of security?
A: No, the ECMPS process will take advantage of vastly different security procedures, which do not include SecuRemote.
Q: Under the new process, will the DAHS send the data directly to the Client Tool?
A: There will be no functionality for direct interaction between the Client Tool and a DAHS.
Q: Will I still use my DAHS to generate the electronic data report file?
A: Yes, you will still use your DAHS software to generate an XML EDR file that will be imported into the Client Tool. The Client Tool is your checking and submission "portal" to the EPA database.
Q: Does the new Percent Monitor Availability (PMA) calculation and missing data application fall within the scope of this project?
A: This issue will be part of proposed rule changes. EPA is proposing to require the use of the PMA on an hour by hour basis (rather than using the PMA calculated at the end of a missing data period) to determine what "tier" of substitute data to utilize on an hour by hour basis. This will keep the substitute data from becoming retroactive when a source has a long missing data period that causes the PMA to go into the more conservative "tiers" of data substitution. Questions regarding this policy change should be directed to Matthew Boze of the Emissions Monitoring Branch.
Q: If for some reason a utility can not submit their emissions report by the end of a quarter, will the EPA accept an incomplete report? EPA cannot impose a level of checking that is capable of preventing a source from making a submission to meet the deadline.
A: EPA has always worked with sources to ensure that they are able to meet the regulatory obligations specified under Part 75. Despite the change to the new process, EPA fully intends to continue this practice. Further, EPA does not now impose a level of checking that prevents a source from making a submission, and will continue to check for data that are required under the program regulations.
Through the ECMPS Client Tool, sources are able to submit their data to meet the regulatory deadline although all of the data's critical errors have not been resolved. In these cases, the data is received by the EPA as an XML file, but the data is not loaded into the EPA Host System database. Consequently, sources will need to resolve the critical errors associated with this data and resubmit the data in order for it to be loaded into the EPA Host System database.
Q: What functionality already present in the Monitoring Data Checking (MDC) software will be carried over into the new desktop tool?
A: The ECMPS Client Tool will incorporate most of the functionality present in the current versions of MDC software. Included in the Client Tool will be the ability to maintain, quality assure and submit monitoring plans; create, quality assure and submit quality assurance and certification test data; quality assure emissions data; create the electronic data report for LME sources; and run reports.
Q: At previous stakeholder meetings, concern was expressed about the process for updating software in EPA's desktop application given that many utilities have firewalls that prevent "automatic" updates. How does EPA intend to resolve this issue?
A: One of the features of the ECMPS process is interactive updates to the Client Tool when the source is logged on to the CAMD Host System. However, it was noted that a few affected sources may not be able to take advantage of this feature. To address the firewall issue and any additional security concerns related to upgrading the software, the EPA will also make all updates to the Client Tool available on the Clean Air Markets Division web site. Furthermore, EPA will develop a process for how and when updates to the Client Tool will be made in order to provide users with as much advance notice as possible about updates.
Q: Will security logs be maintained locally in the Client Tool? If a change was made to data through the Client Tool, will there be a log of who made the change and when?
A: Virtually every table in the Client Tool SQL Server database in which data can be modified includes audit fields. When new data is added or data is modified, the audit fields are updated to reflect who made the change and when the change was made.
Q: Will the Client Tool use the same login as the Windows login?
A: No. The Client Tool does not use the Windows login. The primary login for the Client Tool is the User ID and password that is used for the CAMD Business System.
In addition, the Client Tool allows users to establish some local security which requires an additional login for accessing the desktop application. The default setting is for the local security to be turned off.
Q: Can vendors connect their DAHS directly to the Client Tool with a command lime prompt and have DAHS run checks?
A: While EPA did consider this issue, it is not within the scope of the project.
Q: Will the Client Tool be able to monitor a directory and process any file that appears there?
A: This functionality is not within the scope of the project.
Q: Will sources have input into the look/feel and implementation of the Client Tool?
A: During the beta-test period, EPA will entertain comments regarding the ECMPS Client Tool.