W912ES24B0012_Amend_2 Section 01 14 00.00 13.pdf

LD2GWREPAIR W912ES-24-B-0012

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 14 00.00 13

WORK RESTRICTIONS

PART 1 GENERAL

1.1 REFERENCES

1.2 GROUNDS AND ROADWAYS

1.2.1 Snow Removal

1.3 BLASTING

1.4 STAGING AREA

1.5 SUBMITTALS

PART 2 PRODUCTS

PART 3 EXECUTION

3.1 EXISTING UTILITIES

3.1.1 General

3.1.2 Buried Utilities

3.1.3 Interruption of Services

3.2 PROTECTION OF TREES

3.2.1 Restoration of Damaged Trees

3.3 DEFINED NON-NAVIGATION SEASON

3.4 CONTRACTOR PROPOSED DISPOSAL AREAS

3.5 PRE AND FINAL DIVING INSPECTIONS

3.6 NAVIGATION NOTICE

3.7 NAVIGATION PLAN

3.7.1 Navigation Assistance

3.7.1.1 Minimum Helper Boat Requirements

3.7.1.2 Helper Boat Availability

3.7.1.3 Government Vessels

3.8 FLOATING PLANT

3.8.1 Equipment and Personnel

3.8.2 Navigable Waters

3.8.3 Sewage and Bilge Water Disposal

3.9 WILDLIFE

3.9.1 Northern Long-eared Bat Exclusion Periods

3.9.2 Eagles

3.9.2.1 Avoidance and Minimization

3.9.2.2 Other Conditions

3.10 ATTACHMENTS

-- End of Section Table of Contents --

SECTION 01 14 00.00 13 Page 1 Jul 23, 2024 AMENDMENT 2 - SOLICITATION

SECTION 01 14 00.00 13

WORK RESTRICTIONS

PART 1 GENERAL

Lock and Dam 2 hours of Operation are as followed: Monday through Friday 0700 to 1700. Additional hours will require Government notification.

(Refer to Section 01 00 00.00 13 GENERAL, Paragraph 3.2.2).

1.1 REFERENCES

CODE OF FEDERAL REGULATIONS

46 CFR Chapter 1 Sub Q (2024) Equipment, Constructions, and Materials: Specifications and Approval

1.2 GROUNDS AND ROADWAYS

1.2.1 Snow Removal

The Contractor is responsible for snow removal in the Contractor's access, work, and parking areas.

1.3 BLASTING

Blasting will not be permitted.

1.4 STAGING AREA

All construction laydown and staging areas used for staging of material, equipment, supplies, field offices and parking will be as shown on the drawings. Coordinate final location of all laydown and staging areas with the Contracting Officer for approval to allow sufficient room for staff and public access prior to mobilizing to the site.

1.5 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation 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

Interruption Of Services ; G

PART 2 PRODUCTS

(Not Used)

SECTION 01 14 00.00 13 Page 2

PART 3 EXECUTION

3.1 EXISTING UTILITIES

3.1.1 General

Coordinate all utility relocation requirements. The Contractor is responsible for payment to the utility companies for all services, fees, and permits required to relocate and reestablish service. Protect all existing utilities.

3.1.2 Buried Utilities

The approximate locations of known existing buried utilities are shown on the drawings to the extent of available information at the time the drawings were prepared. Prior to commencing excavation, accurately locate all such installations. Notify the Contracting Officer immediately be notified if the Contractor damages any existing utility lines not intended to be removed. Repair of damaged utilities must be in accordance with

CLAUSE 52.236-9 PROTECTION OF EXISTING VEGETATION, STRUCTURES, EQUIPMENT,

UTILITIES, AND IMPROVEMENTS.

3.1.3 Interruption of Services

Utility services must not be interrupted except for brief periods to facilitate cut-ins. Provide temporary service and relocate existing utilities as required to construct the work shown and insure uninterrupted service. If interruption of services is unavoidable, request approval in writing at least 15 calendar days prior to the proposed interruption.

This submittal must fully describe all details of proposed interruption and the reasons why alternatives are not feasible. Information contained in the submittal must include, but not be limited to, utilities being affected, duration of outage, and any sketches required to support the submittal. Coordinate with the owner of the utility and notify affected consumers at least 10 calendar days in advance of interruption of services. The Contracting Officer will not approve proposals which require interruption of services for more than 4 continuous hours.

3.2 PROTECTION OF TREES

Trees outside of the clearing and grubbing limits or trees designated to remain must be protected as indicated below. The location of the tree protection fence must be staked by the contractor and approved by the Contracting Officer.

The following measures must be implemented for tree protection and must be addressed in the Environmental Protection Plan required under Section

01 57 20.00 13 ENVIRONMENTAL PROTECTION:

a. The trees must be protected from wounds to the bark and foliage.

b. The critical root zone must be protected from compaction and grading.

c. Changes in temporary site drainage and ponding that affect the protected trees must be minimized to the extent possible.

The critical root zone of trees designated to be protected must be surrounded by a high visibility fence 4 feet in height, supplied and

SECTION 01 14 00.00 13 Page 3 erected by the Contractor. The critical root zone must be defined by an area extending 1.5 feet radius from each tree for each inch of Diameter at Breast Height (DBH). The fence must be securely erected and installed prior to any movement through the project site by construction vehicles or equipment, and remain in place until construction and clean-up are completed. The critical root zone must remain free of all construction activities including trenching, staging, stockpiling and storage of materials. Vehicles and equipment must not drive or park within the critical root zone. Variation to the critical root zone size or configuration will only be permitted where it is absolutely necessary for construction of the project, and requires approval of the Contracting Officer. Short duration alterations of the critical root zone involving wood chips and limited equipment travel must be submitted in writing for approval.

The Contractor must not operate equipment in vegetated areas outside the work limits.

3.2.1 Restoration of Damaged Trees

Any existing tree designated to be protected that is damaged by the Contractor's operations must be replaced. Trees will be considered damaged if the critical root zone in cohesive soils is compacted, if there are significant wounds that could contribute to rot, or if distress (evident by reduced growth or other observations of distress documented by a forester) is observed prior to closing the contract. Trees must be replaced in kind on a caliper inch per caliper inch basis (DBH) (e.g. one 6-inch red oak must be replaced with two 3-inch red oaks, three 2-inch red oaks, or six 1-inch red oaks). Replacement tree size and location will be determined and staked by the Contracting Officer. Repair by pruning, aeration, soil conditioning, or other recommendation from a qualified forester will be considered by the Contracting Officer for substitution for replacement.

3.3 DEFINED NON-NAVIGATION SEASON

The Lock and Dam No. 2 will be closed to navigation generally from early December to early March, weather dependent. The Non-navigation window during the winter of 2024/2025 are as follows:

Closes on 9 December 2024; Opens on 14 March 2025

Construction will not start prior to 9 December 2024 however the staging area will be available for pre-construction activities.

3.4 CONTRACTOR PROPOSED DISPOSAL AREAS

Any disposal sites proposed by the Contractor that are not already identified by the Government as approved for this project are subject to approval by the Contracting Officer. This approval process may require the Government to prepare an environmental assessment at no cost to the Contractor. This may require additional review time and may result in additional requirements to offset environmental effects associated with the use of the site. Proposed sites which involve the excavation or placement of material within a cultural site, wetland, wooded area, floodplain, or other environmentally sensitive area will not be approved.

SECTION 01 14 00.00 13 Page 4

3.5 PRE AND FINAL DIVING INSPECTIONS

The Contractor must perform a diving inspection of the river bottom at and around the nose pier and adjacent monolith of the upper guide wall prior to the start of any work on removing the portions of the upper guide wall. This inspection must verify and record the nose pier and adjacent monolith conditions, river bottom conditions, and to search for any obstructions that may delay or impact construction of the project features. The obstructions include but are not limited to concrete, riprap, pieces of reinforcement, timber debris, and miscellaneous sheet piling.

The Contractor must perform a final diving inspection of the nose pier, adjacent monolith, and river bottom out as far as 20 feet from the wall.

The purpose of the final inspection is to enable visual verification of the conditions of the new nose pier concrete placement, the guide wall/ nose pier transition, and to serve as a baseline for future inspections.

The pre and final diving inspections must consist of, but are not limited to a high definition video recording (720p or better) and acoustic imaging.

The videos must be of a quality that will allow the Government to readily assess site conditions at the time the videos are obtained. Videos where factors such as lighting, focus, and clarity do not allow for the Government to clearly evaluate site conditions must be reshot at no additional cost to the Government. Configure the high definition video to include on-screen titles such as time and date, and narration between the diver and surface observer.

3.6 NAVIGATION NOTICE

The main lock will be open to full width and length navigation, except as indicated in the Defined Non-Navigation Season paragraph above. Should the contractor fail to complete all work in accordance with clause 52.211-10, the contractor shall, at its expense, implement a Navigation Plan that outlines the means and methods for providing navigation assistance. Once the Contractor's plan is approved, the Government will provide public notice of the construction and any approved restrictions.

Changes or substitute measures to the plan must be submitted 7 days prior to actual implementation and be approved by the Contracting Officer.

3.7 NAVIGATION PLAN

Establish and maintain a plan to ensure the safety of industry and recreational traffic in the construction area. This plan must include actions as required to protect the public and prevent damage to the incomplete construction. The Contractor must be responsible for coordinating with the Coast Guard and other regulatory agencies to implement any necessary restrictions. The Contractor must also develop and implement a plan to provide public notice of any construction and any necessary restrictions and closures as well as the availability of the helper boat for assistance to tows passing through the lock.

3.7.1 Navigation Assistance

Provide a helper boat to assist navigation within one-half mile upstream of Lock and Dam No.2. The helper boat must be alongside tows entering and exiting the lock and when passing construction areas and must offer any other assistance to navigation as necessary. The purpose of this assistance is to:

a) Protect life of working personnel.

b) Protect incomplete construction works from potential damage due to barge strikes.

SECTION 01 14 00.00 13 Page 5

c) Protect navigation interests from damage and delays associated with ongoing construction.

d) Assist passage through the area where modified approach conditions impact the ability of vessels to safely transit the construction area and approach to the lock.

3.7.1.1 Minimum Helper Boat Requirements

Provide a helper boat and crew, including at least one deckhand, for navigation assistance. The helper boat must be a twin screw push boat with a minimum of 1,000 horsepower. Assistance must be provided in coordination with the tow boat operator to ensure proper assistance is being provided.

3.7.1.2 Helper Boat Availability

In accordance with Paragraph 3.6 above, the helper boat must be available 24 hours per day, 7 days per week, including holidays. Helper boat assistance must continue until all work is complete and accepted by the Government. For the purposes of this requirement, the Contractor is advised that areas upstream and immediately adjacent to the existing guidewall are used for vessel approach. Therefore, any feature or obstruction in this area is considered to present a hazard to navigation and requires the availability of a helper boat. Vessels may elect not to use the helper boat; however, the service must be present to assist if needed.

3.7.1.3 Government Vessels

Government Vessels may also be required to transit the lock and construction area at any time during the navigation season. The Contractor is required to provide a helper boat to the site to assist Government Vessels. Vessels under contract to the Government are considered Government Vessels.

3.8 FLOATING PLANT

3.8.1 Equipment and Personnel

Floating plant and personnel must comply with the applicable U.S. Coast Guard regulations and licensing requirements. Floating plant equipment must meet the applicable requirements of 46 CFR Chapter 1 Sub Q .

3.8.2 Navigable Waters

Floating vessels operating on the Mississippi River and its tributaries must be operated in accordance with Title 33 Chapter II Part 207, 207.300 "Ohio River, Mississippi River above Cairo, Ill., and their tributaries;

use, administration, and navigation."

3.8.3 Sewage and Bilge Water Disposal

The Contractor's methods for disposal of sanitary sewage, and bilge water accumulated aboard floating plant, must meet applicable local, State, and Federal requirements.

SECTION 01 14 00.00 13 Page 6

3.9 WILDLIFE

3.9.1 Northern Long-eared Bat Exclusion Periods

Do not clear trees between April 15 and October 31. No clearing of live or dead trees greater than 3-inches in diameter within 150 feet of known occupied maternity roost trees. The Contracting Officer will provide notification of known occupied roost trees.

3.9.2 Eagles

No work activities or storage of equipment or materials is allowed within 50 ft of any the three eagle nest trees currently present on the island.

Bald eagle nests are located in the attachment. Travel on the access road is permitted but should be minimized to the greatest extent practicable. A daily log must be kept of eagle presence or absence, and general behavior if present. This log of eagle activity should be submitted weekly throughout project implementation.

This project will require a General Permit for Incidental Disturbance Take of an eagle nest. The Fish and Wildlife Service (FWS) reserves the right to conduct periodic on-site inspections of all permit recipients.

3.9.2.1 Avoidance and Minimization

Activities that affect the survivability of the nest tree or other natural nesting substrate. The nest location must be identified on plans and communicated to contractors or other third parties doing work site.

Preserve the root integrity of the nest tree by avoiding heavy equipment operation, soil compaction, or ground disturbance greater than 12 inches deep within the nest tree's dripline or 50 feet, whichever is greater.

3.9.2.2 Other Conditions

(1) Comply with all of the regulations and permit conditions in 50 CFR parts 10, 13, 21, and 22.

(2) Keep records of all activities conducted under this permit, including any subpermittee activities carried out under the authority of this permit (see 50 CFR § 13.46).

3.10 ATTACHMENTS

Bald Eagle Nests and Tree Buffers

-- End of Section --

SECTION 01 14 00.00 13 Page 7

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 SUBMITTALS

1.2 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.1.1 Scheduling Expectations Kickoff Meeting(SEKO)

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Procurement Activities

3.3.4 Mandatory Activities

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Area of Work Coding (AREA)

3.3.6.4 Modification Number (MODF)

3.3.6.5 Bid Item Coding (BIDI)

3.3.6.6 Phase of Work Coding (PHAS)

3.3.6.7 Category of Work Coding (CATW)

3.3.6.8 Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.7.3 Interim Completion Dates and Constraints

3.3.7.3.1 Start Phase

3.3.7.3.2 End Phase

3.3.8 Adverse Weather

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

3.3.13 Added and Deleted Activities

SECTION 01 32 01.00 10 Page 1

3.3.14 Original Durations

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remaining Duration

3.3.19 Cost Loading of Closeout Activities

3.3.19.1 As-Built Drawings

3.3.19.2 O & M Manuals

3.3.20 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Initial Project Schedule Submission

3.4.2 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Electronic Scheduling Data

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Scheduling and Leveling Report

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Grouping and Sorting

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Changes That Do Not Cause Delay

3.8.3 Time Impact Analysis (Prospective Analysis)

3.8.4 Forensic Schedule Analysis (Retrospective Analysis)

3.8.5 Fragmentary Network (Fragnet)

3.8.6 Time Extension

3.8.7 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RESIDENT MANAGEMENT SYSTEM

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 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

Initial Project Schedule ; G

Periodic Schedule Update ; G

1.2 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 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 Primavera P6.

2.1.2.1 Primavera

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

SECTION 01 32 01.00 10 Page 3 than that used by the Government.

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.

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

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

SECTION 01 32 01.00 10 Page 4

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 as-built drawings.

e. Contractor's pre-final inspection.

f . Government's pre-final inspection.

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

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

SECTION 01 32 01.00 10 Page 5

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.

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

SECTION 01 32 01.00 10 Page 6

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.

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

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

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.

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

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

SECTION 01 32 01.00 10 Page 9

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 original duration.

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.

SECTION 01 32 01.00 10 Page 10

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

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 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 30 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.

The approved Initial Project Schedule will be used for payment purposes.

Completely cost load the Initial Project Schedule to balance the contract award CLINS shown on the Price Schedule. It must be early start and late finish constrained and logically tied as specified. The Initial Project Schedule specified herein must include all 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. Government acceptance of 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 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

SECTION 01 32 01.00 10 Page 11

Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the 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 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).

SECTION 01 32 01.00 10 Page 12

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

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

SECTION 01 32 01.00 10 Page 13

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

SECTION 01 32 01.00 10 Page 14 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. Contractor to prepare and submit minutes of this meeting within 3 calendar days to the Government.

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 occurring . Also prepare a time impact analysis for each Government request for proposal (RFP).

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)

Prepare a time impact analysis for approval by…