My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
10-27-2014 Council Minutes
Orono
>
City Council
>
Minutes
>
2010-2019
>
2014
>
10-27-2014 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/5/2015 2:35:04 PM
Creation date
3/5/2015 2:34:27 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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).
Show annotations
View images
View plain text
MINUTES OF THE <br />ORONO CITY COUNCIL MEETING <br />Monday, October 27, 2014 <br />7:00 o’clock p.m. <br />_____________________________________________________________________________________ <br /> <br /> Page 26 of 32 <br />(11. PAVEMENT MANAGEMENT PLAN, Continued) <br /> <br />Levang asked if the entire trail would be repaired or whether the repairs would be done in spots. <br /> <br />Martini indicated it would vary and that they have attempted to break the trails up into smaller sections <br />and apply the appropriate repair or maintenance. Martini stated it would depend on the timing of the <br />project and the goal. <br /> <br />Levang moved, Printup seconded, to approve the Pavement Management Plan. VOTE: Ayes 3, <br />Nays 0. <br /> <br /> <br />12. WATERTOWN ROAD AND STUBBS BAY ROAD REHABILITATION <br /> <br />Edwards noted this item was discussed at the October 13 City Council meeting and was tabled to this <br />meeting. Staff has looked at three different courses of action based on Council’s comments. Edwards <br />noted a fourth option would be not doing Watertown Road at all but that option was discounted since that <br />course of action would have diverted the City from the roads that have the most need. <br /> <br />Edwards stated the first course of option looked at completing the project in its entirety in 2015 at a cost <br />of $2.66 million for both Watertown Road and Stubbs Bay Road. Edwards noted this option is less <br />expensive by a few hundred thousand dollars. <br /> <br />The second course of action looked at completing the project over a two-year time period, which could be <br />altered to stretch out over a longer period of time. Edwards noted Stubbs Bay Road is not eligible for <br />state funding and that there were slightly higher costs associated with this course of action due to delaying <br />a portion for a year and inflation factors. Edwards stated one advantage to delaying a portion of the <br />project is the potential that other funding sources may develop over time and another advantage is that <br />this takes on the worst section of Watertown Road in the first year. The disadvantage is that the most <br />traveled section will not be done until the second year. <br /> <br />Edwards stated the third course of action is over a two-year period of time and provides some flexibility <br />in funding and execution. The other advantage is that it would tackle the most traveled section of <br />Watertown Road first. The disadvantage is that this option would leave the worst section of Watertown <br />Road until 2016 and is more expensive. <br /> <br />Staff would recommend going with course of action three and then following up with the other two <br />sections of Watertown Road the following year. <br /> <br />Edwards stated the total cost of the project, whether it is done in one year or two years, would be <br />approximately $2.6 million. Approximately $1.2 million is available in MSA funds, which would leave <br />$700,000 that could be borrowed from other City funds. Edwards noted the City would need to repay the <br />money with the appropriate interest if it is borrowed from one of the enterprise funds. Another option <br />would be a potential levy increase. That would equate to $46.81 per year on a $600,000 home for every <br />$100,000 borrowed. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.