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
5.0 Meetings <br />The Metropolitan Council and Ban- staff met with representatives of the six cities at the kickoff of <br />this project and to review the draft report. City staff and Metropolitan Council staff were given <br />the opportunity to review and comment on the draft report in September 2014 before the final <br />report was completed. <br />3.2 Assumptions <br />To analyze the data and prepare feasibility study recommendations, several assumptions had to be <br />made as part of the process. Below is a list of assumptions made in the creation of this report. These <br />assumptions are based on the 2012 Great Lakes Upper Mississippi River Board Recommended <br />Standards for Water Works (Ten States Standards'), and our engineering judgment and experience <br />working with municipal water supply systems. <br />Assumptions made in this report are as follows: <br />1.0 The existing system is assumed to be the year 2013 water system, and the future system is <br />assumed to be the year 2030 water system. <br />2.0 Population estimates were taken from the existing city comprehensive plans, which detailed <br />infrastructure needs through 2030, and from the Metropolitan Council's "Thrive NiSP 2040". <br />Comprehensive Plan population projections for 2030 were adjusted to match the Metropolitan <br />Council's 2030 estimate if there was a large discrepancy between the two projections. <br />3.0 Future development boundaries, land use, and infrastructure locations were taken from the <br />existing city 2030 Comprehensive Plans. <br />4.0 Per capita water use (average and peak) for each city was estimated based on the average per <br />capita use for the most recent 5 years (2009-2013) of data available. For cities where all five <br />years of data was not available, an average was computed from what data was available from <br />2009-2013. <br />5.0 There is no upward or downward trend in per capita water use. Future per capita water use is <br />assumed to reflect current historical per capita water use. Future studies may want to look at the <br />emerging trends that show some reduction in per capita use for many cities across the region. <br />6.0 There is no upward or downward trend in percent of water unaccounted for. The percent of <br />water unaccounted for is calculated as the average of the most recent five years of data <br />reported in Minnesota Department of Natural Resources (DNR) water use reports. <br />7.0 The population served by cities' water supply systems is based on city reported data and <br />historical patterns. No future assumptions are made for increased or decreased service areas <br />beyond what cities have projected in their comprehensive plans. <br />8.0 The City of Columbus's existing water demand is generated primarily by industrial and <br />commercial users. Therefore, per capita water use is much higher than the other cities, and is <br />unlikely to reflect demand added by future residential customers. Future demand for the City of <br />Great Lakes - Upper Mississippi River Board of State and Provincial Public Health and Environmental Managers. <br />2012. Recommended Standards for Water Works. Albany: Health Research Inc., 2012. <br />Joint Water utility Feasibility Study 11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.