My WebLink
|
Help
|
About
|
Sign Out
Home
2016-08-23_PWETC_AgendaPacket
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Agendas and Packets
>
201x
>
2016
>
2016-08-23_PWETC_AgendaPacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/18/2016 4:05:21 PM
Creation date
8/18/2016 3:56:42 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Agenda/Packet
Commission/Committee - Meeting Date
8/23/2016
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
78
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
34 <br />35 Discussion included various sidewalk installations or rationale for not installing <br />36 certain segments at this time (e.g. Wheaton Woods); and formal and/or typical <br />37 processes for residents to provide feedback on various city projects before, during <br />38 and after a project (e.g. Commissioner Trainor with S Owasso Drive project). <br />39 <br />40 Mr. Culver encouraged any resident on any project to provide their feedback on <br />41 the project; and reviewed the various methods available (phone, email, personal <br />42 staff contact at City Hall, etc.) at any time to inform future projects. <br />43 <br />44 Specific to the S Owasso project, Mr. Culver noted it had been a challenging year, <br />45 which was both good and bad, with a very aggressive contractor on that particular <br />46 project that kept things ahead of schedule, but made it difficult if not impossible <br />47 to provide proper notification for residents, and staff s normal communication <br />48 methods. However, Mr. Culver noted lessons had been le\way <br />to <br />49 manage the contractor rand projectNwas <br />and reiterated staff s ing from <br />50 residents about the process. <br />51 IAL <br />52 Member Trainor noted the end reshe contractor bhead of <br />53 the schedule which had been painful for the residents. Masked Mr. <br />54 Culver if there was contractual language the city could use to avoid those types of <br />55 happenings. <br />56 <br />57 Due to current contractor laws, Mr. Culver responded it was difficult to make a <br />58 contractor comply unless it was at a financial cost to them, with normal legal <br />59 channels used to fine a contractor or charge for non-performance unsatisfactory <br />60 unless additional costs had actually been incurred (e.g. liquidated damages); and <br />61 the required time and investment for the city to follow-through and ultimate <br />62 taxpayer cost to do so., -44%V <br />63 <br />64 r. Culver noted that o usly some contractors were easier to deal with than <br />65 others. As the city moves more into best value contracting and awarding <br />66 contracts under that method, which the city had yet to do with its Pavement <br />67 Management Program (PMP) projects, Mr. Culver advised that a contractor's <br />68 previous experience on such elements could be used to reduce their score on <br />69 future projects. Mr. Culver advised this would be accomplished through cities <br />70 sharing their reviews and scores on contractors and their experiences, with that <br />71 information used to score contractors accordingly. However, Mr. Culver noted <br />72 this would require a consistent or standard method for post -project reviews; and <br />73 there was some momentum in the industry to give cities more control making it in <br />74 the contractor's best interest to perform above and beyond the norm. <br />75 <br />76 Member Trainor stated he would submit his comments as a resident to Mr. <br />77 Culver. <br />78 <br />79 5. City Campus Solar <br />Page 2 of 19 <br />
The URL can be used to link to this page
Your browser does not support the video tag.