My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
75D - PH WATER QUALITY
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2007
>
07/02/2007
>
75D - PH WATER QUALITY
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/3/2012 4:39:02 PM
Creation date
6/27/2007 10:31:09 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Item #
75D
Date
7/2/2007
Destruction Year
2012
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
6
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
was all summarized in our 2004, 2005, and 2006 Annual Water Quality Reports, which were <br />mailed to all of our customers. (Reference No. 3) <br />Guidelines Followed: <br />The Association of California Water Agencies (ACWA) formed a work group, which <br />prepazed guidelines for water utilities to use in preparing these required reports. The ACWA <br />guidelines were used in the prepazation of this report. <br />Best Available Technology and Cost Estimates: <br />Both the USEPA and CDHS adopt what are known as BATs or Best Available <br />Technology, which are the best known methods of reducing contaminant levels to the MCL. <br />Costs can be estimated for such technologies. However, since many PHGs and all MCLGs aze <br />set lower than the MCL, it is not always possible nor feasible to determine what treatment is <br />needed to further reduce a constituent downwazd to or neaz the PHG or MCLG, many of which <br />are set at zero. Estimating the costs to reduce a constituent to zero is difficult, if not impossible <br />because it is not possible to verify by analytical means that the level has been lowered to zero. In <br />some cases, installing treatment to try and further reduce very low levels of one constituent may <br />have adverse effects on other aspects of water quality. <br />Constituents Detected That Exceed a PHG or a MCLG: <br />The following is a discussion of constituents that were detected in one or more of our <br />drinking water sources at levels above PHG. <br />Naturally Occurring Urauium <br />The PHG for Natural Uranium is 0.43 pCi/L. The MCL or drinking water standard for <br />Natural Uranium is 20 pCi/L. We have detected Natural Uranium in 3 of our 20 wells at levels <br />4.45 to 10.4 pCi/L. The levels detected were below the MCL. The category of health risk <br />associated with Natural Uranium, and the reason that a drinking water standard was adopted for <br />it, is that people who drink water containing Natural Uranium above the MCL throughout their <br />lifetime could experience an increased risk of cancer. The 20 pCi/L MCL established by the <br />CDHS if complied with should have no adverse health effect. The numerical risk for cancer for <br />water containing Uranium at the PHG level of 0.43 pCi/L is one case in 1,000,000. The large <br />water system BAT for Natural Uranium to lower the levels below the PHG is Ion Exchange. <br />Total water production for all affected wells is 32,446 gallons per minute. Based on the USEPA <br />studies, the initial cost to treat one thousand gallons of water at 80 percent removal efficiency for <br />lazge water systems ranges from $0.50 to $0.65. The on going cost for the treatment ranges from <br />$0.50 to $0.65 per thousand gallons of water treated. For the City of Santa Ana, the estimated <br />cost to install such treatment systems (Ion Exchange) ranges between $6.45 and $20.0 Million. <br />The cost to operate the treatment facilities will range from $6.45 to $7.9 million per yeaz. The <br />cost to build the treatment facilities would result in an assumed increased cost for each customer <br />of $18.53 to $57.45 in the first year and from $18.50 to $22.70 per customer annually. <br />2 <br />75D-4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.