A21 - W912PM26RA004-AMDT0003-PACKAGE.pdf

Solicitation #W912PM26RA004 Date: 16 JUNE 2026 Project Title – PHILPOTT DAM ANCHORS AND INSTRUMENTATION, HENRY AND FRANKLIN COUNTIES, VIRGINIA

Amendment No. 0003

ATRIAX-ZAPATA AND BLACK & VEATCH i

TECHNICAL SUMMARY OF CHANGES

1) CHANGES TO SPECIFICATIONS. Attached hereto are [new revised and deleted] sections to the specifications. Revision mark ***AMENDMENT 0003*** is shown on each revised page.

A) REVISED SECTION.

• Section 01 11 00 – SUMMARY OF WORK o 1.6 Any equipment, materials, and any temporary working structure in the lake and within the spillway may need to be removed if the lake is forecast to rise and result in an uncontrolled release from the spillway. If such removal is necessary, the Contractor shall temporarily plus any open borehole to the extent practicable to prevent the entry of overflowing spillway water.

o 1.6 The equipment in the lake may need to be removed if the lake is forecast to rise significantly with an uncontrolled release from the spillway.

o 1.6 The Contractor will need to establish the maximum working lake level for equipment and any temporary working structure, as well as the necessary lead time to receive notice to evacuate any equipment and any temporary working structure. Longer lead times may result in “false alarm” type evacuation notifications where the high lake level and spillway flow are not realized. Shorter lead times will allow for more accurate forecasting.

• Section 01 32 01.00 10 – PROJECT SCHEDULE o 3.1.2 Time Constraints

All work shall be performed during the hours of 0730 AM to 1600 PM.

o 3.1.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval. Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number, and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the work area shall be properly lighted, in full compliance with EM 385-1-1, and approved by the Contracting Officer. The Contractor shall also observe the Fatigue Management rules stated in EM 385-1-1.

• Section 01 50 00 – TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS o 3.5.8 Barge Mooring

VIRGINIA

ATRIAX-ZAPATA AND BLACK & VEATCH ii

Mooring a barge to the dam is allowed and is limited to the non-spillway monoliths. The barge shall be moored in such a way to not impart any vertical forces to the dam. Wind loads on the barge and equipment it carries will be transmitted to the dam and could be significant. The Contractor shall prepare an engineering analysis of the overall dam stability to include mooring forces with wind loads and submit the engineering analysis to the Contracting Office for AE and Government approval. The engineering analysis shall be sealed by a Professional Engineer licensed in the State of Virginia.

• Section 31 68 13 – SPILLWAY ANCHORS o 1.4.5.2 Regrouting Holes will be measured for payment based upon the number of cubic feet 94-pound bags of cement grout that were actually injected into the anchor hole as specified.

o 1.4.5.3 Bags of cement ( 94 lbs). Cubic feet.

• Section 33 51 43 – INSTRUMENTATION AND PERFORMANCE MONITORING OF

STRUCTURES

o 1.5.2.1 b. Automated In-Place Inclinometer: probe, carrying case, cable, readout unit, and software.

o 2.3.1 Factory-calibration curves are required for each laser water level sensor, including individual gage factor and temperature correction factor.

o 3.5.3.4 e. Plot Automated Robotic Total Station Monitoring system data as x, y, z and resultant displacement versus time, and provide in tabular format.

2) CHANGES TO DRAWINGS. Attached hereto are revised drawing sheets. Revised sheets replace like numbered sheets. The revision tracker in the Title Block of each sheet is populated to reflect the current Amendment Number and issue date.

A) REVISED DRAWINGS (ISSUED). The following revised drawings replace the like numbered drawings and are issued herewith.

• Drawings revised in entirety based on the revised Bid Schedule.

o C-400

Revised note 9 with temporary load statement.

ALL TEMPORARY LOADS FROM WORK PLATFORM

BEARING AND OTHER TEMPORARY APPLICATIONS

SHALL BE EVALUATED WITH ACI 381 (CURRENT EDITION)

USING AN APPROXIMATE f'c = 3,375 PSI.

VIRGINIA

ATRIAX-ZAPATA AND BLACK & VEATCH i

CHANGES TO SPECIFICATIONS

Philpott Dam Anchors and Instrumentation 043373

AMENDMENT 0003

SECTION 01 11 00

SUMMARY OF WORK

02/24

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes installation of spillway anchors and automated anchor load sensors. Also included are installation of inclinometers in monoliths 9 and 13 and automation of crack gauges and piezometers, and incidental related work.

1.1.2 Location

The work is located at the Philpott Lake Dam in Henry and Franklin Counties, Virginia which is approximately 7 miles north of Bassett, Virginia, as indicated on the drawings.

1.2 OCCUPANCY OF PREMISES

Philpott Dam will remain in operation throughout the duration of construction. The Government periodically requires access to service or inspect hydraulic steel structures stored in the dam crest. The Contractor shall not impede access to the hydraulic steel structure storage locations, hatches, or operational tracks during said periodic events. Furthermore, the Contractor shall coordinate with the Government and its contractors to accommodate access given a minimum of 30 days’ notice provided by Government. The Contractor may be required to temporarily relocate equipment, move stored materials, and clear the roadway leading to the dam crest to facilitate these operations. The storage hatches are contained within Monoliths 7, 8, and 9. Any disruption of construction operations will be minimized. Access may be required for up to 5 business day increments per occurrence.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.3 EXISTING WORK

Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, affected existing work must be in a condition equal to or better than that which existed before new work started.

1.4 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with installation requirements for locating and marking underground utilities.

Contact local utility locating service a minimum of 48 hours prior to

SECTION 01 11 00 Page 1 excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a holiday. Verify existing utility locations indicated on contract drawings, within area of work.

Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities or utilities encased in dam structures are discovered. Verify the elevations of existing piping, utilities,and any type of underground or encased obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

1.4.1 Notification Prior to Excavation

Notify the Contracting Officer at least 48 hours prior to starting excavation work.

1.5 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at a location designated by the Government.

Maintain a list of material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Provide a system for property control in the salvage plan. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.

***AMENDMENT 0003***

1.6 LAKE OPERATION INFORMATION

Philpott Lake operation information is discussed in the Water Control Plan for Philpott Lake dated June 1992 (minor editorial changes March 2004):

https://epec.saw.usace.army.mil>PhilpottWCP.pdf

In summary, it is the intent of the Water Control Plan to operate Philpott Dam to maintain the lake level at, or near, the guide curve elevation.

The guide curve is at elevation 970.8 feet NAVD88 from October through January and at elevation 972.8 feet NAVD88 from April through July. The guide curve varies linearly between the two limits from February through March and from August through September.

The latest information including Project Description, Pertinent Data, Daily Operating Log Files, Daily Reservoir Reports, Projected Lake Levels during Flood Events, Recent Elevation and Flow Information, and Historic Lake Elevation, Inflow and Outflow data are provided on the following website:

https://epec.saw.usace.army.mil/roanphil.htm

The hydrograph of the daily midnight lake elevation data is provided on Attachment A.

SECTION 01 11 00 Page 2

The Philpott Pool Elevation Duration Curve is provided on Attachment B.

Data and information furnished or referred to above is for the Contractor's information. The Government shall not be responsible for any interpretation of, or conclusion drawn from the data or information by the Contractor.

Flood events, high flow rates, and high-water levels, as well as drought and low-water conditions may occur during construction. Therefore, the Government does not guarantee that water levels in the lake will not fluctuate accordingly.

The equipment in the lake and within the spillway may need to be removed if the lake is forecast to rise significantly with an uncontrolled release from the spillway. Any equipment, materials, and any temporary working structure in the lake and within the spillway may need to be removed if the lake is forecast to rise and result in an uncontrolled release from the spillway. If such removal is necessary, the Contractor shall temporarily plug any open borehole to the extent practicable to prevent the entry of overflowing spillway water.

The Contractor will need to establish the maximum working lake level for equipment and any temporary working structure, as well as the necessary lead time to receive notice to evacuate any equipment and any temporary working structure. Longer lead times may result in "false alarm" type evacuation notifications where the high lake level and spillway flow are not realized. Shorter lead times will allow for more accurate forecasting .

The Contractor shall submit the above information in the Construction Site Plan ( 01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS, paragraph

CONSTRUCTION SITE PLAN)

***AMENDMENT 0003***

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 3

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 01 11 00 Page 4

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/23, CHG 1: 08/24

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)

EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements

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

1.2 SUBMITTALS

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

Submittals not having a "G" classification are for information only. 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 reports. The Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of

SECTION 01 32 01.00 10 Page 1 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.

2.1.1 Government Default Software

The Government uses Primavera P6. Ensure exported schedule files are compatible with the 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 construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors, and suppliers working on the project must also contribute in developing 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.

3.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

In conjunction with the post award conference or pre construction

SECTION 01 32 01.00 10 Page 2 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.

***AMENDMENT 0003***

3.1.2 Time Constraints

All work shall be performed during the hours of 0730 to 1600.

3.1.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number, and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the work area shall be properly lighted, in full compliance with EM 385-1-1 , and approved by the Contracting Officer. The Contractor shall also observe the Fatigue Management rules stated in

EM 385-1-1 .

***AMENDMENT 0003***

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

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.

3.2.2 Cost Loading of Submittals

No costs are to be assigned to activities for the preparation, review, or approval of submittals, except as described under paragraph COST LOADING OF CLOSEOUT ACTIVITIES, paragraph AS-BUILT DRAWINGS, and paragraph O&M

MANUALS.

3.2.3 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

SECTION 01 32 01.00 10 Page 3 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 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.3 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.4 Mandatory Activities

Include the following activities in the initial project schedule and all updates.

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

b. Submission, review and acceptance of features requiring design completion

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.

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

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

These activities may include but are not limited to: commissioning -functional performance testing, and performance verification

SECTION 01 32 01.00 10 Page 4 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).

h. Contractor's pre-final inspection.

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

j. Government's pre-final inspection.

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

l. Final inspection.

3.3.5 Government Activities

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

3.3.6 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:

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.

SECTION 01 32 01.00 10 Page 5

3.3.6.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.6.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.6.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 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.6.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.6.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.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are 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.

SECTION 01 32 01.00 10 Page 6

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.6.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 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.6.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 00 QUALITY CONTROL.

An activity can have only one Feature of Work Code.

3.3.7 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 constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or affect 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.7.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 "Start On" constraint date equal to the date that the NTP is acknowledged.

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

SECTION 01 32 01.00 10 Page 7

3.3.7.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.7.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.8 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 preferred methodology is the use of a weather calendar. If a method other than a weather calendar is proposed, discuss the reason during the SEKO meeting.

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

If a weather calendar is used its implementation and execution is to be in accordance with AACE 84R-13

3.3.10 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, each activity must have at least a start-to-start or finish-to-start relationship with its predecessor and a finish-to-finish or finish-to-start relationship with its successor.

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

3.3.11 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.12 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

SECTION 01 32 01.00 10 Page 8 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.13 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 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.3.15 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. Start to Finish (SF) relationships are prohibited.

3.3.16 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.17 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.18 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 paragraph entitled Percent Complete. The remaining duration for unstarted activities are not to be less than its orginal original duration.

SECTION 01 32 01.00 10 Page 9

3.3.19 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).

3.3.19.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.19.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.20 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 hours) 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

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.

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

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

SECTION 01 32 01.00 10 Page 10 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. Code activities that are summary in nature, after the first 90 calendar days, with the following activity codes: 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. No payment will be made for work items not fully detailed in the Project Schedule.

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.

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.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

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

SECTION 01 32 01.00 10 Page 11 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. Describe activities along the critical path in addition to activities on the next float path after the critical path.

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

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

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

f. Identify and discuss out-of-sequence work.

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

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

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.

Provide 3 set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

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.

SECTION 01 32 01.00 10 Page 12

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

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 longest path.

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

SECTION 01 32 01.00 10 Page 13

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, 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 Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 workdays after the periodic schedule update meeting.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 REQUESTS FOR TIME EXTENSIONS

ASCE 67-17 provides delay analysis guidelines. If there is a conflict between the contract and guidance provided in ASCE 67-17 , the contract will govern. Provide justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval, within 10 days of a delay occuring. Also prepare a time impact analysis for each Government request for proposal (RFP).

SECTION 01 32 01.00 10 Page 14

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date, or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Changes That Do Not Cause Delay

If it is determined that a change does not constitute a schedule time extension, a fragnet as described in paragraph FRAGMENTARY NETWORK, is to be created and inserted into the Project schedule.

3.8.3 Time Impact Analysis (Prospective Analysis)

Submit requests for time extensions based on a prospective analysis if the work involved or the impact identified has not already occurred. Where the impact is ongoing a prospective analysis may be considered. However, the Government reserves the right to require a retrospective analysis be prepared after the impact has ended.

Prepare a time impact analysis for approval by the Contracting Officer based on industry recommended practice AACE 52R-06 . Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.8.4 Forensic Schedule Analysis (Retrospective Analysis)

Submit requests for time extensions based on a retrospective analysis if the work involved or the impact identified has already occurred. The analysis must account for the actual performance of both the impacted work and all other contract work in the schedule.

If a methodology is chosen from AACE 29R-03 , the method must adhere to the principles identified in ASCE 67-17 . If there is a conflict with the methodology chosen from AACE 29R-03 and ASCE 67-17 , ASCE 67-17 will govern. Choice of methodology should be discussed prior to submission to Government.

3.8.5 Fragmentary Network (Fragnet)

Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the

SECTION 01 32 01.00 10 Page 15 project schedule.

3.8.6 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay, are not a cause for an extension to the performance period, completion date, or any interim milestone date.

3.8.7 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.9 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are…