My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC06848
CWCB
>
Water Supply Protection
>
Backfile
>
19000-19999
>
WSPC06848
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 9:40:16 PM
Creation date
10/9/2006 6:06:22 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System-Ray
State
CO
Water Division
5
Date
2/17/1994
Title
PRYSH-Requirements for a Colorado River Policy and Planning Model to Replace the CRSS-Draft
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
56
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />000201 <br /> <br />1 <br /> <br />Introduction <br /> <br />The Colorado River Simulation System (CRSS) is a water resources management tool developed <br />specifically for the Colorado River Basin, CRSS consists of four major components: a historical <br />hydrologic database and processing program (MHYDRO), a projected water demand database <br />and processing program (SMDID), a simulation model (CRSM), and an output processing <br />program (TAPEDIT). The system is used as a long-range planning tool to assess the effects of <br />various operational strategies, basin development plans, and water usage plans. The model runs <br />on a monthly time step for typical time horizons of 50 - 70 years and tracks the quantity of water <br />throughout the system and the quality of the water with respect to salinity. A unique feature of <br />CRSM is that the simulation incorporates operational criteria that have been established to satisfy <br />certain legislative requirements. A major drawback is that these requirements or rules are "hard- <br />wired" in the Fortran, making analysis of alternative criteria very difficult. Furthermore, the <br />methods used in the model (to compute hydroelectric generation, sedimentation accumulation, <br />salinity concentrations, etc.) are "hard-wired", CRSS is also difficult to use as all user-specified <br />changes must be entered in a card image format. <br /> <br />The Upper and Lower Colorado Regions of the Bureau of Reclamation have embarked on a two- <br />year program to complete the development of a decision support system (DSS) for water resource <br />management (Reference I). The program goal is the development of a general-purpose <br />modeling framework for the Colorado and other river basins, A major objective of the program <br />is the replacement of the CRSS with a model that will allow the user direct access to the rules <br />without the need to recompile the code, The new model will also provide a graphical user <br />interface (Gill) to facilitate model building and editing, input data editing, as well as output data <br />analysis, This document specifies the requirements that must be met to satisfy this objective, <br /> <br />The new CRSS will be developed by the Bureau of Reclamation and the University of Colorado <br />Center for Advanced Decision Support for Water and Environmental Systems (CADSWES). The <br />work will be based on the general-purpose modeling framework (PRSYM), currently being <br />developed at CADSWES for the Electric Power Research Institute (EPRI), the Tennessee Valley <br />Authority (TVA), and the Bureau of Reclamation (References 1 and 4). <br /> <br />In this document, we outline the functional requirements for the simulation model and the data <br />that are required to make a simulation run. We then discuss needs for analysis tools and our <br />plans for verification and validation of the new model. In Appendix A, we present the reservoir <br />and powerplant data for the Colorado River System. The operating rules that the current CRSS <br />uses are given in Appendix B. <br /> <br />We view these requirements as the minimal requirements to replace the current CRSS. We <br />reserve Appendix C for specification of new methods and operating rules that will need to be <br />represented, and Appendix D to specify example problem and test scenarios that the user <br />community will want to solve with the new model. These scenarios will be used in the iterative <br />design and development process to ensure a product that will meet the users' needs and also for <br /> <br />3 <br /> <br />DRAFT: February 17. 1994 <br />
The URL can be used to link to this page
Your browser does not support the video tag.