Laserfiche WebLink
<br />Metropolitan Water Supply Investigation Proposal <br />Hydrosphere, Inc. <br /> <br />Septmber 17, 1993 <br />Page 53 <br /> <br />The level of detail to be incorporated in the Study model with regard to time step, <br />disaggregation of water rights, etc., will be commensurate with the Study's needs and the <br />anticipated role of Denver's modeling and planning study. It is anticipated that the MWSI <br />Project's model will provide a preliminary and exploratory modeling capability, and that <br />promising alternatives will be "proven out" through subsequent efforts by others, such as <br />Denver. <br /> <br />The specification will address various modeling requirements including geographic <br />coverage; level of disaggregation in representation of water rights, facilities, demands and <br />diversions; the ability to both separately track and "label" water rights and use and to allow for <br />shared and integrated operations of those features; etc. <br /> <br />Regardless of which path towards model development is selected, it is not anticipated <br />that an elaborate model user interface will be specified. The primary purpose of the MWSI <br />Project is to investigate system integration water supply options and not to develop a full <br />computer-based metro Denver water supply planning decision support system. However, the <br />model will ultimately be publicly available and thus an interface which allows easy input <br />modification and output viewing will be necessary. <br /> <br />The model specification process will involve two meetings with TSC to review I) an <br />initial model wish list, and 2) a draft model specification. <br /> <br />Linkages With Other Tasks <br /> <br />This task relies on all of the previous tasks, especially task 4, "Inventory of Existing <br />Information and Tools", and tasks 5-8, the special studies on the known integration <br />opportunities. The results of this task will provide the guidelines for Model Development in <br />Task 10. <br /> <br />Likely Sources of Information To Be Used <br /> <br />Documents produced in tasks 4 through 8 will be useful for this task, along with <br />considerable input from the TSC to specifically define ihe functional requirement of the model. <br />In addition, information provided by Denver relating to its on-going modeling effort will be <br />valuable. <br /> <br />Anticipated Problems <br /> <br />The model design will have to carefully balance the need for accurate, applicable <br />modeling results with a finite budget, short development period, and flexibility to model many <br />different options. Given these development constraints, an appropriate level of detail and <br />geographical scope will have to be selected. It is likely that some desired but not absolutely <br />necessary features will have to be left out of the functional specification. <br /> <br />Deliverables <br /> <br />A model jUncrional specification memo detailing model requirements including analytical <br />capabilities, user interface expectations, hardware operating requirements, and expected costs. <br />This memo will focus on what the model will be expected to do, not on the implementation <br />details. <br />