Solicitation W9128F24R0070- 12655 Natick.pdf

SEE ADDENDUM

(No Collect Calls)

W9128F24R0070 25-Jun-2024

b. TELEPHONE NUMBER 8. OFFER DUE DATE/LOCAL TIME

02:00 PM 16 Jul 2024

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

W9128F9. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

U.S. ARMY CORPS OF ENGINEERS, OMAHA DIST

CONTRACTING OFFICE

1616 CAPITOL AVENUE

OMAHA NE 68102-4901

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 966752 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

COE PROGRAMS MANAGEMENT BRANCH

CENWO-PPMD-INVOICES

USA, OMAHA CENWO-PM-P

1616 CAPITOL AVE

OMAHA NE 68102-4901

TEL: 402-995-2800 FAX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$25,500,000

NAICS:

541330

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF37

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

W9128F24R0070

Section SF 1449 - CONTINUATION SHEET

SCOPE OF WORK

Scope of Work Road and Parking Pavement Condition Inspection and

PAVER Pavement Management System Update US Army Natick Soldiers Systems Center

28 May 2024

Attachments: 1- PAVER Database 2 – Report Cover Letter Template 3 – Example Report

1. OBJECTIVE

The objective of this effort is to perform pavement condition inspections of all the active paved roads and parking areas at US Army Natick Soldiers Systems Center, MA. The efforts at US Army Natick Soldiers Systems Center, MA are a re-inspection. The areas to be inspected are summarized in the Pavement Network table below. Accomplish all work in accordance with ASTM D6433 (20 or later) except for the sampling rate as identified under task descriptions.

PAVER database shall be developed in accordance with UFC 3-270-08 and as specified in these performance requirements. Use PAVER™ Version 7.1.2 or higher.

US Army Natick Soldiers Systems Center, MA - Pavement Network

Paved Areas Total

Pavement Area (SY)

Number of Sections

Number of Sample Units to be Inspected

Roadway - AC 33,240 35 77

Roadway - PCC 50 2 2

Parking - AC 65,887 24 64

Parking - PCC 439 5 5

Total 99,616 66 148

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 at each installation 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 Garrison 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).

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.). Branch IDs in PAVER shall have the appropriate Prefix as shown in the tables below (note the change from PA to PL for Paved Parking Area).

7.2. 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.3. 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 an 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.4. 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.5. 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.6. Update Prediction Models. Update all existing prediction models for all pavements 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.7. Condition Performance Analysis. Perform condition analysis (e.g., Past, current, and future condition assuming only stop-gap M&R).

7.8. 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.9. 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. All models should be within the PAVER database. Submit PAVER Database to the USACE POC as Database Draft #2.

7.10. 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.11. 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.12. 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.13. 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.14. 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.5.

9.5. REPORTS

The Contractor shall produce one draft and one final PAVER update report for each location. The reports shall be submitted in color printed format and electronically in PDF format on external solid-state drive (SSD) USB connected hard drive. 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 and use the example report as a template.

9.5.1. Cover: The attached Report Cover Template shall be used. The Contractor shall not place their A-E logo on the cover.

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)

Natick - David Bright, david.j.bright11.civ@army.mil 1

Dr Mohamed Y. Shahin, Mo@myshahin.com 1

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

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 five (5) 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) 720-3457 E-mail: matthew.d.bennett@usace.army.mil

11.3 US ARMY NATICK SOLDIERS SYSTEMS CENTER, MA

David Bright, P.E., M.Eng.

Chief of Business Operations and Integration, DPW Acting Chief of Engineering Division, DPW Bldg. 45, Room L100E Com: (508) 206-4119 Cell: (904) 553-5164 Email: david.j.bright11.civ@army.mil

CLAUSES BY FULL TEXT

Antiterrorism (AT)/Operations Security (OPSEC) Provisions

1. General security requirements and guidance: The security requirements described below apply to all contract personnel (including employees of the prime Contractor (“Contractor”) and all subcontractor employees) supporting the performance requirements of this contract. The Contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated Government representative (e.g., Contracting Officer Representative (COR), Requiring Activity (RA) representative, or Contracting Officer (if a COR or other RA representative is not appointed)). Contract personnel are critical to the overall security and safety of US Army Corps of Engineers (USACE) installations, facilities and activities, and security awareness training contributes to those efforts. The Department of Defense (DoD) and Army security training requirements specified below, if applicable, are performance requirements; all applicable contract personnel shall complete initial training within 30 days of contract award or the date new contract personnel begin performance on the contract. Within five business days from the completion of training, the Contractor shall provide written documentation (e.g., email or memorandum) to the Government representative. The documentation shall include the names of contract personnel trained and which training they completed; the Contractor shall maintain training records as part of their contract files and be prepared to provide copies of training certificates to the Government representative. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as “RAMs”), and Health Protection Condition (HPCON) measures. The Contractor is responsible for meeting performance requirements during elevated FPCON and/or HPCON levels in accordance with applicable RA plans and procedures—this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the Government may implement security changes that affect contract personnel. The Contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.

2. Antiterrorism (AT) Level I training: All contract personnel requiring routine access to Army installations, facilities, and controlled access areas, or requiring network access shall complete initial and annual refresher AT Level I awareness training. Online AT Level I awareness training is available at https://jko.jten.mil/ (website subject to change).

3. Physical security and access control requirements: All contract personnel requiring physical access to a federal installation or facility shall comply with the access control procedures of that location. Contract personnel requiring unescorted access to meet contract performance requirements on a DoD installation in the US shall be vetted by the installation/facility Provost Marshal/Directorate of Emergency Services/Security Office using the National Crime Information Center-Interstate Identification Index (commonly referred to as “NCIC-III”) and Terrorist Screening Database (commonly referred to as “TSDB”). Contract personnel shall comply with all personal identity verification requirements specified in installation/facility policies and procedures. Contract personnel who do not meet requirements for unescorted access to USACE facilities shall coordinate escorted access with the Government representative, as needed. Contract personnel who receive keys, access cards, or lock combinations that provide access to government-owned property shall comply with key and lock control procedures of the RA.

4. Contract personnel requiring a common access card (CAC): Contract personnel will be issued a common access card (CAC) only if duties involve one of the following: (1) both physical access to a DoD facility and access to DoD information systems or networks; (2) remote access to a DoD information system or network using DoDapproved remote access procedures; or (3) physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. Before CAC issuance, contract personnel must have, at a minimum, a favorably adjudicated Tier 1 investigation or an equivalent or higher investigation in accordance with applicable Army regulations and Homeland Security Presidential Directive-12 (HSPD-12). At the discretion of the RA, an initial CAC may be issued based on a favorable review of a fingerprint check and a successfully scheduled Tier 1 investigation with the National Background Investigations Bureau. The RA provides contract personnel with additional information and forms to initiate the CAC issuance process, and/or to initiate background investigations, when required. Contract personnel shall complete these processes within established timelines to avoid delays.

5. Security requirements for contract performance outside the US: For contract performance requirements that involve services or delivery in a foreign country, the Contractor shall comply with the requirements of DFARS clause 252.225-7043, as applicable. For performance requirements that involve contract personnel accompanying or supporting US Armed Forces deployed outside the US, the Contractor shall comply with the requirements of DFARS clause 252.225-7040, as applicable. Contract personnel accessing DoD or other federal facilities outside the US shall comply with applicable Status of Forces Agreements and Geographic Combatant Command requirements.

Prior to contract personnel traveling outside the US, the Contractor shall provide documentation of AT, OPSEC, and other required training to the COR, or other RA representative. Additionally, contract personnel shall comply with travel requirements specified in the DoD Foreign Clearance Guide, including country and theater clearance processes.

6. Suspicious Activity Reporting training (e.g. iWATCH, CorpsWatch, or See Something, Say Something): All contract personnel shall receive initial and annual refresher training from the RA representative on the local suspicious activity reporting program. This locally developed training provides contract personnel with general information on suspicious behavior, and guidance on reporting suspicious activity to the project manager, security representative or law enforcement entity.

7. Contract personnel requiring access to Government information systems: All contract personnel with access to a government information system (including USACE business systems and CAC-enabled websites) shall comply with applicable DoD and Army regulations, and shall use the organization’s UserID-Password Administration and Security System (U-PASS) at commencement of services to request network user accounts. Contract personnel shall complete DoD Information Assurance Awareness training prior to accessing information systems, and annually thereafter.

8. Contracts requiring a formal OPSEC program: The Contractor shall develop an OPSEC SOP/Plan within 90 days of contract award. The OPSEC SOP/Plan shall be reviewed and accepted by the RA OPSEC Officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it, and why it needs to be protected. In accordance with Army and DoD regulations, the contractor shall have a certified Level II OPSEC coordinator, who shall ensure OPSEC compliance during contract performance.

9. Training requirements for the protection of sensitive information: All contract personnel with access to critical information (as identified in the RA’s OPSEC Program) shall complete initial and annual refresher OPSEC Level I Awareness training, which is available at the following websites: https://www.iad.gov/ioss/, or http://www.cdse.edu/catalog/operations-security.html (websites subject to change). All contract personnel with access to Controlled Unclassified Information (CUI) shall complete initial and annual refresher CUI training in accordance with applicable Army policy.

10. Information Assurance (IA)/Information Technology (IT) requirements: All contract personnel performing IA/IT services must comply with DoD training and certification requirements specified in DoD 8570.01-M, Information Assurance Workforce Improvement Program. Contract personnel shall provide the Government representative with documentation of requisite certification(s) prior to performing on the contract. In accordance with applicable DoD, Army, and USACE regulations, the Contractor shall ensure that all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract comply with cybersecurity and architectural requirements, including, but not limited to: security technical implementation guides (STIG)(e.g., the current version of the Application Security and Development STIG, and the internet access point (IAP) demilitarized zone (DMZ) STIG), and the use of security controls developed under the risk management framework documentation for the system or platform. The Contractor shall address questions regarding these provisions to the Government representative, who will coordinate between the Contractor and the USACE Chief Information Officer

(CIO).

11. Contracts requiring handling or access to classified information: The prime Contractor shall have a Facility Clearance (FCL) at the appropriate level prior to performance on the contract; the RA will sponsor the prime contract company in obtaining the FCL. All cleared contract personnel shall comply with the FCL requirements, as well as applicable laws and regulations regarding contractor access to national security information. For classified contracts, the RA will generate the DD Form 254, which will be attached to the contract.

12. Threat Awareness Reporting Program: All contract personnel who maintain an active security clearance shall receive initial and annual refresher training on the Threat Awareness and Reporting Program (commonly referred to as “TARP”), provided by a Counterintelligence Agent. As determined by the servicing Counterintelligence Agent for the RA, contract personnel may complete web-based TARP training.

13. Escorting in classified and/or sensitive areas: In accordance with applicable regulations, all contract personnel who do not possess the appropriate security clearance or access privileges will be escorted in areas where they may be exposed to classified information or operations, sensitive information or activities, or restricted areas.

14. Pre-screen candidates using E-Verify Program: Contractors shall comply with the requirements set forth in FAR clause 52.222-54 Employment Eligibility Verification and FAR Subpart 22.18 in using the E-Verify Program at (https://www.e-verify.gov/) (website subject to change) to meet the contract employment eligibility requirements.

Contractors are encouraged to cooperate with Federal and State agencies responsible for enforcing labor requirements to include eligibility for employment under United States immigration laws in accordance with FAR 22.102-1(i). An initial list of verified/eligible candidates shall be provided to the COR no later than three business days after the initial contract award. When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, and submit it to the Contracting Officer to become part of the official contract file.

15. Contracts requiring armed security guards: All contract personnel performing contract security guard duties shall comply with the Individual Reliability Program in accordance with AR 190-56 (The Army Civilian Police and Security Guard Program), as well as applicable installation, facility and area commander installation/facility policies and procedures regarding storing weapons and ammunition in accordance with AR 190-11 (Physical Security of Arms Ammunition, and Explosives).

16. Contracts requiring delivery of food and water: The supplies delivered under this contract shall be transported in delivery conveyances maintained to prevent tampering with and/or adulteration or contamination of the supplies, and if applicable, equipped to maintain a prescribed temperature. All delivery vehicles and storage locations are subject to inspection at any time by the COR, Post Veterinarian, law enforcement officers, or other RA representatives authorized to conduct such inspections. When the sanitary conditions of the delivery conveyance have led, or may lead to product contamination, adulteration, constitute a health hazard, the delivery conveyance is not equipped to maintain prescribed temperatures, or the transport results in product “unfit for intended purpose,” supplies tendered for acceptance may be rejected without further inspection. As the holder of a contract with the DoD, the Contractor shall ensure that all products and/or packaging have not been tampered with or contaminated.

The Contractor shall ensure all delivery conveyances are always locked or sealed, except when actively loading or unloading. Unsecured vehicles shall not be left unattended. All incoming truck drivers shall provide adequate identification upon request. In the event of an identified threat to a delivery location, or a heightened force protection/Homeland Security threat level, the Contractor may be required to adjust delivery routes to minimize vulnerability risks and enable direct delivery to DoD facilities.

OMBUDSMAN

OMBUDSMAN (14 JULY 2023)

Task and Delivery Order Ombudsman. IAW FAR 16.505(B)(6) referring to FAR Part 16 "Ordering". The head of the agency has designated a task-order contract and delivery-order contract ombudsman. The ombudsman must review complaints from contractors and ensure they are afforded a fair opportunity to be considered, consistent with the procedures in the contract. The ombudsman is a senior agency official who is independent of the contracting officer and may be the agency's competition advocate.

Richard L. Jenkins TO/DO Ombudsman 7701 Telegraph Road Alexandria, VA 22315-1000

PH: (202) 761-1000

(End of clause)

GENERAL INFORMATION

GENERAL INFORMATION

CONTRACTOR PERFORMANCE ASSESSMENT REPOSITORY SYSTEM (CPARS)

AFARS Subpart 5142.15 – Contractor Performance Information UAI 5142.1502-100 – USACE roles and responsibilities for Contractor Performance Assessment Reporting System (CPARS).

The Engineering Regulation (ER) 415-1-17, Construction Contractor Performance Evaluations, sets forth the roles, responsibilities, and time requirements for construction contractor performance assessments.

The Engineering Pamphlet (EP) 715-1-7, Architect-Engineer (A-E) Contracting in USACE, sets forth the roles, responsibilities, and time requirements for A-E contractor performance assessments.

A-E SERVICES FOCAL POINT: John Galloway (402) 995-2466, john.r.galloway@usace.army.mil A-E Assessing Official (AO) is the COR John Galloway (402) 995-2466, john.r.galloway@usace.army.mil A-E Reviewing Official (RO) is John Benson, John.m.benson@usace.army.mil

INVOICES (A-E Services) Please reference “Contract W9128F24PXXXX (to be determined) on all submittals and invoices. Contractor is required to include the Contract number on the invoice, so that receipt and payment may be expeditiously processed.

Progress Payments are authorized, subject to approval from Contracting Officer’s Representative.

Electronic Funds Transfer will be the method of payment. Please ensure all account information is current and provided to the Finance and Accounting Center, Millington, TN.

Electronic Funds Transfer capability (a.k.a. direct deposit) is required for receipt of payment for services rendered under the resulting contract. Bill only for services rendered and send the invoices to the attention of CENWOPPMD- Invoices. Contractor is required to include the contract number on all invoices so that receipt and payment for the supplies may be expeditiously processed. Be sure that you are invoicing for correct contract CLIN Line-Item Number when you submit for payment. Submit invoices to:

Department of the Army U.S. Army Corps of Engineers, Omaha District ATTN: CENWO-PPMD-Invoices 1616 Capitol Avenue

Omaha, NE 68102-4901 E-mail: CENWO-PPMD-Invoices@usace.army.mil Payments will be made by: Department of the Army U.S.