WSP01027 - Laserfiche WebLink

Home Browse Search

on~ZS5 USER SESSION DESCRIPTION NO.1 "Add a New Diversion" ., v ..... 'It' Current Version: 4 Version Date: 8/5/92 Previously Reviewed by: CMB, BHU, Committee. Edited by: CRR Hypothetical User 1. The ability to set up a reference scenario ("small-b baseline") and to define a new scenario in relation to it, is assumed for this session. A County Planning Commission staff member, a non-expert user encountering the Planning Model for the first time. Assumed Context of Hypothetical Session A developer has proposed a new subdivision near Crested Butte and has applied to the County for a permit. The proposed water supply for the development includes some projected yield to a new direct-flow water right on the East River. As a routine part of its review, the Planning Commission compares such projections to the results of a simulation using the Gunnison River Basin Planning Model. For this purpose, the Commission has developed a standard planning scenario, which includes assumptions about the administration of water rights, the operations of the Aspinall Unit, and the "build-out" water requirements for other approved developments. The Commission has also defined synthetic hydrology and reservoir starting contents for a dry year and an average year. To assure that their review is made in a consistent manner, the Commission has defined a standard set of impacts that are to be considered and corresponding outputs that are to be generated from the model run. As part of his application, the developer has supplied monthly water requirements data and return flow factors for each phase of the proposed development. The assignment for the Planning Commission's staff member is to quantify the "availability" of water to the proposed development under an assumed "junior-to-everyone" water right using the Commission's standard scenario. Model Capabilities and Limitations to be Illustrated by this Session 2. The addition of a new diversion to create a new scenario is the primary operation illustrated by this scenario. 1. The general style of user-model interaction, e.g. whether through flexible, low-level file manipulation utilities or high-level structured activity options. I ;,1 ';1 'I I q Things to Think About 2. The necessary properties of "baselines" and "scenarios;" how one is built from another; what it should be possible to "save." { :' _., -,.J~ ~,. "." ~-""'_.. i: J L. dL~o<~--_" ~_,~~~