My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 12/13/2005
Ramsey
>
Public
>
Agendas
>
Council
>
2005
>
Agenda - Council - 12/13/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 2:00:57 PM
Creation date
12/12/2005 9:27:31 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
12/13/2005
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.
/
707
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
-:. · Case #3 <br /> DISCUSSION ON PUBLIC WORKS CAMPUS. <br />By: Bi'inn E. Olson, Assistant Director of Public WOrks/Principal City Engineer <br /> <br />Background: <br /> <br />On August 19, 2002, the City Council directed Staff to retain the Alloy Recovery site for <br />the use of the Public Works Department. (minutes attached) <br /> <br />On July 20, 2004, the Public Works Committee recommended to the CitfCouncil to <br />approve the City taking control of the property out to Lim°n/te street. (K.IH property) <br />TI:tis motion was ratified by the City Council on Au~w_~st 10, 2004. (minutes attached) <br /> <br /> This year, Staff was fortunate to have the City Council award 'a Contract to provide a <br /> "temporary" fix to the need for office space by installing the current PW Office and also <br /> installing a' new exterior and roof to the vehicle storage building to provide another <br />· heated environment for our vehicle storage. <br /> <br /> Observations: <br /> <br />Over the past few years it has become increasingly noticeable that the Public Works <br />Campus is becoming utilized and it seemed evident that we are in need of some long <br />range planning for the site. Before the Public Works Department enters into any <br />discussions about what type of"permanent" fa~ilities will be needed in the future, we felt <br />the most important question to ask was whether there was enough land available in the <br />present location for all future maintenance and operations. <br /> <br />Early.in the research to provide an estimate of the amount 0f~oss space (acres) that <br />Would be projected for Public Works Maintenance and Operations (Streets, Parks and <br />Utilities), a couple of things became apparen.t. One was that projecting the mount of land <br />area needed using square footages of warm and cold storage, offices,.outd0or storage, <br />parldng, sedimentation ponds, Police impound, landscaping, drive tunes and accesses etc. <br />was a complex exercise - and one requiring a lot of assumptions. The other matter that <br />became apparent was that there was a lot more similarities in how different city's <br />conducted their respective maintenance operations than dissimilarities. <br /> <br />Staff also learned that the City of Brooklyn Park conducted a fairly detailed survey of. <br />suburbs with populations near 50,000 (50k), for their public works analysis in 2004. <br />These cities were; Apple Valley (46k), Blame (45k), Bloomington (89k), Burnsville <br />(61k.), Coon Rapids (63k), Eagan (66k), Eden Prairie (55k), Edina (50k), Maple Grove <br />(50k), Mim]etonka (52k), and Plymouth at (67k). <br /> <br />Brooklyn Park's findings were that the only si=mn..ificant difference m these cities was the <br />ratio of full-time staff to seasonal. However, the 'full-time equivalent' was generally <br />consistent. Further into staff's research, we met with Brooklyn Park and Coon Rapids' <br />staff and learned that both of these cities felt that ~oss acreage they had were adequate <br />~br their present and near-term needs. Both had 29 acres of land for the maintenance and <br />operations needs of streets, parks, and utilities as well as a police impound. <br /> <br />-682- <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.