40 CFR § 63.867 - Reporting requirements.
(a) Notifications.
(1) The owner or operator of any affected source or process unit must submit the applicable notifications from subpart A of this part, as specified in Table 1 of this subpart.
(2) [Reserved]
(3) In addition to the requirements in subpart A of this part, the owner or operator of the hog fuel dryer at Cosmo Specialty Fibers' Cosmopolis, Washington, facility (Emission Unit no. HD–14) must include analysis and supporting documentation demonstrating conformance with EPA guidance and specifications for bag leak detection systems in § 63.864(e)(12) in the Notification of Compliance Status.
(b) Additional reporting requirements for HAP metals standards.
(1) Any owner or operator of a group of process units in a chemical recovery system at a mill complying with the PM emissions limits in § 63.862(a)(1)(ii) must submit the PM emissions limits determined in § 63.865(a) for each affected kraft or soda recovery furnace, smelt dissolving tank, and lime kiln to the Administrator for approval. The emissions limits must be submitted as part of the notification of compliance status required under subpart A of this part.
(2) Any owner or operator of a group of process units in a chemical recovery system at a mill complying with the PM emissions limits in § 63.862(a)(1)(ii) must submit the calculations and supporting documentation used in § 63.865(a)(1) and (2) to the Administrator as part of the notification of compliance status required under subpart A of this part.
(3) After the Administrator has approved the emissions limits for any process unit, the owner or operator of a process unit must notify the Administrator before any of the actions in paragraphs (b)(3)(i) through (iv) of this section are taken:
(i) The air pollution control system for any process unit is modified or replaced;
(ii) Any kraft or soda recovery furnace, smelt dissolving tank, or lime kiln in a chemical recovery system at a kraft or soda pulp mill complying with the PM emissions limits in § 63.862(a)(1)(ii) is shut down for more than 60 consecutive days;
(iii) A continuous monitoring parameter or the value or range of values of a continuous monitoring parameter for any process unit is changed; or
(iv) The black liquor solids firing rate for any kraft or soda recovery furnace during any 24-hour averaging period is increased by more than 10 percent above the level measured during the most recent performance test.
(4) An owner or operator of a group of process units in a chemical recovery system at a mill complying with the PM emissions limits in § 63.862(a)(1)(ii) and seeking to perform the actions in paragraph (b)(3)(i) or (ii) of this section must recalculate the overall PM emissions limit for the group of process units and resubmit the documentation required in paragraph (b)(2) of this section to the Administrator. All modified PM emissions limits are subject to approval by the Administrator.
(c) Excess emissions report. The owner or operator must submit semiannual excess emissions reports containing the information specified in paragraphs (c)(1) through (5) of this section. The owner or operator must submit semiannual excess emission reports and summary reports following the procedure specified in paragraph (d)(2) of this section as specified in § 63.10(e)(3)(v).
(1) If the total duration of excess emissions or process control system parameter exceedances for the reporting period is less than 1 percent of the total reporting period operating time, and CMS downtime is less than 5 percent of the total reporting period operating time, only the summary report is required to be submitted. This report will be titled “Summary Report—Gaseous and Opacity Excess Emissions and Continuous Monitoring System Performance” and must contain the information specified in paragraphs (c)(1)(i) through (x) of this section.
(i) The company name and address and name of the affected facility.
(ii) Beginning and ending dates of the reporting period.
(iii) An identification of each process unit with the corresponding air pollution control device, being included in the semiannual report, including the pollutants monitored at each process unit, and the total operating time for each process unit.
(iv) An identification of the applicable emission limits, operating parameter limits, and averaging times.
(v) An identification of the monitoring equipment used for each process unit and the corresponding model number.
(vi) Date of the last CMS certification or audit.
(vii) An emission data summary, including the total duration of excess emissions (recorded in minutes for opacity and hours for gases), the duration of excess emissions expressed as a percent of operating time, the number of averaging periods recorded as excess emissions, and reason for the excess emissions (e.g., startup/shutdown, control equipment problems, other known reasons, or other unknown reasons).
(viii) A CMS performance summary, including the total duration of CMS downtime during the reporting period (recorded in minutes for opacity and hours for gases), the total duration of CMS downtime expressed as a percent of the total source operating time during that reporting period, and a breakdown of the total CMS downtime during the reporting period (e.g., monitoring equipment malfunction, non-monitoring equipment malfunction, quality assurance, quality control calibrations, other known causes, or other unknown causes).
(ix) A description of changes to CMS, processes, or controls since last reporting period.
(x) A certification by a certifying official of truth, accuracy and completeness. This will state that, based on information and belief formed after reasonable inquiry, the statements and information in the document are true, accurate, and complete.
(2) [Reserved]
(3) If measured parameters meet any of the conditions specified in § 63.864(k)(1) or (2), the owner or operator of the affected source must submit a semiannual report describing the excess emissions that occurred. If the total duration of monitoring exceedances for the reporting period is 1 percent or greater of the total reporting period operating time, or the total CMS downtime for the reporting period is 5 percent or greater of the total reporting period operating time, or any violations according to § 63.864(k)(2) occurred, information from both the summary report and the excess emissions and continuous monitoring system performance report must be submitted. This report will be titled “Excess Emissions and Continuous Monitoring System Performance Report” and must contain the information specified in paragraphs (c)(1)(i) through (x) of this section, in addition to the information required in § 63.10(c)(5) through (14), as specified in paragraphs (c)(3)(i) through (vi) of this section. Reporting monitoring exceedances does not constitute a violation of the applicable standard unless the violation criteria in § 63.864(k)(2) and (3) are reached.
(i) An identification of the date and time identifying each period during which the CMS was inoperative except for zero (low-level) and high-level checks.
(ii) An identification of the date and time identifying each period during which the CMS was out of control, as defined in § 63.8(c)(7).
(iii) The specific identification of each period of excess emissions and parameter monitoring exceedances as described in paragraphs (c)(3)(iii)(A) through (E) of this section.
(A) For opacity:
(1) The total number of 6-minute averages in the reporting period (excluding process unit downtime).
(2) [Reserved]
(3) The number of 6-minute averages in the reporting period that exceeded the relevant opacity limit.
(4) The percent of 6-minute averages in the reporting period that exceed the relevant opacity limit.
(5) An identification of each exceedance by start and end time, date, and cause of exceedance (including startup/shutdown, control equipment problems, process problems, other known causes, or other unknown causes).
(B) [Reserved]
(C) For wet scrubber operating parameters:
(1) The operating limits established during the performance test for scrubbing liquid flow rate and pressure drop across the scrubber (or alternatively, fan amperage or RPM if used for smelt dissolving tank scrubbers).
(2) The number of 3-hour wet scrubber parameter averages below the minimum operating limit established during the performance test, if applicable.
(3) An identification of each exceedance by start and end time, date, and cause of exceedance (including startup/shutdown, control equipment problems, process problems, other known causes, or other unknown causes).
(D) For RTO operating temperature:
(1) The operating limit established during the performance test.
(2) The number of 1-hour and 3-hour temperature averages below the minimum operating limit established during the performance test.
(3) An identification of each exceedance by start and end time, date, and cause of exceedance including startup/shutdown, control equipment problems, process problems, other known causes, or other unknown causes).
(E) For alternative parameters established according to § 63.864(e)(13) or (14) subject to the requirements of § 63.864(k)(1) and (2):
(1) The type of operating parameters monitored for compliance.
(2) The operating limits established during the performance test.
(3) The number of 3-hour parameter averages outside of the operating limits established during the performance test.
(4) An identification of each exceedance by start and end time, date, and cause of exceedance including startup/shutdown, control equipment problems, process problems, other known causes, or other unknown causes).
(iv) The nature and cause of the event (if known).
(v) The corrective action taken or preventative measures adopted.
(vi) The nature of repairs and adjustments to the CMS that was inoperative or out of control.
(4) If a source fails to meet an applicable standard, including any emission limit in § 63.862 or any opacity or CPMS operating limit in § 63.864, report such events in the semiannual excess emissions report. Report the number of failures to meet an applicable standard. For each instance, report the date, time and duration of each failure. For each failure, the report must include a list of the affected sources or equipment, and for any failure to meet an emission limit under § 63.862, provide an estimate of the quantity of each regulated pollutant emitted over the emission limit, and a description of the method used to estimate the emissions.
(5) The owner or operator of an affected source or process unit subject to the requirements of this subpart and subpart S of this part may combine excess emissions and/or summary reports for the mill.
(d) Electronic reporting.
(1) Within 60 days after the date of completing each performance test (as defined in § 63.2) required by this subpart, the owner or operator must submit the results of the performance test following the procedure specified in either paragraph (d)(1)(i) or (ii) of this section.
(i) For data collected using test methods supported by the EPA's Electronic Reporting Tool (ERT) as listed on the EPA's ERT Web site (https://www.epa.gov/electronic-reporting-air-emissions/electronic-reporting-tool-ert) at the time of the test, the owner or operator must submit the results of the performance test to the EPA via the Compliance and Emissions Data Reporting Interface (CEDRI). (CEDRI can be accessed through the EPA's Central Data Exchange (CDX) (https://cdx.epa.gov/).) Performance test data must be submitted in a file format generated through the use of the EPA's ERT or an alternate electronic file format consistent with the extensible markup language (XML) schema listed on the EPA's ERT Web site. If the owner or operator claims that some of the performance test information being submitted is confidential business information (CBI), the owner or operator must submit a complete file 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 Web site, including information claimed to be CBI, on a compact disc, flash drive, or other commonly used electronic storage media to the EPA. The electronic media must be clearly marked as CBI and mailed 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 ERT or alternate file with the CBI omitted must be submitted to the EPA via the EPA's CDX as described earlier in this paragraph (d)(1)(i).
(ii) For data collected using test methods that are not supported by the EPA's ERT as listed on the EPA's ERT Web site at the time of the test, the owner or operator must submit the results of the performance test to the Administrator at the appropriate address listed in § 63.13 unless the Administrator agrees to or specifies an alternative reporting method.
(2) The owner or operator must submit the notifications required in § 63.9(b) and § 63.9(h) (including any information specified in § 63.867(b)) and semiannual reports to the EPA via the CEDRI. (CEDRI can be accessed through the EPA's CDX (https://cdx.epa.gov).) You must upload an electronic copy of each notification in CEDRI beginning with any notification specified in this paragraph that is required after October 11, 2019. The owner or operator must use the appropriate electronic report in CEDRI for this subpart listed on the CEDRI Web site (https://www.epa.gov/electronic-reporting-air-emissions/compliance-and-emissions-data-reporting-interface-cedri) for semiannual reports. If the reporting form specific to this subpart is not available in CEDRI at the time that the report is due, you must submit the report to the Administrator at all the appropriate addresses listed in § 63.13. Once the form has been available in CEDRI for 1 year, you must begin submitting all subsequent reports via CEDRI. The reports must be submitted by the deadlines specified in this subpart, regardless of the method in which the reports are submitted.
(3) If you are required to electronically submit a report through CEDRI in the EPA's CDX, and due to a planned or actual outage of either the EPA's CEDRI or CDX systems within the period of time beginning 5 business days prior to the date that the submission is due, you will be or are precluded from accessing CEDRI or CDX and submitting a required report within the time prescribed, you may assert a claim of EPA system outage for failure to timely comply with the reporting requirement. 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 caused a delay in reporting. You must provide to the Administrator a written description identifying the date, time and length of the outage; a rationale for attributing the delay in reporting beyond the regulatory deadline to the EPA system outage; describe the measures taken or to be taken to minimize the delay in reporting; and identify a 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. In any circumstance, the report must be submitted electronically as soon as possible after the outage is resolved. 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.
(4) If you are required to electronically submit a report through CEDRI in the EPA's CDX and 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 5 business days prior to the date the submission is due, the owner or operator may assert a claim of force majeure for failure to timely comply with the reporting requirement. 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). If you intend to assert a claim of force majeure, 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 caused a delay in reporting. You must provide to the Administrator a written description of the force majeure event and a rationale for attributing the delay in reporting beyond the regulatory deadline to the force majeure event; describe the measures taken or to be taken to minimize the delay in reporting; and identify a 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. In any circumstance, the reporting must occur as soon as possible after the force majeure event occurs. 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.