AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

J

PAGE OF PAGES

1 3

2. AMENDMENT/MODIFICATION NUMBER

3. EFFECTIVE DATE

01 MAY 2026

4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

99248

6. ISSUED BY CODE W912QR 7. ADMINISTERED BY (If other than Item 6) CODE

W072 ENDIST LOUISVILLE

KO CONTRACTING DIVISION, 600 DR MARTIN LUTHER

LOUISVILLE, KY 40202-2230

UNITED STATES

RANZEL MERIDETH, EMAIL: RANZEL.L.MERIDETH@US

(502) 315-6590

KING JR PL

ACE.AMY.MIL TELEPHONE:

SCD: PAS:

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

W912QR26RA016

9B. DATED (SEE ITEM 11)

13 MAR 2026

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

CODE

11. THIS IT

FACILITY CODE

EM ONLY APPLIES TO A MENDMENTS OF S OLICITATIONS

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

Offers 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 electronic communication 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 letter or electronic communication, provided each letter or electronic communication 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)

SEE SECTION G - CONTRACT ADMINISTRATION DATA

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

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

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

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, 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.)

See Summary of Changes.

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) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

W912QR26RA016_Specs-0002

W912QR26RA0160002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

AMENDMENT 0002 - P2 511686 UEPH FY 26 Barracks Ft Campbell, KY

W912QR26RA016

Amendment 0002

SUMMARY OF CHANGES

1. The following SPECIFICATION SECTIONS have been revised and replaced in their entirety:

01 32 01.00 06 01 50 00 05 50 13 08 11 13 08 14 00 08 41 13 14 21 23 21 13 13 21 30 00 22 00 00 23 03 00 23 09 13 23 64 10

PROJECT SCHEDULE

TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

MISCELLANEOUS METAL FABRICATIONS

STEEL DOORS AND FRAMES

WOOD DOORS

ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

ELECTRIC TRACTION PASSENGER ELEVATORS

WET PIPE SPRINKLER SYSTEMS, FIRE PROTECTION

FIRE PUMPS

PLUMBING, GENERAL PURPOSE

BASIC MECHANICAL MATERIALS AND METHODS

INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

WATER CHILLERS, VAPOR COMPRESSION TYPE

2. The following SPECIFICATION SECTIONS have been added in their entirety:

NONE for Amendment 0002

3. The following SPECIFICATION SECTIONS have been deleted in their entirety:

NONE for Amendment 0002

4. The following PLAN SHEETS have been revised and replaced in their entirety:

G-1002 SHEET INDEX

G-1003 SHEET INDEX

CU101 OVERALL UTILITY PLAN

CU102 UTILITY PLAN

CU105 UTILITY PLAN

A-501 WALL SECTION DETAILS

A-512 ROOF ISOMETRIC DETAILS

A-513 ROOF ISOMETRIC DETAILS

A-601 PARTITION TYPES, SCHEDULE, AND DETAILS

A-611 DOORS AND FRAMES SCHEDULE AND DETAILS

A-662 DOOR DETAILS-HOLLOW METAL (HM)

A-671 WINDOW AND FRAMES AND SCHEDULES AND TYPES AND DETAILS

A-682 ALUMINUM CURTAIN GLASS WALL DETAILS

E-121 1ST FLOOR POWER PLAN

E-122 1ST FLOOR POWER PLAN – LEFT

E-123 1ST FLOOR POWER PLAN – CENTER

E-124 1ST FLOOR POWER PLAN – RIGHT

E-127 2nd FLOOR POWER PLAN CENTER

E-131 3RD FLOOR POWER PLAN CENTER

E-135 4TH FLOOR POWER PLAN CENTER

E-139 5TH FLOOR POWER PLAN CENTER

E-402 1ST AND 2ND FLOOR ELECTRICAL ROOM ENLARGED

E-403 3RD, 4TH, 5TH FLOOR ELECTRICAL ROOM ENLARGED

E-411 STACKED ELECTRICAL ROOM SECTION VIEWS – ALL FLOORS

E-604 ELECTRICAL SINGLE LINE DRAWING

E-605 CONDUIT SCHEDULE AND GROUND DETAILS

E-608 PANEL SCHEDULES

E-612 PANEL SCHEDULES

E-613 PANEL SCHEDULES

E-614 PANEL SCHEDULES

E-615 PANEL SCHEDULES

E-616 PANEL SCHEDULES

E-617 PANEL SCHEDULES

E-618 PANEL SCHEDULES

E-619 PANEL SCHEDULES

FA-106 FAMNS PLAN

FA-501 SEQUENCE OF EVENTS MATRIX

T-001 GENERAL NOTES

T-503 TELECOM OUTLET DETAILS

T-504 DOOR ALARM AND RISER AND DETAILS

M-111 FIRST FLOOR HVAC DUCTWORK PLAN - AREA 1A

M-112 FIRST FLOOR HVAC DUCTWORK PLAN - AREA 1B

M-116 FIRST FLOOR HVAC PIPING PLAN - AREA 1B

M-122 SECOND FLOOR HVAC DUCTWORK PLAN - AREA 2B

M-132 THIRD FLOOR HVAC DUCTWORK PLAN - AREA 3B

M-142 FOURTH FLOOR HVAC DUCTWORK PLAN - AREA 4B

M-152 FIFTH FLOOR HVAC DUCTWORK PLAN - AREA 5B

M-401 FIRST FLOOR MECHANICAL ROOM

M-501 MECHANICAL DETAILS

M-602 MECHANICAL EQUIPMENT SCHEDULES

M-605 MECHANICAL EQUIPMENT SCHEDULE

M-701 POINTS SCHEDULE INSTRUCTIONS

M-702 CONTROL SYSTEM NETWORK

M-703 MAWHP-1 & 2 CONTROL SCHEMATIC

M-716 ENERGY CONTROLS MONITORING

5. The following PLAN SHEETS have been added new:

A-672 WINDOW AND FRAMES AND SCHEDULES AND TYPES AND DETAILS

M-717 ENERGY CONTROLS MONITORING

6. The following PLAN SHEETS have been deleted:

NONE for Amendment 0002

7. The following REFERENCE documents have been added new:

00_Schedule Guide Master Template w-Specs

8. The following CLAUSES have been added:

00 70 00 – FAR 52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0038)

9. The proposal due date has been extended from 12-MAY-2026 to 26-MAY-2026.

Section 00 00 00 - Procurement and Contracting Requirements

The following changes have been made:

Section 00 70 00 - Conditions of the Contract

Additional Information/Notes

The following clauses were added:

FAR Clauses Incorporated by Reference

Number Title Effective Date Alternate/

Deviation

Variation

Effective

Date

52.222-90 Addressing DEI Discrimination by Federal

Contractors. (Deviation 2026-O0038)

Apr 2026

INFORMATION FROM TO

Response Due

Time

10:00 AM 02:00 PM

Response Due

Date

12 May 2026 26 May 2026

Party to receive

Solicitation

W912QR

W072 ENDIST LOUISVILLE

KO CONTRACTING DIVISION, 600

DR MARTIN LUTHER KING JR PL

LOUISVILLE, KY 40202-2230

UNITED STATES

W912QR

W072 ENDIST LOUISVILLE

KO CONTRACTING DIVISION, 220

W MAIN STREET 3RD FLOOR

LOUISVILLE, KY 40202-2230

UNITED STATES

SECTION 01 32 01.00 06

PROJECT SCHEDULE

10/23, CHG 1: 02/26

Amendment 0002

Amendment 0002***********************************************************

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

AACE 84R-13 (2015) Planning and Accounting for Adverse Weather

AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)

ASCE 67-17 (2017) Schedule Delay Analysis

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of

P2 511686 UEPH

Fort Campbell, KY

SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002

SECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 reports. The Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of similar size and complexity to this contract, using Primavera P6..

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification. Verifiable resume must be submitted with Initial/Baseline Schedule, failure to submit and/or unacceptable experience will render the Initial Schedule unacceptable subject to paragraphs 3.1.1 and 3.2. Any periodic schedule or TIA not meeting this requirement is unacceptable.

2.1.1 Government Default Software

The Government uses Primavera P6. Ensure exported schedule files are compatible with the CURRENT version of P6 used by the Government.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.

2.1.2.2 Other Than Primavera

If the Contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, Subcontractors, and suppliers working on the project must also contribute to developing

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002

SECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06

P2 511686 UEPH

Fort Campbell, KY and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

In conjunction with the post award conference or pre construction conference the Government and the Contractor will hold a separate and distinct Scheduling Expectations Kickoff Meeting(SEKO). The intent of this meeting is for the Government to review with the contractor the requirements of the scheduling specification, communicate the Government’s expectations regarding schedule development and management, and answer any questions the Contractor may have regarding the schedule requirements.

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN. Match the progress payment "Pay Period Thru" date in RMS to the schedule data date.

3.2.1 Activity Cost Loading

a. Activity cost loading must be reasonable and without front-end loading. Activities with a negative cost loading is not allowed.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

b. Coordinate with the Contracting Officer to request approval for, and assign costs, to the respective procurement activity for which payment will be requested for materials/equipment in advance of installation.

Any such payment request for approved material/equipment advanced payment shall be supported by a paid invoice or as determined by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial, or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate

Page 3Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2

P2 511686 UEPH

Fort Campbell, KY level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.

3.3.2.1 Actual Durations

Activities with actual durations exceeding Original Duration by 200% or more must be explained and accepted in the Narrative.

3.3.2.2 Actualized Dates

Activity dates must be actualized, marked complete in P6 Primavera, within 30 days of being identified as 100% physically complete.

3.3.3 Design and Permit Activities

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Provide a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. Also include review and correction periods associated with each item.

3.3.4 Procurement Activities

Include in the schedule activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.5 Mandatory Activities

Include the following activities in the initial project schedule and all updates. Duration of Government submittals must match the maximum number of days stated in specification 01 33 00.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission, review and acceptance of design packages.

c. Submission of mechanical/electrical/information systems layout drawings.

d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 4

f. Submission and approval of DD1354 data and installed equipment lists.

g. Submission and approval of testing and air balance (TAB).

h. Submission of TAB specialist design review report.

i. Submission and approval of fire protection specialist.

j. Submission and approval of Building Commissioning Plan, Controls testing plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

Show prerequisite, dependencies and Government review periods for all commissioning activities as required by the commissioning specification and specifications referenced therein. See attachment "Construction Schedule Commissioning Guide" for typical commissioning activities. These activities may include but are not limited to: air and water balancing, building commissioning - functional performance testing, controls testing, and performance verification testing.

Include other systems testing, if required. Include additional commissioning requirements noted elsewhere in the Contract as required in the schedule and discuss during the SEKO meeting, noted in paragraph SCHEDULING EXPECTATIONS KICKOFF MEETING (SEKO).

k. Contractor's pre-final inspection.

l. Correction of punch list from Contractor's pre-final inspection.

m. Government's pre-final inspection.

n. Correction of punch list from Government's pre-final inspection.

o. Final inspection.

3.3.6 Government Activities

Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to approvals,acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein.

The SDEF format is as follows:

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 5

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.7.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.7.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.7.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 6 craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

3.3.7.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.7.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Number (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are design phase, procurement phase and construction phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.7.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to design, design submittal, design reviews, review conferences, permits, construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.7.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 04.10 06 CONTRACTOR QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.3.8 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 7 constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.3.8.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Mandatory Start" constraint date equal to the date that the NTP is acknowledged.

3.3.8.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path.

3.3.8.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.3.8.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.8.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.9 Adverse Weather

Ensure anticipated adverse weather is accounted for in the Project Schedule. AACE 84R-13 provides methodologies for techniques in planning for adverse weather. The REQUIRED methodology is the use of a weather calendar.

3.3.10 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 8

3.3.11 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" is to have no predecessor logic, and the last activity -"End Project" is to have no successor logic. Except as noted above all activities are to have at least a start-to-start or finish-to-start relationship with its predecessor(s) and a finish-to-finish or finish-to-start relationship with its successor(s).

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.

3.3.11.1 Multiple Relationships

Multiple relationships between activities are not allowed.

3.3.12 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.13 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.14 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.3.14.1 Changes from Initial/Baseline Schedule

All changes (including but not limited to: original duration, activity name/description, activity number, activity sequence, addition of activities, deletion of activities, software logic, software/schedule settings, assigned calendar, etc) from received/approved Initial/Baseline Schedule are to be annotated in the accompanying narrative and remain in every update narrative until the project is complete.

3.3.15 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 9 item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

a. Activities with Actual Duration exceeding Original Duration by more than 10% must be identified and explained in the Narrative Report accompanying the schedule in which it occurs.

b. Activities with Actual Duration exceeding Original Duration by more than 90 days must be separated into multiple activities.

3.3.16 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb or create float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Use of positive lag greater than 10 days must be approved on a case-by-case basis by the Contracting Officer.

c. Start to Finish (SF) relationships are prohibited.

d. Activity Relationships must be justifiable to the satisfaction of the Contracting officer, not so numerous or specific as to force an activity onto the critical path, and allow reasonable flow of concurrent activities through to project completion.

e. Relationship ties to more than 5% of the scheduled activities must be explained and accepted in the Narrative.

3.3.17 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.3.18 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management. Budgeted cost of activity is to be reduced by the amount needed to correct deficiency. The activity referenced in paragraph COST LOADING of CLOSEOUT ACTIVITIES must have its budgeted cost increased by this amount.

3.3.19 Remaining Duration

Update the remaining duration for each activity based on the number of estimated workdays it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 10 paragraph entitled Percent Complete. The remaining duration for unstarted activities are not to be less than its orginal duration.

3.3.20 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

a. Schedules with any budget not matching contract values are unacceptable.

b. Payment for materials only occurs upon acceptance of installation, except as noted in specification 01 20 00.

3.3.20.1 As-Built Drawings

Refer to LRL Section 00 80 00.00 06 regarding AS-BUILT DOCUMENTS for D/B or D/B/B contracts for a determination of withholding for final as-built drawing submittals.

3.3.20.2 O & M Manuals

Refer to LRL Section 00 80 00.00 06 regarding EQUIPMENT DATA, O&M & REPAIR MANUALS WITH FIELD TRAINING REQUIREMENTS for a determination of withholding for final acceptance/approval of O&M Manuals.

3.3.21 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

a. Provide the submissions as described below. The data reports and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

b. Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.

Page 11Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2

P2 511686 UEPH

Fort Campbell, KY

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged, submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Project Schedule must begin ("NTP" or "Project Start") and end ("Project End") with 0 float and no activities completed or in-progress. The Initial Project Schedule must have a Data Date matching NTP or Project Start.

Include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences; permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Also cover in the initial design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities concurrent with the monthly schedule updating process. Constrain construction activities by Government acceptance of associated designs. When the design is complete, incorporate into the then approved schedule update all remaining detailed construction activities that are planned to occur after the dry-in milestone. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.2.1 Design Package Schedule Submission

With each design package submitted to the Government, submit a fragnet schedule extracted from the then current Preliminary, Initial or Updated schedule which covers the activities associated with that Design Package including construction, procurement and permitting activities.

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 12

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress. Update the schedule to include detailed construction activities as the design progresses, but not later than the submission of the final un-reviewed design submission for each separate design package. The Contracting Officer may require submission of detailed schedule activities for any distinct construction that is started prior to submission of a final design submission if such activity is authorized.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete. Updated information is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

c. Changes to Actual Start and Actual Finish dates are not allowed.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, every Periodic Schedule Update, and all TIAs throughout the life of the project as submittals in the Submittal Log in RMS:

3.5.1 Electronic Scheduling Data

Provide electronic scheduling data containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include the Narrative Report and all required Schedule Reports. The electronic file is to identify the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and schedule file name. Each schedule must have a unique file name and use project specific settings. The file naming convention is to be determined at SEKO meeting.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Schedule Narrative Report is a "stand alone" report in PDF or Word format. Title the report "Schedule Narrative Report". Show the Report date, schedule name, and contract number on the first page. Indicate who is responsible for the schedule update and narrative report. Provide a brief description of the Project Scope. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for problems, either current or potential, which are revealed through that analysis. Include the following information at a minimum in the Narrative Report:

a. Identify and discuss the work scheduled to start in the next update period.

b. Identify and describe Progress and Non-Progress updates made to the

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 13 schedule.

o Progress Only updates are considered to be: Actual Start (AS), Actual Finish (AF), Reduced Remaining Duration (RD) changes, and Increased Percent Complete.

o Non-Progress updates are considered to be: Addition or Deletion of Activities; Split or combined activities using new activity IDs;

Addition or deletion of logic links; Changes to lag values of logic links; Addition, Deletion, or Changes to constraints;

Changes to OD; Increases in RD such that RD becomes greater than OD; Changes to RD not accompanied by changes to Percent Complete;

Increase in RD of activities that have not started; Changes to calendar assignments; Changes to holiday assignments within a pre-existing calendar.

c. Describe activities along the critical path in addition to activities on the next float path after the critical path.

d. Describe current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective actions taken or required to be taken. Identify the party responsible for delay, if applicable.

e. Identify and explain why activities, based on their calculated late dates, should have either started or finished during the update period but did not.

f. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

g. Identify and explain why out-of-sequence work was performed and how the schedule was corrected to show as-built condition of out-of-sequence work.

h. If the longest path changes from a monthly update to the next, provide an explanation of the factors driving the change.

i. Respond to USACE Schedule Review Comments from the previous update(s).

j. Narrative must be maintained as a running record of all variations from the Initial/Baseline Schedule.

3.5.3 Schedule Reports

The format, filtering, organizing, and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 14

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Scheduling and Leveling Report

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.5.3.6 Three Week Look Ahead & Detail Schedule

a. Prepare and issue a 3-week Look Ahead schedule for each weekly meeting using a 3-week look-ahead filter to show all activities including critical activities, planned start, finish, and total float.

b. In addition, provide a more detailed day-to-day plan of upcoming work derived, but maintained separately, from the project schedule. The detailed plan is typically created and maintained by the Project Superintendent. The detailed plan information shall correspond with the Activity Numbers and Activity Description of the monthly schedule updates. It shall be attached to the corresponding QC Daily Report each week. The detailed plan activities must not exceed 5 working days in duration.

c. The activities shall include a sufficient level of detail to show upcoming outages, closures, testing, preparatory & initial meetings, prime and subcontractor crew assignments (including the name of the subcontractors and/or suppliers as necessary), anticipated crew size, material & equipment as necessary, and specific areas where work is to take place (e.g - POV parking; Ductbank between X & Y; Mech Room ###;

1st floor lobby, Area A Roof, Critical Lifts, etc.)

3.5.4 Network Diagram

P2 511686 UEPH

Fort Campbell, KY

Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2Page 15

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.4.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.5.4.3 Critical Path

Show all activities on the critical path. The critical path is defined as the single, longest path without any gap between activities.

3.5.4.4 Grouping and Sorting

Group and sort activities as directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The Contractor scheduler must attend in person unless virtual attendance is approved by Contracting Officer. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Submit schedule file and narrative to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager must attend the meeting with the authorized representative of the Contracting Officer.

Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the schedule update meeting, make corrections to the schedule and resubmit, Page 16Page 2Page 1SECTION 08 14 00 Page 1 CERTIFIED FINAL - Amendment 0002 ECTION 01 32 01.00 06Page 1SECTION 08 14 00 Page 1SECTION 01 32 01.00 06 Page 2

P2 511686 UEPH

Fort Campbell, KY following the required schedule naming convention. Include only those changes approved by the Government in the schedule review meeting. Only approved schedules may be used to generate invoices for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project…