My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2012/08/13
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2010-2019
>
2012
>
Agenda Packets - 2012/08/13
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:49:33 PM
Creation date
6/26/2018 3:11:08 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
8/13/2012
Supplemental fields
City Council Document Type
City Council Packets
Date
8/13/2012
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.
/
266
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 />Ramsey County Multijurisdictional Hazard Mitigation Plan | February 2012 6-1 <br />Section 6 <br />EXECUTING THE PLAN <br /> <br />6.1 Plan Implementation <br />The Ramsey County Multijurisdictional Hazard Mitigation Planning Committee process was overseen by <br />the Ramsey County Emergency Management and Homeland Security department. The plan will then be <br />submitted to the Minnesota Homeland Security and Emergency Management and the Federal Emergency <br />Management Agency (FEMA) for approval. The Ramsey County Board of Commissioners and all cities <br />and townships will formally adopt the plan by resolution in accordance with the Disaster Mitigation Act <br />of 2000. <br />Each jurisdiction participating in this plan is responsible for implementing specific mitigation actions as <br />prescribed in the mitigation strategies. In each mitigation strategy, every proposed action is assigned to a <br />specific local department or agency in order to assign responsibility and accountability and increase the <br />likelihood of subsequent implementation. This approach enables individual jurisdictions to update their <br />unique mitigation strategy as needed without altering the broader focus of the countywide plan. The <br />separate adoption of locally specific actions also ensures that each jurisdiction is not held responsible for <br />monitoring and implementing the actions of other jurisdictions involved in the planning process. <br />In addition to the assignment of a local lead department or agency, an implementation time period or a <br />specific implementation date has been assigned in order to assess whether actions are being implemented <br />in a timely fashion. As necessary, Ramsey County and its participating jurisdictions will seek outside <br />funding sources to implement mitigation projects in both the pre-disaster and post-disaster environments. <br />When applicable, potential funding sources have been identified for proposed actions listed in the <br />mitigation strategies. <br />6.2 Evaluation <br />All members of the Ramsey County Multijurisdictional Hazard Mitigation Planning Committee and the <br />emergency management director will be responsible for ensuring that the Ramsey County <br />Multijurisdictional Hazard Mitigation Plan is evaluated as required. The evaluation will include analyzing <br />current mitigation projects and evaluating success and reevaluating future mitigation needs and <br />prioritization based upon changes in needs and/or capabilities of Ramsey County. <br />The Ramsey County Multijurisdictional Hazard Mitigation Planning Committee will reconvene annually <br />to ensure that projects are on track and to reevaluate the mitigation goals, objectives, and action steps. The <br />mitigation plan shall be viewed as an evolving, dynamic document. <br />44 CFR Requirement 201.6 (c) (4)(i) <br />[The plan maintenance process shall include a] section describing the method and schedule <br />of monitoring, evaluating, and updating the mitigation plan within a five-year cycle.
The URL can be used to link to this page
Your browser does not support the video tag.