|
<br />Integrating Derived Water Rights, RTi will integrate the data for the three Derived Water
<br />Rights tables called Transactions, Net Amounts, and Aug_wr, The State will provide
<br />these tables to the RTi in a stand-alone fashion, (Meaning that they are not directly
<br />related to any other table in the HB - CRDSS database,) It is RTi's responsibility to use
<br />the Alternate Keys defined in Exhibit I (WD+ID), to build a relationship between the
<br />main Structure table by back filling the foreign key (structure_num),
<br />
<br />Testing, As tables are populated, RTi will verify the integrity of the relationships among
<br />the tables, and the conversion of data into the tables, The results of the table population
<br />will be checked for errors and for records that that did not load, Data that does not load
<br />will be inspected by R Ti and reported to the State, R Ti will account for all data during
<br />the loading sequence by insuring the same number of records contained in the Dbase file
<br />equal the number populated in HB - CRDSS or returned for checking, RTi will spot-
<br />check against the original data source (Dbase) to ensure that the values are correct and are
<br />associated with the correct key identifiers,
<br />
<br />Error Handling, RTi is not responsible for correcting bad data. Whenever bad data is
<br />encountered, an error log will be submitted to the State in a format convenient to RTi
<br />which allows the State to identify the bad data (e,g, ID xxxx did not load) and understand
<br />why it did not load (e,g, a character entry was found in a real field), To reduce the effort
<br />associated with resolving data errors and re-populating data, RTi will, based on
<br />experience with the CRDS S Phase II contract, identify all errors in a data file before
<br />submitting an error log to the State, If these data are corrected by the State and delivered
<br />to RTi 4 weeks prior to the end of this contract or a mutually agreed upon extension, RTi
<br />will re-populate the records for that particular Water District. If corrected data are not
<br />delivered to RTi 4 weeks prior to the end of this contract or a mutually agreed upon
<br />extension, the State will re-populate the records for that particular Water District or
<br />negotiate a change order as part of Task R9, Contingency, If there are minor changes that
<br />are made by RTi after approval by the State, afixed log will be provided to the State,
<br />
<br />Error Handling Costs R Ti' s monthly progress reports will document the cost associated
<br />with repopulating bad data provided by the State, This task assumes twenty (20) percent
<br />of the budget for this task as presented in the Cost Worksheet, Exhibit C, will be adequate
<br />for repopulating bad DWR data, IfRTi's monthly progress reports indicate 20 % of the
<br />budget was inadequate to repopulate bad data, the State will negotiate a change order as
<br />part of Task R9, Contingency, IfRTi's monthly progress reports indicate less than 20 %
<br />of the budget was required, the State will authorize any remaining funds for transfer to
<br />Task R9, Contingency,
<br />
<br />Documentation R Ti will document the results of this task for inclusion as a new section
<br />in the Developers Manual.
<br />
<br />Deliverables
<br />RTi will provide:
<br />L A populated HB - CRDSS database with DWR data, This includes DWR's
<br />streamflow, irrigated acreage, stream, structures (headgates, reservoirs, small dams,
<br />
<br />Scope of Work, HB - CROSS, 1130/97
<br />
<br />0873
<br />
<br />6
<br />
|