(a) You must submit each report in Table 8 to this subpart that applies to you. If you are required to (or elect to) continuously monitor Hg and/or HCl and/or HF emissions, you must also submit the electronic reports required under appendix A and/or appendix B to the subpart, at the specified frequency.

(b) Unless the Administrator has approved a different schedule for submission of reports under §63.10(a), you must submit each report by the date in Table 8 to this subpart and according to the requirements in paragraphs (b)(1) through (5) of this section.

(1) The first compliance report must cover the period beginning on the compliance date that is specified for your affected source in §63.9984 and ending on June 30 or December 31, whichever date is the first date that occurs at least 180 days after the compliance date that is specified for your source in §63.9984.

(2) The first compliance report must be postmarked or submitted electronically no later than July 31 or January 31, whichever date is the first date following the end of the first calendar half after the compliance date that is specified for your source in §63.9984.

(3) Each subsequent compliance report must cover the semiannual reporting period from January 1 through June 30 or the semiannual reporting period from July 1 through December 31.

(4) Each subsequent compliance report must be postmarked or submitted electronically no later than July 31 or January 31, whichever date is the first date following the end of the semiannual reporting period.

(5) For each affected source that is subject to permitting regulations pursuant to part 70 or part 71 of this chapter, and if the permitting authority has established dates for submitting semiannual reports pursuant to 40 CFR 70.6(a)(3)(iii)(A) or 40 CFR 71.6(a)(3)(iii)(A), you may submit the first and subsequent compliance reports according to the dates the permitting authority has established instead of according to the dates in paragraphs (b)(1) through (4) of this section.

(c) The compliance report must contain the information required in paragraphs (c)(1) through (9) of this section.

(1) The information required by the summary report located in 63.10(e)(3)(vi).

(2) The total fuel use by each affected source subject to an emission limit, for each calendar month within the semiannual reporting period, including, but not limited to, a description of the fuel, whether the fuel has received a non-waste determination by EPA or your basis for concluding that the fuel is not a waste, and the total fuel usage amount with units of measure.

(3) Indicate whether you burned new types of fuel during the reporting period. If you did burn new types of fuel you must include the date of the performance test where that fuel was in use.

(4) Include the date of the most recent tune-up for each EGU. The date of the tune-up is the date the tune-up provisions specified in §63.10021(e)(6) and (7) were completed.

(5) Should you choose to rely on paragraph (2) of the definition of “startup” in §63.10042 for your EGU, for each instance of startup or shutdown you shall:

(i) Include the maximum clean fuel storage capacity and the maximum hourly heat input that can be provided for each clean fuel determined according to the requirements of §63.10032(f).

(ii) Include the information required to be monitored, collected, or recorded according to the requirements of §63.10020(e).

(iii) If you choose to use CEMS to demonstrate compliance with numerical limits, include hourly average CEMS values and hourly average flow values during startup periods or shutdown periods. Use units of milligrams per cubic meter for PM CEMS values, micrograms per cubic meter for Hg CEMS values, and ppmv for HCl, HF, or SO2 CEMS values. Use units of standard cubic meters per hour on a wet basis for flow values.

(iv) If you choose to use a separate sorbent trap measurement system for startup or shutdown reporting periods, include hourly average mercury concentration values in terms of micrograms per cubic meter.

(v) If you choose to use a PM CPMS, include hourly average operating parameter values in terms of the operating limit, as well as the operating parameter to PM correlation equation.

(6) You must report emergency bypass information annually from EGUs with LEE status.

(7) A summary of the results of the annual performance tests and documentation of any operating limits that were reestablished during the test, if applicable. If you are conducting stack tests once every 3 years to maintain LEE status, consistent with §63.10006(b), the date of each stack test conducted during the previous 3 years, a comparison of emission level you achieved in each stack test conducted during the previous 3 years to the 50 percent emission limit threshold required in §63.10005(h)(1)(i), and a statement as to whether there have been any operational changes since the last stack test that could increase emissions.

(8) A certification.

(9) If you have a deviation from any emission limit, work practice standard, or operating limit, you must also submit a brief description of the deviation, the duration of the deviation, emissions point identification, and the cause of the deviation.

(d) For each excess emissions occurring at an affected source where you are using a CMS to comply with that emission limit or operating limit, you must include the information required in §63.10(e)(3)(v) in the compliance report specified in section (c).

(e) Each affected source that has obtained a Title V operating permit pursuant to part 70 or part 71 of this chapter must report all deviations as defined in this subpart in the semiannual monitoring report required by 40 CFR 70.6(a)(3)(iii)(A) or 40 CFR 71.6(a)(3)(iii)(A). If an affected source submits a compliance report pursuant to Table 8 to this subpart along with, or as part of, the semiannual monitoring report required by 40 CFR 70.6(a)(3)(iii)(A) or 40 CFR 71.6(a)(3)(iii)(A), and the compliance report includes all required information concerning deviations from any emission limit, operating limit, or work practice requirement in this subpart, submission of the compliance report satisfies any obligation to report the same deviations in the semiannual monitoring report. Submission of a compliance report does not otherwise affect any obligation the affected source may have to report deviations from permit requirements to the permit authority.

(f) On or after July 1, 2020, within 60 days after the date of completing each performance test, you must submit the performance test reports required by this subpart to the EPA's WebFIRE database by using the Compliance and Emissions Data Reporting Interface (CEDRI) that is accessed through the EPA's Central Data Exchange (CDX) (https://cdx.epa.gov). Performance test data must be submitted in the file format generated through use of EPA's Electronic Reporting Tool (ERT) (see https://www.epa.gov/ttn/chief/ert/index.html). Only data collected using those test methods on the ERT website are subject to this requirement for submitting reports electronically to WebFIRE. Owners or operators who claim that some of the information being submitted for performance tests is confidential business information (CBI) must submit a complete ERT file including information claimed to be CBI on a compact disk or other commonly used electronic storage media (including, but not limited to, flash drives) to EPA. The electronic media must be clearly marked as CBI and mailed to U.S. EPA/OAPQS/CORE CBI Office, Attention: WebFIRE Administrator, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same ERT file with the CBI omitted must be submitted to EPA via CDX as described earlier in this paragraph. At the discretion of the delegated authority, you must also submit these reports, including the confidential business information, to the delegated authority in the format specified by the delegated authority.

(1) On or after July 1, 2020, within 60 days after the date of completing each CEMS (SO2, PM, HCl, HF, and Hg) performance evaluation test, as defined in §63.2 and required by this subpart, you must submit the relative accuracy test audit (RATA) data (or, for PM CEMS, RCA and RRA data) required by this subpart to EPA's WebFIRE database by using CEDRI that is accessed through EPA's CDX (https://cdx.epa.gov). The RATA data shall be submitted in the file format generated through use of EPA's Electronic Reporting Tool (ERT) (https://www.epa.gov/ttn/chief/ert/index.html). Only RATA data compounds listed on the ERT website are subject to this requirement. Owners or operators who claim that some of the information being submitted for RATAs is confidential business information (CBI) shall submit a complete ERT file including information claimed to be CBI on a compact disk or other commonly used electronic storage media (including, but not limited to, flash drives) by registered letter to EPA and the same ERT file with the CBI omitted to EPA via CDX as described earlier in this paragraph. The compact disk or other commonly used electronic storage media shall be clearly marked as CBI and mailed to U.S. EPA/OAPQS/CORE CBI Office, Attention: WebFIRE Administrator, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. At the discretion of the delegated authority, owners or operators shall also submit these RATAs to the delegated authority in the format specified by the delegated authority. Owners or operators shall submit calibration error testing, drift checks, and other information required in the performance evaluation as described in §63.2 and as required in this chapter.

(2) On or after July 1, 2020, for a PM CEMS, PM CPMS, or approved alternative monitoring using a HAP metals CEMS, within 60 days after the reporting periods ending on March 31st, June 30th, September 30th, and December 31st, you must submit quarterly reports to the EPA's WebFIRE database by using the CEDRI that is accessed through the EPA's CDX (https://cdx.epa.gov). You must use the appropriate electronic reporting form in CEDRI or provide an alternate electronic file consistent with EPA's reporting form output format. For each reporting period, the quarterly reports must include all of the calculated 30-boiler operating day rolling average values derived from the CEMS and PM CPMS.

(3) Reports for an SO2 CEMS, a Hg CEMS or sorbent trap monitoring system, an HCl or HF CEMS, and any supporting monitors for such systems (such as a diluent or moisture monitor) shall be submitted using the ECMPS Client Tool, as provided for in Appendices A and B to this subpart and §63.10021(f).

(4) On or after July 1, 2020, submit the compliance reports required under paragraphs (c) and (d) of this section and the notification of compliance status required under §63.10030(e) to the EPA's WebFIRE database by using the CEDRI that is accessed through the EPA's CDX (https://cdx.epa.gov). You must use the appropriate electronic reporting form in CEDRI or provide an alternate electronic file consistent with EPA's reporting form output format.

(5) All reports required by this subpart not subject to the requirements in paragraphs (f) introductory text and (f)(1) through (4) of this section must be sent to the Administrator at the appropriate address listed in §63.13. If acceptable to both the Administrator and the owner or operator of an EGU, these reports may be submitted on electronic media. The Administrator retains the right to require submittal of reports subject to paragraphs (f) introductory text and (f)(1) through (4) of this section in paper format.

(6) Prior to July 1, 2020, all reports subject to electronic submittal in paragraphs (f) introductory text, (f)(1), (2), and (4) of this section shall be submitted to the EPA at the frequency specified in those paragraphs in electronic portable document format (PDF) using the ECMPS Client Tool. Each PDF version of a submitted report must include sufficient information to assess compliance and to demonstrate that the testing was done properly. The following data elements must be entered into the ECMPS Client Tool at the time of submission of each PDF file:

(i) The facility name, physical address, mailing address (if different from the physical address), and county;

(ii) The ORIS code (or equivalent ID number assigned by EPA's Clean Air Markets Division (CAMD)) and the Facility Registry System (FRS) ID;

(iii) The EGU (or EGUs) to which the report applies. Report the EGU IDs as they appear in the CAMD Business System;

(iv) If any of the EGUs in paragraph (f)(6)(iii) of this section share a common stack, indicate which EGUs share the stack. If emissions data are monitored and reported at the common stack according to part 75 of this chapter, report the ID number of the common stack as it is represented in the electronic monitoring plan required under §75.53 of this chapter;

(v) If any of the EGUs described in paragraph (f)(6)(iii) of this section are in an averaging plan under §63.10009, indicate which EGUs are in the plan and whether it is a 30- or 90-day averaging plan;

(vi) The identification of each emission point to which the report applies. An “emission point” is a point at which source effluent is released to the atmosphere, and is either a dedicated stack that serves one of the EGUs identified in paragraph (f)(6)(iii) of this section or a common stack that serves two or more of those EGUs. To identify an emission point, associate it with the EGU or stack ID in the CAMD Business system or the electronic monitoring plan (e.g., “Unit 2 stack,” “common stack CS001,” or “multiple stack MS001”);

(vii) The rule citation (e.g., §63.10031(f)(1), §63.10031(f)(2), etc.) for which the report is showing compliance;

(viii) The pollutant(s) being addressed in the report;

(ix) The reporting period being covered by the report (if applicable);

(x) The relevant test method that was performed for a performance test (if applicable);

(xi) The date the performance test was conducted (if applicable); and

(xii) The responsible official's name, title, and phone number.

(g) If you had a malfunction during the reporting period, the compliance report must include the number, duration, and a brief description for each type of malfunction which occurred during the reporting period and which caused or may have caused any applicable emission limitation to be exceeded.

[77 FR 9464, Feb. 16, 2012, as amended at 77 FR 23404, Apr. 19, 2012; 79 FR 68791, Nov. 19, 2014; 79 FR 68799, Nov. 19, 2014; 80 FR 15514, Mar. 24, 2015; 81 FR 20188, Apr. 6, 2016; 82 FR 16739, Apr. 6, 2017; 83 FR 30883, July 2, 2018]