Regulatory Text

§ 63.6 Compliance with standards and maintenance requirements.

(e) Operation and maintenance requirements.

(3) Startup, shutdown, and malfunction plan.

(i) The owner or operator of an affected source must develop a written startup, shutdown, and malfunction plan that describes, in detail, procedures for operating and maintaining the source during periods of startup, shutdown, and malfunction; and a program of corrective action for malfunctioning process, air pollution control, and monitoring equipment used to comply with the relevant standard. The startup, shutdown, and malfunction plan does not need to address any scenario that would not cause the source to exceed an applicable emission limitation in the relevant standard. This plan must be developed by the owner or operator by the source's compliance date for that relevant standard. The purpose of the startup, shutdown, and malfunction plan is to—

(A) Ensure that, at all times, the owner or operator operates and maintains each affected source, including associated air pollution control and monitoring equipment, in a manner which satisfies the general duty to minimize emissions established by paragraph (e)(1)(i) of this section;

(B) Ensure that owners or operators are prepared to correct malfunctions as soon as practicable after their occurrence in order to minimize excess emissions of hazardous air pollutants; and

(C) Reduce the reporting burden associated with periods of startup, shutdown, and malfunction (including corrective action taken to restore malfunctioning process and air pollution control equipment to its normal or usual manner of operation).

(ii) [Reserved]

(iii) When actions taken by the owner or operator during a startup or shutdown (and the startup or shutdown causes the source to exceed any applicable emission limitation in the relevant emission standards), or malfunction (including actions taken to correct a malfunction) are consistent with the procedures specified in the affected source's startup, shutdown, and malfunction plan, the owner or operator must keep records for that event which demonstrate that the procedures specified in the plan were followed. These records may take the form of a “checklist,” or other effective form of recordkeeping that confirms conformance with the startup, shutdown, and malfunction plan and describes the actions taken for that event. In addition, the owner or operator must keep records of these events as specified in paragraph 63.10(b), including records of the occurrence and duration of each startup or shutdown (if the startup or shutdown causes the source to exceed any applicable emission limitation in the relevant emission standards), or malfunction of operation and each malfunction of the air pollution control and monitoring equipment. Furthermore, the owner or operator shall confirm that actions taken during the relevant reporting period during periods of startup, shutdown, and malfunction were consistent with the affected source's startup, shutdown and malfunction plan in the semiannual (or more frequent) startup, shutdown, and malfunction report required in § 63.10(d)(5).

(iv) If an action taken by the owner or operator during a startup, shutdown, or malfunction (including an action taken to correct a malfunction) is not consistent with the procedures specified in the affected source's startup, shutdown, and malfunction plan, and the source exceeds any applicable emission limitation in the relevant emission standard, then the owner or operator must record the actions taken for that event and must report such actions within 2 working days after commencing actions inconsistent with the plan, followed by a letter within 7 working days after the end of the event, in accordance with § 63.10(d)(5) (unless the owner or operator makes alternative reporting arrangements, in advance, with the Administrator).

(v) The owner or operator must maintain at the affected source a current startup, shutdown, and malfunction plan and must make the plan available upon request for inspection and copying by the Administrator. In addition, if the startup, shutdown, and malfunction plan is subsequently revised as provided in paragraph (e)(3)(viii) of this section, the owner or operator must maintain at the affected source each previous (i.e., superseded) version of the startup, shutdown, and malfunction plan, and must make each such previous version available for inspection and copying by the Administrator for a period of 5 years after revision of the plan. If at any time after adoption of a startup, shutdown, and malfunction plan the affected source ceases operation or is otherwise no longer subject to the provisions of this part, the owner or operator must retain a copy of the most recent plan for 5 years from the date the source ceases operation or is no longer subject to this part and must make the plan available upon request for inspection and copying by the Administrator. The Administrator may at any time request in writing that the owner or operator submit a copy of any startup, shutdown, and malfunction plan (or a portion thereof) which is maintained at the affected source or in the possession of the owner or operator. Upon receipt of such a request, the owner or operator must promptly submit a copy of the requested plan (or a portion thereof) to the Administrator. The owner or operator may elect to submit the required copy of any startup, shutdown, and malfunction plan to the Administrator in an electronic format. If the owner or operator claims that any portion of such a startup, shutdown, and malfunction plan is confidential business information entitled to protection from disclosure under section 114(c) of the Act or 40 CFR 2.301, the material which is claimed as confidential must be clearly designated in the submission.

(vi) To satisfy the requirements of this section to develop a startup, shutdown, and malfunction plan, the owner or operator may use the affected source's standard operating procedures (SOP) manual, or an Occupational Safety and Health Administration (OSHA) or other plan, provided the alternative plans meet all the requirements of this section and are made available for inspection or submitted when requested by the Administrator.

(vii) Based on the results of a determination made under paragraph (e)(1)(i) of this section, the Administrator may require that an owner or operator of an affected source make changes to the startup, shutdown, and malfunction plan for that source. The Administrator must require appropriate revisions to a startup, shutdown, and malfunction plan, if the Administrator finds that the plan:

(A) Does not address a startup, shutdown, or malfunction event that has occurred;

(B) Fails to provide for the operation of the source (including associated air pollution control and monitoring equipment) during a startup, shutdown, or malfunction event in a manner consistent with the general duty to minimize emissions established by paragraph (e)(1)(i) of this section;

(C) Does not provide adequate procedures for correcting malfunctioning process and/or air pollution control and monitoring equipment as quickly as practicable; or

(D) Includes an event that does not meet the definition of startup, shutdown, or malfunction listed in § 63.2.

(viii) The owner or operator may periodically revise the startup, shutdown, and malfunction plan for the affected source as necessary to satisfy the requirements of this part or to reflect changes in equipment or procedures at the affected source. Unless the permitting authority provides otherwise, the owner or operator may make such revisions to the startup, shutdown, and malfunction plan without prior approval by the Administrator or the permitting authority. However, each such revision to a startup, shutdown, and malfunction plan must be reported in the semiannual report required by § 63.10(d)(5). If the startup, shutdown, and malfunction plan fails to address or inadequately addresses an event that meets the characteristics of a malfunction but was not included in the startup, shutdown, and malfunction plan at the time the owner or operator developed the plan, the owner or operator must revise the startup, shutdown, and malfunction plan within 45 days after the event to include detailed procedures for operating and maintaining the source during similar malfunction events and a program of corrective action for similar malfunctions of process or air pollution control and monitoring equipment. In the event that the owner or operator makes any revision to the startup, shutdown, and malfunction plan which alters the scope of the activities at the source which are deemed to be a startup, shutdown, or malfunction, or otherwise modifies the applicability of any emission limit, work practice requirement, or other requirement in a standard established under this part, the revised plan shall not take effect until after the owner or operator has provided a written notice describing the revision to the permitting authority.

(ix) The title V permit for an affected source must require that the owner or operator develop a startup, shutdown, and malfunction plan which conforms to the provisions of this part, but may do so by citing to the relevant subpart or subparagraphs of paragraph (e) of this section. However, any revisions made to the startup, shutdown, and malfunction plan in accordance with the procedures established by this part shall not be deemed to constitute permit revisions under part 70 or part 71 of this chapter and the elements of the startup, shutdown, and malfunction plan shall not be considered an applicable requirement as defined in § 70.2 and § 71.2 of this chapter. Moreover, none of the procedures specified by the startup, shutdown, and malfunction plan for an affected source shall be deemed to fall within the permit shield provision in section 504(f) of the Act.

§ 63.8 Monitoring requirements.

(d) Quality control program.

(1) The results of the quality control program required in this paragraph will be considered by the Administrator when he/she determines the validity of monitoring data.

(2) The owner or operator of an affected source that is required to use a CMS and is subject to the monitoring requirements of this section and a relevant standard shall develop and implement a CMS quality control program. As part of the quality control program, the owner or operator shall develop and submit to the Administrator for approval upon request a site-specific performance evaluation test plan for the CMS performance evaluation required in paragraph (e)(3)(i) of this section, according to the procedures specified in paragraph (e). In addition, each quality control program shall include, at a minimum, a written protocol that describes procedures for each of the following operations:

(i) Initial and any subsequent calibration of the CMS;

(ii) Determination and adjustment of the calibration drift of the CMS;

(iii) Preventive maintenance of the CMS, including spare parts inventory;

(iv) Data recording, calculations, and reporting;

(v) Accuracy audit procedures, including sampling and analysis methods; and

(vi) Program of corrective action for a malfunctioning CMS.

(3) The owner or operator shall keep these written procedures on record 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, the owner or operator 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. Where relevant, e.g., program of corrective action for a malfunctioning CMS, these written procedures may be incorporated as part of the affected source's startup, shutdown, and malfunction plan to avoid duplication of planning and recordkeeping efforts.

(e) Performance evaluation of continuous monitoring systems —

(3)

(i) Submission of site-specific performance evaluation test plan. Before conducting a required CMS performance evaluation, the owner or operator of an affected source shall develop and submit a site-specific performance evaluation test plan to the Administrator for approval upon request. The performance evaluation test plan shall include the evaluation program objectives, an evaluation program summary, the performance evaluation schedule, data quality objectives, and both an internal and external QA program. Data quality objectives are the pre-evaluation expectations of precision, accuracy, and completeness of data.

(ii) The internal QA program shall include, at a minimum, the activities planned by routine operators and analysts to provide an assessment of CMS performance. The external QA program shall include, at a minimum, systems audits that include the opportunity for on-site evaluation by the Administrator of instrument calibration, data validation, sample logging, and documentation of quality control data and field maintenance activities.

(iii) The owner or operator of an affected source shall submit the site-specific performance evaluation test plan to the Administrator (if requested) at least 60 days before the performance test or performance evaluation is scheduled to begin, or on a mutually agreed upon date, and review and approval of the performance evaluation test plan by the Administrator will occur with the review and approval of the site-specific test plan (if review of the site-specific test plan is requested).

(iv) The Administrator may request additional relevant information after the submittal of a site-specific performance evaluation test plan.

(v) In the event that the Administrator fails to approve or disapprove the site-specific performance evaluation test plan within the time period specified in § 63.7(c)(3), the following conditions shall apply:

(A) If the owner or operator intends to demonstrate compliance using the monitoring method(s) specified in the relevant standard, the owner or operator shall conduct the performance evaluation within the time specified in this subpart using the specified method(s);

(B) If the owner or operator intends to demonstrate compliance by using an alternative to a monitoring method specified in the relevant standard, the owner or operator shall refrain from conducting the performance evaluation until the Administrator approves the use of the alternative method. If the Administrator does not approve the use of the alternative method within 30 days before the performance evaluation is scheduled to begin, the performance evaluation deadlines specified in paragraph (e)(4) of this section may be extended such that the owner or operator shall conduct the performance evaluation within 60 calendar days after the Administrator approves the use of the alternative method. Notwithstanding the requirements in the preceding two sentences, the owner or operator may proceed to conduct the performance evaluation as required in this section (without the Administrator's prior approval of the site-specific performance evaluation test plan) if he/she subsequently chooses to use the specified monitoring method(s) instead of an alternative.

(vi) Neither the submission of a site-specific performance evaluation test plan for approval, nor the Administrator's approval or disapproval of a plan, nor the Administrator's failure to approve or disapprove a plan in a timely manner shall—

(A) Relieve an owner or operator of legal responsibility for compliance with any applicable provisions of this part or with any other applicable Federal, State, or local requirement; or

(B) Prevent the Administrator from implementing or enforcing this part or taking any other action under the Act.

(5) Reporting performance evaluation results.

(i) The owner or operator shall furnish the Administrator a copy of a written report of the results of the performance evaluation containing the information specified in § 63.7(g)(2)(i) through (vi) simultaneously with the results of the performance test required under § 63.7 or within 60 days of completion of the performance evaluation, unless otherwise specified in a relevant standard.

(ii) The owner or operator of an affected source using a COMS to determine opacity compliance during any performance test required under § 63.7 and described in § 63.6(d)(6) shall furnish the Administrator two or, upon request, three copies of a written report of the results of the COMS performance evaluation under this paragraph. The copies shall be provided at least 15 calendar days before the performance test required under § 63.7 is conducted.

§ 63.9 Notification requirements.

(b) Initial notifications.

(2) The owner or operator of an affected source that has an initial startup before the effective date of a relevant standard under this part shall notify the Administrator in writing that the source is subject to the relevant standard. The notification, which shall be submitted not later than 120 calendar days after the effective date of the relevant standard (or within 120 calendar days after the source becomes subject to the relevant standard), shall provide the following information:

(i) The name and address of the owner or operator;

(ii) The address (i.e., physical location) of the affected source;

(iii) An identification of the relevant standard, or other requirement, that is the basis of the notification and the source's compliance date;

(iv) A brief description of the nature, size, design, and method of operation of the source and an identification of the types of emission points within the affected source subject to the relevant standard and types of hazardous air pollutants emitted; and

(v) A statement of whether the affected source is a major source or an area source.

(5) The owner or operator of a new or reconstructed affected source for which an application for approval of construction or reconstruction is not required under § 63.5(d) must provide the following information in writing to the Administrator:

(i) A notification of intention to construct a new affected source, reconstruct an affected source, or reconstruct a source such that the source becomes an affected source, and

(ii) A notification of the actual date of startup of the source, delivered or postmarked within 15 calendar days after that date.

(iii) Unless the owner or operator has requested and received prior permission from the Administrator to submit less than the information in § 63.5(d), the notification must include the information required on the application for approval of construction or reconstruction as specified in § 63.5(d)(1)(i).

(d) Notification that source is subject to special compliance requirements. An owner or operator of a new source that is subject to special compliance requirements as specified in § 63.6(b)(3) and § 63.6(b)(4) shall notify the Administrator of his/her compliance obligations not later than the notification dates established in paragraph (b) of this section for new sources that are not subject to the special provisions.

(e) Notification of performance test. The owner or operator of an affected source shall notify the Administrator in writing of his or her intention to conduct a performance test at least 60 calendar days before the performance test is scheduled to begin to allow the Administrator to review and approve the site-specific test plan required under § 63.7(c), if requested by the Administrator, and to have an observer present during the test.

(f) Notification of opacity and visible emission observations. The owner or operator of an affected source shall notify the Administrator in writing of the anticipated date for conducting the opacity or visible emission observations specified in § 63.6(h)(5), if such observations are required for the source by a relevant standard. The notification shall be submitted with the notification of the performance test date, as specified in paragraph (e) of this section, or if no performance test is required or visibility or other conditions prevent the opacity or visible emission observations from being conducted concurrently with the initial performance test required under § 63.7, the owner or operator shall deliver or postmark the notification not less than 30 days before the opacity or visible emission observations are scheduled to take place.

(g) Additional notification requirements for sources with continuous monitoring systems. The owner or operator of an affected source required to use a CMS by a relevant standard shall furnish the Administrator written notification as follows:

(1) A notification of the date the CMS performance evaluation under § 63.8(e) is scheduled to begin, submitted simultaneously with the notification of the performance test date required under § 63.7(b). If no performance test is required, or if the requirement to conduct a performance test has been waived for an affected source under § 63.7(h), the owner or operator shall notify the Administrator in writing of the date of the performance evaluation at least 60 calendar days before the evaluation is scheduled to begin;

(2) A notification that COMS data results will be used to determine compliance with the applicable opacity emission standard during a performance test required by § 63.7 in lieu of Method 9 or other opacity emissions test method data, as allowed by § 63.6(h)(7)(ii), if compliance with an opacity emission standard is required for the source by a relevant standard. The notification shall be submitted at least 60 calendar days before the performance test is scheduled to begin; and

(3) A notification that the criterion necessary to continue use of an alternative to relative accuracy testing, as provided by § 63.8(f)(6), has been exceeded. The notification shall be delivered or postmarked not later than 10 days after the occurrence of such exceedance, and it shall include a description of the nature and cause of the increased emissions.

(h) Notification of compliance status.

(1) The requirements of paragraphs (h)(2) through (h)(4) of this section apply when an affected source becomes subject to a relevant standard.

(2)

(i) Before a title V permit has been issued to the owner or operator of an affected source, and each time a notification of compliance status is required under this part, the owner or operator of such source shall submit to the Administrator a notification of compliance status, signed by the responsible official who shall certify its accuracy, attesting to whether the source has complied with the relevant standard. The notification shall list—

(A) The methods that were used to determine compliance;

(B) The results of any performance tests, opacity or visible emission observations, continuous monitoring system (CMS) performance evaluations, and/or other monitoring procedures or methods that were conducted;

(C) The methods that will be used for determining continuing compliance, including a description of monitoring and reporting requirements and test methods;

(D) The type and quantity of hazardous air pollutants emitted by the source (or surrogate pollutants if specified in the relevant standard), reported in units and averaging times and in accordance with the test methods specified in the relevant standard;

(E) If the relevant standard applies to both major and area sources, an analysis demonstrating whether the affected source is a major source (using the emissions data generated for this notification);

(F) A description of the air pollution control equipment (or method) for each emission point, including each control device (or method) for each hazardous air pollutant and the control efficiency (percent) for each control device (or method); and

(G) A statement by the owner or operator of the affected existing, new, or reconstructed source as to whether the source has complied with the relevant standard or other requirements.

(ii) The notification must be sent before the close of business on the 60th day following the completion of the relevant compliance demonstration activity specified in the relevant standard (unless a different reporting period is specified in the standard, in which case the letter must be sent before the close of business on the day the report of the relevant testing or monitoring results is required to be delivered or postmarked). For example, the notification shall be sent before close of business on the 60th (or other required) day following completion of the initial performance test and again before the close of business on the 60th (or other required) day following the completion of any subsequent required performance test. If no performance test is required but opacity or visible emission observations are required to demonstrate compliance with an opacity or visible emission standard under this part, the notification of compliance status shall be sent before close of business on the 30th day following the completion of opacity or visible emission observations. Notifications may be combined as long as the due date requirement for each notification is met.

(3) After a title V permit has been issued to the owner or operator of an affected source, the owner or operator of such source shall comply with all requirements for compliance status reports contained in the source's title V permit, including reports required under this part. After a title V permit has been issued to the owner or operator of an affected source, and each time a notification of compliance status is required under this part, the owner or operator of such source shall submit the notification of compliance status to the appropriate permitting authority following completion of the relevant compliance demonstration activity specified in the relevant standard.

(4) [Reserved]

(5) If an owner or operator of an affected source submits estimates or preliminary information in the application for approval of construction or reconstruction required in § 63.5(d) in place of the actual emissions data or control efficiencies required in paragraphs (d)(1)(ii)(H) and (d)(2) of § 63.5, the owner or operator shall submit the actual emissions data and other correct information as soon as available but no later than with the initial notification of compliance status required in this section.

(6) Advice on a notification of compliance status may be obtained from the Administrator.

(j) Change in information already provided. Any change in the information already provided under this section shall be provided to the Administrator within 15 calendar days after the change. The owner or operator of a major source that reclassifies to area source status is also subject to the notification requirements of this paragraph. The owner or operator may submit the application for reclassification with the regulatory authority (e.g., permit application) according to paragraph (k) of this section to fulfill the requirements of this paragraph, but the information required in paragraphs (j)(1) through (4) of this section must be included. A source which reclassified after January 25, 2018, and before January 19, 2021, and has not yet provided the notification of a change in information is required to provide such notification no later than February 2, 2021, according to the requirements of paragraph (k) of this section. Beginning January 19, 2021, the owner or operator of a major source that reclassifies to area source status must submit the notification according to the requirements of paragraph (k) of this section. A notification of reclassification must contain the following information:

(1) The name and address of the owner or operator;

(2) The address (i.e., physical location) of the affected source;

(3) An identification of the standard being reclassified from and to (if applicable); and

(4) Date of effectiveness of the reclassification.

§ 63.10 Recordkeeping and reporting requirements.

(a) Applicability and general information.

(1) The applicability of this section is set out in § 63.1(a)(4).

(2) For affected sources that have been granted an extension of compliance under subpart D of this part, the requirements of this section do not apply to those sources while they are operating under such compliance extensions.

(3) If any State requires a report that contains all the information required in a report listed in this section, an owner or operator may send the Administrator a copy of the report sent to the State to satisfy the requirements of this section for that report.

(4)

(i) Before a State has been delegated the authority to implement and enforce recordkeeping and reporting requirements established under this part, the owner or operator of an affected source in such State subject to such requirements shall submit reports to the appropriate Regional Office of the EPA (to the attention of the Director of the Division indicated in the list of the EPA Regional Offices in § 63.13).

(ii) After a State has been delegated the authority to implement and enforce recordkeeping and reporting requirements established under this part, the owner or operator of an affected source in such State subject to such requirements shall submit reports to the delegated State authority (which may be the same as the permitting authority). In addition, if the delegated (permitting) authority is the State, the owner or operator shall send a copy of each report submitted to the State to the appropriate Regional Office of the EPA, as specified in paragraph (a)(4)(i) of this section. The Regional Office may waive this requirement for any reports at its discretion.

(5) If an owner or operator of an affected source in a State with delegated authority is required to submit periodic reports under this part to the State, and if the State has an established timeline for the submission of periodic reports that is consistent with the reporting frequency(ies) specified for such source under this part, the owner or operator may change the dates by which periodic reports under this part shall be submitted (without changing the frequency of reporting) to be consistent with the State's schedule by mutual agreement between the owner or operator and the State. For each relevant standard established pursuant to section 112 of the Act, the allowance in the previous sentence applies in each State beginning 1 year after the affected source's compliance date for that standard. Procedures governing the implementation of this provision are specified in § 63.9(i).

(6) If an owner or operator supervises one or more stationary sources affected by more than one standard established pursuant to section 112 of the Act, he/she may arrange by mutual agreement between the owner or operator and the Administrator (or the State permitting authority) a common schedule on which periodic reports required for each source shall be submitted throughout the year. The allowance in the previous sentence applies in each State beginning 1 year after the latest compliance date for any relevant standard established pursuant to section 112 of the Act for any such affected source(s). Procedures governing the implementation of this provision are specified in § 63.9(i).

(7) If an owner or operator supervises one or more stationary sources affected by standards established pursuant to section 112 of the Act (as amended November 15, 1990) and standards set under part 60, part 61, or both such parts of this chapter, he/she may arrange by mutual agreement between the owner or operator and the Administrator (or the State permitting authority) a common schedule on which periodic reports required by each relevant (i.e., applicable) standard shall be submitted throughout the year. The allowance in the previous sentence applies in each State beginning 1 year after the stationary source is required to be in compliance with the relevant section 112 standard, or 1 year after the stationary source is required to be in compliance with the applicable part 60 or part 61 standard, whichever is latest. Procedures governing the implementation of this provision are specified in § 63.9(i).

(b) General recordkeeping requirements.

(1) The owner or operator of an affected source subject to the provisions of this part shall maintain files of all information (including all reports and notifications) required by this part recorded in a form suitable and readily available for expeditious inspection and review. The files shall be retained 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, on magnetic tape disks, or on microfiche.

(2) The owner or operator of an affected source subject to the provisions of this part shall maintain relevant records for such source of—

(i) The occurrence and duration of each startup or shutdown when the startup or shutdown causes the source to exceed any applicable emission limitation in the relevant emission standards;

(ii) The occurrence and duration of each malfunction of operation (i.e., process equipment) or the required air pollution control and monitoring equipment;

(iii) All required maintenance performed on the air pollution control and monitoring equipment;

(iv)

(A) Actions taken during periods of startup or shutdown when the source exceeded applicable emission limitations in a relevant standard and when the actions taken are different from the procedures specified in the affected source's startup, shutdown, and malfunction plan (see § 63.6(e)(3)); or

(B) Actions taken during periods of malfunction (including corrective actions to restore malfunctioning process and air pollution control and monitoring equipment to its normal or usual manner of operation) when the actions taken are different from the procedures specified in the affected source's startup, shutdown, and malfunction plan (see § 63.6(e)(3));

(v) All information necessary, including actions taken, to demonstrate conformance with the affected source's startup, shutdown, and malfunction plan (see § 63.6(e)(3)) when all actions taken during periods of startup or shutdown (and the startup or shutdown causes the source to exceed any applicable emission limitation in the relevant emission standards), and malfunction (including corrective actions to restore malfunctioning process and air pollution control and monitoring equipment to its normal or usual manner of operation) are consistent with the procedures specified in such plan. (The information needed to demonstrate conformance with the startup, shutdown, and malfunction plan may be recorded using a “checklist,” or some other effective form of recordkeeping, in order to minimize the recordkeeping burden for conforming events);

(vi) Each period during which a CMS is malfunctioning or inoperative (including out-of-control periods);

(vii) All required measurements needed to demonstrate compliance with a relevant standard (including, but not limited to, 15-minute averages of CMS data, raw performance testing measurements, and raw performance evaluation measurements, that support data that the source is required to report);

(A) This paragraph applies to owners or operators required to install a continuous emissions monitoring system (CEMS) where the CEMS installed is automated, and where the calculated data averages do not exclude periods of CEMS breakdown or malfunction. An automated CEMS records and reduces the measured data to the form of the pollutant emission standard through the use of a computerized data acquisition system. In lieu of maintaining a file of all CEMS subhourly measurements as required under paragraph (b)(2)(vii) of this section, the owner or operator shall retain the most recent consecutive three averaging periods of subhourly measurements and a file that contains a hard copy of the data acquisition system algorithm used to reduce the measured data into the reportable form of the standard.

(B) This paragraph applies to owners or operators required to install a CEMS where the measured data is manually reduced to obtain the reportable form of the standard, and where the calculated data averages do not exclude periods of CEMS breakdown or malfunction. In lieu of maintaining a file of all CEMS subhourly measurements as required under paragraph (b)(2)(vii) of this section, the owner or operator shall retain all subhourly measurements for the most recent reporting period. The subhourly measurements shall be retained for 120 days from the date of the most recent summary or excess emission report submitted to the Administrator.

(C) The Administrator or delegated authority, upon notification to the source, may require the owner or operator to maintain all measurements as required by paragraph (b)(2)(vii), if the administrator or the delegated authority determines these records are required to more accurately assess the compliance status of the affected source.

(viii) All results of performance tests, CMS performance evaluations, and opacity and visible emission observations;

(ix) All measurements as may be necessary to determine the conditions of performance tests and performance evaluations;

(x) All CMS calibration checks;

(xi) All adjustments and maintenance performed on CMS;

(xii) Any information demonstrating whether a source is meeting the requirements for a waiver of recordkeeping or reporting requirements under this part, if the source has been granted a waiver under paragraph (f) of this section;

(xiii) All emission levels relative to the criterion for obtaining permission to use an alternative to the relative accuracy test, if the source has been granted such permission under § 63.8(f)(6); and

(xiv) All documentation supporting initial notifications and notifications of compliance status under § 63.9.

(3) If an owner or operator determines that his or her existing or new stationary source is in the source category regulated by a standard established pursuant to section 112 of the Act, but that source is not subject to the relevant standard (or other requirement established under this part) because of enforceable limitations on the source's potential to emit, or the source otherwise qualifies for an exclusion, the owner or operator must keep a record of the applicability determination. The applicability determination must be kept on site at the source for a period of 5 years after the determination, or until the source changes its operations to become an affected source subject to the relevant standard (or other requirement established under this part), whichever comes first if the determination is made prior to January 19, 2021. The applicability determination must be kept until the source changes its operations to become an affected source subject to the relevant standard (or other requirement established under this part) if the determination was made on or after January 19, 2021. The record of the applicability determination must be signed by the person making the determination and include an emissions analysis (or other information) that demonstrates the owner or operator's conclusion that the source is unaffected (e.g., because the source is an area source). The analysis (or other information) must be sufficiently detailed to allow the Administrator to make an applicability finding for the source with regard to the relevant standard or other requirement. If applicable, the analysis must be performed in accordance with requirements established in relevant subparts of this part for this purpose for particular categories of stationary sources. If relevant, the analysis should be performed in accordance with EPA guidance materials published to assist sources in making applicability determinations under section 112 of the Act, if any. The requirements to determine applicability of a standard under § 63.1(b)(3) and to record the results of that determination under this paragraph (b)(3) of this section shall not by themselves create an obligation for the owner or operator to obtain a title V permit.

(c) Additional recordkeeping requirements for sources with continuous monitoring systems. In addition to complying with the requirements specified in paragraphs (b)(1) and (b)(2) of this section, the owner or operator of an affected source required to install a CMS by a relevant standard shall maintain records for such source of—

(1) All required CMS measurements (including monitoring data recorded during unavoidable CMS breakdowns and out-of-control periods);

(2)-(4) [Reserved]

(5) The date and time identifying each period during which the CMS was inoperative except for zero (low-level) and high-level checks;

(6) The date and time identifying each period during which the CMS was out of control, as defined in § 63.8(c)(7);

(7) The specific identification (i.e., the date and time of commencement and completion) of each period of excess emissions and parameter monitoring exceedances, as defined in the relevant standard(s), that occurs during startups, shutdowns, and malfunctions of the affected source;

(8) The specific identification (i.e., the date and time of commencement and completion) of each time period of excess emissions and parameter monitoring exceedances, as defined in the relevant standard(s), that occurs during periods other than startups, shutdowns, and malfunctions of the affected source;

(9) [Reserved]

(10) The nature and cause of any malfunction (if known);

(11) The corrective action taken or preventive measures adopted;

(12) The nature of the repairs or adjustments to the CMS that was inoperative or out of control;

(13) The total process operating time during the reporting period; and

(14) All procedures that are part of a quality control program developed and implemented for CMS under § 63.8(d).

(15) In order to satisfy the requirements of paragraphs (c)(10) through (c)(12) of this section and to avoid duplicative recordkeeping efforts, the owner or operator may use the affected source's startup, shutdown, and malfunction plan or records kept to satisfy the recordkeeping requirements of the startup, shutdown, and malfunction plan specified in § 63.6(e), provided that such plan and records adequately address the requirements of paragraphs (c)(10) through (c)(12).

(d) General reporting requirements.

(1) Notwithstanding the requirements in this paragraph or paragraph (e) of this section, and except as provided in § 63.16, the owner or operator of an affected source subject to reporting requirements under this part shall submit reports to the Administrator in accordance with the reporting requirements in the relevant standard(s).

(2) Reporting results of performance tests. Before a title V permit has been issued to the owner or operator of an affected source, the owner or operator shall report the results of any performance test under § 63.7 to the Administrator. After a title V permit has been issued to the owner or operator of an affected source, the owner or operator shall report the results of a required performance test to the appropriate permitting authority. The owner or operator of an affected source shall report the results of the performance test to the Administrator (or the State with an approved permit program) before the close of business on the 60th day following the completion of the performance test, unless specified otherwise in a relevant standard or as approved otherwise in writing by the Administrator. The results of the performance test shall be submitted as part of the notification of compliance status required under § 63.9(h).

(3) Reporting results of opacity or visible emission observations. The owner or operator of an affected source required to conduct opacity or visible emission observations by a relevant standard shall report the opacity or visible emission results (produced using Test Method 9 or Test Method 22, or an alternative to these test methods) along with the results of the performance test required under § 63.7. If no performance test is required, or if visibility or other conditions prevent the opacity or visible emission observations from being conducted concurrently with the performance test required under § 63.7, the owner or operator shall report the opacity or visible emission results before the close of business on the 30th day following the completion of the opacity or visible emission observations.

(4) Progress reports. The owner or operator of an affected source who is required to submit progress reports as a condition of receiving an extension of compliance under § 63.6(i) shall submit such reports to the Administrator (or the State with an approved permit program) by the dates specified in the written extension of compliance.

(5)

(i) Periodic startup, shutdown, and malfunction reports. If actions taken by an owner or operator during a startup or shutdown (and the startup or shutdown causes the source to exceed any applicable emission limitation in the relevant emission standards), or malfunction of an affected source (including actions taken to correct a malfunction) are consistent with the procedures specified in the source's startup, shutdown, and malfunction plan (see § 63.6(e)(3)), the owner or operator shall state such information in a startup, shutdown, and malfunction report. Actions taken to minimize emissions during such startups, shutdowns, and malfunctions shall be summarized in the report and may be done in checklist form; if actions taken are the same for each event, only one checklist is necessary. Such a report shall also include the number, duration, and a brief description for each type of malfunction which occurred during the reporting period and which caused or may have caused any applicable emission limitation to be exceeded. Reports shall only be required if a startup or shutdown caused the source to exceed any applicable emission limitation in the relevant emission standards, or if a malfunction occurred during the reporting period. The startup, shutdown, and malfunction report shall consist of a letter, containing the name, title, and signature of the owner or operator or other responsible official who is certifying its accuracy, that shall be submitted to the Administrator semiannually (or on a more frequent basis if specified otherwise in a relevant standard or as established otherwise by the permitting authority in the source's title V permit). The startup, shutdown, and malfunction report shall be delivered or postmarked by the 30th day following the end of each calendar half (or other calendar reporting period, as appropriate). If the owner or operator is required to submit excess emissions and continuous monitoring system performance (or other periodic) reports under this part, the startup, shutdown, and malfunction reports required under this paragraph may be submitted simultaneously with the excess emissions and continuous monitoring system performance (or other) reports. If startup, shutdown, and malfunction reports are submitted with excess emissions and continuous monitoring system performance (or other periodic) reports, and the owner or operator receives approval to reduce the frequency of reporting for the latter under paragraph (e) of this section, the frequency of reporting for the startup, shutdown, and malfunction reports also may be reduced if the Administrator does not object to the intended change. The procedures to implement the allowance in the preceding sentence shall be the same as the procedures specified in paragraph (e)(3) of this section.

(ii) Immediate startup, shutdown, and malfunction reports. Notwithstanding the allowance to reduce the frequency of reporting for periodic startup, shutdown, and malfunction reports under paragraph (d)(5)(i) of this section, any time an action taken by an owner or operator during a startup or shutdown that caused the source to exceed any applicable emission limitation in the relevant emission standards, or malfunction (including actions taken to correct a malfunction) is not consistent with the procedures specified in the affected source's startup, shutdown, and malfunction plan, the owner or operator shall report the actions taken for that event within 2 working days after commencing actions inconsistent with the plan followed by a letter within 7 working days after the end of the event. The immediate report required under this paragraph (d)(5)(ii) shall consist of a telephone call (or facsimile (FAX) transmission) to the Administrator within 2 working days after commencing actions inconsistent with the plan, and it shall be followed by a letter, delivered or postmarked within 7 working days after the end of the event, that contains the name, title, and signature of the owner or operator or other responsible official who is certifying its accuracy, explaining the circumstances of the event, the reasons for not following the startup, shutdown, and malfunction plan, describing all excess emissions and/or parameter monitoring exceedances which are believed to have occurred (or could have occurred in the case of malfunctions), and actions taken to minimize emissions in conformance with § 63.6(e)(1)(i). Notwithstanding the requirements of the previous sentence, after the effective date of an approved permit program in the State in which an affected source is located, the owner or operator may make alternative reporting arrangements, in advance, with the permitting authority in that State. Procedures governing the arrangement of alternative reporting requirements under this paragraph (d)(5)(ii) are specified in § 63.9(i).

(e) Additional reporting requirements for sources with continuous monitoring systems —

(1) General. When more than one CEMS is used to measure the emissions from one affected source (e.g., multiple breechings, multiple outlets), the owner or operator shall report the results as required for each CEMS.

(2) Reporting results of continuous monitoring system performance evaluations.

(i) The owner or operator of an affected source required to install a CMS by a relevant standard shall furnish the Administrator a copy of a written report of the results of the CMS performance evaluation, as required under § 63.8(e), simultaneously with the results of the performance test required under § 63.7, unless otherwise specified in the relevant standard.

(ii) The owner or operator of an affected source using a COMS to determine opacity compliance during any performance test required under § 63.7 and described in § 63.6(d)(6) shall furnish the Administrator two or, upon request, three copies of a written report of the results of the COMS performance evaluation conducted under § 63.8(e). The copies shall be furnished at least 15 calendar days before the performance test required under § 63.7 is conducted.

(3) Excess emissions and continuous monitoring system performance report and summary report.

(i) Excess emissions and parameter monitoring exceedances are defined in relevant standards. The owner or operator of an affected source required to install a CMS by a relevant standard shall submit an excess emissions and continuous monitoring system performance report and/or a summary report to the Administrator semiannually, except when—

(A) More frequent reporting is specifically required by a relevant standard;

(B) The Administrator determines on a case-by-case basis that more frequent reporting is necessary to accurately assess the compliance status of the source; or

(C) [Reserved]

(D) The affected source is complying with the Performance Track Provisions of § 63.16, which allows less frequent reporting.

(ii) Request to reduce frequency of excess emissions and continuous monitoring system performance reports. Notwithstanding the frequency of reporting requirements specified in paragraph (e)(3)(i) of this section, an owner or operator who is required by a relevant standard to submit excess emissions and continuous monitoring system performance (and summary) reports on a quarterly (or more frequent) basis may reduce the frequency of reporting for that standard to semiannual if the following conditions are met:

(A) For 1 full year (e.g., 4 quarterly or 12 monthly reporting periods) the affected source's excess emissions and continuous monitoring system performance reports continually demonstrate that the source is in compliance with the relevant standard;

(B) The owner or operator continues to comply with all recordkeeping and monitoring requirements specified in this subpart and the relevant standard; and

(C) The Administrator does not object to a reduced frequency of reporting for the affected source, as provided in paragraph (e)(3)(iii) of this section.

(iii) The frequency of reporting of excess emissions and continuous monitoring system performance (and summary) reports required to comply with a relevant standard may be reduced only after the owner or operator notifies the Administrator in writing of his or her intention to make such a change and the Administrator does not object to the intended change. In deciding whether to approve a reduced frequency of reporting, the Administrator may review information concerning the source's entire previous performance history during the 5-year recordkeeping period prior to the intended change, including performance test results, monitoring data, and evaluations of an owner or operator's conformance with operation and maintenance requirements. Such information may be used by the Administrator to make a judgment about the source's potential for noncompliance in the future. If the Administrator disapproves the owner or operator's request to reduce the frequency of reporting, the Administrator will notify the owner or operator in writing within 45 days after receiving notice of the owner or operator's intention. The notification from the Administrator to the owner or operator will specify the grounds on which the disapproval is based. In the absence of a notice of disapproval within 45 days, approval is automatically granted.

(iv) As soon as CMS data indicate that the source is not in compliance with any emission limitation or operating parameter specified in the relevant standard, the frequency of reporting shall revert to the frequency specified in the relevant standard, and the owner or operator shall submit an excess emissions and continuous monitoring system performance (and summary) report for the noncomplying emission points at the next appropriate reporting period following the noncomplying event. After demonstrating ongoing compliance with the relevant standard for another full year, the owner or operator may again request approval from the Administrator to reduce the frequency of reporting for that standard, as provided for in paragraphs (e)(3)(ii) and (e)(3)(iii) of this section.

(v) Content and submittal dates for excess emissions and monitoring system performance reports. All excess emissions and monitoring system performance reports and all summary reports, if required, shall be delivered or postmarked by the 30th day following the end of each calendar half or quarter, as appropriate. Written reports of excess emissions or exceedances of process or control system parameters shall include all the information required in paragraphs (c)(5) through (c)(13) of this section, in §§ 63.8(c)(7) and 63.8(c)(8), and in the relevant standard, and they shall contain the name, title, and signature of the responsible official who is certifying the accuracy of the report. When no excess emissions or exceedances of a parameter have occurred, or a CMS has not been inoperative, out of control, repaired, or adjusted, such information shall be stated in the report.

(vi) Summary report. As required under paragraphs (e)(3)(vii) and (e)(3)(viii) of this section, one summary report shall be submitted for the hazardous air pollutants monitored at each affected source (unless the relevant standard specifies that more than one summary report is required, e.g., one summary report for each hazardous air pollutant monitored). The summary report shall be entitled “Summary Report—Gaseous and Opacity Excess Emission and Continuous Monitoring System Performance” and shall contain the following information:

(A) The company name and address of the affected source;

(B) An identification of each hazardous air pollutant monitored at the affected source;

(C) The beginning and ending dates of the reporting period;

(D) A brief description of the process units;

(E) The emission and operating parameter limitations specified in the relevant standard(s);

(F) The monitoring equipment manufacturer(s) and model number(s);

(G) The date of the latest CMS certification or audit;

(H) The total operating time of the affected source during the reporting period;

(I) An emission data summary (or similar summary if the owner or operator monitors control system parameters), including the total duration of excess emissions during the reporting period (recorded in minutes for opacity and hours for gases), the total duration of excess emissions expressed as a percent of the total source operating time during that reporting period, and a breakdown of the total duration of excess emissions during the reporting period into those that are due to startup/shutdown, control equipment problems, process problems, other known causes, and other unknown causes;

(J) A CMS performance summary (or similar summary if the owner or operator monitors control system parameters), including the total 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 into periods that are due to monitoring equipment malfunctions, nonmonitoring equipment malfunctions, quality assurance/quality control calibrations, other known causes, and other unknown causes;

(K) A description of any changes in CMS, processes, or controls since the last reporting period;

(L) The name, title, and signature of the responsible official who is certifying the accuracy of the report; and

(M) The date of the report.

(vii) If the total duration of excess emissions or process or control system parameter exceedances for the reporting period is less than 1 percent of the total operating time for the reporting period, and CMS downtime for the reporting period is less than 5 percent of the total operating time for the reporting period, only the summary report shall be submitted, and the full excess emissions and continuous monitoring system performance report need not be submitted unless required by the Administrator.

(viii) If the total duration of excess emissions or process or control system parameter exceedances for the reporting period is 1 percent or greater of the total operating time for the reporting period, or the total CMS downtime for the reporting period is 5 percent or greater of the total operating time for the reporting period, both the summary report and the excess emissions and continuous monitoring system performance report shall be submitted.

(4) Reporting continuous opacity monitoring system data produced during a performance test. The owner or operator of an affected source required to use a COMS shall record the monitoring data produced during a performance test required under § 63.7 and shall furnish the Administrator a written report of the monitoring results. The report of COMS data shall be submitted simultaneously with the report of the performance test results required in paragraph (d)(2) of this section.

(f) Waiver of recordkeeping or reporting requirements.

(1) Until a waiver of a recordkeeping or reporting requirement has been granted by the Administrator under this paragraph, the owner or operator of an affected source remains subject to the requirements of this section.

(2) Recordkeeping or reporting requirements may be waived upon written application to the Administrator if, in the Administrator's judgment, the affected source is achieving the relevant standard(s), or the source is operating under an extension of compliance, or the owner or operator has requested an extension of compliance and the Administrator is still considering that request.

(3) If an application for a waiver of recordkeeping or reporting is made, the application shall accompany the request for an extension of compliance under § 63.6(i), any required compliance progress report or compliance status report required under this part (such as under §§ 63.6(i) and 63.9(h)) or in the source's title V permit, or an excess emissions and continuous monitoring system performance report required under paragraph (e) of this section, whichever is applicable. The application shall include whatever information the owner or operator considers useful to convince the Administrator that a waiver of recordkeeping or reporting is warranted.

(4) The Administrator will approve or deny a request for a waiver of recordkeeping or reporting requirements under this paragraph when he/she—

(i) Approves or denies an extension of compliance; or

(ii) Makes a determination of compliance following the submission of a required compliance status report or excess emissions and continuous monitoring systems performance report; or

(iii) Makes a determination of suitable progress towards compliance following the submission of a compliance progress report, whichever is applicable.

(5) A waiver of any recordkeeping or reporting requirement granted under this paragraph may be conditioned on other recordkeeping or reporting requirements deemed necessary by the Administrator.

(6) Approval of any waiver granted under this section shall not abrogate the Administrator's authority under the Act or in any way prohibit the Administrator from later canceling the waiver. The cancellation will be made only after notice is given to the owner or operator of the affected source.

§ 63.11527 What are the monitoring requirements for new and existing sources?

(a) EAF equipped with fabric filters —

(5) You must prepare a site-specific monitoring plan for each bag leak detection system. You must operate and maintain each bag leak detection system according to the plan at all times. Each plan must address all of the items identified in paragraphs (a)(5)(i) through (a)(5)(v)of this section.

(i) Installation of the bag leak detection system.

(ii) Initial and periodic adjustment of the bag leak detection system including how the alarm set-point and alarm delay time will be established.

(iii) Operation of the bag leak detection system including quality assurance procedures.

(iv) Maintenance of the bag leak detection system including a routine maintenance schedule and spare parts inventory list.

(v) How the bag leak detection system output will be recorded and stored.

§ 63.11529 What are the notification, reporting, and recordkeeping requirements?

(a) Initial Notification. You must submit the Initial Notification required by § 63.9(b)(2) no later than 120 days after December 23, 2008, or no later than 120 days after the source becomes subject to this subpart, whichever is later. The Initial Notification must include the information specified in § 63.9(b)(2)(i) through (iv).

(b) Notification of compliance status. You must submit a Notification of Compliance Status in accordance with § 63.9(h) of the General Provisions before the close of business on the 30th day following the completion of the initial compliance demonstration. This notification must include the following:

(1) The results of Method 22 (appendix A-7 of 40 CFR part 60) test for VE as required by § 63.11528(a);

(2) If you have installed a bag leak detection system, documentation that the system satisfies the design requirements specified in § 63.11527(a)(3) and that you have prepared a site-specific monitoring plan that meets the requirements specified in § 63.11527(a)(5);

(3) The results of the Method 9 (appendix A-4 of 40 CFR part 60) test for building opacity as required by § 63.11528(a).

(c) Annual compliance certification. If you own or operate an affected source, you must submit an annual certification of compliance according to paragraphs (c)(1) through (c)(4) of this section.

(1) The results of any daily or weekly visual monitoring events required by § 63.11527(a)(1) and (b)(1), alarm-based visual monitoring at sources equipped with bag leak detection systems as required by § 63.11527(a)(4), or readings outside of the operating range at sources using CPMS on wet scrubbers required by § 63.11527(b)(4).

(2) The results of the follow up Method 22 (appendix A-7 of 40 CFR part 60) tests that are required if VE are observed during the daily or weekly visual monitoring, alarm-based visual monitoring, or out-of-range operating readings as described in paragraph (c)(1) of this section.

(3) The results of the Method 22 (appendix A-7 of 40 CFR part 60) or Method 9 (appendix A-4 of 40 CFR part 60) tests required by § 63.11528(b) and (c), respectively.

(4) If you operate a bag leak detection system for a fabric filter or a CPMS for a wet scrubber, submit annual reports according to the requirements in § 63.10(e) and include summary information on the number, duration, and cause (including unknown cause, if applicable) for monitor downtime incidents (other than downtime associated with zero and span or other calibration checks, if applicable).

(d) You must keep the records specified in paragraphs (d)(1) through (d)(2) of this section.

(1) As required in § 63.10(b)(2)(xiv), you must keep a copy of each notification that you submitted to comply with this subpart and all documentation supporting any Initial Notification, Notification of Compliance Status, and annual compliance certifications that you submitted.

(2) You must keep the records of all daily or weekly visual, Method 22 (appendix A-7 of 40 CFR part 60), and Method 9 (appendix A-4 of 40 CFR part 60) monitoring data required by § 63.11527 and the information identified in paragraphs (d)(2)(i) through (d)(2)(v) of this section.

(i) The date, place, and time of the monitoring event;

(ii) Person conducting the monitoring;

(iii) Technique or method used;

(iv) Operating conditions during the activity; and

(v) Results, including the date, time, and duration of the period from the time the monitoring indicated a problem (e.g., VE) to the time that monitoring indicated proper operation.

(f) As specified in § 63.10(b)(1), you must keep each record for 5 years following the date of each recorded action.

(g) You must keep each record onsite for at least 2 years after the date of each recorded action according to § 63.10(b)(1). You may keep the records offsite for the remaining 3 years.