Laserfiche WebLink
<br />Exhibit A <br /> <br />Scope of Work <br />for <br />HydroBase - CRDSS Project <br /> <br />1.0 Introduction <br />The following introduction is provided to assist users and reviewers of this scope to <br />understand the activities to be performed in this scope and how those activities interact <br />with other related contracts, <br /> <br />Development This contract is one part of a four (4) step development of HydroBase with <br />data for the western slope (Water Divisions 4-7) as follows: <br />. Step I is the design of HydroBase, This step was performed by the State and has <br />been completed, Exhibit I is the design and is a major deliverable from this effort, <br />. Step 2 includes converting the Division of Water Resources (DWR) water rights data <br />into the HydroBase design, This task, described herein as the HydroBase - Water <br />Rights (HB- WR) project, is currently under development under a separate contract. <br />. Step 3, this contract, includes converting all DWR data except water rights into the <br />HydroBase design, In addition, environmental data currently available in CRDSS and <br />three Derived Water Rights tables (Transactions, Net_amounts, and Aug_wr) <br />produced by Step 2 will be included, The database produced by this step will be <br />named and described herein as the HydroBase - CRDSS (HB-CRDSS) project, <br />. Step 4 includes the merging of Step 2 (HB - WR) and Step 3 (HB - CRDSS) into <br />HydroBase, This activity will be performed by the State itself, Upon merging (serial <br />key synchronization) of the two development databases, this single database will <br />become the production version of HydroBase. As development progresses, other data <br />sets such as ground water will also be merged into this master database, <br /> <br />Data contained in both HB - WR and HB - CRDSS Because of the 4 step development <br />process, the HB - CRDSS Project will not contain all of the HydroBase Water Rights <br />tables, just the three Derived Water Rights tables (Transactions, Net_amounts, and <br />Aug_wr), These three tables will be stand-alone until the RTi uses the defined alternate <br />keys (WD+ID) to link these data with the HB - CRDSS main Structure table, and back <br />fill the foreign key (structure _ num) , This is a policy decision aimed at easing <br />development issues such as database serial key synchronization, and the scheduling of <br /> <br />Scope of Work, HB ~ CRDSS, 12/20/96 <br /> <br />0923 <br /> <br />I <br />