Solicitation 693C7322R000014.pdf

Road Inventory Services IDIQ SATOC

SOLICITATION NUMBER: 693C7322R000014

MAIN TABLE OF CONTENTS

SOLICITATION BOOK

PART I - THE SCHEDULE

SECTION TITLE

A Solicitation/Contract Form (SF-252) B Supplies or Services and Prices/Costs C Description/Specifications/Statement of Work E Inspection and Acceptance F Deliveries and Performance G Contract Administration Data H Special Contract Requirements

PART II - CONTRACT CLAUSES

I Contract Clauses

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

J List of Attachments Corporate Certificate Subcontracting Plan

PART IV - REPRESENTATIONS AND INSTRUCTIONS

K Representations, Certifications and Other Statements of Offerors or Respondents

L - Instructions, Conditions, and Notices to Offerors or Respondents

M – Evaluation Factors for Award

ARCHITECT-ENGINEER CONTRACT

1. CONTRACT NO.

2. EFFECTIVE DATE

3a. NAME OF ARCHITECT-ENGINEERING FIRM

3b. TELEPHONE NO. (include Area Code)

3c. ADDRESS OF ARCHITECT-ENGINEERING FIRM (include ZIP code)

CONTRACT ADMINISTRATOR NAME AND MAILING ADDRESS:

DUNS NO.:

4. DEPARTMENT OR AGENCY AND ADDRESS (include ZIP code)

Federal Highway Administration Eastern Federal Lands Highway Division 22001 Loudoun County PKWY Ashburn, Virginia 20147

5. PROJECT TITLE AND LOCATION

The Federal Highway Administration (FHWA), Eastern Federal Lands Highway Division (EFLHD), anticipates awarding a Single Award Task Order Contract (SATOC), Indefinite Delivery, Indefinite Quantity Contracts (IDIQCs) for pavement management data collection on the National Park Service paved road network as well as possible additional state and federal partners when future data needs are determined and required within the continental Unites Dates.

6. CONTRACT FOR (General description of service to be provided)

An Indefinite Delivery, Indefinite Quantity Contract to provide pavement management data collection on the National Park Service paved road network as well as possible additional state and federal partners for the EFLHD.

NAISC CODE: 541370

7. CONTRACT AMOUNT (Express in words and 2figures)

The Contractor’s-Fixed Price Rates Are Contained in Section B. The minimum guaranteed contract amount is $100,000.00 over the life of the contract and the estimated total contract amount is $5,000,000.00.

8. NEGOTIATION AUTHORITY

SF 252 is prescribed for use in awarding fixed-price contracts for architect-engineer services, as specified in 36.702(a). Pending issuance of a new edition of the form, Block 8, Negotiation Authority, is deleted.

9. ADMINISTRATIVE, APPROPRIATION, AND ACCOUNTING DATA:

SEE INDIVIDUAL TASK ORDERS

NSN: 7540-01-152-8072 252-102 STANDARD FORM 252 (REV. 10-83)

PREVIOUS EDITION NOT USABLE Prescribed by GSA FAR (48 CFR) 53.236-2(a) http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/36.htm#P371_67014

10. The United States of America (called the Government) represented by the Contracting Officer Executing this contract, and the Architect- Engineer agree to perform this contract in strict accordance with the clauses and the documents identified as follows, all of which are made a part of this contract:

Road Inventory Program Services Indefinite Delivery/Indefinite Quantity Contracts (IDIQC)

PART I - THE SCHEDULE

SECTION A - Solicitation/Contract Form SECTION B - Supplies or Services and Prices/Costs SECTION C - Description/Specifications/Statement of Work SECTION E - Inspection and Acceptance SECTION F - Deliveries and Performance SECTION G - Contract Administration Data SECTION H - Special Contract Requirements

PART II - CONTRACT CLAUSES

SECTION I - Contract Clauses

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

SECTION J – Corporate Certificate and Subcontracting Plan

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION K - Representations, Certifications and Other Statements of Offerors or Respondents SECTION L - Instructions, Conditions, and Notices to Offerors or Respondents SECTION M – Evaluation Factors for Award

If the parties to this contract are comprised of more than one legal entity, each entity shall be jointly and severally liable under this contract. The parties hereto have executed this contract as of the date recorded in Item 2.

SIGNATURES NAMES AND TITLES (Typed)

11. ARCHITECT-ENGINEER OR ANOTHER PROFESSIONAL SERVICES CONTRACTOR

A

B

C

D

12. THE UNITED STATES OF AMERICA

CONTRACTING OFFICER

STANDARD FORM 252 BACK (REV. 10-83)

SECTION B

SUPPLIES OR SERVICES AND PRICES/COSTS

CONSIDERATION AND PAYMENT

The minimum guaranteed contract amount is $100,000.00 over the life of the contract and the estimated total shared-contract amount is $5,000,000.

A. Cost Control. The Government will pay the Contractor for the full performance of the services required under the terms of each individual negotiated Task Order. This payment will be considered full compensation for the services required to complete the Task Order, including all profit and other costs incurred. The rates shown in this section will be in effect for the one-year base period and four one-year option periods, if exercised. The rates for years 2 through 5 include an annual cost of living escalation. Costs shall be subject to Government surveillance, including audit, and effective cost controls. All costs must be allocable, allowable, and reasonable as defined by the Federal Acquisition Regulation (FAR).

The labor rates that are effective at the issuance of a Task Order will remain effective throughout the duration of that Task Order and will apply to all Contract Modifications issued for the Task Order. The salary rates for a Task Order will not be adjusted for cost of living if the contract year changes during the duration of the Task Order.

B. Schedule of Fees. The following costing items are incorporated as part of the IDIQC:

1. Travel costs will be reimbursed in accordance with FAR 31.205-46 and the Federal Travel Regulation; at the applicable rates, current on the date that each individual Task Order negotiations are initiated. The negotiation initiation date will be the date of the Request for Proposal (RFP) letter from the Contracting Officer.

2. The contract labor rates will be a firm-fixed-price per contract period. The firm-fixed price of each Task Order will be based on types of labor categories required along with the number of labor hours negotiated for each labor category times the labor rate for the current contract period including the other cost factors as follows:

3. Costs Proposal This Indefinite delivery, indefinite quantity (IDIQ) contract solicitation will result in the award of a Single Award Task Order Contract (SATOC). The contract will be for a base year and four option years.

The cost proposal shall specify the total costs of each task as outlined in the technical proposal.

The contractor shall propose a per mile cost for data collection and data condition processing for the base year and for each option year. This total cost per mile will include all expenses related to each task; including but not limited to: planning and executing the task, contractor data preparation, vehicle maintenance/certification/verification testing, labor, travel & per diem, data collection at each site, and other items related to data collection (including LiDAR) and analysis/extraction. Each task order will contain data collection sites and time restraints for collection and delivery.

The cost information should be provided in the format shown in Table 3. Any assumptions made in preparing the cost estimate should be clearly defined.

End of Section B

Contract Tasks

Task A - Road Pavement Data Collection - Costs ($) per mile Base Year $

Option Year 1 $

Option Year 2 $

Option Year 3 $

Option Year 4 $

6-month Extension $

Task B - Data Processing and Analysis - Costs ($) per mile Base Year $

Option Year 1 $

Option Year 2 $

Option Year 3 $

Option Year 4 $

6-month Extension $

Task C - Standalone Data Viewing Software and Online Data Viewer Total Cost $

Task D – LiDAR Data Collection - Costs ($) per mile Pilot Collection $

Task E - Roadside Feature/Asset Collection and Reporting - Costs ($) per mile Base Year $

Option Year 1 $

Option Year 2 $

Option Year 3 $

Option Year 4 $

6-month Extension $

SECTION C

STATEMENT OF WORK

I. Abbreviations and Acronyms Acronym List AASHTO American Association of State Highway and Transportation Officials AC Alligator Cracking ASTM American Society for Testing and Materials CFLHD Central Federal Lands Highway Division COR Contracting Officers Representative DCV Data Collection Vehicle DMI Distance Measuring Instrument EFLHD Eastern Federal Lands Highway Division ESRI Environmental Systems Research Institute FHWA Federal Highway Administration GIS Geographic Information System GNSS Global Navigation Satellite System GPS Global Positioning System H3R Heavy Rehabilitation HPMA Highway Pavement Management Application IDIQ Indefinite Delivery, Indefinite Quantity IRI International Roughness Index L3R Light Rehabilitation LC Longitudinal Cracking LiDAR Light Detection and Ranging LRMS Laser Rut Measurement System LRS Linear Referencing System LTPP Long-Term Pavement Performance Program MAE Maximum Allowable Extent MIRE Model Inventory of Roadway Elements MP Mile point MRL Manually Rated Lane MUTCD Manual on Uniform Traffic Control Devices NPS National Park Service OC Operating Characteristics PCR Pavement Condition Rating PM Project Manager PMS Pavement Management Systems QC Quality Control R3 Reconstruction RCI Roughness Condition Index RIP Road Inventory Program SATOC Single Award Task Order Contract SCR Surface Condition Rating SDF Standard Data Format SOW Statement of Work TC Transverse Cracking TPP Transverse Pavement Profile

Definitions & Acronyms.

Contractor - The Architect-Engineer firm awarded the contract to perform the professional services described in this contract document.

Contracting Officer (CO) - The person who has the authority to enter, administer, and/or terminate contracts and make related determinations and findings.

Contracting Officer's Representative (COR) - The person who has the authority to give the Contractor technical direction only. The COR does not have the authority to change the terms and conditions of the contract or to give directions that incur additional cost.

Deliverable Items - Items that the Contractor provides to the Government under the terms of the contract, and/or the individual Task Orders, such as reports, documents, plans, maps, test results, computer disk or CD’s and any other specified items. These items are usually subject to acceptance and/or approval by the CO or COR.

FAR - Federal Acquisition Regulation.

Government - The Eastern Federal Lands Highway Division (EFLHD) of the Federal Highway Administration (FHWA) of the United States Department of Transportation.

IDIQC - Indefinite Delivery, Indefinite Quantity Contract - Contract Type.

NAICS - North American Industry Classification System Code. Determines business size (Large/Small). The classification code for this contract action is 541370.

Option Period/Year - One contract period that is 12 months in length.

Statement of Work (SOW) - The detailed description of the project or elements of work, and an outline of the services required, responsibilities of the parties, and other information necessary to complete the contract work.

TAR - Transportation Acquisition Regulation.

Task Order - An individually funded order with its own unique SOW issued against the basic contract SOW, terms, and conditions, to carry out a specific project for the Government.

Each Task Order will be awarded in accordance with FAR 16.500(d) and the evaluation procedures in FAR 36.6. A Statement of Work shall be issued for each individual Task Order.

STATEMENT OF WORK SPECIFICATIONS

FOR ROAD INVENTORY PROGRAM (RIP)

DATA COLLECTION, PROCESSING, AND VIEWING

II. Introduction The Eastern Federal Lands Highway Division (EFLHD) of the Federal Highway Administration (FHWA) is responsible for providing transportation engineering services for planning, design, construction, and rehabilitation of the highways and bridges that exist on federally-owned lands or provide access to federal lands. In 1994, at the request of the National Park Service (NPS), the FHWA established a Road Inventory Program (RIP) and began collecting a complete inventory and performing pavement condition surveys on the roads, parkways, and parking areas within the NPS transportation network.

Currently, the EFLHD is preparing for the seventh data collection cycle for the NPS road network. In Cycle 7, the EFLHD will contract to collect an estimated 11,000 miles of paved road condition data for pavement management over 5 years in U.S. National Park Service units across all the 48 contiguous U.S. States and Washington, DC. The EFLHD may also contract to collect additional paved routes of other agencies (such as the U.S. Fish and Wildlife Service or Bureau of Reclamation, but not limited to only these) or additional NPS units when a need for data is determined.

III. Scope of Work EFLHD is seeking proposals for pavement management data collection on the National Park Service paved road network as well as possible additional state and federal partners when future data needs are determined and required. The contractor will provide the data collection vehicle(s), equipment needed, and the trained personnel to collect to the specifications detailed in this Statement of Work. The contractor-provided vehicle(s) shall collect data while traveling at or near the posted speed limit and all sensor data must be collected simultaneously in one pass.

Pavement data shall be analyzed to provide EFLHD with pavement roughness, rut depth, cracking, faulting, macrotexture, and other specified distresses. The contractor shall report condition ratings and distress index scores to EFLHD at specified intervals. Deliverables to EFLHD include pavement distress data (analyzed for condition index and rating scores), Global Navigation Satellite System (GNSS) information, downward pavement images, forward/backward video image logs, field equipment verification documents, data viewing software and/or online/website for video/data display, and other pertinent data as defined in this Statement of Work.

The scope of work for this contract does not include collection of routes that are manually rated (typically paved parking areas or unpaved roads/parking). While the EFLHD Road Inventory Program does collect data on these locations, they are not a part of the scope of work for this contract.

Contractors who submit proposals must have proven experience collecting pavement condition data on large road networks/systems such as statewide road networks. While the mileage for NPS Cycle 7 is low comparable to statewide road systems, the data can be logistically hard to obtain due to expansive, nationwide locations with unique climate and geographic characteristics that may limit time periods for data collection. Quality, verifiable data is paramount for this project to maintain the level of details and standards consistent with previous data collection cycles for the EFLHD Road Inventory Program and Pavement Management System. While some sites are small (very low mileage) and data collection may be completed in less than a day, EFLHD looks to stress completeness of data collection across the NPS road network. Site specific exceptions to data collection shall be communicated clearly and quickly between the EFLHD and the contractor.

During the solicitation phase of this contract, the proposers will be required to participate in an on-site technical field evaluation using their data collection vehicle and equipment as outlined in Section V, Technical Field Evaluation. The data collection vehicle/equipment being proposed by the contractor for performing the work for this contract shall provide equal or better performance than the collection vehicle used for the on-site evaluation tests. The technical field evaluation will evaluate the contractor’s ability to perform the work described in Tasks A and B (cracking identification and data analysis). The proposer is required to provide data in accordance with AASHTO MP 47-21 for the road sections included in the pavement cracking evaluation test. In addition, the proposer is required to provide the transverse pavement profile measurement data as required by AASHTO PP 106, 107, 108, and 109. The technical field evaluation will be April 19-20, 2022 in the metro Washington, DC area. For those planning to attend, a mandatory web meeting on April 7, 2022 at 12:00pm to 1:00pm Eastern Time is required to review the schedule, logistics and details of the on-site field-testing event. To join the web meeting see the instructions posted to sam.gov with solicitation documents. See Section V, Technical Field Evaluation within this Statement of Work for more details.

EFLHD is seeking proposals on the following tasks:

A. Road condition data collection using contractor provided vehicle(s) and equipment

B. Pavement condition data processing and analysis

C. Standalone data viewing software and/or online/website for video/data display to interpret results

D. LiDAR road data collection – on a subset of network miles with contractor equipment and performed by contractor

E. Roadside features/asset extraction and database population from collection vehicle images

Proposers responding to this solicitation should demonstrate experience in the following areas:

1) The successful fabrication of automated road data collection vehicles that collect pavement management data in one pass traveling at or near posted speed limits for at least three state Department of Transportation or other Agency within the last 3 years.

2) Scheduling and accurate pavement condition collection of small and large road networks for network-level pavement management, with clear Quality Control plans created and maintained.

3) Accurate and timely processing of road condition data on large road networks within proposed schedules. Processing includes rut depth, roughness, cracking, faulting, and macrotexture analysis/identification. Additionally, road geometric characteristics such as width measures crossfall, grade, and heading are collected and reported during post-processing.

4) Experience with collection of Global Navigation Satellite System (GNSS) information collected in accordance with an Agency’s linear referencing system (LRS).

5) Ability to store, display, and perform analysis on road condition data and video (downward facing pavement images and forward/backward video log images) via standalone software program and/or through a contractor hosted data service for web-based data viewing.

6) Ability to collect, extract, and view LiDAR data collected at speed along roadways.

7) Ability to extract roadside asset inventories from video and populate database. Ability to view the asset inventory in the data viewing software.

IV. Project Tasks - Descriptions, Schedules, and Deliverables

The proposed project structure includes 5 tasks, which EFLHD may exercise at any point throughout the contract (with agreed upon notification given). The contractor shall perform the tasks specified below for this project and shall work closely with designated EFLHD personnel to accomplish this work. Within each of the project Task descriptions that follow, a list of separate Appendix documents is included to support and describe the work for each Task. The Appendices should be reviewed for project guidance and requirements.

The complete list of Appendices to reference is listed here:

o Appendix A: Location List (Excel Version) o Appendix B: Data Collection Protocols and Database Population o Appendix C: Scheduling, Pre-Data Collection Information, and Vehicle Certifications &

Verifications o Appendix D: Video Measurements o Appendix E: Distress ID Manual o Appendix F: Quality Assurance Manual o Appendix G: Viewing Software Specifications o Appendix H: Roadside Features Inventory Guide o Appendix I: Sign Inventory Guide o Appendix J: Database Data Dictionary o Appendix K: Past Performance Evaluation Questionnaire o Appendix L: Evaluation Site Submittal

Task A: Contractor Pavement Data Collection using Contractor Provided Vehicle(s)

This phase will last a significant duration of the contract (planned for 5 years). The contractor will be provided with route identification information and locations (GIS) of paved roads to collect condition data and images using a data collection vehicle. After award of IDIQ and the subsequent task order(s), EFLHD will provide a list of sites for data collection. The sites to be collected are in the lower 48/continental United States and District of Columbia. Sites with more than 5 paved miles are scheduled to be collected twice over the course of the 5-year contract and the lowest mileage sites are collected only once. Approximately 2,500 to 3,000 miles will be collected each year, with the base year including fewer miles to ensure data collection and analysis are fully acceptable. EFLHD shall provide a 6-month notice should more than 3,000 miles be collected annually. Table 1 provides a summary of paved mileages for the NPS regions.

Table 1: Summary of Paved Mileage and Sites by NPS Region

NPS REGION

FIRST COLLECTION SECOND COLLECTION

MILEAGE No. OF SITES MILEAGE No. OF SITES

INTERMOUNTAIN 1648 70 1615 42

MIDWEST 196 30 169 11

NATIONAL CAPITAL 259 16 251 12

NORTHEAST 496 40 462 16

PACIFIC WEST 1400 39 1382 25

SOUTHEAST 1547 40 1512 17

TOTAL 5545 235 5391 123

During data collection, the contractor will be expected to submit information back to EFLHD to report the status (completeness) of data collection and change tracking for route collection that does not match the previous cycle’s collection. The contractors will also perform regular checks or verifications on collection vehicle(s) and report the results of these tests to EFLHD. In addition to monthly/weekly checks, verification sites will be required before and after collection of larger mileage locations (>10 miles).

A cost per mile shall be proposed from the contractor for data collection. The cost per mile shall encompass all expenses related to planning and executing the data collection trip such as data preparation, vehicle maintenance/certification/verification testing, labor, travel & per diem, data collection at each site, and other items related to data collection.

Task A Supporting Appendix documents:

• Appendix A – list of National Park Service sites for data collection with estimated paved mileage and number of planned collections (subject to change)

• Appendix B – protocols to ensure correct data collection prior to and after collection

• Appendix C – description of schedule and timeline for data collection and the information shared before and during data collection such as equipment verifications, calibrations, and other data quality submittals.

Schedule and Deliverables

Task A includes the collection of parks or sites agreed upon for each contract Task Order. The deliverables and pertinent information is described in the supporting Appendix documentation and include:

1. Pavement condition data collected using contractor provided automated data collection vehicle(s) that collect pavement management data in one pass traveling at or near posted speed limits. Pavement data collection including all sensor, image, road geometric and GNSS data. Pavement distress detection of rut depth, cracking, faulting, roughness, macrotexture, and other EFLHD specified distresses. See Table 2 in Section VI for all desired data collection vehicle specifications.

2. Contractor provided data collection schedules for each Task Order and group of sites defined by EFLHD.

3. Key communication documents from the contractor notifying EFLHD about daily route collection status, vehicles used for data collection, collection exceptions, and collection changes.

4. Contractor provided vehicle/equipment routine maintenance and certification, calibrations and verification tests.

5. Post-collection communications to ensure complete and accurate data collection before post-processing.

It is the goal of the EFLHD to ensure a clear understanding of how routes are to be collected, i.e.

where to start/end each route, what lane to collect, and any other unique situations occurring along the route. Accurate data collection will eliminate the need for the contractor to re-visit sites to correct errors in collected data. Therefore, communication/data submittal protocols are defined to ensure correct data collection prior to departing each site.

The contractor will be expected to identify and note collected routes that have geometry, length, and/or surface type changes, as well as any other item that is preventing collection of the route as expected in the pre-trip data. It is the goal of EFLHD to know these changes prior to collection, but all situations may not be known in advance of collection.

The data provided (GIS/shapefiles) will contain the route geometry from the last cycle’s collection and may include updates from communications with sites prior to the contractor’s arrival.

The contractor is expected to start and stop data collection of routes based on written descriptions and GIS information. If changes in collection start/stop, geometry, or length occur, those exceptions shall be noted and EFLHD shall be alerted of those exceptions within 1 week of data collection. EFLHD will advise on how to proceed with the processing of those changed routes within 10 business days of the notification. Justifiable exceptions are allowed and do not indicate incomplete collection of a road or site. However, routes collected incorrectly or without noted exceptions, may necessitate proper re-collection of road or non-payment.

If the contractor needs a decision from EFLHD due to collection varying from the pre-collection description, the COR will advise on any adjustment to the due date for the site’s data submittal.

Access to some roads could be restricted at time of collection. The contractor will work with EFLHD and the agency owning the road (likely the U.S. National Park Service), to gain access to these routes. Roads with seasonal closures may have pavement obscured due to debris; the contractor will work with EFLHD to determine the best course of action or optimal time to collect in these cases.

All vehicles used for pavement data collection shall be tracked and adhere to the following industry standards and protocols for EFLHD data collection when applicable (also listed in Section VI, Table 2, Part 12 for Technical Standards):

AASHTO

• M 328-14: Standard Specification for Inertial Profiler

• R87-18: Determining Pavement Deformation Parameters and Cross Slope from Collected Transverse

Profiles

• R 43-13: Quantifying Roughness of Pavements

• R 54-14: Standard Practice for Accepting Pavement Ride Quality when Measured using Profiling Systems

• R56-14: Inertial Profiler Certification

• R57-14: Standard Practice for Operating Inertial Profiling Systems

• R 85-18: Standard Practice for Quantifying Cracks in Asphalt Pavement Surface from Collected Pavement

Images Utilizing Automated Methods

• R 86-18: Standard Practice for Collecting Images of Pavement Surfaces for Distress Detection

• R 87-18: Standard Practice for Determining Pavement Deformation Parameters and Cross Slope from

Collected Transverse Profiles

• R 88-18: Standard Practice for Collecting the Transverse Pavement Profile

• MP 47-21: File Format of Two-Dimensional and Three-Dimensional (2D/3D) Pavement Image Data

• PP106-21: Assessment of Static Performance in Transverse Pavement Profiling Systems

• PP107-21: Assessment of Body Motion Cancelation in Transverse Pavement Profiling Systems

• PP108-21: Assessment of Navigation Drift Mitigation in Transverse Pavement Profiling Systems

• PP109-21: Assessment of Highway Performance in Transverse Pavement Profiling Systems

ASTM

• E1703/E1703M-10: Standard Test Method for Measuring Rut-Depth of Pavement Surface using a Straightedge

• E1845-15 – Standard Practice for Calculating Pavement Macrotexture Mean Profile Depth

• E2560-17 - Stand Specification for Data Format for Pavement Profile

• E867-06 – Terminology relating to Vehicle-Pavement Systems

• E950/E950M-09 – Standard Test for Measuring Longitudinal Profiles

• E1926-08 – Computing IRI for roads from Longitudinal Profile

Longitudinal Profiler Certification Any vehicle used to collect data for EFLHD on any task order issued under the awarded IDIQ shall be certified for ride quality at the Texas A&M Transportation Institute, National Center for Asphalt Technology, or with EFLHD approval, a similar ride quality certification organization that uses AASHTO R56-14 or TxDOT Test Method Tex-1001-S. This certification will be the responsibility of the contractor to perform and facilitate. For each site to be collected, each data collection vehicle shall be certified within the last 12 months. The contractor shall submit annually and upon contract award the certification documentation for each vehicle intended to be used to accomplish the data collection.

Transverse Profile Certification The AASHTO transverse pavement profiler certification standards (AASHTO PP 106, 107, 108 and 109) are under national validation testing at this time. It is expected that EFLHD will require the contractor to have a data collection vehicle tested in accordance with these standards not more than annually. The data collection vehicle will be required to provide the data as required by these standards, but the vehicle will not be required to meet the certification requirements. Further information on the transverse pavement profiler certification tests can be found in the following publication:

FHWA-RC-20-004, https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1109.

EFLHD will coordinate with the contractor on the location and date for the testing.

Pilot Collection (Initial Data Collection Efforts) After contract and task order award, the contractor shall join the EFLHD team for a pilot collection at an agreeable site location. EFLHD will be on site to observe calibration/verification procedures and data collection procedures. The main goal for EFLHD will be to observe collection practices, collection vehicle operations, the resulting data, as well as to answer any questions the contractor may have.

https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1109

Task B: Data Processing and Analysis

Data collection is expected to begin with the first task order in Summer 2022. After contractor completes data collection at a site, the contractor shall analyze/process the data by summarizing results in 0.02-mile intervals for loading into the EFLHD Pavement Management System.

A cost per mile shall be proposed from the contractor for data analysis and database population.

Data processing and database population should be sequenced in the order sites are collected in each new task order. The database shall be populated with the following distress extents and indexes:

• Cracking/Faulting – identification and severity

• Rutting

• Roughness

• Macrotexture

• Geometric Attributes

• GNSS locational data

• Calculations for Surface Condition Rating (SCR) and Pavement Condition Rating (PCR)

Task B Supporting Appendix documents:

• Appendix B – description and details of data processing activities

• Appendix D – road measurements from video

• Appendix E – manual on pavement distress identification and index calculation

• Appendix F – quality assurance manual for data analysis

• Appendix J – Database Data Dictionary

1. Kick-off meeting with EFLHD staff to discuss the scope of work for Task B which includes the proposed data analysis expectations, proposed schedule for data processing, details of database population, and specific project roles and responsibilities.

2. A written Quality Control (QC) Plan that ensures all work conforms to the contract requirements and specifications presented in this solicitation and its appendices. The QC Plan shall be approved by the EFLHD before the start of the first task order. The finalized QC Plan should be submitted at least 7 days before the project kick-off meeting.

EFLHD throughout the project will implement its own quality control program and include comprehensive quality checks of all phases of the contractor’s work.

3. Progress meetings will be conducted monthly and possibly more frequently at the beginning of the contract to ensure accuracy and complete understanding of data submittals. Additionally, the contractor shall assume a maximum of three, 1-day in-person progress meetings to be held in the Ashburn, Virginia or Denver, Colorado area over the life of the contract. The remainder of the monthly meetings will be held via conference call. The contractor shall be responsible for setting up the conference calls. The purpose of these meetings is to ensure the project stays on schedule and within budget, to resolve project issues, and to maintain a positive working relationship between the contractor and EFLHD.

4. For each meeting conducted, the contractor shall prepare the meeting minutes and submit the minutes to the COR within seven calendar days after the meeting.

5. For each site collected, the processed data, video, and populated database will be due back to EFLHD within 30 business days. Data processing services provided by the contractor includes:

a. Perform detailed data analysis at 0.02-mile intervals on the downward pavement images identify pavement distress/crack type, faulting (if applicable), severity, and quantities. EFLHD will periodically perform field crack mapping verifications of processed pavement images of contractor. This is done to verify that contractor is adhering to distress ID manual protocols. Contractor will work with EFLHD to reconcile differences between EFLHD field verifications and analyzed data submitted by the contractor.

b. Populate the ROAD_CONDITION table within the database with calculated index values for pavement distress types, roughness, rutting, and macrotexture. Condition index scores for Surface Condition Rating (SCR) and Pavement Condition Rating (PCR) shall also be computed in the database.

c. Populate the WIDTHMEASURE table within the database for roadway width measurements (lane and pavement) using forward camera view images. Develop procedures and methods to perform roadway width measurements on the images that will satisfy the criteria in this SOW .

d. List of tables to be populated by the contractor with details provided in appendix documentation:

i. CUMULATIVE_STATUS

ii. EXCEPTION_NOTES

iii. ROAD_CONDITION

iv. ROUTE_GPS

v. ROUTE_GPS_C7

vi. ROUTE_ID

vii. WIDTH_MEASURE

e. Table 2, Part 9 lists required GNSS and geometric data to be included in the populated database.

Task C: Standalone Data Viewing Software and Online Data Viewer

EFLHD requires a data viewing system that allows for viewing/editing of data and video that is maintained, stored, and owned by EFLHD. Additionally, a viewing system that utilizes contractor-hosted data/video that is viewed via an online website for easy dissemination to partner agencies and outside stakeholders is needed. This may or may not be 2 separate systems, and other variations of data viewing other than the description below can be submitted in the contractor’s proposal.

Any costs proposed for the standard viewing software shall include licenses for unlimited users.

The contractor shall provide EFLHD with the ability to view, QC, and edit processed road condition data, geometric data, and roadside features data that is synchronized with digital video images stored at EFLHD. This method of data viewing is intended to be used by subject matter experts at EFLHD and others as needed.

The contractor shall also provide online data viewing of contractor-hosted digital images (roadway views and downward facing pavement views), maps/location information, and collected road condition information (charts/tables). The online method of viewing data is intended for very easy sharing to many people across FHWA and partner agencies for the purposes of using the road inventory data for decision making.

Task C Supporting Appendix documents:

• Appendix G – requirements of the data viewing software/online viewer

Viewing software shall be provided prior to or at the conclusion of the first data collection submittals. The contractor will update software as needed or repair all software bugs identified by EFLHD within 90 days of the software’s delivery date. The contractor shall provide support, training, and updates to the software over the life of the contract.

Deliverables for this task include:

1. Viewing software with licenses for unlimited users that meets the requirements described in Appendix G and also Section VI, Table 2, Part 10 within this Statement of Work.

2. Demonstration of standalone viewing software and/or online data viewer.

3. User Guide or Instruction Manual for data viewing system(s).

4. Software updates, troubleshooting support, and training as needed over the life of the contract.

Task D: LiDAR Data Collection

In addition to regular road surface condition data collection, EFLHD is exploring collection of LiDAR data (Light Detection and Ranging) at select sites throughout the country. Currently, there is no expectation to collect LiDAR data on the entire National Park Service road network.

This contract may be used to collect LiDAR data on a small number of miles (500 miles or less) to gain understanding with the management of LiDAR data and determining the LiDAR data needs of internal customers. This task would be only executed at the direction of EFLHD via a task order. LiDAR data collection would consist of driving the roads at the posted speed limit while using a LiDAR scanning device to collect positional and intensity information on the roadway and surrounding objects near the road. The vehicle used for LiDAR collection does not have to be the same vehicle used for the pavement condition collection in Task A.

LiDAR data should not be collected during rainstorms, dust storms, with snow cover, at night or during any other factor that will obscure image/data quality.

EFLHD is asking proposers to describe their approach to the following:

• LiDAR data collection

• Feature extraction from collected LiDAR data

• Value-added features or services relating to LiDAR

• Data ownership and storage

• Data validation and quality control

• Deliverable format (for data viewing) and conflation with linear referencing system

No data dictionary or supporting documents are provided because EFLHD is exploring all approaches to provide a very good pilot collection of LiDAR data to determine next steps for additional collection and data needs.

A cost per mile shall be proposed from the contractor for LiDAR data collection (<500 miles).

The cost per mile shall encompass all expenses related to planning and executing the data collection trip such as data preparation, vehicle maintenance/certification/verification testing, labor, travel & per diem, data collection at each site, and other items related to data collection.

Schedule and Deliverables

Similar to regular road surface condition data collection, this collection would be solely completed by the contractor with their own equipment and collection team. EFLHD would give the contractor at least 6 months advanced notice to collect the data, with specific routes and locations to collect. The contractor would be expected to deliver LiDAR files, online viewing software access and/or other LiDAR viewer, video files and other pertinent data within 60 business days of collection.

Task E: Roadside Feature/Asset Collection and Reporting

EFLHD is requesting a proposal to collect, identify and report roadside features or assets from the video obtained in Task A. Where applicable, the assets need to be visible/identified on the roadway video (e.g. box drawn around asset on image). The contractor would populate database tables with inventoried roadside features according to contract specifications in the supporting Appendix. Locations of assets would be identified by milepost and latitude/longitude coordinates. The contractor will not report the condition of assets.

Many sites are planned to be collected for condition data more than one time over the duration of this contract. However, the roadside asset inventory would only need to be collected once and not each time a road is driven for condition. Each task order would describe the sites and routes needing a roadside feature inventory. The reporting of the asset inventories can happen over a longer period than the reporting of pavement distress and conditions, and a deadline for submittal of asset inventories will be provided in each task order.

A cost per mile should be proposed from the contractor for approximately 5,600 miles of asset/features inventories.

Task E Supporting Appendix documents:

• Appendix H – description of asset types and attributes to be inventoried from vehicle images.

• Appendix I - Sign Inventory Guide

• Appendix J – Database Data Dictionary

1. Populated FEATURES table within the database with roadside features inventories for each road needing assets inventoried

2. Assets/Features are to be located using mileposts and latitude/longitude coordinates.

3. Identification of asset types and attributes for each element according to the supporting

Appendix.

4. Identify roadside features in the roadway video collected in Task A to be viewed in the data viewing software system(s) in Task C.

V. Work Performed By EFLHD In support of the project, EFLHD will provide a project manager(s) to oversee the contractor’s work at each site and to provide support as needed. Additional duties EFLHD will perform include the following:

1. Staff resources as required to meet with the contractor and to provide information that may be required for collection.

2. Technical and administrative documentation of available manuals, written policies and procedures, organizational charts, records, or documentation as needed to assist in the processing and delivery of the collected data.

3. Route inventories and location information shall be provided for the contractor to collect the data accurately. Previous collection video will also be available if requested.

4. Access to EFLHD staff and EFLHD contractors or NPS personnel, offices, and/or data needed to complete the work activities.

5. Clear direction for any unique situations that arise on a site-by-site basis.

6. Additional work performed by EFLHD may be defined in the supporting Appendix documentation.

VI. Technical Field Evaluation To obtain more information about each contractor’s ability to perform the work on this contract, an on-site collection vehicle evaluation will be scheduled during the solicitation period. This on-site evaluation will provide EFLHD with information on the contractor’s ability to successfully perform Task A. Additionally, during the on-site evaluation the contractor will participate and provide results for the AASHTO Transverse Pavement Profile (TPP) Tests and Standard Data Formats (SDF) described below. The contractor will be responsible for providing a data collection vehicle needed to perform these field evaluations. EFLHD will be providing the test equipment. Additionally, the data collection vehicle being proposed by the contractor for this contract shall provide equal or better performance than the collection vehicle used during the on-site evaluation.

The on-site evaluation tests are expected to be performed over a 2-day period on April 19-20, 2022. The location will be in the Washington, DC metro area. There will be no compensation for this required evaluation.

Mandatory: On April 7, 2022 at 12:00pm to 1:00pm Eastern Time a mandatory pre-evaluation web conference meeting will be scheduled for all contractors participating in the on-site evaluation. Instructions to join the meeting will be posted with the contract files and documentation. During the meeting the expectations and logistics for the tests and test results will be reviewed in an effort to have the evaluation run smoothly. All contractors planning to participate in the on-site evaluation shall RSVP to EFLHD.AE@dot.gov by 4:00 PM Eastern Time on April 11, 2022 (2 business days after the web conference meeting). The RSVP email subject line should plainly identify the solicitation number and project name “693C73-22-R- 000014 RIP DATA COLLECTION, PROCESSING, AND REPORTING.” Within the email the contractor shall state their name, address, and telephone number.

mailto:EFLHD.AE@dot.gov

For the purposes of evaluating the contract proposals the following will be considered related to the Technical Field Evaluation:

1. Evaluation of the accuracy of pavement distress and severity identification according to the EFLHD Distress ID Manual definitions (see Appendix E)

2. Submittal of pavement distress identification in HPMS format

3. Submittal of distress data using Federal Lands distress format (see Appendix L)

4. Submittal of Standard Data Format (AASHTO MP 47) of collected pavement data

5. Submittal of Transverse Pavement Profile tests measurement data

The contractor’s equipment (data collection vehicle) will be required to perform the tests and provide final data as specified for the TPP and the SDF. The equipment will not be required to meet the TPP certification requirements.

Pavement Cracking Evaluation Test

In the first test, proposers should plan to demonstrate their ability to collect, reduce, and present pavement data over ten 0.3-mile segments that are selected to contain pavement characteristics representative of Federal Lands’ roads.

The proposers will submit results identifying distress type and severity per 0.03-mile sub-segment per the EFLHD Distress ID Manual definitions (see Appendix E) . The distress types to be identified include transverse cracking, longitudinal cracking, alligator cracking, and patching/potholes. Please note, the distress analysis does not have to follow the requirement described in Task B, but rather by populating a simplified spreadsheet which is attached as Appendix L.

Additionally, the evaluated cracking data shall be reported per 0.03-mile sub-segment in accordance with the HPMS field manual chapter 4 item 52, cracking percent, which can be found at: https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/page00.cfm

The results will be evaluated for cracking identification and severity by comparing manual crack mapping assessments done by the EFLHD-RIP team and/or by third party. Further information on the assessment analysis can be found in the following publication, FHWA-RC-20-005, https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1119

The digital image data for the ten 0.3-mile segments shall be delivered in accordance with AASHTO MP 47 File Format of Two-Dimensional and Three-Dimensional (2D/3D) Pavement Image Data with both binary and .CSV file formats. The image quality (clarity and resolution) in the standard data file format shall be equivalent to the image quality used in the proposer’s image processing software for distress reporting.

Contractor shall provide information regarding the number of pixels per image and the associated fill factor. The image shall be collected with a uniform and consistent form of illumination applied to the pavement surface. The illumination shall be regulated to provide sufficient contrast and crack-shadows for the clear discernment of cracking and patching.

Images bearing ambient and/or vehicle shadows that obscure pavement features will not be accepted.

Further information on the standard data format can be found in the following publication:

FHWA-RC-20-001, https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1108 https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/page00.cfm https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1119 https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1108

Transverse Pavement Profile Test The data collection equipment will be required to provide the transverse pavement profile measurement data as required by AASHTO PP 106 Annex B, PP 107 Annex B, PP 108 Annex A, and PP 109 Annex A.

The equipment will not be required to meet the certification requirements for the TPP. The data will be used for information only. Further information on the transverse profiler testing can be found in the following publication: FHWA-RC-20-004, https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1109

Schedule and Deliverables

Submit results from the technical field evaluation, to be included as part of the complete proposal package by this solicitation’s due date. Results for the technical field evaluation include:

1. Submittal of pavement distress and severity identification according to the EFLHD Distress ID Manual definitions in Appendix E

2. Submittal of pavement distress data in HPMS format

3. Submittal of Standard Data Format (SDF) (AASHTO MP 47) of collected pavement data

4. Submittal of Transverse Pavement Profile (TPP) tests measurement data

5. All results must be submitted with clear identification of the contractor name, test name/description, road segment location, and in the format described above.

https://www.fhwa.dot.gov/pavement/pub_details.cfm?id=1109

VII. Technical Specifications of vehicle(s) to be used for data collection The required specifications for the vehicle(s) to be used to collect the condition data are outlined in Table 2. In the response to this solicitation, the contractor should follow the format used in Table 2 to describe their vehicles capabilities and any adjustment or clarification required.

Table 2: Data Collection Vehicle/Equipment Specifications No. Feature

Can this feature be provided as described

(Yes or No)?

Variance

1. Operating conditions for collection a.

The contractor shall ask permission from the EFLHD prior to using their vehicle in any advertising, photographs, illustrations, or by reference. Inclusion on a list of customers as a statement of fact is acceptable.

b. The vehicle, shall be able to collect in ambient air temperatures ranging from 10°F to 120°F.

c. The vehicle shall be able to collect at elevations up to 12,000 feet above sea level.

2. Safety and other protocols

a. While in full…