My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2015_1116
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2015
>
CC_Minutes_2015_1116
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/21/2015 9:52:39 AM
Creation date
12/8/2015 10:22:15 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
11/16/2015
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
39
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
Regular City Council Meeting <br />Monday, November 16, 2015 <br />Page 31 <br />Culver advised that there were several items that had more risk involved (e.g. <br />$75,000 allotment for a signal system) without more detailed review of its final <br />design and fluctuations with the current bidding climate that could also increase <br />that rislc and costs. Mr. Culver noted that the potential to group some of those <br />improvements with another proj ect was also possible. Mr. Culver noted that the <br />applicant had showed this estimate to a regular contractor and they felt it was still <br />in the general ballpark. Mr. Culver stated that he had no grave concerns over that <br />$400,000 estimate; however, based on past experience in unknowns (e.g. Wal- <br />Mart project) and possible private utilities or other items not showing up until <br />constniction time, he remained hesitant to cap those costs at this time. <br />Related to the compete cost of iinprovements, Mayor Roe questioned how those <br />cost shares could be addressed after an agreement was in place (e.g. traffic sig- <br />nal). While Mayor Roe noted that since this is not just a city road and usually <br />costs were shared associated with traffic signal improvements, and further noted <br />that there were other agencies involved that were not subject to the agreement be- <br />tween the City of Roseville and JLL. Under those circumstances, Mayor Roe <br />asked if there was any term of this PUD Amendment Agreement that could be re- <br />considered by mutual agreeinent of both parties in the future. <br />City Attorney Gaughan responded that this was certainly possible, as was current- <br />ly being done through this ainendment to PUD Agreement #3608. <br />Mayor Roe opined that he anticipated parties may be willing to take another loolc <br />at the Agreement depending on how things worked out. <br />Mr. Moston advised that one thing JLL was touching on was the idea of a cost es- <br />timate versus the scope of the project. Mr. Moston advised that JLL's concern <br />comes inore from that scope involving those things and costs not under the con- <br />trol of JLL and their scope of final designs and additions. Mr. Moston reiterated <br />JLL's willingness to contribute to this project and see it benefit their property and <br />the Roseville community. However, Mr. Moston noted their concern remained <br />having some financial controls over that scope versus estimate, thus their willing- <br />ness to include a contingency for unforeseen costs. <br />Councilmeinber Willmus expressed appreciation for the developer's perspective. <br />However, all things considered, Councilmeinber Willmus opined that the most <br />prtident action on the part of the City Council would be to approve the PUD <br />Agreeinent Amendment as presented; and should there be extenuating circuin- <br />stances down the road, further amendment could be considered at that time. <br />Willinus moved, Etten seconded, adoption of Resolution No. 11272 (Attachment <br />G) entitled, "A Resolution Approving Planned Unit Development #15-019 (At- <br />tachment F) related to Improvements at Rosedale Center;" amendecl to �educe de- <br />sign standaNc� rec�uirements for window and dooa� openings (RCA page 4, lines <br />
The URL can be used to link to this page
Your browser does not support the video tag.