My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 01/08/2015
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2015
>
Agenda - Planning Commission - 01/08/2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:22:22 AM
Creation date
1/15/2015 12:12:59 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
01/08/2015
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.
/
344
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
May 14, 2014 Location: Fbrama>H.:Drive>15153>RndingsFeport <br />Qty gaff believes this is a good case study for the OMCStudy Group. In this particular <br />situation, it appears evident little/no conscious effort was exhausted by the Qty (Township <br />in this case) to work with surrounding property owners—to identify, address and avoid <br />potential issues from a data center. <br />It is City Staff's opinion, similar concerns raised in this specific example (Qti Group Data <br />Center) have also been raised with the OMCStudy Group regarding a potential Ramsey data <br />center. The OMC. udy G oup has discussed a number of mitigation tactics to eliminate said <br />concerns. Examples below: <br />1. Regular use of generators on weekends <br />OMCS+udy Group proposed prohibiting use of generators on weekends for testing or <br />other regular uses. Crnly emergency use would be allowed. This would be enforced via <br />a Conditional Use Fermit (CUP). <br />2. Regular of generators at night time, all weekdays, between lOpm and 7am <br />OMCStudy Group has proposed prohibiting use of generators from 6pm-8am for testing <br />or other regular uses. Only emergency use would be allowed. This would be enforced <br />via a Conditional Use FPrmit (CUP). <br />3. Refuse of Defendant to install or design generators to avoid creation of loud noise <br />OMCS+udy Group proposed sound attenuation enclosures for generators, requirement <br />of mechanical rooms to be physically enclosed, required screening of mechanical rooms, <br />required residential transitioning standards and an emphasis to comply with MFCA <br />noise standards for residential areas—not business areas. This would be enforced via a <br />Conditional Use Permit (CUP); and, the City's existing code enforcement process. <br />4. Refuse of Defendant to shift generator operations to normal working/business hours <br />OMCStudy Group proposed use of a Conditional Use Permit (CUP) to require any non- <br />emergency use of generators to take place over normal business hours (8am-6pm M -F). <br />5. Asa result of the above issues not addressed by Oty Group (noise), the Plaintiff has <br />claimed a decrease in property value and would like to be compensated. <br />The claim of causation related to decreased property value, in the case of QtiGroup, was <br />solely based on noise (i.e. concerns 1-4). In the case of Ramsey, the OMCSudyGoup <br />has developed mitigation proposals for all said concerns. <br />This specific case study is a good example of what the Qty of Ramsey should not do, or <br />avoid, in respect to the development of the Sabject R'opertyfor a potential data center <br />project. <br />The Rndings feport Appendix includes opinions from the City Attorney and C:BFE, the pending lawsuit <br />and disposition in Ohio, multiple articles provided by O'1i1C2udyGroup members related to property <br />values, and an example of how residential property valuations were effected before and after two (2) <br />data centers were constructed in Bk Fiver, and case law regarding land value disputes with Minnesota <br />Cities. <br />OMCSudy Coup, Findings Paport (DR4F7) Page 37 of 42 <br />
The URL can be used to link to this page
Your browser does not support the video tag.