109 CRITICAL PATH METHOD PROJECT SCHEDULE

From SHA MediaWiki
Jump to navigation Jump to search
This is not a legal document. Please see disclaimer for more information.
109.01 DESCRIPTION
The Administration will classify projects by complexity and cost to determine the Project Schedule requirements. Project Classification Type B shall apply unless designated differently in the Invitation for Bids (IFB). Project classifications are:
Type A—Bar Chart (BC) Schedule,
Type B—Critical Path Method (CPM) Schedule for Typical Projects, or
Type C—CPM Schedule for Complex Projects.
CPM Schedule techniques used in the Project Schedule to monitor the work specified in the Contract documents will use retained logic. The Administration will use the Project Schedule as a tool for monitoring progress and evaluating any schedule impact from change orders during the Project duration.
See GP-8.04 PROGRESS SCHEDULE for additional provisions regarding the submission and the failure to adhere to the project progress schedule requirements.
109.01.01 Definitions
Activity - A distinct component of work performed during the project with estimated duration, estimated cost, and estimated resource requirements. Schedule activities are connected to other activities or milestones with logical relationships and are decomposed from work packages.
Actual Start Date (AS) - At the activity level, the Actual Start date represents the point in time that meaningful work actually started on an activity.
Actual Finish Date (AF) - At the activity level, the Actual Finish date represents the point in time that work actually ended on an activity so that follow-on work could start.
Calendar Day - A Calendar Day consists of every day shown on the calendar, beginning and ending at midnight.
Completion Date -
(a) Substantial Completion Date
(1)The date specified in the Contract Documents, subject to revision resulting from an authorized time adjustment, or the date the Administration could have or did take possession of all constructed work as it can be safely and effectively used for the intended purpose without delays, disruptions, or other impediments to the end user; or
(2)The date time charges will be suspended (subject to reinstitution upon Contractor failure to achieve Final Completion Date); or
(3)The date the Engineer determines the Administration will issue a Partial Acceptance for Maintenance subject to requirements of GP-5.13(a).
(b) Final Completion Date
(1)The date specified in the Contract Documents, subject to revision resulting from an authorized time adjustment; or the date the Contractor has completed all physical work within the project limits, including any punch-list items, all warranty and landscaping requirements, and any Contractually required submissions (e.g., as-built plans);
(2)The date any reinstitution of time charges terminates; and
(3)The date the Engineer determines the Administration will issue a Final Acceptance subject to the requirements of GP-5.13(b) and (c).
Critical Path - The sequence of activities that determines the longest duration for the project when the longest path has zero or less total float. At this point, the longest path becomes the critical path.
Critical Path Method (CPM) Schedule - Project modeling technique to construct a project that uses activities, durations, and dependencies between activities to determine the longest path to the Substantial Completion Date. Dependencies are based on technical relationships and preferential activity sequence.
Data Date - The day after the date through which a schedule is current. Everything occurring earlier than the data date is “as-built” and everything on or after the data date is “planned.”
Float - Float is the amount of time between when an activity “can start or finish” and when an activity “must start or finish” to complete the project within the specified Contract Time. Float is a shared commodity for the use of the Administration and the Contractor and is not for the exclusive use or benefit of either party. Both parties have the full use of the float until depleted.
Joint Review Conference (JRC) - A JRC is a meeting in person or by phone, where representatives from the Administration and the Contractor discuss comments and questions regarding schedules.
Longest Path - The sequence of interdependent activities that determine the minimum duration of a project.
Milestone - An activity with zero duration that typically represents a significant event, such as the beginning and end of the project, milestones set forth in the Contract, construction stages, a major work package, any Contract interim time-related clauses, Substantial Completion Date, and Final Completion Date.
Project Classification Type - A determination by the Administration that establishes the type of schedule requirements that apply to a Contract based on Contract complexity, cost, and any special requirements.
Project Schedule - A project Schedule as defined by this Specification.
Initial Project Schedule - As specified in 109.03.01;
Updated Project Schedule - As specified in 109.03.02;
Revised Project Schedule - As specified in 109.03.03.
Scheduling Representative - The person primarily responsible for development and maintenance of the CPM schedule for the Contractor. The Contractor shall designate an experienced scheduling representative as part of the written narrative of the Initial Critical Path Method (ICPM) Project Schedule.
Schedule Time Impact Analysis - A process of analyzing a schedule to determine the impact on the project schedule of a change in the Work or conditions, or of a delay event, for the purposes of quantifying and apportioning the effects to the party responsible for the impact.
Start Date -
Projected Start Date - The date when the NTP or a limited NTP is to be issued as advertised by the Administration, which is entered as a Start milestone activity in the schedule;
Project Actual Start Date - The date that field activities begin as stipulated in the NTP (or limited NTP), issued in accordance with GP-8.02 and TC-5.02, as allowed by requirements found in the Contract, and designated as a start milestone in the first Update schedule.
Time Impact Analysis - A forward-looking prospective schedule impact analysis method that adds a modeled delay to the current schedule (where all activities are updated to immediately prior to the time of a change or delay) to determine the possible time impact of the change or delay as it affects the Contract Substantial Completion Date.
Work Breakdown Structure (WBS) - A deliverable oriented hierarchical decomposition of work to be executed for the project. The structure is to be determined by the Contractor. The Contractor may elect to use the WBS to track resources and costs within each work element.
Work Day - Every day except Saturdays, Sundays, State holidays, adverse weather days or other weekdays where Work is restricted as identified explicitly in the Contract Documents.
Written Narrative (WN) - A descriptive report submitted with the initial Project Schedule or ICPM and each Project Schedule update.
109.02 MATERIALS
Not Applicable.
109.03 CONSTRUCTION
109.03.01 Initial Project Schedule Prepare and submit the initial BC (IBC) Schedule for Type A Projects; or an initial CPM (ICPM) Schedule for Type B and Type C Projects; or the elected preliminary ICPM for a Type C Project; and the WN within 20 days of Notice of Award (NOA).
No work may start on the Project until the IBC or ICPM Schedule is accepted or unless otherwise directed in writing by the Engineer.
109.03.01.01 Initial Project Schedule - Type A Project - Requirements. Prepare an IBC Schedule as a bar chart, using spreadsheets, CPM scheduling software, or other means. The IBC Schedule shall include the requirements of paragraphs (a)-(d) and be submitted according to paragraph (e).
(a) Milestones. The IBC Schedule shall include the following major milestones:
(1) Notice to Proceed (NTP).
(2) Substantial Completion Date.
(3) Final Completion Date.
The IBC Schedule may include other milestones for planning work including major interim Contract requirements, starting or ending of Phases of Construction, or other milestones necessary to monitor the work.
(b) Project Duration. The overall project schedule duration used in the IBC Schedule shall be from the anticipated NTP date through the Contract Substantial Completion Date as identified in the IFB.
(c) Activities. Activity original durations shall be limited to a reasonable duration necessary to complete the work required. The Administration reserves the right to specify the number of activities and to require additional breakdown of the activities at any time. Activities shall be listed in chronological order of the proposed start date and include Activity ID numbers for referencing purposes.
(d) Written Narrative. Prepare and submit a unique WN with the IBC Schedule. The WN shall explain the Contractor’s plan to construct the project in accordance with the Contract requirements. The WN shall include, at a minimum, the following elements:
(1) Sequence of Work. Explain the sequence of work, project phasing, and the longest path as planned for the project including interim completion dates, if any, required by Contract;
(2) Crew Composition. Explain the crew composition, including labor and equipment, as anticipated to fulfill activities in the schedule network; and
(3) Access Restriction. Explain any restrictions on access to the work including: coordination with other entities, coordination with all utility companies, coordination with other public contractors, land access requirements, environmental permit requirements, special non-work days or periods, weather restrictions expected as considered in the planning of the schedule, and planned winter shutdowns.
(e) Submittal Requirements. Submit the IBC Schedule to the office designated by the Procurement Officer in the NTP document, with a copy to the on-site Engineer, to include the WN and a printed activity bar chart on ledger size paper. Submit electronic files in native file format, if used, along with the printed IPS graphic and WN.
109.03.01.02 Initial CPM Project Schedule - Type B Project - Requirements. Prepare an Initial CPM (ICPM) Schedule using acceptable scheduling software that is capable of export to compatible version of Oracle Primavera used by the Administration’s reviewer, in. xer format.
CPM schedule techniques used in the Project Schedule to monitor the work specified in the Contract documents will comply with the precedence diagramming method using retained logic.
The ICPM Schedule shall indicate work activities and major material submittals required to complete the project as shown in the Contract plans. The schedule shall include all activities of subcontractors, utilities, railroads, the Administration, and all other parties associated with the construction of the Project.
All work including, but not limited to, submittals, major procurement, delivery, and construction activities shall be included. All activities reasonably necessary to plan the scope of work shown in the Contract plans shall be included. Concurrent work by others, including any indicated in the Contract Utilities Statement, shall also be included. The ICPM schedule shall be based upon the entirety of the Contract Documents.
The ICPM Schedule shall include the requirements of paragraphs (a)-(g) and be submitted in accordance with paragraph (h).
(a) Milestones. Include the following major milestones in the ICPM Schedule:
(1) NOA.
(2) NTP.
(3) Substantial Completion Date.
(4) Final Completion Date.
The ICPM Schedule may include other milestones for planning work including major interim Contract requirements, starting or ending of Phases of Construction, or other milestones necessary to monitor the work.
(b) Project Duration. Include time from Bid Opening to NTP in the ICPM Schedule as 70 days to allow time for administrative Contract execution requirements. Requests for variation of the 70-day period shall be submitted to the administrative office in advance of the ICPM Schedule submittal.
The overall project schedule duration used in the ICPM Schedule shall be from the anticipated NTP date through the Contract Substantial Completion Date as identified in the IFB.
(c) Activity Codes and Work Breakdown Structure. Include activity codes for organizing activities in the schedule. The minimum activity codes shall be:
Project Area (Location of Work).
Project Phase (Construction Phase for Project, if applicable).
Responsibility (e.g., SHA, Contractor, Subcontractor, Utility, Third Party).
Crew Type (defined in WN by trade for Project).
Other activity codes used for planning and organizing activities should be explained in the WN.
Include a work breakdown structure (WBS) for planning and organizing project activities. Explain the WBS in the WN.
(d) Activities. Activities should include tasks necessary to perform the scope of project work and milestones defined in various specifications. Task activities shall include definable work packages that require manpower, materials, and/or equipment to perform.
Activities may include periods of wait time as defined in the specifications for various purposes and milestones. Original durations of tasks shall be limited to a reasonable duration necessary to complete the work required.
Activities with durations of more than 10 work days shall be explained in the narrative for each occurrence.
Third party or Administration submittal review activities shall be included with durations according to relevant specifications, but not be less than 30 days.
The Administration reserves the right to specify the number of activities and to require additional breakdown of the activities at any time.
(e) Relationships and Constraints. Relationships should generally guide the sequence of work on the project by Finish-to-Start type relationships. Explain the use of other type relationships in the WN.
Negative lag shall not be used, and the use of other lag types shall be explained in the WN. Each activity shall have at least one predecessor relationship and one successor relationship, except Milestones, and the first and last activity in the network.
Constraints shall be used to impose restrictions on an activity if defined in the Contract and shall not be used for other reasons.
(f) Calendars. Calendars used in the ICPM Schedule network shall be designated as Project Calendars by a unique naming system. The schedule shall include a Calendar Day calendar and a Work Day calendar. Other Specialty Calendars (for weather sensitive work, permit stream restrictions, etc.) may be used, if necessary to plan the project.
The Work Day calendar shall include restrictions preventing work as defined in the Contract requirements. Work day restrictions include as a minimum weekend, holidays, day before and day after holidays, and an estimate of anticipated bad weather days, with the residual work days as indicated in the table below.
Include estimates for expected work days in the work day calendar as per the minimum days indicated in the following table unless the table is specifically modified in the IFB.
Table 1
Western MD
District 6
Central MD
District 3, 4, 5, 7
Eastern MD
District 1, 2
January 3 8 5
February 3 8 7
March 10 13 11
April 15 17 15
May 15 17 14
June 18 18 19
July 18 17 17
August 18 19 18
September 18 18 18
October 18 17 18
November 10 13 13
December 6 10 9
Total 152 177 164
Non-work days included in Specialty Calendars shall be explained in the WN. Activities that are temperature sensitive (e.g., placement of hot mix asphalt, concrete placement/curing, painting/staining, plantings, vegetation establishment, temporary/permanent roadway markings) shall be assigned to specialty calendars that are consistent with their calendar imposed, seasonal temperature restrictions for the regional location of the work and shall be prohibited during the time periods that may be explicitly identified in the Contract documents. Reasoning for any exceptions shall be noted in the WN.
(g) Written Narrative. Submit a complete and unique WN with the ICPM Schedule. The WN shall explain the Contractor’s plan to construct the project according to Contract requirements without reference to the schedule file or activity chart. Include, at a minimum, the following elements identified as separate paragraphs:
(1) Sequence of Work. Explain the sequence of work, project phasing, and the longest path as planned for the project including interim completion dates, if any, required by Contract or by Contractor’s choice;
(2) Access Restrictions. Explain any restrictions on access to the work including: coordination with other entities, coordination with all utility companies, coordination with other public contractors, environmental permit requirements, special non-work days or periods, anticipated weather restrictions, and planned winter shutdowns;
(3) Modification to Specification. Explain any exceptions or additions to the requirements stated in section 109.03.01.02, related to relationships, durations, activity codes, constraints, milestones, or calendars used in the ICPM Schedule network;
(4) Crew Composition. Explain the crew composition, including labor and equipment, as anticipated to fulfill the crew activity code used in the schedule network;
(5) Unique Schedule Features. Explain unique schedule features necessary to understand the construction plan represented by the schedule.
(6) Schedule Representatives. Designate a Schedule Representative with at least five years of experience for the Project. The Contractor may replace the schedule representative at any time by designating the change in the WN for any schedule submittal. The Administration may request a replacement schedule representative be designated for any project where the Administration deems it necessary.
Include a PDF file as an appendix for printing the activity chart for all activities. The PDF print size shall be 11 in. x 17 in. and organized by Phase and Area for the project.
(h) Submittal Requirements. Submit the ICPM Schedule to the office designated by the Procurement Officer in the NTP document, with a copy to the on-site Engineer. The submittal shall include an electronic schedule file in native format, the WN, a printed schedule activity chart on ledger size paper (see 109.03.01.02(g)), and all other items as detailed above for a Type B Project.
109.03.01.03 Initial CPM Project Schedule - Type C Project - Requirements. Prepare an ICPM Schedule that meets all the requirements of section 109.03.01.02 including paragraphs (a) to (g), and paragraph (a) below. A Preliminary ICPM Schedule meeting the requirements of paragraph (b) below may be submitted in advance of the ICPM.
CPM Schedule techniques used in the Project Schedule to monitor the work specified in the Contract documents will comply with the precedence diagramming method using retained logic.
(a) Resources. Prepare a project specific resource dictionary and include assignment of labor and equipment resources to each construction activity. Assign resources through the resource tracking module of the scheduling software.
Provide resource labor names by labor classification (skilled, unskilled, foreman), and resource equipment names (loader, backhoe, paver). Additional resource assignments for Contract pay item numbers (e.g., 3001, 3002) may be included.
Administrative activities, such as submittal preparation and review, and material fabrication for long lead items, are exempted from resource loading. Third party activities not under the Contractor’s control, concrete curing activities, or other Contract required wait periods are exempted from resource loading.
Explain in the WN any resource limitations that may affect planning the project. Resource related relationships used to sequence activities should be explained in the WN. The Administration reserves the right to request modification to resource relationships, if jointly determined to be in the best interest of the project.
(b) Preliminary ICPM Schedule. A Preliminary ICPM Schedule, although not required, may be submitted prior to submission of the full ICPM Schedule to expedite the start of project Work. The Preliminary ICPM Schedule shall include all the requirements of section 109.03.01.02, paragraphs (a) to (g), and paragraph (a) above, except as noted below:
(1) Administrative activities may include only submittals or other project requirements planned for the first 90 days of project time;
(2) Activities planned for the first 90 days of project time shall be detailed and complete. Activities beyond 90 days may be planned on a summary level that uses all Contract Time through the required Substantial Completion Date;
(3) Organization and composition of the Preliminary ICPM Schedule shall be sufficient to relate the Contractor’s overall project plan for construction to complete the scope of work required by the Contract within the Contract Time;
The Administration will review the Preliminary ICPM Schedule within 10 business days. If the Preliminary ICPM Schedule is conditionally accepted by the administering office, project Work may begin but can only continue through a 90-day period commencing with the NTP date.
The full ICPM Schedule meeting all the requirements of section 109.03.01.02 must be submitted and accepted by the administering office within that 90-day period. Failure to achieve acceptance of the complete ICPM Schedule will result in a suspension of Contract work and suspension of any pending or future Contract-wide progress payment(s). Such action may not be used as grounds for filing a request for equitable adjustment.
(c) Substantial Requirements. Submit the Preliminary ICPM Schedule to the office designated by the Procurement Officer in the NTP document, with a copy to the on-site Engineer. The submittal shall include an electronic schedule file in native format, the WN, a printed schedule activity chart on ledger size paper (see 109.03.01.02(g)), and all other items as detailed above for a Type C Project.
109.03.01.04 Review and Acceptance of the IBC or ICPM Schedule. The following shall apply to Type A, B, and C projects.
The administrating office may allow Contract work to start after submission of an IBC/ICPM Schedule but prior to the schedule acceptance if there is reasonable benefit to the project. However, all work and any pending or future Contract-wide progress payments will be withheld if the IBC/ICPM Schedule is not accepted within 90 days of the NTP.
The Administration will designate the schedule status of the IBC/ICPM Schedule within 20 days after submittal as follows.
Reviewed and Accepted. The IBC/ICPM Schedule is accepted as submitted and becomes the BC Schedule of Record (BCR), or CPM Schedule of Record (CPMR) - Project work may begin;
Accepted as Noted. The IBC/ICPM Schedule comments must be addressed in the first progress update - Project work may begin;
Conditionally Accepted. The IBC/ICPM Schedule must be re-submitted - Project work may begin;
Revised and Resubmit. The IBC/ICPM Schedule must be re-submitted - No project work may begin.
If necessary, a JRC will be convened to make corrections and adjustments to the proposed IBC/ICPM Schedule. If a revision is necessary due to the JRC or Administration’s review, submit the proposed revision within seven days after receiving the Administration’s review comments, or within seven days after the date of the JRC, whichever is the latest.
The Revised IBC/ICPM Schedule will be re-designated within seven days after receipt. Any delay caused by the Administration’s response to the Revised IBCM/ICPM Schedule may not be used as grounds for filing a request for equitable adjustment.
Project delay due to failure to submit or resubmit the IBCM/ICPM Schedule as required and the withholding of payment due to that failure shall not be used as grounds for filing a request for equitable adjustment.
109.03.02 Project Schedule Update. Submit Monthly Project Schedule Updates within seven days of the mutually agreed upon data date for the Project, unless the Administration agrees in writing to a different submittal schedule. Discuss the Project Schedule Update during the project progress meetings, or other meetings, to agree on progress through the data date. Submit Project Schedule Updates of the BCR/CPMR regardless of receiving comments on previous Schedule Updates or Schedule Revisions.
Submit updates as agreed until the day after Substantial Completion of the project.
109.03.02.01 Project Schedule Updates - Type A Project – Requirements. Submit monthly updates to the BCR to indicate progress made to date.
(a) Progress. The Contractor’s Scheduling Representative and the Administration’s on-site Engineer will meet to review, mutually agree to, and sign-off on the information required to update the schedule (AS and AF dates). For activities in progress, the Schedule Representative shall estimate the remaining duration and percent of completion. The Engineer may suggest a differing estimate of completion. The agreements and comments made by the Engineer at the monthly review meeting shall be included as part of the WN for the update submittal.
(b) Written Narative. A complete WN shall be submitted with the Project Schedule Update. The WN shall describe at a minimum, the following elements:
(1) Progress. Explain the progress made on activities planned for the update period;
(2) Delays or Potential Delays. Explain any delays encountered or potential delays that may affect work in the future (e.g., differing site conditions); this requirement does not relieve the Contractor of the notice provisions found in other various portions of the Contract;
(3) Resource Revisions. Explain any crew composition changes in labor or equipment for the next update period to achieve the planned schedule network;
(4) Longest Path. Explain the critical path for the next update period and, if different, why the critical path is different.
Include a PDF file as an appendix for printing the activity chart for all activities. The PDF print size shall be 11 in. x 17 in. and organized by Phase and Area for the project.
109.03.02.02 Project Schedule Updates - Type B and Type C Project – Requirements. Submit monthly Project Schedule Updates to the CPMR describing progress made to date. Submit a WN discussing issues or delays encountered during the update period. There should be no revisions to the schedule other than to show progress accomplished.
(a) Progress. The Contractor’s Scheduling Representative and the Administration’s on-site Engineer will meet to review, mutually agree to, and sign-off on the information required to update the schedule (AS and AF dates). For activities in progress, the Schedule Representative may estimate remaining duration and percent of completion. The Engineer may offer a differing estimate of completion. The agreements and comments made by the Engineer at the monthly review meeting shall be included as part of the WN for the update submittal.
Update the schedule by inserting the agreed AS and AF dates for any activities that started and/or finished during the update period. In addition, the remaining duration of activities in progress shall be updated as agreed by converting the remaining duration to a percentage of the original duration and update the duration percent complete or linked percent complete.
Remaining Durations that exceed the original duration of the activity should be explained in the WN.
Expected Finish dates may only be used on activities for submittal reviews, fabrication of long lead materials, third party work that impacts Contract work, and utility relocations by third parties.
(b) Written Narrative. A complete WN shall be submitted with the Project Schedule Update. The WN shall be unique to each schedule update and include, at a minimum, the following elements:
(1) Progress. Explain the progress made on activities planned for the update period;
(2) Delays or Potential Delays. Explain any delays encountered or potential delays that may affect work in the future (e.g., differing site conditions); this requirement does not relieve the Contractor of the notice provisions found in other various portions of the Contract;
(3) Scope Revisions. Explain any changes in scope or differing site conditions encountered during the update period;
(4) Resource Revisions. Explain any crew composition changes in labor or equipment for the next update period to achieve the planned schedule network; and
(5) Longest Path. Explain the current critical path for the next update period and, if different, why the critical path is different.
Include a PDF file as an appendix for printing the activity chart for all activities. The PDF print size shall be 11 in. x 17 in. and organized by Phase and Area for the project.
(c) Out-of-Sequence Progress. Explain in the WN the circumstances that caused performance of work out-of-sequence. Out-of-sequence activities that do not resolve within 30 days of starting shall be corrected through a schedule revision submitted as specified in 109.03.03.
109.03.02.03 Review and Acceptance of the Project Schedule Updates. The Administration may withhold payment for the entire Contract if Project Schedule Updates are not submitted as required. Upon request, the Contractor shall concurrently submit updates directly to the Administration and the Administration’s designated schedule reviewer. Project delay due to failure to submit the updates as required and the withholding of Contract-wide progress payment(s) due to that failure shall not be used as grounds for filing a request for equitable adjustment.
The Administration will respond to project Schedule Updates within 20 days after receipt as follows:
(a) Reviewed and Accepted – The Schedule Update is accepted as submitted and becomes the new BCM Schedule of Record (BCR) or new CPM Schedule of Record (CPMR); or
(b) Accepted as Noted – The Schedule Update comments must be addressed in the next progress update; or
(c) Revise and Resubmit – The Schedule Update must be revised and re-submitted.
Any delay in response by the Administration is not a reason to not comply with future update submittal requirements.
The Administration may request a schedule revision (recovery schedule) if the calculated Substantial Completion Date of the project schedule update is more than 30 days beyond the Contract Substantial Completion Date. The recovery schedule shall meet all the requirements of a schedule revision shown in section 109.03.03. The Contractor may request a time extension, when warranted in accordance with this specification, in lieu of a recovery schedule.
Failure to submit a recovery schedule, or request a time extension, compliant with timeliness requirements in the Contract may be cause for denial of a time extension.
109.03.03 Project Schedule Revisions. The Contractor may submit project Schedule Revisions when changes in the plan for construction are due to changes directed by the Administration, or due to changes in the Contractor’s approach to construction. Schedule Revisions may be submitted at any time.
Schedule Revision submittals made with Project Schedule Updates shall include all progress information of the schedule update and include a separate WN meeting the requirements below.
109.03.03.01 Project Schedule Revisions – Type A Project – Requirements. Submit the proposed revision in the same format and with the same requirements used for the IBC Schedule.
(a) Revisions. Discuss any proposed revision to the BCR verbally with the Administration. Revisions are defined as one or more of the following:
(1) A change to revise planning.
(2) A change to revise duration of an activity.
(3) A change to add or delete work due to changed requirements.
(b) Written Narrative. Submit a complete and unique WN with the proposed Project Schedule Revision. The WN shall explain the reasons for the revision and include the following elements:
(1) Describe the reason for the schedule revision;
(2) Describe the new longest path;
(3) Explain any changes to the method or manner of work;
(4) Explain any changes in labor or equipment due to deletion or addition of work; and
(5) Explain any acceleration of the work.
Include a PDF file as an appendix for printing the activity chart for all activities. The PDF print size shall be 11 in. x 17 in. and organized by Phase and Area for the project.
109.03.03.02 Project Schedule Revisions –Type B, and Type C Projects – Requirements. Submit the proposed revision in the same format and with the same requirements used for the ICPM Schedule.
(a) Revisions. Discuss any proposed revision to the CPMR verbally with the Administration. Revisions are defined as one or more of the following:
(1) A change in the logic of the schedule due to revised planning.
(2) The deletion or addition of an activity.
(3) Change to resources or assignment of resources.
(4) A change to, addition of, or deletion of a time constraint.
(5) A change to, addition of, or deletion of an activity code assignment or work breakdown structure.
(b) Written Narrative. A complete and unique WN shall be submitted with the Project Schedule Revision. The WN shall be a stand-alone document that explains the reasons for the revision. The WN shall include, at a minimum, the following elements:
(1) Describe the reason for schedule revision;
(2) Describe the new longest path;
(3) Explain any changes to method or manner of work;
(4) Explain any changes in labor or equipment due to deletion or addition of work; and
(5) Explain any acceleration of the work.
Include a PDF file as an appendix for printing the activity chart for all activities. The PDF print size shall be 11 in. x 17 in. and organized by Phase and Area for the project.
109.03.03.03 Review and Acceptance of the Project Schedule Revisions. The Administration will complete the review of Project Schedule Revisions within 20 days after submittal. If required, a JRC will be convened at which time the Administration and Contractor may discuss corrections and adjustments to the proposed Revision. If a revision is necessary due to the JRC’s or the Administration’s review, the Contractor shall submit the proposed revision within seven days after receiving the Administration’s review comments or within seven days after the date of the JRC, whichever is the latest.
Upon written acceptance of the revisions the revised schedule is the new BCR or CPMR.
109.03.04 Extensions of the Substantial Completion Date or Incentive/Disincentive Date. All requests for extension of the Substantial Completion Date shall be in writing and subject to the notice and timeliness of submission provisions as provided for elsewhere in the Contract. Requests for time extension shall be submitted separately from the Project Schedule Update WN. Only delays to activities that affect the Substantial Completion Date or an Incentive/Disincentive Date will be considered for an extension of Contract time.
109.03.04.01 Requirements. The extension of the Substantial Completion Date or Incentive/Disincentive Date will be based upon the number of calendar days the Substantial Completion Date or Incentive/Disincentive Date is impacted as determined by a Time Impact Analysis submitted by the Contractor. The Contractor shall prepare a Schedule Time Impact Analysis of sufficient detail to describe the methodology used, cause for the alleged delay, as well as partnering efforts taken by the Contractor to mitigate any and all Contract delays.
Analysis of sufficient detail to describe the methodology used, cause for the alleged delay, as well as partnering efforts taken by the Contractor to mitigate any and all Contract delays.
The time extension request shall include a description of the events and the alleged impacts to the critical path that affect the Substantial Completion Date or Incentive/Disincentive Date. A time extension requested for changes in project requirements issued by the Administration shall be submitted separately from time extensions requested due to other alleged delays. Each time extension request shall include a Time Impact Analysis and documentation of all supporting facts.
Any time extension for weather related delays shall justify entitlement according to GP 8.08(d)(1). The Contractor shall explain the impact of adverse weather using a Time Impact Analysis and provide support documentation. Deviations from the underlying weather assumptions as framed in the work day table in Section 109.03.01.02(f), or other assumptions in the schedule will not be used as justification for time extensions.
109.03.04.02 Review and Acceptance of Time Extension Requests. Requests for an extension of the Substantial Completion Date or change in an Incentive/Disincentive Date due to changes directed by the Administration (see GP-4.06) will be evaluated by the Administration’s analysis of the BCR or CPMR and any proposed Revised Project Schedule submitted. Any request for time extension for weather delays will be analyzed by the Administration to determine if there was direct impact to work activities that are on the longest path and not analyzed based solely on the number of bad weather days actually encountered. Any time extensions for other reasons will be evaluated based on the time impact analysis, accompanying description, supporting documentation, and other project documents.
109.04 MEASUREMENT AND PAYMENT
The accepted initial Bar Chart Schedule for a Type A project, Project Schedule Revisions, Project Schedule Updates, and any necessary incidentals will not be measured but the cost will be included in other pay items contained in the contract documents.
The accepted Initial Critical Path Method schedule for Type B and Type C projects, Project Schedule Revisions, and all accepted Project Schedule Updates will be paid for at the Contract lump sum price for the Critical Path Method Project Schedule item. 50 percent of the lump sum price will be paid upon acceptance of the Initial Critical Path Method Project Schedule (except when the bid price exceeds half of one percent of the total Contract bid price). The balance will be paid as a monthly, prorated sum based upon the specified Contract duration. This monthly payment will be made on the next progress payment following the Administration’s acceptance of the required Project Schedule updates.
When the bid price for the Type B and Type C Project Schedule item exceeds half of one percent of the total Contract bid price, the total progress payments for the schedule item will be limited to half of one percent of the total Contract price. Any remaining balance (over half of one percent of the total Contract price bid) will be paid upon final Contract payment.