Waianae.pdf

WAIANAE SMALL BOAT HARBOR MAINTENANCE DREDGING, OAHU, HAWAII BCA2

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 29 SAFETY AND OCCUPATIONAL HEALTH REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 01 USACE QUALITY CONTROL SYSTEM (QCS)

01 45 04 CONTRACTOR QUALITY CONTROL

01 57 20 ENVIRONMENTAL PROTECTION

01 74 19 CONSTRUCTION AND DEMOLITION DEBRIS RECYCLING

01 78 02 CLOSEOUT SUBMITTALS

01 90 00 MISCELLANEOUS PROVISIONS

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 20 23 DREDGING

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01

PROJECT SCHEDULE

PART 1 GENERAL

1.1 ELECTRONIC SCHEDULE REQUIREMENT

1.2 SUBMITTALS

1.3 QUALIFICATIONS

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL

3.2 BASIS FOR PAYMENT

3.3 ELECTRONIC PROJECT SCHEDULE

3.3.1 Use of the 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 Government Activities

3.3.2.4 Responsibility

3.3.2.5 Work Areas

3.3.2.6 Modification or Claim Number

3.3.2.7 Bid Item

3.3.2.8 Phase of Work

3.3.2.9 Category of Work

3.3.2.10 Feature of Work

3.3.3 Scheduled Project Completion

3.3.3.1 Project Start Date

3.3.3.2 Constraint of Last Activity

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

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Extended Non-Work Periods

3.3.8 Negative Lags

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.4.4 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data Disks

3.5.1.1 File Medium

SECTION 01 32 01 Page 1

3.5.1.2 Disk Label

3.5.1.3 File Name

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

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.5.5.6 Bar Chart

3.6 PERIODIC PROGRESS MEETINGS

3.6.1 Meeting Attendance

3.6.2 Update Submission Following Progress Meeting

3.6.3 Progress Meeting Contents

3.6.3.1 Start and Finish Dates

3.6.3.2 Time Completion

3.6.3.3 Cost Completion

3.6.3.4 Logic Changes

3.6.3.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 OWNERSHIP OF FLOAT

-- End of Section Table of Contents --

SECTION 01 32 01 Page 2

SECTION 01 32 01

PROJECT SCHEDULE

PART 1 GENERAL

1.1 ELECTRONIC SCHEDULE REQUIREMENT

The Project Schedule to be prepared by the Contractor shall be electronically prepared using software capable of generating a data file in the Standard Data Exchange Format (SDEF). The Project Schedule shall consist of a network analysis system as described in this Section. In preparing this system the scheduling of Construction is the sole responsibility of the Contractor. The requirement for the system is included to assure adequate planning in the execution of the work and to assist the Contracting Officer in appraising the reasonableness of the proposed schedule and evaluating progress of the work for the purposes of payment.

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. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Preliminary Project Schedule; G Initial Project Schedule; G Periodic Schedule Updates

Two copies of the schedules showing codes, values, categories, numbers, items, etc., as required.

Periodic schedule updates schedules shall be submitted together with the monthly progress payment request.

SD-06 Test Reports

Narrative Report Schedule Reports

Two copies of the reports showing numbers, descriptions, dates, float, starts, finishes, durations, sequences, etc., as required.

SD-07 Certificates

Qualifications

Documentation showing qualifications of personnel preparing schedule reports.

SECTION 01 32 01 Page 3

1.3 QUALIFICATIONS

The Contractor shall designate an authorized representative who shall be responsible for the preparation of all required project schedule reports.

This person shall have previously created and reviewed computerized schedules. Qualifications of this individual shall be submitted to the Contracting Officer for review with the Preliminary Project Schedule submission

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL

Pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS, a Project Schedule as described below shall be prepared. The scheduling of construction shall be 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. The approved Project Schedule shall be used to measure the progress of the work, to aid in evaluating time extensions, and to provide the basis of all progress payments.

3.2 BASIS FOR PAYMENT

The schedule shall be the basis for measuring Contractor progress. Lack of an approved schedule or scheduling personnel shall result in an inability of the Contracting Officer to evaluate Contractor progress for the purposes of payment. Failure of the Contractor to provide all information, as specified below, shall result in the disapproval of the entire Project Schedule submission and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes. In the case where Project Schedule revisions have been directed by the Contracting Officer and those revisions have not been included in the Project Schedule, then the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until revisions to the Project Schedule have been made.

3.3 ELECTRONIC PROJECT SCHEDULE

The computer software system utilized by the Contractor to produce the Project Schedule shall be capable of providing all requirements of this specification. Failure of the Contractor to meet the requirements of this specification shall result in the disapproval of the schedule. Manually generated schedules will not be accepted.

The system noted below is capable of generating a file in the Standard Data Exchange Format (SDEF). All electronic data submittals shall be in SDEF.

SDEF information is available from the Contracting Officer.

Vendor/System with SDEF support:

Primavera Systems PRIMAVERA PROJECT PLANNER (P3)

3.3.1 Use of the Critical Path Method

The Critical Path Method (CPM) of network calculation shall be used to

SECTION 01 32 01 Page 4 generate the Project Schedule. The Contractor shall provide the Project Schedule in the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

With the exception of the preliminary schedule submission, the Project Schedule shall include an appropriate level of detail. Failure to develop or update the Project Schedule or provide data to the Contracting Officer at the appropriate level of detail, as specified by the Contracting Officer, shall result in the disapproval of the schedule. The Contracting Officer will use, but is not limited to, the following conditions to determine the appropriate level of detail to be used in the Project Schedule.

3.3.2.1 Activity Durations

Contractor submissions shall follow the direction of the Contracting Officer regarding reasonable activity durations. Reasonable durations are those that allow the progress of activities to be accurately determined between payment periods (usually less than 2 percent of all non-procurement activities' Original Durations shall be greater than 20 days).

3.3.2.2 Procurement Activities

Tasks related to the procurement of long lead materials or equipment shall be included as separate activities in the project schedule. Long lead materials and equipment are those materials that have a procurement cycle of over 90 days. Examples of procurement process activities include, but are not limited to: submittals, approvals, procurement, fabrication, delivery, installation, start-up, and testing.

3.3.2.3 Government Activities

Government and other agency activities that could impact progress shall be shown. These activities include, but are not limited to: approvals, inspections, utility tie-in, Government Furnished Equipment (GFE) and notice to proceed for phasing requirements.

3.3.2.4 Responsibility

All activities shall be identified in the project schedule by the party responsible to perform the work. Responsibility includes, but is not limited to, the subcontracting firm, Contractor work force, or government agency performing a given task. Activities shall not belong to more than one responsible party. The responsible party for each activity shall be identified by the Responsibility Code.

3.3.2.5 Work Areas

All activities shall be identified in the project schedule by the work area in which the activity occurs. Activities shall not be allowed to cover more than one work area. The work area of each activity shall be identified by the Work Area Code.

3.3.2.6 Modification or Claim Number

Any activity that is added or changed by contract modification or used to justify claimed time shall be identified by a mod or claim code that changed the activity. Activities shall not belong to more than one

SECTION 01 32 01 Page 5 modification or claim item. The modification or claim number of each activity shall be identified by the Mod or Claim Number. Whenever possible, changes shall be added to the schedule by adding new activities.

Existing activities shall not normally be changed to reflect modifications.

3.3.2.7 Bid Item

All activities shall be identified in the project schedule by the Contract Line Item (CLIN) to which the activity belongs. An activity shall not contain work in more than one bid item. The CLIN for each appropriate activity shall be identified by the Bid Item Code.

3.3.2.8 Phase of Work

All activities shall be identified in the project schedule by the phases of work in which the activity occurs. Activities shall not contain work in more than one phase of work. The project phase of each activity shall be by the unique Phase of Work Code.

3.3.2.9 Category of Work

All Activities shall be identified in the project schedule according to the category of work which best describes the activity. Category of work refers, but is not limited, to the procurement chain of activities including such items as submittals, permits, submittals, approvals, procurement, fabrication, delivery, installation, start-up, and testing.

The category of work for each activity shall be identified by the Category of Work Code.

3.3.2.10 Feature of Work

All activities shall be identified in the project schedule according to the feature of work to which the activity belongs. Feature of work refers, but is not limited to a work breakdown structure for the project. The feature of work for each activity shall be identified by the Feature of Work Code.

3.3.3 Scheduled Project Completion

The schedule interval shall extend from notice-to-proceed to the contract completion date.

3.3.3.1 Project Start Date

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

3.3.3.2 Constraint of Last Activity

Completion of the last activity in the schedule shall be constrained by the contract completion date. Calculation on project updates shall be such that if the early finish of the last activity falls after the contract completion date, then the float calculation shall reflect a negative float on the critical path. The Contractor shall include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have: a "LF" constraint, a constraint date equal to the completion date for the project, and a zero day duration.

SECTION 01 32 01 Page 6

3.3.3.3 Early Project Completion

In the event the Preliminary or Intial project schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall 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

Contractually specified interim completion dates shall also be constrained to show negative float if the early finish date of the last activity in that phase falls after the interim completion date.

3.3.4.1 Start Phase

The Contractor shall 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

The Contractor shall include as the last activity in 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 completion date for the project, and a zero day duration.

3.3.4.3 Phase X

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

3.3.5 Default Progress Data Disallowed

Actual Start and Finish dates shall not be automatically updated by default mechanisms that may be included in CPM scheduling software systems. Actual Start and Finish dates on the CPM schedule shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the Actual Start and Finish dates on the Daily Quality Control report for every in-progress or completed activity and 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 schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes. Updating of the percent complete and the remaining duration of any activity shall be independent functions.

Program features which calculate one of these parameters from the other shall be disabled.

SECTION 01 32 01 Page 7

3.3.6 Out-of-Sequence Progress

Activities that have posted progress without predecessors being completed (Out-of-Sequence Progress) will be allowed only on a case-by-case acceptance of the Contracting Officer. The Contractor shall 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. The Contracting Officer may direct that changes in schedule logic be made to correct any or all out-of-sequence work.

3.3.7 Extended Non-Work Periods

Designation of Holidays to account for non-work periods of over 5 days will not be allowed. Non-work periods of over 5 days shall be identified by addition of activities that represent the delays. Modifications to the logic of the project schedule shall be made to link those activities that may have been impacted by the delays to the newly added delay activities.

3.3.8 Negative Lags

Lag durations contained in the project schedule shall not have a negative value.

3.4 PROJECT SCHEDULE SUBMISSIONS

The Contractor shall provide the submissions as described below. The data disk, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

The Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days shall be submitted for approval within 20 calendar days after Notice to Proceed is acknowledged. The approved preliminary schedule shall be used for payment purposes not to exceed 90 calendar days after Notice to Proceed.

3.4.2 Initial Project Schedule Submission

The Initial Project Schedule shall be submitted for approval within 60 calendar days after Notice to Proceed. The schedule shall provide a reasonable sequence of activities which represent work through the entire project and shall be at a reasonable level of detail.

3.4.3 Periodic Schedule Updates

Based on the result of progress meetings, specified in "Periodic Progress Meetings," the Contractor shall submit periodic schedule updates. These submissions shall enable the Contracting Officer or 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.4 Standard Activity Coding Dictionary

The Contractor shall use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact

SECTION 01 32 01 Page 8 structure is mandatory, even if some fields are not used. Once accepted with the Initial Project Schedule submission, changes to the activity coding scheme must be accepted by the Contracting Officer.

3.5 SUBMISSION REQUIREMENTS

The following items shall be submitted by the Contractor for the initial submission, and every periodic project schedule update throughout the life of the project:

3.5.1 Data Disks

Two sets of data disks containing the project schedule shall be provided.

Data on the disks shall be in the Standard Data Exchange Format (SDEF), in accordance with ER-1-1-11, PROGRESS, SCHEDULES, AND NETWORK ANALYSIS SYSTEMS, Appendix A, Standard Data Exchange Format Specification (attached at the end of this Project Schedule specification.

3.5.1.1 File Medium

Required data shall be submitted on compact disc, read-only memory (CD-ROM), under the MS-Windows operating system.

3.5.1.2 Disk Label

A permanent exterior label shall be affixed to each disk submitted. The label shall indicate the type of schedule (Initial, Update, or Change), full contract number, project name, project location, data date, name and telephone number of person responsible for the schedule, and the version of the software used to generate the schedule.

3.5.1.3 File Name

Each file submitted shall have a name related to either the schedule data date, project name, or contract number. The Contractor shall develop a naming convention that will ensure that the names of the files submitted are unique. The Contractor shall submit the file naming convention to the Contracting Officer for approval.

3.5.2 Narrative Report

A Narrative Report shall be provided with each update of the project schedule. This report shall be provided as the basis of the Contractor's progress payment request. The Narrative Report shall include: a description of activities along the critical path(s), a description of current and anticipated problem areas or delaying factors and their impact, and an explanation of corrective actions taken. The narrative report is expected to relay 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.

3.5.3 Approved Changes Verification

Only project schedule changes that have been previously approved by the Contracting Officer shall be included in the schedule submission. 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.

SECTION 01 32 01 Page 9

3.5.4 Schedule Reports

The format for each activity for the schedule reports listed below 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 and Actual Finish Dates shall be printed for those activities in progress or completed.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number and then sorted according to Early Start Date. For completed activities the Actual Start Date shall be used as the secondary sort.

3.5.4.2 Logic Report

A list of Preceding and Succeeding activities for every activity in ascending order by activity number. Preceding and succeeding activities shall include all information listed above in paragraph Schedule Reports.

A blank line shall be left between each activity grouping.

3.5.4.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. Activities that have the same amount of total float shall be listed in ascending order of Early Start Dates. Completed activities shall not be shown on this report.

3.5.4.4 Earnings Report

A compilation of the Contractor's Total Earnings on the project from the Notice to Proceed until the most recent Monthly Progress Meeting. This report shall reflect the Earnings of specific activities based on the agreements made in the field and approved between the Contractor and Contracting Officer at the most recent Monthly Progress Meeting. Provided that the Contractor has provided a complete schedule update, this report shall serve as the basis of determining Contractor Payment. Activities shall be grouped by bid item and sorted by activity numbers. This report shall: sum all activities in a bid item and provide a bid item percent;

and complete and sum all bid items to provide a total project percent complete. The printed report shall contain, for each activity: Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), Earnings to Date.

3.5.5 Network Diagram

The network diagram shall be required on the initial schedule submission, on monthly schedule update submissions, whenever any logic changes have occurred. 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 activity or event number, description, duration, and estimated earned value shall be shown on the diagram. 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. The activity or event number, description, duration, SECTION 01 32 01 Page 10 and estimated earned value shall be shown on the diagram.

3.5.5.2 Project Milestone Dates

Dates shall be shown on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.5.5.3 Critical Path

The critical path shall be clearly shown.

3.5.5.4 Banding

Activities shall be grouped 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

A graph of anticipated earnings (S-Curves) showing cumulative earnings for the duration of the project. The vertical scale shall show earnings/ percent complete from 0%-100%. The horizontal scale shall be a time scale showing the calendar months of the project. Three curves shall be plotted on the same graph; the earnings/percent complete based on early finish dates; the earnings/percent complete based on late finish dates; the actual earnings/percent complete to date.

3.5.5.6 Bar Chart

A bar chart covering the previous month's activities and progress, and the planned activities over 3 months projected into the future. The chart shall also include actual and anticipated earnings.

3.6 PERIODIC PROGRESS MEETINGS

Progress meetings to discuss payment shall include a monthly onsite meeting or other regular intervals mutually agreed to at the preconstruction conference. During this meeting the Contractor shall describe, on an activity by activity basis, all proposed revisions and adjustments to the project schedule required to reflect the current status of the project.

The Contracting Officer will approve activity progress, proposed revisions, and adjustments as appropriate.

3.6.1 Meeting Attendance

The Contractor's Project Manager and Scheduler shall attend the regular progress meeting.

3.6.2 Update Submission Following Progress Meeting

A complete update of the project schedule containing all approved progress, revisions, and adjustments, based on the regular progress meeting, shall be submitted not later than 4 working days after the monthly progress meeting.

3.6.3 Progress Meeting Contents

Update information, including Actual Start Dates, Actual Finish Dates, Remaining Durations, and Cost-to-Date shall be subject to the approval of the Contracting Officer. The following is a minimum set of items which the

SECTION 01 32 01 Page 11

Contractor shall address, on an activity by activity basis, during each progress meeting.

3.6.3.1 Start and Finish Dates

The Actual Start and Actual Finish dates for each activity currently in-progress or completed activities.

3.6.3.2 Time Completion

The estimated Remaining Duration for each activity in-progress. Time-based progress calculations must be based on Remaining Duration for each activity.

3.6.3.3 Cost Completion

The earnings for each activity started. Payment will be based on earnings for each in-progress or completed activity. Payment for individual activities will not be made for work that contains quality defects. A portion of the overall project amount may be retained based on delays of activities.

3.6.3.4 Logic Changes

All logic changes pertaining to Notice to Proceed 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, lag durations, and other changes that have been made pursuant to contract provisions shall be specifically identified and discussed.

3.6.3.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, and 3) changes required to correct a schedule which does not represent the actual prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor requests an extension of the contract completion date, or any interim milestone date, the Contractor shall furnish the following for a determination as to whether or not the Contractor is entitled to an extension of time under the provisions of the contract: justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is obligatory to any acceptance.

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 the extension of the schedule, will not be a cause for a time extension to the contract completion date.

SECTION 01 32 01 Page 12

3.7.2 Submission Requirements

The Contractor shall submit a justification for each request for a change in the contract completion date of under 2 weeks based upon the most recent schedule update at the time of the Notice to Proceed 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.

Activities impacted in each justification for change shall be identified by a unique activity code contained in the required data file.

3.7.3 Additional Submission Requirements

For any requested time extension of over 2 weeks, the Contracting Officer may request an interim update with revised activities for a specific change request. The Contractor shall provide this disk within 4 days of the Contracting Officer's request.

3.8 DIRECTED CHANGES

If Notice to Proceed (NTP) is issued for changes prior to settlement of price and/or time, the Contractor shall submit proposed schedule revisions to the Contracting Officer within 2 weeks of the NTP being issued. The proposed revisions to the schedule will be approved by the Contracting Officer 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 suggested revisions to the project schedule. The Contractor shall 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, the Contractor shall advise the Contracting Officer within 2 weeks of receipt of the revisions. Regardless of the objections, the Contractor shall continue to update the schedule with the Contracting Officer's 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 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.

-- End of Section --

SECTION 01 32 01 Page 13

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 SUBMITTAL

1.1.2 SUBMITTAL DESCRIPTIONS (SD)

1.2 SUBMITTALS

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Government Approved

1.3.2 Information Only

1.4 APPROVED/ACCEPTED SUBMITTALS

1.5 DISAPPROVED SUBMITTALS

1.6 WITHHOLDING OF PAYMENT

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL

3.2 SUBMITTAL REGISTER

3.3 SCHEDULING

3.4 TRANSMITTAL FORM (ENG FORM 4025)

3.4.1 USE

3.4.2 NUMBERING

3.5 SUBMITTAL PROCEDURE

3.5.1 Procedures

3.5.2 Deviations

3.6 COORDINATION OF LAYOUTS

3.7 CONTROL OF SUBMITTALS

3.7.1 Monthly Updates of Submittal Register

3.8 GOVERNMENT APPROVED SUBMITTALS

3.9 INFORMATION ONLY SUBMITTALS

3.10 STAMPS

SECTION 01 33 00 Page 1

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 SUBMITTAL

Contract Clauses "FAR 52.236-5, Material and Workmanship," paragraph (b) and "FAR 52.236-21, Specifications and Drawings for Construction," paragraphs (d), (e), and (f) apply to all "submittals."

1.1.2 SUBMITTAL DESCRIPTIONS (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by SD numbers and titles as follows.

SD-01 Preconstruction Submittals

Certificates of insurance.

Surety bonds.

List of proposed subcontractors.

List of proposed products.

Construction Progress Schedule.

Submittal register.

Schedule of prices.

Health and safety plan.

Work plan.

Quality control plan.

Environmental protection plan.

SD-02 Shop Drawings

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 or equipment for some portion of the work.

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

SECTION 01 33 00 Page 2

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

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that product, system or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a supplier, installer or subcontractor through Contractor, the purpose of which is to further quality of orderly progression of a portion of the work by documenting procedures, acceptability of methods or personnel qualifications.

Confined space entry permits.

Text of posted operating instructions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative to confirm compliance with manufacturer's standards or instructions.

Factory test reports.

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. The following shall be submitted in accordance with Section:

SD-01 Preconstruction Submittals

Submittal register; G Monthly Updates (ENG Form 4288)

Four copies of the completed ENG Form 4288.

SECTION 01 33 00 Page 3

One copy of the monthly update shall be submitted together with the monthly progress payment requests.

1.3 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.3.1 Government Approved

Governmental approval/acceptance is required for extensions of design, critical materials, deviations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer. Within the terms of the Contract Clause entitled "Specifications and Drawings for Construction," they are considered to be "shop drawings."

1.3.2 Information Only

All submittals not requiring Government approval/acceptance will be for information only. They are not considered to be "shop drawings" within the terms of the Contract Clause referred to above.

1.4 APPROVED/ACCEPTED SUBMITTALS

The Contracting Officer's approval/acceptance of submittals shall not be construed as a complete check, but will indicate only that the general method of construction, materials, detailing and other information are satisfactory. Approval will not relieve the Contractor of the responsibility for any error which may exist, as the Contractor under the Contractor Quality Control (CQC) requirements of this contract is responsible for dimensions, the design of adequate connections and details, and the satisfactory construction of all work. After submittals have been approved/accepted by the Contracting Officer, no resubmittal for the purpose of substituting materials or equipment will be considered unless accompanied by an explanation of why a substitution is necessary.

1.5 DISAPPROVED SUBMITTALS

The Contractor shall make all corrections required by the Contracting Officer and promptly furnish a corrected submittal in the form and number of copies specified for the initial submittal. If the Contractor considers any correction indicated on the submittals to constitute a change to the contract, a notice in accordance with the Contract Clause "Changes" shall be given promptly to the Contracting Officer.

1.6 WITHHOLDING OF PAYMENT

Payment for materials incorporated in the work will not be made if required approvals have not been obtained and/or complete, satisfactory "FIO" submittals have not been received by the Government.

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL

The Contractor shall make submittals as required by the specifications.

SECTION 01 33 00 Page 4

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 shall be the same as those used in the contract drawings. Each submittal shall be complete and in sufficient detail to allow ready determination of compliance with contract requirements. Prior to submittal, all items shall be checked and approved by the Contractor's Quality Control System Manager (CQCSM) and each item shall be stamped, signed, and dated by the CQCSM indicating action taken. Proposed deviations from the contract requirements shall be clearly identified.

Submittals shall include 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 shall be scheduled and made prior to the acquisition of the material or equipment covered thereby. Samples remaining upon completion of the work shall be picked up and disposed of in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

3.2 SUBMITTAL REGISTER

At the end of this section is one set of Submittal Forms listing items of equipment and materials for which submittals are required by the specifications; this list may not be all inclusive and additional submittals may be required. The Contractor shall use the government-provided software, QCS (see Section 01 45 01 QUALITY CONTROL SYSTEM (QCS)), to create the ENG Form 4288. The Contractor is responsible for completing the columns labeled: Activity Number, Transmittal Number, and Contract Schedule Dates on the submittal resister form. The completed Submittal Register shall be submitted to the Contracting Officer for approval within 30 calendar days after Notice to Proceed. The submit dates and need dates in the submittal register shall be coordinated with the dates in the Contractor's progress schedule. Updates to the Submittal Register showing the Contractor action codes and actual submittal dates with Government action codes and action dates shall be submitted monthly together with the monthly payment request, or until all submittals have been satisfactory completed. When the progress schedule is revised, the submittal register shall also be revised and both resubmitted for approval. The approved submittal register will serve as a scheduling document for submittals and will be used to control submittal actions throughout the contract period.

3.3 SCHEDULING

Submittals covering component items forming a system or items that are interrelated shall be scheduled to be coordinated and submitted concurrently. Certifications to be submitted with the pertinent drawings shall be so scheduled. Adequate time (a minimum of 30 calendar days exclusive of mailing time) shall be allowed and shown on the register for review and approval. No delay damages or time extensions will be allowed for time lost in incorrect, incomplete and/or late submittals. An additional 15 calendar days shall be allowed and shown on the register for review and approval of submittals for food service equipment, fire sprinkler and fire alarm systems, and refrigeration and HVAC control systems.

SECTION 01 33 00 Page 5

3.4 TRANSMITTAL FORM (ENG FORM 4025)

3.4.1 USE

A transmittal form (ENG Form 4025) shall be used for submitting both Government approved and information only submittals. The Contractor shall use the government provided software, QCS (see Section 01 45 01 QUALITY CONTROL SYSTEM (QCS)), to create the Eng Form 4025. A separate transmittal form shall be used for each specification section. This form shall be properly completed by filling out all the heading blank spaces and identifying each item submitted. Special care shall be exercised to ensure proper listing of the specification paragraph and/or sheet number the contract drawings pertinent to the date submitted or each item.

3.4.2 NUMBERING

Transmittals will be automatically numbered by QCS. The transmittal number will consist of 2 parts, the specification number and the sequence number, e.g. 01330-001. Each specification section will begin with the sequence number, 001. Resubmittals will be identified by a decimal number appended to the original transmittal number, e.g. 01330-001.1, will identify resubmittals.

3.5 SUBMITTAL PROCEDURE

Submittals shall be made as follows:

3.5.1 Procedures

The Contractor shall establish procedures for purchasing materials and equipment, subcontracting, and processing of shop drawings, outlining the responsibilities at each level to insure that adequate review and approval, timely delivery, verification of procedures and proper storage are provided. Delays in the review and approval process shall not be given consideration for a time extension or additional cost, when such delays are the result of the Contractor's late submittal or failure to provide proper submittals; or make corrections in compliance with the contract documents or the Contracting Officer's comments; or provide a resubmittal because if an unacceptable original submittal.

Submittals to the Contracting Officer are required in the number of copies identified in paragraphs 3.7 and 3.8 and shall be submitted to:

U.S. Army Corps of Engineer District, Honolulu Fort Shafter Area Office Bldg 230 Fort Shafter, Hawaii 96858-5440

3.5.2 Deviations

a. For submittals which include proposed deviations requested by the Contractor, the column "variation" of ENG Form 4025 shall be checked. The Contractor shall set forth in writing the reason for any deviations and annotate such deviations on the submittal. The Government reserves the right to rescind inadvertent approval of submittals containing unnoted deviations.

b. In cases where "trade names or equal" are used in the plans and/or Technical Specifications, any "equal" substitution by the

SECTION 01 33 00 Page 6

Contractor is considered a variance and will require the Government's approval. Approval action by the Contracting Officer will not relieve the Contractor of his quality control responsibility and compliance with the contract, except for those specific portions of the submittal which clearly highlight the departures from the contract, and which are brought to the attention of the Government. The Contractor shall be responsible for all corrective actions, when submittals containing provisions of non-compliance with the contract are not specifically brought to the Government's attention. Any associated cost or time loss from such corrective actions shall not be made subject to a claim against the Government.

c. Variations from the contract requirements may require an appropriate contract modification prior to acceptance by the Government; however, such pending action shall not be a basis of claim for time or additional cost against the Government, since the Contractor still has the option to comply with the original contract requirements. If the variation is of a minor nature and does not affect a change in cost or time of performance, a modification may not be issued. All variations shall meet the standards set by the contract documents.

3.6 COORDINATION OF LAYOUTS

The Contractor Quality Control (CQC) organization is responsible for insuring that the shop drawings and submittals of the different trades are coordinated in order that space conflicts during installation/construction of mechanical, electrical, architectural, civil, structural and other items of work are avoided. The Contractor shall be required to prepare/develop coordinated working layout drawings prior to commencement of any feature of work, at any Contractor tier, unless otherwise directed by the Contracting Officer. These layout drawings shall be reviewed and certified by the CQC organization prior to the start of work in any area. The CQC shall insure that layout drawings indicate all necessary features of work, providing for a coordinated arrangement of the various installations, giving full consideration for access to installed equipment/systems and the future maintenance of these items. Interference between equipment and systems or construction materials which cannot be resolved between Contractor and subcontracting tiers shall be resolved by the Contracting Officer at no additional cost to the Government, if it is determined that adequate space was available and installations could have been accommodated within the designated construction area through properly coordinated layout drawings.

One (1) CQC certified copy of all layout drawings shall be available for Government's review five (5) working days prior to scheduled commencement of the work. Submission shall be made upon Government's request.

3.7 CONTROL OF SUBMITTALS

The Contractor shall carefully control his procurement operations to ensure that each individual submittal is made on or before the Contractor scheduled submittal date shown on the approved "Submittal Register.

3.7.1 Monthly Updates of Submittal Register

Monthly updates of the initially accepted Submittal Registers, ENG Form 4288, shall be submitted in duplicate at the time the monthly progress payment is requested and be current to within one (1) week of the date of submission. When a monthly payment is not being requested, the update

SECTION 01 33 00 Page 7 shall be submitted on the 15th of each month or the workday closest to the 15th. If the Contractor fails to provide the Government acceptable initial submittal registers or monthly updates within the specified time frames, the Government may issue a stop work order and/or withhold a portion of pending progress payments due to non-performance. Any resulting cost or time loss to the Contractor due to such Government action shall not be subject to a claim for the time extensions, additional cost or for damages by the Contractor. Furnishing of the submittal registers by the Contractor and subsequent review/acceptance by the Government do not relieve the Contractor of the obligation to comply with all of the contract submittal requirements; for example, even if a required submittal was not originally listed on the initial register accepted by the Government, the Contractor will still be responsible for providing such submittal in accordance with the contract. The following shall be provided on the monthly updates to the initially accepted schedule:

a. Activity No., Transmittal No., and entries under other columns, as appropriate.

b. Distinguish those submittals which are VARIANCES, as appropriate.

c. Furnish a separate LISTING of required SUBMITTALS, together with the Government's review comments, and appropriate Contractor's status report on pending resubmittal actions.

d. Furnish a separate LISTING of SUBMITTALS provided by the Contractor to the Government; and another separate LISTING of SUBMITTALS returned by the Government to the Contractor, for the particular month the update is furnished.

3.8 GOVERNMENT APPROVED SUBMITTALS

Upon completion of review of submittals requiring Government approval, the submittals will be identified as having received approval by being so stamped and dated. 3 copies of the submittal will be retained by the Contracting Officer and 1 copy of the submittal will be returned to the Contractor.

3.9 INFORMATION ONLY SUBMITTALS

Submittals provided For Information Only (FIO) to the Government shall be submitted in three (3) copies, including resubmittals. Normally submittals for information only will not be returned. Approval of the Contracting Officer is not required on information only submittals. The Government reserves the right to require the Contractor to resubmit any item found not to comply with the contract. This does not relieve the Contractor from the obligation to furnish material conforming to the plans and specifications;

will not prevent the Contracting Officer from requiring removal and replacement of nonconforming material incorporated in the work; and does not relieve the Contractor of the requirement to furnish samples for testing by the…