(1) The first compliance report must cover the period beginning on the compliance date that is specified for your affected source in § 63.9786 and ending on June 30 or December 31 and lasting at least 6 months but less than 12 months. For example, if your compliance date is March 1, then the first semiannual reporting period would begin on March 1 and end on December 31.

(2) The first compliance report must be postmarked or delivered no later than July 31 or January 31 for compliance periods ending on June 30 and December 31, respectively.

(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 for compliance periods ending on June 30 and December 31, respectively.

(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. In such cases, you must notify the Administrator of this change.

(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 May 19, 2022, if you had a startup, shutdown, or malfunction during the reporting period, and you took actions consistent with your SSMP and OM&M plan, the compliance report must include the information specified in § 63.10(d)(5)(i). On or after May 19, 2022, if you had a deviation from any emission limitations (emission limit, operating limit, or work practice standard) during the reporting period that apply to you, and you took actions consistent with your OM&M plan, the compliance report must include the information specified in (d) and (e) of this section.

(5) If there are no deviations from any emission limitations (emission limit, operating limit, or work practice standard) 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 any affected CPMS was out of control as specified in § 63.8(c)(7), the compliance report must include a statement that there were no periods during which the CPMS was out of control during the reporting period.

(7) For each period when an affected continuous kiln used to manufacture refractory products that use organic HAP was operating while the THC control device was out of service, the compliance report must include a description of the control device maintenance performed, including the information specified in paragraphs (c)(7)(i) through (vi) of this section.

(1) The compliance report must include the total operating time of each affected source during the reporting period.

(2) The compliance report must include information on the number, duration in hours, and cause of deviations (including unknown cause, if applicable) and the corrective action taken.

(3) The compliance report must include the date and time of each deviation, a list of the affected sources or equipment, and an estimate of each regulated pollutant emitted over the emission limit and a description of the method used to estimate the emissions.

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

(2) Before May 19, 2022, the date and time that each startup, shutdown, or malfunction started and stopped. On or after May 19, 2022, the date and time that each startup, shutdown, or malfunction started and stopped is not required.

(3) The date, time, and duration in hours that each CPMS was inoperative.

(4) The date, time and duration in hours that each CPMS was out of control, including the information in § 63.8(c)(8), as required by your OM&M plan.

(5) Before May 19, 2022, the date and time that each deviation from an emission limitation (emission limit, operating limit, or work practice standard) started and stopped, and whether each deviation occurred during a period of startup, shutdown, or malfunction. On or after May 19, 2022, for each deviation from an emission limitation (emission limit, operating limit, or work practice standard), the date and time that each deviation started and stopped, the duration in hours, a list of the affected sources or equipment, an estimate of each regulated pollutant emitted over the emission limit, and a description of the method used to estimate the emissions.

(6) A description of corrective action taken in response to a deviation.

(7) The total number of deviations during the reporting period, a summary of the total duration in hours of the deviations during the reporting period, and the total duration as a percentage of the total source operating time during that reporting period.

(8) Before May 19, 2022, 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 or after May 19, 2022, 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.

(9) A summary of the total duration in hours of CPMS downtime during the reporting period and the total duration of CPMS downtime as a percentage of the total source operating time during that reporting period.

(10) A brief description of the process units.

(11) A brief description of the CPMS.

(12) The date of the latest CPMS initial validation or accuracy audit.

(13) A description of any changes in CPMS, processes, or controls since the last reporting period.

(1) Company name and address.

(2) Identification of the affected kiln.

(3) Reason for using the alternative fuel.

(4) Type of alternative fuel used to fire the affected kiln.

(5) Dates that the use of the alternative fuel started and ended.

(6) Amount of alternative fuel used.

(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 Compliance and Emissions Data Reporting Interface (CEDRI), which can be accessed through the EPA's 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 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 (h)(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/OAPQS/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 (h)(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.

(1) Performance evaluations of CEMS 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 using 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 CEMS 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) 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 (i)(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 (h)(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.

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

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

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

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