(a) As required by § 63.10(b)(1), you must maintain files of all information (including all reports and notifications) for at least 5 years following the date of each occurrence, measurement, maintenance, corrective action, report, or record. At a minimum, the most recent 2 years of data shall be retained on site. The remaining 3 years of data may be retained off site. Such files may be maintained on microfilm, on a computer, on computer floppy disks or flash drives, on magnetic tape disks, or on microfiche. Any records required to be maintained by this part that are submitted electronically via the EPA's CEDRI may be maintained in electronic format. This ability to maintain electronic copies does not affect the requirement for facilities to make records, data, and reports available upon request to a delegated air agency or the EPA as part of an on-site compliance evaluation.
(b) In addition to the records required by § 63.10(b)(2)(iii) and (vi) through (xiv) and (b)(3), you must keep records of the information specified in paragraphs (b)(1) through (15) of this section.
(1) You must keep records of your written materials specifications according to § 63.10885(a) and records that demonstrate compliance with the requirements for restricted metallic scrap in § 63.10885(a)(1) and/or for the use of general scrap in § 63.10885(a)(2) and for mercury in § 63.10885(b)(1) through (3), as applicable. You must keep records documenting compliance with § 63.10885(b)(4) for scrap that does not contain motor vehicle scrap.
(2) If you are subject to the requirements for a site-specific plan for mercury under § 63.10885(b)(1), you must maintain records of the number of mercury switches removed or the weight of mercury recovered from the switches and properly managed, the estimated number of vehicles processed, and an estimate of the percent of mercury switches recovered.
(3) If you are subject to the option for approved mercury programs under § 63.10885(b)(2), you must maintain records identifying each scrap provider and documenting the scrap provider's participation in an approved mercury switch removal program. If your scrap provider is a broker, you must maintain records identifying each of the broker's scrap suppliers and documenting the scrap supplier's participation in an approved mercury switch removal program.
(4) You must keep records to document use of any binder chemical formulation that does not contain methanol as a specific ingredient of the catalyst formulation for each furfuryl alcohol warm box mold or core making line as required by § 63.10886. These records must be the Material Safety Data Sheet (provided that it contains appropriate information), a certified product data sheet, or a manufacturer's hazardous air pollutant data sheet.
(5) You must keep records of the annual quantity and composition of each HAP-containing chemical binder or coating material used to make molds and cores. These records must be copies of purchasing records, Material Safety Data Sheets, or other documentation that provide information on the binder or coating materials used.
(6) You must keep records of monthly metal melt production for each calendar year.
(7) You must keep a copy of the operation and maintenance plan as required by § 63.10896(a) and records that demonstrate compliance with plan requirements.
(8) If you use emissions averaging, you must keep records of the monthly metal melting rate for each furnace at your iron and steel foundry, and records of the calculated pounds of PM or total metal HAP per ton of metal melted for the group of all metal melting furnaces required by § 63.10897(h).
(9) If applicable, you must keep records for bag leak detection systems as follows:
(i) Records of the bag leak detection system output;
(ii) Records of bag leak detection system adjustments, including the date and time of the adjustment, the initial bag leak detection system settings, and the final bag leak detection system settings; and
(iii) The date and time of all bag leak detection system alarms, and for each valid alarm, the time you initiated corrective action, the corrective action taken, and the date on which corrective action was completed.
(10) You must keep records of capture system inspections and repairs as required by § 63.10897(e).
(11) You must keep records demonstrating conformance with your specifications for the operation of CPMS as required by § 63.10897(f).
(12) You must keep records of corrective action(s) for exceedances and excursions as required by § 63.10897(g).
(13) You must record the results of each inspection and maintenance required by § 63.10897(a) for PM control devices in a logbook (written or electronic format). You must keep the logbook onsite and make the logbook available to the Administrator upon request. You must keep records of the information specified in paragraphs (b)(13)(i) through (iii) of this section.
(i) The date and time of each recorded action for a fabric filter, the results of each inspection, and the results of any maintenance performed on the bag filters.
(ii) The date and time of each recorded action for a wet or dry electrostatic precipitator (including ductwork), the results of each inspection, and the results of any maintenance performed for the electrostatic precipitator.
(iii) The date and time of each recorded action for a wet scrubber (including ductwork), the results of each inspection, and the results of any maintenance performed on the wet scrubber.
(14) You must keep records of the site-specific performance evaluation test plan required under § 63.8(d)(2) for the life of the affected source or until the affected source is no longer subject to the provisions of this part, to be made available for inspection, upon request, by the Administrator. If the performance evaluation plan is revised, you shall keep previous (i.e., superseded) versions of the performance evaluation plan on record to be made available for inspection, upon request, by the Administrator, for a period of 5 years after each revision to the plan. The program of corrective action should be included in the plan as required under § 63.8(d)(2)(vi).
(15) You must keep the following records for each failure to meet an emissions limitation (including operating limit), work practice standard, or operation and maintenance requirement in this subpart.
(i) Date, start time, and duration of each failure.
(ii) List of the affected sources or equipment for each failure, 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) Actions taken to minimize emissions in accordance with § 63.10896(c), and any corrective actions taken to return the affected unit to its normal or usual manner of operation.
(c) Prior to March 9, 2021, you must submit semiannual compliance reports to the Administrator according to the requirements in § 63.13. Beginning on March 9, 2021, you must submit all subsequent semiannual compliance reports to the EPA via the 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. Although we do not expect persons to assert a claim of CBI, if persons wish to assert a CBI 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. 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 (c). 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. The reports must include the information specified in paragraphs (c)(1) through (3) of this section and, as applicable, paragraphs (c)(4) through (9) 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 were no deviations from any emissions limitations (including operating limits, pollution prevention management practices, or operation and maintenance requirements), a statement that there were no deviations from the emissions limitations, pollution prevention management practices, or operation and maintenance requirements during the reporting period.
(5) If there were no periods during which a continuous monitoring system (including a CPMS or continuous emissions monitoring system (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.
(6) For each affected source or equipment for which there was a deviation from an emissions limitation (including an operating limit, pollution prevention management practice, 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 (c)(6)(i) through (iii) of this section. The requirement in this paragraph (c)(6) 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, pollution prevention management practice, 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.
(7) 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 (c)(7)(i) through (vi) of this section. The requirement in this paragraph (c)(7) 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.
(8) Identification of which option in § 63.10885(b) applies to you. If you comply with the mercury requirements in § 63.10885(b) by using one scrap provider, contract, or shipment subject to one compliance provision and others subject to another compliance provision different, provide an identification of which option in § 63.10885(b) applies to each scrap provider, contract, or shipment.
(9) If you are subject to the requirements for a site-specific plan for mercury under § 63.10885(b)(1), include:
(i) The number of mercury switches removed or the weight of mercury recovered from the switches and properly managed, the estimated number of vehicles processed, an estimate of the percent of mercury switches recovered;
(ii) A certification that the recovered mercury switches were recycled at RCRA-permitted facilities; and
(iii) A certification that you have conducted periodic inspections or taken other means of corroboration as required under § 63.10885(b)(1)(ii)(C).
(d) You must submit written notification to the Administrator of the initial classification of your new or existing affected source as a large iron and steel facility as required in § 63.10880(f) and (g), as applicable, and for any subsequent reclassification as required in § 63.10881(d) or (e), as applicable.
(e) 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 (e)(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 (e)(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 (e)(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.
(f) 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 (f)(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) 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.
(g) 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 (g)(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.
[73 FR 252, Jan. 2, 2008, as amended at 85 FR 56102, Sept. 10, 2020]