My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP07134
CWCB
>
Water Supply Protection
>
Backfile
>
7001-8000
>
WSP07134
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:25:53 PM
Creation date
10/12/2006 2:06:25 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Decision Support System - CRDSS
State
CO
Basin
Colorado Mainstem
Water Division
5
Date
1/1/1993
Author
Dames and Moore
Title
Feasibility Study Report for a Colorado River Decision Support System
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.
/
188
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 /> <br />e <br /> <br />e <br /> <br />on3T!"22 <br /> <br />and system architectures necessary to support these needs, <br /> <br />The study comprised ten specific tasks, the results of which are presented in <br />detail in the main text and appendices of this report. In summary. the ten tasks <br />achieved the following: <br /> <br />. <br /> <br />Needs analysis - Twelve categories of water management needs <br />were identified through meetings with water users. Within these <br />twelve categories, a total of 99 questions were identified <br />representing decisions faced by water users, which the CRDSS <br />could help to address. Extended meetings with CWCB and DWR <br />staff' d'eveibped three specific problem scenarios; considered' as <br />representative and sufficient for use as "problem" statements which <br />the CRDSS should be capable of addressing, <br /> <br />Evaluation of models . Nine classes of models were identified <br />which address the components of the problem scenarios; existing <br />models were inventoried and ranked in terms of how well they <br />matched the functional specifications. Functions for which new <br />models need to be developed were also identified. <br /> <br />Data requirements. Based on the data needs generated by the <br />scenarios and the requirements of the models. 100 specific types of <br />data that need to be input to the DSS were identified and <br />characterized in terms of their sources and the scenarios to which <br />they apply, <br /> <br />Alternative user interfaces - Based on a wide range of potential <br />users having a variety of information needs, levels of sophistication <br />and available hardware, alternative methods of interacting with the <br />user were explored. Three interfaces were evaluated for their <br />effectiveness in performing four basic reporting requirements. The <br />use of "fill in the blanks" form based screen and the more <br />sophisticated interactive color graphics were well suited to these <br />purposes. Provision of services to the users was reviewed in both <br />cenrralized and disuibuted systems. <br /> <br />Alternative architectures. The internal organization of the system <br />was then reviewed to determine the most effective way to provide <br />the functionality to the users via the two preferred interfaces, Five <br />approaches were investigated with an objective of 1) keeping the <br />data separate from models to allow for widespread accessibility and <br />2) to srructure the system to allow for easy extension of additional <br />application models. Two approaches performed user needs well: <br />data centered systems and dedicated systems. Of these two. the data <br />centered approach was functional under both a cenrralized and <br />distributed approach to delivering service to users. <br /> <br />Estimated costs - Six major components were analyzed in <br />estimating costs to implement the CRDSS. The twO major costs. the <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />DAMES&MOORE/CADSWES-4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.