Laserfiche WebLink
J In addition to the need to simply locate <br /> r _ o-.Y, :M jr, �•t ,�: J ; ,mca�„ all the hydrants to link the test results , <br /> the local fire authorities wanted <br /> .. r-- detailed information about fire <br /> ",ren , hydrants such as the type of hydrant , <br /> Hri�« number of outlets , size of each outlet , <br /> and other information . Requests for <br /> hydrant information originating from <br /> °dM two sources-within EVMWD and from <br /> K. � <br /> local fire agencies-made the GIS staff <br /> decide that if was time for a fire <br /> hydrant inventory. <br /> A custom form was created for <br /> collecting hydrant data <br /> ... The solution proposed by the staff used a Sokkia GIR 1000 GPS unit, a Compaq IPAQ <br /> PocketPC , and ArcPad from ESRI . The existing fire hydrant database , street rights-of-way , <br /> street centerlines , and miscellaneous layers are be loaded on the IPAQ and set up in <br /> ArcPad . A custom form was created for the hydrants for data collection and update . For <br /> each hydrant , the data collector refers to the hydrant database , verifies the hydrant in the <br /> field , and inputs data into the form . A hydrant that does not show up in the database is <br /> located using GPS . At the end of the day, data is downloaded from the IPAQ and the GPS <br /> receiver. Points taken with the GPS are loaded in the Arclnfo database, and attribute <br /> information is loaded into a Microsoft SQL Server database . <br /> - A pilot area study is being used to refine this method . Based on the pilot area . EVMWD will <br /> calculate the time needed to complete the fire hydrant inventory for the entire district . Staff <br /> time will be allocated , and the data collection effort will go into full swing . The data that is <br /> collected will be linked to fire flow test data and will be accessible from the various GIS <br /> interfaces within the district. Having this information readily available will save the district time <br /> and money and ultimately benefit the ratepayers . <br /> KtGIS-Based Work Order Management <br /> A critical component of successful Public Works GIS implementations is accurate and <br /> complete data . Maintenance crews and other field personnel will go out into the field and <br /> make changes or additions to the infrastructure and not report these changes back to GIS <br /> staff . Very quickly GIS layers are missing pertinent data or contain erroneous data . Users will <br /> not know what data is accurate and what is not . Therefore , data sets can become suspect <br /> and staff may begin to doubt its usefulness and reliability. <br /> The solution to this problem is a GIS- based work order management system . A properly <br /> implemented work order management system would allow staff to quickly input specific <br /> information about a task and then print out a paper work order with an accompanying <br /> map . This map would show the infrastructure for the area of concern . Field crews would <br /> then mark any changes or additions to the system on the work order. Once the job was <br /> complete field crew would then return the work order with changes back to support staff for <br /> input into the work order management system and for update of appropriate data layers . <br /> An added benefit of such a system is continual fine-tuning and improvement of mapped <br /> ( GIS ) data . If any errors exist on the GIS maps, then field crew will mark and correct the error. <br /> 82 <br /> GIS Needs Assessment and Implementation Plan Chapter 1 - Departmental GIS Needs Assessment <br />