Laserfiche WebLink
<br />'-"Jork Tasks: <br />TASK 6,1. IDENTIFY ELEMENTS TO BE INCLUDED IN THE CITY'S MODEL <br /> <br />WY A will work closely with the City's staff to develop working maps of proposed modeled pipelines and <br />nodes. The model will include all distribution system pipelines, to preserve a one-to-one correspondence <br />with the GIS, and to facilitate future model updates. WY A will work with City staff to identify those <br />pipelines and specific areas of the City's water system which require special attention. WY A will also <br />work closely with City staff to develop a nodal and pipeline naming convention which will meet both <br />existing and future needs, and to build a model that exchanges new information easily with the City's GIS. <br /> <br />TASK 6.2, IMPORT WATER SYSTEM SHAPEFILE INTO HYDRAULIC MODEL <br /> <br />After the nodal and pipeline naming conventions are established, WY A will work with City staff to <br />generate a shapefile of City's water distribution system facilities (pump stations, tanks, wells and control <br />valves) and pipeline infrastructure. WY A and City staff will also confirm and update any pipelines and/or <br />facilities that have not have been included in the GIS database. WY A will populate the elevation database <br />using U.S.G.S. digital elevation maps (DEM), which will allow WYA to directly extract attribute data <br />from the elevation contour shapefiles of the City and allocate them to their corresponding junction in the <br />model. If required, the model elevations will be converted to North American Vertical Datum, 1988. <br /> <br />As part of this task, WY A will also confirm whether the translation of the network from the GIS <br />geodatabase into the recommended software is complete and accurate. WY A will utilize software tools to <br />check that the network is correctly constructed, and to identify and automatically correct any network <br />topology problems (e.g., disconnected nodes) and data flaws (e.g., duplicated pipes or nodes) that may <br />have arisen from the original model development. These software tools will be used to identify: <br />overlapping or duplicate nodes, pipe-split candidates, crossing or intersecting pipes, orphan pipes, <br />duplicate pipes, disconnected nodes. WY A will utilize these tools to confirm that the model topology is <br />consistent with the City's existing system map files. <br /> <br />TASK 6.3, DEVELOP AND ALLOCATE EXISTING DEMANDS INTO HYDRAULIC MODEL <br /> <br />The City currently has existing meter/consumption data coupled to service address and a revenue class <br />designation. Although consumption data also includes unique meter identifiers, these meter identifiers are <br />not consistent with meter identifiers used in GIS. Therefore, service address will be used to geocode <br />meter/consumption data to a GIS-based street map of the City's water service area. <br /> <br />WY A will use this data, in conjunction with a special GIS street file map, to produce a meter/consumption <br />GIS file containing the City's existing water demands and revenue class designation. WY A will review <br />data that cannot be geo-coded to determine and correct obvious errors (misspelled street names, etc.). For <br />other missing data, WY A will use a variety of techniques to determine whether the demands can be <br />assigned. WY A will also request City assistance in resolving data discrepancies between billing data and <br />GIS street files. WY A will provide billing database corrections to the City for its future use. <br /> <br />Once the meter/consumption GIS file of the City's existing water demands is developed, WY A <br />will then use the modeling software's allocation module to automatically allocate <br />meter/consumption data to individual junctions in the hydraulic model. The allocation module <br />determines the demand at each junction by identifying and summing all the meter/consumption <br />data located within an associated service area. The meter/consumption data will be allocated to <br /> <br />October 22, 2009 <br /> <br />7 <br />