01 32 01.00 15 Project Schedule

SECTION 01 32 01.00 15

PROJECT SCHEDULE (Alternate)

07/09

PART 1: GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 QUALIFICATIONS

1.4 DESIGN-BUILD REQUIREMENTS

1.5 PAYMENT

1.6 UPDATES VERSUS CHANGES

PART 2: PRODUCTS

PART 3: EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 SCHEDULING SOFTWARE REQUIREMENTS

3.3 BASIS FOR PAYMENT AND COST LOADING

3.4 PROJECT SCHEDULE

3.4.1 Level of Detail Required

3.4.2 Activity Durations

3.4.3 Modification or Claim Number

3.4.4 Bid Item

3.4.5 Scheduled Project Completion

3.4.6 Interim Completion Dates

3.4.7 Default Progress Data Disallowed

3.5 PROJECT SCHEDULE SUBMISSIONS

3.6 SUBMISSION REQUIREMENTS

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.8 DIRECTED CHANGES

3.9 OWNERSHIP OF FLOAT

PART 1: GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for 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 Project Schedule (G)

SECTION 01 32 01.00 15 PROJECT SCHEDULE (ALTERNATE) (07/09)

SD-07 Certificates Monthly Network Analysis Updates and Narrative (G)

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. This person may be assigned other duties

1.4 DESIGN-BUILD REQUIREMENTS

If the scope of work of this contract calls for the contractor to perform design, all references herein referring to “activities” or “Construction” shall apply to all design and construction activities, and all references to “subcontractors” shall be read as to include designers.

If no design is called for as part of this contract, all references to “design” or “designer” shall be ignored.

1.5 PAYMENT

Separate payment will not be made for compliance with this specification.

All costs associated therewith shall be included in the applicable unit prices or lump-sum prices contained in the Bidding Schedule.

1.6 UPDATES VERSUS CHANGES

As defined in this specification section, updates to the project schedule refers to information associated with an activity that is changed to reflect actual conditions, and is primarily limited to the entry of actual start and finish dates or changes in the scheduled start and finish dates of an activity based on the actual durations of dependent activities.

Changes or revisions to the project schedule refers to all changes in activity logic, division or joining of activities, changes in scheduled duration or amounts, and any other revisions which alter the planned execution of the works. No changes shall be made to the project schedule without either the express written direction of the Contracting Officer, or their prior approval. All changes must be provided via a formal submittal and shown on the submittal register. Any changes not specifically authorized by the Contracting Officer may result in disapproval of the entire schedule and the rejection of any requests for partial payment.

PART 2: PRODUCTS

(Not Applicable)

PART 3: EXECUTION

3.1 GENERAL REQUIREMENTS

Pursuant to the Contract, a Project Schedule as described below shall be prepared. The scheduling of construction shall be the responsibility of the Contractor. 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 SCHEDULING SOFTWARE 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.

The contractor shall utilize a software that is fully compatible with Primavera project scheduling software. The Contractor shall provide electronic files saved in a format that is compatible with the Contracting Officer's current software version. Additionally, the Contractor shall be responsible for loading the project schedule into the QCS software (reference Specification 01 45 01.10 USACE QUALITY CONTROL SYSTEM (QCS) using either the Corps of Engineers Standard Data Exchange Format (SDEF) or by manually entering the data.

3.3 BASIS FOR PAYMENT AND COST LOADING

The schedule shall be used 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 will result in an inability of the Contracting Officer to evaluate progress for the purposes of payment. If the Contractor fails to submit any schedule within the time prescribed, or if it is determined that the contractor is not following the approved schedule, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

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.4 PROJECT SCHEDULE

3.4.1 Level of Detail Required

The Project Schedule shall include an appropriate level of detail, including the identification of separate activities for:

a. Submission, review and acceptance of design packages

b. Permitting requirements

c. Procurement of long lead materials or equipment (procurement cycle of over 90 days). Examples of procurement process activities include, but are not limited to: submittals, approvals, procurement, fabrication, and delivery.

d. Government and other agency activities that could impact progress, such as: approvals, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

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

3.4.3 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 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, except in the case of decreases, where all decreases must be identified in an existing activity.

3.4.4 Bid Item

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

3.4.5 Scheduled Project Completion

The schedule interval shall extend from NTP to the contract completion date.

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

3.5 PROJECT SCHEDULE SUBMISSIONS

The Contractor shall, within five days after the work commences on the contract or another period of time determined by the Contracting Officer, prepare and submit to the Contracting Officer for approval a practicable schedule showing the order in which the Contractor proposes to perform the work, and the dates on which the Contractor contemplates starting and completing the several salient features of the work (including acquiring materials, plant, and equipment). The schedule shall be in the form of a progress chart of suitable scale to indicate appropriately the percentage of work scheduled for completion by any given date during the period.

3.6 SUBMISSION REQUIREMENTS

The Contractor shall update the actual progress on the chart as directed by the Contracting Officer, but no less than every 30 calendar days; and upon doing so shall immediately deliver three copies of the annotated schedule to the Contracting Officer. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall 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 Contractor shall 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.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 approvals.

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.

3.8 DIRECTED CHANGES

If the 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 with 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 --