§ 63.8818 - What reports must I submit and when?

§ 63.8818 What reports must I submit and when?

(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 compliance report for new or reconstructed flame lamination affected sources semiannually according to paragraphs (b)(1) through (4) 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.8786 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.8786.

(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.8786.

(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.

(c) For each loop slitter adhesive use affected source, you may submit annual compliance reports in place of semiannual reports.

(d) 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.

(e) The compliance report must contain the information in paragraphs (e)(1) through (5) 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) If there are no deviations from any emission limitations (emission limit or operating limit) that applies to you, a statement that there were no deviations from the emission limitations during the reporting period.

(5) For each deviation from an emission limitation that occurs, the compliance report must contain the information specified in paragraphs (e)(5)(i) through (iii) of this section.

(i) The total operating time of each affected source during the reporting period.

(ii) Information on the number, duration, and cause of deviations (including unknown cause, if applicable), as applicable, and the corrective action taken.

(iii) Information on the number, duration, and cause for continuous parameter monitoring system (CPMS) downtime incidents, if applicable, other than downtime associated with zero and span and other daily calibration checks.

(f) The compliance report for a new or reconstructed flame lamination affected source sources required by § 63.8810(c) to conduct continuous monitoring must also contain the following information in paragraphs (f)(1) through and (32) of this section.

(1) If you had a startup, shutdown or malfunction at your new or reconstructed flame lamination affected source during the reporting period and you took actions consistent with your startup, shutdown, and malfunction plan, the compliance report must include the information in § 63.10(d)(5)(i).

(2) If

there were no periods during which the CPMS was out-of-control in accordance with the monitoring plan, a statement that there were no periods during which the CPMS was out-of-control during the reporting period.

(

3

2) If there were periods during which the CPMS was out-of-control in accordance with the monitoring plan, the date, time, and duration of each out-of-control period.

(g) The compliance report for a loop slitter adhesive use affected source must also contain the following information in paragraphs (g)(1) and (2) of this section.

(1) For each annual reporting period during which you use an adhesive that was not included in the list submitted with the Notification of Compliance Status in § 63.8816(h) (1), an updated list of all adhesives used at the affected source.

(2) A statement certifying that each adhesive that was used at the affected source during the reporting period met the emission limit in Table 1 to this subpart.

(h) 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) in this subpart, 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.

(i) For each startup, shutdown, or malfunction during the reporting period where the source does not meet the emission limitations set out in § 63.8790 that occurs at a new or reconstructed flame lamination affected source and that is not consistent with your startup, shutdown, and malfunction plan, you must submit an immediate startup, shutdown and malfunction report.

(1) An initial report containing a description of the actions taken for the event must be submitted by fax or telephone within 2 working days after starting actions inconsistent with the plan.

(2) A followup report containing the information listed in § 63.10(d)(5)(ii) must be submitted within 7 working days after the end of the event unless you have made alternative reporting arrangements with the permitting authority.

[Reserved]

(j) For Performance Test and CMS Performance Evaluation Reports, beginning on May 17, 2022, within 60 days after the date of completing each performance test or CMS performance evaluation (as defined in § 63.2) required by this subpart, the owner or operator must submit the results of the performance test or CMS performance evaluation following the procedures specified in paragraphs (j)(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 or the performance evaluation of CMS measuring relative accuracy test audit (RATA) pollutants 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/). The data must be submitted in a file format generated using 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 or the performance evaluation of CMS measuring RATA pollutants by methods that are not supported by the ERT, 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). Do not use CEDRI to submit information you claim as CBI. Anything submitted using CEDRI cannot later be claimed 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. 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. 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 paragraphs (a)(1) and (2) of this section. All CBI claims must be asserted at the time of submission. 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.

(k) When submitting reports electronically, on and after the date specified in § 63.8786(f)(2), you must submit reports to the EPA via CEDRI, which can be accessed through the EPA's CDX (https://cdx.epa.gov/). 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). Anything submitted using CEDRI cannot later be claimed CBI. You must use the appropriate electronic report template on the CEDRI website (https://www.epa.gov/electronic-reporting-air-emissions/cedri) for this subpart. The date report templates become available will be listed on the CEDRI website. Unless the Administrator or delegated state agency or other authority has approved a different schedule for submission of reports, the report must be submitted by the deadline specified in this subpart, regardless of the method in which the report is submitted. Although we do not expect persons to assert a claim of CBI, if you wish to assert a CBI claim, 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 (k). All CBI claims must be asserted at the time of submission. 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.

(l) For claims of EPA system outage, when you are required to electronically submit a report 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 (l)(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.

(m) For claims of force majeure, when 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 (m)(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 18070, Apr. 14, 2003, as amended at 86 FR 64400, Nov. 18, 2021]