A.07.23_Attachment_4_-_Schedule_Spec.PDF

Attachment 4 – Project Schedule - Page 1

Attachment 4

CONSTRUCTION SCHEDULING

1. GENERAL

1.1 SCOPE OF WORK

1.1.1 Furnish all labor, materials, equipment and incidentals required to prepare and update critical path method project schedules and prepare the weekly progress reports for review at the Pre-Construction Conference and subsequent progress meetings. The schedule shall be entered by the Contractor into the Resident Management System (RMS).

1.1.2 Prepare and update the Contractor’s Project Schedule using a computer software system that produces legible, easily updated critical path schedules. The software shall be capable of providing a bar chart type schedule for use by the Government in interactions with the public and for discussion at progress meetings.

1.2 QUALIFICATIONS

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

1.3 SUBMITTALS

1.3.1 The Contractor shall provide the project schedule submissions as described below. The following shall be submitted in accordance with:

1. Preliminary Project Schedule

a. The Preliminary Project Schedule, defining the

Contractor's planned operations for the first 60 calendar days shall be submitted for approval within 20 calendar days after the construction contract is awarded.

2. Initial Project Schedule

a. The Initial Project Schedule shall be submitted for approval at least 14 calendar days prior to the Pre-Work

Conference. 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. Periodic Schedule Updates

Attachment 4 – Project Schedule - Page 2

a. The Contractor shall submit periodic schedule updates at least once per month. These submissions shall enable the

Engineer to assess the Contractor’s progress. If the

Contractor fails or refuses to furnish the information and project schedule data, which in the judgment of the

Engineer or authorized representative is necessary for verifying the Contractor's progress, no progress payments will be made.

2.0 EXECUTION

2.1 GENERAL REQUIREMENTS

2.1.1 A project schedule as described below shall be

prepared. The approved Project Schedule shall be used to measure the progress of the work and to aid in evaluating time extensions and progress payments, as required.

2.2 PROJECT SCHEDULE

2.2.1 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. Manual methods used to produce any required information shall require approval by the

Engineer.

2.2.1.1 Use of the Critical Path Method - The Critical Path

Method (CPM) of network calculation shall be used to generate the

Project Schedule. The Contractor shall provide the Project

Schedule in the Precedence Diagram Method (PDM).

2.2.1.2 Level of Detail Required - The Project Schedule shall include an appropriate level of detail. Failure to develop or update the Project Schedule or provide data to the USACE

Representative at the appropriate level of detail, as specified by the USACE Representative, shall result in the disapproval of the schedule. The USACE Representative will use, but will not be limited to, the following conditions to determine the appropriate level of detail to be used in the Project Schedule.

i. Activity Durations

Reasonable activity durations shall be incorporated into the schedule. Reasonable activity durations are those that allow the progress of activities to be accurately determined.

ii. Procurement Activities

Attachment 4 – Project Schedule - Page 3

Tasks related to the procurement of long lead materials or equipment shall be included as separate activities in the Project Schedule.

iii. Government Activities

Government and other agency activities that could impact progress shall be shown. These activities include, but are not limited to: approvals and inspections.

iv. Work Areas

All activities shall be identified in the Project

Schedule by the work area/site in which the activity occurs. Activities shall not be allowed to cover more than one work area.

v. 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 modification or claim number.

Activities shall not belong to more than one modification or claim item. Whenever possible, changes shall be added to the schedule by adding new activities. Existing activities shall not normally be changed to reflect modifications.

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

2.2.1.3 Scheduled Project Completion - The schedule interval

shall extend from the contract start date to the contract completion date.

i. Project Start Date

The schedule shall start no earlier than the date on which the 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 an “Early Start” (ES) constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

ii. Constraint of Last Activity

Attachment 4 – Project Schedule - Page 4

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 “Finish Project”. The “Finish Project” activity shall have an “LF” constraint date equal to the contract completion date for the project with a zero day duration.

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 “Late Finish”

(LF) constraint date equal to the completion date for the project, and a zero day duration.

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

i. Start Site

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.

ii. End Site

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 phase, and a zero day duration.

iii. Site X

The Contractor shall include a hammock type activity for each project site called “Site X” where “X” refers to the sub-district site in which the work is being

Attachment 4 – Project Schedule - Page 5 conducted. The “Site X” activity shall be logically tied to the earliest and latest activities for that site.

2.2.1.5 Milestones – The schedule must include milestone

activities for each significant project event including, but not limited to Work Plan approval, Start Site X, Finish Site

X, and IRAR Report Completion.

2.3 SUBMISSION REQUIREMENTS

2.3.1 The following items shall be submitted by the Contractor for the preliminary submission, initial submission, and every periodic project schedule update throughout the duration of the project.

2.3.1.1 Data Disks - Two compact discs containing the

Project Schedule shall be provided. The compact disc shall be a “CD-R” format and shall be labeled to indicate the type of schedule (Preliminary, Initial, Update, or Change), full contract number, project name, project location, data date and the name and telephone number or person responsible for the schedule. The submitted schedule shall be in .PDF format as well as in the native software format.

2.3.1.2 Narrative Report - A Narrative Report shall be

provided with the preliminary, initial, and each update of the Project Schedule. The Narrative Report shall include a description of activities along the critical paths, 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 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.

2.3.1.3 Approved Changes Verification - Only project

schedule changes that have been previously approved by the

USACE Representative shall be included in the schedule submission.

2.4 PERIODIC PROGRESS MEETINGS

Progress meetings to discuss schedule shall include a monthly on-site meeting or other regular intervals mutually agreed to at the

Pre-Construction meeting. During this meeting the Contractor shall describe all proposed revisions and adjustments to the Project

Schedule required to reflect the current status of the project.

Attachment 4 – Project Schedule - Page 6

The USACE Representative will approve proposed revisions and adjustments as appropriate.

2.5 TIME EXTENSIONS FOR DIRECTED CHANGES

If a 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 COR within 14 calendar days of the NTP being issued. The proposed revisions to the schedule will be approved by the COR or Contracting Officer, as appropriate, prior to inclusion of those changes within the Project Schedule. If the

Contractor fails to submit the proposed revisions, the COR 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 USACE Representative, the Contractor shall advise the USACE Representative within 14 calendar days of receipt of the revisions. Regardless of the objections, the Contractor shall continue to update the schedule with the COR’s revisions until a mutual agreement in the revisions is reached. If the Contractor fails to submit alternative revisions within 14 calendar days of receipt of the COR's proposed revisions, the Contractor will be deemed to have concurred with the COR's proposed revisions. The proposed revisions will then be the basis for an equitable adjustment for performance of the work.

END OF SECTION