My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Public Works Committee - 08/15/2011
Ramsey
>
Public
>
Agendas
>
Public Works Committee
>
2010 - 2019
>
2011
>
Agenda - Public Works Committee - 08/15/2011
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2025 10:17:42 AM
Creation date
11/3/2011 8:33:54 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Public Works Committee
Document Date
08/15/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
57
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Public Works Committee 5. 1. <br />Meeting Date: 08/15/2011 <br />By: Tim Himmer, Engineering/Public <br />Works <br />Title: <br />Review Standard Contract Language Related to Construction Projects <br />Background: <br />Construction contract language has been discussed numerous times over the past year, with the main item of <br />contention by the Council being the requirement for prompt remedial action by the contractor. There is a desire to <br />understand the timing for getting a contractor back on a project should any work be found defective. Attached is <br />the City's standard general condition language contained within our specifications. I have highlighted specific <br />items germane to the Council's concern, and feel that the current language is sufficient to resolve timely corrective <br />actions of deficient work. Additional language could be added to clarify the timelines for contractor response, and <br />staff is looking for feedback from the Council on whether they feel their concerns are satisfactorily addressed in the <br />current language or whether revisions are necessary. <br />Notification: <br />Observations: <br />Staff would also like to discuss a couple of other items related to our construction contracts; including contract close <br />out (warranty bonds), and contingency authority. We have heard from contractors on several occasions that they <br />would like to final projects with minor items remaining, and handle those with the warranty bond that they are <br />required to post following project close out. There are currently several existing projects in the City where the only <br />remaining item is turf establishment; the seed has been planted but we are awaiting full growth over the entire area. <br />The contractors are arguing that the warranty bonds should satisfy the security requirement and ensure that any <br />necessary corrective actions (if any) will be addressed should something go wrong. They state that in some <br />instances they cannot take on additional projects because their bonding capacity has reached its limit; they cannot <br />get additional performance and payment bonds issued until some of their previous projects are released. They are <br />hopeful that the Council will consider turf establishment similar to road and utility work where we currently require <br />a 1 year warranty following project acceptance. Under this scenario a project could potentially be accepted for final <br />payment following the installation of seed (or other ground cover) in the fall of the year without knowing whether <br />the turf would actual take (spring growth). <br />Another item staff is looking for feedback on is whether the Council is comfortable including a standard <br />construction contingency with projects, as a small percentage of the overall contract price. This would be approved <br />by the Council at the time of award but not included in the overall contract with the contractor; it would be an <br />allowance authority for staff to utilize if site conditions require additional work or a revised approach. Usually at <br />the onset of construction property owners come forward with concerns that weren't previously identified during the <br />design process that would necessitate a revised approach to the work; including such things as addition of a catch <br />basin and /or storm pipe to address a drainage concern, realigning a sidewalk /trail around a junction box, tree, or <br />private improvement near the construction limits of the project, septic system and /or wells near the construction <br />limits, etc. Other unknown items could also present themselves during construction; including high water table, <br />poor soils, deteriorated pipes, expanded removal limits, etc. <br />Staff understands that we must effectively manage projects to keep them on schedule and on budget, but sometimes <br />unknown conditions present themselves. It's in these instances that it would be nice to have some flexibility at the <br />staff level to effectively construction manage and resolve matters quickly. This contingency would only be utilized <br />as necessary, and up to a maximum cap — similar to what frequently occurs on larger projects. <br />Funding Source: <br />
The URL can be used to link to this page
Your browser does not support the video tag.