Laserfiche WebLink
<br />cards when sc~ng is complete. The scanned image "nfes shall be given filenames <using <br />information punched onto the cards. The initial contract budget is based on scanning of <br />4,000 cards. <br /> <br />2.2 Verify that each modeled pipe segment appears in the appropriate scanned image file. <br />Create a database that associates each modeled pipe segment (via the MS link numbers) <br />with the image filename. Create an exception report listing the pipe segments which do not <br />appear on the plans referenced on the atlas maps. City staff shall be responsible for <br />investigating these exceptions and providing the correct cards for scanning. If the City <br />cannot find the appropriate cards, they shall instruct the Consultant as to how to proceed <br />(e.g., use information shown on atlas maps, interpolate elevations, survey the elevations, <br />etc.) <br /> <br />2.3 Develop a procedure to create a database for manhole rim and invert elevations (for <br />upstream and downstream pipes), recognizing that datum inconsistencies are present <br />throughout the source maps and drawings. The procedure shall include extracting <br />elevations from the scanned plans and other data sources as well as surveying of elevations <br />at selected manholes. The procedure shall also describe the methods to be used in the <br />manhole surveys and the format of the data to be provided by the surveyor. The final <br />product of the procedure shall consist of manhole rim and invert elevations adjusted to the <br />current NA VD 1988 datum. Document the proposed procedure in a technical <br />memorandum for City review and approval. Finalize the procedure based on City <br />comments. <br /> <br />2.4 Implement the approved procedure to create a database of manhole rim and invert <br />elevations for all 1800 modeled manholes. The initial contract budget provides for 400 <br />manholes to be surveyed in the field with rim and invert elevations collected. Surveyed <br />elevations shall be measured to plus or minus 0,05 feet. During the surveys, pipe material <br />and size shall also be recorded from the surface and checked against record drawings. The <br />database shall include fields that document the elevations from the atlas maps, from the <br />plans (where available), and from surveys (when performed). The elevation source used <br />and the adjustment shall also be recorded as separate entities in the database. Populate the <br />database tables associated with the City's Microstation design file for the modeled <br />manholes and pipes. The City shall provide the tables with the following fields already <br />populated: manhole and pipe identifiers and MS link numbers, and upstream and <br />downstream manhole identifiers for each pipe. Consultant shall populate the following <br />fields for manholes: rim elevation, invert elevation, plan number, and year built. For pipes, <br />Consultant shall populate the following fields: diameter, length, slope, upstream and <br />downstream invert elevations, year built, pipe material, and plan number. This information <br />shall be obtained from the best available source. In order or priority, those sources are <br />surveys (where performed), scanned plans, and atlas maps. Consultant shall validate the <br />data using a series of automated quality checks, correct errors identified in the validation <br />using available information, and provide the city with the populated database and a list of <br />how each discrepancy was resolved (e.g., conflicting data from different sources, reversed <br />pipe direction, etc.). lfthe City wishes to change the data related to these specific <br />discrepancies, they shall provide the Consultant with the changes, and the Consultant shall <br />input the changes to the database. <br /> <br />cs 387 FORM: C:\DOCUME-I\cleeshaw\tOCALS-IITcmp\AgrtaTlml Package for city Attorney_.doc <br />