Specifications include, but are not limited to: 2.3. SCOPE OF WORK The Contractor shall provide automated pavement condition data collection services (collection, processing, analyses, quality control & assurance and reporting) for the City’s road network and parking lots to support short and long term planning objectives and decisions. The Offeror must include in its proposal a description of data collection technology, standard collection protocols and data quality management of the data acquisition vehicles used for the automated pavement survey. The Offeror must propose the methods and technology they intend to use to capture the data and ensure its spatial accuracy. The anticipated scope of work is detailed in the tasks below. Offerors shall list in their proposal additional tasks, if any, needed to complete the work that are not included below. 2.4. TASK 1 – PROJECT INITIATION A. Project Kick-off Meeting Upon signing of the Agreement, the Contractor will arrange a project kick-off meeting. During the meeting, the Contractor will present the proposed project approach, including but not limited to: project team, project equipment, software, methodology, schedules and deliverables. B. Route Planning i. The Contractor must prepare data collection maps and routes, based on existing centerline data to be provided by the City, for the pavement condition survey and provide the City with the proposed data collection route maps (.pdf and ArcGIS file geodatabase) confirming the data collection requirements for each pavement segment. ii. Data must be collected in two directions (two passes) except for one-way streets. On multi-lane roadways (including one-way streets), data must be collected on all lanes and the average score reported for the segment. iii. When a roadway is separated by a median creating two distinct roadways, each side will be treated as its own road segment. Each driving direction must have its own PCI, IRI and rut depth value. iv. The Contractor m
