Laserfiche WebLink
Physical Characteristics Database <br />The physical characteristics data collected during Phase I will be checked for reasonableness. In <br />cases where more than one source of data is identified, RTi will determine the primary source. RTi <br />will maintain a notebook for each reservoir, containing the reservoir's physical characteristics. The <br />use of these data in the modeling tasks will provide additional quality control. <br />Historical Database <br />Historical data collected during Phase I will be subject to QA/QC procedures including range <br />checking, computation of annual/monthly means and standard deviations, and statistical and double- <br />mass analysis to check for consistency. RTi has developed data analysis utilities to assist in the <br />statistical data evaluation. In some cases, simple water balances will be used to verify the <br />reasonableness of the data. The use of historical data in the modeling tasks will provide additional <br />quality assurance. <br />User Database <br />QA/QC procedures will be limited to verifying that user information is loaded properly into the <br />CRDSS user database. <br />Station Database <br />QA/QC procedures will be limited to verifying that station index information for different data sets <br />is loaded properly into the CRDSS station database. <br />Water Rights Planning and Consumptive Use Models <br />Water rights data will be checked as outlined in Task 1.03. Water rights data will be provided by the <br />State, and it is assumed that these data will have already been subject to QA/QC. <br />Both the water rights planning and consumptive use models will undergo validation and verification <br />to ensure that the results from the CRDSS are accurate and reliable. Model results will be compared <br />to previous work or accepted values. In the case of the consumptive use model, results will be <br />compared to the USBR Consumptive Uses and Losses Report. In the case of the water rights <br />planning model, the results will be compared to other modeling work. The results from baseline runs <br />will be stored for use in model validation and verification at different stages of software <br />development. Incremental changes to the models will be compared to the baseline runs to ensure <br />each change produces reasonable results. <br />Software <br />Software that is part of the CRDSS will undergo prototype cycles involving redesign and <br />corresponding recoding and implementation. Different CRDSS products will have prototype cycles <br />of varying length, depending on the complexity of the product and its dependence on other CRDSS <br />components. Stable product prototypes will periodically be installed on the Briefing Room machine <br />for evaluation by State personnel and interested users. A detailed description of the prototyping <br />cycle is described in Task Memorandum 1.05-22. <br />2 <br />A275 05.10.94 1.05-4 Ritsch, Day <br />