My WebLink
|
Help
|
About
|
Sign Out
Home
2016.04.18 CC Packet
Hugo
>
City Council
>
City Council Agenda/Packets
>
2016 CC Packets
>
2016.04.18 CC Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/14/2016 4:37:53 PM
Creation date
4/14/2016 4:33:02 PM
Metadata
Fields
Template:
City Council
Document Type
Agenda/Packets
Meeting Date
4/18/2016
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
107
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
Table 10.1 Revised cost estimate WITHOUT the City of Columbus <br />Storage <br />Supply <br />Contingency <br />Centerville <br />$0 <br />$0 <br />$0 <br />Circle Pines <br />$0 <br />$0 <br />$0 <br />Hugo <br />$0 <br />$0 <br />$0 <br />Lexington <br />$0 <br />$0 <br />$0 <br />Lino Lakes <br />$0 <br />$0 <br />$0 <br />Joint Utility Cost <br />without <br />Columbus <br />$6,100000 <br />15,476,000 <br />$3472,800 <br />Total <br />$6,100,000 <br />$5,476,000 <br />$3,472,800 <br />Legal and <br />Engineering <br />$0 <br />$0 <br />$0 <br />$0 <br />$0 <br />$3.009.760 <br />$3,009,760 <br />• Negotiate initial buy -in for asset and capital sharing between cities <br />Combined <br />Infrastructure <br />Costs <br />$0 <br />$0 <br />$0 <br />$0 <br />$0 <br />$18,058,560 <br />$18,000,000 <br />The final financial terms of a Joint Utility are open for negotiation. But assuming that all parties <br />are interested in making it happen the benefits are straight forward. The fully developed <br />communities have existing assets (wells and water towers) that are needed by the growing <br />communities. The growing communities can either build them new on their own or purchase use <br />of the existing assets from the fully developed communities as part of the formation of the Joint <br />Utility. In this transaction, the assets would be valued at some fraction of the cost it would take <br />to build them new. The "purchase price" paid by the Joint Utility to the fully developed <br />communities would be based on remaining useful life and acknowledge the fact that the existing <br />fully developed community still needs and uses the asset. <br />In this way the growing communities get to access supply and storage at a fraction of the cost of <br />buying new and the fully developed communities get an influx of capitol to either pay off bonds <br />or use as they see fit. Once joined as a utility the costs of maintenance would be shared by a <br />larger group. In addition to this fewer total items would need to be maintained. <br />• Refine cost estimates based on new comprehensive planning, other studies <br />The formation of a joint utility appears to be beneficial as long as the cost of new trunk <br />watermain does not outweigh the benefits to one municipality over another. As the costs <br />reported in this study are considered high-level preliminary estimates, they should only be used <br />for comparison purposes. Future work should include a more in-depth cost analysis using future <br />2018 Comprehensive Plans and other studies. <br />10.1 Future Studies <br />As this study included only a high-level preliminary analysis, several subsequent studies are <br />recommended to move the project forward. Each recommended future study should use revised 2018 <br />City Comprehensive Plans through 2040 that use the new population projections. Studies are shown in <br />the order in which they should occur. The first two studies shown address if the water systems should <br />be joined at all and if so which ones should actually be combined. The remaining studies provide <br />guidance related to better defining the details of how city water systems would join together. <br />Joint Water Utility Feasibility Study 36 <br />
The URL can be used to link to this page
Your browser does not support the video tag.