Laserfiche WebLink
<br />e <br /> <br />e <br /> <br />. <br /> <br />-) ~ Ij <br />:I <br /> <br />Functional Specification for the Planning Model <br /> <br />Among the practices to be represented in the Historical Scenario are the following: 1) <br />minimum flow of 300 cfs through the Black Canyon supported by releases from Blue Mesa <br />(when above minimum power pool), 2) subordination of Blue Mesa water rights to all existing <br />upstream uses, and 3) no call by Gunnison Tunnel direct flow rights against existing upstream <br />uses except Blue Mesa storage. All operating assumptions and practices represented in the <br />Baseline and Historical scenarios will be documented with references to the underling decrees <br />and authorities. <br /> <br />Outputs from both the Baseline and Historical scenarios will be provided with the <br />model. This will obviate the need to run these scenarios in order to compare them to user- <br />defined scenarios. . <br /> <br />Generalized Model "Constructs" and Their "Attributes" <br /> <br />Certain physical and operational components of the river basin system will be defined <br />within the model software to have a set of generic qualities or "attributes" and to operate in a <br />standardized manner. Examples of such standardized constructs are reservoirs, demands, <br />minimum streamflow rights, and contract delivery obligations, The purpose of using <br />standardized constructs is to make it easier for model users to specify new scenarios with <br />additional facilities or different operational rules in a consistent manner. The model will be <br />able to provide assistance and error-checking as such components are specified and will <br />"know" how to operate them during a model run, <br /> <br />In order for each instance of a generic construct in the model, a reservoir for example, <br />to be able to have the specific set of attributes which correspond to the important qualities of <br />its real-world counterpart, the generic construct must possess the superset of all reservoir <br />attributes. Therefore, there may be references in the following sections to some possible <br />characteristic of a particular reservoir, contracts for delivery of water to a group of demands, <br />for instance, which it does not have in the real world and will not have in the Baseline, but <br />which a user might decide to give it in a scenario. <br /> <br />WATER RIGHTS ADMINISTRATION AND STORAGE ACCOUNTING <br /> <br />This section of the Specification describes the general approach that will be used in <br />representing water rights administration and storage water accounting in the Planning Model <br />and describes how certain broad categories of water uses and rights will be treated. Details <br />about representation of specific water supply projects and systems are provided in a later <br />section of the Specification. <br /> <br />Water Rights Administration Approach <br /> <br />Existing basin water rights will be represented explicitly in the Planning Model and the <br />allocation of "available" water among water rights will adhere to the fundamental principle of <br />strict administration according to priority. A central part of the problem to be solved by the <br />model is the determination of the total amount of water available for allocation among water <br />rights. The total available water will include inflows to the stream system and water which <br />becomes "free" within the system after it has been beneficially used. The most common <br />example of such free water is return flow from irrigation, though the largest blocks <br />(volumetrically speaking) of free water will probably be those associated with power releases <br />from Blue Mesa and instream flows through the Black Canyon. <br /> <br />The water rights of larger projects and systems, as well as instream flow rights, will be <br />represented individually, while the water rights of smaller diversions will be represented in <br />aggregated form, Priorities and amounts of water rights will generally be subject to user <br /> <br />4 <br /> <br />" <br />I <br />I <br />I <br /> <br />.2.._ ;~.",~_,",,_ ,L _-;~j,4j <br />