Embed Size (px)
Citation preview
MnDOT District 3
7694 Industrial Park Road Baxter, MN 56425-8096
218-828-5700
Scope of Work (DRAFT)
MINNESOTA TRUNK HIGHWAY 210/WASHINGTON STREET
CORRIDOR STUDY BAXTER DRIVE TO PINE SHORES ROAD IN BRAINERD, MN
.
Baxter Dr.
Pine Shores Rd.
2
Table of Contents
Background 3
Objective 3
Projects for Consideration 4
Scope of Work 5
Task 1: Project Management/Stakeholder Involvement 5
Subtask 1.1: Public Involvement Plan 5
Subtask 1.2: Progress Reports 8
Subtask 1.3: Development of Information Materials 8
Subtask 1.4: Ongoing Internal Project Coordination 8
Task 1 Deliverables and Due Dates 8
Task 2: Operational Needs 10
Task 2 Deliverables and Due Dates 10
Task 3: Traffic/Corridor Analysis 11
Subtask 3.1: Traffic Operations Analysis – Identify Needs 11
Subtask 3.2: Identify Geometric/Traffic Control Alternatives. 11
Subtask 3.3: Traffic Operations Analysis/Simulation-Assess 12
Subtask 3.4: Develop Conceptual Alternatives 12
Subtask 3.5: Develop Evaluation Criteria and Measures 13
Task 3 Deliverables 13
Task 4: Benefit/Cost Analysis 14
Task 4 Deliverables 14
Task 5: Level 1 layout 15
Subtask 5.1: Environmental Documentation 16
Subtask 5.2: Design Memo 16
Task 5 Deliverables 16
MnDOT Contacts for Assistance 17
3
Background Washington Street is a major travel corridor spanning from West to East Brainerd, MN along T.H. 210. 2016 and 2107 traffic counts show ADTs varying from 12,300 to 30,500 along Washington Street as it spans the Brainerd Baxter area. This portion of T.H. 210 has the largest traffic volume in Crow Wing County with varying patterns in traffic characteristics along the corridor. These variances are due to the distribution of business and residential areas and their relative proximity to controlled intersections as well as other areas of congestion. In addition, the Paul Bunyan Trail and planned Cuyuna Lakes Trail enter Brainerd from the west and east respectively. Washington Street may be a candidate to improve bicycle connections across Brainerd and bring these two trails together.
Objective The Minnesota Department of Transportation is requesting proposals to complete a corridor and development study for an upcoming T.H. 210 improvement project. This project is planned for fiscal year 2025. The result of this study would be providing MnDOT with a Geometric Design Support Unit (GDSU) approved Level 1 layout of the corridor. This Level 1 layout must have municipal consent. The primary objective of this study is to guide MnDOT and all interested/impacted parties to what the future corridor reconstruction/rehabilitation project will look like. This project would be along the four lane portion of Washington Street from Baxter Dr. to Pine Shores Rd. in Brainerd, approximately 4 miles in length. Primary areas of concern which will be seeking information and input on include:
• ADA Improvements o Extensive changes to pedestrian access routes (PAR) in order to achieve
compliance and improve safety. • Railroad
o Evaluate the working relationship of the RR corridor and maintenance yard parallel of the road corridor.
• Access Changes o Analyze potential vehicle access issues which need to be addressed in order to
improve safety and traffic flow along the corridor. o Look at all available access control and future decisions regarding access.
• Bridge o Analyze the need for changes to the cross-section of Mississippi River Bridge
#5060 and their potential impacts to the corridor. • Mississippi River Walk
o Coordination with the City of Brainerd’s Mississippi Riverfront Committee which has pending conceptual plans for a river walk along the Mississippi River in downtown Brainerd.
• Bicycle Connectivity o Coordination with the City of Brainerd, Cuyuna Lakes Trail Association, Paul
Bunyan Trail, and DNR. Trail facilities currently exist along and near the corridor, and additional connections are proposed. There is a gap in bicycle facilities through Brainerd.
4
• Freight and Commercial Vehicles o Coordination with reginal trucks and businesses that use this route to transport
goods. • Utility Coordination
o Inventory all existing utilities and potential conflicts. This includes but is not exclusive to utility crossings, water mains, storm sewer, and street lighting.
• Environmental o Investigate environmental impacts and provide a final environmental document
with the GDSU approved Level 1 Layout.
Projects for Consideration: There are numerous projects involving the City of Brainerd, Crow Wing County and several other potential stakeholders in the vicinity of the Washington Street Corridor. These projects are likely to be completed or in progress during the time in which the study is desired to take place. These projects all may have serious impacts to the characteristics of the corridor. It is required that all of these projects are monitored and taken into consideration with regards to the completion of this layout. Coordination and correspondence with all invested parties will be essential.
Upcoming projects and their anticipated construction dates include:
2019
• City of Baxter: Cypress Drive construction/expansion. • MnDOT Bridge #5060 Management Plan Study: A study by consultant to determine
best practices for preserving the bridge to provide a level of service that does not restrict permit vehicles along TH210 corridor and provides guidance for extending the service life of the bridge for an additional 10 to 40 years.
2020
• City of Brainerd: Possible signal relocation from 4th Ave NE to 5th Ave NE to accommodate for trail crossing.
• Cuyuna Lakes Trail: Trail connection and improvements in Brainerd. • Crow Wing County: CR 20/NW 4th St. resurfacing and roundabout.
2022
• MnDOT: Bridge #9099 replacement and coordination with City of Brainerd for trail connection with bicycle and pedestrian accommodations.
2025
• MnDOT: Bridge #5060 rehabilitation project with scope of work based on Management Plan Study.
• MnDOT: Washington Street Corridor Rehabilitation/Reconstruction with scope of work based on the layout of this study.
5
Scope of Work
Task 1: Project Management/Stakeholder Involvement (Source Code: 1010) This task focuses on effective communication of the project work to expedite the decision making process and maintain project schedule. It requires the Consultant to support MnDOT efforts to engage and involve local stakeholders and partners along the Washington Street corridor. The Consultant will be required to prepare a Project Management Plan. The Project Management Plan will be continually updated and will include such items as a summary of the project’s purpose and scope, schedule, project management approach and organization, and the Public Involvement Plan referenced below. The Project Management Plan will be submitted to MnDOT for review, revision and approval through the entire process.
Subtask 1.1: Public Involvement Plan
The Consultant will be required to prepare a Public Involvement Plan that will support MnDOT efforts to develop and maintain trust, awareness and understanding of the project among identified stakeholders. The corridor study represents an opportunity to engage local and regional project stakeholders in the identification of issues, planning goals and project visioning that leads to the identification and support of improvement alternatives for the corridor. MnDOT will also be a partner in public engagement throughout the project and should be updated frequently regarding plans and shared outreach opportunities. The Public Involvement Plan will be submitted to MnDOT for review, revision and approval.
Key Consideration of the Public Involvement Plan:
For the Public Involvement Plan to be successful, it should engage the impacted stakeholders early and often, be inclusive and address transportation infrastructure needs while balancing community needs and impacts.
Context
Demonstrate understanding of the project’s physical, historical and political context as well as the demographics, economy and physical environment of those who are impacted by the project.
Identify and evaluate land use context zones within the corridor by looking at adjacent land use; is it commercial, suburban, etc. and what is its relationship to the corridor and its users. Additional uses such as pedestrian and freight traffic should also be considered.
An understanding of the context equates to knowing the project’s audience and an understanding of the community’s underlying values and issues of importance, now and into the future. The project plan should demonstrate that vision and commitment to the community over time.
There are currently several initiatives that the City of Brainerd, ISD 181 and other groups are working on that can provide in-depth context for the corridor study, these include:
• Imagine Brainerd - https://imaginebrainerd.org/
6
• Blueprint 181 - https://blueprint181.org/ • Destination Downtown - http://www.downtownbrainerd.org/
Stakeholders
People who should be engaged in the project should be identified and contacted. Public engagement should be early and frequent throughout the study. To establish thorough representation of stakeholders for this project, they can be identified through the following questions:
• Who are the key decision-makers? • What organizations are here? • Who lives here? • Who works here? • Who visits here? • What under-represented communities need special-attention? • What specialized expertise is needed?
Parties who will potentially have interest or be affected by this project’s undertaking include the following:
• BNSF Railway • City of Brainerd
o Brainerd Housing and Redevelopment Authority o Mississippi Riverfront Committee o Planning Department o Review of the City’s Comprehensive Plan and Zoning Ordinances o Engineering Department o Brainerd Public Utilities o ADA Transition Plan o Walkable Bikeable City Committee o Brainerd Transit – Dial-a-Ride o Brainerd Law Enforcement
• MN DNR o Cuyuna Lakes Trail Association
• Brainerd Lakes Chamber of Commerce • Medical & Emergency Services • Brainerd Arboretum • Paul Bunyan Trail • ISD 181 School District • City of Baxter • Crow Wing County Highway Department • Adjacent Businesses
In addition to the potential stakeholders identified above, the Consultant will identify additional groups/individuals that should be engaged during the project. This should include under-represented populations, non-profit and community organizations, residents, workers, businesses, neighborhood organizations, etc.
7
Tactics
Determining how, when and where affected communities will be engaged. Specific planning and thought should go into how community engagement activities will be conducted to successfully achieve a collaborative and inclusive engagement process.
Activities selected for public engagement should go beyond informing and consulting and aim to involve and collaborate with stakeholders in the decision-making process.
Tactics for community engagement should consider outreach goals, reaching stakeholders early and often, resources available, seeking opportunities and addressing any special needs of the community.
Messages
Messages to communicate about the project should resonate with affected communities by speaking to community values and transportation needs. Messages should not only inform but also invite the community to collaborate and become involved in the decision-making process.
Evaluation
Assessment will be done to include the plan’s effectiveness. It will show how the Public Involvement Plan will be measured and evaluated. Results and outcomes will be communicated to MnDOT as part of progress reports and as a conclusion of the study.
Deliverables of the Public Involvement Plan:
• Stakeholder Database: A stakeholder database will be created and updated throughout the study.
• Timeline: A Public Involvement Plan Timeline should be created outlining key activities and corresponding dates with updates made as needed.
• Project Communication Strategy: This should be coordinated with MnDOT and will include the creation of project websites, social media and other channels for external communication regarding the project.
• Issues Matrix: The Public Involvement Plan will include the development and ongoing maintenance of an issues matrix that will identify audiences/audience segments, messages/talking points tailored to each audience/audience segment, communications goals/strategies/tactics, desired outcomes and feedback concerning the effectiveness of the strategies/tactics employed. The issues matrix will identify controversial issues encountered or anticipated, and how they will be addressed.
• Policymaker Input: The Consultant will develop and implement a process for obtaining feedback from key local, corridor and regional policymakers at key milestones throughout the project.
• Technical Workshops: The Consultant will plan and coordinate technical workshops involving technical staff from MnDOT and other county and city staff.
• Public Comment Register: The Consultant should track all public comments/feedback on the project and establish how a response will be provided to those comments.
8
Subtask 1.2: Progress Reports The Consultant will be required to prepare quarterly reports of progress and such other reports related to stakeholder and public involvement as needed for the project.
Subtask 1.3: Development of Information Materials The Consultant will be required to assist MnDOT in the preparation of materials that can be used at various stakeholder meetings including, but not limited to handouts, Powerpoint presentations, and other informational materials and displays as needed.
Subtask 1.4: Ongoing Internal Project Coordination The Consultant will be required to support efforts to update MnDOT internal functional groups, and meetings. This includes the preparation of meeting agendas, meeting materials, and meeting minutes.
Task 1 Deliverables and Due Dates Consultant
• Project Management Plan including a Project Schedule and Public Involvement Plan – Within 30 days of Notice to Proceed, maintained and updated throughout project
• Quarterly Progress Reports – within 30 days of the end of the quarter. Quarters are defined as Jan.–Mar., Apr.–Jun., Jul.–Sept., and Oct.–Dec.
• Meeting Agendas – 3 days prior to scheduled meetings • Meeting Minutes – Within one week after meeting • Project one-pager (s), PowerPoint presentations and other informational
materials/displays as needed – Within 30 days from Notice to Proceed. These will be maintained and updated as needed throughout the project
• Attendance at key project meetings.
All deliverables will be submitted in both electronic and hardcopy formats, unless otherwise notified by the MnDOT PM. All deliverables shall be provided to the MnDOT PM in native/original file type.
All deliverables must be provided in “Plain Language”, as defined in Governor Mark Dayton’s Executive Order 14-07 which requires the Office of the Governor and all Executive Branch agencies to communicate with Minnesotans using Plain Language. As defined, Plain Language is a communication, which an audience can understand the first time they read or hear it, thereby providing Minnesotans better state services by reducing confusion, saving time, and improving customer satisfaction. To achieve that, the following steps must be taken:
• Use language commonly understood by the public. • Write in short and complete sentences. • Present information in a format that is easy-to-find and easy-to-understand. • Clearly state directions and deadlines to the audience.
9
The Consultant shall ensure that all documents and content provided to MnDOT for posting on MnDOT’s public website, or shared electronically, meet the provisions the State of Minnesota’s Accessibility Standards: http://mn.gov/oet/images/Stnd_State_Accessibility.pdf including Minnesota’s accessibility standard for electronic documents. http://mn.gov/oet/programs/accessibility/electronic_documents.jsp. Also see: http://wwwdev.dot.state.mn.us/metro/consultants/adaplainlanguage.html Both state and federal ADA law requires that all documents posted online must be ADA compliant, which ultimately helps improve understanding among all audiences. MnDOT will provide the Consultant with access to resources for accessible documents, emails and webpages – as documents on its internal website at: http://ihub/communications/adaweb.
MnDOT
• List of potential stakeholders. • MnDOT Contacts.
Task 2: Operational Needs (Source Code 1003) The Consultant will summarize and gain consensus on user and stakeholder current and future needs along the corridor including safety issues, recurring congestion points, pedestrian and bicyclist requirements, and needs that maintain or enhance transit advantages. The Consultant will coordinate with the local agencies and MnDOT to identify planned and programmed improvements along the corridor. This can be developed through the review of existing documentation and reports such as the District 3 District Bicycle Plan. The project needs should identify existing and forecasted vehicle traffic and transit volumes, on-time transit performance, roadway congestion levels and causes, high crash areas, and other operational issues.
The evaluation of operational needs may extend beyond the corridor when considering bicycle travel as it relates to Washington Street. The District 3 District Bicycle Plan shows the Paul Bunyan Trail entering Brainerd from the west and the Cuyuna Lakes Trail entering from the east. However, bicycle routes through Brainerd have not yet been identified. In order to determine bicycle operational needs along the corridor, a high-level evaluation of bicycle connectivity through Brainerd is necessary.
Consultant will evaluate on-street parking utilization, needs, and removal to provide information for consideration of a roadway reconfiguration for cross-sectional balance for multi-modal needs.
Task 2 Deliverables and Due Dates Consultant
• Draft Needs Assessment-October 2019 • Final Needs Assessment-April 2020
10
Task 3: Traffic/Corridor Analysis (Source Code 1808) The Consultant will perform a study of current conditions along the corridor in order to determine the vehicle Level-of-Service and any capacity, flow or other issues or concerns that are occurring. The Consultant will use the results of this study and stakeholder input to recommend improvements and/or mitigation strategies along Washington Street. The Consultant will develop conceptual layout alternatives pertaining to the needs of the project addressed in this scope of work as well as any other findings obtained throughout the course of this corridor study. The Consultant will provide associated cost estimates for each conceptual alternative according to the criteria defined in the following tasks.
Subtask 3.1: Traffic Operations Analysis – Identify Needs • Safety Analysis
Consultant will perform a safety analysis of the corridor and existing intersections studied within the corridor. The vehicle safety analysis will be based upon the most recent seven years of crash data available from State Patrol. Pedestrian and bicycle safety analysis will be based upon the most recent seven years of data. Crashes will be sorted by type, location and severity. Crash rates, Severity rates, and Crash Indexes will be calculated and compared to District and Statewide averages for similar facilities. Crash frequency, for those types of crashes considered to be potentially correctable, will be documented for the intersections being studied in the corridor.
• Existing and Future Vehicle Traffic Conditions
A capacity analysis of existing and future forecasted traffic volumes for the intersections and corridor will be performed for the existing weekday PM peak hour conditions. The Consultant will calculate forecasted traffic volumes based on historical traffic volumes provided by MnDOT. An additional analysis with a percentage increase determined by the consultant of TH 210 PM peak hour traffic should be performed to reflect peak summer weekend recreational traffic times conditions.
A model and operational analysis will be conducted for Existing 2017 and Year 2037 design hour traffic conditions using VISSIM traffic operations analysis software. The result will be an analysis of future operation conditions for the TH 210 Washington Street corridor assuming existing geometric and traffic control conditions. The traffic operations analysis will allow the identification of future operating deficiencies along the TH 210 Washington Street study segment and will be a key component in identifying future improvement needs. Intersection Control Evaluations for any intersection control changes.
• Pedestrian and Bicyclist Operational Evaluation
Consultant will perform an assessment of pedestrian and bicyclist travel along the corridor. This includes an evaluation of ADA needs, sidewalk widths, crossing locations, access to key destinations, and bicycle facilities. This assessment may consist of both quantitative and qualitative reporting of existing and future conditions along the corridor.
11
The information evaluated in this task will also be used in the comparison of alternatives in Subtask 3.2.
• Freight and Commercial Vehicle Operations
Contractor will perform an assessment of freight and commercial travel along the corridor. This will involve evaluation of the amount of use, areas of critical movements, and geometric constraints/opportunities. John Hausladen, President of the Minnesota Trucking Association would be an industry contact for external discussions. Discussions with MTA will need to be measured.
Subtask 3.2: Identify Geometric/Traffic Control Alternatives. Consultant will review future operational conditions on TH 210 and evaluate any possible safety/capacity improvements for the intersections along this corridor.
Intersections of particular interest (but not limited to) with the Washington Street Corridor include:
• Baxter Drive/Charles Street • CSAH 20/NW 4th • 4th Street • TH 371B • CR 45 • 4th Ave NE/RR Shop entrance possibly moving to 5th Ave NE • TH 25/CR 3 and configuration of the entire operations from 5th Ave NE to 10th Ave
NE (mall access and commercial movement). • Any other no signalized intersection that could warrant improvements.
Cost benefit analysis will need to be completed for each alternative considered at an intersection deemed worthy for a possible improvement. Alternatives evaluated may include any solution to benefit the corridor.
Subtask 3.3: Traffic Operations Analysis/Simulation-Assess Traffic Control Options
• Conduct traffic operations analyses for the improvement concepts identified in Task 3 using VISSIM operational analysis software for future conditions.
• CAPX software should be used for checking the general capacity of each alternative and RODELL software should be used for detailed roundabout capacity analysis if needed.
Subtask 3.4: Develop Conceptual Alternatives • Working with the stakeholders and public input, the Consultant will develop design
concepts to be incorporated in the level 1 layout for the Washington Street corridor. In addition to the stakeholders listed in Task 1, MnDOT internal stakeholders include:
o ADA o Bridge Office
12
o GDSU o Office of Freight o Ped and Bike Unit
• The Consultant will develop conceptual alternatives incorporating the analysis of conflict points along the corridor and concepts for corridor improvements at such points at locations, including but not limited to the following:
o Inclusion of FHWA Safe Transportation for Every Pedestrian (STEP) proven countermeasures, where applicable.
o Curb ramps at intersections will need to be upgraded to meet MnDOT standard.
o All signalized intersections will need to be upgraded to accessible pedestrian signals (APS).
o Sidewalk at back of curb in commercial areas (with buildings at back of walk) should be widened reasonably to accommodate amenities and pedestrian access routes (PAR).
o Sidewalk deficiencies need to be addressed (cross-slopes, trip hazard, bad condition, etc).
o Evaluate for any new/necessary sidewalk connection. o Existing structure/poles need to be relocated to outside of PAR. o Trail repair if they are not on limited use permit (LUP) property. o Side path or road shoulder needs to accommodate for bicycles and pedestrians
between Pine Shores Rd and 14th Ave NE. o Coordination of any changes to Bridge #5060 with the City of Brainerd’s
desires for a river walk. o Evaluate three scenarios with Bridge #5060. MnDOT will evaluate the load
rating of scenario #2. 1.) Impacts to the corridor if no changes were made to the cross-section
on Bridge # 5060. 2.) Impacts to the corridor based on a new cross-section at Bridge # 5060
that fits within the existing roadway width of 64’-0” on the bridge. Note that the existing sidewalks widths must be maintained as minimum based on structural load rating requirements.
3.) Desired cross-section if Bridge # 5060 where to be replaced with a new bridge.
o Potential changes to the existing cross section which would positively impact the corridor.
o Right of way constraints/opportunities. o Access issues for various business locations along the corridor. o Evaluation of freight and commercial vehicle movements. o Accommodation of RR right of way along the corridor and at the BNSF
Brainerd Maintenance Yard. o RR xing at 1st Ave NE and the potential need for this. o All aspects of the projects which may impact the Washington Street Corridor
listed in “Projects of Consideration” prior to scope.
13
Subtask 3.5: Develop Evaluation Criteria and Measures The Consultant will develop criteria and measures for screening and evaluating the layout concepts. This criteria should include pedestrian and bicyclist safety and mobility and should be consistent with the project goals and MnDOT long range transportation plans. The Consultant will evaluate each of the layout options against these criteria.
The Consultant will also develop a priority assessment of each section of the corridor. The consultant will determine which section of the corridor is the highest priority according to the evaluation criteria.
Task 3 Deliverables Consultant
• PowerPoint presentation(s) and other informational materials/displays for agency and public information sharing
• Notification to MnDOT of any outstanding findings, especially those having an immediate impact on the safety of the traveling public, that need to be addressed prior to the project’s construction.
• Highlighting potential layout changes resulting from this analysis in quarterly progress reports.
• Implementation of findings from the analysis in the Consultant’s conceptual alternatives.
• Evaluation table(s) • ICE reports for any intersection control changes. • Technical memorandum (Microsoft Word) documenting safety analysis and traffic
operations analysis findings - with existing and future traffic demands o Crash diagrams for each intersection. VISSIM traffic model of existing and
future traffic volumes. o Document measures of effectiveness (i.e., LOS for existing conditions and
future volumes. • Technical memorandum identifying concepts considered and qualitative assessment
of constraints and impacts o Conceptual typical sections for improvement concepts (previously developed
sections will be utilized where appropriate) o Representative intersection/access concept plans (geometric layouts) at along
the entire study corridor. o Assessment of key corridor constraints and impact assessment review.
• Technical memorandum (Microsoft Word) reporting results of warrant evaluation and traffic operations analysis
o Preliminary traffic signal warrant assessment o Signalized operational analysis o Roundabout operational analysis o RCI capacity results
• Conceptual alternatives for the Washington Street corridor rehabilitation/reconstruction project.
14
• Cost estimates for each layout concept including right of way estimate, capital costs and life cycle costs.
MnDOT
• Crash data along the corridor. • Historic traffic counts. • Survey data including existing alignment and right of way information. Lidar data
will be available to consultant by early 2020. • Pavement and material recommendations. • Existing and proposed typical sections. • County GIS parcels. • Existing plans for the modification of the storm sewer system as well as other
drainage features.
Task 4: Benefit/Cost Analysis (Source Code: 1805) A benefit-cost analysis will be conducted by the Consultant for one no-build and up to three build scenarios to understand the economic tradeoffs of investments identified for the Washington Street corridor. This analysis will evaluate incremental differences between each of the alternatives identified for consideration. The objective of a benefit-cost analysis is to translate the effects of an investment into monetary terms and to account for the fact that benefits generally accrue over a long period of time while capital costs are incurred primarily in the initial years. The primary transportation-related elements that can be monetized are travel time costs, right of way impacts, construction material costs, vehicle operating costs, safety costs, ongoing maintenance costs, remaining capital value, if any, to the end of the project life. The benefit-cost analysis will provide an indication of whether travel time and safety savings exceed the costs of design, construction, and long-term increased operating costs. A benefit-cost analysis provides a monetary measure of the relative economic desirability of project alternatives, but decision-makers often weigh the results against other non-monetized effects and impacts of the project, such as environmental impacts.
Task 4 Deliverables
Consultant:
• Technical Memorandum summarizing methodology, assumptions and findings of Benefit/Cost analysis of alternatives.
• PowerPoint presentation for agency and public information sharing.
MnDOT:
• High level cost estimate of the three bridge scenarios.
15
• Task 5: Level 1 Layout (Source Code: 1010) The consultant will create a final layout based on the analysis and findings from the corridor study and other tasks listed above. This will be a GDSU approved Level 1 Layout with municipal consent and a final environmental document. In addition, the Consultant will document any change in impervious surface resulting from the final layout. The layout will include all elements and requirements described in the tasks of this document and construction limits to determine impacts. Guidance on layout development, design standards, and exceptions can be found at their website at http://www.dot.state.mn.us/design/geometric/ .
Subtask 5.1: Environmental Documentation
Class II Environmental Document:
• The Consultant will prepare a Class II Environmental Document (CATEX) for approval with the following assumptions:
• Project meets the definition of a Class II Action (non-programmatic Categorical Exclusion) under NEPA.
• Environmental document is a non-programmatic, long-form Categorical Exclusion (CATEX) document.
• Proposed improvements do not meet the threshold for mandatory EAW under Minnesota Environmental Quality Board (MEQB) rules. If MnDOT (as the responsible governmental unit (RGU) for projects on state trunk highway system) determines that a discretionary EAW is necessary, additional scope will be prepared.
• Assumes District 3 has completed Early Notification Memo (ENM) review process and will provide ENM responses for completion of CATEX.
• Assumes District 3 will coordinate draft and final CATEX reviews and approvals with MnDOT Office of Environmental Stewardship (OES) and FHWA.
• Assumes no noise analysis is required. • Assumes no Section 3 (Endangered Species Act) consultation required. Assumes a
determination of no effect from OES. • Assumes no use of Section 4(f) property and that all conditions in 23 CFR 774.13(d)
can be met for any potential project impacts. • Assumes no Section 6(f)/LAWCON involvement. • Assumes no low income and/or minority populations within the study area and no
additional public outreach necessary to satisfy environmental justice review requirements.
• Assumes a qualitative MSAT analysis per Interim Guidance on Air Toxic Analysis in NEPA Documents Feb. 3, 2006 (or current) FHWA Memo. Assumes no quantitative air quality modeling (MSAT and CO) required.
• Assumes “no adverse effect” to Section 106 (historic) properties with the determination to be provided by MnDOT Cultural Resources Unit (CRU) in response to ENM. Any cultural resources studies (architectural history and/or archaeology), if required, will be prepared by MnDOT CRU.
16
• Phase I environmental site assessment (ESA) requirements to be determined by MnDOT Environmental Investigation Unit (EIU). Assumes a Phase I ESA, if required, will be prepared by EIU.
Environmental Document Coordination:
The Consultant will perform on-going coordination with MnDOT District 3 staff during development, processing and approval of the CATEX document including agency coordination.
Subtask 5.2: Design Memo
The consultant will prepare a design memo in conjunction with the Level 1 layout. This is a requirement of GDSU when submitting a layout for approval.
Task 5 Deliverables Consultant:
• GDSU approved Level 1 layout of the corridor which has municipal consent. • Documentation of the percent change of impervious surface. • Storm water treatment options for any net increase of storm water flow resulting from
the layout. • Modifications needed to existing storm water collection system. • Final environmental document (Non-Programmatic Categorical Exclusion) included
with layout. • Design Memo.
MnDOT:
• Early Notification Memo.
17
MnDOT Contacts for Assistance • District 3
o District Engineer Dan Anderson, District Engineer
• [email protected] • 218-828-5700
o Assistant District Engineer, Program Delivery Jim Hallgren
• [email protected] • 218-828-5797
o Assistant District Engineer, Maintenance Jamie Hukriede
• [email protected] • 218-828-5705
o Assistant District Engineer, Construction Cal Puttbrese
• [email protected] • 218-828-5704
o Project Development Engineer Darren Nelson
• [email protected] • 218-828-5760
o Traffic Tom Dumont, District Traffic Engineer
• [email protected] • 320-223-6540
o Tony Hughes Resident Construction Engineer
• [email protected] • 218-828-5735
o District Materials Engineer Sara Johnson
• [email protected] • 218-828-5747
o Surveys Kevin Metz, District Principal Land Surveyor
• [email protected] • 218-828-5761
o Hydraulics Bob Miller, District Hydraulics Engineer
• [email protected] • 218-828-5792
18
o District Right of Way Engineer Kevin Schmidt
• [email protected] • 218-828-5801
o Transportation Planning Director Steve Voss
• [email protected] • 218-828-5779
o Bridge Adam Ahrndt, District Bridge Engineer
• [email protected] • 320-223-6502
• CO/Metro o ADA Design Program Engineer
Todd Grugel • [email protected] • 651-366-3531
o Pedestrian and Bicycle Safety Engineer Sonja Piper
• [email protected] • 651-234-7376
o Geometrics Design Support Unit [email protected]
o MnDOT Rail Office Rick Van Wagner
• [email protected] • 651-366-3713
o MnDOT Freight Office (regional freight/oversize-overweight and truck permits) Andrew Andrusko
• [email protected] • 651-366-3644
