26.02.2015 Views

o_19f3m1n7k170b14e9u0oqipgu4a.pdf

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

tuations, which can affect system reliability. However,<br />

the general methodologies described in this section can<br />

also be applied to other uses of reclaimed water and other<br />

locations as long as the appropriate parameters are defined.<br />

3.5.1 Identifying the Operating Parameters<br />

In many cases, a water reuse system will provide reclaimed<br />

water to a diverse customer base. Urban reuse<br />

customers typically include golf courses and parks and<br />

may also include commercial and industrial customers.<br />

Such is the case in both the City of St. Petersburg,<br />

Florida, and Irvine Ranch Water District, California, reuse<br />

programs. These programs provide water for cooling,<br />

washdown, and toilet flushing as well as for irrigation.<br />

Each water use has a distinctive seasonal demand<br />

pattern and, thereby, impacts the need for storage.<br />

Reuse systems have significant differences with traditional<br />

land application systems starting with the fundamental<br />

objectives of each. Land application systems<br />

seek to maximize hydraulic loadings while reuse systems<br />

provide nonpotable waters for uses where a higher<br />

quality of water is not required. Historical water use patterns<br />

should be used where available. Methodologies<br />

developed for land application systems are generally<br />

poorly suited to define expected demands of an irrigation-based<br />

reuse system and should be replaced with<br />

methodologies expressly developed to estimate irrigation<br />

needs. This point was illustrated well by calculations<br />

of storage required to prevent a discharge based<br />

on: (1) actual golf course irrigation use over a 5-year<br />

period and (2) use of traditional land application water<br />

balance methods using site-specific hydrogeological information<br />

and temperature and rainfall corresponding to<br />

the 5-year record of actual use. Use of historical records<br />

estimated a required storage volume of 89 days of flow,<br />

while traditional land application methods estimated a<br />

required storage volume of 196 days (Ammerman et al.,<br />

1997). It should also be noted that, like potable water,<br />

the use of reclaimed water is subject to the customer’s<br />

perceived need for water.<br />

The primary factors controlling the need for supplemental<br />

irrigation are evapotranspiration and rainfall. Evapotranspiration<br />

is strongly influenced by temperature and<br />

will be lowest in the winter months and highest in midsummer.<br />

Water use for irrigation will also be strongly<br />

affected by the end user and their attention to the need<br />

for supplemental water. Where uses other than irrigation<br />

are being investigated, other factors will be the driving<br />

force for demand. For example, demand for reclaimed<br />

water for industrial reuse will depend on the needs of the<br />

specific industrial facility. These demands could be estimated<br />

based on past water use records, if data are available,<br />

or a review of the water use practices of a given<br />

industry. When considering the demand for water in a<br />

manmade wetland, the system must receive water at the<br />

necessary time and rate to ensure that the appropriate<br />

hydroperiod is simulated. If multiple uses of reclaimed<br />

water are planned from a single source, the factors affecting<br />

the demand of each should be identified and integrated<br />

into a composite system demand.<br />

Figure 3-12 presents the average monthly potential<br />

evaporation and average monthly rainfall in southwest<br />

Florida and Davis, California (Pettygrove and Asano,<br />

Figure 3-12.<br />

Average Monthly Rainfall and Pan Evaporation<br />

120

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!