My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 05/08/2007
Ramsey
>
Public
>
Agendas
>
Council
>
2007
>
Agenda - Council - 05/08/2007
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/19/2025 1:21:06 PM
Creation date
5/4/2007 3:11:40 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
05/08/2007
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
184
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
comprises a significant portion of the proposal. The process will include identification <br />of drainage basins without an outlet, perennial ponding areas that require remedial • <br />action to protect structures and streets. The process will also include creation of a storm <br />water model for the City that can be manipulated by the staff in the future. This will <br />provide the ability to assess the potential impact of new development on downstream <br />properties. Currently we receive models for each site that show how the storm sewer on <br />site will function; however, we lack the capability of dete the cumulative effect <br />of multiple projects on a drainage way. <br />The City has been part of the FEMA Flood Insurance Program since 1979. There were <br />several areas in that study where the flood elevation was not determined. The WRMP <br />will provide data for updating the Flood Insurance Maps for Ramsey for the areas where <br />the elevation was not established and reviewing areas where significant development <br />has occurred. <br />This plan will be an update of the 1980 Comprehensive Storm Drainage Plan. There <br />were amendments in 1987, 1997 and 2002. The 1997 and 2002 amendments only <br />covered the southeast quadrant of the city where updated topographic information was <br />available. The 1980 plan was prepared using USGS 10 foot contours, which were the <br />best available data at the time. This update will utilize the 2003 Aerial maps with 2 foot <br />contours commissioned by the city. Data for areas developed after the aerial maps were <br />created will use the approved plans on file at the city. <br />Staff has requested that the WRMP be a working document, organized so that the • <br />recommendations and action items are easily identifiable and can be implemented in a <br />systematic approach. The storm sewer model requested will assist in this process. <br />The request for proposal (RFP) was approved by the Public Works Committee in <br />January 2007 and ratified by the City Council in February. Requests were sent out in <br />March to seven consultants identified by staff as having experience in preparing studies <br />of this nature. Staff met with each consultant after they had a chance to review the REP <br />and answer their specific questions. Proposals were received on April 12 and then <br />reviewed and ranked. Each consultant prepared a quality proposal and evaluation to <br />determine the finalists was a lengthy process. <br />The evaluation criteria were spelled out in the RFP and are summarized below: <br />1. Project Understanding: The firm's understanding of the project and concerns <br />of the City as presented in the proposal. <br />2. Project Approach: Clarity, innovation, organization and overall responsiveness <br />to the RFP. <br />3. Project Personnel: The assignment of qualified and experienced staff who have <br />proven their ability to work together as a team. <br />4. Firm References: Firm's past performance on City projects, inquiries with <br />previous clients and other references. <br />5. Firm Experience: Qualifications and expertise of the firm and key project • <br />personnel in performing services required for this project as demonstrated by the <br />quality of the firm's previous and current projects. <br />—116— <br />
The URL can be used to link to this page
Your browser does not support the video tag.