|
<br />commissioner (primarily a database query, some (GIS, Water Resource Planning, and
<br />Consumptive Use) from an FTP site. Also, there is no intent to provide a GIS tool to
<br />other users, only GIS data.
<br />
<br />Data Storage(s) As presented in the above Table, three separate, dependent data storage
<br />locations are envisioned as part of CRDSS in order to meet user needs within the
<br />limitation of network communication speeds; Central Based Data, Division Based Data,
<br />and Water Commissioner or Other Based Data.
<br />
<br />The Central Data Server will contain HydroBase, the statewide relational database
<br />operating under Informix and other non relational graphically intensive information.
<br />HydroBase will contain official, DWR data such as water rights, diversions, well records,
<br />reservoirs, etc. In addition, HydroBase will contain real time streamflow measurements
<br />via' satellite monitoring stations, archived Water Administration Tool Worksheets, and
<br />the relational data required for the planning components of CRDSS such as historic
<br />streamflow, temperature, precipitation, snow pack, etc. Non relational data within the
<br />Central Based- Data, but not within HydroBase, includes official GIS coverage's, the
<br />Depletion Analysis Model and data, the Curtailment Analysis Model and data, the Point
<br />How Analysis Model, the Water Resource Planning model (StateMod) and data, and the
<br />Consumptive Use model (CRDSS-CU) and data.
<br />
<br />The Division Based Data or Other Users will contain the same non relational data and
<br />models as those in the Central Based Data because network speed is not expected to be
<br />adequate for applications that require large graphic images. Because the network speed is
<br />adequate for transfer of relational data, they will operate as a client to the Central Data
<br />Server. The Division office might have local copies in ACCESS of selected database
<br />tables for input, review, or performance purposes.
<br />
<br />Water Commissioner cannot use a client-server approach similar to the Division because
<br />of inadequate network speed. Therefore, they will have a local, relational database on
<br />their PC's operating under ACCESS. This local database is expected to mimic the
<br />HydroBase design to simplify maintenance. It will contain a subset, typically a single
<br />water district, of all data necessary to operate the Water Right Administration Tool off.
<br />line after refreshing real.time or archived information once a day. Note, if a water
<br />commissioner needs to perform a division wide evaluation such as a depletion analysis, a
<br />curtailment analysis, or a historical point flow analysis, they can connect to the Central
<br />Data Server.
<br />
<br />The three separate, dependent data storage locations described above are considered
<br />realistic, not optimal. Indeed with better communications, all information would be
<br />stored at a central site to minimize maintenance costs, hardware costs, software update
<br />procedures and data duplication. However, by designing within current network
<br />constraints, the system is expected to be extremely robust. For example, if performance
<br />at a Division office is considered inadequate, a local copy of relational data may be stored
<br />locally and the application would continue to work as designed. Similarly, if
<br />communication speeds to water commissioners increase in the future, they might not.need
<br />
<br />c:\w\crdss\scope\phlllb\scope.doc
<br />
<br />0'731
<br />
<br />4/24/97 - 3
<br />
|