Laserfiche WebLink
<br />O{)1259 <br /> <br />. <br /> <br />. <br /> <br />Draft Task 7 Technical Memorandum <br /> <br />Results from model scenarios were used in two ways. First, the model was used to test <br />the sensitivity of predicted demands shortages, reservoir contents and instream flows to various <br />operational constraints, new storage facilities and instream flow requirements. Second, model <br />results for each scenario were compared against results of the baseline scenario in order to <br />evaluate which scenario could best meet basin-wide water demands while providing flatwater <br />recreational opportunities and helping to protect the endangered fish. <br /> <br />Definition of Model Scenarios <br /> <br />In defining model scenarios, particular attention was given to the relative priorities of <br />the existing direct flow rights, the proposed instream flow right, existing and future storage <br />rights and future water demands. The structure of the scenarios was chosen to help answer the <br />following fundamental questions: 1) is there a sufficient legal and physical supply to meet all <br />future demands?, 2) if there is an insufficient legal supply, can the Juniper subordination make <br />up the shortages?, and 3) if there is an insufficient physical and/or legal supply, can reservoir <br />releases (from existing and/or proposed projects) make up the shortages? These questions <br />were addressed by the careful selection of priorities assigned to the proposed instream flow <br />right, to storage in reservoirs and to future demand increments. <br /> <br />Model scenarios were defined to help identify the best administrative and/or <br />development strategies to meet various demand levels in the basin. Each model scenario was <br />comprised of a suite of individual model runs and included three possible demand levels. The <br />three demand levels included the baseline (1989 maximum), 201S-level and 2040-level demand <br />conditions (Figure 3). These demand levels are represented in the model by defining demand <br />increments to bring the depleted depleted hydrology of the model up to the baseline or future <br />conditions (Figure 4). Formulation of the size and locations of basin demands was discussed in <br />detail in the Task 2 Technical Memorandum for this Feasibility Study. <br /> <br />Several administrative strategies were also investigated and included examining the <br />utility of subordination of the Juniper rights to all existing demands and possibly to 2015- <br />and/or 2040-level demands. Scenarios were structured to facilitate comparison of the strategies <br />of meeting future demands through subordination of the instream flow for endangered fish and <br />meeting future demands by making releases from storage accrued under rights considered <br />senior to the instream flow. <br /> <br />The following sections of this Technical Memorandum provide an overView of modeled <br />assumptions, a summary of results of model runs from five water development scenarios and <br />environmental and cost considerations for each alternative. <br /> <br />GENERAL MODEL ASSUMPTIONS <br /> <br />Priorities of Demands and Reservoirs <br /> <br />Diversions to meet demands or to fill reservoirs in the the basin model are made <br />according to the ranks assigned to demand and reservoir storage arcs of the network. These <br />ranks generally map the relative priorities of basin water rights, senior rights having higher <br />ranks. Conceptually, there are four categories of demands and reservoirs in the model, <br />grouped according to the priorities of the water rights which support them. Included are: 1) <br />existing demands and reservoirs with rights which are senior to the Juniper project water rights <br />(1954), 2) existing demands and reservoirs with rights which are junior to 1954, 3) future <br />demands and reservoirs with rights which are senior to 1954, and 4) future demands and <br />reservoirs with rights which are junior to 1954. <br /> <br />4 <br /> <br />,1,._, ~. <br />