Draft PWS - PCI Studies FA805124R4004.pdf

FA805124R4004

PERFORMANCE WORK STATEMENT

FOR

PAVEMENT CONDITION INDEX STUDIES

AT

AIR FORCE INSTALLATIONS

12 March 2024

General

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

This Performance Work Statement (PWS) defines requirements to provide airfield and/or roads and parking pavement condition index (PCI) evaluations and corresponding analysis and report at various locations Air Force wide.

In carrying out the work assignment issued in this task order (TO), 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 3.7, Qualifications of Personnel, shall perform primary technical services.

1.0 SCOPE

The contractor shall provide 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 ASTM level PCI inspection to document specific distresses on the airfields and/or roads and parking areas at the installations listed in Attachment 1. As part of the effort, the contractor will create or update the PAVER pavement management system database, generate PCI reports for use as planning data for maintenance, repair, and construction, and generate a separate report 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.

2.0 APPLICABLE DOCUMENTS

The publications listed in Table 1 below are the processes, standards, and guidance that shall be followed in performance of the tasks under the appendices of this PWS. Other guidance that shall be followed is contained in the body of the PWS. They include US Air Force (USAF), US Army Construction Engineering Research Laboratory (CERL), and various other 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

AFMAN 32-1041 Oct 2019 Pavement Evaluation Program

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

UFC 3-250-03 May 2018 Standard Practice Manual for Flexible Pavements

UFC 3-250-04 Jul 2009 Standard Practice for Concrete Pavements

UFC 3-250-08FA Jan 2004 Standard Practice for Sealing Joints and Cracks in Rigid and Flexible Pavements

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

UFC 3-260-03 Apr 2001 Airfield Pavement Evaluation

UFC 3-260-16 Feb 2019 O&M Manual: Standard Practice for Airfield Pavement Condition Inspections

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

UFC 3-270-08 (Airfields) Jan 2004 Pavement Maintenance Management

UFC-3-701-01 Feb 2021 DoD Facilities Pricing Guide

Air Force Civil Engineer Sustainment Management System Playbook Aug 2020 Air Force Civil Engineer (AFCE) Sustainment Management System (SMS)

Playbook (Attachment 2)

Transportation and Airfield Pavements AMP Business Rules Jul 2020 FY22-26 AFCAMP Business Rules (Attachment 3)

CERL Manual Nov 2023 PAVER Version 7.1.2 User Guide

TSPWG Manual 3-270-08.14-03 Oct 2019 Preventive Maintenance Plan (PMP) for Airfield Pavements

Table 1: References

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 CAD or 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 is not providing the information needed IAW Section 2.0 within fourteen (14) business days after original request.

The COR will then assist with obtaining the information from the installation.

3.0 TASK ORDER MANAGEMENT, PLANNING, AND REPORTING SERVICES

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.

3.1 Contractor’s Progress, Status, and Management Report

The contractor shall prepare and submit a Contractor’s Progress, Status, and Management Report (CPSMR) on a monthly basis. 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)

3.2 Meeting and Teleconference Support

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

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

3.4 Project Planning Chart (PPC)/Worksite Coordination

No later than seven (7) business days after Task Order 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) staffs, 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 Point of Contact (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)

3.4.1 Site Briefings

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 installation support needed to complete the evaluation.

The last business day prior to departing each installation, the contractor shall provide an exit briefing to the Base Civil Engineer POC and other installation officials, as arranged by the POC. This out-brief shall summarize the survey results and give impression status of current pavement maintenance performance and recommendations for future work requirements. If the installation opts not to have a live out-brief, prepare the briefing and leave it with the installation POC. A copy of the in-brief and out-brief will be provided to the CO and COR.

3.5 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 the AFCEC sampling rates IAW Table 2. Quality control plan shall address the following:

• Survey equipment calibration/certifications and QC analysis results

• Survey procedures for producing consistent & reproducible datasets

• Survey equipment and data collection tolerances

• Manual QA/QC of automated distresses detected

• Procedures to correct and/or recollect unacceptable data

In addition, the QA/QC Plan shall also demonstrate the internal report review process by the staff engineers during the report development and prior to distribution. The quality control team must thoroughly study all existing information regarding design, construction, maintenance, and traffic history 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 in order to provide the best maintenance and repair (M&R) recommendations during the report development. The project manager/senior engineer, as defined in Section 3.7, shall be the final reviewer on all draft and final reports before submission. The COR will perform Quality Assurance checks of random pavement section conditions.

3.6 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 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 2024. Contractors may direct questions to the help desk at: Systems Award Maintenance (SAM) https://www.sam.gov/SAM/

3.7 Qualifications of Personnel

Qualified personnel under the direction of a senior civil engineer shall execute the 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.

https://www.sam.gov/SAM/ https://www.sam.gov/SAM/

• PCI Lead Engineer/Technician- on site manager for AF PCI task orders 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 10 years of professional industry experience completing GIS and/or CAD maps.

4.0 TECHNICAL SERVICES

4.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 report as specified in the performance requirements beginning in Section 4.2 for each installation.

4.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 Assessment 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 in tabular format as seen in Section 4.3.2.9.2.

All pavement facilities (whether active or closed/inactive) listed within the installation Geobase records will 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 during the exit briefing. See Paragraphs 4.1.2.5 – 4.1.2.8, 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

4.1.2.4 for specific guidance on installation housing.

4.1.2 Pavement Real Property Inventory Mapping and Segmentation

4.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 fails 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.

4.1.2.2 Common Installation Picture

The installation will provide the contractor 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/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 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 (Attachment 2).

4.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, Real Property Unique ID (RPUID), 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 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.

4.1.2.4 Installation Housing

For roads and parking areas within installation housing, the contractor shall conduct the PCI field survey and PAVER database updates. Privatized housing shall be excluded from maintenance planning effort.

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

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

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

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

4.2 PCI Inspection Requirements

4.2.1 CADD/GIS Mapping Project Requirements

4.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 document any changes to the CIP outlining the accuracy of the procedures used to make the change in the paragraph on CADD/GIS Mapping in Chapter 1 of the report. 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.

4.2.1.2 Area Validation

The contractor shall verify the actual area of each pavement branch by physically measuring key dimensions using a tape or a wheel that has been calibrated against a known distance. The contractor shall use resource or survey grade GPS equipment to validate the area of each branch. 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 the paragraph CADD/GIS Mapping in Chapter 1 of the report.

4.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 images stripped out to reduce file size (CDRL D001). 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 the one on the Real Property Records.

4.2.1.4 CIP Updates

Typically, the CIPs provided by the installations are accurate; however, on occasion geospatial data is inaccurate. If this occurs, the contractor shall make the necessary changes to the geospatial data and provide information to the installation, prior to the evaluation, to alleviate any concerns that may arise. Any CADD drawings developed outside of PAVER or any work done on the CIP or data layers in GIS must comply with the version of Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) that was used to generate the CIP. This should be SDSFIE Gold. If it is not, the contractor shall contact the COR to determine how to proceed.

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.

4.2.1.5 GPS

The contractor shall use a mapping (resource) or survey-grade GPS for collection of PCI data. In particular, the contractor shall identify the centroid of each sample unit for the roads and parking survey.

4.2.2 Pavement Condition Inspection

4.2.2.1 As-Built Drawings

The contractor shall work with the installation POC to acquire as-built data for all projects conducted since the last AFCEC Airfield Pavement Evaluation report (airfields) or PCI inspection (roads and parking). The installation POC may provide the information to you or arrange for you 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 within the PAVER database.

4.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].

4.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 asset data in PAVER as TBD and ensure that these areas are identified and addressed during the exit briefing.

4.2.2.4 Field Inspection

The contractor shall conduct Pavement Condition Index (PCI) distress evaluations in accordance with ASTM D5340 for Airfields and ASTM D6433 for Roads and parking with the following exceptions;

-Sampling rate will be in accordance with Table 2 below for each pavement type.

- Select the same samples as the last AFCEC comprehensive (structural/PCI/friction) evaluation.

-If needed, add more samples in order to meet the total number of survey samples in Table 2.

-If a reduced sampling rate is requested on the task order for roads and parking, follow the guidance provided on ASTM D6433 Para 7.6.

-Airfield shoulder pavement will be evaluated using a standard PCI evaluation technique.

Table 2: Sampling Rates

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

4.2.2.5 PAVER Data Entry

The contractor shall ensure the PAVER database is divided in different networks installation on real property ownership or use. For example, housing (un-privatized or privatized), Air National Guard/DOD 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 cleaned of any extraneous system tables or user-fields not applicable to the respective database. Duplicate worktypes in the database shall be deleted. For all airfield databases, the contractor shall assign the FOD Aircraft at the section level in PAVER.

4.2.2.6 Data Analyses

The contractor shall also provide the following analysis and outputs from PAVER which shall be included as part of the draft and final report (CDRL D001):

A table with the area and area-weighted average PCI for the current and previous PCI inspection for each branch use category. In addition, provide a bar graph with a comparison of the area weighted average PCI for the current and previous PCI results for each branch use category as well as the overall area weighted average PCI for the network.

Apply asset management principles based on PAVER data and engineering judgement in project recommendations.

Include general observations and PCI inspection results for the different pavement use areas with emphasis on problem areas.

Provide detailed explanations of sections that have an unexplained increase in PCI, unusually high rate of deterioration (hereby defined as ±1.5 times the average deterioration rates from the PCI deterioration models) or likely major M&R performed but not recorded in the detailed description paragraph for each branch/section.

Repair recommendations obtained from PAVER are not always the most effective and/or feasible type of repair, therefore the engineer shall evaluate the type of distress and history information and use engineering analysis and judgement when making a final recommendation.

Identify sections with PCI values of 40 or below or increase in PCI values above 40 from the previous inspection in a table. The COR will then provide the contractor with new PCN values during the draft review which will be used to calculate the structural index prior to the final report.

Develop maintenance and repair requirements for each pavement network. The maintenance program will list the type of work required and estimated cost for completing the work. This maintenance plan should cover a period of 10 years from the beginning of the next fiscal year after the inspection. List projects that should be funded first and outline the impact of unfunded projects. Maintenance requirements should be determined based on maintaining all primary pavements at a PCI of 70 or greater, all secondary and tertiary pavements at a PCI of 55 or greater. Note: Costs projections shall be based on the latest cost data and location area cost factor adjustments. The contractor will publish the cost by work data in the report.

Make repair type recommendations and provide associated costs according to the standard M&R maintenance policies established for the DAF in AFMAN 32-1041 and UFC 3-270-08. Recommendations should include both global and localized preventive maintenance, major repair, and complete reconstruction projects, as necessary.

Provide a prioritized list of major M&R projects and associated cost for each year in the optimum budget scenario. These projects shall consolidate adjacent or nearby sections into logical groups for execution in a given year for economy of scale and operational impact and should avoid doing multiple projects in consecutive years unless it is part of a phasing strategy.

Provide a table with a prioritized list of localized distress maintenance requirements utilizing preventative and stopgap maintenance and repair policies outlined in TSPWG Manual 3-270-08.14-03, UFC 3-270-08 or as directed by COR. List the types of work required as well as quantity and estimated cost for each work type.

Upon request, the COR will provide a list of USAF Preventive and Stopgap policies for Airfields and Roads and Parking Networks.

Create a table with actionable items for the installation to complete in order to rectify discrepancies between the data in the RPAD and the inspected facilities listed within the PAVER database.

Provide a condition table from the PAVER database broken out by aprons, overruns, runways, taxiways, shoulders (or roads and parking), and total. Provide a table from the PAVER database that gives an area breakdown of pavement surface type (PCC, AC, composite, etc.). Provide a condition table from the PAVER database that gives an area breakdown of pavement age. Provide a table from the PAVER database that gives an area breakdown of pavement age that gives a PCI breakdown of pavement condition by rank and pavement surface type.

Provide a summary of sections not inspected and excluded from condition analysis and work plans with justification for exclusion.

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

Photographs should be properly referenced to the report or included in the report. 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. All photos shall be provided as a deliverable along with an Excel spreadsheet index and organized by distress. (CDRL D001)

4.2.2.8 PCI Ratings

PCI ratings shall be determined for each network as a whole, as well as for each branch, and section. 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.

Ratings for larger groupings of sections at the branch level or by pavement use will be summarized in tables according the report format content specified in the following sections. 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

4.3 Report (CDRL D001)

4.3.1 Report Format

The Contractor shall produce a draft and final report for the airfield and/or roads and parking network at each location listed in each task order. The draft submission will include PDF report, drawing files, photos, and a copy of the PAVER database, all in electronic format. The final report will be delivered electronically in a PDF format. The final report deliverable shall include all word documents, CAD and/or GIS files, databases, photographs, and other electronic source files used to generate the report.

Report Schedule: The contractor shall deliver a draft report for government review within 60 working days after completion of all fieldwork. The government will provide the contractor written comments on the draft within 60 working days of receipt. The contractor shall respond to the government comments in writing within 14 working days of receipt of the comments and discuss adjudication of the comments with the government prior to delivering the final report. The final report shall be delivered within 21 working days of adjudication of comments.

4.3.2 Report Content

4.3.2.1 Cover

Title “Airfield (or Roads and Parking) Pavement Condition Index Evaluation Report”, Name of Base, Date of Survey, Agency Performing Survey, and Status of Report (i.e. Final or Draft).

4.3.2.2 Preface

Includes: purpose statement, regulation references, evaluation team and contractor information, date of field survey and information on base support team and contacts.

4.3.2.3 Executive Summary

This section shall be a maximum of two written pages and include an 11 inch by 17-inch fold-out, seven-color PCI map. This map will also display Section ID bubbles with pavement thickness from last structural evaluation or as-built drawings for each section on the map. The two written pages will include the following information as a minimum.

4.3.2.3.1 Purpose

A very short description of the goals and objectives of the report.

4.3.2.3.2 Summary Table

A table with the area and area-weighted average PCI for the current and previous PCI inspection for each branch use category. Present numerical values to the nearest whole number value.

4.3.2.3.3 Conclusions & Recommendations

Provide a brief paragraph(s) highlighting any significant issues for the base pavements and include general recommendations for M&R by surface type.

Identify key branches that are recommended for Major M&R.

4.3.2.4 Chapter 1: Overview and Background

4.3.2.4.1 Introduction

The introduction should include the survey objectives, scope, and description of work performed.

4.3.2.4.2 Background Information

Background data should include any history of base relevant to the survey (date opened, location, climatological data, current traffic data, previous evaluations (PCI/Structural/Comprehensive), and construction history).

4.3.2.4.3 Major Projects

Provide a synopsis of major projects completed since last evaluation and entered into the PAVER database. If major projects have been accomplished, the contractor shall verify pavement thickness with installation personnel. The contractor shall inquire with AFCEC to determine if PCNs have been updated for airfield construction.

4.3.2.5 Chapter 2: PCI Results and Recommendations

4.3.2.5.1 PCI Inspection Process

Provide a description of the Pavement Condition Index survey process with explanation of the pavement life cycle graph shown on Figure 2 below.

Figure 2: Pavement Life Cycle Graph

4.3.2.5.2 PAVER Implementation

Provide a description of PAVER implementation and report products.

4.3.2.5.3 Overview of PCI Results

Include general observations and PCI inspection results for the different pavement use areas with emphasis on problem areas. Include a table that provides a definition of PCI rating and pavement distribution (see Table 3). In addition, include a table with PCI results by branch use and pavement surface type (PCC, AC, composite, etc.) along with a pie chart that graphically depicts the data (see Table 4). Include a synopsis of the deterioration rate for each family model and a reference to the PAVER deterioration model plots in Appendix L. Provide detailed explanations of sections that have an unexplained increase in PCI, unusually high rate of deterioration (hereby defined as 1.5 times the average deterioration rates from Appendix L) or likely major M&R performed but not recorded in the detailed description paragraph for each branch/section. Reference Table 13 in Section 4.3.2.10 for a deterioration summary and comparison of results from last and current PCI inspection.

Table 3: Definition of PCI ratings and pavement distribution

Table 4: PCI results by branch use and pavement surface type

4.3.2.5.4 Detailed PCI Description

Organize the narrative by branch use. Provide a summary of the pavement condition by branch use, highlighting key areas of the installation. Identify common and/or significant distresses. Provide M&R recommendations for the key areas, utilizing both PAVER recommendations and engineering judgement for recommendations. Repair recommendations obtained from PAVER are not always the most effective and/or feasible type of repair, therefore the engineer shall evaluate the type of distress and history information and use engineering analysis and judgement when making a final recommendation. Present multiple repair options and consequence.

These descriptions will identify the branches/sections within the branch use and highlight the details of any special interest items such as sections with high deterioration rates based on changes since the last evaluation or over the life of the pavement and potential mechanisms/reasons for these issues with representative photos of the primary distresses.

Pictures in the report shall be around 2 inches wide by 3 inches tall, in table format.

4.3.2.5.5 Projected PCI Table

Include a table depicting the projected PCI for the next 10 years based on deterioration rate computed in Appendix L assuming only stopgap work is performed.

4.3.2.6 Chapter 3: Engineering Assessment (Not required for roads and parking)

4.3.2.6.1 EA Rating Process

For airfields, provide a synopsis of the Engineering Assessment rating process and criteria IAW AFMAN 32-1041 and include a brief discussion of each of the EA components and the critical aircraft used to determine the rating (if applicable). Include Table 5 below showing the criteria for each index used to determine the EA.

Table 5: EA Rating Criteria

4.3.2.6.2 EA Rating Results

Determine the EA rating for each airfield section IAW AFMAN 32-1041. Provide a summary table similar to Table 6 below. Reference Appendix F for PCI rating, Appendix G for FOD potential rating, Appendix H for structural index rating, and Appendix I for friction index rating. Include a reference to Appendix A for EA map(s). Identify sections with new PCIs of 40 or below, or increase in PCIs above 40 from the previous inspection in a table. The COR will then provide the contractor with new PCNs during the draft review which will be used to calculate the structural indexes prior to the final report.

Table 6: EA Ratings by Section

4.3.2.7 Chapter 4: Optimum Budget Scenario and Maintenance/Repair Requirements

4.3.2.7.1 Maintenance and Repair (M&R) Requirements

Develop maintenance and repair requirements for each non-privatized pavement network. The maintenance program will list the type of work required and estimated cost for completing the work. This maintenance plan should cover a period of 10 years from the beginning of the next fiscal year after the inspection.

List projects that should be funded first and outline the impact of unfunded projects. Maintenance requirements should be determined based on maintaining all primary pavements at a PCI of 70 or greater, all secondary and tertiary pavements at a PCI of 55 or greater. Note: Costs projections shall be based on the latest cost data available in RS Means Heavy Construction Cost Handbook. The team or consultant will apply the sustainment area cost factor and the O&M escalation factor for the desired program year from UFC 3-701-01. The contractor will publish the cost by work type and cost by condition data in the report.

4.3.2.7.2 Budget Scenario Process Overview

Provide an overview of the process and logic that PAVER uses for running budget scenarios.

4.3.2.7.3 Comparison of Budget Scenarios

Provide a table with a comparison of budget scenarios outlining the annual costs for each budget scenario as shown in Table 7 below.

Table 7: Comparison of Budget Scenarios

4.3.2.7.4 Repair Recommendations and Cost

The Contractor shall make repair type recommendations, and provide associated costs according to the standard M&R maintenance policies established for the AF in AFMAN 32-1041 and UFC 3-270-01. Recommendations should include both global and localized preventive maintenance, stopgap maintenance and major repair. Include a reference to budget scenario details in Appendix K and pavement repair plan maps in Appendix A.

4.3.2.7.5 Optimum Budget

Provide a short discussion of the chosen optimum budget scenario with justification.

4.3.2.7.6 Prioritized List of Major M&R Projects

Provide a prioritized list of major M&R projects and associated cost for each year from the optimum budget scenario chosen in PAVER. Indicate the specific major M&R work type recommended.

4.3.2.7.7 List of Consequence of Localized Distress Maintenance

Provide a table with a list of localized distress maintenance requirements utilizing the PAVER preventative and stopgap maintenance and repair policies outlined in TSPWG Manual 3-270-08.14-03 and UFC 3-270-01. Organize the list by section.

List the types of work required as well as quantity and estimated cost for each work type.

4.3.2.8 Appendix A: Maps

Provide a list of the CAD and GIS files included on the disk with a description of each file. Include the name and description of any data elements or layers used in these files. All airfield maps shall be provided as CAD and/or ESRI/shapefiles for export to AF geographic information systems. As an option, the new APE mapping template which uses AutoCAD Map 3D or ESRI ArcMap Pro will be made available to the contractor for their use and can be requested through the COR. All roads and parking maps shall be provided as CAD and/or ESRI/shapefiles for export to AF geographic information systems. Also, ensure each CAD map contains a title block with the organization’s information, map title, installation name, engineer, date, drawing number, drafter, scale, north arrow, appropriate legend, and sheet number.

Appendix A shall include maps A1-A9 for airfields and A1, A3, A4, A8, and A9 for roads and parking pavements. (CDRL D001)

4.3.2.8.1 Map A1

Map A1 shall consist of the Pavement Facility Map. It will include all applicable pavement facilities on the installation.

4.3.2.8.2 Map A2

Map A2 shall consist of the Pavement Branch Identification Map. All major branches of the pavement networks shall be included.

4.3.2.8.3 Map A3

Map A3 shall consist of the Pavement Rank Map.

4.3.2.8.4 Map A4

Map A4 shall consist of the 7-color PCI Map.

4.3.2.8.5 Map A5

Map A5 shall consist of the FOD Potential Rating.

4.3.2.8.6 Map A6

Map A6 shall consist of the Structural Index Rating.

4.3.2.8.7 Map A7

Map A7 shall consist of the Friction Index Rating (runways only).

4.3.2.8.8 Map A8

Map A8 shall consist of the Engineering Assessment Rating.

4.3.2.8.9 Map A9

Map A9 shall consist of the Sample Unit Identification Map.

4.3.2.9 Appendix B: Pavement Inventory and Condition Information

4.3.2.9.1 Real Property Summary

Provide a user defined report from the PAVER database with the Facility Number, Real Property Unique ID (RPUID), Category Code (CATCODE), branch name, branch ID, rank, PCI, and area (in square feet and square yards) as shown in Table 8 below. This report will be included in both the draft and final report and as an Excel spreadsheet as part of the final deliverables. In addition, include a table prior to the summary with definitions for each of the terms above.

Reference AFMAN 32-1041 and DAFI 32-9005 for current guidance on linear segmentation, as well as real property accountability and reporting policies for pavement assets.

Table 8: Real Property Summary

4.3.2.9.2 PAVER/RPAD Comparison

Create a table with action items for the installation to complete in order to rectify discrepancies between the facility data in the RPAD and the inspected facilities listed within the PAVER database. The table will list discrepancies such as:

missing information for any category (i.e. missing facility number), data that does not correlate in both the PAVER SMS and real property database (i.e.

CATCODE, RPUID, and type of facility mismatch between systems), inspected areas that are not within +/-5% of the area listed in the RPAD. An example of the table headings is provided in Table 9 below. In addition, and prior to, include a table with definitions for each of the terms above. Reference AFMAN 32-1041 and DAFI 32-9005 for current guidance on linear segmentation, as well as real property accountability and reporting polities for pavement assets.

Table 9: PAVER/RPAD Comparison Table

4.3.2.9.3 Branch Use Inventory

Provide a table broken out by aprons, overruns, runways, taxiways, shoulders (or roads and parking), and total (see Table 10 below). The table will have a column for pavement area (SF), percent area, number of sections, and area-weighted average PCI. Pie or bar charts may be used in addition to the table to show the distribution of pavement branch use and condition.

Table 10: Branch Use Inventory

4.3.2.9.4 Pavement Surface Type

Provide a table that gives an area breakdown of pavement surface type (PCC, AC, composite, etc.). The table will include the pavement surface type, area (SF), percent area, number of sections, and area-weighted average PCI for each pavement type (see Table 11 below). Pie or bar charts may be used to show the distribution of pavement surface types and condition.

Table 11: Pavement Surface Type

4.3.2.9.5 Summary of Area-Weighted Average Condition by Rank

Provide a table that gives a PCI breakdown of pavement condition by rank and surface type (see Table 12 below). The table will include branch use, pavement rank, pavement surface type, area (SF), and percent area, number of sections, and area-weighted average age and PCI.

Table 12: Area-weighted Average Condition by Rank

4.3.2.9.6 Sections Not Inspected

Provide a summary list of sections not inspected and excluded for condition analysis and work plans with justification for exclusion.

4.3.2.10 Appendix C: PCI Deterioration Rate Summary

Include a table sorted by section with a comparison of results from last and current PCI inspection with a remarks column that provides a brief explanation for…