Attachment_11_-_Proposed_Form_of_Agreement_56A0889.pdf

PDF 3 MB Posted

Attached to
Retroreflectivity Data Collection
Solicitation number
56A0889
Issued by
California

About this file

This is a Proposed Form of Agreement document between the California Department of Transportation (Caltrans) and a contractor for retroreflectivity data collection services across Caltrans highway networks. The contractor shall collect, analyze, and report retroreflectivity data of pavement markings on both on-system (Caltrans-managed) and off-system highways across all 12 Caltrans districts covering approximately 85,556 stripe miles. The agreement commences on August 17, 2026 (estimated), or upon Caltrans approval, and expires on August 16, 2029, with the contractor required to survey all longitudinal markings once per year for three consecutive years. Data collection shall occur during standard working hours (Monday through Friday, 8:00 a.m. to 5:00 p.m. Pacific Standard Time), and final submittals are due within nine months from contract execution. The contractor must demonstrate a minimum of three years of experience in mobile retroreflectivity data collection with at least 250,000 cumulative stripe-miles collected and operate a minimum of four mobile retroreflectivity units (MRUs) during the performance period. Weekly and monthly progress reports shall be submitted to the Caltrans Contract Manager, with data uploaded to a web-based interface within seven days of field collection.

The agreement allows for amendments up to three additional years and $5,000,000 in additional work beyond the base contract term. Compensation shall be provided on a per-centerline-mile basis for asset collection, monthly rates for data hosting, hourly rates for on-call database support, per-training-session rates for required meetings, and data transfer fees, all according to the contractor's submitted Cost Sheet (Attachment 1). Caltrans shall retain 10 percent of each invoice until satisfactory completion of all work, and the total agreement amount is to be determined pending cost proposals. The contract includes Disabled Veteran Business Enterprise (DVBE) participation requirements and Small Business (SB) participation incentives, with contractors required to report utilization through the ADM-3059 form with each invoice. Insurance requirements include Commercial General Liability ($1,000,000 per occurrence/$2,000,000 aggregate), Automobile Liability ($1,000,000 combined single limit), Workers' Compensation with statutory limits and waiver of subrogation, and Professional Liability ($1,000,000). The contractor must comply with state data security requirements, provide 99 percent web-based interface uptime with unlimited concurrent access for Caltrans users, and furnish training to all 12 districts and up to 80 hours of technical support at Caltrans' discretion.

View the file

Other files

File Type Posted
E._Solicitation_Package_56A0889.pdf PDF
Attachment_1-Cost_Sheet_56A0889.xlsx XLSX spreadsheet

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

2. The term of this Agreement is:

Department of Transportation TBD Agreement Number 56A0889 Exhibit A

STATEMENT OF WORK

1. The work to be performed under this Agreement shall be in accordance with Exhibit A – Statement of

Work, Attachment 1 – Cost Sheet and Attachment 2 – Technical Proposal in this Agreement. In the event of any conflicts related to this Agreement, Exhibit C – General Terms and Conditions, DGS PD

402-ITGP (Cloud), Section 3, Order of Precedence, and Section 17, Dispute Resolution, shall apply.

2. Contractor agrees to provide inventory and collection of retroreflectivity data to Caltrans as described herein.

3. This Agreement will commence on August 17, 2026 (estimate), or upon approval by the California

Department of Transportation (Caltrans), whichever is later, and no work shall begin before that time. This

Agreement is of no effect unless approved by Caltrans. The Contractor shall not receive payment for work performed prior to approval of the Agreement and before receipt of notice to proceed by the Caltrans

Contract Manager. This Agreement shall expire on August 16, 2029 (estimate). The services shall be provided during working hours, Monday through Friday from 8:00 a.m. to 5 p.m., Pacific Standard Time

(PST), except State Holidays. The parties may amend this Agreement as permitted by law.

4. Agreement Amendment

A. Subject to the terms and conditions of the original Agreement, and contingent upon the approval of

Caltrans and the Contractor, Caltrans may have the option, prior to the Agreement expiration date, to amend the Agreement. The agreement allows for an amendment for time and/or quantity, for more of the same services.

B. The Agreement Amendment shall be amendable up to an additional three (3) years and an additional

$5,000,000.00.

C. If the Agreement were amended, the Contractor’s rates offered in the “Amendment Pricing” section of

Attachment 1 – Cost Sheet, for the additional work would apply.

D. Any resulting Agreement Amendment will not take effect until it is signed by a Caltrans Contract Officer, and Contractor has received a signed copy of the Agreement Amendment.

5. All inquiries during the term of this Agreement will be directed to the project representatives listed in the

Table 1 – Project Representatives, below:

Table 1 – Project Representatives

Department of Transportation (Caltrans) Contractor: TBD

Contract Manager:

Project Manager:

Address: Address:

Cell: Cell:

Email: Email:

6. Description of Work

The Contractor shall collect, analyze and report of Retro-Reflectivity of Pavement Marking from the

Caltrans Highway Network (On-system) as well as on the Non-Caltrans Highway Network (Off-system) as described in APPENDIX A below.

https://www.calhr.ca.gov/employees/pages/state-holidays.aspx

Exhibit A

STATEMENT OF WORK

APPENDIX A

SCOPE OF WORK

3 CALTRANS Division of Maintenance

Agreement Number 56A0889 Exhibit A

TABLE OF CONTENTS

1. SCOPE

2. APPLICABLE STANDARDS AND TERMINOLOGY

2.1. STANDARDS

2.2. TERMINOLOGY

3. MOBILE RETROREFLECTIVITY EQUIPMENT REQUIREMENTS

A. COMPUTER

B. HIGH DEFINITION VIDEO RECORDING SYSTEM

C. DISTANCE MEASURING INSTRUMENT (DMI)

D. GLOBAL POSITIONING SYSTEM (GPS)

E. HANDHELD RETROREFLECTOMETER

F. MOBILE RETROREFLECTOMETER UNIT (MRU)

4. SUMMARY OF TEST METHOD

5. PAVEMENT STRIPE NOMENCLATURE

6. DATA ACQUISITION, SUBMISSION, AND REPORTING REQUIREMENTS

6.1 HOSTING AND WEB-BASED INTERFACE

6.2 OWNERSHIP OF EXTRACTED DATA

6.3 TRAINING AND TECHNICAL SUPPORT

7. CALIBRATION

7.1. CALIBRATION AND STANDARDIZATION ELEMENTS

8. INTERFERENCE AND ENVIRONMENTAL INFLUENCE

9. EVENT CODES

10. QUALITY ASSURANCE FOR MOBILE RETROREFLECTIVITY UNITS

10.1 VISUAL INSPECTION

10.2 CALIBRATION

10.3 BACKGROUND NOISE TESTING

10.4 COMPARISON TESTING WITH HANDHELD RETROREFLECTOMERS

10.5 FIELD TESTING

10.6 DISTANCE MEASURING INSTRUMENT (DMI) ACCURACY

10.7 RETROREFLECTIVE STABILITY AND TEMPERATURE TEST

10.8 RETROREFLECTIVE STABILITY AND SPEED TEST

10.9 OPERATIONAL COMPETENCY TEST

4 CALTRANS Division of Maintenance

Agreement Number 56A0889 Exhibit A

10.10 QUALITY ASSURANCE

11. MINIMUM REPORTING REQUIREMENTS

11.1 DATA REPORT

12. PRECISION

12.1 REPEATABILITY

12.2 REPRODUCIBILITY

13. WORK PLAN

13.1 GENERAL

13.2 PERSONNEL

13.3 EQUIPMENT

Exhibit A

1. SCOPE

The objective of this contract is to inventory and collect retroreflectivity data (RL) of all longitudinal markings at a network level using multiple vehicle-mounted Mobile Retroreflectivity Units (MRU) operating at posted roadway speeds, in compliance with ASTM E3320.

The test method measures the retroreflective properties of dry, longitudinal marking materials, using a Mobile (vehicle-mounted) Retroreflectivity Unit (MRU) operated at posted roadway speeds at a prescribed geometry. The prescribed geometry corresponds to the European Committee for Standardization (CEN) and ASTM E3320. The minimum operational MRUs required are four pieces, including personnel with the necessary experience in mobile retro collection.

This test method does not claim to address all potential safety concerns related to its use. It is the user’s responsibility to establish appropriate safety and health practices and to determine the applicability of any regulatory restrictions before use.

The scope of this contract is to survey all Longitudinal markings once per year for three consecutive years in all the following Districts.

DISTRICT CENTER LINE MILES STRIPE MILES

1 996 4,170

2 1,839 7,043

3 1,596 7,744

4 1,519 10,302

5 1,218 5,583

6 1,897 8,797

7 1,196 10,075

8 1,949 11,086

9 1,034 4,491

10 1,401 6,143

11 1,137 7,071

12 296 3,051

TOTAL 16,078 85,556

ESTIMATED STRIPE MILES BY DISTRICT.

Exhibit A

The contractor shall provide Caltrans with retroreflectivity (RL) data of existing Longitudinal markings in their current condition. To accomplish this, the contractor must supply all necessary resources, including equipment and personnel, to perform a network-level survey.

Any unforeseen events (e.g., weather conditions or equipment malfunctions) occurring during contract execution must be promptly reported to the Contract Manager.

The Contractor shall not commence work until a kick-off meeting has been held.

Data collection shall begin upon execution of the contract. Final submittals are due within 9 months from the contract execution date. All deliverables shall be submitted on a weekly and monthly basis to the Caltrans Contract Manager and uploaded to the web-based interface. (Reference section 11 “MINIMUM REPORTING REQUIREMENTS” of this Appendix). Yearly submittals are due in the same month for three consecutive years.

The Contractor shall demonstrate adequate data collection equipment, resources, and technical expertise to meet the project’s schedule and scope of services.

A minimum of three years of experience in mobile retroreflectivity data collection is required, with a minimum of 250,000 cumulative stripe-miles collected.

Exhibit A

2. APPLICABLE STANDARDS AND TERMINOLOGY

2.1 STANDARDS

D4061: Standard Test Method for Retroreflectance of Horizontal Coatings

D7585/D7585M: Standard Practice for Evaluating Retroreflective Pavement Markings Using Portable Hand-Operated Instruments

E284: Standard Terminology of Appearance

E808: Standard Practice for Describing Retroreflection

E1710: Standard Test Method for Measurement of Retroreflective Pavement Marking Materials

ASTM E3320: Standard Test Method for Measurement of Retroreflective Pavement Marking Materials Using a Mobile Retroreflectometer Unit (MRU)

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

ASTM D6359: Standard Specification for Minimum Retroreflectance of Newly Applied Pavement Marking Using Portable Hand-Operated Instruments

2.2 TERMINOLOGY

The definition of all the terms used in this document, as well as other relevant terms, can be found in ASTM E284, ASTM E808, ASTM E1710, ASTM E3320, ASTM D7585/D7585M, and ASTM D4061.

The definitions listed below are direct excerpts from the above references for the terms that are most relevant to the content of this document.

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.

Coefficient of retroreflected luminance, RL: the ratio of the luminance of a projected surface to the normal luminance at the surface on a plane normal to the incident light, expressed in candelas per square meter per lux (cd/m2/lux).

Exhibit A

3. MOBILE RETROREFLECTIVITY EQUIPMENT REQUIREMENTS

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

A. COMPUTER

The computer is used to operate the mobile retroreflectometer, the video recording system, the distance measuring instrument (DMI), and the global positioning system (GPS) device, which are part of the vehicle setup. The computer must be equipped with an operating system for data entry, acquisition, display, and storage. It must have sufficient capabilities to analyze the collected data, operate the software, and receive input from the mobile retroreflectometer. The computer must be up to date with the most recent version of the software to provide accurate data.

B. HIGH DEFINITION VIDEO RECORDING SYSTEM

The video recording system shall be integrated with the computer to provide a synchronized video overlay displaying both the forward scene (all highway assets per direction of travel) and the collected data for each Line Type. Its primary purpose is to support data verification and identify discrepancies.

Retroreflectometer evaluations shall document average retroreflectivity values, GPS coordinates, and include a high-quality video recording of all measured striping. The video must capture identifiable landmarks and feature a data overlay with all deficient sections marked. The video resolution shall be full HD 1080p or 1080i. The video shall have the overlay of the data being collected. The web-based interface shall have each file number and video displayed for easy download.

The video recording system shall digitally record the roadway while displaying the Date, Time, GPS

Coordinates, Route, Direction, Retroreflectivity values, and Odometer reading.

C. DISTANCE MEASURING INSTRUMENT (DMI)

The Distance Measuring Instrument (DMI) is used to tag the data to the roadway Postmile. The DMI must be within ±5.280 feet (0.1%) when measuring a 1.0-mile section of roadway. The DMI must be calibrated, and GPS verified monthly or as deemed necessary at locations designated by Caltrans. Additionally, a DMI recalibration must be performed anytime tires are changed, rotated, or air pressure is adjusted.

D. GLOBAL POSITIONING SYSTEM (GPS)

The GPS is an antenna for collecting and reporting the GPS coordinates with pavement marking data. GPS must be within an instantaneous horizontal positioning accuracy of ±3.0 feet (1 meter) or better. A GPS minimum output of ±5 HZ is required.

E. MOBILE RETROREFLECTOMETER UNIT (MRU)

The retroreflectometer must be capable of collecting data conforming to ASTM E 3320

Exhibit A

The retroreflectometer must be capable of collecting pavement marking data at roadway speeds while accounting for horizontal wander and vertical movement of the host vehicle.

The retroreflectometer must be capable of measuring the retroreflectivity of pavement markings ranging from 0 to 2,000 (mcd∙m-2∙lux-1).

The retroreflectometer must be capable of measuring the retroreflectivity of pavement markings during both daylight and nighttime conditions. The contractor is responsible for demonstrating that night readings are comparable to day readings with the reproducibility tests. Measurements must be collected during daylight hours.

The retroreflectometer(s) must be capable of being operated on either side, both sides, or the front of the host vehicle.

Proposed Mobile Reflectometers will be reviewed and approved by the Contract Manager.

Exhibit A

4. SUMMARY OF TEST METHOD

ASTM 30-meter geometry, specified in ASTM E1710, describes the measurement of pavement marking retroreflectivity at 30 meters, mimicking a driver's typical viewing distance. This geometry uses a standardized vehicle with a headlight height of 0.65 meters and a driver's eye height of 1.2 meters.

The entrance angle is 88.76° and the observation angle is 1.05°.

FIGURE 1. STANDARD 30 METER GEOMETRY SPECIFIED IN ASTM E 1710

The MRU must have a known light source that measures the return light of that know light source. The MRU must be calibrated per the manufacturer’s specifications. This includes a factory calibration of the known light source with documentation of the MRU’s light intensity.

Retroreflectivity is measured with the MRU operated along the section of the roadway.

Retroreflectivity data should be collected, processed, analyzed, and reported using the software provided and recommended by the MRU manufacturer or service provider.

That data collected, including videos and raw data files, shall be uploaded to the service providers web-based browser with all the features required in this scope of work.

Exhibit A

5. PAVEMENT STRIPE NOMENCLATURE

Contractor shall follow the standard naming convention stated below. This standard naming convention was developed to identify each pavement stripe, regardless of the number of lanes. Table 1 shows an explanation of the nomenclature used.

• The pavement stripe nomenclature includes the direction of travel followed by the stripe type as identified in Table 1. For skip lines, a line is used to delineate traffic lanes for the movement of vehicles traveling on the roadway.

• As an example, based on the information shown below, the northbound skip line closest to the center line would be identified as LL1; the edge line is in the same direction as the travel way and is located on the far right side of the roadway would be designated as REL.

Figure 2 shows the Pavement stripe nomenclature for a multi-lane divided roadway, and Figure

3 shows the Pavement Stripe nomenclature for a roadway with HOV lanes, and

Figure 4 shows the Pavement stripe nomenclature for a conventional roadway.

PURPOSE CODE* DESCRIPTION

Direction* NB, SB, EB & WB

Northbound Travel Way, Southbound Travel Way, Eastbound Travel Way & Westbound Travel Way

Stripe Types

REL Right Edge Line (White)

LEL Left Edge Line (Yellow)

HOV Double Solid Line (White)

CL

Center Line (Yellow). All yellow stripes, including yellow skip lines, are considered center lines. When collecting yellow center line pavement markings, white pavement markings such as turn lanes must not influence the yellow center line reflectivity.

Exhibit A

LL

Lane Line (White Skip Line). A lane line is designated between the through movement in the same direction of travel, and a number is placed after it to indicate the order of the skip lines, starting with the one closest to the center Line

TABLE 1 - PAVEMENT STRIPE NOMENCLATURE

*Note: The Caltrans Route Directional Designation specifies direction.

FIGURE 2. PAVEMENT STRIPE NOMENCLATURE FOR A MULTI-LANE DIVIDED ROADWAY

Exhibit A

FIGURE 2. PAVEMENT STRIPE NOMENCLATURE FOR HOV LANE

Exhibit A

FIGURE 4. PAVEMENT STRIPE NOMENCLATURE FOR A CONVENTIONAL ROADWAY

Exhibit A

6. DATA ACQUISITION, SUBMISSION, AND REPORTING REQUIREMENTS

The retroreflectivity measurements should be based on ASTM E 3320 and the sampling protocol specified in ASTM D7585.

The acquisition frequency must be analyzed for every 0.1-mile interval (unless recommended otherwise) and be reported in millicandelas per square meter per lux (mcd∙m-2∙lux-1).

The MRU must be capable of:

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

• Filtering out the high retroreflectivity levels of Raised Pavement Markings (RPMs) that influence the pavement marking readings.

• Reporting all retroreflectivity statistics as required under “APPENDIX C: "MINIMUM DATA

ELEMENTS FOR RAW AND SUMMARY DATA FILES"

• Being operated on either side or the front of the host vehicle.

The acquisition system must be capable of recording manual trigger event codes (Reference Section 9 of this Appendix) during the data collection process to mark roadway characteristics, such as bridges, intersections, pavement changes, etc. Additional information can be found under APPENDIX C:

"MINIMUM DATA ELEMENTS FOR RAW AND SUMMARY DATA FILES."

The retroreflectometer evaluations should document the average retroreflectivity values, including GPS location, with a video of all the stripes being measured with identifiable landmarks in high-quality resolution and data overlay with all deficient sections marked.

The data shall be collected for each line on each route continuously at posted roadway speeds with minimal vehicle wander. Any unusual appearance of the striping line (e.g., debris, damaged line, etc.)

shall be noted during the survey. In addition, the collected data shall be linked to roadway-specific information. The Raw Data CSV file should contain the Minimum Column Information as shown in

APPENDIX C: "MINIMUM DATA ELEMENTS FOR RAW AND SUMMARY DATA FILES".

The contractor will be required to review and evaluate the quality of the data. The contractor will be responsible for submitting the data summarized at every 0.1-mile segment, in addition to the raw data files from the equipment. Both the summary and the raw data files shall be in CSV file format. The minimum required data elements to be included in the raw and summary data files are shown under Appendix C: “MINIMUM DATA ELEMENTS FOR RAW AND SUMMARY DATA FILES”.

In addition to the CSV format, summary data files shall be submitted in both KML (Google Earth) format and either Shapefile or File Geodatabase format compatible with Esri ArcGIS. All point and line features shall contain the same attribute fields as those in the summary CSV files. The coordinates in the Shapefile or File Geodatabase must match the latitude and longitude values provided in the CSV files.

Exhibit A

6.1 HOSTING AND WEB-BASED INTERFACE

The Contractor (or other third party) is to host the web-based interface and:

1. Provide details of level-of-service guarantees, including service availability (uptime) and response times. Have backup and restoration plans, and 99% uptime.

2. Web-based interface must support up to 30 users concurrently.

3. Provide details of hosting costs for the duration of the contract period, including maintenance and all available upgrades.

4. Provide the ability to restore data in case of data loss or corruption.

5. Provide access to data after the contract has expired.

Readings shall be uploaded to a cloud-based storage system every week and should be accessible via a Web Browser (Internet Explorer, Chrome, Firefox, …).

The web-based interface must be able to show each Caltrans District separately. Caltrans has 12

Districts. District locations can be found on the Caltrans Near Me Link.

https://dot.ca.gov/caltrans-near-me

The web-based interface shall, at a minimum, provide methods and tools for displaying and interacting with mobile retroreflectivity data. It must be capable of displaying and analyzing the complete dataset, including year-over-year degradation rates. The system shall serve as a centralized, secure platform where Caltrans can access, analyze, download, upload, view, manage, and geospatially visualize all collected data. This includes longitudinal retroreflectivity data, videos, images captured during the project, and any other relevant project information. Key functionalities will include real-time project tracking down to the roadway level, detailing the crew and completion date/time for each segment.

Furthermore, the system will offer real-time project tracking for percentage completion per district and real-time crew tracking for vehicles equipped with GPS devices.

The web-based interface should provide the following capabilities/functionality:

• Data output shall provide the following added attributes for each 1/10th mile interval:

a) Contrast Ratios

b) Line width

c) Subjective Rating as defined in Section 11 of this SOW

d) Surface Type i.e., concrete or bituminous

e) Surface treatment i.e., grooved markings, surface applied, shoulder rumble strip (6 inch or 12 inch)/centerline rumble strip/sinusoidal rumble strip

• Web based interface must be able to utilize Caltrans POST MILE REFERENCES for all aspects of data reporting.

• Web based interface must be able to produce District/County/Roadway striping plans based on user define dynamic parameters.

a. This includes but is not limited to retro values, subjective ratings, user defined length of

Exhibit A failures, etc.

• Provide line width reports for each district which include a list of contiguous segments of 4” lines within the district and their locations, postmiles, plus other metadata.

• Be accessible via multiple machines simultaneously.

• All collected data should be accessible through a web browser, and no additional software should need to be installed locally.

• Each District should be depicted on a separate layer of a GIS map.

• Analyze the entire data set to include year-to-year degradation rates.

• Access historical asset data.

• Provide a security role for a read-only environment to prevent individuals from making edits to the data.

• Include the ability to export/import mass data in various formats such as Excel, ESRI shapefile, or others.

• Ability to print reports and queries.

• The web-based interface should include a dashboard which includes charts and tables to provide a high-level overview of measurement progress and + reflectivity data, including:

a. A graph of measurement progress completion over time.

b. A chart of the number of line miles which pass and fail the defined retro thresholds per district.

c. A table with statistics per district and totals, including pass and fail mileage and percentage, 4” and 6” line width mileage and percentage.

d. A graph of retroreflectivity statistics (min, max, avg, median) over time, broken down by line color or line type, with user selectable filters for county and district.

e. A graph of SB1 lifecycle retroreflectivity performance by material age broken down by material type, with user selectable filters for warranty or not, district, county, route, and line type.

f. Each chart or table can be downloaded in tabular or image form or can be printed.

g. The data on the dashboard is updated at least daily.

• Provide real-time project tracking down to the roadway level, including the crew and the exact date and time of completion for each segment.

• Enable real-time project tracking for percentage complete per district.

• Facilitate real-time crew tracking for each vehicle equipped with GPS devices.

• Allow selecting a roadway on the map and review the video for the given roadway segment

Exhibit A

FIGURE 5. VIDEO INTEGRATION INTO WEB BASED INTERFACE

All data must be made available on the website within 7 days of data collection in the field.

Monthly website maintenance shall include at a minimum:

a. Unlimited access to website features described above.

b. Individual logins for each Caltrans website user (3 users per district, 5 users for HQ, and one for the Contract Manager). Unlimited Users within Caltrans

c. Provide a 99% uptime guarantee

At the end of each year, the contractor shall provide the Contract Manager with a hard drive containing all the data files described under Section 6.

6.2 OWNERSHIP OF EXTRACTED DATA

All extracted data becomes and remains the property of Caltrans.

6.3 TRAINING AND TECHNICAL SUPPORT

a. Provide a 4-hour training session for each District (Total of 12 Districts) via a video conference at the end of the District Data Collection. The training is for the web-based interface functionality.

Creating reports, queries, and exporting data. For District locations, check the Caltrans Near Me link.

b. Provide up to 80 hours of onsite/offsite technical support training as needed at Caltrans’

Exhibit A discretion. This would be online training.

Exhibit A

7. CALIBRATION

Before beginning a survey for a day, the equipment shall be warmed up for a duration recommended by the manufacturer and calibrated according to the manufacturer and the listed applicable standards.

7.1 CALIBRATION AND STANDARDIZATION ELEMENTS:

Calibrate the equipment per the manufacturer’s specifications.

1. The DMI distance must be calibrated with an error tolerance of ±5.28 ft/mile or less for test vehicle speeds up to the maximum specified for the equipment utilized.

2. The DMI must be calibrated every month and per the manufacturer's recommendations or as deemed necessary. Additionally, a recalibration must be performed anytime tires are changed, rotated, air pressure is adjusted, or the data is questionable.

3. The MRU system must be calibrated, and its performance verified per the manufacturer’s requirements.

4. The calibration of the MRU should conform to the 30-m geometry.

5. The calibration equipment provided and/or recommended by the manufacturer should be used for calibration.

6. A log of calibration must be maintained.

7. The MRU calibration equipment should be verified and standardized by the manufacturer at least once a year.

The frequency of the Check and Calibration Procedures can be found in Table 2 below.

Type of Test Testing Frequency

Daily Mon thly

Bi- Mon thly

Tire Pressure Check X

Distance Check and Calibration

X

Quality Assurance Testing

Field Calibrations and Verifications X

Clean and Inspect Detector Optical Window

TABLE 2 – FREQUENCY OF CHECK AND CALIBRATION PROCEDURES

Exhibit A

8. INTERFERENCE AND ENVIRONMENTAL INFLUENCE

A. Measurements made with the MRU may be adversely affected by moisture in the air and on the surface of the pavement markings. Standing water, dew, sleet, and snow on the surface of the pavement marking or fog and smoke in the air decrease the amount of retroreflected luminance due to light reflecting off the water and away from the detector. Environmental factors are difficult to measure and may vary dramatically; therefore, testing must be avoided when these conditions are present.

B. Measurements made with the MRU may be adversely affected by surface dirt, debris, and contamination on the pavement marking, which decreases the amount of retroreflected luminance. This may cause variability in the retroreflected luminance of the pavement marking and must be noted accordingly. The operator must note when these conditions are present. See Section 9 – EVENT CODES for additional information.

C. Background noise from roadway surfaces and high retroreflectivity levels of Raised Pavement Markings (RPMs) can influence the retroreflected luminance of the pavement markings. The operator must recognize these issues if the data acquisition system is not working properly, so that appropriate corrective actions can be applied.

D. The MRU contains advanced optical and electronic components that are sensitive to temperature fluctuations. To ensure optimal performance, it is recommended to maintain a stable internal temperature within ±2°C of 25°C. If this temperature range cannot be maintained, corrective actions must be taken as per the manufacturer's guidelines. It is essential to understand and implement these corrective measures if the optical or electronic components are not functioning properly or as intended.

Exhibit A

9. EVENT CODES

A. For roadway events, use the standard nomenclature and data acquisition event codes, as shown in Table 3. The roadway events must be recorded to the nearest thousandth of a mile. It should be noted that, except for triggered events, the data should remain in exact 1/10th mile increments.

(i.e., if an event is flagged at mile point 1.555 with ascending mile points, regardless of whether it is part of the “Reset Data” or “Hold Event” data, the preceding and following mile points should be 1.5 and 1.6, respectively.

B. The following items describe how the events must be processed.

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

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

3. Stop Collection – The data acquisition system shall automatically halt data collection whenever conditions may result in an inaccurate representation of pavement markings.

TABLE 3 – DATA ACQUISITION SYSTEM EVENT CODES

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

DESCRIPTION* RESET DATA HOLD EVENT

Construction X

Audible X X

No Line X X

Bridge X X

Rumble Stripe X X

Line Damage X X

Debris on the Line X X

Pavement Change X X

Lane Interference X X

Misc. Event X X

Exhibit A

10. ACCEPTANCE CRITERIA FOR MOBILE RETROREFLECTIVITY UNITS

10.1 VISUAL INSPECTION

Visual inspection is the first step in making sure the MRU is ready for operation. A good practice to ensure the equipment is test-ready is to inspect that all brackets, mounts, and bolts are tight and mounted securely around the exterior of the equipment before calibration and routine operation.

The retroreflectometer window shall be inspected to ensure it is clean and free of any damage or debris.

Following the inspection of external components, the MRU shall be powered on. The calibration panel must be checked for signs of damage or wear. The MRU operator shall then perform the calibration procedure, which must be reviewed to verify accuracy and correct geometry. The retroreflectometer’ s laser power intensity and laser profile shall be measured to ensure readings fall within acceptable limits. Arc-like or parabolic distortions must be avoided to prevent data collection errors. For a 3.28-foot scan, the longitudinal variation of the laser path shall not exceed

3.28 feet. This visual inspection of the MRU shall be performed monthly or as needed.

10.2 CALIBRATION

The MRU calibration equipment should be verified and standardized by the manufacturer at least once a year for

• ALIGNMENT AND WANDER

• LATERAL WANDER

• LONGITUDINAL WANDER

10.3 BACKGROUND NOISE TESTING

Background Noise Testing is performed to ensure that the noise from the environment and other reflective materials are not influencing the RL values.

10.4 COMPARISON TESTING WITH HANDHELD RETROREFLECTOMETERS

To determine if the RL values measured using the MRU are comparable to those from conventional handheld retroreflectometer, a total of six panels (3 white and 3 yellow) with RL values ranging between 100 and 1,000 mcd/m2/lux will be tested. After the MRU has been calibrated, the RL of all six panels will be measured with the MRU, one at a time. The RL from the MRU shall be within ±15.0% of the handheld RL values. The background noise will be monitored during this test to see if different panels affect the background noise. The comparison tests shall be conducted once every two months or as deemed necessary.

Exhibit A

10.5 FIELD TESTING

The following field tests will be conducted to verify the performance of the MRU, operator, and data collection software:

1. Distance Measuring Instrument (DMI) Accuracy

2. Precision Testing

3. Retroreflective Stability and Temperature Test

4. Retroreflective Stability and Speed Test

5. Operational Competency Test

10.6 DISTANCE MEASURING INSTRUMENT (DMI) ACCURACY

The MRU must be equipped with a distance measuring instrument (DMI) to measure the distance traveled by the vehicle. The DMI distance must be within ±5.280 feet (0.1%) when measuring a 1.0-mile section of roadway. The DMI shall be calibrated monthly or as required at locations designated by Caltrans. Additionally, recalibration must be performed whenever tires are changed, rotated, or their air pressure is adjusted.

10.7 RETROREFLECTIVE STABILITY AND TEMPERATURE TEST

Testing for stability with a temperature change is recommended before using an MRU on actual projects.

10.8 RETROREFLECTIVE STABILITY AND SPEED TEST

MRU testing is conducted at Posted Roadway Speeds, so it is important to verify the MRU results are not affected by vehicle speed.

10.9 OPERATIONAL COMPETENCY TEST

Additional field tests will be conducted to evaluate the following factors:

a. Proper use of event codes such as pavement changes, construction, no stripe line, etc.

b. Daytime and nighttime testing

c. Driver competency (e.g., vehicle wander)

d. Proper identification of stripes

e. Ability to set RL thresholds for the Raised Pavement Markings (RPM)

f. Proper handling of MRU during acceleration, braking, and stopping

For these tests, the MRU will be mounted on either side or the front of the vehicle. Tests shall be conducted on roadways with various pavement types and markings selected by Caltrans to include the following:

• Stripe colors - Yellow and white

• Stripe patterns - Single solid, single skip, double solid, left solid/right skip, left skip/right solid, and edge line.

• Various ranges of retroreflectivity

These additional tests shall be conducted yearly or as deemed necessary.

Exhibit A

10.10 QUALITY ASSURANCE

Before providing MRU services to Caltrans, the contractor must demonstrate that their MRU and operator satisfy all the quality assurance criteria described above. To provide MRU services, the contractor must conduct the quality assurance tests at the frequency designated for each respective test. Anytime a quality assurance criterion is not met, the contractor must inform Caltrans and take remedial action. The contractor must notify Caltrans once remedial actions have been implemented and subsequently demonstrate that all quality assurance criteria are met.

Caltrans will determine which quality assurance tests need to be repeated after reviewing the issue and the contractor’s corrective measures.

Caltrans reserves the right to perform initial inspections to verify that the contractor has provided accurate data and a quality product. These initial checks will occur at the start of the contract and periodically thereafter to ensure data is submitted in the required format and condition. Ongoing data reviews will also be conducted to confirm that all submitted files meet acceptance criteria.

Furthermore, Caltrans will examine both summary and raw data files to verify that proper settings and data collection procedures are being followed.

The data will be reviewed by Caltrans using in-house or contractor resources to rate up to 10 percent of the data being collected. The Contractor will be notified of the results. The Contractor shall investigate, at no cost to Caltrans, any data that does not meet acceptance criteria. The Contractor shall conduct the investigation promptly and report the findings. At a minimum, the investigation report shall include the following components:

• Description of the non-compliance and/or errors in the data.

• Reasons/factors for the problems.

• Data that are affected by the same problems.

• Corrective measures, including but not limited to repair and/or recalibration of equipment.

• Debugging and/or recording of the computer programs used for data collection and data analysis.

• Re-collection and/or re-analysis of the affected data.

• Corrective measures that the Contractor will employ to avoid similar problems in the future.

Caltrans will perform quality assurance on the initial batches of data delivered.

Caltrans reserves the right to halt new data collection and/or analysis until the resubmitted data satisfies all acceptance criteria.

Exhibit A

11. MINIMUM REPORTING REQUIREMENTS

The following information must be reported as described in APPENDIX C: “MINIMUM DATA

ELEMENTS FOR RAW AND SUMMARY DATA FILES”:

A. Project information (project ID, beginning/ending mileposts, roadway direction, stripe type, and other relevant information).

B. Survey date and weather conditions at the beginning of the test.

C. Identification of the pavement stripe (e.g., CL, LEL, LL1, REL, etc.).

D. Identification of the MRU ID, operator, and software used.

E. Equipment calibration information.

F. The results must be reported in millicandelas per square meter per lux (mcd∙m-2∙lux-1).

Worksheets specific to the direction of travel and stripe type must be reported in 0.1-mile intervals.

G. The results must include event codes as mentioned in Section X – “EVENT CODES”.

H. Condition Assessment:

A subjective rating will be noted at every 1/10th of a mile of raw data delivered for each line on each route that is surveyed for its retroreflectivity. The scale will rate a given marking between 5 and 1, and that value will be representative of a marking’s daytime presence/condition. The following table is an example of how the markings will be assessed.

Subjective Rating/Co ndition Assessme nt

Description of Condition Assessment Rating Value

5 New pavement markings with no visible wear or poor workmanship.

4 Pavement marking is providing 100% presence and no apparent damage.

Typical wear and/or discoloration to the pavement marking, the marking still provides good presence with minor damage.

2 Poor condition - pavement marking not providing adequate presence.

1 Failure - pavement marking is not providing any presence.

I. Summary statistics of retroreflectivity, such as average and standard deviation.

J. Video Recordings

Exhibit A

11.1 DATA REPORT

A. WEEKLY REPORTS

The Contractor must submit weekly updates on the progress of the retroreflectivity collection.

The weekly updates must include a description of any problems encountered. A weekly log must be created even if no work was performed each week. The Contractor shall submit with the weekly logs a brief plan for the routes that are planned for data analysis in the monthly report.

Weekly log reports must include District/Route:

• Center Line-miles estimated.

• Center Line-miles collected.

• Center Line-miles analyzed.

• Center Line-miles reported/uploaded to the web-based interface.

• Percentage of collection complete

B. MONTHLY MEETINGS AND PROGRESS REPORTS

A monthly virtual meeting will be held between the Contractor and the Contract Manager. A Monthly status report shall be submitted a week before the monthly meeting. The monthly report shall detail the progress and status of work completed in each of the twelve (12) Caltrans Districts.

The Contractor must also submit a complete District Report at the end of the collection and analysis for each district.

Exhibit A

12. PRECISION

12.1 REPEATABILITY

The results of two properly conducted retroreflectivity tests using the same MRU on the same pavement marking test section must not differ by more than 10.0% at a 95 percent confidence level.

12.2 REPRODUCIBILITY

The results of two properly conducted retroreflectivity tests using different MRUs on the same pavement marking test section must not differ by more than 10.0% at a 95 percent confidence level.

13. WORK PLAN

13.1 General

The Contractor shall develop a complete and detailed Work Plan for each district collection. The

Work Plan must include a detailed description of well-identified milestones such as the completion of a district survey, the activities considered necessary to achieve those milestones, and all deliverables described in this Appendix.

The Work Plan must provide a thorough description of the Contractor’s staffing and equipment, which must be adhered to in the contract.

The Work Plan shall clearly outline the Contractor’s approach to planning, monitoring, submitting, and implementing the activities outlined in this document and specify the time for each task.

13.2 Personnel

The Work Plan shall list all personnel who will be working on the project. Include their titles, qualifications, a summary of similar work or studies performed, a resume for each professional, a statement indicating the amount of time each professional will be assigned to the project, and what tasks each professional will perform. The Contractor shall not substitute members of the project team without prior written approval of Caltrans. The positions below may be combined if an individual possesses the qualifications.

Project Manager: This individual shall oversee the work and shall review all measured and calculated data before uploading it to the web-based interface and submitting it to Caltrans. The project manager must have a working knowledge of asset collection related to roadway safety and an ability to recognize the various assets.

Database Manager: This individual shall lead the data handling and database management for this contract. The individual is expected to be familiar with the data processing software and hardware used for data collection, processing, and storage. This individual must be efficient at database information retrieval and data report formatting and must demonstrate experience and knowledge of the latest computer equipment and the database system.

Exhibit A

13.3 Equipment

The Work Plan shall list all equipment which will be used on the project, including:

• Manufacturer Name of the Equipment Used in this contract.

• Address

• City, State, Zip Code

• Brief Description of Equipment

• Equipment Certification and Calibration Dates

If any equipment is changed during collection, the Contractor must notify Caltrans of the changes, and the new equipment shall obtain certification from Caltrans Profiler Certification Program before it can be used for data collection.

Exhibit A

APPENDIX B:

SPECIFICATION FOR VEHICLE MOUNTED MOBILE

RETROREFLECTOMETER

Exhibit A

APPENDIX B:

Specification for Vehicle-Mounted Mobile Retroreflectometer

1. The instrument shall detect, measure, and record the location of retroreflective road marking based on

ASTM E3320.

2. Measuring aspects of the total angular spread shall not exceed 0.33 degrees.

3. The Operating Temperature Range shall be 0° to 120°F.

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

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

6. The instrument shall accurately measure skip lines (broken lines) without any correction factors.

7. The device shall be able to measure both white and yellow, flat, and profiled road markings of any type on Flat and Rough, Dry surfaces. The device must compensate for daylight and continue to measure under changing light conditions during the day and night.

8. The instrument shall give individual readings for both lines of a double line.

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

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

11. GPS shall report GPS coordinates with each measurement point.

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

13. 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.

14. 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.

15. Data shall be uploaded to a Cloud-based storage and accessible through a Web Browser.

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. The retroreflectometer shall be capable of being mounted on either side of a vehicle.

19. Subjective Rating Condition Assessment (5- New pavement markings with no visible wear or poor workmanship; 4- Pavement marking is providing 100% presence and no apparent damage; 3- Typical wear and/or discoloration to the pavement marking, the marking still is providing good presence with damage; 2- Poor condition, pavement marking is not providing adequate presence; 1- Failure, pavement marking is not providing any presence.)

Exhibit A

APPENDIX C:

MINIMUM DATA ELEMENTS FOR RAW AND

SUMMARY DATA FILES

Exhibit A

COMMON RAW DATA

REFERENCE DATA ELEMENT EXAMP

LE

1 The raw file name is needed for a reference.

BMR_L1SL_201

7-04- 21_10_27

2 The data analysis software and version being used.

1.013_(TEST6)

_1113_202 1)

3 The company performing the data collection.

Joe's Retroreflectivity Testing

4 Enter the operator's initials. JTS

5 The retroreflectometer serial number. RR 555

6 Operator’s notes specific to the test. Notes

7 Mobile Reflectometer Model. ABC57

8 Acquisition frequency is 0.1 mi unless specified otherwise. 0.1

9 Stripe 1 Calibration Date and Time (PST). 5-29- 2015/08:00:44

10 Stripe 1 Calibration factor with at least 4 decimal places. 1.0000

Stripe 1 Assigned retroreflective value obtained by a certified testing facility (mcd/m2/lux)

12 Stripe 1 Temperature in Celsius inside equipment at the time of calibration.

24.72

13 Stripe 1 Background noise at the time of calibration. 39.3

14 Stripe 2 Calibration Date and Time (PST). 5-29- 2015/08:09:11

15 Stripe 2 Calibration factor with at least 4 decimal places. 0.9999

Stripe 2 Assigned retroreflective value obtained by a certified testing facility (mcd/m2/lux).

17 Stripe 2 Temperature in Celsius inside equipment at the time of calibration.

35.24

18 Stripe 2 Background noise at the time of calibration. 43.5

19 Describe whether the internal temperature compensation is applied. YES

20 Describe whether the stripe width compensation is applied. NO

21 Enter the system number of the roadway being tested. Freeway

OPTIONS

1. Freeway

2. Expressway/Conventional

3. Toll Road

4. City Street

22 Enter the district that the test is being run in. 11

23 Enter the county being tested. SD

24 Enter either the SR (State Route), I (Interstate), or US (US Route). I

25 Enter the State Route number (3 DIGITS). 005

26 Enter travel direction either NB, SB, EB, or WB. NB

27 Enter the lane in which is being tested LEL

28 Enter weather conditions either Sunny Day, Clear Night, Overcast, or Cloudy.

Overcast

29 Enter the temperature of the outside environment. 80

Exhibit A

COMMON RAW DATA (Continue)

REFERENCE DATA ELEMENT EXA

MPL

E

30 Enter the test type of roadway being tested. 5

1. Inventory–Old Striping

2. Special Request

3. Overlay

4. New Construction

5. Retest

6. Asset Management

31 Stripe Color: White or Yellow. White

32 Stripe Type. Edge Line

1. Single Solid

2. Single Skip

3. Double Solid

4. Left Solid/Right Skip

5. Left Skip/Right Solid

6. Edge Line

Exhibit A

RAW DATA FILES

33 Data file number 1542

34 Odometer – The distance traveled. Ex. 0.10 0.10

35 Date. 5/22/

36 PST Time. 9:00:

37 Latitude. 32.95

38 Longitude. - 117.1

39 GPS Accuracy – The uncertainty of the GPS position fix (in meters or feet, depending on units selected).

0.65

40 Vehicle Speed - mph 65

41 Temperature 79.5

42 Humidity 18.25

43 Valid Scans – The number of valid measurements of the line over the complete interval. 925

44 Average road surface retroreflectivity value 115.2

45 Retro Average – Average retroreflectivity value of the line over the complete interval. 110.2

Retro Contrast – The average contrast value between the stripe and the pavement of the line over the complete interval

47 The standard deviation of the retroreflectivity for the stripe (mcd/m2/lux). 32

48 Retro Stripe width – The average stripe width as measured by the line over the complete interval.

3.95

49 The averaged background noise for each row of data

50 Subjective Rating Condition of the Stripe 3

5. New Pavement Marking with no visible wear or poor workmanship.

4. Pavement Marking provides 100% presence and no apparent damage.

3. Typical wear and/or discoloration to the pavement marking, the marking still provides good presence with minor damage.

2. Poor Condition – Pavement marking is not providing adequate presence.

1. Failure – Pavement marking is not providing any presence.

51 The event codes were inserted during testing. Bridg e

1. Pavement Change

2. Construction

3. Audible

4. No Line

5. Bridge

6. Rumble

7. Line Damage

8. Debris on the line

9. Lane Interference

10. Misc. Event

Exhibit A

SUMMARY FILE

➢ Postmile (for each 0.1 mile segment)

➢ Subjective Rating Condition of the Stripe

➢ Average retroreflectivity for each segment

➢ Total number of 0.1 mile segments

➢ Number and percent of 0.1-mile segments with average retroreflectivity in one of the following categories using different colors:

o Below 100 mcd/m2/lux o Between 100 mcd/m2/lux and 150 mcd/m2/lux o Above 150 mcd/m2/lux and 200 mcd/m2/lux o Between 200 mcd/m2/lux and 500 mcd/m2/lux o Above 500 mcd/m2/lux

Exhibit A

APPENDIX D:

ESTIMATED LINE MILES BY DISTRICT

Line Mile Accuracy is within +/- 5 %

Exhibit A

DISTRICT 1

ROUTE CENTERLINE

MILES

STRIPE

MILES

001 108 371

020 95 338

029 54 216

036 48 160

053 7 36

096 46 154

101 301 1,697

101U 2 6

128 54 177

162 36 118

169 25 83

175 40 130

197 7 23

199 38 156

200 3 9

211 6 19

222 2 6

253 18 60

254 34 111

255 9 37

271 16 51

281 3 11

283 0 1

299 44 193

GRAND TOTAL 996 4,170

Exhibit A

DISTRICT 2

STRIPE

MILES

003 153 517

005 200 1,301

032 26 88

036 213 748

044 112 402

049 8 26

070 105 373

089 130 450

096 107 356

097 57 210

099 26 88

139 128 426

147 13 41

151 7 29

161 20 67

172 9 30

263 8 28

265 1 2

273 18 116

284 8 28

299 277 972

395 210 744

GRAND TOTAL 1,839 7,043

Exhibit A

DISTRICT 3

STRIPE

MILES

005 133 951

012 6 23

016 76 257

020 128 502

028 12 48

032 55 195

045 74 244

049 161 582

050 116 783

051 11 91

065 32 176

070 86 398

080 160 1,170

084 17 55

089 91 309

099 123 728

104 19 62

113 40 174

128 11 34

149 6 40

153 1 2

160 50 181

162 82 280

174 14 46

191 12 40

193 38 124

220 3 11

244 1 9

267 13 41

275 0 3

395 6 28

505 23 155

GRAND TOTAL 1,596 7,744

Exhibit A

DISTRICT 4

STRIPE

MILES

001 172 652

004 51 340

009 14 53

012 67 278

013 11 61

017 15 112

024 15 166

025 3 9

029 57 280

035 48 193

037 23 132

061 7 45

077 0 2

080 79 851

082 44 358

084 75 343

085 25 229

087 9 78

092 29 191

101 185 1,773

109 1 5

112 2 12

113 24 82

114 1 6

116 49 172

121 36 126

123 7 51

128 65 214

130 21 71

131 4 21

152 37 177

156 1 2

160 3 19

185 11 67

205 1 8

Exhibit A

220 3 12

221 3 19

237 13 98

238 13 86

242 4 29

260 2 12

262 1 7

280 63 694

380 2 20

505 12 74

580 70 671

680 77 755

780 8 49

880 50 558

880S 3 14

980 2 22

GRAND TOTAL…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .