01_32_01.00_10_Project_Schedule.pdf

SECTION 01 32 01.00 10

PROJECT SCHEDULE

05/08

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.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 SCHEDULING SOFTWARE REQUIREMENTS

3.3.1 License for the Government

3.3.2 Compatibility with SDEF

3.4 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.4.1 Critical Path Method

3.4.2 Level of Detail Required

3.4.3 Scheduled Project Completion and Activity Calendars

3.4.4 Early Project Completion

3.4.5 Interim Completion Dates

3.4.6 Default Progress Data Disallowed

3.4.7 Out-of-Sequence Progress

3.4.8 Negative Lags and Start to Finish Relationships

3.4.9 Calculation Mode

3.4.10 Milestones

3.5 PROJECT SCHEDULE SUBMISSIONS

3.5.1 Preliminary Project Schedule Submission

3.5.2 Initial Project Schedule Submission

3.5.3 Schedule Updates

3.5.4 Periodic Schedule Changes

3.5.5 Standard Activity Coding Dictionary

3.6 SUBMISSION REQUIREMENTS

3.6.1 Electronic Data

3.6.2 Narrative Report

3.6.3 Approved Changes Verification

3.6.4 Network Diagram

3.7 PERIODIC MEETINGS

3.7.1 Update Submission Following Progress Meeting

3.7.2 Status of Activities

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Submission Requirements

3.8.3 Additional Submission Requirements

3.9 DIRECTED CHANGES

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

SECTION 01 32 01.00 10 PROJECT SCHEDULE (05/08)

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)

ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in Construction

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) Qualifications of Scheduler (G)

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

SD-11 Closeout Submittals As-Built Schedule (G)

1.3 QUALIFICATIONS

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 and have previously developed, created, and maintained at least 2 (two) electronic schedules for projects 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.

This position is a permanent position and shall be filled from the time of Notice to Proceed until completion. The representative may have other duties only if approved in advance by the Contracting Officer.

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

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 the entire project is required.

Scheduling is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. Subcontractors and suppliers, Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The schedule must be 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.

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

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 or qualified scheduling personnel will result in an inability of the Contracting Officer to evaluate contract earned value 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.3 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.

3.3.1 License for the Government

During the performance of the contract, through final payment, the contractor shall provide, at no additional cost to the government, one (1) licensed copy of the scheduling software for use of the government. The software and license shall be returned to the contractor after final payment has been made, unless requested otherwise by the contractor.

3.3.2 Compatibility with SDEF

The scheduling software must meet the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 to allow for interchange of data with the QCS software required by Section 04 45 01.10 USACE QUALITY CONTROL SYSTEM (QCS). Should the contractor utilize software which is not compatible with the SDEF, the contractor shall be responsible for manually entering and updating all schedule information in QCS.

3.4 PROJECT SCHEDULE DETAILED REQUIREMENTS

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

Bar charts or other scheduling methods which do not show dependencies between activities shall not be allowed

3.4.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 characteristics and requirements identified in the following paragraphs to determine appropriate level of detail. The government reserves the right to direct the contractor to add additional activities or provide a further breakdown of activities to ensure the adequacy of the schedule.

3.4.2.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Procurement activities are defined herein.

3.4.2.2 Design and Permit Activities

Include any design and permit activities with the necessary conferences and follow-up actions and design package submission dates, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period.

This shall be at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. The schedule shall include review and correction periods associated with each item. This should be a forward planning as well as a project monitoring tool.

3.4.2.3 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.4.2.4 Mandatory Tasks

The following tasks, when identified elsewhere in these specifications or scope of work, must be included and properly scheduled:

a. Submission, review and acceptance of design packages.

b. Submission of systems and/or shop drawings.

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Submission and approval of 1354 data and installed equipment lists.

f. Submission and approval of testing and air balance (TAB).

g. Submission of TAB specialist design review report.

h. Submission and approval of fire protection specialist.

i. Submission and approval of testing and balancing of HVAC plus commissioning plans and data. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with ECB 2005-10.

j. Air and water balancing.

k. HVAC commissioning.

l. Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

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

r. Government's pre-final inspection.

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

t. Final inspection.

3.4.2.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.4.2.6 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity.

Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, 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); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for

USACE).

3.4.2.7 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.4.2.8 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.4.2.9 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.4.2.10 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. Code activities to either a Design Phase or a Construction Phase. Code fast track phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages. If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase 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.4.2.11 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: design, design submittal, design reviews, review conferences, permits, construction submittals, construction submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive

Installation, Non-Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a Category of Work Code to each activity. Each activity shall have only one Category of Work Code.

3.4.2.12 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 01 USACE QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. All activities are required to be Definable Feature of Work Coded.

3.4.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, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged 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.4.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.4.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 float constraints such as "zero fee float" or "zero total float" are 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.4.4 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, 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.4.5 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.4.5.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.4.5.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.4.5.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.4.6 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.

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.4.7 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.4.8 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.4.9 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.4.10 Milestones

The schedule must include milestone activities for each significant project event.

3.5 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.5.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required Plan and Program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, the planned submissions of all early design packages, permitting activities, design review conference activities and other non-construction activities intended to occur within the first 90 calendar days. Schedule any construction activities planned for the first 90 calendar days after NTP.

Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.5.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 45 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 in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences; permit submissions and any required Government actions; and long lead item acquisition prior to design completion.

3.5.3 Schedule Updates

The contractor shall update the schedule on a regular basis and submit a schedule which has been updated within the last 72 hours with all requests for payment as a separate submittal. 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.5.4 Periodic Schedule Changes

When it becomes necessary to change or revise (not update) the approved schedule, prepare a detailed narrative identifying all changes to the project schedule by activity, to include all changes in logic, and discuss the changes with the government during the meeting described in paragraph

PERIODIC MEETINGS.

No changes or revisions to the schedule shall be made without prior coordination with the Contracting Officers Representative. As a result of the meeting discussed above, the government will either allow the contractor to prepare and submit for approval a revised project schedule, or provide other written direction.

Requests for payment shall not include any changes or revisions from the last approved project schedule. If a proposed change has not been approved via the completion of a submittal, regardless of any other discussions, they shall not be shown in any schedule attached to a request for payment.

3.5.5 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: www.rmssupport.com. The SDEF format is as follows:

Field Code Length Description

1 WRKP 3 Workers per Day 2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE) 3 AREA 4 Area of Work 4 MODF 6 Modification or REA number 5 BIDI 6 Bid Item (CLIN) 6 PHAS 2 Phase of Work 7 CATW 1 Category of Work http://www.rmssupport.com/

8 FOW1 10 Feature of Work (1st 10 characters) 9 FOW2 10 Feature of Work (2nd 10 characters) 10 FOW3 10 Feature of Work (3rd 10 characters)

3.6 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update or Revision throughout the life of the project:

3.6.1 Electronic Data

Provide one copy of the schedule in electronic format. This may be provided via e-mail or electronic/optical media.

3.6.2 Narrative Report

Provide a Narrative Report. 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.6.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. It shall also clearly identify all proposed changes in logic, successors/predecessors, durations, or sequencing of activities, and the proposed reason for the change explained.

3.6.4 Network Diagram

A network diagram is required for the Preliminary, Initial and Periodic Updates. 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.6.4.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.6.4.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.6.4.3 Critical Path

Clearly show the critical path.

3.6.4.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.6.4.5 S-Curves

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

3.7 PERIODIC MEETINGS

At least monthly, jointly review the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks, as well as reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. This meeting may take place during the normal Coordination Meeting as described in Section 01 45 01 USACE QUALITY CONTROL.

A draft of any proposed changes in the schedule, including activity logic corrections and narrative report shall be provided to the Government 72 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with the Authorized Representative of the Contracting Officer.

Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis.

Provide a bar chart produced by the scheduling software, organized by Total Float and Sorted by Early Start Date, and a two 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.

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.7.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

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

3.7.2.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.7.2.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.7.2.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 punch list 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.7.2.4 Logic Changes

Specifically identify and discuss all logic changes. 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.7.2.5 Other Changes

Identify and discuss 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.8 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 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, the Contractor shall submit a schedule impact analysis demonstrating whether or not the change contemplated by the Government impacts the critical path.

3.8.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.8.2 Submission Requirements

Submit a justification for each request for a change in the contract completion date. 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.8.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.9 DIRECTED CHANGES

If a 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. 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, 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.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

The Contractor shall download and upload the schedule data into the Resident Management System (RMS) prior to RMS databases being transferred to the Government and 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.

-- End of Section --