Preventing and Resolving Reporting Errors Using Monitor Data Checking Software (MDC)

1. Preventing and Resolving Reporting Errors Using Monitor Data Checking Software (MDC) Louis Nichols Clean Air Markets Division

2. Why Check QA/QC Status? • Catch reporting errors prior to submitting electronic data reports (EDR) • Avoid triggering negative audit results with resulting notice to Designated Representative • Assure that data will not be disallowed at true-up • Identify QA/QC problems early and therefore minimize impact on data (limit substitute data)

3. SOFTWARE TOOLSMDC vs. MDC-hourly • MDC • MDC is a tool primarily used to check the reported monitoring plan and QA tests for reporting and calculation errors. • MDC also acts as a database of Monitoring Plan and QA test information for the MDC-hourly software. • MDC-hourly • MDC-hourly is a tool which evaluates the validity of hourly emissions data in relation to the MP and QA test data • MDC-hourly also checks the emission calculations

4. MDC Blue – MP/QA Database

5. MDC Hourly – Analyzes Hourly Data

6. Step One: Load the Current MP • You must assure that the most current monitoring plan is loaded into the MDC software. • Assure that old monitoring plan records are properly closed out by: • Loading in previously submitted monitoring plan • Then load the new monitoring plan and evaluate and review. • This will mimic the update to our system ie. RT536 Range of Operation: (See hints)

7. Step Two: Load Last RATA • Load the RATA completed prior to quarter of interest into MDC. • No need to load hourly data from previous quarters if previous year or quarter is not of interest. • In this case, use the following MDC command: File>Import Monitoring Plan and/or QA Data

8. Loading the Current RATA (if applicable) • For a RATA completed in the current quarter, you may either: • Import the QA data into MDC prior to loading the hourly emissions data into MDC-hourly by using the following MDC command: File>Import Monitoring Plan and/or QA Data ; or • Import the hourly data and the QA data simultaneously using the following MDC command: File >Import Hourly and MP/QA Data • When it prompts you with “Do you also want to import monitoring plan (RT 5xx) and QA test (RTxx) data?”, choose “yes”.

9. Step Three: Load Linearity Checks • Load the last linearity check from a quarter prior to the quarter of interest into MDC. • No need to load hourly data from previous quarters if previous year or quarter not of interest. • In this case, use the MDC command: File>Import Monitoring Plan and/or QA Data

10. Loading the Current Linearity(if applicable) • For the linearity check completed in the current quarter, you may either: • Import the QA data into MDC prior to loading the hourly emissions data into MDC-hourly by using the following MDC command: File>Import Monitoring Plan and/or QA Data ; or • Import the hourly data and the QA data simultaneously using the following MDC command: File >Import Hourly and MP/QA Data • When it prompts you with “Do you also want to import monitoring plan (RT 5xx) and QA test (RTxx) data?”, choose “yes”.

11. Step Four: Adding Unit Operating Hours to Claim Extensions • To claim extensions: add unit operating hours from record type (RT) 301 or RT 307 for any quarters that the QA test is entered but not the hourly data. Use the MDC command:Edit>Monitoring Plan Data (RT 102, RT 5xx) • Find and select Tab OP Hours (RT 301/307) • Select Add • Enter the unit operating hours

12. Adding Operating Hours

13. Step Five: MDC Reports • Monitoring Plan Evaluation Report:Reports>Monitoring Plan Reports>Monitoring Plan Evaluation Report • Will list monitoring plan errors using EPA review criteria • Monitoring Plan Printout:Reports>Monitoring Plan Reports>Monitoring Plan Printout • Useful for verifying monitoring plan is correct and up-to-date • Certification and QA Test Report:Reports>Certification and QA Test Reports>Test Evaluation and Detail Report • Provides a list of reporting or QA test calculation errors identified; and • Provides a printout of the QA test information entered in and easy to read table

14. Step Six: Import Hourly Data • Open MDC-hourly from the MDC menu • Load all quarters of interest into MDC-hourly using the MDC-hourly command:File> Import, Calculate,& Evaluate Hourly Data. • All quarters must be for the same plant, unit and calendar year. You cannot load quarters across year. If you must load more than one year, then repeat process. • Note: Check Import Error Report, print or save report. Check the number of pages at the top and check all pages. Do not ignore this report.

15. MDC Hourly • Check name of plant, Oris code, unit ID and quarters on top of menu. • Create Archive using command: • File>Archive MDC Hourly Data. • Once an archive is created, re-calculation of data is not necessary unless changes are made in MDC to either the Monitoring Plan or QA test information

16. Recalculating QA Status • If recalculation is necessary, recalculate using the the MDC-hourly command File>recalculate hourly data. • At the prompt “Would you like to evaluate QA status? Select “yes”. • Wait for recalculation. •  Archive data.

17. Step Seven: MDC-hourly Reports • Hourly Data Evaluation Report:Reports>Hourly Data Evaluation Report • Lists calculation errors, including BAF application errors on an hourly basis • Hourly Data Evaluation Report calculates the error totals for all parameters and hours which have been imported • QA Status Report:Reports>QA Status Report • Identifies hours where the QA test (linearity or RATA) has either expired or was failed, aborted, invalid or missing, resulting in the data for that hour being considered invalid. • Hours where substitute data was used are not evaluated for QA status and will not be shown as errors on this report

20. Step Eight: Review Detailed Hourly Emissions Data • View hourly data using the command: Review Quarterly Report>Detailed Emissions Data • Emissions Data is organized by parameter (SO2, CO2, NOx) using tabs • All data needed to calculate the parameter of interest are included on the applicable tab. (ie, flow data may appear on the SO2, CO2, and Heat Input tabs) • Note: errors may effect multiple systems as in the case of flow and SO2 systems share the flow monitor, diluent components which effects NOx and Heat input, and fuel flow monitors which effect heat input, SO2, and CO2.

22. Error Codes • All Error codes are listed in the last column on the right side of screen under heading “Error Codes”. • These Error codes match those used on the hourly data evaluation report • A description of the errors for each code can be viewed by clicking on the “viewing glass” icon (view errors) • Toggle between error codes if more than one code is listed in the error code column

24. Hints: Check the RT 556 • Was there a Recertification/Certification Event? Needs RT 556 • Are the dates correct on RT 556? • Is the conditional data flag (C) on the RT 556 if you claim conditional data? • Are there enough RT 556s (one for each system affected by the change)? • If the conditional data goes across quarters include a RT 556 in each EDR.

25. Single Load RATAs – RT 695 • If you did a single load RATA, because the units operates at one load 85% of the time, did you include the RT 695 (annual reporters only)? • If you did a single load RATA because the unit is a peaking unit, did you include the RT 507 claiming peaking unit status?

26. RATA Errors – Wrong Unit Loads • If you get an error that states that the RATA was not performed at the correct load, check the RT 536 to see if it has been update. • Was it updated correctly? • Do not update a RT 536 by just changing the load. You must close out the old RT 536 and then add a new RT 536. • If that does not fix the problem, then contact us and get a history of the RT 536. CAMD may need to purge an old RT 536.