My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 05/23/2017
Ramsey
>
Public
>
Agendas
>
Council
>
2017
>
Agenda - Council - 05/23/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2025 3:33:01 PM
Creation date
5/25/2017 11:36:20 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
05/23/2017
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.
/
235
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
year Capital Improvement Plan (CIP) a separate resolution is not necessary. Instead provide a copy of the <br />appropriate pages from the CIP and clearly reference this point in the request letter. <br />6. Supporting Documentation and Additional Materials <br />Required Elements <br />a. Indicate if right-of-way is expected to be acquired (temporary and permanent) and if any will be <br />passed along to MnDOT. (All R/W acquired by and for MnDOT requires Environmental Due Diligence <br />(EDD) forms to be completed and evaluated during design.) <br />b. Indicate if there will be any excavation below the level of Class 5. (This determines future <br />involvement of the Office of Environmental Stewardship.) <br />c. If you are submitting applications for more than one project, please rank them in order of priority. <br />The preference will be considered but the committee reserves the right to select any project from <br />those submitted regardless of stated ranking. <br />Suggested Elements <br />While these materials are not required for the application, they may help the selection committee understand <br />your project better and increase the likelihood of project selection. Please note that this information may be <br />needed during the design phase if the project is selected. <br />a. Traffic Study (as applicable) <br />b. Approved Intersection Control Evaluation (ICE) report or letter if an all -way stop, signal or roundabout is <br />proposed <br />c. Environmental studies or documentation if available, such as the following: <br />i. Contaminated Properties/Regulated Waste Screening Checklist <br />ii. Phase 1 and/or 2 Environmental Site Assessment <br />iii. Clearance Letters from pertinent Regulatory Agencies <br />iv. Project Memo, EA, EIS, etc. as applicable or available at time of submittal <br />d. Compliance with Metropolitan Council Transportation Policy Plan (TPP), MnDOT/Metro Highway <br />Investment Plan (HIP) or Local Comprehensive Plans as applicable, indicating how the proposal supports <br />community development. <br />Please note that during design, the review by MnDOT functional areas will be different from reviews you have <br />typically experienced with State Aid plans. Ultimately, plans will need to be developed to MnDOT standards <br />which are different than State Aid standards. There will be more need for coordination with and input from <br />various MnDOT groups. Local Agencies are advised to have staff or consultants experienced with MnDOT Trunk <br />Highway projects directly involved with the plan development. Adequate discussion with MnDOT Area Managers <br />or Cooperative Agreements staff will help to minimize surprises during the application and plan development <br />stages. <br />For projects that are selected, there are newer requirements required during design for all plans with Trunk <br />Highway impacts. Discuss these with your design staff or include in your contract if you are using a consulting <br />firm for design. These requirements are: <br />• Quality Management Process (QMP) — Designers must have quality management procedures that <br />they use during plan development. It does not have to be the same process that MnDOT uses, but it <br />A-2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.