My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-12-1996 Council Packet
Orono
>
City Council
>
1996
>
08-12-1996 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2023 11:53:52 AM
Creation date
9/5/2023 11:51:57 AM
Metadata
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.
/
224
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
¥ <br />Request for Council Action <br />page 2 of 2 <br />August 8, 1996 <br />John O’Sullivan Appeal of Local SAC and WAC Charges <br />Staff then surveyed other cities to get an idea of what a reasonable fee would be. Fees in other <br />cities are generally in the range of $200.00 to $1,500.00 per unit (please see the attached <br />survey). Based on this range, staff recomuieiided the local access charge be tied to the <br />Metropolitan Council ’s SAC charge which is $900.00 pe*" unit. <br />The purpose of the local SAC and WAC charges is to collect revenue to accurately reflect the <br />level of usage of the water and sewer system, in relation to the cost of constructing the system. <br />Regular sewer and water fees reflect the cost of maintaining and repairing existing lines, <br />facilities, etc. The local SAC and WAC charges reflect the costs of both the initial installation <br />of lines and facilities, and the future replacement and expansion of the lines and facilities. <br />It is important that these fees be collected at the time the expansion of usage by individual <br />properties occuis. These funds can then be set aside to cover at least a portion of the cost of <br />the future expansion or replacement of the system. If this does not happen, development may <br />continue to intensify with no plan for addressing capacity expansion needs until the specific <br />development occurs which requires the expansion. TTie result of this would be either that the <br />last development would have to pay the full cost of the expansion, or the city would be placed <br />in the position of trying to assess the benefitti d properties for the expansion project. This could <br />be very difficult since those properties that had been able to expand their sewer and water usage <br />prior to the need for the expansion project would make the case that the expansion is not <br />benefitting them. <br />A somewhat similar situation, but dealing with new development, is the sewer expansion for the <br />Highway 12 area. This sewer expansion was planned so that the cost was built into a connection <br />charge that is collected at the time development occurs in the area to be served by the sewer <br />expansion. The amount of the connection charge related to the sewer expansion was set at <br />$1,200.00 per unit. <br />Staff Recommendation <br />It is reasonable that a developer should make some form of payment related to city sewer and <br />water capacity and availability when the development results in a substantial increase in water <br />and sewer usage. The $900 per unit SAC and WAC charges, while being toward the high end <br />of what other cities charge, are still a reasonable cost for sewer and water servic ’f the <br />O’Sullivan development was occurring in the Highway 12 area, the sewer and water connection <br />charges would be over $8,000 per unit (sewer and water combined). This would result in a total <br />cost exceeding $176,000. It is staffs recommendation that the local SAC and WAC charges <br />remain at the current level and that those charges related to the O’Sullivan development be paid. <br />COUNCIL ACTION REQUESTED <br />Motion to deny the appeal of John O’Sullivan of the local SAC and WAC charges related to his <br />development project at 3340 Shoreline Drive.
The URL can be used to link to this page
Your browser does not support the video tag.