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 1 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 2 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