40 CFR § 63.5580 - What reports must I submit and when?
(a) You must submit each report in Table 8 to this subpart that applies to you.
(b) Unless the Administrator has approved a different schedule for submitting reports under § 63.10, you must submit each compliance report by the date in Table 8 to this subpart and according to the requirements in paragraphs (b)(1) through (6) 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.5495 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.5495.
(2) The first compliance report must be submitted no later than August 31 or February 28, whichever date follows the end of the first calendar half after the compliance date that is specified for your affected source in § 63.5495.
(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 submitted no later than August 31 or February 28, 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 according to the dates in paragraphs (b)(1) through (4) of this section.
(6) Prior to December 29, 2020, all compliance reports submitted by mail must be postmarked or delivered no later than the dates specified in paragraphs (b)(1) through (5). Beginning on December 29, 2020, you must submit all compliance reports following the procedure specified in paragraph (g) of this section by the dates specified in paragraphs (b)(1) through (5).
(c) The compliance report must contain the information in paragraphs (c)(1) through (6) of this section.
(1) Company name and address.
(2) Statement by a responsible official, with that official's name, title, and signature, certifying that, based on information and belief formed after reasonable inquiry, the statements and information in the report are true, accurate, and complete.
(3) Date of report and beginning and ending dates of the reporting period.
(4) Before December 30, 2020, for each existing source (and for each new or reconstructed source for which construction or reconstruction commenced on or before September 9, 2019), if you had a startup, shutdown, or malfunction during the reporting period and you took actions consistent with your SSM plan, the compliance report must include the information in § 63.10(d)(5)(i). After December 29, 2020, you are no longer required to report the information in § 63.10(d)(5)(i). No SSM plan is required for any new or reconstruction source for which construction or reconstruction commenced after September 9, 2019.
(5) If there are no deviations from any emission limits, operating limits, or work practice standards that apply to you (see Tables 5 and 6 to this subpart), the compliance report must contain a statement that there were no deviations from the emission limits, operating limits, or work practice standards during the reporting period.
(6) If there were no periods during which the CMS was out-of-control, the compliance report must contain a statement that there were no periods during which the CMS was out-of-control during the reporting period. You must include specifications for out-of-control operation in the quality control plan required under § 63.8(d)(2).
(d) For each deviation from an emission limit or work practice standard that occurs at an affected source where you are not using a CMS to demonstrate continuous compliance with the emission limits or work practice standards in this subpart (see Table 5 to this subpart), the compliance report must contain the information in paragraphs (c)(1) through (4) and (d)(1) and (2) of this section. This includes periods of startup, shutdown, and malfunction.
(1) The total operating time of each affected source during the reporting period.
(2) Information on the number, duration, and cause of deviations (including unknown cause, if applicable), as applicable, and the corrective action taken.
(e) For each deviation from an emission limit or operating limit occurring at an affected source where you are using a CMS to demonstrate continuous compliance with the emission limit or operating limit in this subpart (see Tables 5 and 6 to this subpart), you must include the information in paragraphs (c)(1) through (4) and (e)(1) through (14) of this section. This includes periods of SSM.
(1) The date and time that each malfunction started and stopped.
(2) The date, time, and duration that each CMS was inoperative, except for zero (low-level) and high-level checks.
(3) The date, time, and duration that each CMS was out-of-control.
(4) The date and time that each deviation started and stopped, and whether each deviation occurred during a period of startup, shutdown, or malfunction or during another period.
(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) 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.
(7) A summary of the total duration of CMS downtime during the reporting period and the total duration of CMS downtime as a percent of the total source operating time during that reporting period.
(8) An identification of each HAP that is known to be in the emission stream at the affected source.
(9) A brief description of the process units.
(10) A brief description of the CMS.
(11) The date of the latest CEMS certification or audit or CPMS inspection, calibration, or validation check.
(12) A description of any changes in CMS, processes, or controls since the last reporting period.
(13) The operating day average values of monitored parameters.
(14) An estimate of the quantity of each regulated pollutant emitted over any emission limit, and a description of the method used to estimate the emissions.
(f) If you have obtained a title V operating permit according to 40 CFR part 70 or 40 CFR part 71, you 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 you submit a compliance report according 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 standard in this subpart, then submitting the compliance report will satisfy any obligation to report the same deviations in the semiannual monitoring report. However, submitting a compliance report will not otherwise affect any obligation you may have to report deviations from permit requirements to the permit authority.
(g) If you are required to submit notifications or reports following the procedure specified in this paragraph, you must submit notifications or reports to the EPA via the Compliance and Emissions Data Reporting Interface (CEDRI), which can be accessed through the EPA's Central Data Exchange (CDX) (https://cdx.epa.gov/). Notifications must be submitted as PDFs to CEDRI. You must use the semi-annual compliance 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 semi-annual compliance 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 confidential business information (CBI), submit a complete report, including information claimed to be CBI, to the EPA. The report must be generated using the appropriate form 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 the EPA via the EPA's CDX as described earlier in this paragraph.
(h) 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 (h)(1) through (3) of this section.
(1) Data collected using test methods supported by the EPA's Electronic Reporting Tool (ERT) as listed on the 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 the EPA via CEDRI, which can be accessed through the EPA's CDX (https://cdx.epa.gov/). The data must be submitted in a file format generated through the use of the EPA's ERT. Alternatively, you may submit an electronic file consistent with the extensible markup language (XML) schema listed on the EPA's ERT website.
(2) Data collected using test methods that are not supported by the EPA's ERT as listed on the 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 the EPA's ERT website. Submit the ERT generated package or alternative file to the EPA via CEDRI.
(3) Confidential business information (CBI). If you claim some of the information submitted under this paragraph (h) is CBI, you must submit a complete file, including information claimed to be CBI, to the EPA. The file must be generated through the use of the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the 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 the EPA via the EPA's CDX as described in paragraph (h) of this section.
(i) Within 60 days after the date of completing each CMS performance evaluation (as defined in § 63.2), you must submit the results of the performance evaluation following the procedures specified in paragraphs (i)(1) through (3) of this section.
(1) Performance evaluations of CMS measuring relative accuracy test audit (RATA) pollutants that are supported by the EPA's ERT as listed on the EPA's ERT website at the time of the evaluation. Submit the results of the performance evaluation to the EPA via CEDRI, which can be accessed through the EPA's CDX. The data must be submitted in a file format generated through the use of the EPA's ERT. Alternatively, you may submit an electronic file consistent with the XML schema listed on the EPA's ERT website.
(2) Performance evaluations of CMS measuring RATA pollutants that are not supported by the EPA's ERT as listed on the 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 the EPA's ERT website. Submit the ERT generated package or alternative file to the EPA via CEDRI.
(3) Confidential business information (CBI). If you claim some of the information submitted under this paragraph (i) is CBI, you must submit a complete file, including information claimed to be CBI, to the EPA. The file must be generated through the use of the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the 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 the EPA via the EPA's CDX as described in this paragraph (i).
(j) If you are required to electronically submit a report or notification through CEDRI in the EPA's CDX, you may assert a claim of EPA system outage for failure to timely comply with the reporting requirement. To assert a claim of EPA system outage, you must meet the requirements outlined in paragraphs (j)(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 the EPA's CEDRI or CDX systems.
(2) The outage must have occurred within the period of time beginning 5 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) A description of 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 the 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.
(k) If you are required to electronically submit a report through CEDRI in the EPA's CDX, you may assert a claim of force majeure for failure to timely comply with the reporting requirement. To assert a claim of force majeure, you must meet the requirements outlined in paragraphs (k)(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) A description of 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.