Laserfiche WebLink
Understanding of Need /Scope of WorkIlt - <br />Distress types will be collected based upon actual surface conditions and physical characteristics <br />of the segment. Surveying methods will be conducted by remaining consistent with StreetSaver <br />& the Army Corp of Engineers sampling guidelines while being flexible to current City practices. <br />We will use the City's GIS centerline live in the field to <br />reduce survey times and project schedules. If the City �StreetSaver <br />has a recent high -resolution aerial (approx. 3") we will - <br />use this file during our field survey efforts to verify - <br />street measurements and other segment attributes. ry �:- , ,. <br />For all surveys, the use of our StreetSaver PMP-Tablet <br />units allows our staff to collect pavement data with the <br />City of Santa Ana's StreetSaver database live in the <br />field. Due to StreetSaver being acloud-based PIMP we <br />i <br />will be assessing our field crew's work daily/weekly at _ <br />our office to ensure quality control and management. ° <br />VI <br />Our MobileRater Tablet methodology sets us apart <br />from the competition since we are using a paper -less- <br />inventory process to enter data; we are also using the — — - — <br />City's street GIS layer live on our Tablets to expedite our surveys and GIS editing. <br />Roadway Verification Survey - A listing of the field attribute data that is updated/verified during <br />the survey for the pavement management database is listed below. Bucknam will obtain <br />measurements of each streets width, length and surface classification and compare it to existing <br />StreetSaver data. Discrepancies in the data will be tabulated and reviewed by Bucknam and the <br />City prior to any update within StreetSaver. <br />1. Field Attribute Data (updated and/or verified) <br />• From/to, indicating the assigned limits of the section, sample test areas, street <br />name, a street codification (arranged west to east and south to north) <br />• Street ranking indicating local, alley, arterial, collector, # of lanes, surface type <br />• Historical PCI tracking from previous inspections and 2021 PC] inspections <br />• Segment quantities, indicating the length, width, and total true area of the section <br />• Pavement distresses compliant with StreetSaver — OCTA guidelines (i.e. alligator <br />cracking, block cracking, rutting, long/trans cracking, weathering, etc. <br />• Provide City with "discrepancy report" indicating variances between field data <br />collection and previous PMP database <br />2. Conditional data will be evaluated for all street segments and will include: <br />StreetSaver 20 AC & 19 PCC distresses by type, severity and sample area <br />PC] ratings (0-100); per segment, per grid zone, per maintenance zone and citywide <br />Corrections / changes to the database shall not be made w/o prior City approval <br />3-4 <br />