NR 220.32(3)(a) (a) The alternative effluent limitation or standard requested is no more stringent than justified by the fundamental difference.
NR 220.32(3)(b) (b) Compliance with the alternative effluent limitation or standard would not result in any of the following:
NR 220.32(3)(b)1. 1. A removal cost wholly out of proportion to the removal cost considered during development of the effluent limitation guidelines.
NR 220.32(3)(b)2. 2. A non-water quality environmental impact, including energy requirements, fundamentally more adverse than the impact considered during development of the effluent limitations.
NR 220.32(4) (4)Fundamentally different factors. Factors that may be considered fundamentally different are limited to any of the following:
NR 220.32(4)(a) (a) The nature or quality of pollutants contained in the raw waste load of the applicant's process wastewater.
NR 220.32(4)(b) (b) The volume of the discharger's process wastewater and effluent discharged.
NR 220.32(4)(c) (c) Non-water quality environmental impact of control and treatment of the discharger's raw waste load.
NR 220.32(4)(d) (d) Energy requirements of the application of control and treatment technology.
NR 220.32(4)(e) (e) Age, size, land availability, and configuration as they relate to the discharger's raw waste load.
NR 220.32(4)(f) (f) Cost of compliance with required control technology.
NR 220.32(5) (5)Unapprovable FDFV requests. A variance request or portion of such a request under this section may not be granted on any of the following grounds:
NR 220.32(5)(a) (a) The infeasibility of installing the required waste treatment equipment within the time specified in the effluent limitation guidelines or standards or Clean Water Act.
NR 220.32 Note Note: A variance may be approved based on the discharger's inability to ultimately achieve effluent limitations, but not based on the discharger's ability to meet a limit within statutory deadlines.
NR 220.32(5)(b) (b) The assertion that the effluent limitation guidelines cannot be achieved with the appropriate waste treatment facilities installed if the assertion is not based on factors listed in sub. (4).
NR 220.32(5)(c) (c) The discharger's ability to pay for the required waste treatment.
NR 220.32(5)(d) (d) The impact of a discharge on local receiving water quality.
NR 220.32 History History: CR 17-002: cr. Register April 2018 No. 748, eff. 5-1-18.
NR 220.33 NR 220.33Variance application process.
NR 220.33(1) (1)ELG variance application deadlines.
NR 220.33(1)(a)(a) FDFV deadline. A written request for an alternative limitation based on a fundamentally different factors variance shall be submitted no later than 180 days after the date on which an effluent limitation guideline is published in the federal register, and any of the following apply:
NR 220.33(1)(a)1. 1. For a variance from an effluent limitation that is based on the best practicable control technology currently available under 33 USC 1311(b)(1)(A) and 1314(b)(1), the request shall be submitted by the close of the public comment period under s. 283.39, Stats.
NR 220.33(1)(a)2. 2. For a variance from an effluent limitation that is based on the best control technology available for conventional pollutants under 33 USC 1311(b)(2)(E) and 33 USC 1314(b)(4), or for variances from an effluent limitation that is based on the best available treatment technology economically achievable under 33 USC 1311(b)(2) and 33 USC 1314(b)(2), the request shall be submitted as part of the permit application for reissuance or modification.
NR 220.33(1)(b) (b) Other technology based limitation variance deadlines. Requests for a variance to an effluent guideline limitation under 33 USC 1311(c) or (g) shall comply with the deadlines and requirements in 40 CFR 122.21(m).
NR 220.33(1)(c) (c) Advanced notification. Before public notice of a draft permit modification or reissuance is given under s. 283.39, Stats., the department may notify a permitee or applicant in writing that the draft permit will likely contain limitations based on effluent limitation guidelines or standards that may be eligible for a variance under par. (a) or (b). In the written notice to the permittee, the department may require that the permittee submit a variance request within a reasonable time period if the permittee is interested in applying for a variance under par. (a) or (b). If the permittee wishes to request a variance, the variance application shall explain how the requirements for the variance have been met and the application shall be submitted within the reasonable time period specified in the written notice. The department may send the written notice to a permittee prior to submittal of a permit application for reissuance. If the department determines the variance is approvable, the draft permit or final permit may contain an alternative limitation that takes effect upon approval by the department and the EPA.
NR 220.33(2) (2)Content of FDFV application. Any permittee requesting an FDFV shall demonstrate and explain each of the following in the application:
NR 220.33(2)(a) (a) How the appropriate criteria of s. NR 220.32 have been met.
NR 220.33(2)(b) (b) How the factors listed in s. NR 220.32 regarding the discharger's facility are fundamentally different from the factors EPA or the department considered in establishing the effluent limitation guidelines. The requester shall reference all relevant material and information such as the published development documents in support of the effluent limitation guidelines, all associated technical and economic data collected for use in developing each effluent limitation guideline, all records of legal proceedings, and all written and printed documentation including records of communication that relevant to the regulations that are kept as public records by the department.
NR 220.33(2)(c) (c) How the alternative limitations requested are justified by the fundamental difference alleged in par. (b).
NR 220.33 History History: CR 17-002: cr. Register April 2018 No. 748, eff. 5-1-18.
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.