My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 04/27/2010
Ramsey
>
Public
>
Agendas
>
Council
>
2010
>
Agenda - Council - 04/27/2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 2:35:41 PM
Creation date
4/22/2010 3:20:21 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
04/27/2010
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.
/
249
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
Observations• <br />Contained within the above information there does appear to be discrepancies related to municipal utility <br />connections, both within City Code itself and compared to City Charter. At the work session a majority <br />of the Council thought the Charter Commission should undertake a review of this matter and provide <br />comments to rectify. Staff felt this issue could be resolved with amendments to City Code, to ensure <br />consistency with the Charter, and could be handled at the Council level. The main point of contention is <br />the concern that the City could force municipal utility connections on residents. The intent of the <br />proposed ordinance (and code revisions) is to clarify that the City is not trying to force such utility <br />connections, but is strictly trying to protect the health and safety of the general public. <br />There also appeared to be some concern with regard to the Charter language of "functional" systems. <br />Some Council members feel that inconsistencies may still exist and the language is not quite clear enough <br />on the intent of the City with regard to forced utility connections, therefore a resolution is attached to this <br />case for Council consideration. This resolution requests the Charter Commission to review this matter <br />and provide their input on whether the language within Charter should be revised to clarify the City's <br />stance on municipal utility connections. <br />City Code Section 4.70 defines anon-functional system as an on-site private system which does not <br />comply with Chapters 7080 (sewer) or 4725 (water) of Minnesota Rules. This section was added to Code <br />as a means of ensuring that the provisions of the City Charter related to sewer and water project ware <br />adequately enforced, and reinforced in Code. <br />Minnesota Rules determine a system to be non-functional if one or more of the following conditions <br />apply: <br />1) Sewage discharge to surface water; <br />2) Sewage discharge to ground surface; <br />3) Sewage backup; or <br />4) Any other situation with the potential to immediately affect or threaten public health safety. <br />If any such conditions apply then the system constitutes an imminent threat to public health or safety and, <br />if not repaired, must be upgraded, replaced, or its use discontinued within ten months of receipt of the <br />notice or noncompliance, or within a shorter period of time if required by local ordinance. <br />City Code Section 113-23 (d) (2) references under what conditions a notice of noncompliance will be <br />issued: <br />a) A failed individual sewage treatment system (ISTS) shall be upgraded, replaced, or repaired in <br />compliance with MN Rules Chapter 70$0, as applicable within one (1) year of the date of notice of <br />noncompliance. The Department will give consideration to weather conditions as compliance <br />dates are established; <br />b) An ISTS posing an imminent threat to public health or safety shall be upgraded, replaced, or <br />repaired within ten (10) months of the date of noncompliance; <br />c) When the ISTS is determined to be failing at the point of sale or transfer of property; <br />d) The owner shall submit to the Department an acceptable replacement plan within twenty (20) days <br />after notification by the Department. The replacement plan shall identify the location and design <br />of the ISTS and a schedule for its replacement. Failure to submit and execute an acceptable <br />replacement plan is a violation of this Section. <br />
The URL can be used to link to this page
Your browser does not support the video tag.