Amendment 00001 Update SOW.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to extend the due date to 10 June 2024 at 1400 MT, provide an revised statement of w ork, and post answ ers to questions received.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 12

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-May-2024

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W9128F24R0055

X 9B. DATED (SEE ITEM 11)

16-May-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-May-2024

CODE

U.S. ARMY CORPS OF ENGINEERS, OMAHA DIST

CONTRACTING OFFICE

1616 CAPITOL AVENUE

OMAHA NE 68102-4901

W9128F 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9128F24R0055

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMEND 00001

The purpose of this amendment is to do the following:

1. The response date is extended from 03 June 2024 to 10 June 2024.

2. Post a revised Statement of Work dated 28 May 2024

3. Post answers to quesitons received.

QUESTION AND ANSWERS

1. Q: Looking at the solicitation with scope Pavement Network Details Table, it shows 13,575,088 SY and 8,510 Samples to Inspect. Is this solicitation for survey (full scope) and full report? Within the Contract Information on the synopsis, it states there is a SAT of $250,000, with this full implementation (inspection and report) need to be under this threshold?

2. A: The updated statement of work dated 28 MAY 2024 is now posted.

STATEMENT OF WORK 28 MAY 2024

Scope of Work Road and Parking Pavement Condition Reinspection and

PAVER Pavement Management System Update Fort Riley KS 28 May 2024

Attachments: 1- PAVER Database 2 - Network Inventory List

1. OBJECTIVE

The objective of this effort is to perform a pavement condition re-inspection of all the active paved roads and parking areas at Ft. Riley, KS. The areas to be inspected are summarized in the Pavement Network table below. Review and update the inventory for the unmanaged pavements and tank trail networks shown in the tables but do not inspect them. Accomplish all work in accordance with ASTM D6433 (20 or later) except for the sampling rate as identified under task descriptions. Update all models and work plans in accordance with UFC 3-270-08 and as specified in these performance requirements. Use PAVER™ Version 7.1.2 or higher.

Ft Riley - Pavement Network

Paved Areas Total Pavement

Area (SY) Number of Sections

Number of Sample Units to be Inspected

Roadway - AC 152,410 33 117

Roadway - PCC 43,258 16 36

Parking - AC 443,700 100 316

Parking - PCC 35,191 21 38

Total 674,559 170 507

2. DEFINITIONS AND TERMS

The following definitions and terms apply. See UFC 3-270-08 for additionally definitions.

2.1. PAVEMENT MANAGEMENT STRUCTURE

2.1.1. Network: A logical unit for organizing pavements into a structure for the purpose of pavement management. For example, an airfield pavement system is one network, and the Garrison roadway system is a separate network.

2.1.2. Branch: A branch is an identifiable part of the pavement network usually comprised of one or more sections and serves a separate and distinct purpose such as roads, driveways, parking lots, etc.

2.1.3. Section: A section is a division of a branch that has certain consistent characteristics throughout its area or length. These characteristics are structural composition (thickness and materials), construction history, traffic, and pavement condition. For airfield pavements, a section is synonymous with the term feature used in structural evaluations.

2.1.4. Sample Units: Pavement sections are divided into sample units for inspection purposes;

sample units are the smallest component of the pavement network. For asphalt or tar-surfaced roadway and parking lot pavements, sample units are 2500 square feet ± 1000 square feet. For concrete pavements, the sample unit size is 20 slabs, ±8 slabs. For slabs with joint spacing greater than 30 feet, imaginary joints should be assumed. For example, if slabs have a joint spacing of 50 feet, imaginary joints may be assumed at 25 feet. Thus, each slab would be counted as two slabs for the purpose of pavement inspection.

2.1.5. Primary Pavements: Include installation roads and streets which serve as the main distributing arteries for traffic originating outside and within an installation and which provide access to, though, and between the various functional areas. Access to mission essential facilities, such as medical, flight line, ammunition, etc. Facilities are primary pavements.

2.1.6. Secondary Pavements: Secondary pavements include installation roads and streets which supplement the primary highway system by providing access to, between, and within the various functional areas.

2.1.7. Tertiary Pavements: Tertiary pavements include installation roads and streets which provide access from other roads and streets to individual units of facilities of a functional area. Un-surfaced roads and abandoned in place, but usable roads, are classified as tertiary.

2.2. PAVEMENT MANAGEMENT SOFTWARE

PAVER™ is pavement maintenance and repair management system software developed by the United States Army Corps of Engineers (USACE).

3. CONTRACTOR COMPLIANCE

The Contractor shall follow the requirements listed below while completing the work specified in the task order.

3.1. QUALIFICATION OF PERSONNEL

Perform field inspection with technically trained personnel under the direct supervision of an engineer experienced in evaluating road pavement distress according to ASTM D6433 (20 or later). Measurements shall be made using techniques that give accuracy necessary for measuring procedures outlined in ASTM D6433 (20 or later). Contractors must also have experience with the EMS program PAVERTM.

3.2. COORDINATION/PERMITS

Conduct the appropriate coordination and obtain necessary approvals/permits to work on the pavements from all Garrison organizations as well as any local, State or Federal authorities as necessary for the performance of services.

3.3. FIELD SURVEY SCHEDULE

The Contractor shall coordinate a schedule with the Garrison Directorate of Public Works (DPW), POC (Rafael E Flores, :(785) 239-0423, rafael.e.flores-acosta.civ@army.mil ) to ensure the field work does not conflict with major Garrison events that would prevent access to the pavements.

3.4. TASK ORDER SUBMITTALS

The products submitted shall fully meet the requirements of the delivery order. Submittals shall be reviewed for technical accuracy. The Contractor shall return all reference materials provided by the U.S. Government.

3.5. GOVERNMENT OWNERSHIP

All data, reports, and materials related to this project are the property of the U.S. Government and shall not be released by the Contractor or sub-consultants without the prior written approval.

4. SECURITY/NATIONAL AGENCY REQUIREMENTS

The Contractor shall ensure compliance with the basic contract, including but not limited to Security/National Agency Check Requirements set forth in Section C of the basic contract regarding all employees who require access to Automated Information Systems (AIS), (e.g., stand-alone computers, network computers/systems, e-mail), and regarding foreign nationals who may be performing work on this task order.

5. ANTITERRORISM(AT)/OPERATIONS SECURITY (OPSEC) PROVISIONS

5.1. AT LEVEL I TRAINING

All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after Task Order start date or effective date of incorporation of this requirement into the Contract, whichever is applicable. Upon request, the Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee, to the DPW Project Manager within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website:

http://jko.jten.mil/courses/atl1/launch.html.

5.2. ACCESS AND GENERAL PROTECTION/SECURITY POLICY AND PROCEDURES

All Contractor’s and all associated sub-contractor’s employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The Contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this Contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in Contractor security matters or processes.

Contractor’s and all associated sub-contractors’ employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government Representative, as NCIC and TSDB are available).

5.3. IWATCH AND/OR CORPSWATCH TRAINING

The Contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the DPW Project Manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of Task Order award and within 30 calendar days of new employees commencing performance with the results reported to the DPW Project Manager NLT 5 calendar days after the completion of the training.

5.4. OPSEC TRAINING

All Contractor employees will complete Level I OPSEC training within 30 calendar days of their reporting for duty.

Additionally, all Contractor employees must complete annual OPSEC awareness training. The Contractor shall submit certificates of completion for each affected Contractor and subcontractor employee, to the DPW Project Manager within 5 calendar days after completion of training. OPSEC awareness training is available at the following websites:

https://www.iad.gov/ioss/ or http://www.cdse.edu/catalog/operations-security.html; or it can be provided by the RA OPSEC Officer in presentation form which will be documented via memorandum.

5.5. E-VERIFY PROGRAM

The Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Contractor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the DPW Project Manager no later than 3 business days after the initial Task Order award.

6. INSTALLATION ASSISTANCE

The Fort Riley DPW POC will assist the Contractor in obtaining available information and establishing contacts with the appropriate individuals and organizations at the Garrison, as necessary, to accomplish the work required under this contract.

7. MAJOR REQUIREMENTS

The Government will provide the Contractor with a copy of the PAVER database that includes the pavement inventory and sample unit layout map. In order for the Contractor to accomplish the work under this task order, it shall be necessary for the Contractor to complete the following tasks:

7.1. In-brief Meeting. Shortly after arrival at the Garrison, provide an entry briefing to the Garrison DPW POC and other Garrison officials, as arranged by the DPW POC. This in-brief should be performed before beginning the inspection and should explain the survey procedures and describe the Garrison support needed to complete the evaluation. A copy of the notes documenting the meeting will be provided to the Task Order Technical POC. The Contractor shall coordinate the date of the in-brief meeting with the DPW Project Manager and Task Order Technical and Administrative POCs. There is a strong possibility that the Technical POC will be joining the in-brief, therefore an advance notice should be provided by the Contractor (preferably 3 weeks).

7.2. Inventory Update. The Government will provide the Contractor with a pavement inventory GIS shape file which includes network, branches and sections and a copy of the PAVER database that includes the pavement inventory. The Government will also provide the Contractor with a sample unit GIS shape file layout map for asphalt-surfaced pavements to be used by the Contractor for inspection. The Contractor may revise the sample unit layout if approved by the Government. Any revisions to the sample unit GIS shapefiles layout map will be the responsibility of the Contractor. The Contractor will be responsible for updating the sample unit GIS shape file for any changed pavements. The sample unit map shall include all sample units, not just those being inspected. Layout of individual slabs within the sample unit shape files is not required. The total number of slabs in each sample unit (inspected and not inspected) should be entered in PAVER. All sample units shall be included in one shapefile. The database should not include multiple sample unit shapefiles. The Contractor will verify the inventory in the field of all sections being inspected and update the inventory to reflect the changes. The GIS inventory and sample unit shape files provided by the Government shall be modified accordingly by the Contractor. The section and sample unit GIS file naming convention shall be maintained. For example, sample units should be numbered with 3 digits (001, 002, 003, etc.).

7.3. Branch ID Update. The Contractor shall evaluate and update all Branch IDs that need updating to match the Real Property Branch ID in PAVER. Compare all PAVER shape files to the Real Property Shape files.

Edit Paver shape files to match the Real Property Shape files.

7.4. Update Work History. The last construction date for all sections shall be determined from Garrison records.

After substantial effort to determine last construction date from Garrison records, GIS and imagery tools shall be utilized to determine last construction date. The last construction date may be backcalculated if there are no other means to determine the date. The Contractor shall update (or add if missing) work history for all pavement sections in the inventory.

7.5. Collect condition data. The Contractor shall resurvey previously inspected sample units at a minimum. A single representative inspection date should be applied to all section inspections as opposed to a different inspection date for different sections. If any of the previously inspected samples listed in the attached network inventory are no longer representative of the distresses in the section, treat it as and additional sample unit (type A sample units) and inspect an additional representative sample unit (type R sample units) to ensure at least the minimum number of representative samples are inspected as outlined in the table below. The survey will be performed manually according to ASTM D6433 (20 or later). Each inspection team shall include at least two persons for safety. At least one member of the inspection team will have had considerable experience in performing PCI pavement inspection as per ASTM D6433-20 standard. Inspectors should identify distress types accurately 95% of the time. The accuracy will be based on the results of quality assurance inspections by the Government. Linear measurements should be considered accurate when they are within 10% if remeasured. Area measurements should be considered accurate when they are within 20% if remeasured. Distress severities based on ride quality are considered subjective. The Task Order Technical POC may meet the Contractor during the collection of condition data.

The Contractor shall notify the Task Order Technical POC at least 3 weeks prior to collecting condition data.

Total No. Of Sample Units in Section (N)

Min. No. Of Units to be Inspected (n)

1 1

2 to 5 2

6 to 15 3

16 to 40 4

Over 40 10%

7.6. Photos. Provide at least two photographs for each surveyed sample unit. One of the photographs should be an overview of the sample unit. The other photograph(s) should show the significant distresses in the sample unit. All photographs should have GPS coordinates. A table showing a list of photographs for each sample unit shall be provided by the Contractor. The table will include the pavement network, branch, section, and sample unit where the photographs were taken. All photographs should be associated with the appropriate pavement section; however, the photographs should be stored in an external media instead of the PAVER database. The external media shall be provided to the Government.

7.7. Database Cleanup and Draft #1 Submission. The Contractor shall update the database to remove any unused information in the system tables. Enter condition data into database, perform data verification and provide an error-free PAVER database verification run. Submit PAVER Database to the USACE POC as Database Draft #1.

7.8. Update Prediction Models. Update all existing prediction models for all pavements at Fort Riley using the entered work history and pavement conditions. At a minimum, prediction models will be developed for each combination of Branch Use and Surface Type. The critical PCI will be 70 for primary roads and 55 for secondary and tertiary roads. Submit the Prediction Models to the USACE Technical POC as part of the Draft #2 Database submission. The USACE Technical POC shall review and approve the prediction models and critical PCI assigned before the contractor develops the Work Plans.

7.9. Condition Performance Analysis. Perform condition analysis (e.g., Past, current, and future condition assuming only stop-gap M&R).

7.10. Rate of Deterioration Table. The PCI of each section shall be compared from the last previous inspection with the current inspection and a Rate of Deterioration Table shall be created in Microsoft Excel which lists all pavement sections that have a PCI increase of more than 5 or a decrease of more than 20 points. Any increase in PCI of more than 5 or decrease of more than 20 shall be explained if possible.

7.11. Update Existing PCI vs. Cost Models. All M&R cost tables and PCI vs. Cost models should be reviewed by the USACE Technical POC before performing the work plan analysis. Submit PAVER Database to the USACE POC as Database Draft #2.

7.12. 10-Year Work Planning Analysis. Perform a 10-year work planning analysis for the entire inventory which is 5 years more than the period required to meet the management objectives. This will allow for the determination of the M&R cost for the second 5 years of the budget scenario (e.g., Consequence of different budgets and required budgets to reach management objectives. Develop and save M&R budget requirements using four (4) budget scenarios. Each of the budget scenarios are described below in this paragraph. Each budget requirement scenario will list the type of work required and estimated cost for completing the work. The budget requirement scenarios should cover a period of five (5) years, from the time of inspection, and utilize the appropriate M&R families. At a minimum, two (2) separate M&R families will be developed, one for asphalt and one for concrete pavements.

Budget Scenarios Shall Include:

Scenario 1: Cost per year to eliminate major M&R backlog in five (5) years Scenario 2: Cost per year to maintain current area weighted PCI for five (5) years Scenario 3: Projected PCI at current and projected budget level Scenario 4: Cost for M&R to deal with safety issues only with projected drop in PCI

The first year of the work plan will be the next fiscal year after the inspections are completed.

7.13. Develop List of Projects. Develop a list of projects recommended for the following three (3) years using the PAVER™ project formulation tool. The projects shall be included in the PAVER database delivered to the Government. The first year will be the next fiscal year after the inspections are completed. The projects will include specific work types and costs. The work type names included in PAVER shall be used unless otherwise approved by the Task Order Technical POC. This list should be based on the PAVER analysis and to meet installation mission requirements. A project formulation is different than the automated section level work recommended by the PAVER work plan. The formulated projects would normally consist of multiple sections for economy of scale. Also, work should be in terms of work type, for example cold mill and overlay, slurry seal, etc. as opposed to the recommended work by PAVER which is only in terms of category, such as global and major. A draft list of projects shall be submitted to the installation for review.

In addition to the list of projects, the Contractor shall develop a table (M&R Details for Project Sections) which explains the M&R recommendations for each project. See attached example. The approved list of projects, M&R Details for Project Sections and color-coded maps showing the projects will be included in the report.

7.14. Project Formulation Out-brief Meeting. The Contractor shall meet with the DPW project manager at the installation to discuss the survey results and verify the list of projects and the years they are to be scheduled. The Contractor shall coordinate the date of the out-brief meeting with the DPW Project Manager and USACE POC’s. There is a strong possibility that the Technical POC will be joining the out-brief, therefore an advance notice should be provided by the Contractor (preferably 3 weeks). A copy of the notes documenting the meeting will be provided to the Task Order Technical POC. These notes will include any questions or issues raised by the Garrison personnel regarding the survey results or the proposed list of projects.

7.15. ISR Reporting. The contractor shall report all existing surfaced area conditions vs. the surfaced area requirements as outlined in DA PAM 420-1-3 (Chapter 3). This report shall outline the deficiencies of each section individually, each categorized section group and all surfaced areas as a whole. The Report shall sufficiently provide results showing the “percentage of surface areas that meet pavement Condition Index (PCI) rating per AR 420-1 (Chapter 7) and DA PAM 420-1-3.”

7.16. Reports. Generate Reports as described in the SOW Attachment. Upon completion of the draft report, please submit to the Government for comment. In addition, submit PAVER Database to the USACE POC as Database Draft #3.

8. QUALITY ASSURANCE

The Government may perform a quality assurance inspection of selected sample units as well as a quality assurance review of all PAVER data. If in the opinion of the Task Order Technical POC, an error which is clearly the fault of the Architect-Engineer is encountered, the Contracting Officer may direct the Contractor to immediately contact the Task Order Technical POC for the purpose of rectifying the mistake. The Contractor shall perform such services in the manner directed by the Contracting Officer at no additional cost to the Government and on an expedited schedule.

In the event that the Contractor should dispute the Contracting Officer’s decision in this regard, it shall be considered a dispute concerning a question of fact within the meaning of Disputes article of the contract and, pending final decision of the dispute, the Contractor shall proceed diligently with the work and services in accordance with the decision of the Contracting Officer.

9. DELIVERABLES

The Contractor shall submit the following final deliverables:

9.1. Meetings – Kick-off, In-brief, Project Formulation, and Outbrief – A copy of the notes documenting the meetings will be provided to the USACE POC.

9.2. PAVER™ DATABASE:

9.2.1. Draft 1 shall be submitted with the completion of inventory updates and evaluations

9.2.2. Draft 2 shall be submitted with the Prediction Models and PCI v Cost Models.

9.2.3. Draft 3 shall be submitted with the Draft Report.

9.2.4. Final delivered PAVER™ database shall contain:

- Updated inventory as well as inspection data free of errors.

- Condition Analysis plan used in the final report.

- Condition prediction families, deterioration families, maintenance and repair families, project formulation and cost data.

- System tables unique only to the particular database of interest.

The delivered PAVER™ database shall successfully pass the PAVER™ verification tool, error free.

9.3. GEOGRAPHIC INFORMATION SYSTEM (GIS)

The Contractor will deliver a fully updated GIS geo-referenced map and shape files.

9.4. PHOTOGRAPHS

Provide Photographs as outlined in paragraph 7.6.

9.5. REPORTS

The Contractor shall produce one draft and one final PAVER update report for Fort Riley. The reports shall be submitted in color printed format and electronically in PDF format. In addition, include a zip file with all Microsoft Word files, CAD and GIS drawings, PAVER™ databases, photos, and other files used to generate the report(s). Deliver the report in two (2) volumes. Include all Appendix B Maps in Volume II and the remainder of the report in Volume I. Format the report as described below.

9.5.1. Cover: The attached Report Cover Template shall be used. The Contractor shall replace the A-E logo with their own.

9.5.2. Table of Contents: The report should have tabs identifying each section/chapter. The Table of contents should also include: List of Figures, List of Tables, List of Maps.

9.5.3. Preface

9.5.4. Executive Summary

Purpose Pavement Condition Index PAVER Recommended Maintenance and Repair Requirements Summary and estimated cost Follow format of executive summary in attached example report.

9.5.5. Chapter 1: Introduction Objective and Scope Description of Tasks Performed Implement the PAVER™ Pavement Management System Installation Background Data

9.5.6. Chapter 2: ISR-PCI Results and Recommendations

ISR-PCI Inspection Introduction ISR-PCI Inspection Procedure Pavement Life Cycle Pavement Management System (PMS) Implementation Products & ISR-PCI Inspection Results Branch/Section Condition Summary

Pavement Deterioration Rates (since construction & last inspection) PCI Prediction Models Summary

9.5.7. Chapter 3: Maintenance and Repair Budget Scenarios

Introduction Budget Scenario Details Budget Scenario Results M&R Budget Recommendations and Projects Summary

9.5.8. Chapter 4: M&R Project Recommendations

Formulated Projects Tables Formulated Projects Maps

9.5.9. Appendix A: Pavement Inventory and Condition Information Real Property Information Inspection Data Summary by Branch Use Inspection Data Summary by Surface Type Inspection Data Summary by Age Group Sections Not Inspected and Excluded from Condition Analysis and Work Plans Work History (include reason)

9.5.10. Appendix B: Maps (11” x 17”)

Branch (Facility) Identification Map Section (Feature) Identification Map Primary, Secondary, Tertiary Pavements Map PCI Summary Map (5-color) by Section ISR-PCI Summary Map (3-color, Green, Amber, Red) by Section* ISR-PCI Summary Map (3-color, Green, Amber, Red) by Branch* Sample Unit Layout Map Project Formulation Map 5-Color PCI Summary Map

PCI Color Rating

“A” Good 86 - 100 Dark Green “B” Satisfactory 71 - 85 Green “C” Fair 56 – 70 Yellow “D” Poor 41 – 55 Orange “E” Failing 0 - 40 Dark Red

9.6. DELIVERABLES DISTRIBUTION

Send the deliverables to the following addresses:

Agency (Digital Deliverable)

Rafael Flores, rafael.e.flores-acosta.civ@army.mil

Dr Mohamed Y. Shahin, Mo@myshahin.com

Matthew Bennett, matthew.d.bennett@usace.army.mil

10. PROJECT SCHEDULE

- Provide Monthly status reports to the USACE POC via email.

- Initiate start of work prior to the Field Survey In-brief. Contact the installation POC within 15 days of the Task

Order award and provide the POC with a summary of the work requirements in this task order SOW. Begin preparations for the Field Survey In-brief with the installation POC.

- Kick-off Meeting – Conduct virtual Kick-off meeting withing 30 days after Award of Task Order. The kick-off meeting should include USACE POC, Installation POC, and installation stakeholders determined by Installation

POC. Topic included in the kick-off meeting should include, at a minimum, introduction of the project team, general overview of the scope, anticipated schedule and deliverables, and the opportunity for stakeholders to ask questions.

- Field Survey In-brief – Conduct field survey In-brief within 60-90 calendar days after Award of Task Order.

- Database Draft 1 – Submit draft 1 database for review no more than one (1) month after the completion of the condition survey.

- Database Draft 2 – Submit draft 2 database for review no more than three (3) months after the completion of the condition survey.

- Draft Report and Database Draft 3 – Submit Draft Report and Database Draft 3 for review no more than three

(3) months after the completion of the condition survey or about Seven (7) months after Award of Task Order, whichever comes first.

Final Report & Database – After incorporating review comments, submit the Final Report and PAVER Database within 10 months after Award of Task Order.

11. POINTS OF CONTACT

Although other Government personnel may clarify technical points or supply relevant information, only the Contracting Officer has the authority to revise any requirements in this Scope of Work, including those resulting from verbal clarifications.

11.1. IMCOM ADTIP PROGRAM MANAGER

Michael Andres Buildings and Ground Branch HQ IMCOM, G4 Public Works Division U.S. Army Installation Management Command 2405 Gun Shed Road Fort Sam Houston, TX 78234-1223 Tel: (210) 466-0593 E-mail: michael.r.andres.civ@army.mil

11.2. ARMY CORPS OF ENGINEERS

Dr. Mohamed Y. Shahin

USACE-ED-TX

5382 Trade Wind Ct Windsor, CO 80528 Phone : (217) 417-3308 E-mail: mo@myshahin.com

Matthew Bennett

USACE-ED-TX

1616 Capitol Avenue Omaha, NE 68102 Phone : (402) 326-5646 E-mail: matthew.d.bennett@usace.army.mil

11.3 FORT RILEY DPW ENGINEERING

Rafael E. Flores PAVER Program Manager Engineering Division Directorate of Public Works USAG Fort Riley, Kansas Desk:(785) 239-0423

DSN: (312) 856-0423

rafael.e.flores-acosta.civ@army.mil

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 03-Jun-2024 02:00 PM to 10-Jun-2024 02:00 PM.

(End of Summary of Changes)