My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2017_0717
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2017
>
CC_Minutes_2017_0717
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/18/2017 9:05:28 AM
Creation date
8/18/2017 9:03:58 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
7/17/2017
Meeting Type
Work Session
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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, July 17, 2017 <br /> Page 2 <br /> programs to determine what each fund needed to be most seriously addressed <br /> without having a huge impact on residents to carry those additional costs. <br /> Along that line, Councilmember Willmus sought clarification on the projected <br /> status for the Street Replacement Capital Improvement Program (CIP) funding at <br /> five, ten and twenty year increments in the additional attachment to the staff re- <br /> port as referenced above. <br /> Mr. Miller responded that the report showed the Street Replacement CIP funding <br /> in good shape today. However, over the next twenty years, Mr. Miller noted that <br /> this CIP fund would eventually run out of money at the current pace, creating a <br /> challenge even though it was also a unique situation with time available to ad- <br /> dress the fund over the next 15-16 years, projecting a gap of approximately $1 <br /> million between revenue and expenditures at that point. Therefore, Mr. Miller <br /> noted staff's recommendation along with previous City Councils to repurpose ex- <br /> isting debt levies when they're paid off and add additional levy funding after that, <br /> including staff's recommendation in the 2018 budget to increase the levy by <br /> $160,000 to slowly strengthen the Street CIP fund to achieve a more sustainable <br /> point. Mr. Miller noted that the sooner that gap was addressed, the easier it would <br /> get, especially with the current cash reserve level at the end of 2016 at over $10 <br /> million. <br /> Councilmember Willmus noted that, earlier this year, discussion had been initiat- <br /> ed to potentially reallocate CIP dollars; and asked if staff had started that review <br /> or was waiting for the City Council to take the lead. <br /> City Manager Trudgeon responded that potential CIP reallocation was continually <br /> reviewed by all departments as standard operating procedure, especially when the <br /> city continued to have so many needs and limited cash to address those needs. <br /> When a CIP item can be deferred, Mr. Trudgeon advised that they were. Howev- <br /> er, Mr. Trudgeon noted several funds that would be experiencing problems sooner <br /> rather than later, advising that staff was focused on those. If the City Council <br /> identified some CIP items as unnecessary replacements, Mr. Trudgeon advised <br /> that staff would need to react accordingly. Trudgeon advised that staff continued <br /> to research additional or new funding sources, or how to do things differently in <br /> order to save money. <br /> Mayor Roe noted that, for the initial 2018 budget projections, in conjunction with <br /> previous CIP task force recommendations staff recommends adding new levy ca- <br /> pacity for the street CIP, after already previously repurposing existing levy funds <br /> (page 2). <br /> Councilmember McGehee opined that it was also important with the CIP to note <br /> that there was nothing anywhere near adequate being set aside for pathways <br /> and/or parking lot maintenance at this point, further opining that $5,000 per year <br /> per mile was the standard suggested allotment. Councilmember McGehee stated <br />
The URL can be used to link to this page
Your browser does not support the video tag.