Difference between revisions of "108.05 Progress Schedule"

From MediaWiki
Jump to navigation Jump to search
m (Changed visabke text in new link related to 12SP-101A to simplify per Content Manager request (BD))
(→‎Progress Schedule, Form 1130: Replaced all information for 108.05 Progress Schedule section)
 
Line 1: Line 1:
==[[#Progress Schedule, Form 1130|Progress Schedule, Form 1130]]==
+
==[[#Progress Schedule|Progress Schedule]]==
  
A requirement of the Progress Clause is to submit a construction schedule. Unless the contract requires a CPM schedule, a Progress Schedule is required and is typically submitted on [https://mdotjboss.state.mi.us/webforms/GetDocument.htm?fileName=1130.pdf Form 1130]. This Progress Schedule is submitted by the Contractor for approval within 7 calendar days after award and prior to starting work per [https://mdotcf.state.mi.us/public/dessssp/spss_source/12SP-101A-02%20corrected%20file.pdf 12SP-101A]Typically the Progress Schedule will be submitted and discussed at the preconstruction meeting, but can vary depending upon the overall project timing.
+
The Standard Specifications for Construction subsection 108.05 contains the contract provisions for a progress schedule.   
  
 +
Scheduling requirements are included in the contract for several reasons:
 +
* Ensures that the Contractor has a detailed plan for completing the project in accordance with contract time requirements.
 +
* Provides a means of monitoring project progress.
 +
* Aids the Engineer in the management of inspection and other staff activities such as shop drawing and other reviews.
 +
* Aids the Engineer in coordinating and understanding the Contractor's work with other projects working within or near the contract limits.
 +
* Provides a means to report progress to the travelling public, local communities, government officials, and other stakeholders.
 +
* Is required to analyze the impact of changed conditions, delays, extra work, and contract modifications on any contract completion dates.
 +
* Is required to resolve construction disputes and/or claims concerning contract time.
  
The Progress Schedule will include, as a minimum, the starting and completion dates for all major items of work, controlling operations, and a final project completion date. If an open to traffic date is specified in the bidding proposal, or if the bidding proposal specifies other controlling or interim completion dates, these must also be included in the Progress Schedule. It is acceptable for the contractor to list “Contract Award” as the first item on form 1130 if the award date is correctly noted and confirmed. The first work item listed (after “Contract Award” if the contractor chooses to list this) must contain an anticipated start date with an asterisk and “*Start work on date as noted or within 10 days of contract award” in the REMARKS section of form 1130.  
+
The progress schedule can, and should, be a valuable project management tool for both the Contractor and the Engineer throughout the life of the contract.
  
 +
<u><b>Format of Progress Schedule</b></u>
  
On [https://mdotjboss.state.mi.us/webforms/GetDocument.htm?fileName=1130.pdf Form 1130], overlapping dates or workdays for start/complete of the controlling items may be allowed if sufficient justification is included in the submitted Contractor's Progress Schedule. There can be the same start date for completing an item and starting the next.
+
Per subsection 108.05.A.2, the progress schedule can be submitted in various formats using several platforms. It is preferential to use whatever native platform and format that the Contractor uses for scheduling (spreadsheet, bar chart, Gannt chart, MS Project, P6, etc.) as long as the submittal meets the requirements of the specification. This can assist with promoting transparency and collaboration, limiting conversion and duplication efforts, and allows both the Contractor and Engineer to be referencing the same schedule details. However, understand that additional scrutiny and review may be needed if the Contractor is using a scheduling software program as settings, constraints, logic, etc. may not always be apparent and they can have the ability to affect the perception of the critical path, float, etc.  
  
+
Additional documentation, narratives, and supplemental files may be necessary to comply with the scheduling specifications and can be attached to the schedule.
On workday projects, there has to be a statement on [https://mdotjboss.state.mi.us/webforms/GetDocument.htm?fileName=1130.pdf Form 1130] as to when the Contractor will start work (e.g. "Start work within 10 days of award" or "Start by June 16, 2018").  
 
  
 +
The Progress Schedule form (2012 specifications use Form 1130, 2020 specifications use Form 1130A) is intended to be used absent of any other schedule or when the Contractor’s native scheduling mechanisms do not meet specifications. If filled out correctly and completely, the Progress Schedule form will satisfy all the contractual requirements of the schedule specifications.
  
Updates to the Progress Schedule must occur as described in the 108.05.A.3 of the Standard Specifications.
+
<u><b>Schedule Review</b></u>
  
 +
The Engineer’s review of a schedule is not strictly limited to the items associated with specification compliance. In addition, the Engineer should review the schedule for the following:
  
'''''Figure 102-7''''' is an example of a completed Progress Schedule for a calendar date project. '''''Figure 102-8''''' is an example of a completed Progress Schedule for a work day project.
+
* Is the schedule sufficiently detailed so that progress can be monitored? Does the work plan make sense? Are there obvious errors in the sequence of work?  If something doesn't make sense, the Contractor should be asked to explain the intent.
 +
* Does it align with maintaining traffic and staging requirements? Are non-work periods considered like holidays, shutdowns, noise ordinances, etc.?
 +
* Does the critical path and/or controlling operations make sense? Does the logic connecting these activities seem sound? A thorough review of these activities and sequencing should be completed to understand the potential delays and issues that could impact the overall schedule and project completion.
 +
* Are the Contractors' activity durations reasonable? Do the production rates make sense? If an activity duration or production rate seems questionable, the Contractor should be asked to explain. These inquiries ensure that the schedule accurately reflects the work plan and to avoid schedule errors that could potentially cause a problem later.
 +
* Ensure that the schedule considers review and approval of major contract required submittals, either by the Engineer and/or other agencies. Activities that are beyond the Contractors' control should be carefully reviewed.
 +
* Does the schedule consider weather and seasonal limitations? If winter work is shown, can it realistically be completed? Lost days due to normal weather conditions should be included and factored into the durations and activities.
 +
* Does the Contractor have enough resources (sufficient staff and equipment) to perform the activities as scheduled? are two activities scheduled simultaneously that require the same piece of equipment (pavers, cranes, etc.)?
 +
* Confirm that material procurement is considered in the schedule, particularly for major materials with long lead times such as structural steel or bridge beams. Further guidance can be found here: [https://mdotwiki.state.mi.us/construction/index.php/102.02_Contents_of_Proposal_-_Progress_Clause#Progress_Clause 102.02 Contents of Proposal - Progress Clause].
 +
* Ensure that any third-party contract work is considered in the schedule, such as work performed by utility companies, maintenance operations , local agencies, railroad agencies, etc. Any impact of this work on the Contractor's activities should be reflected in the schedule.
 +
* Check to see that all time related contract requirements and completion dates from the Progress Clause are shown or reflected in the schedule.
 +
* Note: If a Contract Time Determination (CTD) schedule was developed for the project, it may provide some additional insight and points of reference which could assist in reviewing the items noted above. However, any direct comparison between the CTD and the Progress Schedule is for information only and must not be the basis of specification compliance.
 +
 
 +
The purpose of the review is to ensure that the schedule meets the scheduling requirements and that all time related contract requirements are included. A detailed review of the initial schedule can mitigate delays and will make it easier to address any time related issues.
 +
 
 +
<u><b>Schedule Approval</b></u>
 +
 
 +
The Engineer will review and approve schedules that meet contract requirements. The schedule can only be rejected if it does not meet the scheduling specifications, or it does not align with other contract requirements i.e. maintaining traffic provisions, staging requirements, completion dates, etc. While inquiries into production rates, activity durations, and other general constructability concerns may help to refine the schedule during the review process, they do not warrant rejection on their own. Continuous requests, discussions, and updates should occur in order to track and avoid potential issues over the life of the contract.
 +
 
 +
Approval can be designated by use of signature blocks, approval stamps, and/or correspondence (email, letter) to the Contractor. If no response is provided back to the Contractor within 7 calendar days, then the schedule will be considered approved. 
 +
 
 +
<u><b>Updates and Modifications</b></u>
 +
 
 +
Updates and modifications to the Progress Schedule must occur as described in subsection 108.05.A.3 of the Standard Specifications.
 +
 
 +
Typically, the progress schedule should be discussed and referenced as part of routine progress meetings. If the current schedule is no longer considered an accurate, valuable, relevant project management tool then it must be updated. It is highly recommended to update the schedule on a monthly basis so that it can continue to assist the project team (Engineer and Contractor) and be a valuable tool in making project management and administrative decisions.  
  
[[File:Figure 102.03-1.JPG|thumb|center|600px|Figure 102-7 - Example - Calendar Date Project Progress Schedule]]
 
  
[[File:Figure 102.03-2.JPG|thumb|center|600px|Figure 102-8 - Example - Work Day Progress Schedule]]
 
 
[[Category:Construction Manual]]
 
[[Category:Construction Manual]]
 
[[category:Division 1]]
 
[[category:Division 1]]
 
[[category:Section 108]]
 
[[category:Section 108]]

Latest revision as of 11:13, 8 September 2021

Progress Schedule

The Standard Specifications for Construction subsection 108.05 contains the contract provisions for a progress schedule.

Scheduling requirements are included in the contract for several reasons:

  • Ensures that the Contractor has a detailed plan for completing the project in accordance with contract time requirements.
  • Provides a means of monitoring project progress.
  • Aids the Engineer in the management of inspection and other staff activities such as shop drawing and other reviews.
  • Aids the Engineer in coordinating and understanding the Contractor's work with other projects working within or near the contract limits.
  • Provides a means to report progress to the travelling public, local communities, government officials, and other stakeholders.
  • Is required to analyze the impact of changed conditions, delays, extra work, and contract modifications on any contract completion dates.
  • Is required to resolve construction disputes and/or claims concerning contract time.

The progress schedule can, and should, be a valuable project management tool for both the Contractor and the Engineer throughout the life of the contract.

Format of Progress Schedule

Per subsection 108.05.A.2, the progress schedule can be submitted in various formats using several platforms. It is preferential to use whatever native platform and format that the Contractor uses for scheduling (spreadsheet, bar chart, Gannt chart, MS Project, P6, etc.) as long as the submittal meets the requirements of the specification. This can assist with promoting transparency and collaboration, limiting conversion and duplication efforts, and allows both the Contractor and Engineer to be referencing the same schedule details. However, understand that additional scrutiny and review may be needed if the Contractor is using a scheduling software program as settings, constraints, logic, etc. may not always be apparent and they can have the ability to affect the perception of the critical path, float, etc.

Additional documentation, narratives, and supplemental files may be necessary to comply with the scheduling specifications and can be attached to the schedule.

The Progress Schedule form (2012 specifications use Form 1130, 2020 specifications use Form 1130A) is intended to be used absent of any other schedule or when the Contractor’s native scheduling mechanisms do not meet specifications. If filled out correctly and completely, the Progress Schedule form will satisfy all the contractual requirements of the schedule specifications.

Schedule Review

The Engineer’s review of a schedule is not strictly limited to the items associated with specification compliance. In addition, the Engineer should review the schedule for the following:

  • Is the schedule sufficiently detailed so that progress can be monitored? Does the work plan make sense? Are there obvious errors in the sequence of work? If something doesn't make sense, the Contractor should be asked to explain the intent.
  • Does it align with maintaining traffic and staging requirements? Are non-work periods considered like holidays, shutdowns, noise ordinances, etc.?
  • Does the critical path and/or controlling operations make sense? Does the logic connecting these activities seem sound? A thorough review of these activities and sequencing should be completed to understand the potential delays and issues that could impact the overall schedule and project completion.
  • Are the Contractors' activity durations reasonable? Do the production rates make sense? If an activity duration or production rate seems questionable, the Contractor should be asked to explain. These inquiries ensure that the schedule accurately reflects the work plan and to avoid schedule errors that could potentially cause a problem later.
  • Ensure that the schedule considers review and approval of major contract required submittals, either by the Engineer and/or other agencies. Activities that are beyond the Contractors' control should be carefully reviewed.
  • Does the schedule consider weather and seasonal limitations? If winter work is shown, can it realistically be completed? Lost days due to normal weather conditions should be included and factored into the durations and activities.
  • Does the Contractor have enough resources (sufficient staff and equipment) to perform the activities as scheduled? are two activities scheduled simultaneously that require the same piece of equipment (pavers, cranes, etc.)?
  • Confirm that material procurement is considered in the schedule, particularly for major materials with long lead times such as structural steel or bridge beams. Further guidance can be found here: 102.02 Contents of Proposal - Progress Clause.
  • Ensure that any third-party contract work is considered in the schedule, such as work performed by utility companies, maintenance operations , local agencies, railroad agencies, etc. Any impact of this work on the Contractor's activities should be reflected in the schedule.
  • Check to see that all time related contract requirements and completion dates from the Progress Clause are shown or reflected in the schedule.
  • Note: If a Contract Time Determination (CTD) schedule was developed for the project, it may provide some additional insight and points of reference which could assist in reviewing the items noted above. However, any direct comparison between the CTD and the Progress Schedule is for information only and must not be the basis of specification compliance.

The purpose of the review is to ensure that the schedule meets the scheduling requirements and that all time related contract requirements are included. A detailed review of the initial schedule can mitigate delays and will make it easier to address any time related issues.

Schedule Approval

The Engineer will review and approve schedules that meet contract requirements. The schedule can only be rejected if it does not meet the scheduling specifications, or it does not align with other contract requirements i.e. maintaining traffic provisions, staging requirements, completion dates, etc. While inquiries into production rates, activity durations, and other general constructability concerns may help to refine the schedule during the review process, they do not warrant rejection on their own. Continuous requests, discussions, and updates should occur in order to track and avoid potential issues over the life of the contract.

Approval can be designated by use of signature blocks, approval stamps, and/or correspondence (email, letter) to the Contractor. If no response is provided back to the Contractor within 7 calendar days, then the schedule will be considered approved.

Updates and Modifications

Updates and modifications to the Progress Schedule must occur as described in subsection 108.05.A.3 of the Standard Specifications.

Typically, the progress schedule should be discussed and referenced as part of routine progress meetings. If the current schedule is no longer considered an accurate, valuable, relevant project management tool then it must be updated. It is highly recommended to update the schedule on a monthly basis so that it can continue to assist the project team (Engineer and Contractor) and be a valuable tool in making project management and administrative decisions.