Laserfiche WebLink
<br />tl <br /> <br />". <br />. <br /> <br />authorized prior to any work being performed, The names of all entities and <br />attributes and relationships between entities will remain the same as the names and <br />relationships in the approved design, <br />· The data received by the RTi will be assumed to have been subjected to quality <br />assurance procedures by the State, If a record of data contains errors, (for example, <br />they do not contain unique 10' s, or contain duplicate records, or nulls in key and <br />constrained fields), it will not be converted, A list of the erroneous records will be <br />sent to the State for correction, RTi is are not responsible for correcting data errors, <br />· If the State provides corrected data 4 weeks prior to the completion of this project, the <br />RTi will re-convert all of the records for that particular Water District. <br />· Data for the station and cu model will be loaded from the current CRDSS database, <br />into HB-CRDSS (Exhibit 1), <br />· DWR data for the HB-CRDSS design (Exhibit 1) will be loaded from the most <br />current DWR Dbase databases (the anticipated freeze date for these files is 6/30/96), <br />These include irrigated acreage, streamflow and the following Dbase files: Snn, Snna, <br />Snnm, Dnna, Dnni, Dnnc, Dnnd, Pond, Dam, Rnnf, Rnny, <br />· Serial number assignment between the HB-CRDSS and current CRDSS databases <br />will not be the same, <br />· Development of this database will be performed on a development dbspace that is not <br />being used for production <br /> <br />()92~ <br /> <br />Scope ofWark, HB - CROSS, 12/11/96 <br /> <br />11 <br />