6-02. Attachment B- Scope of Work.docx

ATTACHMENT B

SCOPE OF WORK

MEASURING RETROREFLECTIVITY OF PAVEMENT MARKING MATERIALS USING A MOBILE RETROREFLECTIVITY UNIT (MRU)

Scope of Work Page 2 of 2

1. SCOPE

The Utah Department of Transportation (UDOT) Maintenance Group is responsible for maintaining statewide pavement markings. The purpose of this contract is to select a qualified vendor to collect Retroreflectivity data of durable pavement marking materials Using a Mobile Retroreflectivity Unit (MRU) on edge lines and the adjacent lane lines of a selected route and mileposts provided by the Department. To gather the retroreflectivity data the contractor must operate the MRU, per manufactures recommended data collection speed and up to posted roadway speeds at a prescribed geometry. The prescribed geometry corresponds to the European Committee for Standardization (CEN) geometry and is the standard geometry adopted by ASTM E 1710.

1.1 The contract duration is for one year with the option to renew for up to five years.

1.2 This test method applies to the measurement of the pavement marking retroreflectivity using mobile instruments to ensure that night-time visibility is adequate.

1.3 This test method does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the contractor to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

1.4 The contractor is required to provide UDOT with both wet and dry retroreflectivity (RL) as directed of existing pavement marking materials in an “as is" condition.

1.5 Any unexpected event (e.g., weather and equipment malfunction) that occurs during the execution of this contract must be reported to the Contract Manager.

2. REFERENCED DOCUMENTS

2.1 ASTM E 1710: Standard Test Method for Measurement of Retroreflective Pavement Marking Materials with CEN-Prescribed Geometry Using a Portable Retroreflectometer

2.2 ASTM D 7585/D7585M: Standard Specification for Pavement Marking Using Portable Hand-Operated Instruments

2.3 ASTM E 284: Terminology of Appearance

2.4 ASTM E 808: Practice for Describing Retroreflection

2.5 ASTM E1347: Standard Test Method for Color and Color-Difference Measurement by Tristimulus Colorimetry

2.6 ASTM E-2832: Standard Test Method for Measuring the Coefficient of Retroreflected Luminance of Pavement Markings in a Standard Condition of Continuous Wetting (RL-2)

3. ASTM E-2177: Standard Test Method for Measuring the Coefficient of Retroreflected Luminance (RL) of Pavement Markings Method in A Condition of Wet Recovery

4. DEFINITION OF TERMS

4.1 Definitions:

4.1.1 Coefficient of retroreflected luminance, RL – the ratio of the luminance of a projected surface to the normal illuminance at the surface on a plane normal to the incident light, expressed in millicandelas per square meter per lux (mcd/m2/lux).

4.1.2 Data Collection Unit - All equipment, personnel and software required to collect, and process measurements from a single vehicle.

4.1.3 Mobilization - All costs associated with the contract that is not covered in the quantified unit price list of deliverables.

4.1.4 Retroreflection – a reflection in which the reflected rays are returned preferentially in directions close to the opposite of the direction of the incident rays, this property being maintained over wide variations of the direction of the incident rays.

4.1.5 Collection will be done annually in the Fall or as directed by UDOT.

5. APPARATUS

5.1 The required field-testing apparatus consists of a vehicle equipped with the following devices:

5.1.1 Vehicle-mounted retroreflectometer.

5.1.1.1 The retroreflectometer must be capable of collecting data in accordance with the 30-meter geometry conforming to ASTM E 1710. See section 5.1 for more information regarding the 30-meter geometry.

5.1.1.2 The retroreflectometer must be capable of collecting pavement marking data at posted speed while accounting for horizontal wander and vertical changes of the host vehicle.

5.1.1.3 The retroreflectometer must be capable of measuring retroreflectivity of pavement markings.

5.1.1.4 The retroreflectometer(s) must be capable of being operated on either side of the host vehicle.

5.1.1.5 See Appendix A for specification for vehicle mounted mobile Retroreflectometer

5.1.2 A distance measuring device (DMI) using either a mechanical or a Global Positioning System (GPS) based system with accuracy requirements.

5.1.3 An operating system for data entry, acquisition, display, and storage.

6. SUMMARY OF TEST METHOD

6.1 Conduct measurements of retroreflected luminance using a MRU and the 30-meter geometry shown in Figure 1. The angles that are specified for the 30-meter geometry are as follows:

6.1.1 The entrance angle is fixed at 88.76° (co-entrance angle1.24°).

6.1.2 The observation angle is fixed at 1.05°.

Figure SEQ Figure \* ARABIC 1 Standard 30-meter geometry specified in ASTM E 1710

Figure 1. Standard 30 meter geometry specified in ASTM E 1710

6.2 Calibrate and meet all conditions of the approved QA/QC plan prior to data collection.

6.3 Retroreflectivity is measured with the MRU operating along the pavement marking survey section of a roadway.

7. PAVEMENT STRIPE NOMENCLATURE

7.1 A standard naming convention was developed to identify each pavement stripe regardless of the number of lanes. This contract will only measure the right shoulder edge line and the next proximate lane line. Table 1 shows an explanation of the nomenclature used.

7.2 The pavement stripe nomenclature includes the direction of travel followed by the stripe type as identified in Table 1 and figures 2, 3, and 4.

Table 1 - PAVEMENT STRIPE NOMENCLATURE

· = Negative direction is when the milepoint is decreasing in the direction of travel.

Stripe Types

LL

Lane Line (White Skip Line or Yellow Line). A lane line designated between the through movements a travel way starting with the one closest to the edge line

*Note: Direction is specified by the UDOT Route Directional Designation.

REL

REL

LL

LL

LL

REL

LL

REL

LL

REL

LL

REL

Figure 2. Pavement stripe nomenclature for a 2 lane roadway (dry continuous)

REL

REL

LL

Figure 3 Pavement stripe nomenclature for a 4-lane non-divided roadway (dry continuous)

REL

REL

LL

Figure 4 Pavement stripe nomenclature for a multi-lane divided roadway (dry continuous) Edge Lines (R/L) Lane Lines

Figure 5 Pavement stripe nomenclature for a multi-lane divided roadway (wet continuous / wet recovery)

8. DATA ACQUISITION, SUBMISSION AND REPORTING REQUIREMENTS

8.1 This contract includes one data collection annually in the Fall or as directed by UDOT.

8.2 Analyze acquisition frequency every 0.1-mile interval (unless recommended otherwise). Report in millicandelas per square meter per lux (mcd/m2/lux).

8.3 Compensate for changes in background retroreflectivity without influencing the reflectivity of the pavement marking.

8.4 The acquisition system must be capable of recording manual trigger event codes during the data collection process in order to mark roadway characteristics, such as bridges, intersections, pavement changes, etc.

8.5 Document the average retroreflectivity values from the retroreflectometer including GPS location of all the stripes being measured.

8.6 Collect the data for each line on each route continuously at manufactures recommended speed up to the posted roadway speeds with minimal vehicle wander. Note any unusual appearance of the striping line (e.g., debris, damaged line, etc.) during the survey.

8.7 Review and evaluate the quality of data prior to submission. Submit the data summarized at every 0.1 mile segment. Both the summary and the raw data files shall be in CSV files format. In addition to CSV format, summary data files must be submitted both as KML (Google Earth) and either Shapefile or File Geodatabase (Esri ArcGIS) format. See Appendix B for the data dictionary to be provided for this project.

9. QUALITY CONTROL/QUALITY ASSURANCE

9.1 Vendor is responsible for the accuracy and quality of the data.

9.2 Provide 3 copies of the proposed Quality Control/Quality Assurance Plan (QC/QA Plan) to be evaluated at selection.

9.3 The QC/QA Plan must include a minimum of the following:

9.3.1 Provide the following information for each recommended test:

9.3.1.1 Key item that is being checked.

9.3.1.2 Criteria required to be met.

9.3.1.3 Testing frequency.

9.3.1.4 Reporting method to be provided to the Department.

9.3.2 Tests to be included (additional can be added if deemed necessary by vendor):

9.3.2.1 Setup and visual inspection of all equipment. Verify that all equipment is secure, clean, and operational within required limits.

9.3.2.2 Calibration and verification of MRU. Verify daily that MRU readings are within ±5% of the calibration standard’s assigned value being used. Document calibration within the previous 12 months.

9.3.2.3 Background noise. Provide procedure for calibrating for background noise. Document that procedure has been implemented successfully in the previous 12 months.

9.3.2.4 Lateral and Longitudinal Dynamics of equipment. Provide documentation to show that MRU has been standardized by the manufacturer to account for alignment and wander, lateral wander, and longitudinal wander. Document calibration within the previous 12 months.

9.3.2.5 DMI and GPS distance and position. Provide documentation that equipment is accurate within ±5.280 feet (0.1%). Document calibration within the last 30 days. Recalibrate when tires are changed, rotated, or air has been added to the tires.

9.3.2.6 Precision tests including repeatability procedures.

· Identify a 0.5 mile roadway test segment for each Data Collection Unit for measurements to be collected.

· Document that information provided during the two measurements does not vary more than ±10.0% between measurements.

· Conduct precision tests prior to beginning any other roadway segments.

· Obtain handheld readings for the test segment.

· RL values measured using the MRU are comparable to those from conventional handheld retroreflectometers with RL values. The RL from the MRU shall be within ±15.0% of the handheld RL values.

· No additional payment will be paid for line miles measured for repeatability tests.

9.3.2.7 Reflectivity stability with speed. Document stability of MRU readings over the range of expected travel speeds.

9.3.2.8 Reflectivity stability with temperature. Document stability of MRU reading over the range of expected ambient temperature variations.

9.3.2.9 Operational Competency of equipment and personnel. Document the deliverable results for each Data Collection Unit. Factors to be considered include

· Proper use of event codes

· Driver competency (e.g. vehicle wander, route planning, etc.).

· Proper identification of stripe type, width, and color.

· Proper handling of MRU during acceleration, breaking, and stopping

9.4 Provide all forms, test documentation, certifications, records etc. outlined in the approved QC/QA Plan in accordance with the frequency agreed upon.

9.5 Re-test any segments that were found to be in error by the Department. No additional payment will be allowed for re-testing segments due to random checks by the Department.

10. INTERFERENCE AND ENVIRONMENTAL INFLUENCE

10.1 Avoid measurement during adverse environmental conditions including: Standing water, dew, sleet, and snow on the surface of the pavement marking or fog and smoke in the air, decreases the amount of retroreflected luminance.

10.2 Avoid measurement during adverse pavement conditions including: surface dirt, salt, debris, and contamination on the pavement marking.

10.3 Maintain internal temperature of MRU within ±2°C of 25°C. Take corrective actions per manufacturer guidelines if internal temperatures are not maintained. Report actions taken in accordance with the QC/QA Plan.

11. EVENT CODES

11.1 Use the standard nomenclature and data acquisition system event codes, as shown in Table 2. Record roadway events to the nearest thousandth of a mile. Except for triggered events, the data should remain in exact 1/10th mile increments.

11.2 Reset Data – When triggering a roadway event (pavement change, rumble, etc.) end the current row of data analysis to the nearest thousandth while beginning a new row of data analysis.

11.3 Hold Event – Hold the event code while continuing data analysis until the event is triggered a second time for roadway conditions (bridges, turn lane, construction, etc.).

Table 2 - Data Acquisition System Event Codes

DESCRIPTION*

RESET DATA

HOLD EVENT

*Note: These event codes are used to identify roadway characteristics within a pavement marking data collection section.

12. MINIMUM WORK PLAN REQUIREMENTS

12.1 Submit a brief plan for the routes that are planned for data collection prior to conducting the work include the following:

12.1.1 Route information (beginning/ending mileposts, roadway direction, stripe type, and other relevant information).

12.1.2 Work Schedule- Submit a detailed work schedule of the collection operation two weeks prior to beginning work. Update the schedule weekly as needed. Schedule includes routes, mile points, and dates. Notify the Department 24-48 hours prior to any deviation from the schedule.

12.1.3 Identification of the equipment, operators, and software used.

12.1.4 Include the following equipment information:

12.1.4.1 Manufacturer name and model used for the contracted work.

12.1.4.2 Brief description of the equipment.

12.1.4.3 Certification and calibration information.

12.1.5 List all personnel who will be working on the project. Include their titles, qualifications.

12.1.6 Identify the Project Manager with all contact information. The Project Manager will provide the following:

12.1.6.1 Responsible charge of the work

12.1.6.2 Review all measured and calculated data before submitting it to UDOT.

12.1.6.3 Have a working knowledge of data collection related to the roadway and an ability to recognize and address the various needs of the work.

12.2 Notify the Department of changes to personnel or equipment, if necessary, during collection. Update and resubmit the work plan when changes are required.

13. PAYMENT PROCEDURES

13.1 Compensation includes:

13.1.1 Unit Pricing as identified on the CONTRACTOR's bid

13.1.2 Mobilization allowed by the contract

Submit invoices to UDOT after the work is completed and accepted by UDOT. Include with invoice the following:

13.1.2.1 Contract number

13.1.2.2 Locations and date of the work that was performed by route and milepost

13.1.2.3 Itemized work items and quantity

13.1.2.4 Payment will be processed when UDOT has reviewed and approved all data collection included in the invoice. Payment will be provided based on the number of data collection completed on that invoice and will not be issued for data with errors until valid data is provided.

13.2 Mobilization:

13.2.1 Mobilization will be paid for each data collection session.

13.2.2 50% of Mobilization will be paid upon the following:

13.2.2.1 Vendor has mobilized to the worksite.

13.2.2.2 Vendor has submitted and the Department has approved the work plan.

13.2.2.3 Initial calibration and equipment information has been provided from the QC/QA Plan.

13.2.2.4 Submittal of approved invoice in accordance with this section.

13.2.3 The remaining 50% of Mobilization will be paid upon successful completion and acceptance of at least half of the measurement sites.

14. EXECUTION

14.1 Collect retroreflectivity data and associated proof of quality assurance information for roadway segments outlined in as provided in Appendix C. The lists in Appendix C include locations for dry continuous retroreflectivity, and wet continuous/wet recovery measurement methods. The Segment List in Appendix C may change from year to year per Department directive.

14.2 Data collection means, methods, and delivery formats must meet all specifications provided herein and as requested by the Department.

14.3 Provide one point of contact that will serve as the vendor’s project manager; UDOT will not coordinate with multiple offices, groups, or subcontractors.

14.4 Vendor is responsible for all project management, equipment, training, safety equipment, documentation of work, data processing, quality assurance documentation, transportation, and any other costs or materials required to deliver the specified data.

14.5 Damage to machines, weather, vandalism, or other circumstances of any kind resulting in data collection errors or invalid data the vendor is responsible to re-collect the segment. Additional payment will not be given to recollect lost data. If errors are discovered during data review the vendor will be required to re-collect the segments with no additional payment.

APPENDIX A:

Specification for Vehicle Mounted Mobile Retroreflectometer

1. Instrument shall detect, measure, and record the location of retroreflective road marking in the 30- meter geometry ASTM E1710.

2. Entrance Angle shall be 88.76° (per ASTM E1710)

3. Observation Angle shall be 1.05° (per ASTM E1710)

4. Measuring aspects of the total angular spread shall not exceed 0.33 degree

5. Operating Ambient Temperature Range shall be 0° to 120°F

6. Measurements shall be collected at a minimum of 400 measurements per second.

7. Longitudinal Resolution of Measurement, 3 inches or better at posted speeds. Resolution of the measurement shall be at least 18-bit

8. Instrument shall accurately measure skip lines (broken lines) without any correction factors

9. Devices shall be able to measure white and yellow, flat and profiled road markings of any type on flat and rough, dry surfaces. The device must compensate for the daylight and must continue to measure under different light conditions during the day and night.

10. Instrument shall give individual readings for both lines of a double line.

11. The system shall have a standard real-time display of retroreflectivity profile of measured markings.

12. The system shall have a built-in standard high precision Distance Measuring Instrument to tag data to the odometer.

13. GPS system shall report GPS coordinates with each measurement point

14. The system shall have a real-time event code, with programmable header labels so the operator can tag data as measurements are being collected.

15. Data file shall record and report the following values in a user-specified test distance (adjustable from 0.01 to 10 miles, but typically every 0.1 miles., or 10 to 10000 meters, but typically every 100 meters): Record number; Odometer reading; Date; Time; GPS Coordinates; GPS position fix accuracy; Vehicle Speed; Ambient Temperature; Ambient Humidity; Number of valid scans; average retroreflectivity, stripe width of left and right stripes individually, stripe type, event codes.

16. The instrument shall automatically generate color-coded Google Map Files (KML) with up to five (5) different colors representing five (5) different retroreflectivity intervals.

17. Calibration Standard shall have a traceable certificate from NIST and be ISO/IEC 17025 compliant.

18. Retroreflectometer shall be capable of being mounted to either side of a vehicle.

APPENDIX B:

Retroreflectivity Measurement Data Dictionary

RIGHT

TRUE

TRUE

Contractor's vehicle identifier

APPENDIX C:

Continuous Dry Retroreflectivity Measurement Data Collection Sites

Direc-tion

Total

1534.8

Wet Continuous / Wet Recovery Measurement Data Collection Sites

Direc-tion

*Note: Includes both the right and left edgelines and the first dashed line on the right, and the first dash line on the left see Figure 5 above.

APPENDIX D:

Pavement Marking Data Collection Segments Note: some short segments of non-durable marking are included in the Appendix C and Pricing Sheet totals as shown in the following maps. These short yellow segments are used to include continuity from durable marking installations to adjacent durable markings.

Figure 6: Statewide Retroreflective Segments

Figure 7: Region 1 Area Retroreflective Segments

Figure 8: Region 2 Area Retroreflective Segments

Figure 9: Region 3 Area Retroreflective Segments

APPENDIX E:

UDOT REGIONS

Region Three (Daggett, Duchesne, Juab, Uintah, Utah, and Wasatch counties) Region Four (Beaver, Carbon, Emery, Garfield, Grand, Iron, Kane, Millard, Piute, San Juan, Sanpete, Sevier, Washington, and Wayne counties) image1.jpg image2.jpeg image3.gif image4.png image5.png image6.png image7.png image8.png image9.png image10.jpg image100.png image11.jpg image12.jpg image13.jpg image14.jpg