§141.172. Disinfection profiling and benchmarking. — Inbound Citations

(2) Compliance with the profiling and benchmark requirements under the provisions of § 141.172.

As used in this part, the term:

(2) Systems may use disinfection profile(s) developed under § 141.172 or §§ 141.530 through 141.536 in lieu of developing a new profile if the system has neither made a significant change to its treatment practice nor changed sources since the profile was developed. Systems that have not developed a virus profile under § 141.172 or §§ 141.530 through 141.536 must develop a virus profile using the same monitoring data on which the Giardia lamblia profile is based.

(iv) When conducting sanitary surveys for systems required to comply with the disinfection profiling requirements in § 141.172 of this chapter, the State must also review the disinfection profile as part of the sanitary survey.

(i) Section 141.172(a)(3) of this chapter—How the State will approve a more representative annual data set than the data set determined under § 141.172 (a)(1) or (2) of this chapter for the purpose of determining applicability of the requirements of § 141.172 of this chapter.

(i) Section 141.172(a)(3) of this chapter—How the State will approve a more representative annual data set than the data set determined under § 141.172 (a)(1) or (2) of this chapter for the purpose of determining applicability of the requirements of § 141.172 of this chapter.

(i) Section 141.172(a)(3) of this chapter—How the State will approve a more representative annual data set than the data set determined under § 141.172 (a)(1) or (2) of this chapter for the purpose of determining applicability of the requirements of § 141.172 of this chapter.

(5) The system must submit data to the State on the schedule in paragraphs (a)(5)(i) through (v) of this section.

(i) Those systems that collected TTHM and HAA5 data under the provisions of subpart M (Information Collection Rule), as required by paragraphs (a)(1)(i) and (a)(2)(i) of this section, must submit the results of the samples collected during the last 12 months of required monitoring under § 141.142 not later than December 31, 1999.

(ii) Those systems that have collected four consecutive quarters of HAA5 occurrence data that meets the routine monitoring sample number and location for TTHM in §§ 141.12 and 141.30 and handling and analytical method requirements of § 141.142(b)(1), as allowed by paragraphs (a)(1)(ii) and (a)(2)(ii) of this section, must submit those data to the State not later than April 16, 1999. Until the State has approved the data, the system must conduct monitoring for HAA5 using the monitoring requirements specified under paragraph (a)(2)(iii) of this section.

(iii) Those systems that conduct monitoring for HAA5 using the monitoring requirements specified by paragraphs (a)(1)(iii) and (a)(2)(iii)(A) of this section, must submit TTHM and HAA5 data not later than March 31, 2000.

(iv) Those systems that elect to comply with all other provisions of this section as if the HAA5 monitoring had been conducted and the results required compliance with this section, as allowed under paragraphs (a)(2)(iii)(B) of this section, must notify the State in writing of their election not later than December 31, 1999.

(v) If the system elects to request that the State approve a more representative annual data set than the data set determined under paragraph (a)(2)(i) of this section, the system must submit this request in writing not later than December 31, 1999.

(5) The system must submit data to the State on the schedule in paragraphs (a)(5)(i) through (v) of this section.

(i) Those systems that collected TTHM and HAA5 data under the provisions of subpart M (Information Collection Rule), as required by paragraphs (a)(1)(i) and (a)(2)(i) of this section, must submit the results of the samples collected during the last 12 months of required monitoring under § 141.142 not later than December 31, 1999.

(ii) Those systems that have collected four consecutive quarters of HAA5 occurrence data that meets the routine monitoring sample number and location for TTHM in §§ 141.12 and 141.30 and handling and analytical method requirements of § 141.142(b)(1), as allowed by paragraphs (a)(1)(ii) and (a)(2)(ii) of this section, must submit those data to the State not later than April 16, 1999. Until the State has approved the data, the system must conduct monitoring for HAA5 using the monitoring requirements specified under paragraph (a)(2)(iii) of this section.

(iii) Those systems that conduct monitoring for HAA5 using the monitoring requirements specified by paragraphs (a)(1)(iii) and (a)(2)(iii)(A) of this section, must submit TTHM and HAA5 data not later than March 31, 2000.

(iv) Those systems that elect to comply with all other provisions of this section as if the HAA5 monitoring had been conducted and the results required compliance with this section, as allowed under paragraphs (a)(2)(iii)(B) of this section, must notify the State in writing of their election not later than December 31, 1999.

(v) If the system elects to request that the State approve a more representative annual data set than the data set determined under paragraph (a)(2)(i) of this section, the system must submit this request in writing not later than December 31, 1999.

(5) The system must submit data to the State on the schedule in paragraphs (a)(5)(i) through (v) of this section.

(i) Those systems that collected TTHM and HAA5 data under the provisions of subpart M (Information Collection Rule), as required by paragraphs (a)(1)(i) and (a)(2)(i) of this section, must submit the results of the samples collected during the last 12 months of required monitoring under § 141.142 not later than December 31, 1999.

(ii) Those systems that have collected four consecutive quarters of HAA5 occurrence data that meets the routine monitoring sample number and location for TTHM in §§ 141.12 and 141.30 and handling and analytical method requirements of § 141.142(b)(1), as allowed by paragraphs (a)(1)(ii) and (a)(2)(ii) of this section, must submit those data to the State not later than April 16, 1999. Until the State has approved the data, the system must conduct monitoring for HAA5 using the monitoring requirements specified under paragraph (a)(2)(iii) of this section.

(iii) Those systems that conduct monitoring for HAA5 using the monitoring requirements specified by paragraphs (a)(1)(iii) and (a)(2)(iii)(A) of this section, must submit TTHM and HAA5 data not later than March 31, 2000.

(iv) Those systems that elect to comply with all other provisions of this section as if the HAA5 monitoring had been conducted and the results required compliance with this section, as allowed under paragraphs (a)(2)(iii)(B) of this section, must notify the State in writing of their election not later than December 31, 1999.

(v) If the system elects to request that the State approve a more representative annual data set than the data set determined under paragraph (a)(2)(i) of this section, the system must submit this request in writing not later than December 31, 1999.

(5) The system must submit data to the State on the schedule in paragraphs (a)(5)(i) through (v) of this section.

(i) Those systems that collected TTHM and HAA5 data under the provisions of subpart M (Information Collection Rule), as required by paragraphs (a)(1)(i) and (a)(2)(i) of this section, must submit the results of the samples collected during the last 12 months of required monitoring under § 141.142 not later than December 31, 1999.

(ii) Those systems that have collected four consecutive quarters of HAA5 occurrence data that meets the routine monitoring sample number and location for TTHM in §§ 141.12 and 141.30 and handling and analytical method requirements of § 141.142(b)(1), as allowed by paragraphs (a)(1)(ii) and (a)(2)(ii) of this section, must submit those data to the State not later than April 16, 1999. Until the State has approved the data, the system must conduct monitoring for HAA5 using the monitoring requirements specified under paragraph (a)(2)(iii) of this section.

(iii) Those systems that conduct monitoring for HAA5 using the monitoring requirements specified by paragraphs (a)(1)(iii) and (a)(2)(iii)(A) of this section, must submit TTHM and HAA5 data not later than March 31, 2000.

(iv) Those systems that elect to comply with all other provisions of this section as if the HAA5 monitoring had been conducted and the results required compliance with this section, as allowed under paragraphs (a)(2)(iii)(B) of this section, must notify the State in writing of their election not later than December 31, 1999.

(v) If the system elects to request that the State approve a more representative annual data set than the data set determined under paragraph (a)(2)(i) of this section, the system must submit this request in writing not later than December 31, 1999.

(5) The system must submit data to the State on the schedule in paragraphs (a)(5)(i) through (v) of this section.

(i) Those systems that collected TTHM and HAA5 data under the provisions of subpart M (Information Collection Rule), as required by paragraphs (a)(1)(i) and (a)(2)(i) of this section, must submit the results of the samples collected during the last 12 months of required monitoring under § 141.142 not later than December 31, 1999.

(ii) Those systems that have collected four consecutive quarters of HAA5 occurrence data that meets the routine monitoring sample number and location for TTHM in §§ 141.12 and 141.30 and handling and analytical method requirements of § 141.142(b)(1), as allowed by paragraphs (a)(1)(ii) and (a)(2)(ii) of this section, must submit those data to the State not later than April 16, 1999. Until the State has approved the data, the system must conduct monitoring for HAA5 using the monitoring requirements specified under paragraph (a)(2)(iii) of this section.

(iii) Those systems that conduct monitoring for HAA5 using the monitoring requirements specified by paragraphs (a)(1)(iii) and (a)(2)(iii)(A) of this section, must submit TTHM and HAA5 data not later than March 31, 2000.

(iv) Those systems that elect to comply with all other provisions of this section as if the HAA5 monitoring had been conducted and the results required compliance with this section, as allowed under paragraphs (a)(2)(iii)(B) of this section, must notify the State in writing of their election not later than December 31, 1999.

(v) If the system elects to request that the State approve a more representative annual data set than the data set determined under paragraph (a)(2)(i) of this section, the system must submit this request in writing not later than December 31, 1999.

(iv) Section 141.173(b) of this chapter—For filtration technologies other than conventional filtration treatment, direct filtration, slow sand filtration, or diatomaceous earth filtration, how the State will determine that a public water system may use a filtration technology if the PWS demonstrates to the State, using pilot plant studies or other means, that the alternative filtration technology, in combination with disinfection treatment that meets the requirements of § 141.172(b) of this chapter, consistently achieves 99.9 percent removal and/or inactivation of Giardia lamblia cysts and 99.99 percent removal and/or inactivation of viruses, and 99 percent removal of Cryptosporidium oocysts. For a system that makes this demonstration, how the State will set turbidity performance requirements that the system must meet 95 percent of the time and that the system may not exceed at any time at a level that consistently achieves 99.9 percent removal and/or inactivation of Giardia lamblia cysts, 99.99 percent removal and/or inactivation of viruses, and 99 percent removal of Cryptosporidium oocysts.

(2) The system must monitor daily for a period of 12 consecutive calendar months to determine the total logs of inactivation for each day of operation, based on the CT99.9 values in Tables 1.1-1.6, 2.1, and 3.1 of § 141.74(b), as appropriate, through the entire treatment plant. This system must begin this monitoring not later than April 1, 2000. As a minimum, the system with a single point of disinfectant application prior to entrance to the distribution system must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section. A system with more than one point of disinfectant application must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section for each disinfection segment. The system must monitor the parameters necessary to determine the total inactivation ratio, using analytical methods in § 141.74(a), as follows:

(i) The temperature of the disinfected water must be measured once per day at each residual disinfectant concentration sampling point during peak hourly flow.

(ii) If the system uses chlorine, the pH of the disinfected water must be measured once per day at each chlorine residual disinfectant concentration sampling point during peak hourly flow.

(iii) The disinfectant contact time(s) (“T”) must be determined for each day during peak hourly flow.

(iv) The residual disinfectant concentration(s) (“C”) of the water before or at the first customer and prior to each additional point of disinfection must be measured each day during peak hourly flow.

(2) The system must monitor daily for a period of 12 consecutive calendar months to determine the total logs of inactivation for each day of operation, based on the CT99.9 values in Tables 1.1-1.6, 2.1, and 3.1 of § 141.74(b), as appropriate, through the entire treatment plant. This system must begin this monitoring not later than April 1, 2000. As a minimum, the system with a single point of disinfectant application prior to entrance to the distribution system must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section. A system with more than one point of disinfectant application must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section for each disinfection segment. The system must monitor the parameters necessary to determine the total inactivation ratio, using analytical methods in § 141.74(a), as follows:

(i) The temperature of the disinfected water must be measured once per day at each residual disinfectant concentration sampling point during peak hourly flow.

(ii) If the system uses chlorine, the pH of the disinfected water must be measured once per day at each chlorine residual disinfectant concentration sampling point during peak hourly flow.

(iii) The disinfectant contact time(s) (“T”) must be determined for each day during peak hourly flow.

(iv) The residual disinfectant concentration(s) (“C”) of the water before or at the first customer and prior to each additional point of disinfection must be measured each day during peak hourly flow.

(2) The system must monitor daily for a period of 12 consecutive calendar months to determine the total logs of inactivation for each day of operation, based on the CT99.9 values in Tables 1.1-1.6, 2.1, and 3.1 of § 141.74(b), as appropriate, through the entire treatment plant. This system must begin this monitoring not later than April 1, 2000. As a minimum, the system with a single point of disinfectant application prior to entrance to the distribution system must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section. A system with more than one point of disinfectant application must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section for each disinfection segment. The system must monitor the parameters necessary to determine the total inactivation ratio, using analytical methods in § 141.74(a), as follows:

(i) The temperature of the disinfected water must be measured once per day at each residual disinfectant concentration sampling point during peak hourly flow.

(ii) If the system uses chlorine, the pH of the disinfected water must be measured once per day at each chlorine residual disinfectant concentration sampling point during peak hourly flow.

(iii) The disinfectant contact time(s) (“T”) must be determined for each day during peak hourly flow.

(iv) The residual disinfectant concentration(s) (“C”) of the water before or at the first customer and prior to each additional point of disinfection must be measured each day during peak hourly flow.

(2) The system must monitor daily for a period of 12 consecutive calendar months to determine the total logs of inactivation for each day of operation, based on the CT99.9 values in Tables 1.1-1.6, 2.1, and 3.1 of § 141.74(b), as appropriate, through the entire treatment plant. This system must begin this monitoring not later than April 1, 2000. As a minimum, the system with a single point of disinfectant application prior to entrance to the distribution system must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section. A system with more than one point of disinfectant application must conduct the monitoring in paragraphs (b)(2)(i) through (iv) of this section for each disinfection segment. The system must monitor the parameters necessary to determine the total inactivation ratio, using analytical methods in § 141.74(a), as follows:

(i) The temperature of the disinfected water must be measured once per day at each residual disinfectant concentration sampling point during peak hourly flow.

(ii) If the system uses chlorine, the pH of the disinfected water must be measured once per day at each chlorine residual disinfectant concentration sampling point during peak hourly flow.

(iii) The disinfectant contact time(s) (“T”) must be determined for each day during peak hourly flow.

(iv) The residual disinfectant concentration(s) (“C”) of the water before or at the first customer and prior to each additional point of disinfection must be measured each day during peak hourly flow.

(ii) Section 141.172(b)(5) of this chapter—How the State will approve a method to calculate the logs of inactivation for viruses for a system that uses either chloramines or ozone for primary disinfection.

(i) Records of systems consulting with the State concerning a modification to disinfection practice under §§ 141.170(d), 141.172(c), and 141.542 of this chapter, including the status of the consultation.

(iii) Section 141.172(c) of this chapter—How the State will consult with PWSs to evaluate modifications to disinfection practice.

(d) Subpart H systems that did not conduct optional monitoring under § 141.172 because they served fewer than 10,000 persons when such monitoring was required, but serve more than 10,000 persons prior to January 1, 2005 must comply with §§ 141.170, 141.171, 141.173, 141.174, and 141.175. These systems must also consult with the State to establish a disinfection benchmark. A system that decides to make a significant change to its disinfection practice, as described in § 141.172(c)(1)(i) through (iv) must consult with the State prior to making such change.

(d) Subpart H systems that did not conduct optional monitoring under § 141.172 because they served fewer than 10,000 persons when such monitoring was required, but serve more than 10,000 persons prior to January 1, 2005 must comply with §§ 141.170, 141.171, 141.173, 141.174, and 141.175. These systems must also consult with the State to establish a disinfection benchmark. A system that decides to make a significant change to its disinfection practice, as described in § 141.172(c)(1)(i) through (iv) must consult with the State prior to making such change.

(d) Subpart H systems that did not conduct optional monitoring under § 141.172 because they served fewer than 10,000 persons when such monitoring was required, but serve more than 10,000 persons prior to January 1, 2005 must comply with §§ 141.170, 141.171, 141.173, 141.174, and 141.175. These systems must also consult with the State to establish a disinfection benchmark. A system that decides to make a significant change to its disinfection practice, as described in § 141.172(c)(1)(i) through (iv) must consult with the State prior to making such change.

(d) Subpart H systems that did not conduct optional monitoring under § 141.172 because they served fewer than 10,000 persons when such monitoring was required, but serve more than 10,000 persons prior to January 1, 2005 must comply with §§ 141.170, 141.171, 141.173, 141.174, and 141.175. These systems must also consult with the State to establish a disinfection benchmark. A system that decides to make a significant change to its disinfection practice, as described in § 141.172(c)(1)(i) through (iv) must consult with the State prior to making such change.

(2) Any system that is modifying its disinfection practice must calculate its disinfection benchmark using the procedure specified in paragraphs (c)(2)(i) through (ii) of this section.

(i) For each year of profiling data collected and calculated under paragraph (b) of this section, the system must determine the lowest average monthly Giardia lamblia inactivation in each year of profiling data. The system must determine the average Giardia lamblia inactivation for each calendar month for each year of profiling data by dividing the sum of daily Giardia lamblia of inactivation by the number of values calculated for that month.

(ii) The disinfection benchmark is the lowest monthly average value (for systems with one year of profiling data) or average of lowest monthly average values (for systems with more than one year of profiling data) of the monthly logs of Giardia lamblia inactivation in each year of profiling data.

(2) Any system that is modifying its disinfection practice must calculate its disinfection benchmark using the procedure specified in paragraphs (c)(2)(i) through (ii) of this section.

(i) For each year of profiling data collected and calculated under paragraph (b) of this section, the system must determine the lowest average monthly Giardia lamblia inactivation in each year of profiling data. The system must determine the average Giardia lamblia inactivation for each calendar month for each year of profiling data by dividing the sum of daily Giardia lamblia of inactivation by the number of values calculated for that month.

(ii) The disinfection benchmark is the lowest monthly average value (for systems with one year of profiling data) or average of lowest monthly average values (for systems with more than one year of profiling data) of the monthly logs of Giardia lamblia inactivation in each year of profiling data.

(4) The system must submit information in paragraphs (c)(4)(i) through (iii) of this section to the State as part of its consultation process.

(i) A description of the proposed change;

(ii) The disinfection profile for Giardia lamblia (and, if necessary, viruses) under paragraph (b) of this section and benchmark as required by paragraph (c)(2) of this section; and

(iii) An analysis of how the proposed change will affect the current levels of disinfection.

(4) The system must submit information in paragraphs (c)(4)(i) through (iii) of this section to the State as part of its consultation process.

(i) A description of the proposed change;

(ii) The disinfection profile for Giardia lamblia (and, if necessary, viruses) under paragraph (b) of this section and benchmark as required by paragraph (c)(2) of this section; and

(iii) An analysis of how the proposed change will affect the current levels of disinfection.

(4) The system must submit information in paragraphs (c)(4)(i) through (iii) of this section to the State as part of its consultation process.

(i) A description of the proposed change;

(ii) The disinfection profile for Giardia lamblia (and, if necessary, viruses) under paragraph (b) of this section and benchmark as required by paragraph (c)(2) of this section; and

(iii) An analysis of how the proposed change will affect the current levels of disinfection.

(2) Any system that is modifying its disinfection practice must calculate its disinfection benchmark using the procedure specified in paragraphs (c)(2)(i) through (ii) of this section.

(i) For each year of profiling data collected and calculated under paragraph (b) of this section, the system must determine the lowest average monthly Giardia lamblia inactivation in each year of profiling data. The system must determine the average Giardia lamblia inactivation for each calendar month for each year of profiling data by dividing the sum of daily Giardia lamblia of inactivation by the number of values calculated for that month.

(ii) The disinfection benchmark is the lowest monthly average value (for systems with one year of profiling data) or average of lowest monthly average values (for systems with more than one year of profiling data) of the monthly logs of Giardia lamblia inactivation in each year of profiling data.

(4) The system must submit information in paragraphs (c)(4)(i) through (iii) of this section to the State as part of its consultation process.

(i) A description of the proposed change;

(ii) The disinfection profile for Giardia lamblia (and, if necessary, viruses) under paragraph (b) of this section and benchmark as required by paragraph (c)(2) of this section; and

(iii) An analysis of how the proposed change will affect the current levels of disinfection.

(d) Subpart H systems that did not conduct optional monitoring under § 141.172 because they served fewer than 10,000 persons when such monitoring was required, but serve more than 10,000 persons prior to January 1, 2005 must comply with §§ 141.170, 141.171, 141.173, 141.174, and 141.175. These systems must also consult with the State to establish a disinfection benchmark. A system that decides to make a significant change to its disinfection practice, as described in § 141.172(c)(1)(i) through (iv) must consult with the State prior to making such change.