This is the preview version of the Wisconsin State Legislature site.
Please see http://docs.legis.wisconsin.gov for the production version.
NR 460.05(7)(h)5.b.b. Under par. (d), the proper operation and maintenance of the installed controls during the extension period.
NR 460.05(7)(i)(i) The owner or operator of an existing source that has been granted a compliance date extension under par. (g) may be required to submit to the department progress reports indicating whether the steps toward compliance outlined in the compliance schedule have been reached. The contents of the progress reports and the dates by which they shall be submitted shall be specified in the written compliance date extension granted under par. (h).
NR 460.05(7)(j)1.1. The department shall notify the owner or operator in writing of approval or intention to deny approval of a request for an extension of compliance within 30 calendar days after receipt of sufficient information to evaluate a request submitted under par. (c) 1. or (d). The department shall notify the owner or operator in writing of the status of the application, that is, whether the application contains sufficient information to make a determination within 30 calendar days after receipt of the original application and within 30 calendar days after receipt of any supplementary information that is submitted. The 30-day approval or denial period shall begin after the owner or operator has been notified in writing that the application is complete.
NR 460.05(7)(j)2.2. When notifying the owner or operator that an application is not complete, the department shall specify the information needed to complete the application and provide notice of opportunity for the applicant to present, in writing, within 30 calendar days after notification of the incomplete application, additional information or arguments to the department to enable further action on the application.
NR 460.05(7)(j)3.3. Before denying any request for a compliance date extension, the department shall notify the owner or operator in writing of the department’s intention to issue the denial, together with all of the following:
NR 460.05(7)(j)3.a.a. Notice of the information and findings on which the intended denial is based.
NR 460.05(7)(j)3.b.b. Notice of opportunity for the owner or operator to present in writing, within 15 calendar days after notification of the intended denial, additional information or arguments to the department before further action on the request.
NR 460.05(7)(j)4.4. The department’s final determination to deny any request for an extension shall be in writing and shall set forth the specific grounds on which the denial is based. The final determination shall be made within 30 calendar days after presentation of additional information or argument, if the application is complete, or within 30 calendar days after the final date specified for the presentation if no presentation is made.
NR 460.05(7)(k)1.1. The department shall notify the owner or operator in writing of approval or intention to deny approval of a request for a compliance date extension within 30 calendar days after receipt of sufficient information to evaluate a request submitted under par. (c) 2. The 30-day approval or denial period will begin after the owner or operator has been notified in writing that the application is complete. The department shall notify the owner or operator in writing of the status of the application, that is, whether the application contains sufficient information to make a determination, within 15 calendar days after receipt of the original application and within 15 calendar days after receipt of any supplementary information that is submitted.
NR 460.05(7)(k)2.2. When notifying the owner or operator that an application is not complete, the department shall specify the information needed to complete the application and provide notice of opportunity for the applicant to present, in writing, within 15 calendar days after notification of the incomplete application, additional information or arguments to the department to enable further action on the application.
NR 460.05(7)(k)3.3. Before denying any request for a compliance date extension, the department shall notify the owner or operator in writing of the department’s intention to issue the denial, together with all of the following:
NR 460.05(7)(k)3.a.a. Notice of the information and findings on which the intended denial is based.
NR 460.05(7)(k)3.b.b. Notice of opportunity for the owner or operator to present in writing, within 15 calendar days after notification of the intended denial, additional information or arguments to the department before further action on the request.
NR 460.05(7)(k)4.4. A final determination to deny any request for an extension shall be in writing and shall set forth the specific grounds on which the denial is based. The final determination shall be made within 30 calendar days after presentation of additional information or argument, if the application is complete, or within 30 calendar days after the final date specified for the presentation if no presentation is made.
NR 460.05(7)(L)(L) The department may terminate an extension of compliance at an earlier date than specified if any specification under par. (h) 3. or 4. is not met.
NR 460.05(7)(L)1.1. Upon making a determination to terminate, the department shall notify, in writing, the owner or operator of the department’s determination to terminate, together with both of the following:
NR 460.05(7)(L)1.a.a. Notice of the reason for termination.
NR 460.05(7)(L)1.b.b. Notice of opportunity for the owner or operator to present in writing, within 15 calendar days after notification of the determination to terminate, additional information or arguments to the department before further action on the termination.
NR 460.05(7)(L)2.2. A termination of an extension of compliance shall be in writing and shall set forth the specific grounds on which the termination is based. The termination shall be made within 30 calendar days after presentation of additional information or arguments, or within 30 calendar days after the final date specified for the presentation if no presentation is made.
NR 460.05 HistoryHistory: Cr. Register, March, 1997, No. 495, eff. 4-1-97; corrections in (4) (c) 4., (6) (b) 1. b. and c., (d) 1. b., (f) 2., 5., and (g) made under s. 13.93 (2m) (b) 7., Stats., Register March 2002 No. 555; CR 05-039: am. (1) (a) (intro.), (2) (a), (c) 1., (d), (f), (3) (b), (4) (a) 1., 2., (c) 1., 3. to 6., 7. (intro.), b., c., and 8., (5), (6) (a), (7) (c) 1. b., 2., (j) 1. and (L), r. and recr. (1) (a) 1. and 2., renum. (3) (c) 1., (7) (e) 2. b. and d. to be (3) (c), (7) (e) 2. a. and b. and am. (3) (c) and (7) (e) 2. a., r. (3) (c) 2., (4) (b), (7) (e) 2. a. and c., 3. and 4., cr. (3m), (4) (c) 7. d. and 9., (7) (c) 1. c., (L) 1. and 2., Register February 2006 No. 602, eff. 3-1-06; CR 07-105: am. (4) (a) 2., (c) 1. (intro.), 3. to 5., 9., r. (4) (c) 2. Register December 2008 No. 636, eff. 1-1-09.
NR 460.06NR 460.06Performance testing requirements.
NR 460.06(1)(1)Applicability and performance test dates.
NR 460.06(1)(a)(a) Unless otherwise specified, this section applies to the owner or operator of an affected source required to do performance testing, or another form of compliance demonstration, under a relevant standard.
NR 460.06(1)(b)(b) Except as provided in par. (d), if required to do performance testing by a relevant standard, and unless a waiver of performance testing is obtained under this section or the conditions of sub. (5) apply, the owner or operator of the affected source shall perform the tests within 180 days of the compliance date.
NR 460.06(1)(c)(c) Except as provided in par. (d), when an emission standard promulgated under 40 CFR part 63 is more stringent than the standard as proposed, the owner or operator of a new or reconstructed source subject to that standard for which construction or reconstruction is commenced between the proposal and promulgation dates of the standard shall comply with performance testing requirements within 180 days after the standard’s effective date, or within 180 days after startup of the source, whichever is later. If the promulgated standard is more stringent than the proposed standard, the owner or operator may choose to demonstrate compliance with either the proposed or the promulgated standard. If the owner or operator chooses to comply with the proposed standard initially, the owner or operator shall conduct a second performance test within 3 years and 180 days after the effective date of the standard, or after startup of the source, whichever is later, to demonstrate compliance with the promulgated standard.
NR 460.06(1)(d)(d) If a force majeure is about to occur, occurs or has occurred for which the affected owner or operator intends to assert a claim of force majeure, all of the following apply:
NR 460.06(1)(d)1.1. The owner or operator shall notify the department in writing as soon as practicable following the date the owner or operator first knew, or, through due diligence, should have known that the event may cause or caused a delay in testing beyond the regulatory deadline specified in pars. (b) and (c), chs. NR 462 to 469 or a permit, but the notification shall occur before the performance test deadline unless the initial force majeure or a subsequent force majeure delays the notice, in which case the notification shall occur as soon as practicable.
NR 460.06(1)(d)2.2. The owner or operator shall provide to the department a written description of the force majeure and a rationale for attributing the delay in testing beyond the regulatory deadline to the force majeure, describe the measures taken or to be taken to minimize the delay and identify a date by which the owner or operator proposes to conduct the performance test. The performance test shall be conducted as soon as practicable after the force majeure occurs.
NR 460.06(1)(d)3.3. The decision as to whether or not to grant an extension to the performance test deadline is solely within the discretion of the department. The department shall notify the owner or operator in writing of approval or disapproval of the request for an extension as soon as practicable.
NR 460.06(1)(d)4.4. Until an extension of the performance test deadline has been approved by the department under subd. 3., the owner or operator of the affected facility remains strictly subject to the requirements of chs. NR 460 to 469 and all applicable permits.
NR 460.06(2)(2)Department oversight of performance testing. Performance tests shall be conducted in accordance with s. NR 439.07 (2) to (4) and (6).
NR 460.06(3)(3)Performance testing facilities. If required to do performance testing, the owner or operator of each new MACT source and, at the request of the department, the owner or operator of each existing source, shall provide all of the following performance testing facilities:
NR 460.06(3)(a)(a) Sampling ports adequate for test methods applicable to the source. This includes all of the following:
NR 460.06(3)(a)1.1. Constructing the air pollution control system such that volumetric flow rates and pollutant emission rates can be accurately determined by applicable test methods and procedures.
NR 460.06(3)(a)2.2. Providing a stack or duct free of cyclonic flow during performance tests, as demonstrated by applicable test methods and procedures.
NR 460.06(3)(b)(b) Safe sampling platforms.
NR 460.06(3)(c)(c) Safe access to sampling platforms.
NR 460.06(3)(d)(d) Utilities for sampling and testing equipment.
NR 460.06(3)(e)(e) Any other facilities that the department deems necessary for safe and adequate testing of a source.
NR 460.06(4)(4)Conduct of performance tests.
NR 460.06(4)(a)(a) Performance tests shall be conducted under such conditions as the department specifies to the owner or operator based on normal, representative performance of the affected source. Operations during periods of startup, shutdown and malfunction do not constitute representative conditions for the purpose of a performance test, nor will emissions in excess of the level of the relevant standard during periods of startup, shutdown and malfunction be considered a violation of the relevant standard unless otherwise specified in the relevant standard or a determination of noncompliance is made under s. NR 460.05 (4). Upon request, the owner or operator shall make available to the department such records as may be necessary to determine the conditions of performance tests.
NR 460.06(4)(b)(b) Performance tests shall be conducted and data shall be reduced in accordance with the test methods and procedures in this section, in each relevant standard, and, if required, in applicable appendices of parts 51, 60, 61 and 63 of title 40 of the code of federal regulations, incorporated by reference in s. NR 484.04 (9), (13), (21), (23) and (25), unless any of the following actions is taken:
NR 460.06(4)(b)1.1. The department specifies or approves, in specific cases, the use of a test method with minor changes in methodology. Changes may be approved in conjunction with approval of the site-specific test plan specified in sub. (2).
NR 460.06(4)(b)2.2. The department approves the use of an intermediate change or alternative, or the administrator approves the use of a major change or alternative to a test method, the results of which the department or administrator has determined to be adequate for indicating whether a specific affected source is in compliance.
NR 460.06 NoteNote: Under 40 CFR 63.91 (g) only EPA can approve major alternatives to test methods.
NR 460.06(4)(b)3.3. The department approves shorter sampling times or smaller sample volumes when necessitated by process variables or other factors.
NR 460.06(4)(b)4.4. The department waives the requirement for performance tests because the owner or operator of an affected source has demonstrated by other means to the department’s satisfaction that the affected source is in compliance with the relevant standard.
NR 460.06(4)(c)(c) Unless otherwise specified in a relevant standard or test method, each performance test shall consist of 3 separate runs using the applicable test method. Each run shall be conducted for the time and under the conditions specified in the relevant standard. For the purpose of determining compliance with a relevant standard, the arithmetic mean of the results of the 3 runs shall apply. Upon receiving approval from the department, results of a test run may be replaced with results of an additional test run in the event that any of the following occurs:
NR 460.06(4)(c)1.1. A sample is accidentally lost after the testing team leaves the site.
NR 460.06(4)(c)2.2. Conditions occur in which one of the 3 runs must be discontinued because of forced shutdown.
NR 460.06(4)(c)3.3. Extreme meteorological conditions occur.
NR 460.06(4)(c)4.4. Other circumstances occur that are beyond the owner or operator’s control.
NR 460.06(5)(5)Use of an alternative test method.
NR 460.06(5)(a)(a) Until authorized to use an intermediate or major change or alternative to a test method, the owner or operator of an affected source remains subject to the requirements of this section and the relevant standard.
NR 460.06 NoteNote: Under 40 CFR 63.91 (g) only EPA can approve major alternatives to test methods.
NR 460.06(5)(b)(b) The owner or operator of an affected source required to do performance testing by a relevant standard may use an alternative test method from that specified in the standard provided that the owner or operator does all of the following:
NR 460.06(5)(b)1.1. Notifies the department of his or her intention to use an alternative test method at least 60 days before the performance test is scheduled to begin.
NR 460.06(5)(b)2.2. Uses Method 301 in Appendix A of 40 CFR part 63, incorporated by reference in s. NR 484.04 (25), to validate the alternative test method. This may include the use of specific procedures of Method 301 if use of the procedures is sufficient to validate the alternative test method.
NR 460.06(5)(b)3.3. Submits the results of the Method 301 validation process along with the notification of intention and the justification for not using the specified test method. The owner or operator may submit the information required in this subsection well in advance of the deadline specified in subd. 1. to ensure a timely review by the administrator or the department in order to meet the performance test date specified in this section or the relevant standard.
NR 460.06(5)(c)(c) The department shall determine whether the owner or operator’s validation of the proposed alternative test method is adequate and issue an approval or disapproval of the alternative test method. If the owner or operator intends to demonstrate compliance by using an alternative to any test method specified in the relevant standard, the owner or operator is authorized to conduct the performance test using an alternative test method after the department approves the use of the alternative method. However, the owner or operator is authorized to conduct the performance test using an alternative method in the absence of notification of approval or disapproval 45 days after submission of the request to use an alternative method and the request satisfies the requirements in par. (b). The owner or operator is authorized to conduct the performance test within 60 calendar days after authorization to demonstrate compliance using an alternative test method. Notwithstanding the requirements in the preceding 3 sentences, the owner or operator may proceed to conduct the performance test as required in this section, without the department’s prior approval of the site-specific test plan, if the owner or operator subsequently chooses to use the specified testing and monitoring methods instead of an alternative.
NR 460.06(5)(d)(d) If the department finds reasonable grounds to dispute the results obtained by an alternative test method for the purposes of demonstrating compliance with a relevant standard, the department may require the use of a test method specified in a relevant standard.
NR 460.06(5)(e)(e) If the owner or operator uses an alternative test method for an affected source during a required performance test, the owner or operator of the source shall continue to use the alternative test method for subsequent performance tests at that affected source until he or she receives approval from the department to use another test method as allowed under this subsection.
NR 460.06(5)(f)(f) Neither the validation and approval process nor the failure to validate an alternative test method shall abrogate the owner or operator’s responsibility to comply with the requirements of 40 CFR part 63 or chs. NR 460 to 469.
NR 460.06(6)(6)Data analysis, recordkeeping, and reporting.
NR 460.06(6)(a)(a) Unless otherwise specified in a relevant standard or test method, or as otherwise approved by the department in writing, results of a performance test shall include the analysis of samples, determination of emissions and raw data. A performance test is “completed” when field sample collection is terminated. The owner or operator of an affected source shall report the results of the performance test to the department 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 department. The results of the performance test shall be submitted as part of the notification of compliance status required under s. NR 460.08 (8). The owner or operator shall send the results of the performance test to the department.
NR 460.06(6)(b)(b) For a minimum of 5 years after a performance test is conducted, the owner or operator shall retain and make available, upon request, for inspection by the department the records or results of the performance test and other data needed to determine emissions from an affected source.
NR 460.06(7)(7)Waiver of performance tests.
NR 460.06(7)(a)(a) Until a waiver of a performance testing requirement has been granted by the department under this subsection, the owner or operator of an affected source remains subject to the requirements of this section.
NR 460.06(7)(b)(b) Individual performance tests may be waived upon written application to the department if, in the department’s judgment, the source is meeting the relevant standards on a continuous basis, or the source is being operated under a compliance date extension, or the owner or operator has requested a compliance date extension and the department is still considering that request.
NR 460.06(7)(c)1.1. If a request is made for a compliance date extension under s. NR 460.05 (7), the application for a waiver of an initial performance test shall accompany the information required for the request for an extension. If no extension is requested or if the owner or operator has requested an extension and the department is still considering that request, the application for a waiver of an initial performance test shall be submitted at least 60 days before the performance test.
NR 460.06(7)(c)2.2. If an application for a waiver of a subsequent performance test is made, the application may accompany any required compliance progress report, compliance status report, or excess emissions and continuous monitoring system performance report, but it shall be submitted at least 60 days before the performance test.
NR 460.06(7)(c)3.3. Any application for a waiver of a performance test shall include information justifying the owner or operator’s request for a waiver, such as the technical or economic infeasibility, or the impracticality, of the affected source performing the required test.
NR 460.06(7)(d)(d) The department shall approve or deny a request for a waiver of a performance test made under par. (c) when it does whichever of the following applies:
NR 460.06(7)(d)1.1. Approves or denies a compliance date extension under s. NR 460.05 (7) (g) to (L).
NR 460.06(7)(d)2.2. Responds to a site-specific test plan under sub. (2).
NR 460.06(7)(d)3.3. Makes a determination of compliance following the submission of a required compliance status report or excess emissions and continuous monitoring systems performance report.
NR 460.06(7)(d)4.4. Makes a determination of suitable progress towards compliance following the submission of a compliance progress report.
NR 460.06(7)(e)(e) Approval of any waiver granted under this section may not in any way prohibit the department from later canceling the waiver. The cancellation shall be made only after notice is given to the owner or operator of the affected source.
NR 460.06 HistoryHistory: Cr. Register, March, 1997, No. 495, eff. 4-1-97; CR 00-175: am. (4) (b) (intro.), 1. and 2., (5) (a), (b) 3. and (c), renum. (4) (b) 3. and 4. to be (4) (b) 4. and 5. and am., cr. (4) (b) 3. and (5) (b) 4. Register March 2002 No. 555, eff. 4-1-02; correction in (5) (b) 2. made under s. 13.93 (2m) (b) 7., Stats., Register March 2002 No. 555; CR 05-039: renum. (1) (b) (intro.) and 7. and (4) (b) 4. and 5. to be (1) (b) and (c) and (4) (b) 3. and 4. and am., r. (1) (b) 1. to 6., (4) (b) 3. and (5) (b) 4., am. (4) (b) 1., 2., (5) (a), (b) 1., 2., and (c), Register February 2006 No. 602, eff. 3-1-06; CR 07-105: am. (1) (b) and (c), cr. (1) (d) Register December 2008 No. 636, eff. 1-1-09; corrections in (1) (d) 1. and 2. made under 13.92 (4) (b) 4., Stats., Register December 2008 No. 636.
NR 460.07NR 460.07Monitoring requirements.
NR 460.07(1)(1)Applicability.
NR 460.07(1)(a)1.1. Unless otherwise specified in a relevant standard, this section applies to the owner or operator of an affected source required to do monitoring under that standard.
NR 460.07(1)(a)2.2. Relevant standards established under 40 CFR part 63 or chs. NR 460 to 469 will specify monitoring systems, methods or procedures, monitoring frequency and other pertinent requirements for sources regulated by those standards. This section specifies general monitoring requirements such as those governing the conduct of monitoring and requests to use alternative monitoring methods. In addition, this section specifies detailed requirements that apply to affected sources required to use CMS under a relevant standard.
NR 460.07(1)(b)(b) For the purposes of 40 CFR part 63 and in chs. NR 460 to 469, all continuous monitoring systems required under relevant standards shall be subject to the provisions of this section upon federal promulgation of performance specifications for continuous monitoring systems as specified in the relevant standard or otherwise by the department.
NR 460.07(1)(c)(c) Additional monitoring requirements for control devices used to comply with provisions in relevant standards of 40 CFR part 63 are specified in s. NR 460.10.
Loading...
Loading...
Published under s. 35.93, Stats. Updated on the first day of each month. Entire code is always current. The Register date on each page is the date the chapter was last published.