|
<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 RTi and reported to the State, RTi 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 - CROSS 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,. c';i1111 ...-1::
<br />
<br />Error Handling, RTi is not, responsible for correcting bad data, w~e~_ev~ta is
<br />encountered, an error log wIll be submItted to the State III a formJt~t to Rt! whIch
<br />allows the State to understand why the data did not load and t~1 track the bad data, If ~
<br />these data are corrected by the State and delivered to RTi 4 wee~ prior to the end of this
<br />contract, R Ti will re-populate the records for that particular W'}ter District. If corrected
<br />data are not delivered to Rti 4 weeks prior to the end of this cbntract, the State will re-
<br />populate the records for that particular Water District or negot\~te a change order as part
<br />of Task R9, Contingency, If there are minor changes that are made by RTi after approval
<br />"by the State, ajixed log will be provided to the State,
<br />
<br />RTi will document the results ofthis task for inclusion as a new section in the Developers t:;I
<br />M I j "J"" k
<br />anua , ' \. 1 M' t ,. .- I
<br />- .,.,;, 5{.r ~ "".....1 ""r
<br />J' 11- d''''''_
<br />De/iverables co >.>- ,. ,i 01/>> U "". ~,
<br />RTi will provide: ,,,.~,fv ~ lu'
<br />1. A populated HB - CROSS database with DWR data, This includes DWR's
<br />streamflow, irrigated acreage, stream, structures (headgates, reservoirs, small dams,
<br />jurisdictional dams), diversions (daily, monthly, annual time series), diversion
<br />comments, and derived water rights (transactions, net amounts, aug_ wr),
<br />2, All routines, programs, and/or scripts used to perform the population, These routines
<br />should be sufficient for an experienced database administrator to redo the conversion,
<br />beginning with source (typically Dbase) files and ending with a populated Informix
<br />database, The objective is to allow the conversion to be reproduced in a "delete and
<br />re-build" fashion,
<br />3, An error log of all records that could not be loaded, Confirmation through Email or
<br />progress reports that revised records provided to Rti by the State up to 4 weeks prior
<br />to the end of this contract have been loaded,
<br />4, Ajixed log of all records that were fixed,
<br />5, A draft section of the Developers Manual which describes the population of HB -
<br />CROSS database with DWR data, This section, which may be called DWR Data
<br />Population, is expected to contain approximately IO pages of text and will include the
<br />results of the relationship and constraint checking, the population verification, the
<br />accounting ofrecords, and the spot-checks,
<br />6, Incorporate State comments,
<br />
<br />Scope ofWark, HB ~ CRDSS, 12/20/96
<br />
<br />0, \.<0
<br />~-
<br />
<br />6
<br />
|