SoW - Pavement Condition Surveys FY22.docx

R5/R6 Paved Road Condition Surveys 4 of 4 Statement of Work for R5/R6 Paved Road Condition Surveys

1. Scope of Work: This work includes the collection, processing, and reporting of data to support the determination of the pavement condition index (PCI) for paved roads and the pavement surface evaluation and rating (PASER) for gravel roads and unimproved roads.

2. Location: The location, road number, segment length, and National Forest (NF) are listed on the attached tables and maps. Roads are located across the states of Oregon and California, within the Pacific Southwest Region (5) and Pacific Northwest Region (6) of the US Forest Service.

3. Paved Roads

3.1 General: Distresses to be collected are included in the ASTM Standard 6433-20. Distresses shall be continuously collected on the designated asphalt concrete (AC) and bituminous surface treated (BST) Forest Service Roads, with quantity of centerline-miles of road outlined in schedule of items. Roughness (ride quality) data shall be collected for both directions of roads where fill failures are present. Collection of distresses can be done using automated means with vehicles or devices that meet Federal Lands Highway quality assurance protocols. The services to be provided include the following:

· Determination of current road distress conditions containing data useful for the planning of network wide maintenance and rehabilitation of roads in the Forest Service Regions of the pacific coast states.

· Existing pavement conditions vary and will be determined based on the distresses outlined in ASTM D 6433-20.

· Specific procedures to collect the data shall be submitted to the Forest Service for approval prior to beginning field data collection.

· The distresses can be collected by automated means according to protocol set by FHWA, or as agreed upon in writing by the CO.

· Collection of images for distress detection shall be in accordance with AASHTO R 86-18, or as agreed upon in writing by the CO.

· Quantifying crack from collected images shall be in accordance with AASHTO R 85-18, or as agreed upon in writing by the CO.

· Determine IRI in accordance with AASHTO M 328 and ASTM E950, and certified according to AASHTO R56, or as agreed upon in writing by the CO. Calibrate equipment according to AASHTO R57, or as agreed upon in writing by the CO.

3.2 Business Practice Protocols

Develop and submit for approval Business Practice Protocols that satisfy the Federal Highway Administration (FHWA) Federal Lands Highways (FLH) requirements for completing Quality Control for the collection of data and include associated Protocols for data management of collected data points including the following:

· Route Identification Protocols

· See attachment for USFS Route Identification Minimum Requirement Definitions

· Field Data Collection Procedures

· Quality Control Plan

· Submit proposed procedures to ensure compliance with contract requirements.

· Describe the inspection, testing, calibration, and other activities to be performed during field data collection and data processing. Include methods, schedule, frequency. Include equipment specific procedures.

· Field checks of automated data collection methods and monitoring

· Sampling protocols to allow FHWA or Forest Service to do random quality checks to verify condition assessments.

Manually perform at least one field check per road, and at least 1 field check every 10 miles, or as needed based on approved protocol or changing road conditions. Manually performed field check data shall be submitted in a separate data file. In addition, provide automated equipment to the Forest Service for a period of 2 weeks so the Forest Service can perform quality assurance of the data collection (this is an optional pay item, to be awarded at the discretion of the Government).

3.3 Sampling Requirements

· Sampling shall be used for the determination of a PCI rating as a subset of the continuous data collection. Frequency of samples will be at least 5 samples per mile and up to 10 samples per mile.

· For segments with a PCI of < 40, sampling frequency may be reduced to a minimum of 3 samples per mile.

· The area of interest will be defined as an individual lane for a double-lane road, and the full-width for a single-lane road; use the area between the center of stripes (yellow and/or white lines) for video image distresses, and to edge of pavement for visually observed distresses (but no greater than 2 feet beyond the edge stripe).

· A sample shall be between 1,500 to 3,500 square feet in area, per the definition of sample limits given above.

Collect the following pavement surface distresses by either manual survey methods or automated methods to be incorporated into the protocols developed above:

· Longitudinal cracking (non-wheel-path)

· Transverse cracking

· Block cracking (collected as longitudinal and/or transverse cracking)

· Alligator cracking (including longitudinal cracking in the wheel path)

· Patching

Collect the following distresses by either manual methods or by windshield survey methods with protocols to be incorporated into the protocols developed above.

· Bleeding

· Bumps and sags

· Corrugations

· Depressions

· Edge cracking

· Joint reflections

· Lane/shoulder drop-off

· Polished aggregate

· Potholes

· Rutting

· Shoving

· Slippage cracking

· Swelling

· Weathering and raveling

Determine ride quality on IRI-based results.

Collect locations of road fill slope failures.

3.4 Requirements of Automated Data Collection Methods

Collect the following data for the identified roads, georeferenced with GPS and labeled to a linear roadway milepost designation. Note that some roads will have sections that change from asphalt pavement to short sections of aggregate surfacing; video imaging, and associated GPS and roadway milepost designation shall be collected, but no downward-facing imaging over aggregate surfacing will be required:

· Forward-facing and rear-facing (when required) high-resolution video

· Downward-facing high-resolution images

· Road number and milepost reference caption in images and video

· Accelerometer to collect IRI-based roughness All pavement condition data shall be in a format approved by the COR that can be uploaded to PAVER 7 for pavement evaluations.

3.5 Proof of Concept Review

Government and Contractor shall agree upon a set of road segments for proof of concept review. Proof of concept review shall include at least 10 miles of identified road segments.

Complete data acquisition for road segments in the agreed upon set for proof of concept review. Sampling and data collection for proof of concept will require data collection in all lanes on the roads selected by the contractor.

· Process data and provide PCI ratings for government review based on ASTM D 6433-20.

· Provide a file compatible with PAVER 7 and in a format approved by the COR within 30 days of data initially collected.

· Provide the deliverables as listed in the section “Final Deliverables.”

· Provide manual field check data for Quality Control.

· Allow 15 days for government review of data and obtain approval from CO before proceeding with data collection after proof of concept review.

3.6 Submittals

Provide Business Practice Protocols within 30 days of the government’s Notice To Proceed. Allow 7 business days for government review.

Provide Proof of Concept Submittal for review within 30 days of collection data for Proof of Concept review. Allow 15 business days for government review.

· Optional Item: 30% submittal Government may exercise optional item to require a 30% submittal. Government and contractor shall agree upon a delivery date for 30% submittal.

Provide an interim deliverable of data collected on 30% of the road miles to include the following:

· Provide all raw data and appropriate software to be able to read the raw data.

· Provide manually collected Quality Control field check data in separate file, including all sampling information and location for manually collected data.

· Provide processed Data. Collect pavement roughness (IRI).

Provide data that can be uploaded into PAVER 7 software and in a format approved by the COR.

3.7 Final Deliverables

Provide final deliverables by June 30, 2023.

· Provide all raw data and appropriate software to be able to read the raw data.

· Provide manually collected Quality Control field check data in separate file, including all sampling information and location (lat/long) for manually collected data.

· Images and video collected in Automated Data Collection Methods.

· Provide processed data. Collect pavement roughness (IRI).

· Provide data that can be uploaded into PAVER 7 software and in a format approved by the COR.

· Integrate existing Forest Service PAVER 7 pavement management data into final deliverable.

· Optional Item: Maintenance and Rehabilitation Recommendation Report as described in Section 5 of this Statement of Work.

4. Gravel Roads and Unimproved Roads

4.1 General: The services to be provided include the following:

Determination of the current road distress condition containing data useful for the planning of network wide maintenance and rehabilitation of Forest Service gravel surfaced roads and unimproved roads. The Forest Service uses the following road surface type terminology:

“AGG - CRUSHED AGGREGATE OR GRAVEL” as gravel surfaced roads and “NAT - NATIVE MATERIAL”

Gravel Roads existing conditions vary and will be determined based on the distresses outlined in the PASER Gravel Roads Manual. Rate aggregate or gravel surfaced roads on a scale of 1 to 5 as outlined in the PASER Gravel Roads Manual, where 1 is failed and 5 is excellent.

Unimproved roads existing conditions vary and will be determined based on the distresses outlined in the PASER Unimproved Roads Manual. Rate unimproved roads on a scale of 1 to 4 as outlined in the PASER Unimproved Roads Manual, where 1 is poor and 4 is very good.

Use the latest versions of PASER manuals published by the University of Wisconsin-Madison Transportation Information Center. PASER manuals are available online: https://epd.wisc.edu/tic/resources/publications-available-for-download/

4.2 Business Practice Protocols

Develop and submit for approval Business Practice Protocols that satisfy the Federal Highway Administration (FHWA) Federal Lands Highways (FLH) requirements for completing Quality Control for the collection of data and include associated Protocols for data management of collected data points including the following:

· Route Identification Protocols

· See attachment for USFS Route Identification Minimum Requirement Definitions

· Field Data Collection Procedures

· Quality Control Plan

· Submit proposed procedures to ensure compliance with contract requirements.

· Describe the inspection, testing, calibration, and other activities to be performed during field data collection and data processing. Include methods, schedule, frequency. Include equipment specific procedures.

· Field checks of automated data collection methods and monitoring

· Sampling protocols to allow FHWA or Forest Service to do random quality checks to verify condition assessments.

Provide data collection equipment to the Forest Service for a period of 2 weeks so the Forest Service can perform quality assurance of the data collection (this is an optional pay item, to be awarded at the discretion of the Government).

4.3 Sampling Requirements

Sampling shall be used for the determination of a PASER condition rating. Sampling shall be continuous for the length of the road segment to be condition rated and shall identify the distresses and their locations.

The area of interest will be defined as the full-width of the road for both single and double lane roads.

Determination of current Gravel Road and Unimproved Road distresses shall be evaluated and rated using the appropriate PASER manual. Evaluate all items identified in the PASER manual and the following:

· Surface shape for proper drainage (crown, inslope, outslope)

· Identification of damage caused by surface water (rilling, gullying)

· Drainage feature condition (the ability of roadside ditches and under-road culverts to carry water away from the road).

· Gravel layer condition (depth and quality of aggregate)

· Surface deformation (washboard, potholes, ruts)

· Surface defects (dust, loose aggregate)

· Road fill slope failures

Record a georeferenced forward and backward view video of the road. All video and images shall include a road number and milepost reference caption.

4.4 Proof of Concept Review

Government and Contractor shall agree upon a set of road segments for proof of concept review. Proof of concept review shall include at least 10 miles of identified road segments.

Complete data acquisition for road segments in the agreed upon set for proof of concept review. Sampling and data collection for proof of concept will require data collection in all lanes on the roads selected by the contractor.

· Process data and provide PASER ratings for government review.

· Provide the deliverables as listed in the section “Final Deliverables.”

· Allow 15 days for government review of data and obtain approval from CO before proceeding with data collection after proof of concept review.

4.5 Submittals

Provide Business Practice Protocols within 30 days of the government’s Notice To Proceed. Allow 7 business days for government review.

Provide Proof of Concept Submittal for review within 30 days of collection data for Proof of Concept review. Allow 15 business days for government review

· Optional Item: 30% submittal Government may exercise optional item to require a 30% submittal. Government and contractor shall agree upon a delivery date for 30% submittal.

Provide an interim deliverable of data collected on 30% of the road miles to include the following:

· Provide all raw data and appropriate software to be able to read the raw data.

· Provide manually collected Quality Control field check data in separate file, including all sampling information and location for manually collected data.

· Provide processed Data.

4.6 Final Deliverables

Provide final deliverables by March 31, 2023.

· Provide all raw data and appropriate software to be able to read the raw data.

· Provide a georeferenced forward and backward view video of the road. All video and images shall include a road number and milepost reference caption.

· Provide segmented PASER ratings and observed distresses on a per mile basis, or a segment of a mile where a full mile cannot be surveyed.

· Provide road number and milepost of any observed fill failures.

· Optional Item: Maintenance and Rehabilitation Recommendation Report as described in Section 5 of this Statement of Work.

5. Optional Item: Maintenance and Rehabilitation (M&R) Recommendation Report

An all-inclusive final data collection and M&R report will be delivered to the Forest Service within 60 days of the completion of field data collection. Report to include the following items:

· Executive Project Summary

· List and Description of Route Segmentations

· Deterioration Rate Models

· M&R Matrix Plan

· M&R Recommendations based on the PCI values and/or distress types of each segment

5.1 Route Segmentation

Any route greater than 1 mile in length shall be segmented based on construction history. If construction history is not available and cannot be determined, segmentation will be governed by PCI values that reflect similar pavement deterioration. If PCI values are consistent, even breaks may be made. Segmentations should be updated in PAVER.

5.2 Deterioration Rate Models

The Contractor shall work with the Forest Service to determine representative deterioration rate models for all paved routes. Models will include Functional Class, Operational Maintenance Level, and a regional/elevation specific weight factor. Family models shall be created and stored in PAVER for use in development of the Maintenance and Rehabilitation plan.

5.3 M&R Matrix Plan

The Contractor shall work with the Forest Service to develop an M&R Matrix Plan for Localized, Global, and Major M&R. The Forest Service will provide approximate M&R costs for each Region.

6. Government Furnished Items:

1. Business Practice Protocols review and feedback.

2. List of routes

3. GIS layer showing routes to be surveyed.

4. Existing Forest Service PAVER 7 E70 file pavement management data.

Note: GIS layers showing optional roads to be surveyed may show more roads than what will be awarded. Roads to be surveyed will be dependent on available funding and will be negotiated with the contractor. Dependent upon results of Price-Redetermination, optional roads not included in the above data will be provided at time of addition through option exercise.

The Forest Service attribute tables use the following terminology to describe road surface types, which shall correspond to paved, gravel, and unimproved roads. If the existing condition of the road does not match the records in the Forest Service attribute tables, then perform work in accordance with the existing condition of the road segment.

7. Schedule: The final deliverables are due on the dates indicated above.

8. Quality Control / Quality Assurance: Consultant is responsible for the quality and accuracy of their work. The contractor shall provide the government the equipment used for automated data collection for two weeks so the government can collect data for quality assurance purposes (this is an optional pay item, to be awarded at the discretion of the Government). Dates for independent use of the data acquisition equipment shall be negotiated with the contractor.

9. Forest Service Review: Forest Service review of the work at the various submittals shall be for overall conformance with the project scope of work, design criteria, and generally accepted practices of the Pavement Engineering Field.

10. Key Personnel: The contractor shall provide key personnel that meet or exceed the following minimum qualifications/experience:

10.1 Project Manager: The project manager is the key point of contact interacting with the government personnel and the contactor’s personnel and subcontractors. The individual that the contractor identifies for this function must have the following minimum experience:

i. Within the last 3 years, experience and knowledge in Pavement Management Systems.

ii. 2 years experience as project manager on pavement management projects covering multiple states.