ECMPS Support

The 2010 Q1 version of the Client Tool has a known issue that generates an incorrect RATA status error.

The error message indicates that OPHOURS, OSHOURS, or OPDAYS is missing for 2009Q4.

This error is being incorrectly generated for sources which have switched from ozone season reporting in 2009 to quarterly reporting in 2010. The evaluation check is not correctly recognizing this reporting frequency change, and the check is determining that data are missing. Because the source was an ozone season reporter in 2009, the data were not required for that source in 2009Q4.

Sources who believe that they are receiving this error incorrectly should contact technical support.

Labels: Known Issues

There is a known issue related to updating the shared database version of the Client Tool. The issue only affects shared database users who are attempting to update from the 2009 Q2 version of the Client Tool to the 2009 Q3 version of the Client Tool. The known issue does not affect users who use a stand-alone version of the Client Tool.

Shared database updates are performed by first updating the Client Tool's shared database. This quarter, users must update their shared database from the 2009 Q2 version to the 2009 Q3 version. (Service Pack 1 for 2009 Q3 only affects the Client Tool. It does not affect the Client Tool shared database.) This is done the database administrator running a script which updates the shared database.

After the shared database has been updated, each Client Tool which connects to the shared database needs to be updated. This is where the known issue occurs. Normally, users can start up their Client Tool, log in to the EPA Host System, and then be guided through the automatic update process built in to the Client Tool. However, when users attempt to start up the Client Tool, an error occurs:


Generally, this error prevents users from continuing and updating their version of the Client Tool. In order to complete the update, shared database users should follow the steps provided on the Shared Database Update page. If the shared database has already been updated, users should only need to perform all of the steps listed under item 7. After the steps have been completed, users will have updated their version of the Client Tool to the 2009 Q3 SP1 version.

After updating to the latest version of the Client Tool, shared database users should no longer receive the error. This error only relates to the 2009 Q3 update, and the error should not occur during future updates of the Client Tool.

Labels: Known Issues

The Q2 release of the production version of the Client Tool was released earlier this month. Since then we have identified several issues. These known issues also apply to the ECMPS Client Tool Preview (CTP) version 2.

Issue
Invalid LME-33-B error on generation of LME data.

Response
We have identified the problem, corrected it, and are testing the solution. It is has not been determined when this solution will be provided to production users.

Work-Around
There is no work-around for this issue. Instead, until the solution has been provided to users, the errors can be suppressed pending CAMD's approval. After the error has been suppressed, you will no longer receive the incorrect error during the generation of emissions data. In order to request that the error be suppressed, send an email to ecmps-support@pqa.com.

Appendix D CO2 and the Formula Identifier
In the emissions evaluation, you might receive an HOURDHV-29-A error which leaves you scratching your head. The reason is that the reporting instructions are not as clear as they should be regarding when the formula identifier should be reported in the Derived Hourly Value (DHV) record.

Response
The instructions simply indicate that the formula identifier that is used for the calculation of the parameter should be reported. For Appendix D CO2, this is partially correct. The formula identifier should be reported if there are multiple fuels for the hour. In other words, if a formula was necessary for the summation, it needs to be reported. However, in the case where there is only a single fuel for the hour, the formula identifier should not be reported.

The reporting instructions will be modified to make it clear when it is necessary to report the formula identifier in the DHV record.

Work-Around
This is not really a work-around so much as modifying the reporting of the DHV record. Only report the formula identifier in the DHV record for hours in which there are multiple fuels.

Labels: Known Issues

The Q2 release of the production version of the Client Tool was released earlier this month. Since then we have identified several issues. All of the following relate to the production version of the Client Tool. They do not apply to the ECMPS Client Tool Preview (CTP).

Issue
Adding or editing Analyzer Range data on the Add/Edit screen will cause an error.

Response
We have identified the problem, corrected it, and are testing the solution. It is has not been determined when this solution will be provided to production users.

Work-Around
Users can complete the following steps in order to edit Analyzer Range data:

1. Export the monitoring plan XML file.
2. Edit the Analyzer Range data record which needs to be modified.
3. In the Add/Edit Analyzer Range screen, delete the record which needs to be modified.
4. Import the updated monitoring plan XML file.
5. The updated record should now appear in the Add/Edit Analyzer Range data screen.

To add an Analyzer Range data record, simply add it to the monitoring plan XML file and import the file into the Client Tool.

Issue
Editing and deleting certain QA data records on the Add/Edit screens will cause an error. This issue affects the following data:

• Appendix E Heat Input from Gas Data
• Appendix E Heat Input from Oil Data
• Calibration Injection Data
• Cycle Time Injection Data
• Linearity Injection Data
• RATA Traverse Data
• Unit Default Test Run Data

Response
We have identified the problem, corrected it, and are testing the solution. It is has not been determined when this solution will be provided to production users.

Work-Around
Users must import changes and deletions for QA data affected by this issue.

Issue
Previously Submitted Emissions Data cannot be Retrieved through the Retrieve Module

Response
We are working to complete the data loading of emissions data which were previously submitted from quarter 1 2003 to quarter 1 2008.

It is not necessary to be able to retrieve previously submitted emissions data in order to submit any data related to your 2008 quarter 2 emissions data submission. During synchronization, the Client Tool retrieves from the EPA Host System all of the previously submitted data necessary for submitting all data related to your 2008 quarter 2 submission.

Labels: Known Issues