WSP00452 - Laserfiche WebLink

Home Browse Search

e . e ,..-- "'1:9 ..l)~."".t-': Functional Specification for the Planning Model On the North Fork, it is anticipated that six inflow data files will be developed representing the following: I) virgin inflow to Overland Reservoir, 2) virgin inflow to Paonia Reservoir, except for operations of Overland Reservoir and Canal, 3) historical (depleted) reach gains between Paonia Reservoir and the Fire Mountain Canal, 4) virgin reach gains below Fire Mountain Canal and above the confluence of Minnesota Creek,S) virgin flow in Leroux Creek above the highest diversion, and 6) historical (depleted) reach gains between the confluence of Minnesota Creek and the confluence with the Gunnison River, including lower Leroux Creek. For the Smith Fork and Crystal Creek, it is anticipated that five inflow data files will be developed representing the following: I) historical (depleted) inflows at the Smith Fork Feeder Canal headgate, 2) virgin inflows below the Feeder Canal and above the confluence with the Gunnison River, 3) virgin flow in Crystal Creek at the Fruitland Ditch headgate, 4) virgin inflows to Gould Reservoir, and 5) virgin inflows to Crawford Reservoir, exclusive of the area tributary to Gould Reservoir. THE PLANNING MODEL'S USER INTERFACE The preceding sections of this Specification have described aspects of the real-world river basin system which will be represented in the computer model. The infonnation and relationships that are represented in the model establish absolute limits upon the accuracy, detail and meaning of the data that could theoretically be produced by the model. This section describes the model's "user interface." This tenn refers to the interaction between the human user and the computer program. For purposes of the Functional Specification, the "user interface" refers to that part of the computer program which determines what the use.r can see on the screen while the program is running and which provides means for the user to control the model, input data to it and obtain results from it. Thus, the user interface defines the set of actions and the kinds of infonnation which are available to a user and detennines how easy it is to use the model. This section contains, first, a review of the context or "planning process" within which the model will be used. Then a general discussion of the design objectives for the user interface is given. Finally, the areas of activity which will be supported by the user interface and particular features of the interface are discussed. The Planning Process The Gunnison River Basin Planning Model is intended to be used by a broad spectrum of organizations and governmental agencies with widely varying interests in the water resources of the Gunnison Basin. Individual users of the Planning Model will want flexibility to focus their studies upon particular regions and narrowly-defined interests. In the case of issues which affect more than one user. however, the planning process may involve communication between model users and comparison of results. All users will, therefore, want uniformity in the manner in which basiC elements of planning scenarios can be specified and modified. It will be important for users of the Model to be able to exchange and operate scenarios and to ascertain the assumptions upon which a scenario is based. The central water resource issues which motivate the development of the planning model involve the operations of large-scale projects and the basin-wide administration of water rights. Although the model may be used by individual organizations with interests in specific kinds of impacts, the planning problems for which the model is suited will still be related to the basin- wide scope of the central problems for which the model was designed. ! I I 15 """ 1i.,_"-~L _= -;b",1! " ~- .