html5-img
1 / 31

What’s the Latest Version of MDC ?

What’s the Latest Version of MDC ?. The current version of MDC is 4.2.46, revised as of March 15, 2004 You can download MDC 4.2.46 from the web,at: http://www.epa.gov/airmarkets/monitoring/mdc/index.html. What Has Changed ?.

talia
Télécharger la présentation

What’s the Latest Version of MDC ?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. What’s the Latest Version of MDC ? • The current version of MDC is 4.2.46, revised as of March 15, 2004 • You can download MDC 4.2.46 from the web,at: http://www.epa.gov/airmarkets/monitoring/mdc/index.html

  2. What Has Changed ? • The QA Status Evaluation feature of MDC Hourly no longer relies on RTs 697, 698 and 699 to determine: • RATA deadline extensions due to non-QA operating quarters • Linearity exemptions due to non-QA operating quarters • Linearity exemptions for SO2 and NOx span values < 30 ppm • RATA and Linearity QA status during grace periods

  3. What Has Changed ? (cont’d) • For dual-range components (e.g., SO2A, NOXA), MDC 4.2.46 checks the linearity status of both ranges to make sure all required tests were performed. • For new (or newly-affected) units, logic has been added for tracking initial certifications when conditional data validation is used • For new (or newly-affected) units, v 4.2.46 can properly assess initial certifications that span across calendar quarters

  4. Identifying Non-QA Operating Quarters • Previous version of MDC • For an extension of a RATA deadline, MDC would look for RT 697 with a Type of Extension code of “1”, indicating a non-QA operating quarter • For a linearity check exemption, MDC would look for RT 698 with a Basis for Exemption code of “1”, indicating a non-QA operating quarter

  5. Identifying Non-QA Operating Quarters (cont’d) • MDC version 4.2.46 • Relies on actual unit or stack operating hours • When the monitoring plan is imported, MDC extracts and stores the quarterly unit/stack operating hours from RT 301 (or 307) • Quarterly operating hour information can be accessed in the Monitoring Plan Information Edit mode, using the new “Op Hours” tab

  6. Grace Periods • Previous version of MDC • When a RATA or linearity check expired, MDC would look for a RT 699 grace period claim • If no valid RT 699 was found, an out-of-control status was assigned to the monitoring system after the test expiration date, continuing until a RATA or linearity check was passed

  7. Grace Periods • MDC version 4.2.46 • Automatically applies a grace period of 168 operating hours (for a linearity check) or 720 operating hours (for a RATA) after the test expiration date • Invalidates data only if the grace period expires and the required test has not been passed • Still relies on the Reason for Test code (“G”) in RT 602 or 611 to identify a grace period test

  8. Low-Span Linearity Exemptions • Previous version of MDC • Would look for a RT 698 linearity check exemption claim for an SO2 or NOx span value < 30 ppm (Basis for Exemption code “4”)

  9. Low-Span Linearity Exemptions (cont’d) • MDC version 4.2.46 • MDC Hourly checks the SO2 and NOx span value(s) in the active RT(s) 530, to determine whether any monitoring scale qualifies for a low-span (< 30 ppm) linearity exemption. If so, a linearity QA status of “exempt” is assigned to that scale.

  10. Dual-Range Analyzers • Previous version of MDC • MDC Hourly would only evaluate the linearity QA status of the scale(s) that were used to report data during the quarter

  11. Dual-Range Analyzers (cont’d) • MDC version 4.2.46 • A second logic loop has been added, so that the linearity QA status of both ranges is checked. If either range is out-of-control (OOC), the QA status for the monitoring system is OOC. • A new monitoring plan check, “NBP-33C” has been added to ensure that dual-range component types (SO2A, NOXA) are not being reported in RT 510 for single-span units

  12. Dual-Range Analyzers (cont’d) • Linearity specification “LIN-10A” has been modified and a new specification “LIN-10C” has been added so that an error message is generated if the span scale in RTs 601 and 602 is left blank for a dual-range component type (e.g., SO2A, NOXA)

  13. Some “Bugs” that Have Been Fixed • RT 698 • Fixed the logic so that MDC looks for and applies linearity exemption type code “2” (analyzer range not used during the quarter) • RT 556 Events Requiring Linearity Checks • Version 4.2.46 allows the date & hour of the “event” in RT 556 to be the same as the date & hour of completion of the linearity check. This applies mainly to span changes.

  14. Some “Bugs” that Have Been Fixed (cont’d) • Initial Certification w/ Conditional Data • Added logic to see if initial certification testing for new and newly-affected units is completed within 90 calendar days or 180 operating days (as applicable), when conditional data validation is used. • This logic is applied only if RT 556 is submitted and the “Operating Days” information is provided using the new “Op Hours” tab.

  15. Some “Bugs” that Have Been Fixed (cont’d) • Initial Certifications that Span Quarters • Added logic to determine when the standard Appendix B QA test schedule begins for certification tests that span across calendar quarters • This requires RT 556 to be submitted,even if conditional data validation is not used (EDR Instructions need to be modified). Last test date must be accurately represented in RT 556.

  16. Are 69X Records Now Obsolete ? • No! RTs 69X are still required. However, version 4.2.46 does not rely as heavily on the information in these record types as did the previous MDC versions. Version 4.2.46 still looks for and evaluates the following RT 69X claims: • RT 695 single-load flow RATA claims • Certain RT 697 RATA Extensions/Exemptions:

  17. Are 69X Records Now Obsolete ? (cont’d) • Code “2”: Extension of SO2 RATA deadline---only very low sulfur fuel was combusted this quarter • Code “3”: On-going SO2 RATA exemption claimed---only very low sulfur fuel was combusted this quarter • Code “4”: Conditional SO2 RATA exemption claimed---year-to-date usage of high-sulfur fuel is < 480 hours • Code “5”: Conditional RATA exemption for non-redundant backup system---system year-to-date usage < 720 hours and < 8 quarters since last RATA

  18. Are 69X Records Now Obsolete ? (cont’d) • Code “6”: On-going SO2 RATA exemption lost • Code “7”: ConditionalSO2 RATA exemption lost • Code “8”: Conditional RATA exemption lost for a non-redundant backup system • Code “9”: Permission obtained from EPA to perform a single-load RATA at a non-normal load • RT 698 linearity exemption claim for a range that was not used during the quarter (Code “2”)

  19. “Loose Ends” • A bias adjustment factor (BAF) issue surfaced after the March 15, 2004 release of MDC version 4.2.46. EPA “patched” the E-audit software to address it. However, the patched version will not be available to users until next quarter. This is how the patched software evaluates BAFs when conditional data validation is used:

  20. “Loose Ends” (cont’d) • If RT 556 indicates a monitor is replaced and the system ID is changed, a BAF of 1.000 is assumed from start of conditional data until the RATA of the new system is completed. • If RT 556 indicates a monitor is replaced, but the system ID is not changed, a BAF of 1.000 (not the BAF from the previous RATA) is assumed from start of conditional data until the recertification RATA is completed.

  21. “Loose Ends” (cont’d) • If RT 556 does not indicate a system or analyzer replacement but the “event” requires a RATA, apply the BAF from the previous RATA during the conditional data period.

  22. Technical Assistance • Technical assistance is available as follows to help you use the MDC software: • Inside the MDC software is a “Help” system, which contains: • All of the monitoring plan, QA test, and hourly checking specifications • The EDR Instructions • Flow charts showing how the linearity and RATA QA status is determined

  23. Technical Assistance (cont’d) • Self-study tutorials are available on CD-ROM: • MDC Basics (How to use MDC) • Low Mass Emissions Tutorial (how to use MDC to generate monitoring plans and quarterly reports for LME units under 75.19) • To obtain the tutorials, send an E-mail request to mdc@pqa.com, to the attention of Nat Rogers. Indicate which one(s) you want and include your mailing address

  24. Technical Assistance (cont’d) • If you have questions about downloading or installing the software, contact PQA at (434) 979-3700 or mdc@pqa.com • If you have questions about any of the monitoring plan, QA test or hourly specifications, contact Kim-Oanh T. Nguyen, at (202) 343-9102 or nguyen.kim@epa.gov or thantrucvo@aol.com

  25. Technical Assistance (cont’d) • Starting in 2nd quarter of 2004, EPA will post on the MDC website the current monitoring plan and QA test information for all affected sources. This will allow sources to compare their MP and QA information against EPA’s database prior to submitting the quarterly reports. EPA will work with the sources to resolve any discrepancies.

More Related