FY14_Mac_Lock_Modernizatin_Amendment_0001_Specs_8-8-14.pdf

FY14 Mac Lock Modernization - Amendment 0001 FY14MCLMPC1

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 22 00.00 10 MEASUREMENT AND PAYMENT

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 13.10 SPECIAL PROJECT PROCEDURES

01 35 29 SAFETY AND OCCUPATIONAL HEALTH REQUIREMENTS

01 38 00 CONSTRUCTION PHOTOGRAPHS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.10 10 QUALITY CONTROL SYSTEM (QCS)

01 45 04.00 10 CONTRACTOR QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 20.00 20 ENVIRONMENTAL PROTECTION

01 58 01 PROJECT SIGN AND SAFETY SIGN

01 62 35 RECYCLED / RECOVERED MATERIALS

01 78 00.00 40 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 42 91 REMOVAL AND SALVAGE OF HISTORIC BUILDING MATERIALS

02 81 00 TRANSPORTATION AND DISPOSAL OF HAZARDOUS MATERIALS

02 82 14.00 10 ASBESTOS HAZARD CONTROL ACTIVITIES

02 82 33.13 20 REMOVAL/CONTROL AND DISPOSAL OF PAINT WITH LEAD

02 84 33 REMOVAL AND DISPOSAL OF POLYCHLORINATED BIPHENYLS (PCBs)

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 00.00 40 COMMON WORK RESULTS FOR ELECTRICAL

26 05 13.00 40 MEDIUM-VOLTAGE CABLES

26 05 19.00 10 INSULATED WIRE AND CABLE

26 05 71.00 40 LOW VOLTAGE OVERCURRENT PROTECTIVE DEVICES

26 12 16.30 SUBSTATION TRANSFORMERS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 16.00 40 PANELBOARDS

26 24 19.00 40 MOTOR CONTROL CENTERS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 01.00 10 ELECTRIC MOTORS, 3-PHASE VERTICAL INDUCTION TYPE

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 13 23.00 40 COMMUNICATIONS OPTICAL BACKBONE CABLING

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 23 23.00 10 CLOSED CIRCUIT TELEVISION SYSTEMS

DIVISION 40 - PROCESS INTEGRATION

40 95 00 PROCESS CONTROL

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

PROJECT TABLE OF CONTENTS Page 2

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

SUMMARY OF WORK

01/08

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

1.1.2 Location

1.2 OCCUPANCY OF PREMISES

1.3 EXISTING WORK

1.4 SALVAGE MATERIAL AND EQUIPMENT

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

01/08

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes MacArthur Lock Electrical Modernization Power and Controls and incidental related work.

1.1.2 Location

The work shall be at various locations at the Soo Locks Complex, Sault St.

Marie, Michigan. The exact locations shall be shown on the drawings.

1.2 OCCUPANCY OF PREMISES

The project area will be partially operational to the extent described per Section 01 35 13 10 SPECIAL PROJECT PROCEDURES. Contractor shall provide all necessary controls to protect pedestrians and government employees.

Before work is started, the Contractor shall arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment.

1.3 EXISTING WORK

In addition to "FAR 52.236-9, Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements":

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

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

1.4 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged shall remain the property of the Government.

The salvaged property shall be segregated, itemized, delivered, and off-loaded at the Government designated storage area.

Contractor shall maintain property control records for material or equipment designated as salvage. Contractor's system of property control may be used if approved by the Contracting Officer. Contractor shall be responsible for storage and protection of salvaged materials and equipment until disposition by the Contracting Officer. The following items shall be salvaged intact specifically but not limited to: Consoles in 1 North

SECTION 01 11 00 Page 2 manhole & in 2 North manhole.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 3

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 22 00.00 10

MEASUREMENT AND PAYMENT

04/06

PART 1 GENERAL

1.1 SUBMITTALS

1.2 JOB PAYMENT ITEMS

1.2.1 MacArthur Lock Electric and Controls (Bid Item 0001), Rockwell

Equipment (Bid Item 0002), Schweitzer Equipment (Bid Item 0003), All other equipmemt and installation of all equipment (Bid Item 0004).

1.2.1.1 Payment

1.2.1.2 Unit of Measure

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 22 00.00 10 Page 1

SECTION 01 22 00.00 10

MEASUREMENT AND PAYMENT

04/06

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Schedule of Prices; G, AOF

1.2 JOB PAYMENT ITEMS

Payment items for the work of this contract for which contract job payments will be made for items listed in the BIDDING SCHEDULE and described below.

Contractor shall submit Schedule of Prices for job payment items within 14 calendar days of issuance of the Notice to Proceed. All costs for items of work, which are not specifically mentioned to be included in a particular job payment item, shall be included in the listed job item most closely associated with the work involved. The job price and payment made for each item listed shall constitute 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.1 MacArthur Lock Electric and Controls (Bid Item 0001), Rockwell Equipment (Bid Item 0002), Schweitzer Equipment (Bid Item 0003), All other equipmemt and installation of all equipment (Bid Item 0004).

1.2.1.1 Payment

Payment will be made for the entire work complete in accordance with the drawings and specifications (Division 00-28) associated with Base - MacArthur Lock Electric and Controls Modernization work.

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

SECTION 01 22 00.00 10 Page 3

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

05/14

PART 1 GENERAL

1.1 1.2 SUBMITTALS

1.2 QUALITY ASSURANCE

PART 2 PRODUCTS

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.1.1 Approved Project Schedule

3.1.2 Schedule Status Reports

3.1.3 Default Terms

3.2 BASIS FOR PAYMENT AND COST LOADING

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Procurement Activities

3.3.2.3 Mandatory Tasks

3.3.2.4 Government Activities

3.3.2.5 Activity Responsibility Coding (RESP)

3.3.2.6 Activity Work Area Coding

3.3.2.7 Contract Changes/Requests for Equitable Adjustment (REA)

Coding (MODF)

3.3.2.8 Contract Line Item (CLIN) Coding (BIDI)

3.3.2.9 Phase of Work Coding (PHAS)

3.3.2.10 Category of Work Coding (CATW)

3.3.2.11 Definable Features of Work Coding (FOW1, FOW2, FOW3)

3.3.3 Scheduled Project Completion and Activity Calendars

3.3.3.1 Project Start Date

3.3.3.2 Schedule Constraints and Open Ended Logic

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Start Phase

3.3.4.2 End Phase

3.3.4.3 Phase "X" Hammock

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Negative Lags and Start to Finish Relationships

3.3.8 Calculation Mode

3.3.9 Milestones

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Initial Project Schedule Submission

3.4.2 Monthly Schedule Updates

SECTION 01 32 01.00 10 Page 1

3.4.3 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD's

3.5.2 Narrative Report

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report by CLIN

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 MONTHLY SCHEDULE UPDATE

3.6.1 Status of Activities

3.6.1.1 Start and Finish Dates

3.6.1.2 Remaining Duration

3.6.1.3 Percent Complete

3.6.1.4 Logic Changes

3.6.1.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 WEEKLY PROGRESS MEETINGS

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

05/14

PART 1 GENERAL

1.1 1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Schedule; G, AOF

1.2 QUALITY ASSURANCE

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects and have previously maintained at least two (2) electronic schedules for similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS

Not used

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. Subcontractors and suppliers working on the project shall 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.

3.1.1 Approved Project Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

SECTION 01 32 01.00 10 Page 3

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 BASIS FOR PAYMENT AND COST LOADING

Use the schedule as the basis for determining contract earnings during each update period and therefore the amount of each progress payment. Lack of an approved schedule update, or qualified scheduling personnel, will result in the inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification. Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule.

3.3.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following

SECTION 01 32 01.00 10 Page 4 characteristics and requirements to determine appropriate level of detail:

3.3.2.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Most activities shall have Original Durations (OD) between two (2) and six (6) working days with the exception of procurement activities.

3.3.2.2 Procurement Activities

The schedule must include activities associated with the submittal, approval, 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. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.3 Mandatory Tasks

The following tasks must be included and properly scheduled:

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

b. Submission and approval of O & M manuals.

c. Submission and approval of as-built drawings.

d. Controls testing plan submission.

e. Controls testing.

f. Performance Verification testing (include this item for each major piece of equipment before it's put into service and accepted by Government.).

g. Process control commissioning.

h. Other systems testing, if required.

i. Contractor's pre-final inspection.

j. Correction of punchlist from Contractor's pre-final inspection.

k. Government's pre-final inspection.

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

m. Final inspection.

3.3.2.4 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 phasing requirements.

SECTION 01 32 01.00 10 Page 5

3.3.2.5 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor or Government agency responsible for performing the activity. Activities coded with a Government Responsibility code include, but are not limited to:

Government approvals, environmental permit approvals by State regulators, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Code all activities not coded with a Government Responsibility Code to the Prime Contractor or Subcontractor responsible to perform the work. Activities shall not have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); KTR for the prime contractor; and GOVT (for USACE).

3.3.2.6 Activity Work Area Coding

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 shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

3.3.2.7 Contract Changes/Requests for Equitable Adjustment (REA) Coding

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the Contracting Officer, with a Contract Changes/REA Code. Key all Code values to the Government's modification numbering system. Any activity or sequence of activities added to the schedule as a result of alleged constructive changes made by the Government may be added to a copy of the current schedule, subject to the approval of the Contracting Officer. Assign Activity codes for these activities with a Contract Changes/REA Code. Key the code values to the Contractor's numbering system. Approval to add these activities does not necessarily mean the Government accepts responsibility and, therefore, liability for such activities and any associated impacts to the schedule, but rather the Government recognizes such activities are appropriately added to the schedule for the purposes of maintaining a realistic and meaningful schedule. Such activities shall not be Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

3.3.2.8 Contract Line Item (CLIN) Coding (BIDI)

Code all activities to the CLIN on the Contract Line Item Schedule to which the activity belongs. An activity shall not contain more than one CLIN Item Code. CLIN Item code all activities, even when an activity is not cost loaded.

3.3.2.9 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase

SECTION 01 32 01.00 10 Page 6

Code to allow filtering and organizing the schedule accordingly. Each activity shall be identified with a single project phase and have only one Phase of Work code.

3.3.2.10 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the urgency of work (1 = critical, 2 = near critical or 3 = non-critical) to which the activity belongs. Each activity shall have only one Category of Work Code.

3.3.2.11 Definable Features of Work Coding (FOW1, FOW2, FOW3)

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. Definable Feature of Work is defined in Specification Section 01 45 00.00 10 QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is received by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a 7 day calendar when the contract assigns calendar day durations for the activity such as a Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive Installation to those activities that are weather sensitive.

Original durations must account for anticipated normal adverse weather.

The Government will interpret all work periods not identified as non-work periods on each calendar as meaning the Contractor intends to perform work during those periods.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. Include as the first activity in the project schedule an activity called "Start Project" (or NTP). The "Start Project" activity shall have an "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

3.3.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the contract completion date for the project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial

SECTION 01 32 01.00 10 Page 7 float constraints such as "zero fee float" or "zero total float" are typically prohibited. There shall only be 2 open ended activities: Start Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start Phase X" where "X" refers to the phase of work. The "Start Phase X" activity shall have an "ES" constraint date equal to the date on which the NTP was acknowledged, and a zero day duration.

3.3.4.2 End Phase

Include as the last activity for a project phase an activity called "End Phase X" where "X" refers to the phase of work. The "End Phase X" activity shall have an "LF" constraint date equal to the specified completion date for that phase and a zero day duration.

3.3.4.3 Phase "X" Hammock

Include a hammock type activity for each project phase called "Phase X" where "X" refers to the phase of work. The "Phase X" hammock activity shall be logically tied to the earliest and latest activities in the phase.

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the AS and AF dates on the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

SECTION 01 32 01.00 10 Page 8

Updating of the percent complete and the remaining duration of any activity shall be independent functions. Disable program features which calculate one of these parameters from the other.

3.3.6 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 all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

Lag durations contained in the project schedule shall not have a negative value. Do not use Start to Finish (SF) relationships.

3.3.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. 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") will not be allowed.

3.3.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: delivery date of MCC and each time a gate or valve is taken out of service.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD, reports, and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS.

3.4.1 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 25 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer. Include permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Also cover in the preliminary design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities concurrent with the monthly schedule updating process. Constrain construction activities by Government acceptance of associated designs. When the design is complete, incorporate into the then approved schedule update all

SECTION 01 32 01.00 10 Page 9 remaining detailed construction activities that are planned to occur after the dry-in milestone.

3.4.2 Monthly Schedule Updates

Submit monthly schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgment of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.4.3 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used. A template SDEF compatible schedule backup file (sdef.prx) is available on the QCS website:

http://rms.usace.army.mil/. The SDEF format is as follows:

SDEF Format Field Activity Length Description Code 1 WRKP 3 Workers per Day 2 RESP 4 Responsible Party (e.g. Designer of Record, Prime Contractor, and

USACE)

3 AREA 4 Area of Work (May be left blank) 4 MODF 6 Modification or REA number (May be left blank if not applicable) 5 BIDI 6 Bid Item (CLIN) 6 PHAS 2 Phase of Work (Pre-Construction, Construction or Post-Construction) (Note: Procurement activities shall be coded as Pre-Construction) 7 CATW 1 Category of Work (Critical, Near Critical, Not Critical) 8 FOW1 10 Feature of Work (used up to 10 characters in length) 9 FOW2 10 Feature of Work (used up to 20 characters in length) 10 FOW3 10 Feature of Work (used up to 30 characters in length)

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Initial Schedule and every Monthly Schedule Update throughout the life of the project:

3.5.1 Data CD's

Provide two sets of data CD's containing the project schedule in the backup format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of schedule (Initial, Update, full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the Contractor.

SECTION 01 32 01.00 10 Page 10

3.5.2 Narrative Report

Provide a Narrative Report with the Initial and each Monthly Update of the project schedule, as the basis of the progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, 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. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Contracting Officer. The Narrative Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall 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. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission. The reports may be submitted in hard copy or electronic copy on a CD as directed by the contracting officer.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

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

3.5.4.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.4.4 Earnings Report by CLIN

A compilation of the Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by

SECTION 01 32 01.00 10 Page 11 activity number. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram is required for the Initial submission and may be require with the Monthly Updates if requested by the Contracting Officer.

The network diagram shall 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.5.1 Continuous Flow

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

3.5.5.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.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

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

3.5.5.5 S-Curves

Earnings curves showing projected early and late earnings and earnings to date.

3.6 MONTHLY SCHEDULE UPDATE

Provide monthly schedule updates for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government with the updated schedule.

3.6.1 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete shall be subject to the approval of the Government prior to the meeting. As a minimum, address the following items on an activity by activity basis during each progress

SECTION 01 32 01.00 10 Page 12 meeting.

3.6.1.1 Start and Finish Dates

Accurately show the status of the AS and/or AF dates for each activity currently in-progress or completed since the last update. The Government may allow an AF date to be assigned with the percent complete less than 100% to account for the value of work remaining but not restraining successor activities. Only assign AS dates when actual progress occurs on an activity.

3.6.1.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.1.3 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, cost load the correction of punchlist from Government pre-final inspection activity(ies) not less than 1 percent of the total contract value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s).

3.6.1.4 Logic Changes

Specifically identify and discuss all logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, Contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, and other changes that have been made pursuant to contract provisions. The Government will only approve logic revisions for the purpose of keeping the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and accurately sequencing the work.

3.6.1.5 Other Changes

Other changes required due to delays in completion of any activity or group of activities include: 1) delays beyond the Contractor's control, such as strikes and unusual weather. 2) delays encountered due to submittals, Government Activities, deliveries or work stoppages which make re-planning the work necessary. 3) Changes required to correct a schedule that does not represent the actual or planned prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor believes it is entitled to an extension of the contract performance period, completion date, or any interim milestone date, furnish the following for a determination by the Contracting Officer:

justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of excusable

SECTION 01 32 01.00 10 Page 13 delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is a condition precedent to any approvals by the Government. In response to each Request For Proposal issued by the Government, submit a schedule impact analysis demonstrating whether or not the change contemplated by the Government impacts the critical path.

3.7.1 Justification of Delay

The project schedule shall clearly display that the Contractor has used, in full, all the float time available for the work involved with this request.

The Contracting Officer's determination as to the number of allowable days of contract extension shall be based upon the project schedule updates in effect for the time period in question, and other factual information.

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.7.2 Submission Requirements

Submit a justification for each request for a change in the contract completion date of less than 2 weeks based upon the most recent schedule update at the time of the NTP or constructive direction issued for the change. Such a request shall be in accordance with the requirements of other appropriate Contract Clauses and shall include, as a minimum:

a. A list of affected activities, with their associated project schedule activity number.

b. A brief explanation of the causes of the change.

c. An analysis of the overall impact of the changes proposed.

d. A sub-network of the affected area.

Identify activities impacted in each justification for change by a unique activity code contained in the required data file.

3.7.3 Additional Submission Requirements

The Contracting Officer may request an interim update with revised activities for any requested time extension of over 2 weeks. Provide this disk within 4 days of the Contracting Officer's request.

3.8 DIRECTED CHANGES

If the NTP is issued for changes prior to settlement of price and/or time, submit proposed schedule revisions to the Contracting Officer within 2 weeks of the NTP being issued. The Contracting Officer will approve proposed revisions to the schedule prior to inclusion of those changes within the project schedule. If the Contractor fails to submit the proposed revisions, the Contracting Officer may furnish the Contractor with suggested revisions to the project schedule. Include these revisions in the project schedule until revisions are submitted, and final changes and impacts have been negotiated. If the Contractor has any objections to the revisions furnished by the Contracting Officer, advise the Contracting Officer within 2 weeks of receipt of the revisions. Regardless of the objections, continue to update the schedule with the Contracting Officer's

SECTION 01 32 01.00 10 Page 14 revisions until a mutual agreement in the revisions is reached. If the Contractor fails to submit alternative revisions within 2 weeks of receipt of the Contracting Officer's proposed revisions, the Contractor will be deemed to have concurred with the Contracting Officer's proposed revisions.

The proposed revisions will then be the basis for an equitable adjustment for performance of the work.

3.9 WEEKLY PROGRESS MEETINGS

a. Meet weekly 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. The then current and approved schedule update shall be used for the purposes of this meeting and for the production and review of reports. The Contractor's Project Manager and the Authorized Representative of the Contracting Officer shall attend. The weekly progress meeting will address the status of RFI's, RFP's and Submittals.

b. Provide a bar chart produced by the scheduling software, organized by Total Float and Sorted by Early Start Date, and a four week "look-ahead" schedule by filtering all schedule activities to show only current ongoing activities and activities schedule to start during the upcoming two weeks, organized by Work Area Code (AREA) and sorted by Early Start Date.

c. The Government and the Contractor shall jointly review the reports. If it appears that activities on the longest path(s) which are currently driving the calculated completion date (driving activities), are not progressing satisfactorily and therefore could jeopardize timely project completion, corrective action must be taken immediately. Corrective action includes but is not limited to: increasing the number of work crews;

increasing the number of work shifts; increasing the number of hours worked per shift; and determining if Government responsibility coded activities require Government corrective action.

3.10 OWNERSHIP OF FLOAT

Float available in the schedule, at any time, shall not be considered for the exclusive use of either the Government or the Contractor.

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Download and upload the schedule data into the Resident Management System (RMS) prior to RMS databases being transferred to the Government. The schedule is considered to be additional supporting data in a form and detail required by the Contracting Officer pursuant to FAR 52.232-5 - Payments under Fixed-Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 - Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and electronic export from QCS of the application for progress payment.

SECTION 01 32 01.00 10 Page 15

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

02/09

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

1.1.2 Approving Authority

1.1.3 Work

1.2 SUBMITTALS

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Government Approved

1.3.2 Information Only

1.4 PREPARATION

1.4.1 Transmittal Form

1.4.2 Identifying Submittals

1.4.3 Format for SD-02 Shop Drawings

1.4.4 Format of SD-03 Product Data and SD-08 Manufacturer's

Instructions

1.4.5 Format of SD-04 Samples

1.4.6 Format of SD-05 Design Data and SD-07 Certificates

1.4.7 Format of SD-06 Test Reports and SD-09 Manufacturer's Field

Reports

1.4.8 Format of SD-10 Operation and Maintenance Data (O&M)

1.4.9 Format of SD-01 Preconstruction Submittals and SD-11 Closeout

Submittals

1.5 QUANTITY OF SUBMITTALS

1.5.1 Number of Copies of SD-02 Shop Drawings

1.5.2 Number of Copies of SD-03 Product Data and SD-08

Manufacturer's Instructions

1.5.3 Number of Samples SD-04 Samples

1.5.4 Number of Copies SD-05 Design Data and SD-07 Certificates

1.5.5 Number of Copies SD-06 Test Reports and SD-09 Manufacturer's

Field Reports

1.5.6 Number of Copies of SD-10 Operation and Maintenance Data

1.5.7 Number of Copies of SD-01 Preconstruction Submittals and SD-11

Closeout Submittals

1.6 INFORMATION ONLY SUBMITTALS

1.7 VARIATIONS / SUBSTITUTION REQUESTS

1.7.1 Considering Variations

1.7.2 Proposing Variations

1.7.3 Warranting That Variations Are Compatible

1.7.4 Review Schedule Is Modified

1.8 SUBMITTAL REGISTER

1.8.1 Use of Submittal Register

1.8.2 Contractor Use of Submittal Register

1.8.3 Approving Authority Use of Submittal Register

1.8.4 Contractor Action Code and Action Code

1.8.5 Copies Delivered to the Government

SECTION 01 33 00 Page 1

1.9 SCHEDULING

1.10 GOVERNMENT APPROVING AUTHORITY

1.10.1 Review Notations

1.11 DISAPPROVED OR REJECTED SUBMITTALS

1.12 APPROVED/ACCEPTED SUBMITTALS

1.13 APPROVED SAMPLES

1.14 WITHHOLDING OF PAYMENT

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 33 00 Page 2

SECTION 01 33 00

SUBMITTAL PROCEDURES

02/09

PART 1 GENERAL

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor's Quality Control (CQC) System Manager and the Designer of Record, if applicable, to check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as: Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited

to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders; samples; O&M manuals (including parts list); certifications;

warranties; and other such required submittals.

Submittals requiring Government approval are to be scheduled and made prior to the acquisition of the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by Submittal Description (SD) numbers and titles as follows:

SD-01 Preconstruction Submittals

Submittals required prior to the start of work:

Certificates of insurance SF 1413 for each subcontractor Project Schedule Submittal register Schedule of prices Health and safety plan Work plan Quality control(QC) plan Environmental protection plan

SD-02 Shop Drawings

SECTION 01 33 00 Page 3

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. (Testing must have been within three years of date of contract award for the project.)

Report which includes findings of a test required to be performed by the Contractor on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily logs and checklists.

Final acceptance test and operational test…