(a) You must submit each report in Table 6 to this subpart that applies to you.
(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 6 to this subpart and according to the following dates:
(1) The first compliance report must cover the period beginning on the compliance date that is specified for your affected source in § 63.8683 and ending on June 30 or December 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.8683.
(2) The first compliance report must be postmarked or delivered no later than July 31 or January 31, whichever date follows the end of the first calendar half after the compliance date that is specified for your affected source in § 63.8683.
(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 delivered 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 40 CFR part 70 or 40 CFR part 71, 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 the dates in paragraphs (b)(1) through (4) of this section.
(6) On and after September 9, 2020, you must submit all compliance reports to EPA via the CEDRI, which can be accessed through EPA's CDX (https://cdx.epa.gov/). You must use the appropriate electronic report template on the CEDRI website (https://www.epa.gov/electronic-reporting-air-emissions/compliance-and-emissions-data-reporting-interface-cedri) for this subpart. The date report templates become available will be listed on the CEDRI website. The report must be submitted by the deadline specified in this subpart, regardless of the method in which the report is submitted. If you claim some of the information required to be submitted via CEDRI is CBI, submit a complete report, including information claimed to be CBI, to EPA. The report must be generated using the appropriate form on the CEDRI website or an alternate electronic file consistent with the extensible markup language (XML) schema listed on the CEDRI website. Submit the file on a compact disc, flash drive, or other commonly used electronic storage medium and clearly mark the medium as CBI. Mail the electronic medium to U.S. EPA/OAQPS/CORE CBI Office, Attention: Group Leader, Measurement Policy Group, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same file with the CBI omitted must be submitted to EPA via EPA's CDX as described earlier in this paragraph (b)(6). You may assert a claim of EPA system outage or force majeure for failure to timely comply with the reporting requirement in this paragraph (b)(6) provided you meet the requirements outlined in § 63.8693(h) or (i), as applicable.
(c) The compliance report must contain the following information:
(1) Company name and address.
(2) Statement by a responsible official with that official's name, title, and signature, certifying the truth, accuracy, and completeness of the content of the report.
(3) Date of report and beginning and ending dates of the reporting period.
(4) Before September 9, 2020, if you had a startup, shutdown, or malfunction during the reporting period and you took actions consistent with your SSMP, the compliance report must include the information in § 63.10(d)(5)(i). On and after September 9, 2020, this paragraph (c)(4) no longer applies.
(5) For each reporting period, you must include in the compliance report the total number of deviations that occurred during the reporting period. If there are no deviations from any emission limitations (emission limit, operating limit, opacity limit, and visible emission limit) in § 63.8684 that apply to you, then you must include a statement that there were no deviations from the emission limitations during the reporting period.
(6) If there were no periods during which the CPMS, CEMS, or COMS was out-of-control as specified in § 63.8(c)(7), a statement that there were no periods during which the CPMS, CEMS, or COMS was out-of-control during the reporting period.
(d) For each deviation from an emission limitation (emission limit, operating limit, opacity limit, and visible emission limit) in § 63.8684, you must include in the compliance report the information in paragraphs (c)(1) through (6) of this section, and the information in paragraphs (d)(1) through (13) of this section.
(1) The start date, start time, and duration of each malfunction.
(2) For each instance that the CPMS, CEMS, or COMS was inoperative, except for zero (low-level) and high-level checks, the start date, start time, and duration that the CPMS, CEMS, or COMS was inoperative; the cause (including unknown cause) for the CPMS, CEMS, or COMS being inoperative; and descriptions of corrective actions taken.
(3) For each instance that the CPMS, CEMS, or COMS was out-of-control as specified in § 63.8(c)(7), the start date, start time, and duration that the CPMS, CEMS, or COMS was out-of-control, including the information in § 63.8(c)(8).
(4) Before September 9, 2020, the start date, start time, and duration of the deviation, and whether each deviation occurred during a period of startup, shutdown, or malfunction or during another period. On and after September 9, 2020, the start date, start time, and duration of the deviation including a description of the deviation and the actions you took to minimize emissions in accordance with § 63.8685(b). You must also include:
(i) A list of the affected sources or equipment for which the deviation occurred;
(ii) The cause of the deviation (including unknown cause, if applicable); and
(iii) Any corrective actions taken to return the affected unit to its normal or usual manner of operation.
(5) A summary of the total duration of the deviation during the reporting period and the total duration as a percent of the total source operating time during that reporting period.
(6) Before September 9, 2020, a breakdown of the total duration of the deviations during the reporting period into those that are due to startup, shutdown, control equipment problems, process problems, other known causes, and other unknown causes. On and after September 9, 2020, a breakdown of the total duration of the deviations during the reporting period into those that are due to control equipment problems, process problems, other known causes, and other unknown causes.
(7) A summary of the total duration of CPMS, CEMS, or COMS downtime during the reporting period and the total duration of CPMS, CEMS, or COMS downtime as a percent of the total source operating time during that reporting period.
(8) An identification of each air pollutant that was monitored at the affected source.
(9) A brief description of the process units.
(10) A brief description of the CPMS, CEMS, or COMS.
(11) The date of the latest CPMS, CEMS, or COMS certification or audit.
(12) A description of any changes in CPMS, CEMS, or COMS, processes, or controls since the last reporting period.
(e) Each affected source that has obtained a title V operating permit pursuant to 40 CFR part 70 or 40 CFR part 71 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 6 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 limitation (including any operating limit), submission of the compliance report shall be deemed to satisfy any obligation to report the same deviations in the semiannual monitoring report. However, submission of a compliance report shall not otherwise affect any obligation the affected source may have to report deviations from permit requirements to the permit authority.
(f) On and after September 9, 2020, within 60 days after the date of completing each performance test required by this subpart, you must submit the results of the performance test following the procedures specified in paragraphs (f)(1) through (3) of this section.
(1) Data collected using test methods supported by EPA's Electronic Reporting Tool (ERT) as listed on EPA's ERT website (https://www.epa.gov/electronic-reporting-air-emissions/electronic-reporting-tool-ert) at the time of the test. Submit the results of the performance test to EPA via the CEDRI, which can be accessed through EPA's CDX (https://cdx.epa.gov/). The data must be submitted in a file format generated through the use of EPA's ERT. Alternatively, you may submit an electronic file consistent with the XML schema listed on EPA's ERT website.
(2) Data collected using test methods that are not supported by EPA's ERT as listed on EPA's ERT website at the time of the test. The results of the performance test must be included as an attachment in the ERT or an alternate electronic file consistent with the XML schema listed on EPA's ERT website. Submit the ERT generated package or alternative file to EPA via CEDRI.
(3) CBI. If you claim some of the information submitted under paragraph (f)(1) of this section is CBI, you must submit a complete file, including information claimed to be CBI, to EPA. The file must be generated through the use of EPA's ERT or an alternate electronic file consistent with the XML schema listed on EPA's ERT website. Submit the file on a compact disc, flash drive, or other commonly used electronic storage medium and clearly mark the medium as CBI. Mail the electronic medium to U.S. EPA/OAQPS/CORE CBI Office, Attention: Group Leader, Measurement Policy Group, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same file with the CBI omitted must be submitted to EPA via EPA's CDX as described in paragraph (f)(1) of this section.
(g) On and after September 9, 2020, within 60 days after the date of completing each continuous monitoring system (CMS) performance evaluation (as defined in § 63.2) as specified in your site-specific monitoring plan, you must submit the results of the performance evaluation following the procedures specified in paragraphs (g)(1) through (3) of this section.
(1) Performance evaluations of CMS measuring relative accuracy test audit (RATA) pollutants that are supported by EPA's ERT as listed on EPA's ERT website at the time of the evaluation. Submit the results of the performance evaluation to EPA via CEDRI, which can be accessed through EPA's CDX. The data must be submitted in a file format generated through the use of EPA's ERT. Alternatively, you may submit an electronic file consistent with the XML schema listed on EPA's ERT website.
(2) Performance evaluations of CMS measuring RATA pollutants that are not supported by EPA's ERT as listed on EPA's ERT website at the time of the evaluation. The results of the performance evaluation must be included as an attachment in the ERT or an alternate electronic file consistent with the XML schema listed on EPA's ERT website. Submit the ERT generated package or alternative file to EPA via CEDRI.
(3) CBI. If you claim some of the information submitted under paragraph (g)(1) of this section is CBI, you must submit a complete file, including information claimed to be CBI, to EPA. The file must be generated through the use of EPA's ERT or an alternate electronic file consistent with the XML schema listed on EPA's ERT website. Submit the file on a compact disc, flash drive, or other commonly used electronic storage medium and clearly mark the medium as CBI. Mail the electronic medium to U.S. EPA/OAQPS/CORE CBI Office, Attention: Group Leader, Measurement Policy Group, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same file with the CBI omitted must be submitted to EPA via EPA's CDX as described in paragraph (g)(1) of this section.
(h) If you are required to electronically submit a report through CEDRI in EPA's CDX, you may assert a claim of EPA system outage for failure to timely comply with the reporting requirement in this section. To assert a claim of EPA system outage, you must meet the requirements outlined in paragraphs (h)(1) through (7) of this section.
(1) You must have been or will be precluded from accessing CEDRI and submitting a required report within the time prescribed due to an outage of either EPA's CEDRI or CDX systems.
(2) The outage must have occurred within the period of time beginning five business days prior to the date that the submission is due.
(3) The outage may be planned or unplanned.
(4) You must submit notification to the Administrator in writing as soon as possible following the date you first knew, or through due diligence should have known, that the event may cause or has caused a delay in reporting.
(5) You must provide to the Administrator a written description identifying:
(i) The date(s) and time(s) when CDX or CEDRI was accessed and the system was unavailable;
(ii) A rationale for attributing the delay in reporting beyond the regulatory deadline to EPA system outage;
(iii) Measures taken or to be taken to minimize the delay in reporting; and
(iv) The date by which you propose to report, or if you have already met the reporting requirement at the time of the notification, the date you reported.
(6) The decision to accept the claim of EPA system outage and allow an extension to the reporting deadline is solely within the discretion of the Administrator.
(7) In any circumstance, the report must be submitted electronically as soon as possible after the outage is resolved.
(i) If you are required to electronically submit a report through CEDRI in EPA's CDX, you may assert a claim of force majeure for failure to timely comply with the reporting requirement in this section. To assert a claim of force majeure, you must meet the requirements outlined in paragraphs (i)(1) through (5) of this section.
(1) You may submit a claim if a force majeure event is about to occur, occurs, or has occurred or there are lingering effects from such an event within the period of time beginning five business days prior to the date the submission is due. For the purposes of this section, a force majeure event is defined as an event that will be or has been caused by circumstances beyond the control of the affected facility, its contractors, or any entity controlled by the affected facility that prevents you from complying with the requirement to submit a report electronically within the time period prescribed. Examples of such events are acts of nature (e.g., hurricanes, earthquakes, or floods), acts of war or terrorism, or equipment failure or safety hazard beyond the control of the affected facility (e.g., large scale power outage).
(2) You must submit notification to the Administrator in writing as soon as possible following the date you first knew, or through due diligence should have known, that the event may cause or has caused a delay in reporting.
(3) You must provide to the Administrator:
(i) A written description of the force majeure event;
(ii) A rationale for attributing the delay in reporting beyond the regulatory deadline to the force majeure event;
(iii) Measures taken or to be taken to minimize the delay in reporting; and
(iv) The date by which you propose to report, or if you have already met the reporting requirement at the time of the notification, the date you reported.
(4) The decision to accept the claim of force majeure and allow an extension to the reporting deadline is solely within the discretion of the Administrator.
(5) In any circumstance, the reporting must occur as soon as possible after the force majeure event occurs.
[68 FR 24577, May 7, 2003, as amended at 85 FR 14550, Mar. 12, 2020]