WSPC00985 - Laserfiche WebLink

Home Browse Search

OOHl~8 4. Demand Data 4.1 General The CRSS demand data consist of all the depletion inforlnation used by the simulation model. Since the CRSS uses a natural streamflow hydrology data base (see section 5), it is necessary to have demand data to deplete those natural flows for studying various levels of basin development and the resulting effects on water quality, flow, power generation, reservoir levels, etc. Several demand data bases have been developed for CRSS and are used as studies require. These demand data bases include a depletion schedule developed using Bureau of Reclamation data, and two depletion schedules developed using data provided by the Colorado River Basin Salinity Control Forum. 4.2 Demand Data Base ~ r: I A considerable amount of information is contained in the demand data base. This information includes locations of demands and return flows, annual amounts of withdrawal and depletion for each user, monthly di stri but ions of wi thdrawa 1 sand depl et ions, types of water use, and information on salt pickup. ~ The demand data base is not input directly to the model but is input to the SMOID (Simulation Model Demand Input Data) generation program. With the demand data base as input, SMDID generates the demand input data file for CRSM. The CRSM is structured such that 10 demand points can be utilized in each reach. The demand data base is structured such that each of these 10 demands can be further divided into as many as 10 separate "users." These 10 users are constrained, however, to using the same monthly distribution and the same return flow loop. While the theoretical 1 imi t to the number of users that coul d be used is presently 2500 (25 model reaches x 10 demand points/reach x 10 users/demand), the prac- tical limit is much less because some tributary reaches have few diver- sions. Since the model is also limited to a total of 10 inflow points per reach and most demands or diversions are associated with an inflow (return flow), this also effectively limits the number of demands possible in a reach. The present demand data base contains 120 demands consisting of a total of 245 users. Two lower basin demands, the Central Arizona Project and Metropolitan Water District, are handled uniquely. Both of these demands use two demand points. The first point gives the normal diversion schedule, whi Cll represents the demand' santi c i pated share of Colorado Ri ver water. The second point is used by the model to store the actual delivery, which includes the scheduled delivery minus any declared shortage or plus any scheduled surplus. i ~ 13