My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
City Council Agenda and Packet 2015 05 19
PORTAL
>
CITY COUNCIL RECORDS
>
AGENDAS & PACKETS (45.010)
>
2010-2019 City Council Agendas and Packets
>
2015 City Council Agendas and Packets
>
City Council Agenda and Packet 2015 05 19
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 2:08:08 PM
Creation date
6/2/2015 9:40:16 AM
Metadata
Fields
Template:
City Council Records
Doc Type
City Council Packet
Original Hardcopy Storage
7A5
Record Series Code
45.010
Supplemental fields
Test
CCAGPKT 2015 05 19
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
658
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
City Council <br />Meeting Minutes <br />May 5, 2015 <br />Page 17 of 33 <br />City Manager Fleming confirmed the model would provide the assumptions for various <br />scenarios. He was comfortable with the marginal cost fiscal model and going forward <br />with the average cost fiscal model. <br />Council member Stolzmann stated the key piece of adopting a model is the <br />assumptions, which start in the model. There are two models, a hybrid approach and a <br />marginal approach, but Council has only reviewed one. She felt the assumptions are <br />the crux of the matter. She was comfortable directing staff to continue working on the <br />model, but she was uncomfortable with approving the model. <br />Mayor Pro Tem Dalton felt the Council is being asked to agree with the structure of the <br />model. The assumptions would be put in later. Council member Lipton was willing to <br />accept the work of the consultant. It would be up to Finance Committee to use the <br />model and provide some analysis for decision making in the future. <br />City Manager Fleming explained the financial projections for the next 5 years are based <br />on key assumptions, which are made clear to Council. The assumptions are on <br />changes in revenue over the next five years. These assumptions are presented in a <br />summary table every June and during the budget process and Council is asked to <br />confirm the assumptions. If staff is overly optimistic or overly cautious, Council can <br />modify the assumptions. Staff will be able to demonstrate scenarios for the Finance <br />Committee to make sure the approach is correct. When the model is used, the <br />assumptions will be made clear. It was his understanding those assumptions are <br />relatively easy to change. <br />Council member Loo was comfortable with approving the model. She asked if Council <br />will be able to determine the capacity of facilities and noted that is what the public is <br />concerned about. She asked whether it will be a staff recommendation or will it be a <br />recommendation from the Finance Committee. <br />Council member Stolzmann stated a large piece of the model is to determine capacities. <br />The model is really two models and Council has only reviewed one model. She stated <br />her understanding was to direct staff to continue with the second model. <br />Mr. Bise confirmed they are waiting to see if Council is comfortable with the first model <br />before the second model is done. <br />Council member Stolzmann asked if the model presented is the marginal cost model or <br />the average cost model. Mr. Bise stated it is the marginal cost model. <br />Council member Stolzmann would be more comfortable with the Finance Committee <br />looking at both models and making a recommendation. Council member Lipton was <br />comfortable with the model and felt the process must be moved along. He accepted <br />Council member Stolzmann's recommendation for Finance Committee review. <br />48 <br />
The URL can be used to link to this page
Your browser does not support the video tag.