(a) Compliance report due dates. Unless the Administrator has approved a different schedule, you must submit a semiannual compliance report to your permitting authority according to the requirements specified in paragraphs (a)(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 iron and steel foundry by § 63.7683 and ending on June 30 or December 31, whichever date comes first after the compliance date that is specified for your iron and steel foundry.

(2) The first compliance report must be postmarked or delivered no later than July 31 or January 31, whichever date comes first after your first compliance report is due.

(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 comes first after the end of the semiannual reporting period.

(5) For each iron and steel foundry 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 specified in paragraphs (a)(1) through (4) of this section.

(b) Compliance report contents. Each compliance report must include the information specified in paragraphs (b)(1) through (3) of this section and, as applicable, paragraphs (b)(4) through (8) 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) [Reserved]

(5) If there were no deviations from any emissions limitations (including operating limit), work practice standards, or operation and maintenance requirements, a statement that there were no deviations from the emissions limitations, work practice standards, or operation and maintenance requirements during the reporting period.

(6) If there were no periods during which a continuous monitoring system (including a CPMS or CEMS) was inoperable or out-of-control as specified by § 63.8(c)(7), a statement that there were no periods during which the CPMS was inoperable or out-of-control during the reporting period.

(7) For each affected source or equipment for which there was a deviation from an emissions limitation (including an operating limit, work practice standard, or operation and maintenance requirement) that occurs at an iron and steel foundry during the reporting period, the compliance report must contain the information specified in paragraphs (b)(7)(i) through (iii) of this section. The requirement in this paragraph (b)(7) includes periods of startup, shutdown, and malfunction.

(i) A list of the affected source or equipment and the total operating time of each emissions source during the reporting period.

(ii) For each deviation from an emissions limitation (including an operating limit, work practice standard, or operation and maintenance requirement) that occurs at an iron and steel foundry during the reporting period, report:

(A) The date, start time, duration (in hours), and cause of each deviation (characterized as either startup, shutdown, control equipment problem, process problem, other known cause, or unknown cause, as applicable) and the corrective action taken; and

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

(iii) A summary of the total duration (in hours) of the deviations that occurred during the reporting period by cause (characterized as startup, shutdown, control equipment problems, process problems, other known causes, and unknown causes) and the cumulative duration of deviations during the reporting period across all causes both in hours and as a percent of the total source operating time during the reporting period.

(8) For each continuous monitoring system (including a CPMS or CEMS) used to comply with the emissions limitation or work practice standard in this subpart that was inoperable or out-of-control during any portion of the reporting period, you must include the information specified in paragraphs (b)(8)(i) through (vi) of this section. The requirement in this paragraph (b)(8) includes periods of startup, shutdown, and malfunction.

(i) A brief description of the continuous monitoring system, including manufacturer and model number.

(ii) The date of the latest continuous monitoring system certification or audit.

(iii) A brief description and the total operating time of the affected source or equipment that is monitored by the continuous monitoring system during the reporting period.

(iv) A description of any changes in continuous monitoring systems, processes, or controls since the last reporting period.

(v) For each period for which the continuous monitoring system was inoperable or out-of-control during the reporting period, report:

(A) The date, start time, and duration (in hours) of the deviation;

(B) The type of deviation (inoperable or out-of-control); and

(C) The cause of deviation (characterized as monitoring system malfunctions, non-monitoring equipment malfunctions, quality assurance/quality control calibrations, other known causes, and unknown causes, as applicable) and the corrective action taken.

(vi) A summary of the total duration (in hours) of the deviations that occurred during the reporting period by cause (characterized as monitoring system malfunctions, non-monitoring equipment malfunctions, quality assurance/quality control calibrations, other known causes, and unknown causes) and the cumulative duration of deviations during the reporting period across all causes both in hours and as a percent of the total source operating time during the reporting period.

(c) [Reserved]

(d) Part 70 monitoring report. If you have obtained a title V operating permit for an iron and steel foundry pursuant 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 for an iron and steel foundry 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 the required information concerning deviations from any emissions limitation or operation and maintenance requirement in this subpart, submission of the compliance report satisfies any obligation to report the same deviations in the semiannual monitoring report. However, submission of a compliance report does not otherwise affect any obligation you may have to report deviations from permit requirements for an iron and steel foundry to your permitting authority.

(e) Compliance report submission requirements. Prior to March 9, 2021, you must submit semiannual compliance reports to the Administrator as specified in § 63.13. Beginning on March 9, 2021, you must submit all subsequent semiannual compliance 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/). 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 to be 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. 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 the 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. Although we do not expect persons to assert a claim of CBI, if persons wish to assert a CBI, 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 (e). 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 requires EPA to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available.

(f) Performance test results submission requirements. 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 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 the 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 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. 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. Anything submitted using CEDRI cannot later be claimed to be CBI. Although we do not expect persons to assert a claim of CBI, if you claim some of the information submitted under paragraph (f)(1) or (2) of this section 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 (f)(1) 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 requires EPA to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available.

(g) Performance evaluation results submission requirements. Within 60 days after the date of completing each continuous monitoring system (CMS) performance evaluation (as defined in § 63.2), 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 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. 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. Anything submitted using CEDRI cannot later be claimed to be CBI. Although we do not expect persons to assert a claim of CBI, if you claim some of the information submitted under paragraph (g)(1) or (2) of this section 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 (g)(1) 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 requires EPA to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available.

(h) Claims of EPA system outage. If 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 (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 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.

(i) Claims of force majeure. 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 (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.