Specifications SOO09 - RTA - 03-26-21.pdf

Certified Final Documents – RTA

Specifications for

CHIPPEWA COUNTY

SAULT STE. MARIE, Ml

POE LOCK

REHABILITATION

SHIP ARRESTORS

DEPARTMENT OF THE ARMY

DETROIT DISTRICT, CORPS OF ENGINEERS

DETROIT, MICHIGAN

March 2021

This page was intentionally left blank for duplex printing.

Poe Lock Rehabilitation Ship Arrestors SOO09

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 22 00.00 10 PRICE AND PAYMENT PROCEDURES

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 13 SPECIAL PROJECT PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 78 24.00 10 FACILITY DATA REQUIREMENTS

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 11 19.00 06 INSULATING CONCRETE FORM (ICF) SYSTEM

03 22 70.01 CONTROLLED LOW-STRENGTH MATERIAL (CLSM)

03 30 00 CAST-IN-PLACE CONCRETE

03 45 33 PRECAST STRUCTURAL CONCRETE

DIVISION 04 - MASONRY

04 72 00.00 48 CAST STONE

DIVISION 05 - METALS

05 12 00 STRUCTURAL STEEL

05 30 00 STEEL DECKS

05 50 14 STRUCTURAL METAL FABRICATIONS

05 50 15 CIVIL WORKS FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 22 00 ROOF AND DECK INSULATION

07 54 19 POLYVINYL-CHLORIDE ROOFING

07 60 00 FLASHING AND SHEET METAL

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 71 00 DOOR HARDWARE

08 91 00 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 90 00 PAINTS AND COATINGS

09 97 02 PAINTING: HYDRAULIC STRUCTURES

09 97 13.27 EXTERIOR COATING OF STEEL STRUCTURES

DIVISION 22 - PLUMBING

PROJECT TABLE OF CONTENTS Page 1

22 00 00 PLUMBING, GENERAL PURPOSE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

23 82 00.00 20 TERMINAL HEATING UNITS

DIVISION 26 - ELECTRICAL

26 05 73.13 08 ARC FLASH HAZARD ANALYSIS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 01 41.00 10 ELECTROMECHANICAL OPERATING MACHINERY FOR LOCKS AND DAMS

35 01 70.13 WIRE ROPE FOR SHIP ARRESTORS

35 05 40.14 10 HYDRAULIC POWER SYSTEMS FOR CIVIL WORKS STRUCTURES

DIVISION 40 - PROCESS INTERCONNECTIONS

40 95 00 PROCESS CONTROL

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

SECTION 00 01 20

GENERAL CONTRACT ADMINISTRATION

PART 1 GENERAL

1.1 PARTNERING (FEB 2000)

1.2 CONTRACTOR SUPPLY AND USE OF ELECTRONIC SOFTWARE FOR PROCESSING

WAGE RATE REQUIREMENTS STATUTE CERTIFIED LABOR PAYROLLS (APR 2011)

1.3 BASIS FOR SETTLEMENT OF PROPOSALS

1.4 EQUIPMENT OWNERSHIP AND OPERATING EXPENSE SCHEDULE

-- End of Section Table of Contents --

DOCUMENT 00 01 20 Page 1

SECTION 00 01 20

GENERAL CONTRACT ADMINISTRATION

PART 1 GENERAL

1.1 PARTNERING (FEB 2000)

In order to most effectively accomplish this contract, the Government proposes to form a partnership with the Contractor to develop a cohesive building team. It is anticipated that this partnership would involve the Contractor, primary subcontractors and designers, and the Corps of Engineers. This partnership would strive to develop a cooperative management team drawing on the strengths of each team member in an effort to achieve a quality project within budget and on schedule. This partnership would be bilateral in membership and participation will be completely voluntary. Any cost associated with effectuating this partnership, excluding travel and lodging cost of Government personnel, will be borne by each party. The partnering meetings shall be held at agreed upon dates/times of all involved parties.

1.2 CONTRACTOR SUPPLY AND USE OF ELECTRONIC SOFTWARE FOR PROCESSING WAGE

RATE REQUIREMENTS STATUTE CERTIFIED LABOR PAYROLLS (APR 2011)

(a) The Contractor is encouraged to use a commercially-available electronic system to process and submit certified payrolls electronically to the Government. The requirements for preparing, processing and providing certified labor payrolls are established by the Wage Rate Requirements statute.

(b) If the Contractor elects to use an electronic payroll processing system, then the Contractor shall be responsible for obtaining and providing for all access, licenses, and other services required to provide for receipt, processing, certifying, electronically transmitting to the Government, and storing weekly payrolls and other data required for the Contractor to comply with the Wage Rate Requirements statute. When the Contractor uses an electronic payroll system, the electronic payroll service shall be used by the Contractor to prepare, process, and maintain the relevant payrolls and basic records during all work under this construction contract and the electronic payroll service shall be capable of preserving these payrolls and related basic records for the required 3 years after contract completion. If the Contractor chooses to use an electronic payroll system, then the Contractor shall obtain and provide electronic system access to the Government, as required to comply with the Wage Rate Requirements over the duration of this construction contract. The access shall include electronic review access by the Government contract administration office to the electronic payroll processing system used by the contractor.

(c) The Contractor's provision and use of an electronic payroll processing system shall meet the following basic functional criteria:

(1) commercially available;

(2) compliant with appropriate Wage Rate Requirements statute payroll provisions in the Federal Acquisition Regulation (FAR);

(3) able to accommodate the required numbers of employees and subcontractors planned to be employed under the contract;

(4) capable of producing an Excel spreadsheet-compatible electronic output of weekly payroll records for export in an Excel spreadsheet to be imported

DOCUMENT 00 01 20 Page 2 into the Contractor's Quality Control System (QCS) version of Resident Management System (RMS), that in turn shall export payroll data to the Government's RMS;

(5) demonstrated security of data and data entry rights;

(6) ability to produce Contractor-certified electronic versions of weekly payroll data

(7) ability to identify erroneous entries and track the date/time of all versions of the certified Wage Rate Requirements statute payrolls submitted to the Government over the life of the contract;

(8) capable of generating a durable record copy, that is, a CD or DVD and PDF file record of data from the system database at end of the contract closeout. This durable record copy of data from the electronic payroll processing system shall be provided to the Government during contract closeout.

(d) All Contractor-incurred costs related to the Contractor's provision and use of an electronic payroll processing service shall be included in the Contractor's price for the overall work under the contract. The costs for compliance with the Wage Rate Requirements statute by using electronic payroll processing services shall not be a separately bid or reimbursed item under this contract.

1.3 BASIS FOR SETTLEMENT OF PROPOSALS

Actual costs will be used to determine equipment costs for a settlement proposal submitted on the total cost basis under Federal Acquisition Regulation (FAR) 49.206-2(b). In evaluating a termination settlement proposal using the total cost basis, the following principles will be applied to determine allowable equipment costs:

(a) Actual costs for each piece of equipment, or groups of similar serial or series equipment, need not be available in the contractor's accounting records to determine total actual equipment costs.

(b) If equipment costs have been allocated to a contract using predetermined rates, those charges will be adjusted to actual costs.

(c) Recorded job costs adjusted for unallowable expenses will be used to determine equipment operating expenses.

(d) Ownership costs (depreciation) will be determined using the Contractor's depreciation schedule (subject to the provisions of Federal Acquisition Regulation (FAR) 31.205-11).

(e) License, taxes, storage and insurance costs are normally recovered as an indirect expense and unless the Contractor charges these costs directly to contracts, they will be recovered through the indirect expense rate.

1.4 EQUIPMENT OWNERSHIP AND OPERATING EXPENSE SCHEDULE

(a) This clause does not apply to terminations. Federal Acquisition Regulation (FAR) part 49.

(b) Allowable costs for construction and marine plant and equipment in sound workable condition owned or controlled and furnished by a contractor or subcontractor at any tier shall be based on actual cost data for each piece of equipment or groups of similar serial and series for which the Government can determine both ownership and operating costs from the Contractor's accounting records. When both ownership and operating costs

DOCUMENT 00 01 20 Page 3 cannot be determined for any piece of equipment or groups of similar serial or series equipment from the Contractor's accounting records, costs for that equipment shall be based upon the applicable provisions of Engineer Pamphlet (EP) 1110-1-8, Construction Equipment Ownership and Operating Expense Schedule, Region 4. Working conditions shall be considered to be average for determining equipment rates using the schedule unless specified otherwise by the Contracting Officer. For equipment not included in the schedule, rates for comparable pieces of equipment may be used or a rate may be developed using the formula provided in the schedule. For forward pricing, the schedule in effect at the time of negotiations shall apply.

For retroactive pricing, the schedule in effect at the time the work was performed shall apply.

(c) Equipment rental costs are allowable, subject to the provisions of FAR 31.105(d)(ii) and FAR 31.205-36. Rates for equipment rented from an organization under common control, lease-purchase arrangements, and sale-leaseback arrangements, will be determined using the schedule, except that actual rates will be used for equipment leased from an organization under common control that has an established practice of leasing the same or similar equipment to unaffiliated lessees.

(d) When actual equipment costs are proposed and the total amount of the pricing action exceeds the simplified acquisition threshold (SAT), the Contracting Officer shall request the Contractor to submit either certified cost or pricing data, or partial/limited data, as appropriate. The data shall be submitted on Standard Form 1411, Contract Pricing Proposal Cover Sheet.

-- End of Section --

DOCUMENT 00 01 20 Page 4

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 22 00.00 10

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 SINGLE JOB PAYMENT ITEMS

1.2 BIDDING SCHEDULE

1.2.1 Fabricate D/S Spiral Drum Arrestors, Bid Item 0001

1.2.1.1 Payment

1.2.1.2 Unit of Measure

1.2.2 Rehabilitation of D/S Ship Arrestor, Bid Item 0002

1.2.2.1 Payment

1.2.2.2 Unit of Measure

1.2.3 Option 1 - Fabricate U/S Spiral Drum Arrestors, Bid Item 0003

1.2.3.1 Payment

1.2.3.2 Unit of Measure

1.2.4 Option 2 - Rehabilitate U/S Ship Arrestor, Bid Item 0004

1.2.4.1 Payment

1.2.4.2 Unit of Measure

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 22 00.00 10 Page 1

SECTION 01 22 00.00 10

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 SINGLE JOB PAYMENT ITEMS

Payment items for the work of this contract for which contract job payments will be made are listed in the BIDDING SCHEDULE and described below. All costs for items of work, which are not specifically mentioned to be included in a particular job or unit price payment item, are included in the listed job item most closely associated with the work involved. The job price and payment made for each item listed constitutes full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, and for performing all work required for which separate payment is not otherwise provided.

1.2 BIDDING SCHEDULE

1.2.1 Fabricate D/S Spiral Drum Arrestors, Bid Item 0001

1.2.1.1 Payment

Payment will be made for costs associated with fabricating the downstream spiral drum arrestors, to include filter cart, portable hydraulic power unit, shop testing and shipment to the site.

1.2.1.2 Unit of Measure

Unit of measure: job.

1.2.2 Rehabilitation of D/S Ship Arrestor, Bid Item 0002

1.2.2.1 Payment

Payment will be made for costs associated with demolition and rehabilitation of the Downstream Ship Arrestor. Payment will include, but not be limited to, installing the spiral drum arrestors (including field testing) and rehabilitating and installing spare fender boom; furnishing and installing wire rope, buildings, ship detection system, boom and socket cylinders for both the upstream and downstream ship arrestor, miscellaneous electrical work and automated grease system, payment also includes costs for mobilization and demobilization. Also, payment will include removing and disposing of existing rolling segment building and existing equipment (cross-heads, cross-head guides, brake cylinders, hydraulic reservoir, including hydraulic oil, reservoir supporting structure and hydraulic piping within the cylinder pit, bollards), and filling Boom 12 and 13 recesses as shown, and providing a concrete cap. In addition, payment will include rehabilitation of the counterweight, clean and paint the quadrants. Payment will include furnishing and installing new pins and bushing. Payment will also include modifications to the existing hydraulic system. In addition, payment shall include new gratings and covers.

SECTION 01 22 00.00 10 Page 2

1.2.2.2 Unit of Measure

Unit of measure: Job.

1.2.3 Option 1 - Fabricate U/S Spiral Drum Arrestors, Bid Item 0003

1.2.3.1 Payment

Payment will be made for costs associated with fabricating the upstream spiral drum arrestors, to include testing and shipment to the site.

1.2.3.2 Unit of Measure

Unit of measure: job.

1.2.4 Option 2 - Rehabilitate U/S Ship Arrestor, Bid Item 0004

1.2.4.1 Payment

Payment will be made for costs associated with demolition and rehabilitation of the U/S Ship Arrestor. Payment will include, but not be limited to, installing the spiral drum arrestors (including field testing) and rehabilitating and installing spare fender boom; furnishing and installing wire rope, buildings, ship detection system, miscellaneous electrical work and automated grease system, payment also includes costs for mobilization and demobilization. Also, payment will include removing and disposing of existing rolling segment building and existing equipment (cross-heads, cross-head guides, brake cylinders, hydraulic reservoir, including hydraulic oil, reservoir supporting structure and hydraulic piping within the cylinder pit, bollards), and filling Boom 11 recesses as shown and providing a concrete cap. In addition, payment will include rehabilitation of the counterweight, clean and paint quadrants. Payment will also include furnishing and installing new pins and bushing. In addition, payment shall include new gratings and covers.

1.2.4.2 Unit of Measure

Unit of measure: Job.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 22 00.00 10 Page 3

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 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

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

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 Tasks

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 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

3.3.12 Added and Deleted Activities

SECTION 01 32 01.00 10 Page 1

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

3.3.15 Retained Logic

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Cost Loading of Closeout Activities

3.3.18.1 As-Built Drawings

3.3.18.2 O & M Manuals

3.3.19 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD/DVDs

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

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 Banding

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 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 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

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

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. 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

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 authorized representative must have a minimum of two-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. 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

SECTION 01 32 01.00 10 Page 3 specification.

2.1.1 Government Default Software

The Government intends to use Primavera P6.

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.

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.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

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.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

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

SECTION 01 32 01.00 10 Page 4

3.2.2 Withholdings / Payment Rejection

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

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

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate 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. Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

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

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

a. Fabricate and Install Ship Arrestor Ship Date - for Arrestors Standard Administrative tasks CPT Ryan/Isaac to provide.

b. Activities that MUST be done in a non-navigation season should be included as a mandatory task and identified as such on the schedule

c. Activities that require Government support (Locking out a boom or any other lockout, movement of lock booms or gates, shutting down navigation, etc.)

d. Operational Testing

SECTION 01 32 01.00 10 Page 5

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: 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. A template SDEF compatible schedule backup file is available on the RMS web site:

http://rms.usace.army.mil.

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

SECTION 01 32 01.00 10 Page 6

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.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

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

SECTION 01 32 01.00 10 Page 7

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.00 10 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 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. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

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 Calendars

Schedule activities on a Calendar to which the activity logically belongs.

SECTION 01 32 01.00 10 Page 8

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 an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in Section 01 35 13 SPECIAL PROJECT PROCEDURES. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

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

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

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

SECTION 01 32 01.00 10 Page 9

3.3.14 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 float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

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

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

3.3.17 Remaining Duration

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

3.3.18 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.18.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.18.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.19 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that

SECTION 01 32 01.00 10 Page 10 indicates all scope of the required contract work will be completed before the contractually required completion date.

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

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, 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, then 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 logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. 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.

SECTION 01 32 01.00 10 Page 11

Provide a draft Periodic Schedule Update for review monthly. For winter work that involves opening a lock by a specified date, provide a draft Periodic Schedule Update every two weeks. 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 is subject to the approval of the Government.

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 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis. Include the following information as minimum in the Narrative Report:

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

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

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.

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 at monthly pay estimate review meetings. 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 Schedule Log

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 Banding

Organize activities using the WBS or as otherwise 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 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 four work days after the periodic schedule update meeting.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) 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 four 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

Provide a 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) to justify time extensions.

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

SECTION 01 32 01.00 10 Page 14 schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard 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.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03.

3.8.4 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 project schedule.

3.8.5 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 will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.8.6 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 excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval.