FA805126Q4001

PERFORMANCE WORK STATEMENT (PWS)

FOR

PAVEMENT CONDITION INSPECTION

STUDIES FY26

AT

AIR FORCE INSTALLATIONS

4 June 2026

TABLE OF CONTENTS

1. GENERAL

2. SCOPE

3. APPLICABLE DOCUMENTS

4. CONTRACT MANAGEMENT, PLANNING, AND REPORTING SERVICES

4.1. Monthly Status Report (MSR)

4.2. Conference Minutes

4.3. Notification Requirements

4.4. Project Planning Chart (PPC)

4.4.1. Site Briefings

4.5. Airfield Driving and Flight Safety

4.6. Quality Assurance/Quality Control Plan

4.7. Contractor Manpower Reporting

4.8. Qualifications of Personnel

5. TECHNICAL SERVICES

5.1. Technical Investigation

5.1.1. Pavement Area Summary

5.1.2. Pavement Real Property Inventory Mapping and Segmentation

5.1.2.1. Inventoried Surfaces

5.1.2.2. Common Installation Picture

5.1.2.3. Real Property Data in PAVER

5.1.2.4. Installation Housing

5.1.2.5. Paved Airfield Shoulders

5.1.2.6. AGE Storage Aprons

5.1.2.7. Wash Racks

5.1.2.8. Curbs and Gutters

5.2. PCI Inspection Requirements

5.2.1. CADD/GIS Mapping Project Requirements

5.2.1.1. CIP Vector Data

5.2.1.2. Area Validation

5.2.1.3. PAVER Database Updates

5.2.1.4. CIP Updates

5.2.1.5. GPS

5.2.2. Pavement Condition Inspection

5.2.2.1. As-Built Drawings

5.2.2.2. Interviews

5.2.2.3. Pavement Identification

5.2.2.4. Sampling Rates, Airfield Networks

5.2.2.5. Sampling Rates, Roads and Parking Networks

5.2.2.6. PAVER Data Entry

5.2.2.7. Photography

5.2.2.8. PCI Ratings

5.2.3. Automated PCI Inspection: Alternate Methods and Approval

5.2.3.1. Data Quality Standards for Automated Measurement of Pavement Attributes:

5.2.3.2. Equipment, Technology, and Software Tool Requirements

5.2.3.3. Distress Feature Identification

5.2.3.4. Data Acquisition Methodology

5.2.4. sUAS Operations for Pavement Condition Index (PCI) Data Collection

5.2.4.1. sUAS Approvals

5.3. Deliverable Package (CDRL D001)

5.3.1. Executive Summary

5.3.1.1. Introduction and Purpose

5.3.1.2. Background Information

5.3.1.3. Major Projects

5.3.1.4. Key Findings

5.3.1.5. Summary Tables

5.3.1.6. Seven-color PCI map

5.3.2. Updated PAVER database

5.3.3. Excel Workbook

5.3.3.1. Overview of PCI results

5.3.3.2. Projected PCI Table

5.3.3.3. Maintenance and Repair (M&R) Requirements

5.3.3.4. Comparison of Budget Scenarios

5.3.3.5. Prioritized List of Major M&R Projects

5.3.3.6. List of Consequence of Localized Distress Maintenance

5.3.3.7. Real Property Summary

5.3.3.8. PAVER/RPAD Comparison

5.3.3.9. PCI Deterioration Rate Summary

5.3.3.10. Branch Use Inventory

5.3.3.11. Pavement Surface Type

5.3.3.12. Summary of Area-Weighted Average Condition by Rank

5.3.3.13. Sections Not Inspected

5.3.3.14. Pavement Condition Index Results

5.3.3.15. FOD Potential Information (Airfields Only)

5.3.3.16. Structural Results (Airfields Only)

5.3.3.17. Friction Characteristic Results (Airfields Only)

5.3.3.18. Engineering Assessment Summary Tables (Airfields Only)

5.3.3.19. Budget Details

5.3.3.20. Family Models for Condition Deterioration Prediction

5.3.3.21. Distribution List and References

5.3.4. Appendix A: Maps

5.3.4.1. Map A1

5.3.4.2. Map A2

5.3.4.3. Map A3

5.3.4.4. Map A4

5.3.4.5. Map A5

5.3.4.6. Map A6

5.3.4.7. Map A7

5.3.4.8. Map A8

5.3.4.9. Map A9

5.3.5. Appendix B: CIP and Pavement Area data

5.3.6. Appendix C: Work History Report

5.3.7. Appendix D: Distress Database

6. SERVICES SUMMARY

7. STATUS OF FORCES AND HOST NATION SUPPORT AGREEMENTS

8. OPTIONAL/UNFUNDED BASES CLINs

9. GOVERNMENT POINTS OF CONTACT

Appendix A: Installation-Specific sUAS Operations Information/Restrictions

Appendix B: DAF Compass Part 52 Provisions/Clauses

1. GENERAL

Pavement Condition Inspection and PAVER Pavement Management System Update for Airfields and/or Roads and Parking at Air Force installations in the continental United States (US) and overseas.

This Performance Work Statement (PWS) defines requirements to provide airfield and/or roads and parking pavement surface condition evaluations and corresponding analysis and deliverables at various locations across the Air Force enterprise.

In carrying out the work assignments issued in this contract, the Contractor shall furnish the personnel, services, equipment, materials, facilities, and other requirements necessary for, or incidental to, the performance of work set forth herein.

Individuals who possess the qualifications established in Paragraph 4.8, Qualifications of Personnel, shall perform primary technical services.

2. SCOPE

The contractor shall provide non-personal services and shall ensure personnel do not perform any inherently governmental functions in accordance with (IAW) RFO 7.503 to do site evaluation and analysis in support of infrastructure condition assessments. The contractor shall provide technical expertise, labor, travel and all materials required to verify and/or update the pavement inventory and conduct American Society for Testing and Materials (ASTM) level Pavement Condition Index (PCI) inspection to document specific distresses on the airfields and/or roads and parking areas at the installations listed in PWS Attachment 1. As part of the effort, the contractor will create or update the PAVER pavement management system database, generate PCI summary reports for use as planning data for maintenance, repair, and construction, and generate separate deliverables for the airfield and/or the roads and parking networks as outlined in this PWS for each of the sites.

The Contractor shall provide all labor, supervision, equipment, supplies, and incidentals pertinent to the performance of the requirements.

3. APPLICABLE DOCUMENTS

The references listed in Table 1 below are the processes, standards, and guidance that shall be followed in performance of the tasks outlined within the body of this PWS. They include US Air Force (USAF), US Army Construction Engineering Research Laboratory (CERL), ASTM and various other references.

Table 1. References

Reference Date Title

ASTM D5340 (Airfields) Current Version

Standard Test Method for Airport Pavement Condition Index Evaluations

ASTM D6433 (Roads and Parking)

Current Version

Standard Practice for Roads and Parking Lots Pavement Condition Index Evaluations

DAFI 32-1041 Jun 2024 Pavement Evaluation Program

UFC 3-250-01 Nov 2016 Pavement Design for Roads and Parking Areas

UFS 3-250-03 Jan 2026 Standard Practice for Flexible Pavements

UFS 3-250-04 Jan 2026 Standard Practice for Concrete Pavements

UFC 3-260-01 Feb 2026 Airfield and Heliport Planning and Design, Change 3

UFC 3-260-02 Jun 2001 Pavement Design for Airfields

UFM 3-260-03 Feb 2026 O&M Manual: Standard Practice for Airfield Pavement Evaluation

UFC 3-260-04 May 2016 Airfield and Heliport Marking

UFM 3-260-16 Feb 2026 O&M Manual: Standard Practice for Airfield Pavement Condition Surveys

UFM 3-270-01 Feb 2026 O&M Manual: Asphalt and Concrete Pavement Maintenance and Repair

UFM 3-270-08 Feb 2026 O&M Manual: Pavement Management

UFS-3-701-01 Feb 2026 DoD Facilities Pricing Guide

Air Force Civil Engineer Center Sustainment Management System

Playbook Nov 2024 Air Force Civil Engineer Center (AFCEC) Sustainment

Management System (SMS) Playbook (PWS Attachment 2)

Transportation and Airfield Pavements AMP Business Rules May 2025 FY27-31 AFCAMP Business Rules (PWS Attachment 3)

CERL Manual Nov 2023 PAVER Version 7.1.2 User Guide

TSPWG Manual 3-270-08.14-03 Jan 2024 Pavement Management Plan (PMP)

Department of the Air Force Manual (DAFMAN) 11-501 Jan 2025 Small Unmanned Aircraft Systems Management

Department of the Air Force Manual (DAFMAN) 11-502 Jan 2025 Group(s) 1 and 2 Small Unmanned Aircraft Systems

Department of Air Force Instruction (DAFI) 13-213 Nov 2023 Airfield Driving

FAA AC 150/5300-16B Jul 2019 General Guidance and Specifications for Aeronautical

Surveys: Establishment of Geodetic Control and Submission to the National Geodetic Survey

The references cited in this PWS (e.g., FAA ACs, UFCs, ASTM standards) are intended to provide technical context and best practices. In the event of a conflict between these references and the specific requirements outlined in this PWS, the PWS shall take precedence.

The Contracting Officer Representative (COR) will provide the contractor with previous PCI reports, APE comprehensive evaluation reports, and any supplemental guidance requested within fourteen (14) business days after TO award. In addition, the COR will provide the latest PAVER database and any computer-aided design (CAD) or geographic information systems (GIS) data available from these previous reports. The installation Point of Contact (POC) will be provided so the contractor can request the common installation picture (CIP), construction history updates, Real Property Records and other pertinent data prior to the start of field work. The contractor must contact the COR if the installation POC does not provide the information needed IAW Section 5 within fourteen

(14) business days after the original request. The COR will then assist with obtaining the information from the installation.

4. CONTRACT MANAGEMENT, PLANNING, AND REPORTING SERVICES

The contractor shall conduct project planning activities, including assisting in the development, implementation, and maintenance of project schedules, events, status of resources, report(s) on the activities, and progress toward accomplishing project objectives more specifically identified in the subparagraphs below.

4.1. Monthly Status Report (MSR)

The contractor shall prepare and submit a MSR each month of the contract period of performance. Include a summary of events occurring during the reporting period, discussion of performance, existing problem areas, identification of new or potential problems, corrective action taken, and outstanding issues. (CDRL A001)

4.2. Conference Minutes

The contractor shall attend and/or support meetings and teleconferences as required by the Contracting Officer (CO) and/or the COR. The purpose of the meetings includes contract discussions, progress reviews, project status, and feedback from the government on the review of draft submittals. The contractor will be responsible for drafting and submitting all meeting minutes to the CO and COR. (CDRL B001). The contractor will also be responsible for submitting any conference agenda(s) at least 24 hours prior to the conference.

4.3. Notification Requirements

The contractor shall notify the CO and COR of critical issues that may affect the contract performance and/or human health and the environment. On critical issues, verbal notification is to be made immediately, followed by written notification within three (3) business days of verbal notification.

4.4. Project Planning Chart (PPC)

No later than seven (7) business days after Contract Award, the contractor shall submit a

PPC of the entire project which also includes the timelines for each CLIN (installation) which will include proposed field work schedule to the AFCEC COR for coordination with the identified installations and MAJCOM/AFIMSC Detachment(s) staff, if applicable. Once the COR has notified the contractor that the schedule has been approved by the installation, the contractor will follow up with the installation POC to coordinate any entry requirements, approvals, or permits prior to arrival at the site for field work.

This coordination will include providing team information for installation access and the airfield entry authorization letters. Entry requirements vary from location to location so a minimum of 30 business days for CONUS and 45 business days for OCONUS locations is required. The contractor shall coordinate photography of any kind through the installation POC. When required by the installation POC, the contractor must coordinate a photo authorization letter at least fourteen (14) calendar days before starting field work.

(CDRL C001)

4.4.1. Site Briefings

On the first business day of arrival at each installation, the contractor shall provide an entry briefing to the Base Civil Engineer POC and other installation officials, to include:

Engineering, Real Property, Operations, Security Forces and Airfield Management, as arranged by the installation POC. This in-brief shall explain the survey procedures and describe the support needed from the installation to complete the evaluation.

All Contractor personnel shall use normal base working hours of 0800 to 1700 Monday to Friday and exclude any federal holidays unless coordinated in advance or waved by the Base Civil Engineer (BCE), or BCE representative.

The Contractor shall coordinate with the BCE for a complete and updated list of any security/sensitive locations within the installation which would require special permission, special escorts, and/or restrictions to access.

4.5. Airfield Driving and Flight Safety

If proposed plan of contract execution includes vehicle collected data, the contractor shall be responsible for ensuring personnel attending evaluations complete necessary training to obtain an airfield driver’s license (AF Form 483 Certificate of Competency) in accordance with all requirements in DAFI 13-213, Airfield Driving. If contractor members do not already possess a valid AF Form 483, the contractor may work with the COR to facilitate the necessary training activities (requires in-person attendance by contractor personnel to Tyndall AFB) and testing requirements with the AFCEC Airfield Driving Program Manager (ADPM) and Airfield Manager. After obtaining an AF Form 483, the contractor will still be responsible for working with the installation Airfield Manager at the location receiving a pavement assessment, for completion of any installation specific airfield driving training/certification requirements and to obtain usage of a radio for communication with the tower. The contractor’s QC plan should address ensuring data quality while accounting for the possibility of interruption during data collection. If it is determined that NOTAMs are required to close portions of the airfield for specific periods of time to support testing activities, the contractor shall be responsible for coordinating these closures with the Airfield Manager to mitigate the impact on aircraft operations.

4.6. Quality Assurance/Quality Control Plan

The contractor shall maintain a Government approved Quality Assurance/ Quality Control Plan (QA/QC). QA/QC Plan shall demonstrate the steps taken during the field survey to ensure the data is collected IAW ASTM D5340 (Airfields) and ASTM D6433 (Roads and Parking), entered into the PAVER database accurately, and meets or exceeds the AFCEC sampling rates specified in Section 5.2.2.4 and 5.2.2.5. The quality control plan shall address the following:

• Survey equipment calibration/certifications and QC analysis results o All equipment calibrations and camera maintenance (if applicable) are to be performed in accordance with specific manufacturer’s recommendations.

o Equipment calibrations refer to anything that requires proper/regular calibration to ensure that it is in proper working order and shall produce expected, acceptable results.

o Calibrations shall be repeated as needed, according to manufacturer’s recommendations.

o All calibration procedures performed during this project, along with the recorded calibration data, are to be documented (i.e., results from tests are recorded and any corrective action taken shall be explained in detail) and reported to the USAF (CDRL D001).

• Survey procedures for producing consistent & reproducible datasets

• Survey equipment and data collection tolerances o As part of this QC plan, the contractor shall certify that their proposed data collection and analysis methods, regardless of apparatus or technique employed, can reliably produce results in accordance with the minimum data quality standards for pavement and distress attribute measurement as defined in Table 2. These standards are intended to expand upon the intent of those explicitly described in ASTM D6433 and ASTM D5340 and shall be applied and evaluated equally across all methods. A testing apparatus aligning with that described in ASTM D5340, Section 5 inherently shall be assumed to be able to produce results in accordance with these minimum data quality standards, provided that the 12 in scale used by the surveyor reads to the nearest 1/16 inch (1.5 mm).

o The QC Plan shall define the quality assurance methods and procedures in place to ensure that both georeferenced, and location referenced, data and images are located within proposed precision and accuracies.

• Manual QA/QC of automated distresses detected o When manual rating of various pavement distresses/conditions are provided, or when distress rating review of automated distress identifications are provided, the Contractor shall provide a data quantification rating/review process which shall include a rater training plan.

o The data quantification rating/review process shall assure rater accuracy and consistency.

o For manual rating, the data collection and quantification process should be applied in the same manner by all raters using the process. The plan must address the methods to demonstrate and monitor rater consistency throughout the entire data collection and quantification process.

o For review of automated ratings, the plan must address how reviewers provide consistency via the methods and procedures in place to validate automated ratings.

o The data quantification rating process must be approved by the USAF prior to implementation.

• Procedures to correct and/or recollect unacceptable data o The Contractor’s submittals shall require USAF-completed QA reviews and acceptance of deliverables for invoice approvals.

o The Contractor shall be advised if the submitted deliverables are accepted.

o If some percentage of a deliverable is not accepted, the USAF shall advise the

Contractor of the specific problems, and the expected problem resolution.

Once advised of such a need to resolve a problem, the Contractor is expected to resolve problem, at no additional cost to the USAF, within thirty (30) calendar days.

In addition, the QA/QC Plan shall also demonstrate the internal review process by the staff engineers prior to distribution of the deliverables. The quality control team must thoroughly study all existing information regarding design, construction, and maintenance of the pavements provided by the installation and the AFCEC COR. They must also review any previous comprehensive pavement evaluation and PCI reports, results of physical property tests of pavements, climatic data for the vicinity, and soils and drainage data. This information shall be used and analyzed by the team to enable the employment of sound engineering judgement in order to provide the best possible recommendations. The program manager/senior engineer, as defined in Section 4.8, shall be the final reviewer on all draft and final deliverables before submission. The COR will perform Quality Assurance checks of random pavement section conditions.

4.7. Contractor Manpower Reporting

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: Systems Award Maintenance (SAM) https://www.sam.gov/SAM/.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs from October 1 through September 30.

While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2026. Contractors may direct questions to the help desk at: Systems Award Maintenance (SAM) https://www.sam.gov/SAM/.

4.8. Qualifications of Personnel

Qualified personnel under the direction of a senior civil engineer shall execute the https://www.sam.gov/SAM/ https://www.sam.gov/SAM/ contract. The qualifications are as follows (personnel must meet at least one qualification for their respective qualification category):

• Program Manager/Senior Engineer- manages AF PCI contracts and performs QA/QC on all reports prior to draft/final submission o Registered professional engineer in civil engineering with at least 5 years managing PCI evaluations of airfields or roads and parking IAW ASTM D5340 and ASTM D6433 or;

o PhD in civil engineering with at least 5 years managing PCI evaluations of airfields or roads and parking IAW ASTM D5340 and ASTM D6433 or;

o Master’s degree from an ABET accredited school in transportation or pavement engineering with at least 10 years managing PCI evaluations of airfields or roads and parking IAW ASTM D5340 and ASTM D6433.

• PCI Lead Engineer/Technician- on site manager for AF PCI contract o ABET accredited bachelor’s degree in civil engineering with at least 20 network installation PCI evaluations completed of airfield and roads and parking IAW ASTM D5340 and ASTM D6433 or;

o Engineering technician with at least 25 network installation PCI evaluations completed of airfields or roads and parking IAW ASTM D5340 and ASTM D6433.

• PCI Technicians o Engineering technician with at least 10 network installation PCI evaluations completed of airfields or roads and parking IAW ASTM D5340 and ASTM D6433 under the direct supervision of a senior civil engineer.

• GIS/CAD Lead Technician o Engineering technician with at least 5 years of professional industry experience completing GIS and/or CAD maps.

5. TECHNICAL SERVICES

5.1. Technical Investigation

The contractor shall provide technical expertise, labor, travel and all materials required to inspect and verify the pavement inventory, conduct a pavement condition inspection to document specific distresses on the airfields or roads and parking areas, create/update the PAVER pavement management system database, perform condition analysis, provide maintenance and repair or construction planning requirements, and generate a deliverable package as specified in the Section 5.3 for each installation.

5.1.1. Pavement Area Summary

The contractor shall capture a 100% inventory of the pavements that exist in the corresponding network at each installation and use this data to assist in reconciling the differences between the PAVER inventory quantities and installation's Real Property Asset Database (RPAD). The contractor shall provide suggested actions to the Base Civil Engineer POC for installation Real Property Office personnel to complete in order to rectify discrepancies between the facility data listed in the installation's RPAD and the inspected facilities identified within the PAVER database. The PAVER/RPAD comparison shall be provided in tabular format as seen in Section 5.3.3.8.

All pavement facilities (whether active or closed/inactive) listed within the installation Geobase records shall be included in the mapping and PAVER inventory to provide data to rectify the disparity in areas. The contractor shall also create branches and sections, or validate previous linear segmentation, for all pavements in the PAVER database including shoulders and closed/inactive pavement. For unaccounted pavement or other concerns (i.e. abandoned in place sections or active sections not captured on the base CIP), the contractor should include in the PAVER inventory and discuss these areas with the POC. See Section 5.1.2, for specific guidance on closed/inactive pavement, shoulders, AGE storage, wash racks, etc.

All paved and unpaved roads and parking areas will be included in the mapping and PAVER inventory to provide data to rectify this disparity in areas. The contractor shall also create branches and sections, or validate previous segmentation, for all pavements in the PAVER database including unpaved and closed or unaccounted pavement. The contractor shall note the general condition of unpaved or unused pavement in the database but do not need to perform a detailed PCI on these pavements. See Paragraph

5.1.2.4 for specific guidance on installation housing.

5.1.2. Pavement Real Property Inventory Mapping and Segmentation

5.1.2.1. Inventoried Surfaces

When performing 100% inventory of all pavements, any open or closed/inactive, paved and unpaved surfaces shall be included in the mapping. The pavement rank of “U” should be assigned to closed/inactive pavement sections within the PAVER database. The general condition of closed/inactive/unsurfaced pavement should be determined via a cursory visual survey and noted in the PAVER database. A cursory visual survey denotes assessments in which the number of inspected sampling units fail to meet the ASTM minimum requirements in order to be considered either a simplified or standard evaluation. The results of a cursory visual survey should be reported as a qualitative assessment of the pavement surface condition as a “GOOD”, “FAIR” or “POOR” within the Overall Condition field of textual condition type within the PAVER database. If the results of a cursory visual survey are to be presented in a tabular format, the Cursory 3- Color Scale should be used.

5.1.2.2. Common Installation Picture

The installation will provide the contractor with the latest common installation picture (CIP) showing installation pavements and buildings (with facility number), and a pavement facility map showing the location of the pavement facilities (with facility number/Real Property Unique ID (RPUID)) listed in the real property record. The contractor shall use this information to adjust branches and sections from previous evaluations to align with the pavement facilities as outlined in Unified Facility Criteria (UFC) 3-260-01 and the general business rules for linear segmentation of pavements as outlined in the Transportation Networks and Airfield Pavements (TNAP), Supplemental Guidance of the Air Force Civil Engineer (AFCE) SMS Playbook. A PDF of the

Transportation Networks and Airfield Pavements (TNAP) sections of the AFCE SMS Playbook relative to PCI evaluations and this contract will be provided to the contractor (PWS Attachment 2).

5.1.2.3. Real Property Data in PAVER

The contractor shall enter/update the real property data in the PAVER database at the Section and Branch level. This data shall include the following: Real Property Site Unique ID (RPSUID), Facility Number, RPUID, facility analysis code (FAC), and Category Code (CATCODE) for each pavement section. These fields are defined in PAVER 7.x, but not in earlier versions of PAVER. If the facility numbers or RPUIDs are not available for specific facilities, the contractor shall request the installation to provide the appropriate data. If no data is provided, the contractor shall enter TBD## (## indicates a sequential number beginning with the first available number) for the Facility ID, RPUID, and Facility Name fields within the database and on any mapping products.

The contractor shall coordinate the requested updates to the linear segmentation plan affecting branch and section areas with the COR and installation POC during field investigations and throughout the performance period.

5.1.2.4. Installation Housing

For roads and parking areas within housing (CONUS Installations), the contractor shall conduct the PCI field survey and PAVER database updates for pavements that are not privatized. Privatized housing shall be inventoried but excluded from PCI survey and maintenance planning effort. For OCONUS installations, all housing roads and parking pavements shall be included in the PCI Survey. Driveways are to be inventoried but not inspected.

5.1.2.5. Paved Airfield Shoulders

The contractor shall include these pavements as part of the inventory for airfields when creating drawings and the database. Perform a standard PCI inspection of these pavements. The pavement rank of shoulder sections should match the rank assigned to the adjacent supporting active pavement within the PAVER database. Collect all available construction history of shoulders from the installation POC and input into

PAVER.

5.1.2.6. AGE Storage Aprons

The contractor shall include these tertiary pavements as part of the inventory for airfields when creating drawings and the database. The contractor shall perform a standard PCI inspection of these pavements and include them as part of the maintenance planning effort. Any aircraft support storage area within the airfield pavements layer shall be included as part of the effort.

5.1.2.7. Wash Racks

The contractor shall include these tertiary pavements as part of the inventory for airfields when creating drawings and the database. The contractor shall perform a standard PCI inspection of these pavements and include them as part of the maintenance planning effort.

5.1.2.8. Curbs and Gutters

For roads and parking, the contractor shall utilize a USAF created user defined field for each section to indicate the existence of curbs and gutters and a user defined field to note their general condition.

5.2. PCI Inspection Requirements

5.2.1. CADD/GIS Mapping Project Requirements

5.2.1.1. CIP Vector Data

The contractor shall determine the method used to create the vector data for the pavement facilities shown on the CIP. If it was surveyed, the contractor shall not adjust any vector data for pavement facilities to align with imagery. If it was digitized from imagery, the contractor shall determine what image was used and the accuracy of that image. The contractor shall not adjust any vector data for pavement facilities using less accurate procedures than used to create the CIP vector data. The contractor shall digitize new pavement areas from most recent aerial imagery provided in the AF Geo Library (https://www.my.af.mil/datalibrary/). If imagery is not available, use survey grade equipment to plot boundaries of newly constructed pavement and include in computer-aided design and drafting (CADD)/GIS Mapping and shapefiles. Document any recommended changes to the CIP in Appendix B of the Deliverable Package (refer to Section 5.3.5). As an option, the APE mapping template which uses AutoCAD 3D map or ArcGIS Pro will be made available to the contractor for their use and can be requested through the COR.

5.2.1.2. Area Validation

The contractor shall choose at least one pavement section of each branch use (i.e., Runway, Taxiway, Apron, etc.) and verify/validate the area. Compare the field verified area to the CIP and installation GeoBase pavement layer. Where a branch is made up of more than one section, the contractor will physically measure key dimensions for each section and sum them up to determine the area of the branch. The intent of this task is to validate the mapping received from the installation and reconcile any differences between the CIP and what the contractor sees on the ground. Document the procedure used to validate dimensions in Appendix B of the Deliverable Package (refer to Section 5.3.5).

5.2.1.3. PAVER Database Updates

If the inventory definition in the PAVER database changes, the Contractor is responsible for updating the map and any associated links to the PAVER database to reflect the changes. In addition, the contractor shall provide a full listing of any CIP adjustments to the AF as part of the deliverables for this project.

Shapefile associated with the PAVER database shall have the following metadata requirements:

Under Tags: Year of survey, Type of Survey, Installation Name, Company name, Author

Under Summary: Description of survey performed (For Example: PCI inspection, Structural Evaluation, Real Property Validation, etc.).

The final PAVER .e70 database provided shall have all sample unit (SU) images stripped out to reduce file size (CDRL D001). Note: While all Sample Unit images shall be stripped from the final PAVER .e70 database to minimize file size, the full set of collected images must still be included as part of the overall deliverable in accordance with Section 5.2.2.7 and CDRL D001. Images shall be organized by Section ID and Sample Unit ID and accompanied by a spreadsheet index.

The shapefile shall be in State Plane Coordinate System (SPCS) for all CONUS installations and Universal Transverse Mercator (UTM) for OCONUS installations and free of any topology errors. It shall be named using the following naming convention;

SiteName_Air/Roads_4-digit Year of Survey. The site name should be the same as what is on the Real Property Records.

5.2.1.4. CIP Updates

The contractor shall validate all CIP transportation vector data received from installations (e.g., Airfield, Roadway, Vehicle Parking). These three feature classes are separate entities in the CIP and often not checked against each other for topology errors between them. Typical errors that are identified:

• Vehicle Parking areas overlapping Airfield areas

• Roadway areas overlapping Airfield areas

• Vehicle Parking entrance areas overlapping Roadway areas or having gaps between them.

If these CIP data layers require updates/manipulation, the contractor shall make any necessary changes to the geospatial data and notify the installation, prior to the evaluation, to alleviate any concerns that may arise. If the number of errors is excessive (more than 100 topology errors), the contractor shall report these findings to the COR and request the installation GeoBase office to make the updates and supply repaired transportation vector data as soon as possible. When any geospatial information collected as a result of the contract includes information identified in the CIP or pavement Mission Data Set (MDS), the contractor will identify those changes and available metadata and provide it to the installation GeoBase office in SDSFIE file geodatabase format for them to update the CIP. The new APE-mapping template provides a tool to create an SDSFIE compliant file geodatabase using the PAVER .e70 and its shapefile. All geospatial data shall be delivered in the same coordinate system and projection that the CIP originally was provided. All geospatial information system (GIS) and mapping data will be delivered in SDSFIE Gold format.

5.2.1.5. GPS

Any Geospatial datasets captured by the contractor (e.g., shapefiles, point clouds, imagery) shall be tied to established geodetic control in accordance with FAA AC 150/5300-16B and referenced to NAD 83 (2011) and NAVD 88, or applicable local datum. The contractor shall include metadata describing the coordinate system, projection, datum realization, method of georeferencing (e.g., RTK, post-processed static survey), and the number and location of control points used. The contractor shall employ positioning methods capable of achieving a horizontal positional accuracy of ≤3 cm and vertical accuracy of ≤5 cm RMSE. In particular, the contractor shall identify the centroid of each sample unit for the airfield or roads and parking survey. RTK GNSS is one acceptable method, but alternative techniques may be used if they meet the required accuracy and are documented.

5.2.2. Pavement Condition Inspection

5.2.2.1. As-Built Drawings

The contractor shall work with the installation POC to acquire as-built data for all projects completed since the last AFCEC Airfield Pavement Evaluation report (airfields) or PCI inspection (roads and parking). The installation POC may elect to provide the information or arrange for the contractor to review as-built drawings and records at the Base Civil Engineer offices. The contractor shall review as-built drawings and records to determine the project or work order number(s) and phase (if applicable), project or work order cost, construction date, major maintenance and repair date(s), pavement thickness (if applicable), and work type performed for all inspected pavements, and ensure that this information is accurately reflected in the appropriate data fields within the PAVER database.

5.2.2.2. Interviews

In cases where the installation does not have a thorough historical record of construction dates and maintenance and repair projects, especially on roads and parking lots, the contractor shall review available imagery, to include Google Earth, and interview Installation Civil Engineering and Airfield Management personnel to estimate the date of construction, last major maintenance and repair date(s), and type of work. The contractor shall input “Date Estimated” and source within the comments field of the work history module within the PAVER database. If they cannot provide this estimate, the contractor shall collect and input the data that is available into the PAVER database and will estimate the construction date based on average deterioration rates calculated for asphalt and concrete pavement using sections for which historical data was available. Request background data to include any history of installation relevant to the survey [date opened, location, current traffic data, previous evaluations (PCI/ Structural), and construction history].

5.2.2.3. Pavement Identification

For pavements that have not been inspected previously, the contractor shall divide the paved areas of the network into branches, sections and sample units. For pavements that have been inspected previously, the contractor shall update the branches and sections as required and assign them to pavement facilities following segmentation guidance and naming conventions as outlined in UFC 3-270-08 and the current general business rules for linear segmentation of pavements as outlined in the TNAP Supplemental Guidance of the SMS Playbook. If pavement is found during the evaluation and not included as part of the installation CIP or Real Property Asset Data, the contractor shall inventory and inspect the pavement, leave real property inventory data in PAVER as TBD, and ensure that these areas are identified and addressed with the installation POC.

5.2.2.4. Sampling Rates, Airfield Networks

For Airfields, the contractor shall determine sampling rate in accordance with procedures for a 95% confidence PCI assessment as described in ASTM D 5340, assuming an acceptable margin of error (e) of +/- 5 PCI points. If a section has not previously been inspected, assume a standard deviation of 15 for concrete and 10 for asphalt to determine the number of sample units to be inspected according to ASTM D 5340-23 Equation (1) and complete the inspection. If a given section has previously been inspected, start with the inspected sample units from the previous inspection. Compute the standard deviation of sample unit PCIs from the previous inspection to determine the required number of sample units to be inspected for the current inspection. Add or remove sample units from the current planned inspection as necessary. Exception: The total number of sample units inspected shall amount to no less than 10% of the section area.

Following completion of the inspection, the actual standard deviation of the sample unit PCIs within each section will be computed according to ASTM D 5340-23, Equation (2) and a revised minimum number of sample units to be surveyed will be computed using Equation (1). If the revised number of sample units to be surveyed is greater than the number of sample units already surveyed, select and survey additional random sample units.

5.2.2.5. Sampling Rates, Roads and Parking Networks

For road and parking surveys, the contractor shall use a reduced sampling rate as indicated in ASTM D6433 para. 7.6. However, for sections exceeding 40 sample units in size, the contractor shall inspect either:

A) 10% of the total section by area

Or

B) the number of sample units required to achieve 95% confidence according to ASTM D 6433 Eqn. (1), (assume standard deviation of 15 for concrete and 10 for asphalt if section has not previously been inspected)

Whichever is less.

The contractor shall create or update the PAVER database to record the inventory and inspection data for the network. The final use of this data will be to manage the pavement network effectively. If additional sampling is required to support project development at the required confidence level, the contractor shall inspect additional sample units. In addition, if extrapolated distress estimates are inaccurate based on the data collected, the contractor shall collect additional sample units to ensure the data provides an accurate reflection of the condition. For example, if there are large areas of POOR pavement that were not captured in the random sampling and the engineer believes it will have a significant effect on the budget analysis, increase the sampling.

The contractor shall identify and highlight any significant issues for the base pavements.

5.2.2.6. PAVER Data Entry

The contractor shall ensure the PAVER database is divided into separate installations or site networks based on real property ownership or use. For example, housing (un-privatized or privatized), Air National Guard/Department of War (DoW) leased areas, and/or geographically separated areas/sites. The naming for these network IDs should follow this format; Site NameFH (non-privatized housing), Site NamePH (privatized housing), Site NameANG (Air National Guard). The contractor shall contact the COR if there are any questions on the separation of networks and naming convention. If separated in the existing PAVER file, the contractor shall combine the unpaved and paved roads and parking network. The PAVER database shall be cleared of any extraneous system tables or user-fields not applicable to the respective database.

Duplicate work types in the database shall be deleted. For all airfield databases, the contractor shall assign the Foreign Object Debry (FOD) Aircraft at the section level in

PAVER.

5.2.2.7. Photography

The contractor shall include digital photo documentation of pavement sections and typical distresses for each section. An overview photograph of each section shall be included. All photos will have a text box at the bottom with the GPS location, date the photo was taken, and description of distress/severity and grouped into folders identified with the Section IDs. At a minimum, the contractor shall take one (1) overview photograph and three (3) pavement distress photographs per section.

The contractor shall coordinate photography of any kind through the installation POC. If imagery is collected as part of an automated survey process, the contractor will provide all imagery data on an external hard drive(s) in a format that can be read in PAVER Image Inspector and ArcGIS Pro. Pavement images shall not be collected during periods when the visibility of cracking and other distress forms are continuously obstructed or obscured. This includes water on the pavement surface, either sand or mud on the pavement surface, low light conditions, excessive shadows, etc. All photos shall be provided as a deliverable along with an Excel spreadsheet index and organized by distress. (CDRL D001)

5.2.2.8. PCI Ratings

PCI ratings shall be determined for each network, as well as for each branch, and section according to procedures described in ASTM D 5340-23 for airfields and ASTM D 6633 for roads and parking networks. The PCI ratings at the section level shall be shown on a color- coded map using the applicable PCI Rating specified in ASTM D5340 or D6433.

Specific Red, Green, Blue (RGB) color codes to be used for PCI mapping and graphics are shown in Figure 1 below.

Figure 1. PCI Ratings.

5.2.3. Automated PCI Inspection: Alternate Methods and Approval

The Performance Work Statement (PWS) for PCI Inspections does not exclude the use of automated pavement inspection technologies in lieu of the manual equipment specified in Section 5 of ASTM D5340 and ASTM D6633. However, contractors are required to effectively demonstrate that their solution meets the requirements contained herein.

When sUAS technology cannot be used due to installation/location restrictions or pending COTs UAS exemptions, contractors must use manual or alternative inspection methods. These alternative methods must still meet all the requirements defined in this document and be effectively demonstrated. The USAF reserves the ultimate right to determine technical acceptability and to approve a proposed technology and process for measuring pavement attributes

The USAF recognizes that automated systems (e.g., laser scanners, imaging devices) differ significantly in their principles of operation compared to the tools associated with manual inspection. Further, a given technique employing measurement devices or methods other than those mentioned in ASTM D5340, Section 5 could theoretically produce measurement results meeting the ASTM-specified standard for accuracy/repeatability (+/- 10% if remeasured) but with actual values and results differing significantly from corresponding manual observations, and which may or may not be reflective of ground truth (i.e. manual inspections). Therefore, there is a requirement for additional specificity related to the data quality standards (applicable across all methods of inspection) that can ensure reasonable compatibility of results between various potential evaluation techniques. Note that these data quality standards do not relax the requirements outlined in ASTM D5340 or unfairly disadvantage contractors proposing manual inspection techniques. Instead, the requirements detailed in this section are intended to:

• Avoid limiting the potential enhancements to efficiency and data-rich capabilities of automated and semi-automated inspection methods, while maintaining results and outcomes comparable to manual techniques.

• Establish minimum data quality standards for automated methods to ensure reasonably accurate identification and quantification of pavement distress, achieving parity with the intent of requirements defined in ASTM D5340 and ASTM D6633. These standards will address:

a. Measurement Resolution, Accuracy and Repeatability

b. Industry best practices and environmental considerations for data collection to ensure the highest level of data integrity

5.2.3.1. Data Quality Standards for Automated Measurement of Pavement Attributes:

The following data quality standards for automated measurement of pavement attributes as indicated in Table 2 are implemented to define acceptable tolerances for length, width, depth, height, and area attribute measurements of distresses and pavement attributes, ensuring reasonable consistency with manual inspection outcomes. For the government to approve an automated method, the Contractor shall submit results from at least one prior project or independent study demonstrating the accuracy and repeatability of their proposed methodology while showing a direct comparison of similar conditions to manual inspections outlined in this PWS. This documentation must include:

• Data collection performed over both an asphalt and concrete surfaced test section not less than (1) standard sample unit in size where all pavement features and distresses have known attributes as determined via manual test apparatus, and each test section containing at least one (1) cracking-based distress at both low-severity and (1) at medium-or greater severity and at least

(1) depth/height based distress at low-severity and (1) at medium- or greater severity, independently verified using standard testing apparatus as indicated in ASTM D5340 to establish ground truth.

• A minimum of three (3) independent data collection runs over each test section using the proposed methodology.

• Analysis demonstrating compliance with the data quality standards for measurement accuracy and repeatability as described in Table 2.

The USAF reserves the ultimate right to determine technical acceptability and to approve a proposed technology and process for measuring pavement attributes.

Table 2. Minimum Data Quality Standards for Pavement and Distress Attribute Measurements

Requirements Resolution Accuracy Repeatability (min. 3 measurements)

Width Attribute Measurements (x-y plane) 0.06 in (1.5

mm) ± 0.12 in (3.0 mm) Greater of ± 0.12 in (3.0 mm) or ± 10%

Height/Depth Attribute Measurements (z-plane)

0.06 in (1.5

mm) ± 0.20 in (5.0 mm) Greater of ± 0.20 in (5.0 mm) or ± 10%

Length Attribute Measurements (x-y plane) 0.1 ft (30 mm)

± 30% for features with corresponding width dimension < 0.12 in (3.0 mm) ± 15% for features with corresponding width dimension of 0.12 in (3.0 mm) to 0.24 in

(6.0 mm) ± 10% for features with corresponding width dimension > 0.24 in (6.0 mm)

Area Attribute Measurements 0.01 square feet ± 20% ± 20%

Mean Texture Depth (if applicable) 0.004 in (0.01

mm) ± 0.04 in (0.1 mm) Greater of ± 0.04 in (.1 mm) or ± 10%

Pavement Geometry (if applicable) 0.1 degrees ± 0.5 degrees ± 0.5 degrees

5.2.3.2. Equipment, Technology, and Software Tool Requirements

5.2.3.2.1. Navigation System:

The Contractor shall include a detailed plan outlining the proposed data-collection system's navigation components and procedures (e.g., establishing of ground control points (GCPs), network real-time kinematic (RTK)) to ensure accurate and synchronized spatial referencing for all collected data, including coordinates, images, and distress measurements.

Note: The global positional accuracy requirements established in Section 5.2.1.5 for the purpose of pavement inventory validation are not sufficient to ensure accurate distress identification. Contractors must demonstrate that all spatial datasets used to resolve pavement distress attributes are synchronized, whether through real-time methods or post-processing, such that feature alignment errors do not exceed the tolerances defined in Table 2.

This plan must address procedures for mitigating GPS signal loss and satellite outages, as well as strategies for minimizing driver-induced bias (if applicable) or excessive wind (for sUAS based platforms). The plan must clearly define expected accuracies, both relative (e.g., pixel-to-pixel) and global, for all devices and equipment, and summarize these details in a "Technical Detail Response" table (Section 5.2.3.4.1).

5.2.3.2.2. Methodology for Accuracy

The Contractor shall detail their methodology for accurately synchronizing any pavement images and all other collected data with the inventory-related features of the CIP to include Network ID, Branch ID, Section ID, Sample ID, and, where applicable, Slab ID.

The plan must differentiate between data/images synchronized in real-time versus post-processing, and…