View all text of Subjgrp 122 [§ 63.7130 - § 63.7133]
§ 63.7131 - What reports must I submit and when?
(a) You must submit each report listed in Table 8 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 specified 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.7083 and ending on June 30 or December 31, whichever date is the first date following the end of the first half calendar year after the compliance date that is specified for your source in § 63.7083.
(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 half calendar year after the compliance date that is specified for your affected source in § 63.7083.
(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 part 70 or part 71 of this chapter, if the permitting authority has established dates for submitting semiannual reports pursuant to §§ 70.6(a)(3)(iii)(A) or 71.6(a)(3)(iii)(A) of this chapter, you may submit the first and subsequent compliance reports according to the dates the permitting authority has established instead of according to the dates specified in paragraphs (b)(1) through (4) of this section.
(6) Beginning on the relevant compliance date for your source as specified in § 63.7083(e), submit all subsequent compliance reports following the procedure specified in paragraph (h) of this section.
(c) The compliance report must contain the information specified 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 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) Prior to the relevant compliance date for your source as specified in § 63.7083(e), 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).
(5) If there were no deviations from any emission limitations (emission limit, operating limit, opacity limit, and VE limit) that apply to you, the compliance report 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 continuous monitoring systems (CMS) were out-of-control as specified in § 63.8(c)(7), a statement that there were no periods during which the CMS were out-of-control during the reporting period.
(d) For each deviation from an emission limitation (emission limit, operating limit, opacity limit, and VE limit) that occurs at an affected source where you are not using a CMS to comply with the emission limitations in this subpart, the compliance report must contain the information specified in paragraphs (c)(1) through (4) and (d)(1) and (2) of this section. The deviations must be reported in accordance with the requirements in § 63.10(d) prior to the relevant compliance date for your source as specified in § 63.7083(e) and the requirements in § 63.10(d)(1)-(4) beginning on the relevant compliance date for your source as specified in § 63.7083(e).
(1) The total operating time of each emission unit during the reporting period.
(2) Information on the number, duration, and cause of deviations (including unknown cause, if applicable), and the corrective action taken.
(3) An estimate of the quantity of each regulated pollutant emitted over a non-opacity or VE emission limit, and a description of the method used to estimate the emissions.
(e) For each deviation from an emission limitation (emission limit, operating limit, opacity limit, and VE limit) occurring at an affected source where you are using a CMS to comply with the emission limitation in this subpart, you must include the information specified in paragraphs (c)(1) through (4) and (e)(1) through (11) of this section, except that beginning on the relevant compliance date for your source as specified in 63.7083(e), the semiannual compliance report must also include the information included in paragraph (e)(12) of this section. This includes periods of startup, shutdown, and malfunction.
(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, including the information in § 63.8(c)(8).
(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 deviations during the reporting period and the total duration as a percent of the total affected 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 emission unit operating time during that reporting period.
(8) A brief description of the process units.
(9) A brief description of the CMS.
(10) The date of the latest CMS certification or audit.
(11) A description of any changes in CMS, processes, or controls since the last reporting period.
(12) An estimate of the quantity of each regulated pollutant emitted over a non-opacity or VE emission limit, and a description of the method used to estimate the emissions.
(f) Each facility 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 § 70.6(a)(3)(iii)(A) or 71.6(a)(3)(iii)(A) of this chapter. If you submit a compliance report specified in Table 8 to this subpart along with, or as part of, the semiannual monitoring report required by § 70.6(a)(3)(iii)(A) or 71.6(a)(3)(iii)(A) of this chapter, 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 you may have to report deviations from permit requirements to the permit authority.
(g) If you are required to submit reports following the procedure specified in this paragraph (g), you must submit 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/). 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. The EPA will make all the information submitted through CEDRI available to the public without further notice to you. Do not use CEDRI to submit information you claim as Confidential Business Information (CBI). Although we do not expect persons to assert a claim of CBI, if you wish to assert a CBI claim for some of the information in the report, you must submit a complete file, including information claimed to be CBI, to the EPA following the procedures in this paragraph (g). Clearly mark the part or all of the information that you claim to be CBI. Information not marked as CBI may be authorized for public release without prior notice. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2. All CBI claims must be asserted at the time of submission. Anything submitted using CEDRI cannot later be claimed CBI. Furthermore, under CAA section 114(c), emissions data is not entitled to confidential treatment, and the EPA is required to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available. You must submit the same file submitted to the CBI office with the CBI omitted to the EPA via the EPA's CDX as described earlier in this paragraph (g).
(1) The preferred method to receive CBI is for it to be transmitted electronically using email attachments, File Transfer Protocol, or other online file sharing services. Electronic submissions must be transmitted directly to the Office of Air Quality Planning and Standards (OAQPS) CBI Office at the email address [email protected], and as described above, should include clear CBI markings and be flagged to the attention of the Lime Manufacturing Sector Lead. If assistance is needed with submitting large electronic files that exceed the file size limit for email attachments, and if you do not have your own file sharing service, please email [email protected] to request a file transfer link.
(2) If you cannot transmit the file electronically, you may send CBI information through the postal service to the following address: OAQPS Document Control Officer (C404-02), OAQPS, U.S. Environmental Protection Agency, P.O. Box 12055, Research Triangle Park, North Carolina 27711, Attention Lime Manufacturing Sector Lead. The mailed CBI material should be double wrapped and clearly marked. Any CBI markings should not show through the outer envelope.
(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). (i) The EPA will make all the information submitted through CEDRI available to the public without further notice to you. Do not use CEDRI to submit information you claim as CBI. Although we do not expect persons to assert a claim of CBI, if you wish to assert a CBI claim for some of the information submitted under paragraph (a)(1) or (2) of this section, you must submit a complete file, including information claimed to be CBI, to the EPA.
(ii) The file must be generated using the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website.
(iii) Clearly mark the part or all of the information that you claim to be CBI. Information not marked as CBI may be authorized for public release without prior notice. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
(iv) The preferred method to receive CBI is for it to be transmitted electronically using email attachments, File Transfer Protocol, or other online file sharing services. Electronic submissions must be transmitted directly to the OAQPS CBI Office at the email address [email protected], and as described above, should include clear CBI markings and be flagged to the attention of the Group Leader, Measurement Policy Group. If assistance is needed with submitting large electronic files that exceed the file size limit for email attachments, and if you do not have your own file sharing service, please email [email protected] to request a file transfer link.
(v) If you cannot transmit the file electronically, you may send CBI information through the postal service to the following address: OAQPS Document Control Officer (C404-02), OAQPS, U.S. Environmental Protection Agency, P.O. Box 12055, Research Triangle Park, North Carolina 27711, Attention Group Leader, Measurement Policy Group. The mailed CBI material should be double wrapped and clearly marked. Any CBI markings should not show through the outer envelope.
(vi) All CBI claims must be asserted at the time of submission. Anything submitted using CEDRI cannot later be claimed CBI. Furthermore, under CAA section 114(c), emissions data is not entitled to confidential treatment, and the EPA is required to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available.
(vii) You must submit the same file submitted to the CBI office with the CBI omitted to the EPA via the EPA's CDX as described in paragraphs (h)(1) and (2) of this section.
(i) 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 (i)(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 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.
(j) 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 (j)(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.