I-494/TH 62 Mnpass Managed Lane Concept Development Scope of Work (Final Draft – 11/17/14)

I-494/TH 62 MnPASS Managed Lane Concept Development Scope of Work (Final Draft – 11/17/14)

BACKGROUND Interstate 494 and Trunk Highway 62 experience significant, recurring congestion during peak periods. The 2012 Average Annual Daily Traffic (AADT) volumes for I-494 between TH 62 and the Minneapolis-St. Paul Airport range from 72,000 to 160,000 vehicles a day. The 2012 AADT volumes on TH 62 between I-494 and the MSP Airport range from 89,000 to 106,000 vehicles a day. The Metropolitan Freeway System 2013 Congestion Report shows congestion on I-494 and TH 62 ranging from under an hour to greater than three hours at certain locations in the morning and afternoon peak periods. In recent years, MnDOT, along with other governmental agencies, has conducted a variety of long and short-term planning activities that establish a general policy framework for future operation and condition of the I-494 and TH 62 corridors. These planning initiatives and studies include: • 2010 Metropolitan Council 2030 Transportation Policy Plan • 2010 Metropolitan Highway System Investment Study • MnPASS System Studies 1 (2005) and 2 (2010) • 2012 CMSP III Study • 2014 Minnesota State Highway Investment Plan • 2014 TH 77 Managed Lane Study • 2014 I35W-I494 Interchange Vision Layout • MAC Study of I-494/TH 5 Interchange

OBJECTIVE The Minnesota Department of Transportation (MnDOT) is requesting proposals to support MnDOT and its partners in the development and evaluation of MnPASS managed lane improvements, spot mobility improvements and other transit advantage improvements on the I- 494 and TH 62 corridors. The project area for the I-494 corridor segment is about 18 miles in length and includes the area between TH 62 on the west, to the MSP Airport on the east via TH 5. The project area for TH 62 corridor segment is about 12 miles in length and includes the area between I-494 on the west, to the MSP Airport on the east via TH 55. The goals for any recommended improvements to the I-494 and TH 62 corridors will include: 1. enhancing safety and mobility by providing congestion free options for bus transit, car/vanpools, and other commuters during peak rush hour periods 2. utilizing existing infrastructure, right-of-way and performance based design principles to the maximum extent possible, as well as other lower cost/higher return-on-investment strategies 3. coordinating implementation recommendations with other planned and programmed investments

4. enhancing or maintaining advantages for transit, including taxi cabs, airport park and rides, airport shuttles, ride sharing and non-motorized connections 5. increasing corridor person throughput and travel time reliability (both reliability related to recurring congestion and non-recurring congestion as demonstrated by SHRP 2 Reliability and Data Analysis tools – see: http://www.fhwa.dot.gov/goshrp2/Solutions/Reliability/L02_L05_L07_L08_C11/Reliabil ity_Data_and_Analysis_Tools) 6. Improving and enhancing economic vitality

The above goals will be subject to refinement based on stakeholder input early in the study process. All recommendations must be consistent with current state and regional transportation plans.

SCOPE OF WORK Task 1: Project Management/Stakeholder Involvement This task focuses on effective communication of the project work to expedite the decision making process and maintain project schedule. It requires the Contractor to support MnDOT efforts to engage and involve local stakeholders and partners along the I-494 and TH 62 corridors. It assumes Contractor involvement for eighteen (18) months from Notice to Proceed, however, a majority of the work is expected to be completed within the first twelve (12) months of the project. The Contractor 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.

Subtask 1.1: Technical Steering Committee The Technical Steering Committee (TSC) will consist of technical staff representing, but not limited to, the following stakeholders:

• City of Minnetonka • Hennepin County • • City of Eden Prairie Metro Transit • • City of Edina Southwest Transit • • City of Bloomington Minnesota Valley Transit • • City of Richfield Metropolitan Council • • City of Minneapolis Metropolitan Airports Commission • • Scott County Federal Highway Administration

• Dakota County

The TSC will provide oversight and direction for the study and the Contractor Team. To involve the TSC, the Contractor will schedule meetings (suggested 1 per month) for the duration of the

project and develop agendas and meeting minutes for all meetings. Additional working group meetings and/or subgroup meetings may also be scheduled as needed.

Subtask 1.2: Public involvement with I-494 Corridor Commission, I-35W Solutions Alliance, and Others. The Contractor 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, including the I-494 Corridor Commission, the I-35W Solutions Alliance, local agencies, transportation/transit advocacy groups and others along the corridor, as needed. The Public Involvement Plan will be continually updated and include a stakeholder database (mailing/contact list) and issues matrix. The matrix will identify audiences/audience segments, messages/talking points tailored to each audience/audience segment, communications goal(s)/strategies/tactics, desired outcomes and feedback concerning the effectiveness of the strategies/tactics employed. The Public Involvement Plan will be submitted to MnDOT for review, revision and approval.

Subtask 1.3: Coordination with the Metropolitan Airports Commission (MAC) Coordinate with the MAC for improved access and connection opportunities at Minneapolis/St. Paul International Airport (MSP) that are consistent with MnDOT policies and plans, and consistent with the MSP Long Term Comprehensive Plan (LTCP).

Subtask 1.4: Progress reports The Contractor will be required to prepare quarterly reports of progress and such other reports related to stakeholder involvement as needed for the project.

Subtask 1.5: Development of informational materials The Contractor 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.6: Ongoing Internal Project Coordination The Contractor 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.

Subtask 1.7: Coordination with TH 169 Transit and MnPASS Managed Lane Study The Contractor will be required to coordinate with the TH 169 Transit and MnPASS Managed Lane Study. This includes close coordination of forecasting and modeling methodology and

3 implementation, as well as concept development and evaluation. The Contractor will be required to attend study meetings and provide progress updates as needed. It also includes coordination and consistency with other MnPASS Managed Lane studies.

Task 1 Deliverables and Deliverable Due Dates • Project Management Plan including a Project Schedule and Public Involvement Plan – Within 30 days of Notice to Proceed, maintained and updated throughout project • Quarterly 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; and • Clearly state directions and deadlines to the audience.

The Contractor 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 Contractor with access to resources for accessible documents, emails and webpages – as documents on its internal website at: http://ihub/communications/adaweb.

Task 2: Assess and Document Operational Needs in the I-494 and TH 62 Corridors The Contractor will summarize and gain consensus on user and stakeholder current and future (2040) needs along the corridor including safety issues, recurring congestion points, known bottlenecks, and needs that maintain or enhance transit advantages. The Contractor 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. The project needs should identify existing and forecasted traffic and transit volumes, on-time transit performance, congestion levels and causes, high crash areas, and other operational issues. . The Contractor is encouraged to use relevant and readily available data sources (e.g., LEHD, CTPP, TBI-2010, the Home Interview Survey, the Transit on-Board Survey, the Airport Special Generator Study, and the Mall of America Special Generator Study from the 2010 TBI) to analyze travel sheds for the study area corridors by major planning segments. The corridors should be assessed in logical segments based on key travel and geometric characteristics.

Task 2 Deliverables and Deliverable Due Dates • Draft Needs Assessment – no later than 4 months after Notice to Proceed. • Final Needs Assessment – no later than 6 months after Notice to Proceed.

Task 3: Develop Concept Layouts and Cost Estimates Subtask 3.1: Develop Design Concepts Working with the TSC and other corridor stakeholders, the Contractor will develop MnPASS managed lane design concepts, spot mobility improvement design concepts and other transit advantage design concepts for I-494 from TH 62 to the MSP Airport via TH 5; and TH 62 from I-494 to the MSP Airport via TH 55, in the Cities of Minnetonka, Eden Prairie, Edina, Bloomington, Minneapolis and Richfield. These design concepts will include: • Single line/lane continuity diagrams and lane schematic drawings for individual segments of the corridor • Analysis of conflict points along the corridor and conceptual layouts for improvements at such points at locations, including but not limited to the following:

o I-494/TH 77 Interchange I-494 at 12th/Portland/Nicollet o th o I-494/24 Avenue Interchange o I-494/TH 100 o TH 62/TH 77 Interchange

• Priority assessment of each section of the corridor • Analysis of the synergies/impacts between existing and potential future MnPASS lanes

After preliminary review of the design, evaluation criteria, cost, forecast and modeling results, additional design concepts may be required. These may be new concepts or hybrid approaches to the initial concepts. The additional concepts will also evaluate cost and operational comparisons among alternatives that either meet standards or require design exceptions. The Contractor will develop single line lane continuity diagrams and lane schematic diagrams to assist with initially screening design concepts. The Contractor will develop alignments, profiles, and typical sections for each design concept included in a build scenario. These project alignments will be developed to the extent practicable using current State Standards (including MicroStation V8) for layout development and in accordance with the HPDP handbook, incorporated by reference.

Subtask 3.2: Develop Evaluation Criteria and Measures The Contractor will develop criteria and measures for screening and evaluating the design concepts consistent with the project goals, past MnPASS studies such as the MnPASS System 2 Study, and MnDOT and Met Council long range transportation plans. The Contractor will evaluate each of the design options against these criteria.

Subtask 3.3: Develop of Cost Estimates For each of the developed concepts, the Contractor will provide cost estimates including capital costs and life cycle/operations costs. Capital costs will include high level estimates of noise wall and right-of-way costs.

Task 3 Deliverables • Single line/lane continuity diagrams and lane schematic drawings for initial screening and evaluation of design concepts • Preliminary alignments, profiles, and typical sections for each design concept used in a build scenario, • Evaluation table(s) • Cost estimates for each design concept including capital costs and life cycle costs, including noise wall, right-of-way and hydraulic costs, • PowerPoint presentation(s) and other informational materials/displays for agency and public information sharing

Task 4: Multi-Resolution Modeling (MRM) and Analysis The contractor will develop a proposed Multi-Resolution Modeling process for analyzing a range of corridor improvements and strategies for both opening year and the planning horizon year. The exact amount of macroscopic, mesoscopic and microsimulation modeling required will be determined by which model offers the most appropriate and useful tool for analyzing various improvements and strategies under consideration. The MRM process should consider how these

models relate to each other and consider feedback loops between models where appropriate to improve overall modeling performance and robustness. Maximum numbers of model runs are listed under the subsequent subtasks for estimating resources required for the project. Contractors are encouraged to provide cost/hour estimates for additional model runs that may be requested during the course of the project. Upon determination of the corridor vision and development of the implementation plan, the modeling methodology should be adequately designed to use for analyzing construction zone phasing used in developing the corresponding Traffic Management Plan (TMP). TMP forecasting and modeling should be identified as an optional task separate from the subtasks described below.

Subtask 4.1: Travel Demand Forecasting The Contractor will develop travel demand forecasts using the most recent version of the Twin Cities Regional Travel Demand Forecast Model. The Contractor will review the regional model validation of the study corridors for the base year against observed data (for highway Single Occupant Vehicles and High Occupant Vehicles, and transit ridership). Highway Annual Average Daily Traffic (AADT) and AM/PM peak period AWDT volume forecasts will be developed for the study corridors, parallel corridors, major cross streets, and interchange access/egress ramps. Forecasts will be developed for general purpose lanes, managed lanes, and the transit system. A refined base year model (2015) will be developed and model runs will be completed for up to three (3) alternative build scenarios for the planning horizon year (2040), and one (1) no-build alternative. The travel demand modeling methodology should be consistent with the guidelines and reasonableness checks described in MnDOT’s Revised Guidelines for Twin City Travel Demand Forecasts Prepared for the Metropolitan District memorandum dated May 10, 2006.

Subtask 4.2: Mesoscopic Dynamic Traffic Assignment (DTA) Modeling The Contractor will develop a mesoscopic DTA model for the study area to provide more refined and robust analysis, particularly of queuing and route diversion of the proposed managed lane alternatives under consideration. Output from the mesoscopic DTA model output serve as the input to any microsimulation (e.g. CORSIM, Vissim) modeling where needed to address issues and concerns not adequately or appropriately addressed in the macro and mesoscopic model. A base year model will be developed and validated and up to three (3) alternatives will be modeled. Modeled peak period ramp to ramp volume origin/destination trips will be developed as input to the to a traffic microsimulation modeling process. The Contractor is encouraged to propose mesoscopic modeling processes and software package options that would generate an effective analysis tool and provide useful and meaningful data for assessing project alternatives. MnDOT currently has a contract to develop a DynusT model for analyzing traffic impacts for several Hennepin County area construction projects. This modeling product may be available to the contractor from which to build a modeling tool for this corridor.

Subtask 4.3: Origin Destination Assessment

a. The Contractor will utilize the Twin Cities Regional Model and any other readily available data (e.g., LEHD, 2010 TBI, etc.) to evaluate and assess the origins and destinations of trips using the study corridors. b. The contractor should recommend 3rd party data options (e.g, AirSage, Bluetooth, Inrix, etc.) for further evaluation of origin/destination patterns for the study area travel shed. This data should increase the overall understanding of corridor usage by time of day as well as improving model validation. Such data should help determine trip lengths, trip types, usage patterns, and reliability along the corridors. This is an optional task to be priced out separately.

Subtask 4.4: HOT Traffic and Revenue Analysis The Contractor will forecast MnPASS users for each MnPASS alternative. The Contractor will forecast HOV demand, transit demand and toll paying SOV demand and project corresponding toll revenues.

Subtask 4.5: Transit Operations and Ridership Forecasting Working with the transit partners along the corridor, the Contractor will forecast 2040 transit ridership along the study corridors with and without the proposed improvements. Transit assumptions in the corridor will be verified and/or developed with transit planners and appropriate changes made to the model transit network as needed. Travel times on the transit network will be reviewed and revised as necessary to reflect the presence transit advantages being analyzed. The Contractor will forecast 2040 Carpool and/or Vanpool usage along the TH 62 and I-494 corridors for the existing condition and the proposed condition, and be able to forecast person throughput for alternatives being considered.

Subtask 4.6: Microsimulation Modeling and Analysis The Contractor will model and analyze spot locations and preferred design concepts for 2020 and 2040 (up to two scenarios) using microsimulation modeling as early in the process as possible. The modeling will conform to the current “MnDOT Modeling Guidelines” that can be found at the internet web site, www.dot.state.mn.us/trafficeng/index.html, and are incorporated herein by reference. Existing conditions modeling should be verified and approved by MnDOT traffic operations staff prior to further analysis. All travel demand forecasts must be approved by the Metro District Traffic Forecaster prior to the microsimulation modeling of alternatives.

A CORSIM model was developed for segments of these corridors. MnDOT will provide these files, which includes CORSIM files, link-node diagrams, and lane schematics for the existing conditions and build-scenarios studied.

Task 4 Deliverables • Document summarizing methodology and assumptions used for macro and mesoscopic model validations, model development, and reasonable checks. • Forecasts for the following years: Year of opening (2020) and design year (2040), including average annual daily traffic, AM peak hour, and PM peak hour (with a breakdown of projected SOV, Car/Van pool, and Transit Bus trips using managed lanes. • One paper and one electronic copy of the draft report, three copies of the final report plus one electronic copy in pdf and one in MS Word copy. • Graphic representation (i.e. maps) of existing volumes plus forecast years 2020 and 2040. • All relevant electronic files of macro and mesoscopic model runs. • Microsimulation technical memorandum and PowerPoint slides for agency and public information sharing. • Traffic simulation modeling of each spot location design and preferred design concept ( up to two scenarios). • Summary of operations analysis on I-494 and TH 62.

Task 5: Benefit/Cost Analysis A benefit-cost analysis will be conducted by the Contractor for one no-build and up to three build scenarios to understand the economic tradeoffs of investments identified for the I-494 and TH 62 corridors. 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, 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 5 Deliverables • Technical Memorandum summarizing methodology, assumptions and findings of Benefit/Cost analysis of alternatives considered. • PowerPoint presentation for agency and public information sharing.

Task 6: Develop Short and Long Term Recommendations and Implementation Plan. In Consultation with MnDOT, the Technical Steering Committee and other project stakeholders, and based on what was learned over the course of the study, the Contractor will develop short and long term recommendations including phased implementation plan. The recommendations will also discuss how to finance a project based on revenue forecasts and cost estimates from previous tasks. The Contractor will identify any legal, legislative, and policy issues that may need to be addressed with these recommendations.

Task 6 Deliverables • The deliverables will include a technical memorandum and PowerPoint slides for agency and public information sharing.

Task 7: Community Outreach and Education As part of the required Public Involvement Plan (Task 1, Subtask 1.2), the Contractor will be required to develop, implement and document results of a Community outreach and education effort that will support MnDOT efforts to develop and maintain trust, awareness and understanding of the project.

Subtask 7.1: Policymaker Input The Contractor will develop and implement a process for obtaining feedback from key local, corridor and regional policymakers at key milestones throughout the project. Subtask 7.2: Technical Workshop The Contractor will plan and coordinate up to two technical workshops involving technical staff from MnDOT, Met Council, FHWA, MAC, and other county and city staff including others not actively involved in the Technical Steering Committee. Subtask 7.3: Public Open House The Contractor will plan up to two open houses for the general public on the corridor. The Contractor shall provide a summary of the issues and opinions expressed at the two open houses. Subtask 7.4: Additional Community Outreach and Meetings When requested, the Contractor will provide presentations to elected officials, transportation/transit advocacy groups, and other interest groups. Subtask 7.5: Project Website The Contractor will be responsible for supporting MnDOT staff in the development and maintenance of a project website (both internal and external) and creative use of other social media outlets (e.g. twitter).

Task 7 Deliverables and Due Dates

• Documentation summarizing the issues and opinions expressed through the policymaker input process, the technical workshop, and public open houses – within 2 weeks of open house or workshop • Project Website (s) – within 30 days of project start and updated as needed.

MnDOT Assistance • TH 62/I-494 Bridge and Pavement Condition Information • Three Year Crash Data • Most Recent Aerial Photos • Information on Planned and Programmed Projects • The 2010 MnPASS System 2 Study • All studies and information prepared on the I-494 and TH 62 Corridors o Environmental Documents o Traffic Reports o Other Studies.