My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 02/22/2000
Ramsey
>
Public
>
Agendas
>
Council
>
2000
>
Agenda - Council - 02/22/2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2025 1:39:15 PM
Creation date
9/8/2003 9:52:32 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
02/22/2000
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
159
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
I <br /> I <br /> I <br /> I <br /> I <br />I <br />I <br /> I <br /> I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br /> <br />PW CAS] # 2.. <br /> <br />UPDATE OF STORM WATER UTILITY IMPLEMENTATION <br /> By: Steve Jankowski, City Engineer <br /> <br />Background: <br /> <br />At the December 21, 1999 Public Works Committee meeting, a discussion was held on the <br />details affecting the implementation of the storm water utility. Initially it was anticipated that the <br />billing for the first quarter could be mailed in April. The adopted ordinance, however, was not <br />published until February 4, 2000, and will not go into affect until March 6, 2000. The City <br />Attorney has advised that billing should not be retroactive. Therefore, we will only be able to <br />bill for 25 of the 91 days in the first quarter. It may be preferable to delay the first billing until <br />the second quarter. <br /> <br />The second purpose of this case is to present an update on the status of determining the charges <br />for the non-residential customer. At the time of this writing, 150 non-residential customers have <br />been identified. To determine the charge for these non-residential customers, parcel area and the <br />percentage of area that is impervious needs to be calculated for each parcel. The area has been <br />determined for 100 of the~ 150 parc6is, however, only 50 parcels have completed the <br />determination of impervious coverage. Staff believes that, with additional staff assigned to this <br />task, the remaining parcels can have the calculations completed by March 1. We have been <br />advised by Connexus, who performs the City utility billing, that all information needs to be <br />submitted to them by the first week of March. <br /> <br />The final purpose of this case is to present issues that have arisen in the process of implementing <br />the utility and seek direction or concurrence on policy to deal with these issues: <br /> <br />1) The majority of parcels have a single utility customer and address. How should multi- <br /> address and multi-tenant parcels be charged? <br /> <br />In checking with other communities having storm water utilities, these parcels are usually <br />billed to the property owner. The owner then is responsible for collecting from his tenants as <br />he sees fit. This system will require a separate billing. We have identified 14 such <br />customers. <br /> <br />2) <br /> <br />According to the ordinance, no commercial customer would be charged a Residential <br />Equivalent Factor (REF) less than 1.02. For very large properties, this can result in some <br />unusually high monthly costs. For example, the Rum River Hills Golf Course contains 100 <br />acres. Their monthly bill would be $1,020 under the formula. " <br /> <br />An alternative would be to use the percentage of paved area around only the clubhouse and <br />parking area. In this case, an impervious factor of 86% calculated on the two acres <br />encompassing the clubhouse would result in a monthly charge of $414. Similar situations are <br />typical of the Gun Club, the Boy Scout Camp, The Links Golf Course, Green Valley <br />Greenhouse, and Armstrong Kennels. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.