Laserfiche WebLink
Ease of Understanding . The fundamental logic of HYDROSS is straightforward and relatively easy <br />to understand, as are the basic input and data requirements. The existing model documentation is <br />very good, with detailed descriptions of the model logic, the variables, file structures, error <br />messages, etc. The HYDROSS documentation is continually updated, with specific reference to <br />model enhancements and modifications that occur with new versions. The source code itself is very <br />well documented, greatly improving the understanding of the model operations. <br />Development for the CRDSS and Future Maintenance . HYDROSS is fully supported by the USBR, <br />and future modifications and enhancements can be expected. Presently, it is our understanding that <br />there is a one-time license fee for the workstation version of HYDROSS ($3,500) and annual <br />maintenance and updates are available for an annual cost of $3,000. It is not known whether the <br />USBR would waive these fees for the State, if the model were selected for the CRDSS. <br />Level One Decision Criteria <br />Availability of Model Code . There is an unresolved question about whether the internal source code <br />for HYDROSS would be available to the State for use in the CRDSS or what terms and conditions <br />would be attached to a licensing agreement. As with any model developer, the USBR is sensitive to <br />allowing a user to change and/or modify the source code because of potential errors that might be <br />introduced. However, it is our opinion that the USBR would likely consider some form of license <br />agreement with the State that would protect the reputation of the USBR. Use of the source code by <br />third parties beyond the State would also require some form of agreement with the USBR. There are <br />no restrictions on obtaining executable versions of HYDROSS, complete with documentation and the <br />availability of updates. HYDROSS is fully supported by the USBR. <br />Model Functionality . HYDROSS appears to address most of the issues of functionality for the <br />CRDSS objectives. Notable exceptions include the difficulty to model multiple accounts and <br />ownerships within a reservoir and the inability to address water right exchanges. Another significant <br />concern relates to the need to generate pristine virgin flows external to operation of the model. <br />Development of these data or adoption of the existing CRDSS virgin flow database could require <br />additional effort by the CRDSS Project Team. There is also a concern about the basic HYDROSS <br />logic as it relates to the distinction between natural and project flows and diversions. It could prove <br />to be difficult to override this underlying feature of the model when developing specific applications <br />for the CRDSS. <br />Past Applications . HYDROSS is widely used by the USBR an d other federal agencies, including the <br />FWS. It has a proven track record and is expected to continue to be used as a water rights planning <br />tool by the federal agencies. There do not appear to be extensive applications by state or private <br />interests. <br />Documentation . The documentation for HYDROSS is very good, with detailed descriptions of the <br />model logic, variables, data files, and error messages. The documentation is continually updated as <br />modifications or enhancements to the model are made. <br />Level Two Decision Criteria <br />The HYDROSS model was evaluated against the Level Two decision criteria. Many of these criteria <br />are subjective by nature, and the review was intended primarily to identify any other attributes and/or <br />4 <br />A275 05.10.94 1.15-4 Fosha, Hyre <br />