W91EF18R0020_Amend_0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to incorporate the changes outlined below . The proposal submission date has been extended from 11 April 2018 to 25 April 2018 not later than 4:00 pm local time.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 3

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 04-Apr-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912EF18R0005

X 9B. DATED (SEE ITEM 11)

09-Mar-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

04-Apr-2018

CODE

USAED, WALLA WALLA - CONTRACTING DIV.

HILLARY A. MORGAN

201 N. THIRD AVENUE

WALLA WALLA WA 99362

W912EF 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912EF18R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

Summary of changes for Amend – 0002

Lower Snake River XJO Breaker Replacement

W912EF18R0005

SPECIFICATIONS

a. SECTION 01 11 01.00 28 “GENERAL REQUIREMENTS”

Revised the following paragraphs:

1.22, “WEEKLY PRODUCTION MEETINGS”

See revised specification for details.

1.24, “RED ZONE MEETING”

b. SECTION 01 32 01.00 28 “PROJECT SCHEDULE”

Revised the following paragraph:

3.6.1, “Periodic Schedule Update Meetings”

c. SECTION 01 45 04.00 28 “CONTRACTOR QUALITY CONTROL”

Revised the following paragraph:

3.2.2, “Content of the CQC Plan”

SECTION 00 10 00 - SOLICITATION

The required response date/time has changed from 11-Apr-2018 04:00 PM to 25-Apr-2018 04:00 PM.

(End of Summary of Changes)

Lower Snake River XJO Breaker Replacement W912EF18R0005 Amend-0002

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 01.00 28

SUPPLEMENTARY REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 FIELD VERIFICATION OF SITE CONDITIONS

1.4 DEFINITIONS

1.5 REGULAR CLEANUP AND DEBRIS DISPOSAL

1.6 GOVERNMENT ISSUED ITEMS

1.7 EQUIPMENT LIST

1.8 TESTING OF EQUIPMENT

1.9 DISPOSITION OF REMOVED EQUIPMENT

1.10 PROTECTION AND RESTORATION OF EXISTING FACILITIES

1.11 PRE-WORK AND POST WORK SURVEYS

1.12 CONTRACTOR RESPONSIBILITY FOR CONTRACT WORK

1.13 CARE OF DRAINS

1.14 PROTECTION OF POWERHOUSE FLOORS

1.15 FIRE CONTROL

1.16 TRAINING

1.17 PROJECT OPERATORS' TRAINING

1.18 PROJECT TECHNICAL SUPPORT

1.19 PROJECT SUPERINTENDENT

1.20 KEY PERSONNEL SUBSTITUTION

1.21 POST AWARD MEETINGS

1.21.1 Pre-Work Meeting

1.21.2 Pre-Construction Meeting

1.21.2.1 Minutes

1.21.2.2 Demobilizing And Remobilizing

1.22 WEEKLY PRODUCTION MEETINGS

1.22.1 Minutes

1.23 ADDITIONAL MEETINGS

1.24 RED ZONE MEETING

1.25 USE OF CRANES

1.25.1 Crane Operators

1.25.2 Use of the Cranes

1.25.3 Riggers

1.25.4 Lifting Devices

PART 2 PRODUCTS (Not Used)

PART 3 EXECUTION (Not Used)

ATTACHMENTS:

Weekly Meeting Agenda Template

SECTION 01 11 01.00 28 - Page 1 g4edddca Line g4edddca Line

-- End of Section Table of Contents --

SECTION 01 11 01.00 28 - Page 2

SECTION 01 11 01.00 28

SUPPLEMENTARY REQUIREMENTS

PART 1 GENERAL

The work covered by this section of the specifications consists of work common to more than one section of these TECHNICAL SPECIFICATIONS.

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 Safety and Health Requirements Manual

Comply with the current edition and all changes posted on the web as of the effective date of this solicitation.

1.2 SUBMITTALS

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

submittals having an "I" designation are for information only. Designation following the "G" or "I" designation identifies the office that will review the submittal for the Government. Submit in accordance with SECTION

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Equipment List; I C

HLD Pre-Work Survey Photos And Report; I C

LMA Pre-Work Survey Photos and Report; I C

LGA Pre-Work Survey Photos and Report; I C

LLA Pre-Work Survey Photos and Report; I C

Project Superintendent; I C qualifications; I C

SD-07 Certificates

Key Personnel Substitution; G C

SD-11 Closeout Submittals

HLD Post-Work Survey Photos and Report; I C

LMA Post-Work Survey Photos and Report; I C

SECTION 01 11 01.00 28 - Page 3

LGA Post-Work Survey Photos and Report; I C

LLA Post-Work Survey Photos and Report; I C

HLD Training Manuals; G C

LMA Training Manuals; G C

LGA Training Manuals; G C

LLA Training Manuals; G C

Government Issued Items; G C

1.3 FIELD VERIFICATION OF SITE CONDITIONS

Field verify all elevations, dimensions, and coordinates of existing features indicated on the contract drawings that affect new construction.

Any deviations shall be updated as per SECTION 01 78 00.00 28, CLOSEOUT SUBMITTALS, paragraph MAINTAIN WORKING AS-BUILT CONTRACT DRAWINGS AND FIO

DRAWINGS.

1.4 DEFINITIONS

a. Qualified Person.

As defined in EM 385-1-1; "DEFINITIONS", unless otherwise specified.

b. F.O.B.

An abbreviation for free on board, which means that a vendor or consignor will deliver goods on a railroad car, truck, vessel, or other conveyance without any expense to the purchaser or consignee.

1.5 REGULAR CLEANUP AND DEBRIS DISPOSAL

With the exception of materials specifically indicated or specified to be salvaged for reuse in construction, or turned over to the Government, all wastes and demolished materials shall become the property of the Contractor and shall be removed from the job site daily in accordance with Federal, State, and local regulations. The Contractor shall furnish waste containers. All small waste containers provided by the contractor shall be emptied daily, large bin containers shall be emptied when full or once a week.

1.6 GOVERNMENT ISSUED ITEMS

Return to the Government all items issued to the Contractor from the Government, including but not limited to the following: keys, ID and security badges, radios, pagers, and excess/unused Government Furnished Property/Equipment. Submit documentation signed by the Contractor and Contracting Officer indicating items have been returned or fully accounted for. Format of submittal will be discussed and agreed upon at the Pre-Work Meeting.

SECTION 01 11 01.00 28 - Page 4

1.7 EQUIPMENT LIST

Furnish a complete list of all equipment to be used on each of the Projects 30 days prior to commencement of on-site work. Seperate equipment on the list by dam. Submit a revised list in the event of change of equipment.

Lists shall include rented equipment as well as lease-purchase or sale-leaseback equipment. The initial list and the revised lists shall indicate dates equipment is assigned to or removed from the Projects and adequate identification or description of each item of equipment including manufacturer's name (abbreviated), model number, manufacturer's serial number, year of manufacture, and Contractor's assigned serial or record number.

1.8 TESTING OF EQUIPMENT

Before any machinery or mechanized equipment is put to use on the job, it shall be inspected and tested by a qualified person and determined to be in safe operating condition. Cranes or derricks shall be tested by the Contractor or a qualified testing agency in accordance with EM 385-1-1.

Equipment shall be large enough to safely handle proposed picks or tasks without exceeding the crane rating established by these tests.

1.9 DISPOSITION OF REMOVED EQUIPMENT

Unless otherwise specified in other sections of the specifications, all existing equipment removed and not reinstalled shall become the property of the Contractor, removed from the Project site, and disposed of in a legal manner. Materials that cannot be removed daily may be temporarily stored on-site at an approved area. Salvaged materials shall not be sold on the project site.

1.10 PROTECTION AND RESTORATION OF EXISTING FACILITIES

Reference FAR 52.236-9 Protection of Existing Structures, Equipment, Utilities, and Improvements (Apr 1984).

1.11 PRE-WORK AND POST WORK SURVEYS

Conduct a HLD pre-work survey, LMA pre-work survey, LGA pre-work survey,and LLA pre-work survey prior to start of on-site work and a HLD post-work survey, LMA post-work survey, LGA post-work survey, and a LLA post-work survey during project cloesout, with the Contracting Officer Representative, of the Government facilities at the work areas. The results of the surveys shall be documented by digital photographs and descriptive narrative reports. A color copy of the survey photographs and narrative reports shall be submitted to the Contracting Officer within five

(5) days after surveys have been completed.

1.12 CONTRACTOR RESPONSIBILITY FOR CONTRACT WORK

The Contractor is responsible for correcting all damage and defects to work covered by this contract, until final acceptance by the Government.

1.13 CARE OF DRAINS

Existing Powerhouse floor drains shall not be used for disposal of any solid material or any liquids other than clear water. Demonstrate that the pipes and drains are unobstructed when so directed.

SECTION 01 11 01.00 28 - Page 5

1.14 PROTECTION OF POWERHOUSE FLOORS

Care shall be taken to prevent damage to floors (tile and non-tile) and curbs within the Powerhouse. Damage to floors or curbs caused by Contractor's operation shall be repaired at no additional cost to Government. Repairs shall match surrounding area in color, texture, and surface finish and are subject to approval.

1.15 FIRE CONTROL

Each piece of internal combustion engine driven equipment used at the work site shall be equipped with a fire extinguisher in accordance with recommendation National Fire Protection Association (NFPA) as appropriate.

The minimum approved rating of extinguishers shall not be less than 5-B:C.

1.16 TRAINING

Provide the services of authorized start-up engineers (Manufacturer's Representatives) as necessary to provide training in programming, operation and maintenance on all equipment. Provide training for operators and maintenance personnel prior to project operation of the breakers. Provide two, eight-hour class sessions; one class for operators and maintenance personnel and one for system managers and engineers. A total of eight training sessions will be required, two at each dam. The Government will provide for the training location at each dam. Each class session shall include approximately 10 employees. Training will be tailored to match the systems and equipment of the respective dam where the training is held.

Submit HLD training manuals, LMA training manuals, LGA training manuals, LLA training manuals and documentation for approval 30 days prior to scheduled classes and shall furnish sufficient training materials at the training classes for all students plus a minimum of three (3) copies for project files. Where audio/visual materials are used in training classes, three (3) copies of such materials shall be furnished to the Project for use in future training. It shall be the Contractor's responsibility to coordinate the training sessions with the Projects to ensure minimum conflicts with ongoing Project work.

Demonstrations shall be on the actual Circuit Breaker and equipment furnished. To the maximum extent possible, provide course materials with site-specific operation and maintenance data. Any important maintenance information that would be unique to a specific project should be included in that project's training session. The Government may videotape the training sessions for future use. Minimally, the training shall cover:

a. Circuit breaker design and theory of operation

b. Construction of the actual circuit breakers furnished

c. Routine maintenance, trouble analysis, and safety precautions

d. Major overhaul procedures

e. Emphasis on emergency procedures

1.17 PROJECT OPERATORS' TRAINING

Provide the services of one or more authorized individuals for Project Operators' training. Contractor personnel shall be experienced in the operational requirements of all newly installed breakers, and control

SECTION 01 11 01.00 28 - Page 6 features. Contractor personnel shall be present at the project and available for assistance for three (3) ten hour work shifts at each dam immediately following Government acceptance of newly installed features.

Required work shifts shall be coordinated with the Contracting Officer.

1.18 PROJECT TECHNICAL SUPPORT

a. In addition to those requirements for the above paragraph, PROJECT OPERATORS' TRAINING, provide 20 hours of on site project technical support after Government acceptance of the completed project. One or more Contractor personnel experienced in the operational requirements of all newly installed equipment, and control features shall be available for Technical Support during normal Government Work Schedule hours. See paragraph "Government's Work Schedule" in SECTION 01 14 00.10 28.

b. Support shall include site visits by Contractor personnel. Contractor personnel shall be available at the project within 48 hours following notification by the Contracting Officer's Representative. Technical support shall be available for 60 days following Government acceptance of the newly installed breakers, or until final Operation and Maintenance Manuals and Parts Catalogs have been approved and received by the Government - whichever is later. See SECTIONS 01 78 00.00 28 CLOSEOUT

SUBMITTALS.

1.19 PROJECT SUPERINTENDENT

At all times during performance of this contract and until the work is completed and accepted, assign and have on the worksite, a competent superintendent as per FAR Clause 52.236-6 "Superintendence by the Contractor". If the Contractor has personnel working at more than one site, a superintendent shall be provided for each location. Submit Superintendent name and contact information prior to start of on-site construction.

1.20 KEY PERSONNEL SUBSTITUTION

If the Contractor plans on replacing any Key personnel (Project Superintendent, CQC System Manager, they must have the approval of the Contracting Officer. Personnel shall possess the qualifications that meet or exceed those stated in this contract for the position of the individual they are replacing. Submit qualifications of new personnel at least 15 calendar days in advance of date of replacement.

1.21 POST AWARD MEETINGS

1.21.1 Pre-Work Meeting

Within 30 calendar days after receipt of Notice to Proceed, attend a Pre-Work Meeting. Senior Level members of the Contractor's staff involved with this contract shall participate in this meeting to discuss the overall contract requirements. The Government will lead this meeting and take the meeting minutes.

1.21.2 Pre-Construction Meeting

The Project Superintendent shall coordinate with the Contracting Officer and establish the date of the Pre-Construction Meeting. The meeting will be held at each Project site at least one (1) week prior to mobilizing to each job site. The Project Superintendent shall lead the Pre-Construction

SECTION 01 11 01.00 28 - Page 7

Meeting discussing the Contractor's plan on executing the work at the project site, schedule, required clearances and timeframe for them, and plan for implementing safety and quality control. The Government will have key members from the Project staff to discuss environmental and clearance issues. Key members of the contractor staff shall attend this meeting including the Quality Control (QC) System Manager, Site Safety and Health Officer (SSHO) and any other members determined by the Government to be required.

1.21.2.1 Minutes

The Project Superintendent shall be responsible for taking the meeting minutes and shall send them electronically within 48 hours of the meeting to the Government's Project Engineer, Quality Assurance Representative, and Resident Engineer.

1.21.2.2 Demobilizing And Remobilizing

Anytime the Contractor demobilizes from the site and remobilizes at a later date, another Pre-Construction Meeting shall be held and shall follow the requirements listed above.

1.22 WEEKLY PRODUCTION MEETINGS

During all onsite construction work the Project Superintendent shall lead a weekly production meeting using the attached "Weekly Meeting Agenda Template " to brief the Government on the status of the project. All elements listed in the agenda shall be thoroughly discussed. These activities shall align to the overall construction schedule submitted under SECTION 01 32 01.00 28 PROJECT SCHEDULE, the construction schedule shall be updated to include these changes by the next scheduled update. Key members of the Contractor's staff shall attend this meeting, including the Quality Control System Manager, who is responsible for discussing QC aspects of the work as outlined under SECTION 01 45 04.00 28 CONTRACTOR QUALITY CONTROL and SSHO.

The Government reserves the right to require any person from the Contractor's staff, such as the Project ManagerSuperintendent, Engineer, scheduler, etc., or key subcontractor personnel to attend this meeting, if Government feels their participation is required.

1.22.1 Minutes

The Project Superintendent shall be responsible for taking the meeting minutes and shall send them electronically within 24 hours of the meeting to the Government's Project Engineer, Quality Assurance Representative, and Resident Engineer.

1.23 ADDITIONAL MEETINGS

Record the minutes of all meetings, including all conference calls, that occur between the Contractor and Government. Send minutes electronically within 24 hours of the meeting to the Contracting Officer for concurrence.

E-mail subject line shall include project name and meeting topic.

1.24 RED ZONE MEETING

When the project is 80 percent completed at each dam, the Contractor’s Superintendent shall set up and lead a Red Zone meeting. The Contractor’s Superintendent shall contact the Contracting Officer to Schedule this meeting. The Government’s representative will include the Contracting

SECTION 01 11 01.00 28 - Page 8

Officer, key personnel from the Project, Project Engineer, Quality Assurance Representative, and Resident Engineer. The key people from the Contractor shall be, at a minimum, the Project Superintendent, Quality Control System Manager, Scheduler, and key subcontractors personnel, and Project Manager.

The purpose of this meeting is to develop an overall schedule for all activities required by both the Government and Contractor and to complete the project. The Government will come prepared with all their activities, key dates, and durations for all work required by the Government to complete the project. Provide the same information for all of their activities. The Contractor’s scheduler shall input all of this information into the Contractor’s project schedule during the meeting.

This schedule shall be updated weekly, or as needed, based on the information from the weekly production meetings for both the Government and Contractor activities.

1.25 USE OF CRANES

1.25.1 Crane Operators

Furnish qualified crane operators for all lifting operations. Each operator, in addition to meeting the requirements of EM 385-1-1, shall have had at least 1-year experience on a crane of equivalent capacity and characteristics. Submit qualifications for each operator in the form of an affidavit signed by the operator and the Contractor. The affidavit shall include a complete record of all related work with particular emphasis on experience directly related to operation of a similar crane handling with comparable loads. Before any operator is approved, they shall spend at least one (1) hour in being checked out on the cranes under the direct surveillance of a Government operator. Ensure that the crane operators have current (within the previous 12 months) physical or medical examinations with emphasis on hearing, eyesight, and cardiovascular conditions. Dates of physical exams shall be submitted to the Contracting Officer.

1.25.2 Use of the Cranes

The Contractor will be liable for all damage, due to fault or negligence, incurred while the cranes are operated by the Contractor's crane operators.

1.25.3 Riggers

Only qualified riggers shall be used in preparing loads for lifting and in attaching such loads to the cranes. See SECTION 01 35 29.10 28 SAFETY AND OCCUPATIONAL HEALTH REQUIREMENTS paragraph "Riggers" for additional information.

1.25.4 Lifting Devices

The Contractor is responsible for furnishing all other rigging, lifting devices, and containers for use with the cranes. Any special lifting devices required for handling new equipment furnished by the Contractor shall be turned over to the Government upon completion of the contract.

Standard slings and shackles are not considered "special" lifting devices.

SECTION 01 11 01.00 28 - Page 9

PART 2 PRODUCTS (Not Used)

PART 3 EXECUTION (Not Used)

-- End of Section --

SECTION 01 11 01.00 28 - Page 10

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 28

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 Main Unit Outages

3.3.6 Government Activities

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers Per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (AREA)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase of Work Coding (PHAS)

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

3.3.8.3.1 Start Phase

3.3.8.3.2 End Phase

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

SECTION 01 32 01.00 28 - Page 1

3.3.13 Added and Deleted Activities

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.20 Anticipated Adverse Weather

3.3.21 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 Gantt Chart

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

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

ATTACHMENTS:

Current outage schedules

-- End of Section Table of Contents --

SECTION 01 32 01.00 28 - Page 2

SECTION 01 32 01.00 28

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 having an "I" designation are for information only. Designation following the "G" or "I" designation identifies the office that will review the submittal for the Government. Submit in accordance with SECTION

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G, ECC

Preliminary Project Schedule; G, ECC

Initial Project Schedule; G, ECC

Periodic Schedule Update; G, ECC

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

SECTION 01 32 01.00 28 - Page 3

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

SECTION 01 32 01.00 28 - Page 4

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.

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.

Limit durations of all non-procurement activities to 10 workdays or 15 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. Mandatory tasks are required for each dam independant of the othes.

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

b. Submission, review and acceptance of features that require design completion.

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

SECTION 01 32 01.00 28 - Page 5

d. Material Procurements.

e. Long procurement activities.

f. All Definable Features of Work.

g. Completion dates, constraints, and limited work windows as described in Clause 52.211-10 COMMENCEMENT, PROSECUTION, AND COMPLETION OF WORK (APR 1984).

h. Submission and approval of O & M manuals.

i. Submission and approval of as-built drawings.

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

k. Submission and approval of fire protection specialist.

l. Submission and approval of Commissioning Plan, test data, and reports:

Develop the schedule logic associated with testing and commissioning to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

m. Controls testing plan submission.

n. Controls testing.

o. Performance Verification testing.

p. Other systems testing, if required.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

u. Final inspection.

v. Dates and duration of all unit outage periods for each dam.

3.3.5 Main Unit Outages

Make every effort to match the Contractors desired main unit outages with that of each dam's current outage schedule. Current outage schedules are attached at the end of this section for each dam. These dates are subject to change. Outage requests matching existing outages remain subject to disapproval at the Governments discretion.

3.3.6 Government Activities

Show 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

SECTION 01 32 01.00 28 - Page 6 phasing requirements.

3.3.7 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS 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.7.1 Workers Per Day (WRKP)

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

3.3.7.2 Responsible Party Coding (RESP)

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

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

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

SECTION 01 32 01.00 28 - Page 7

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

3.3.7.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or 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.7.4 Modification Number (MODF)

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

3.3.7.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item 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.7.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 construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

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

3.3.7.7 Category of Work Coding (CATW)

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

3.3.7.8 Feature of Work Coding (FOW)

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

SECTION 01 32 01.00 28 - Page 8

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

3.3.8 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

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

3.3.8.1 Project Start Date Milestone and Constraint

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

3.3.8.2 End Project Finish Milestone and Constraint

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

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.8.3 Interim Completion Dates and Constraints

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

3.3.8.3.1 Start Phase

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

3.3.8.3.2 End Phase

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

3.3.9 Calendars

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

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

SECTION 01 32 01.00 28 - Page 9

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 days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. 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.10 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.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 float, or to replace proper schedule logic. Lags are limited to 5 workdays.

SECTION 01 32 01.00 28 - Page 10

a. Leads (negative lags) are prohibited.

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

3.3.16 Retained Logic

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

3.3.17 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.3.18 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 entitled Percent Complete.

3.3.19 Cost Loading of Closeout Activities

Cost load closeout activities in accordance with the retainage of payment for final submittals as specified in Section 01 22 00.00 28 "MEASUREMENT

AND PAYMENT."

3.3.20 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.21 Early Completion Schedule and the Right to Finish Early

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

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

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

SECTION 01 32 01.00 28 - Page 11

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

Provide the hardcopy Preliminary Project Schedule, defining the Contractor's planned operations, at a summary level, at the Pre-work meeting. Provide an electronic PDF version to the COR the day prior to the Pre-work meeting to allow time for distribution. The Preliminary Project Schedule shall include NTP, major design activities, major preconstruction submittals (to include APP, EPP, and CQC), mobilization, construction/installation, testing/commissioning, demobilization.

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS.

These updates will enable the Government to assess Contractor's progress.

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

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

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the 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. Contractor shall e-mail a copy to the Contracting Officer's Representative.

SECTION 01 32 01.00 28 - Page 12

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.