EXHIBIT 2-2-C SCHEDULES

Transcription

1 EXHIBIT 2-2-C SCHEDULES PART 1 GENERAL 1.01 SUMMARY A. The Work specified in this section consists of furnishing transportation, labor, materials, equipment, and incidentals necessary for preparation, submittal, and updating of the Project schedules and reports. B. The Design-Builder shall develop and maintain a resource integrated scheduling system for this Contract. Planning, scheduling, management, and execution of the Work in accordance with Contract Documents are the sole responsibility of Design-Builder. Whenever the term schedule is used in this section it shall mean a Critical Path Method (CPM) schedule RELATED REQUIREMENTS Not used REFERENCE A. Construction Planning & Scheduling Manual by the Associated General Contractors of America 1.04 MEASUREMENT AND PAYMENT A. Not Applicable 1.05 DEFINITIONS A. The following definitions shall apply to the provisions contained herein: 1. Activity A task that is a definable part of the overall Project. The task must be performed in order to complete the Work defined in the Contract. Activities have interrelationships, and are measurable by resource and time. 2. Critical Path Method (CPM) A schedule network of all Work to be performed under the Contract that has been defined and organized by Activities. 3. Data Date The Day after the Month End Cut-Off, through which progress updates will be calculated. Everything occurring earlier than the data date is actual Work completed and everything on or after the data date is Work planned to be completed. Final for Execution 1

2 4. Fragnet A section or fragment of the network diagram comprising a group of Activities used to illustrate changes and impact to the whole network. 5. Look-Ahead Schedule A weekly schedule indicating the previous week s Work and the Work planned for the next two weeks. This is in greater detail than the network schedule. The Look-Ahead Schedule shall conform to the current Updated Schedule. 6. Milestone A marker in a schedule network, which is typically used to mark a point in time or denote the beginning or end of a sequence of Activities. A Milestone is linked with other scheduled Activities via logic ties. A Milestone has zero duration, no Resources, and no quantities. 7. Month End Cut-Off The last Day of the month or a Day negotiated at the pre-construction meeting. 8. Narrative Report A written text report that addresses the Project status, Resources, and issues. The narrative shall include appropriate details to address the following as needed: Project progress, potential problem areas, current and anticipated delaying factors and their impact, actions taken or proposed, proposed changes in schedule logic, extension or contraction of Activities, proposed addition or deletion of Activities, explanation for changes in the Critical Path, explanation for changes in Design-Builder s scheduled date for Substantial Completion, out of sequence Work, and other topics related to job progress or scheduling. 9. Negative Float Having a net negative Float condition. 10. Recovery Schedule The Design-Builder s plan to bring the Contract Work back on schedule. This schedule may require additional Resources. 11. Resource The labor and equipment required to complete an Activity. 12. Resource Dictionary Defines the Resources used in the schedule, including description, units, and normal and maximum number of units. Resources are assigned to each Activity from the Resource Dictionary. 13. Time Impact Analysis Provides guidelines and methods to assess and quantify the effects of an unplanned event or events on Activities and/or Milestones as required in section 3.04 contained herein. 14. Total Float The amount of time that an Activity may be delayed without delaying a Completion Deadline. 15. Updated Schedule The most current schedule in effect, which incorporates actual progress and sequence of Activities to date, projected completion dates and proposed logic changes for future Work, and Approved Change Orders. Final for Execution 2

3 1.06 SUBMITTALS A. Schedule submittals shall be clear, neat, legible, and reproducible. These documents shall include a narrative explaining the schedule, a color bar chart, and time-scaled network diagram. Tabular reports shall be printed on Letter- Size (8.5 inch by 11 inch) paper. Hardcopy scheduling submittals shall consist of six color copies of the schedule (size 11 inch by 17 inch) and tabular reports, unless noted otherwise. All schedules, except the Look-Ahead Schedule, shall be backed up via CD-RW disc format and submitted to the Port. B. The schedules, tabular reports, and narratives shall include the Contract name, specification number, Data Date, file name, and date of the submittal on each page. C. The Design-Builder shall re-submit all revised schedules and tabular reports within seven (7) Days after receipt of Port s response if the Port requires change and/or information. D. The Design-Builder shall continuously maintain an Updated Schedule using the scheduling software as directed by the Port. All updates shall be available to the Port. E. The following is a summary of the submittal requirements. The details of each submittal requirement are discussed at length in the respective sections. 1. Preliminary 120-Day schedule shall be submitted in accordance with Book Look-Ahead Schedules and Updated Schedules shall be submitted weekly and monthly respectively using the scheduling software. a) Look-Ahead Schedules and tabular reports shall be formatted as requested by the Port and submitted for the weekly progress meetings. b) Updated Schedules, tabular reports, and narratives shall be submitted by the end of the month for the month-end review. 3. Fragnets shall be submitted at the request of the Port if the Design- Builder is delayed in execution of Work as indicated by Negative Float, or when the Updated Schedule no longer appears to represent actual execution of Work. 4. Final as-built schedule shall be submitted within thirty (30) Days of Substantial Completion of the Contract. 5. Written narratives shall be submitted with every Updated Schedule submittal. The narratives shall stand alone with sufficient detail to Final for Execution 3

4 1.07 QUALITY ASSURANCE explain the Design-Builder s schedule submittal. A. A scheduler shall be employed by the Design-Builder and shall have a minimum of five (5) years of experience using Primavera scheduling software, two years of which must be using Primavera P6 Professional Project Management. B. If the Design-Builder does not have a scheduler on staff, the Design-Builder shall submit for Acceptance, a consultant scheduler fulfilling the outlined qualifications for the duration of the Project. C. The scheduler provided by the Design-Builder shall cooperate with the Port and shall be available for the purpose of continuously monitoring, reporting, and maintaining the Design-Builder's schedule. D. Within fifteen (15) Days of NPT1, the Design-Builder shall submit to the Port the scheduler's qualifications including resume of experience as a construction project scheduler, and at least four professional references that have had experience with the individual as a construction project scheduler. The Port has the right to reject the scheduler. E. If the Port rejects the scheduler proposed by the Design-Builder, the Design- Builder shall, within seven (7) Days, provide another scheduler who meets the experience requirements stated herein. PART 2 PRODUCTS 2.01 SOFTWARE A. The Design-Builder shall use Primavera P6 Professional Project Management (P6) for the resource integrated scheduling system. PART 3 EXECUTION 3.01 MEETING REQUIREMENTS A. The Design-Builder s scheduler shall attend the following: 1. Pre-construction meeting 2. Weekly progress meetings 3. Month-end Updated Schedule meetings Final for Execution 4

5 4. Other scheduling meetings as required by the Port 3.02 SCHEDULE REQUIREMENTS A. The Work shall be scheduled to show the completion of the Contract within the Completion Deadlines. B. Schedule start date shall be NTP1. C. The Design-Builder shall establish Project-specific calendars for the Work. At the pre-construction meeting, the Design-Builder shall provide a list of non-work days, which include Holidays and weather days. D. The Design-Builder shall submit tabular reports detailing the predecessors and successors and a report sorted by Total Float with every schedule submittal except the weekly Look-Ahead Schedule. E. All out of sequence logic conditions shall be corrected by adding new Activities and relationships as opposed to deleting Activities. Alternative approaches to correcting out of sequence Activities shall be submitted and Accepted by the Port prior to incorporating such corrections into the schedule. F. Activities shall not be deleted from the schedule. If the scope of Work associated with an Activity has been removed through a Change Order, the Design-Builder shall set the Activity s duration to zero, change the status to complete, and add DELETE to the description. G. The Design-Builder shall establish the Resource Dictionary. The Resource Dictionary shall include labor and equipment. Labor may be represented by work crews, labor classifications, and/or individual names. If utilizing work crews, the composition of each crew shall be detailed and included as an appendix to the Baseline Schedule narrative report. H. Failure to include any element of Work required for performance of this Contract in the preliminary 120-Day schedule, Baseline Schedule, the Updated Schedule, or Revised Baseline Schedule will not excuse the Design- Builder from completing Work required to achieve Completion Deadlines, notwithstanding Acceptance of schedule submittals. I. Schedule submittals shall not be used to notify the Port of Port-Caused Delays or to request additional Contract time. Formal notice and requests are required per applicable Contract provisions. The Port s Acceptance of a schedule that shows Work being performed later than an applicable Completion Deadline shall not be construed as Port s Approval to extend a Completion Deadline. Final for Execution 5

6 3.03 ACTIVITY REQUIREMENTS A. A Critical Path Activity shall be defined as a current Activity located on the longest path. Not more than 50% of Activities in the schedule can be critical or near critical. Near critical being defined as having a Float value of five (5) Days or less. The Design-Builder shall submit any proposed constraints in the schedule to the Port for Approval. B. Schedule Activities shall be cost and Resource-loaded. Resource loading shall include all major equipment and hours for each Resource. The Resource Dictionary shall be used to assign the required Resources to each Activity. There shall be no more than one driving Resource per Activity. All schedules shall be scheduled and Resource-leveled using the driving Resources. The Activity ID numbering, scope of Work, and descriptions of Activities shall remain the same as in the Baseline Schedule. C. The sum of all cost-loaded Activities shall equal the current Contract Price. D. Activity descriptions shall briefly convey scope and location of Work indicated. The description shall consist of a verb or work function (e.g.; form, pour, excavate), an object (e.g.; slab, footing), and area (e.g.; bent 200, northeast corner). E. The schedules shall reflect any Port activities such as review times and third party activities. F. Work Activities shall be subdivided to identify the staging of construction through the use of coding structure within P6. The coding structure can use either the Work Breakdown Structure (WBS) or Activity code structures and shall subdivide area, sub-area, discipline, stage, phase, and reference to sheet and spec sections. G. Work Activities shall have a duration of fifteen (15) Days or less, except for non-construction Activities such as management, design, procurement of materials and/or fabrication of equipment, unless otherwise Approved by the Port. No work Activity shall have an associated cost over $500,000, unless otherwise Approved by the Port. H. Should a Work Activity require more than fifteen (15) Days, it shall be subdivided into separate Work Activities. The Port reserves the right to require more detailed sequences of Work Activities as deemed necessary to review the schedule or monitor the Work. I. With the exception of the first (start) and the last (finish) Milestone Activities, all other Activities shall be logically tied to appropriate predecessors and successors. J. The Contract Milestone dates and any Port furnished equipment availability date, as described in the Contract Documents, shall be unique zero-duration Final for Execution 6

7 Activities containing corresponding dates and logic ties. These Activities shall be designed as either "start" or "finish" Milestones. Each Milestone Activity shall constrain its dependent Work. Calculation of constraint dates for Milestones shall assume NTP1 is given at day zero. K. Leads or lags shall not be used when the creation of an Activity will perform the same function (e.g. concrete cure time). Lag durations shall not have a negative value. The use of interrelation constraints such as leads and lags on Activities shall be explained in the Narrative Report and submitted to the Port. L. Use of mandatory start or finish constraints, start on, expected finish and zero Total Float constraints shall not be used in the Baseline Schedule, Revised Baseline Schedule, Recovery Schedule, or Updated Schedules without the Approval of the Port REQUIRED ACTIVITIES A. In addition to Work Activities, the following Activities and/or Milestones shall be included in the schedules: 1. Notice to Proceed. 2. Mobilization FILE STRUCTURE 3. Procurement of critical materials and equipment. 4. Submittals and submittal review periods. 5. Time related to furnishing products and materials with long lead times. 6. Lead time related to Utility services including, but not limited to, connection periods. 7. Completion Deadlines A. The coding structure can use either the Work Breakdown Structure (WBS) or Activity code structures and shall subdivide area, sub-area, discipline, stage, phase, responsibility (i.e., Port, Design-Builder, Subcontractor, or third parties such as Utility companies) and reference to sheet and spec sections. B. Activity codes, Activity IDs, Resource accounts, as well as some report formats shall be developed by the Design-Builder and Approved by the Port. C. The Design-Builder is responsible for establishing detailed Activities, Activity duration, Resource loading, and sequencing of Work in developing the schedule submittals as defined by this specification. Final for Execution 7

8 D. Design-Builder shall maintain Activity codes, Resource accounts, Activity ID codes, and report specifications on schedule submittals WEATHER Ja Fe Ma Ap Ma Ju Ju Au Se Oc No De Tota n 3 b 3 r 2 r 2 y 1 n 0 l 0 g 0 p 0 t 1 v 1 c 2 l 15 A. Delete special condition SC-9 Weather Delays Caused by Rain in its entirety. B. The Design-Builder shall build into the schedule sufficient time for seasonally anticipated weather delays. A minimum of 15 weather delay days per year shall be allocated in the Baseline Schedule for anticipated weather delays. The Design-Builder shall allocate anticipated weather delay days in one of the following options: 1. Allocate on a monthly basis the number of weather delay days anticipated to those Activities in the month most likely to be impacted by weather. The Design-Builder shall clearly define all Activities with increased durations due to anticipated weather delays within the Baseline Schedule narrative. When the number of actual weather delay days exceeds the amount originally anticipated in a month, weather delay days shall be re-allocated from future months to account for the difference. Any unused anticipated weather delay days in a month shall either be re-allocated into future months, or put into a separate Activity in accordance with Option 2 below for future use if necessary. 2. Add a separate Activity for the anticipated weather delay days as the final schedule Activity. The weather Activity shall be on the Critical Path, a successor to the last Work Activity, and a predecessor to the Contract Completion Date. When an actual weather delay occurs, the delay is incorporated into the affected Critical Path Activities, and the anticipated weather delay day Activity is reduced by an equal amount. C. The determination of a qualified weather delay will be a function of locally prevailing conditions at the Site. To qualify as a weather delay, the adverse weather must impact a Critical Path element of the Work and the duration must be in excess of four (4) hours. D. On Days where adverse weather is encountered, the Design-Builder shall submit a list of all Activities that were impacted, and identify which Activities were on the Critical Path. This information shall be submitted at the end of the adverse weather day for the Port s review and Approval to incorporate into the schedule as a weather delay. Final for Execution 8

9 E. When the sum of all weather delays exceeds the total anticipated weather delay days, the Design-Builder may submit a Request for Change Order to extend a Completion Deadline per Book 1, Section TOTAL FLOAT A. Total Float is not for exclusive use or benefit of either the Port or the Design- Builder, but is an expiring Resource available to both parties on a nondiscriminatory basis. Either party is entitled to use the Float on a first come first serve basis. B. In the event Delays or disruptions impact an already Negative Float path, the Design-Builder shall not receive a time extension unless, and until, the Activity with highest Negative Float is driven even further negative. C. Pursuant to Float sharing requirements of these provisions, use of Floatsuppression techniques such as, but not limited to, preferential sequencing or logic, special lead/lag logic restraints, and extended Activity times or durations is prohibited. Use of Float time disclosed or implied by use of alternate Float-suppression techniques shall be shared to the proportionate benefit of the Port and the Design-Builder. The use of any network technique solely for the purpose of suppressing Float will be cause for rejection of schedule submittal TIME IMPACT ANALYSIS A. The Design-Builder shall submit to the Port a stand-alone fragmented network schedule (fragnet), excluding all unaffected Activities, if the latest forecasted Completion Deadline is, or will be, changed by Change Order or Port-Caused Delay. Each fragnet submitted shall be provided in P6 format on compact disc. B. Submittal shall show Activities affected, date(s) Delay occurred, or impacted productivity rates, and unmitigated impact(s) to schedule resulting from Delay. C. The Design-Builder shall submit, at the Port s request, a similar fragnet showing the Design-Builder s plan to mitigate Delay and subsequent impact(s) to schedule. Submission of such fragnets does not constitute permission to proceed with the plan. D. The Design-Builder shall provide written narrative describing circumstances that caused the Delay, and methodology used to determine the extent of the Delay. E. Activities of revised portion(s) of schedule shall be properly connected to, and constrained by, previously existing predecessor and successor Activities, as applicable. Band impacted Activities in separate networks (fragnets), indicating specific Delays, and submit to the Port for review. Final for Execution 9

10 F. The Design-Builder shall combine the reviewed and Accepted fragnets into the Updated Schedule. The Port will review aggregate impact to the Critical Path NARRATIVES A. Narratives prepared by the Design-Builder shall include sufficient detail to explain the specific submittal. B. The preliminary 120-Day schedule narrative shall address the Design- Builder s approach to the Work during the first 120 Days following NTP1. C. The Baseline Schedule narrative shall address the Design-Builder s approach to executing the scope of Work including procurement, long lead items, third party coordination, equipment, materials, Site access, interrelation Activity constraints such as leads and lags, potential problem areas, weather-sensitive Activities, submittals, and permits throughout the duration of the Project. D. The Updated Schedule narratives shall address the following: 1. The narrative shall state Work that is actually completed and reflect progress along Critical Path in terms of Days ahead of or behind allowable dates. 2. If the Updated Schedule indicates an actual or potential Delay to the Completion Deadlines, the Design-Builder shall identify the causes of Delay. The Design-Builder s narrative shall also provide an explanation of Work affected and proposed corrective action to meet Completion Deadlines involved or to mitigate potential Delays or disruptions. 3. The narrative shall discuss added Change Order Work. 4. The Updated Schedule narrative shall address the basis for the following changes subsequent to the latest Updated Schedule: scope, Activity, logic, Activity duration, calendars, and Resources. E. The fragnet narratives shall address, at a minimum, the circumstances that caused Delay and the methodology used to determine extent of Delay. F. The final as-built schedule narrative shall address the basis for all logic or Activity duration changes from the Baseline Schedule or the latest Revised Baseline Schedule to the as-built schedule SCHEDULE TYPES A. Preliminary 120-Day Schedule: 1. The Data Date of the schedule shall be the date of NTP1. Final for Execution 10

11 2. The preliminary 120-Day schedule shall contain all Work that will occur during the first 120 Days following NTP1. 3. Prior to Acceptance of the preliminary 120-Day schedule, the Design- Builder shall be prepared to review and discuss the schedule and sequence of operations including: cost and Resource-loading methodology; as-built schedule development and maintenance; procedures of updating and revisions; and required submittals as specified in these provisions. The Design-Builder shall describe the Design-Builder's approach for meeting required Completion Deadlines, as specified by the Contract. As a minimum, the Design- Builder shall include the following: basis and assumptions used in preparing submittal (such as crew sizes, equipment requirements, anticipated delivery dates, etc), constraints, Critical Path Activities, production rates, Activities requiring overtime and/or additional shifts, Activities containing time contingencies for impacts to be expected, potential problem areas, permits, coordination, and long lead delivery items (greater than 30 Days from order to delivery). B. Baseline Schedule: 1. The Baseline Schedule shall contain the Design-Builder's detailed Activities and sequencing for all Work included in this Contract from NTP1 through Final Acceptance. The Design-Builder shall assign unique Activity identification for each detailed Activity. It is essential that the Baseline Schedule present a clear understanding of the staging of construction. This shall be reflected in the coding structure in the schedule. The Design-Builder shall, unless directed otherwise by the Port, use the Baseline Schedule as target for required comparisons to the current updates in tabular reports, bar charts, physical progress curves, or any other comparisons requested by the Port. 2. The Baseline Schedule Activities shall indicate the Design-Builder's best estimate for original durations, early dates, late dates, logic ties, constraint dates, and Total Float. Activities shall be scheduled in the sequence the Design-Builder intends to perform the Work. 3. The Baseline Schedule shall contain the Activity sequence for major material and equipment procurement, including submittal preparation, reviews by the Port and others, fabrication, and delivery. Procurement items that may contain multiple submittals occurring at different times shall be divided into separate Activity sequences that can be tracked on an individual basis. 4. Activities shall include the Contract deliverables, such as submittal and Approval and/or Acceptance (as applicable) of design documents, permit applications, material samples, shop drawings, working drawings, resumes, inspection and test plans, safety and security plans. Activities that may affect progress shall be reflected, as well as those Final for Execution 11

12 of affected Utility companies and other similarly involved third parties. Any such Activities set forth in the Contract Documents shall be reflected on the Baseline Schedule. 5. Once the Baseline Schedule is Accepted by the Port, it shall become the basis for the Updated Schedule. C. Updated Schedule: 1. The Design-Builder shall prepare a duplicate of the Accepted Baseline Schedule. The original Accepted Baseline Schedule shall be archived by the Design-Builder, and the duplicate schedule shall be used to prepare the first Updated Schedule. 2. On a monthly basis, the Updated Schedule shall be submitted with the Data Date agreed to by the Port and the Design-Builder. 3. The schedule shall be updated to include all Work and progress up to and including the Data Date. 4. Schedules shall be calculated using the progress override option as opposed to the retained logic option. 5. The Updated Schedule shall detail progress based on actual start and finish dates for Activities either in progress or completed, and the percent of Work completed to date on each Activity started but not yet completed. 6. The Design-Builder shall respond to all comments or questions from the Port s month end review within five (5) Days. The Design-Builder shall also include these responses in the current Updated Schedule narrative. 7. The Design-Builder shall obtain the Port's Approval before making deviations in logic and Activity durations between the Updated Schedule and the Baseline Schedule or between the Updated Schedule and the Revised Baseline Schedule. 8. The Design-Builder and Design-Builder s scheduler shall attend a month-end Updated Schedule meeting to be held seven (7) Days prior to the month-end Data Date. At these meetings, the Design-Builder must be able to discuss the Project status using the scheduling software. This will include actual start and actual finish dates for Activities either in progress or completed, remaining durations of Activities in progress, percent complete of Resource-loaded Activities, logic changes, new or deleted Activities, and new Change Orders. 9. The Design-Builder shall submit to the Port a Recovery Schedule at the sole expense of the Design-Builder if the Design-Builder s Final for Execution 12

13 Updated Schedule indicates Negative Float and there are no pending Requests for Change Order to extend a Completion Deadline. 10. The Updated Schedule will be subject to rejection and re-submittal if it no longer appears to represent the actual execution of Work. 11. Once the Updated Schedule is Accepted by the Port, it shall become the basis for the next Updated Schedule. The Design-Builder shall prepare a duplicate of the current Accepted Updated Schedule. The original Accepted Updated Schedule shall be archived by the Design- Builder, and the duplicate schedule shall be used to prepare the next month s Updated Schedule. D. Look-Ahead Schedule 1. On a weekly basis, the Design-Builder shall submit from the current Accepted Baseline Schedule or Updated Schedule, using the Approved scheduling software; a Look-Ahead Schedule covering actual Work accomplished during previous week and planned Work for current and subsequent two weeks. 2. The Look-Ahead Schedule shall include Activity ID numbers and indicate which Activities are on the Critical Path. E. Revised Baseline Schedule: 1. The original Baseline Schedule shall only be revised upon Approval of the Port. 2. The Design-Builder shall, unless directed otherwise by the Port, use the Revised Baseline Schedule as the target for required comparisons in tabular reports, bar charts, and cash flow and physical progress curves, or any other comparisons requested by the Port. 3. The Design-Builder shall use the Revised Baseline Schedule for the purposes of subsequent Updated Schedules once the Revised Baseline Schedule has been Accepted by the Port. F. As-Built Schedule: 1. Submit a final as-built schedule covering all Work performed under this Contract within thirty (30) Days after Substantial Completion of the Work. 2. The as-built schedule specified herein shall be based upon the actual dates, Activity durations and logic relationships as they occurred without leads or lags to reflect as-built construction sequencing. The as-built schedule shall have a Data Date as of the date of Notice to Proceed. Final for Execution 13

14 3.11 SCHEDULE REVIEW AND COMPLIANCE A. The Port s review of the schedule submittals shall not relieve the Design- Builder from the responsibility for any variation from the requirements of the Contract Documents. Nor shall any Approval by the Port relieve the Design- Builder from responsibility for compliance with any provision of the Contract. B. If, in the opinion of the Port, the schedule (1) does not accurately reflect the Design-Builder s actual or anticipated progress or work plan or, (2) cannot be used to effectively evaluate the Design-Builder s progress or, (3) is not in compliance with the provisions contained herein and other parts of the Contract, it will be returned to the Design-Builder for corrections and clarification. The Design-Builder shall make the necessary corrections and resubmit, or shall respond in detail to the Port s comments with reasonable explanation why such corrections or clarifications should not be required. Final for Execution 14