ATTACHMENT 03 Section 01 32 00 Project Schedule.pdf

SECTION 01 32 00

PROJECT SCHEDULE

PART 1-GENERAL.

1.1 Payment. No separate payment will be made for providing work required by this section and all costs associated therewith shall be included in the applicable unit prices of the work it pertains.

1.2 REFERENCES:

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

B. U.S. ARMY CORPS OF ENGINEERS (USACE) ER 1-1-11 Progress, Schedules, and Network Analysis Systems

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

1.4 Submittals.

A. Sequencing and Scheduling. The Contractor shall furnish the Contracting Officer a Project Progress Schedule at least two weeks prior to the start of work.

The schedule shall indicate all phases of work including any design-effort submittals required by the Task Order. The construction portion of the schedule shall include, but is not limited to, projected dates of the start and completion of work at the jobsite, and projected start and completion dates for each major phase of construction.

B. Changes to the Schedule. Changes to the Progress Schedule shall be submitted by the Contractor to the Contracting Officer, in writing, two weeks prior to the scheduled start of the affected work on the jobsite, or as directed by the Contracting Officer.

PART 2 - PRODUCTS (Not Applicable)

PART 3. EXECUTION

3.1 General. The Contractor shall be responsible for scheduling of all design, procurement and construction activities. Designers, Subcontractors and Suppliers should provide input for the schedule. The approved Project Progress Schedule shall be use by the Contracting Officer to measure the progress of the work, to aid in evaluating requests for time extensions, and to provide a 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 will result in an inability of the Contracting Officer to evaluate Contractor's 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, 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 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. Manual methods used to produce any required information shall require approval by the Contracting Officer.

A. 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 as a Gantt (Bar) chart.

B. 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 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:

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 are greater than 20 days).

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, and delivery.

3. Critical Activities:The following activities shall be listed as separate line activities on the Contractor's project schedule:

a. Design if required by the task order.

b. Prefinal inspection.

c. Correction of punchlist from prefinal inspection.

d. Final inspection.

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

approvals, approvals, design reviews, environmental permit approvals by State regulators, inspections, and Notice to Proceed (NTP) for phasing requirements.

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

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

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

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

C. Scheduled Project Completion: The schedule interval shall extend from NTP to the contract completion date.

1. 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 "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

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 an "LF" constraint date equal to the completion date for the project, and a zero day duration.

3. Early Project Completion: In the event the project schedule shows completion of the project prior to the contract completion date, the Contractor shall identify those activities that have been accelerated and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. Contractor shall specifically address each of the activities noted in the narrative report at every project schedule update period to assist the Contracting Officer in evaluating the Contractor's ability to actually complete prior to the contract period.

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

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.

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

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

F. Out-of-Sequence Progress: Activities that have posted progress without all preceding logic being satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case approval 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.

G. 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 reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS.

A. Preliminary Project Schedule Submission: The Preliminary Project Schedule, defining the Contractor's planned operations shall be submitted for approval within 10 calendar days after the NTP is acknowledged. The approved preliminary schedule shall be used for payment purposes not to exceed the first 30 calendar days after NTP.

B. Initial Project Schedule Submission: The Initial Project Schedule shall be submitted for approval within 30 calendar days after NTP. 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.

C. 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 to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgement 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.5 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.

A. Meeting Attendance: The Contractor's Project Manager and Scheduler shall attend the regular progress meeting.

B. 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, and shall be submitted not later than 4 working days after the monthly progress meeting.

C. 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. As a minimum, the Contractor shall address the following items on an activity by activity basis during each progress meeting. 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.6 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 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.

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

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