exhibit a – scope of work and deliverables...9.1 drainage spread and urban vs. rural analysis (p6...

MnDOT Contract No. 1037007

Exhibit A – Scope of Work and Deliverables

1

General Information and Requirements 3 Background 3 Draft Schedule & Contract Completion Timeline 3 Source Type Codes and P6 Activity Codes 3 Standards 4 Items provided by State 4 Plain Language and Accessibility Standards 4

Plain Language 4 Accessibility Standards 4

Project Management, Coordination, and Meetings (Source Type 1010) 5 1.1 Schedule (Source Type 1003) 5 1.2 Initial Project Coordination Meeting (P6 Activity OPM1000) 5 1.3 Internal and External Team Coordination (P6 Activity OPM1000) 6 1.4 Project Management Team (PMT) Meetings (P6 Activity OPM1000) 6 1.5 Monthly Progress Meetings (P6 Activity OPM1000) 6 1.6 Project Instructions, Work Plan, and Quality Assurance (P6 Activity OPM1000) 7 1.7 Subcontractor Management and Oversight (P6 Activity OPM1000) 7 1.8 Risk Analysis and Tracking (P6 Activity OPM1000) 7

Public and Agency Involvement (Source Type 0054) 7 2.1 Public Involvement Plan (PIP) 7 2.2 Project Analysis (P6 Activity PIP1000) 8 2.3 Stakeholder Identification (P6 Activity PIP1010) 9 2.4 Conflict Identification (P6 Activity PIP1020) 10 2.5 Conflict Mapping (P6 Activity PIP1030) 10 2.6 Conflict Assessment (P6 Activity PIP1040) 10 2.7 Public Involvement Strategy (P6 Activity PIP1050) 10 2.8 Electronic Communications (P6 Activity OPM1010) 11

Alternatives Charrette Facilitation (Source Type 1010) 11 3.1 Review work completed to date (P6 Activity CAH1000) 11 3.2 Conduct Charrette (P6 Activity CHA1010) 11

3.2.1 Facilitation 11 3.2.2 Base Mapping 12 3.2.3 Charrette Summary 12

3.3 Identify and Develop Alternatives 12 3.3.1 Frame alternatives (P6 Activity CHA1020) 12

Deliverable 3.3.1: 12 3.3.2 Review alternatives (P6 Activity CHA1030) 12

Deliverable 3.3.2: 13 3.3.3 Final Summary Report (P6 Activity CHA1040) 13

Environmental Documentation (Source Type 1071) 13 4.1 Early Notification Memo (ENM) (P6 Activity ENM1000) 13 4.2 Purpose and Need Statement (P6 Activity AAA1110) 14 4.3 Alternatives Evaluation (Source Type 1071) (P6 Activity PMM1020) 14

4.3.1 Alternatives Screening 14 4.3.2 Alternatives Meeting Support 15 4.3.3 Alternatives Evaluation 15 4.3.4 Logical Termini Analysis and Report 15

4.4 Work To Be Completed by Contractor 15 4.4.1 Benefit-Cost Analysis (P6 Activity AAA1300) 15 4.4.2 Traffic 16 4.4.3 Visual Impact Assessment 16


Exhibit A-– Scope of Work and Deliverables

2

4.4.4 Considerations Relating to Pedestrians and Bicyclists 16 4.4.5 Public and Agency Involvement 17

4.5 Meeting Support (Source Type 1010) 17 4.5.1 Noise Mitigation Meetings (P6 Activity NOI1055) 17

Existing Traffic Conditions Report (Source Type 1016) (P6 Activity TOA1000) 17

Traffic Operations Analyses (Source Type 1250) 18 6.1 Initial Traffic Operations Meeting (P6 Activity TOA1010) 18 6.2 Alternative Evaluation Modeling (P6 Activity TOA1020) 18

6.2.1 VISSIM Analysis for Alternative Evaluation 19 6.2.2 VISSIM Analysis Report for Alternative Evaluation 19 6.2.3 VISSIM Analysis Meetings 19

6.3 Travel Demand Forecasts (P6 Activity TOA1030) 19 6.3.1 Travel Demand Forecasts for Alternative Evaluation 20 6.3.2 Sensitivity Analysis on Travel Demand Modeling 20 6.3.3 Travel Demand Forecasting Memorandum/Report 20 6.3.4 Travel Demand Forecasts Meetings 21

6.4 Microsimulation Modeling and Analysis (P6 Activity TOA1040) 21 6.4.1 Building of Base Model 21

6.4.1.1 Base Model Calibration Report 21 6.4.2 Year 2025 No-Build Scenario Traffic Analysis 22 6.4.3 Year 2045 No-Build Scenario Traffic Analysis 22 6.4.4 Year 2025 Preferred Alternative Traffic Analysis 22 6.4.5 Year 2045 Design Alternative Traffic Analysis 22 6.4.6 Sensitivity Analysis on Microsimulation Modeling 23

6.5 Traffic Management Plan (TMP) (Source Type 1254) (P6 Activity TOA1050) 23 6.5.1 Staging Alternatives Analysis Report 23

6.5.2 Local Road TMP Analysis 24 6.5.2.1 Detour Analysis 24 6.5.2.2 Travel Demand Modeling 24

6.6 Enhanced NEPA Screening Analysis (P6 Activity TOA1060) 26 6.6.1 Coordination 26 6.6.2 Transit Ridership Forecasts 26 6.6.3 Travel Time Reliability Evaluation 26 6.6.4 Benefit-Cost Analysis for NEPA Alternative Screening 27

7. Bridge Evaluation (Source Type 1250) 27 7.1 Bridge Evaluation of Alternatives (P6 Activity BRE1000) 28 7.2 Bridge Evaluation of Staff Approved Layout (P6 Activity BRE1010) 29

8. Value Engineering (P6 Activity VEA1010) 30

9. Preliminary Design Package (Source Type 1250) 30 9.1 Drainage Spread and Urban vs. Rural Analysis (P6 Activity DRA1000) 30

10. Implementation and Phasing Report (Source Type 1010) (P6 Activity IPR1000) 31

11. Potential Future Transit Operations Analysis (Source Type 1290) 31 11.1 Develop Concepts and Planning Level Cost Estimates for a Walk-up Transit Station at Palomino Drive

(P6 Activity FTOA1000) 31 11.2 Identify Pedestrian and Bicycle Gaps and Safety Issues (P6 Activity FTOA1010) 31 11.3 Engage the Public (P6 Activity FTOA1020) 31 11.4 Evaluate Transit Operations and Safety (P6 Activity FTOA1030) 31



3

General Statement of Scope of Work Assist State in project management, public and agency involvement, alternatives charrette facilitation, environmental documentation and graphics support, traffic modeling and analysis, bridge evaluation, value engineering participation, preliminary drainage evaluation, implementation and phasing, and potential transit operations analysis.

General Information and Requirements

Background This Project is located on Minnesota Trunk Highway (TH) 77 (MN 77) from 138th St. in Apple Valley to Interstate (I)-494 in Bloomington, for a total length of approximately 9.5 miles. The current Reference Points (RPs) are from 0+00.000 to 9+00.500.

MN 77 serves as an important connection across the Minnesota River between Hennepin and Dakota Counties, and between the Minneapolis-St. Paul urban core and cities in Dakota County. To address ongoing transportation issues on MN 77, two studies were completed that analyzed a managed lane and access to/from the Cedar Grove Transit Station (2014 study) and identified operational deficiencies and evaluated various options to improve the capacity of the corridor (2010 study). The recommendations from these studies will be used for the ongoing analysis in the MN 77 corridor under this contract. State recently completed a traffic modeling and bridge analysis to determine the northern limits for this evaluation and feasibility of the bridge over the Minnesota River. The results of this analysis will be used to provide direction for this contract.

State has identified a number of upcoming proposed projects in the MN 77 corridor, including: 1. In 2023, Corridors of Commerce project on I-494 2. In 2022, resurface, improve drainage, Americans with Disabilities Act (ADA), extend right turn lanes, and install

cable median barrier on MN 77 from the north end of the Minnesota River Bridge in Bloomington to Highway 62 in Richfield

3. In 2026, resurface MN 77 from 138th St. in Apple Valley to the MN River Bridge in Eagan 4. In 2021 and 2025, repair MN 77 Minnesota River Bridge 5. In 2021, construct a pedestrian overpass over Cedar Avenue/CSAH 23 at 140th St

Additionally, the METRO Red Line transitway currently operates in the corridor. The 2015 Cedar Avenue Transitway/METRO Red Line Implementation Plan Update identifies two potential infill stations on MN 77 at Cliff Road and Palomino Drive. The timeframe for implementation of these stations is unknown, though should be considered in long-range plans and traffic modeling for the corridor.

Draft Schedule & Contract Completion Timeline State will provide a draft P6 schedule. The Contractor will work with the State in scheduling the activities in this scope of work with the goal of completing the layout by December 31, 2021. Once the schedule is agreed upon by Contractor and State, the Late Finish dates for the activities in that schedule are the due dates for the tasks in this scope of work. Additionally, Contractor will need to evaluate the entire schedule for accuracy and feasibility for project delivery and provide corrections where needed. The schedule provided by the State is subject to change.

Source Type Codes and P6 Activity Codes Every deliverable will list a Source Type Code and a P6 Activity Code. The Source Type Code is used in the consultant contract budget and invoice to subtotal the deliverables together under that source type code. The P6 Activity code matches the P6 activity in the P6 schedule. The Contractor can use this code to understand the due dates for that deliverable in the schedule, and how the activity relates to other activities in the schedule. The overall goal is to get the Contractor deliverables and cost estimate for the contract to match the format and organization of the P6 schedule as much as possible. The Contractor is not required to know how to use Primavera P6 or work within the program itself. The Contractor is expected to understand the concept of Critical Path Method scheduling, be able to understand hard copy reports printed by



4

the P6 schedule, update the hardcopy reports using a pencil, and recommending changes to the schedule to reflect changes in the scope or flow of work.

Standards Comply with all State, Federal, and local standards, laws and regulations related to the scope of work and project area. Work must comply with the latest edition or revision of that standard in effect on the Due Date, including any amendments in effect on that date, unless otherwise specified in the Contract or otherwise directed by State.

Items provided by State Project files and reports for this project can be viewed at: http://dotapp7.dot.state.mn.us/eDIGS_guest/DMResultSet/Urlsearch?columns=docnumber,docname&folderid=7405118

1. Draft P6 project schedule. 2. TH 77 Corridor Managed Lanes Study (2010) 3. Highway 77 Managed Lane & Cedar Grove Transit Access Engineering (2014) 4. Traffic modeling and bridge feasibility analysis (2020) 5. MnPASS System Study – Phase 3 (2018) 6. Congestion Management Safety Plan (CMSP) (2017) 7. Freeway System Interchange Study (2020) 8. Principal Arterial Intersection Conversion Study (2017) 9. Truck Freight Corridor Study (2017) 10. Regional Bike Barrier GIS link 11. Regional Bicycle Transportation Network (RBTN) link 12. Dakota County Principal Arterial Study (2018) 13. 2015 Cedar Avenue Transitway/METRO Red Line Implementation Plan Update List of potential alternatives 14. StreetLight Access until September 30, 2020 15. Bridge BRIM reports and link to bridge plans

Plain Language and Accessibility Standards

Plain Language Provide all documents or exhibits specifically designed to be used by the public in “Plain Language”. Technical documents, presentations, spreadsheets, and drawings used by technical staff do not need to be in plain language. Executive Order 14-07 requires the Office of the Governor and all Executive Branch agencies to communicate with Minnesotans using Plain Language. As defined in Executive Order 14-07, Plain Language is a communication which an audience can understand the first time they read or hear it. Additional information can be read at this website: https://www.dot.state.mn.us/consult/adaplainlanguage.html. To achieve that, the successful responder will take the following steps in the deliverables:

1. Use language commonly understood by the public; 2. Write in short and complete sentences; 3. Present information in a format that is easy-to-find and easy-to-understand; and 4. Clearly state directions and deadlines to the audience.

Accessibility Standards Comply with the State of Minnesota’s Accessibility Standard (http://mn.gov/oet/images/Stnd_State_Accessibility.pdf ) for all documents or exhibits specifically designed to be used by the public. Technical documents, presentations, spreadsheets, and drawings used by technical staff do not need to be in plain language. The State of Minnesota’s Accessibility Standards entail, in part, the Web Content Accessibility Guidelines (WCAG) 2.0 (Level AA) and Section 508 of the Rehabilitation Act, as amended. Additional requirements can be found at this website: http://www.dot.state.mn.us/ada/accommodation.html and include:

1. Providing interpreters, translators or other special accommodations, to be provided by State 2. Providing documents in an alternative format 3. Following the PDF accessibility guidance.

http://dotapp7.dot.state.mn.us/eDIGS_guest/DMResultSet/Urlsearch?columns=docnumber,docname&folderid=7405118https://www.dot.state.mn.us/consult/adaplainlanguage.htmlhttp://mn.gov/oet/images/Stnd_State_Accessibility.pdfhttp://www.dot.state.mn.us/ada/accommodation.html



5

Compliance with the State of Minnesota’s Accessibility Standard includes, but is not limited to, the specific requirements as follows:

1. All videos must include closed captions, audio descriptions and a link to a complete transcript; 2. All documents, presentations, spreadsheets, drawings, and other material must be provided in an accessible

format. In addition, provide native files in an editable format. Acceptable formats include InDesign, Word and Excel; and

3. All materials intended for downloading and printing such as promotional brochures, must be labeled as such and the content must additionally be provided in an accessible format.

Tasks Project Management, Coordination, and Meetings (Source Type 1010)

This task focuses on effective communication and coordination of the contract work to expedite the decision-making process and maintain the scheduled completion dates. The Contractor will use the State’s ProjectWise system for transferring and saving electronic files and deliverables.

1.1 Schedule (Source Type 1003) Contractor will provide updates to the draft P6 schedule supplied by State after analyzing the work required to complete this project, evaluating each activity’s duration and networking to create a schedule that will meet the goal of completing the layout by December 31, 2021. For this task, updates to the schedule will be entered into the State P6 system by the State utilizing the information provided by Contractor. Review meetings will be scheduled to evaluate the schedule and revise as needed, all revisions to the P6 schedule will be performed by the State, based on the outcome of these meetings. State will approve the schedule before becoming final. Once agreed upon, the schedule will set the expected progression and due dates of the tasks. Contractor will provide updates to the schedule on a monthly basis in time for the monthly invoicing and progress meetings and at other times deemed necessary to allow the use of the schedule as an effective management tool. At a minimum the schedule will include durations and due dates for all deliverables listed in this scope of work. Contractor will schedule and attend two Scheduling Meetings with State’s Project Manager (PM), State Scheduler and other team members as needed to revise Project Schedule.

Deliverable 1.1: 1.1.1. Up to two scheduling meetings with State PM, State Scheduler and other team members and or functional

groups as needed to revise and baseline the Project Schedule. 1.1.2. One electronic schedule and subsequent monthly updates. 1.1.3. Format: All files submitted electronically. Monthly reports must be in Adobe Acrobat (pdf extension). 1.1.4. Due: The first revised schedule is due within 40 business days of Notice to Proceed with monthly updates

on progress. 1.1.5. Standard: Critical Path Method (CPM).Primavera P6 software. 1.1.6. State Review: Five business days. 1.1.7. Contractor Update: Five business days.

1.2 Initial Project Coordination Meeting (P6 Activity OPM1000) Contractor will facilitate and attend a project kickoff meeting with State’s Project Manager and other State representatives to understand their scope, schedule, identify roles of key personnel and establish communication procedures. Review and concurrence of responsibilities of Contractor and State. Establishment of submittal requirements, review dates and overall project schedule. Establishment of the frequency of ongoing project team meetings and reviews. Contractor will coordinate with State’s Project Manager to establish personnel required to attend. Review work plan and work plan schedule, identify and present key tasks to initiate project development.

Deliverable 1.2:



6

1.2.1. Prepare, facilitate and provide meeting minutes for one meeting. 1.2.2. Format: All files submitted electronically. Meeting may be in person, teleconference, or web conference.

Send email to State’s Project Manager at completion of meeting documenting that meeting. 1.2.3. Due: Within 20 days of Notice to Proceed 1.2.4. State Review: During the meeting. 1.2.5. Contractor Update: Within five business days.

1.3 Internal and External Team Coordination (P6 Activity OPM1000) Manage day-to-day project coordination activities of individual work packages and coordination with State PM and functional groups. This includes a monthly meeting with functional groups (i.e. environmental, water resources, bridge, design, etc), phone calls, e-mails and other correspondence.

Deliverable 1.3

1.3.1 Prepare, facilitate and provide meeting minutes 1.3.2 Format: All files submitted electronically. Meeting may be in person, teleconference, or web conference. 1.3.3 Send email to State’s Project Manager at completion of meeting documenting that meeting. 1.3.4 Due: Monthly 1.3.4 State Review: During the meeting.

1.3.5 Contractor Update: Within five business days.

1.4 Project Management Team (PMT) Meetings (P6 Activity OPM1000) Contractor will prepare for and conduct monthly PMT meetings during the project. The PMT meetings will be attended by the State’s PM, State Functional Groups (as necessary) and other as determined by the Contractor. This task includes agenda preparation, meeting facilitation, follow-up, and a summary of outcomes and action items from each meeting. The Contractor will create and maintain a living action item/issue list, noting date added to the list, responsible party, status, date completed, and any other information to track outstanding project action items and issues.

Deliverable 1.4:

1.4.1 Prepare, facilitate and document up to 18 PMT meetings. 1.4.2 Format: All files submitted electronically in Adobe Acrobat (pdf extension). 1.4.3 Due: Monthly 1.4.4 Standard: Not applicable 1.4.5 State Review: five business days 1.4.6 Contractor Update: five business days after State review.

1.5 Monthly Progress Meetings (P6 Activity OPM1000) Contractor’s PM will coordinate and meet with State’s PM once per month to review the monthly progress and invoices. Contractor’s PM will solicit feedback from State’s PM to assess whether all services meet or exceed the requirements of the project. If needed, Contractor will direct changes to personnel and/or procedures to correct identified deficiencies and implement opportunities for improvements. Contractor will prepare monthly progress reports. Work will include: Prepare a work summary for reporting periods including work completed to be resolved, items pending that require action by State, present stage of project (% complete), and next major deliverables to be submitted. Financial billings and budget status that meet State requirements. Filing and record keeping, project logs and correspondence.

Deliverable 1.5: 1.5.1. Monthly informal meetings to review invoices and progress.



7

1.5.2. Format: All files submitted electronically. Meeting may be in person, teleconference, or web conference. Send email to State’s Project Manager at completion of meeting documenting that meeting.

1.5.3. Due: Monthly at the same time as the invoices. 1.5.4. Standard: Meeting minutes are not required. 1.5.5. State Review: During the meeting. 1.5.6. Contractor Update: Update invoices within five business days.

1.6 Project Instructions, Work Plan, and Quality Assurance (P6 Activity OPM1000) Develop tools (i.e. Project Instructions, Work Plans, and a Quality Assurance Plan) to establish budgets, roles, and responsibilities for the project team members throughout the project. Provide project leadership and oversight, and facilitate and document team meetings. Perform Quality Assurance/Quality Control (QA/QC) functions throughout the project duration to confirm delivery of a quality product. Contractor will detail specific QC activities and process that will be utilized throughout the duration of the project. This includes specific processes for specific work groups. Perform independent review of the Quality Management Plan (QMP) deliverables, administer the QMP, verify the document QC reviews of all deliverables and coordinate with State on audit of the QC process.

Deliverable 1.6: 1.6.1. Electronic copies of project instructions, work plans, and quality assurance plan for the contract. 1.6.2. Format: Microsoft Word and Adobe PDF. 1.6.3. Due: Within 15 business days from notice to proceed. 1.6.4. Standard: Not applicable. 1.6.5. State Review: five business days. 1.6.6. Contractor Update: five business days after State review.

1.7 Subcontractor Management and Oversight (P6 Activity OPM1000) Manage, coordinate, direct, and monitor subcontractor services. This includes review of progress reports, deliverables, schedule and invoices. Each subcontractor will be responsible for their own internal management and quality control (QC).

1.8 Risk Analysis and Tracking (P6 Activity OPM1000) Develop a project risk register to track cost and schedule risks in the project.

Deliverable 1.8:

1.8.1. Electronic copy of risk register for discussion at monthly meeting under Task 1.4 and/or 1.5. 1.8.2. Format: Microsoft Excel, using MnDOT Risk Register Template 1.8.3. Due: Monthly 1.8.4. Standard: As stated within this work order contract for specific items. 1.8.5. State Review: Monthly 1.8.6. Contractor Update: five business days after State review

Public and Agency Involvement (Source Type 0054) The State expects this project to require a significant amount of public, stakeholder, and agency involvement throughout the duration of the preliminary design phase. The State will provide oversight by the State’s PM and/or Public Affairs Coordinator for the Contractor’s Public Involvement effort, however the Contractor will be responsible for the majority of the public involvement efforts as described in this Scope of Work.

Public information goals will be consistent with the current State Communications plan. These include meeting customer expectations with information that is reliable and encourages open communication with and among all audiences. Contractor will provide a facilitator to assess and guide public involvement for the project.

2.1 Public Involvement Plan (PIP)



8

Contractor will develop and implement the PIP through Step 6. Steps 7-9 are intended to be amended into the contract, taking into consideration work completed under Steps 1-6.

The PIP consists of nine steps: 1. Project Analysis 2. Stakeholder Identification 3. Conflict Identification 4. Mapping 5. Assessment 6. Strategy 7. Implementation and Management 8. Resolution, Review, and Regeneration 9. Post-Project Analysis

Prepare a PIP that supports the State in developing and maintaining a consistent level of public, stakeholder and agency communication with the goal of establishing trust, public awareness and understanding of the Project. The Contractor will develop a PIP that will identify public, stakeholders and agency concerns, appropriate public involvement and techniques for those stakeholders, a schedule for public involvement activities, and what information is needed prior to those activities. The public involvement schedule will align activities with major milestones and decisions as determined in the overall project schedule. The Contractor will develop a PIP that identifies when public involvement activities will be held, what the purpose of the activity is, who the intended audience is, what the intended format will be, and what information will be needed prior to the meeting. The plan will identify contacts with primary stakeholder groups and identify which groups should attend specific project meetings. The PIP will also include a listing of media outlets and contacts, publication dates and procedures, and address how information requests and inquiries will be handled. The Contractor will support the State by being proactive in providing information and responding to the public and by helping to facilitate the resolution of public involvement issues. Activities described in the Contractor’s PIP will be implemented and managed by the Contractor. State will provide oversight and direction as deemed appropriate by the State. The Contractor will work with the State and respond to address public involvement issues. The phone numbers and e-mail of the Contractor’s Public Involvement staff will be provided to State. The Contractor will submit and meet with State and other appropriate representatives as designated by State to review, assess input, and/or modify the Contractor’s PIP Strategy. The Contractor and State will use performance-monitoring methods determined by the Contractor and approved by State to evaluate the effectiveness of the Contractor’s overall communications effort. Design the PIP to engage, inform, gather input, propose and establish ongoing project coordination meetings with all stakeholders including State agencies, Federal Agencies, local agencies, local businesses, local residents and others. The PIP will be continually updated.

Assumptions: 1. One work session will be held with project staff to discuss PIP, state will provide comments, and Contractor will make changes. Updates at PMT meeting on as needed basis as an agenda item

2.2 Project Analysis (P6 Activity PIP1000) Contractor will conduct thorough project research will be conducted and scaled to the size of the project or policy. The Project Goals Statement will be formalized. Document and explain all project goals, from major to minor.



9

Deliverable 2.2: 2.2.1. Project Analysis Report

2.2.2. Format: Microsoft Word and/or Adobe PDF 2.2.3. Due: Within 30 days of NTP 2.2.4. State Review: 10 days 2.2.5. Contractor Update: five business days after State review

2.3 Stakeholder Identification (P6 Activity PIP1010) Contractor will identify and create a living contact document for internal and external stakeholders including agencies, elected and appointed officials, advocacy groups, businesses and adjacent property owners/tenants. Contractor will conduct initial outreach and engagement to better understand the project area and how the project effects the various stakeholders. Contractor will keep track of stakeholder outreach, identify stakeholder’s needs to review, participate and document the outreach process. Agency and stakeholder coordination is anticipated to be an important and involved task. Contractor will be responsible for keeping the appropriate stakeholders informed, involved and gain required project consent and approval.

Below is draft stakeholder identification list of agencies as a starting point:

1. State 2. State’s Project Manager 3. State Functional Groups 4. Federal Highway Administration (FHWA) 5. Metropolitan (Met) Council 6. Metro Transit 7. Minnesota Valley Transit Authority (MVTA) 8. Minnesota Department of Natural Resources (MnDNR) 9. Dakota and Hennepin Counties 10. Cities of Apple Valley, Eagan, Bloomington and Richfield 11. Other Governmental Agencies 12. Private and Public Utilities 13. Non-Motorized and Active Transportation Organizations 14. Businesses 15. Freight Community 16. Public 17. Other agencies and groups as required

Contractor will update the stakeholder report to include new or additional information on stakeholders throughout project.

Include the following meetings:

1. Up to two work sessions for each city and county, for a total of up to 12 work sessions. Assume two hour meetings not including travel.

2. Initial outreach should include up to three meetings with stakeholders. Assume two hour meetings not including travel.

3. Up to two Project Kickoff Open Houses including virtual and in person options. Assume two hour meetings not including travel.

Deliverable 2.3: 2.3.1 Stakeholder Identification, Contact and Engagement List 2.3.2 Up to twelve work sessions 2.3.3 Three stakeholder meetings 2.3.4 Up to two Project Kickoff Open Houses



10

2.3.5 Format: Microsoft Excel, Word or PDF 2.3.6 Due: Initial contact list within 20 business days of NTP

2.4 Conflict Identification (P6 Activity PIP1020) Contractor will identify existing and potential issues related to the identified stakeholders.

Deliverable 2.4: 2.4.1. Conflict Identification Document 2.4.2. Due: Update as necessary 2.4.3. Format: Microsoft Excel, Word or PDF

2.5 Conflict Mapping (P6 Activity PIP1030) Contractor will produce an influence/interest grid of stakeholders. Relationships between stakeholders will be mapped, including alliances, relationships with friction, broken relationships, relationships that don’t exist and relationships that need to exist. Power imbalances and triggering events which may create issues will be indicated. Discuss with project team and update as needed throughout the contract.

Deliverable 2.5:

2.5.1. Influence/interest grid document

2.6 Conflict Assessment (P6 Activity PIP1040) Contractor will review conflicts for likelihood of occurring, risk to the project for time, scope and budget, and risk to the agency’s reputation.

Deliverable 2.6:

2.6.1. Assessment document that explains risk of each conflict

2.7 Public Involvement Strategy (P6 Activity PIP1050) Contractor will provide a facilitator to assess and guide public involvement for the Project.

Contractor will propose and prepare a strategy report that supports developing and maintaining a consistent level of public and agency communication with the goal of establishing trust, public awareness and understanding of the Project.

Contractor will establish measurable communications and engagement goals for the project, with a focus on engagement to help define the project purpose and need.

The strategy will identify stakeholders and their concerns, appropriate public involvement and techniques for those stakeholders, a schedule for public involvement and agency meeting and activities, and what information is needed prior to those activities. The public involvement schedule will align activities with major milestones and decisions as determined in the overall project schedule.

Contractor will identify community partners who can play a role in reaching potentially effected interests stakeholder groups identified in the stakeholder analysis. Contractor will provide recommendations for engaging community resources in communicating the history and interests of people and places near the project.

Contractor will recommend a set of communication channels that the State’s project team should use, to effectively and economically reach segmented consumer and stakeholder groups with project updates, opportunities for input, and relevant project information.

The strategy will also include a listing a media contacts, publication dates and procedures, and address how information requests and inquiries will be handled.



11

Contractor will deliver an outreach and engagement strategy briefing, in addition to a report, for the PMT. Deliverable 2.7: 2.7.1. Outreach and Engagement Strategy document

2.8 Electronic Communications (P6 Activity OPM1010) Contractor will develop a list and schedule of project documents that need to be posted to State’s hosted project website or distributed by other electronic means. Contractor will develop information for the website that is in plain language and ADA compliant, and provide to State for review. Contractor will develop an ongoing list of potential information that should be on the website.

Deliverable 2.8: 2.8.1. List, content, and schedule of project documents

Alternatives Charrette Facilitation (Source Type 1010) Contractor will facilitate alternatives charrettes focused on alternatives identification. State will complete the alternatives design.

Deliverables: See below for specific deliverables. Format: All files submitted electronically. Reports written in Microsoft Word. Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Due: To be determined upon completion of the schedule, or as noted below. See State’s sample schedule for intent. Standard: Not applicable. State Review: Five business days Contractor Update: Five business days

3.1 Review work completed to date (P6 Activity CAH1000) Contractor will review studies and evaluations and any work products created to this point.

Deliverable 3.1 3.1.1. Summary of studies and recommendations and assumptions 3.1.2. Due: 30 calendar days after NTP

3.2 Conduct Charrette (P6 Activity CHA1010)

3.2.1 Facilitation Contractor will conduct a half-day charrette to explore ideas for MN 77 corridor. Contractor will prepare a summary of key directions to help guide the work of the charrette and to inform any new participants that may become involved in the charrette. A final agenda will be created in concert with the State and representatives of the community, but a general outline of the session will be as follows:

1. Introductions of charrette participants 2. Review goals for the charrette and the process to be used during the session 3. Review background information 4. Explore ideas for MN 77 and the related issues in corridor, including transit 5. Identify a series of alternatives to be developed further 6. Summarize key directions and opportunities

Contractor will schedule a coordination meeting with State to prepare for charrette, including reviewing outline, agenda and other meeting materials. Meeting may be in person, teleconference, or web conference. Send email to State’s Project Manager documenting coordination meeting.



12

Charrette participants are anticipated to include Contractor, State, FHWA, Met Council, Transit providers, County and City staff members. Contractor should assume up to 6 Contractor staff participants at the Charrette. Consultant participants should be identified based on key expertise including traffic, transit, geometrics, safety, drainage or other areas deemed useful for charrette discussion. Charrette graphics are intended to include, but not be limited to, 100 scale aerial plot of project area and 11x17 map worksheets for logical sections throughout the corridor for each participant to be used to draft concept ideas. State will be responsible for inviting participants and providing meeting space, assumed to be the State’s Arden Hills facility.

Deliverable 3.2.1: 3.2.1.1 Meeting materials for each charrette including: Charrette directions, goals and outline, agenda,

presentation, graphics, sign-in sheet 3.2.1.2 Due: 10 business days before meeting

3.2.2 Base Mapping State will provide Contractor with base mapping and other background information needed during the charrette. State will provide .tif and .dgn files and other background/existing condition information available (e.g. wetlands, contaminated properties, etc.)

3.2.3 Charrette Summary Contractor will summarize the charrette and provide copies of the summary to participants within one week of the charrette.

Deliverable 3.2.3: 3.2.3.1 Charrette Summary 3.2.3.2 Format: Microsoft Word, Excel and/or Adobe PDF. 3.2.3.3 Due: 5 business days after meeting 3.2.3.4 State Review: 10 days 3.2.3.5 Contractor Update: 10 days

3.3 Identify and Develop Alternatives

3.3.1 Frame alternatives (P6 Activity CHA1020) Contractor will develop a prioritization worksheet to be used as an evaluation template and tool which State will complete using key directions defined during Task 3.2. State will review the ideas explored and the key directions defined during the charrette, and frame a series of alternatives for MN 77 for further evaluation under Task 4.3. The alternatives will be schematic in nature, and will be developed by State so that their implications and advantages can be analyzed. State will identify or frame screening constraints or fatal flaw scenarios that rule out ideas or components of ideas in the review and evaluation of alternative ideas (i.e. accommodation of emergency vehicles, transit operations, financial feasibility, accepted engineering practice, etc.).

Deliverable 3.3.1: 3.3.1.1. Prioritization worksheet 3.3.1.2. Format: Microsoft Word, Excel and/or Adobe PDF 3.3.1.3. Due: 5 business days after meeting 3.3.1.4. State Review: 15 days 3.3.1.5. Contractor Update: 10 days

3.3.2 Review alternatives (P6 Activity CHA1030) Contractor will reconvene the charrette group to review and comment on the alternatives. Suggestions for modifications to alternatives will be noted and subsequently incorporated into the alternatives illustrated in the Summary Report. If an



13

obviously favored alternative becomes apparent, it will be so noted in the Summary Report. A summary of comments will be prepared and distributed.

Deliverable 3.3.2: 3.3.2.1 Meeting materials including: agenda, presentation, graphics, sign-in sheet, meeting summary 3.3.2.2 Due: Meeting materials 5 business days before meeting 3.3.2.3 Due: Meeting summary 5 business days after meeting 3.3.2.4 Format: Microsoft Word, Excel and/or Adobe PDF 3.3.2.5 State Review: 10 days 3.3.2.6 Contractor Update: 10 days

3.3.3 Final Summary Report (P6 Activity CHA1040) Contractor will prepare a Summary Report at the conclusion of the work to document the process, list alternatives identified, and results of the charrette process. Copies will be provided to the State and the City in electronic format.

Deliverable 3.3.3: 3.3.3.1 Final Summary Report 3.3.3.2 Due: To be determined upon completion of the schedule, or as noted below. See State’s sample schedule

for intent.

Environmental Documentation (Source Type 1071) State will prepare the environmental document in accordance with the National Environmental Policy Act (NEPA) and State Environmental Policy that meets the project schedule. Contractor will provide input, analysis and deliverables for use by State as specified in sections below.

Contractor will provide deliverables related to the following tasks:

1. Purpose and Need Statement (Task 4.2) 2. Alternatives Evaluation (Task 4.3) 3. Benefit-Cost Analysis as required per State policy (Task 4.4.1) 4. Traffic Analysis (Task 4.4.2)

Deliverables 4: 4.1 Deliverables: See tasks below for specific deliverables. 4.2 Format: All files submitted electronically. Reports written in Microsoft Word. Complete package in Adobe

Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages.

4.3 Due: To be determined upon completion of the schedule, or as noted below. See State’s sample schedule for intent.

4.4 Standard: All requirements listed on the State’s Highway Project Development Process (HPDP) website: http://www.dot.state.mn.us/planning/hpdp/. The FHWA’s guidebook or State’s HPDP must be used as guidance to ensure that the NEPA laws have been fulfilled in the EA/EAW. Refer to the following websites: http://environment.fhwa.dot.gov/guidebook/index.asp, and http://www.dot.state.mn.us/pm/scope.html Guidance for Preparing And Processing Environmental and Section 4(f) Documents, Federal Highway Administration Technical Advisory 6640.8A.

Key tasks that are required as part of the EA, EAW, and FOFC are described below. All subtasks must be represented in the separate detailed cost breakdown.

4.1 Early Notification Memo (ENM) (P6 Activity ENM1000) State’s Metro District will prepare and circulate the ENM to State functional groups and FHWA.

http://www.dot.state.mn.us/planning/hpdp/http://environment.fhwa.dot.gov/guidebook/index.asphttp://www.dot.state.mn.us/pm/scope.htmlhttp://www.environment.fhwa.dot.gov/projdev/impTA6640.asp



14

4.2 Purpose and Need Statement (P6 Activity AAA1110) State will develop the Purpose and Need Statement. Contractor will provide the tasks listed in this scope, which will be used to inform and develop the purpose and need statement. Contractor will provide the following items to State needed for development of the Purpose and Need Statement:

1. Traffic operations outlining current traffic problems, including modeling and analysis as described under Task 6. 2. Describe current geometric deficiencies as described in Task 5 3. Pedestrian and bicycle connectivity 4. Provide graphic support, as needed, including up to 12 thematic maps, charts, illustrations and/or visualizations,

in electronic format(s) that are suitable for print and web publication.

Deliverable 4.2: 4.2.1 Summary of Traffic operations 4.2.2 Summary of geometric deficiencies developed under Task 5 to be used to develop Purpose and Need 4.2.3 Summary of pedestrian and bike connectivity 4.2.4 Graphics to support Purpose and Need Statement 4.2.5 State Review: 10 business days 4.2.6 Contractor Update: 10 business days

4.3 Alternatives Evaluation (Source Type 1071) (P6 Activity PMM1020) State will complete the Alternatives Evaluation. Contractor will provide the tasks listed in this scope, which will be used to inform and develop the Alternatives Evaluation.

4.3.1 Alternatives Screening State will develop evaluation criteria and complete the Alternatives Screening documentation. State will provide Contractor with a list of potential alternatives. The list may include, but not be limited to the following mainline alternatives:

1. New General Purpose lane 2. New High Occupancy Vehicle (HOV) lane 3. New High Occupancy Toll (HOT)/MnPASS lane 4. New General Purpose Third Lane Gap Fill for Northbound MN 77 5. Up to 5 Spot Mobility Improvements 6. No-Build

The development of alternatives will also consider various northern termini for the alternatives, such as TH 13 or connecting to possible MnPASS lanes on I-494. This may result in multiple traffic models. Assume 15 alternatives combinations and associated models.

Contractor may identify additional alternatives from initial outreach and engagement activities to include alternatives suggested by stakeholders (this work to be included by amendment to Task 2). Contractor will provide these alternatives to the State to develop to a level detailed enough so that they can be screened by the State. State will develop a screening process to evaluate the alternatives produced for screening. The screening will reduce the number of alternatives to be more fully evaluated down to five or less. The screening process will evaluate alternatives based metrics vetted by the PMT including cost, mobility improvements, transit improvements, travel time reliability, R/W impacts, community benefits, bicycle and pedestrian improvements, and other issues discovered during the initial outreach and engagement activities. State will screen the alternatives based on the screening process developed and prepare a report describing the alternatives considered, the process developed to evaluate them, the results of the evaluation, and the alternatives recommended to continue to be evaluated.

Contractor will support the alternatives screening process through tasks under public involvement, alternatives charrette, and traffic analysis completed under Tasks 2, 3, 5, and 6.



15

Deliverables 4.3.1: 4.3.1.1 Deliverables described in Tasks 2, 3, 5, and 6

4.3.2 Alternatives Meeting Support Contractor will present analysis and lead discussions on alternatives at PMT meetings described under Task 2. Topics for presentation include work completed under Tasks 4 through 9. Contractor will assume staff preparation time for meetings and bring staff knowledgeable in resource area and analysis to meetings. Contractor will provide brief meeting summaries for each meeting. Details of discussion is not needed as that will be provided in the technical memorandums.

Deliverable 4.3.2: 4.3.2.1 Meeting materials to support presentations, including, but not limited to, PowerPoint presentations, meeting

agendas, meeting notes, graphics 4.3.2.2 Due: 5 business days prior to meetings. 4.3.2.3 State Review: 2 business days 4.3.2.4 Contractor Update: 2 business days

4.3.3 Alternatives Evaluation Using the five or fewer alternatives moved forward from the screening process, State will evaluate the alternatives and complete the documentation for the Alternatives Evaluation Report. Contractor will provide graphic support for the alternatives as needed, including up to 24 thematic maps, charts, illustrations, and/or visualizations, in electronic format(s) that are suitable for print and web publication. Contractor will provide a Stakeholder Engagement summary as part of the amendment discussed under Task 2 for use in the Alternatives Evaluation Report.

Through the Alternatives Evaluation process, it is anticipated that several of the Build Alternatives will be dismissed from further consideration and three Build Alternatives will subsequently be evaluated in greater detail. Based on the results of the detailed evaluation, a Preferred Alternative is anticipated to be identified.

Contractor will provide the following tasks for use in the Alternatives Evaluation process: 1. Stakeholder Engagement Summary Task 2 2. Benefit-Cost analysis as described in Tasks 4.4.1 and Task 6.7.4 3. Traffic analysis and modeling as described in Tasks 5 and 6 4. Bridge evaluation as described in Task 7 5. Drainage analysis as described in Task 9

Deliverables 4.3.3: 4.3.3.1 Deliverables described in Task 4, 5, 6, 7, and 9 4.3.3.2 State Review: 20 business days 4.3.3.3 FHWA Review: Along with Draft Alternatives Evaluation Report (developed by State) 4.3.3.4 Contractor Update: 10 business days after each review cycle

4.3.4 Logical Termini Analysis and Report State will create a logical termini write-up detailing the reasons for the end points of the project. The logical termini and the purpose and need statement influence each other, because the logical termini analysis can influence the outcome of the purpose and need just as the purpose and need can influence the outcome of the logical termini.

4.4 Work To Be Completed by Contractor

4.4.1 Benefit-Cost Analysis (P6 Activity AAA1300) Assumes the benefit-cost analysis will compare the No-Build Alternative to up to five Build Alternatives. Assumes cost estimates for Build Alternatives will be provided by State. Contractor will prepare a benefit-cost analysis following the steps outlined on the Benefit-Cost Analysis for Transportation Projects website: http://www.dot.state.mn.us/planning/program/benefitcost.html#section3 using cost

http://www.dot.state.mn.us/planning/program/benefitcost.html#section3



16

estimates provided by State. The analysis will compare the No-Build to the identified Build Alternatives. Please note, State is now requiring that the benefit-cost analysis be completed for more than just the preferred alternative. The analysis does not have to be done for every concept considered, but does need to be completed for those that are feasible and have been considered as part of the study. The Contractor will incorporate information from the benefit-cost analysis into the Alternatives Evaluation and the EA/EAW document.

Deliverable 4.4.1: 4.4.1.1 Benefit-Cost Analysis 4.4.1.2 Due: To be completed in conjunction with the Alternatives Evaluation deliverable. 4.4.1.3 Standard: Benefit-Cost Analysis for Transportation Projects website:

http://www.dot.state.mn.us/planning/program/benefitcost.html#section3 4.4.1.4 State Review: 20 business days. 4.4.1.5 FHWA Review: Along with the Alternatives Evaluation (developed by State) 4.4.1.6 Contractor Update: 10 business days after each review cycle

4.4.2 Traffic Contractor will provide a summary report that addresses the questions outlined in the State EAW for traffic. In addition, this report will show how the preferred alternative addresses the purpose and need by using data from traffic modeling. This will include tables and illustrative exhibits for the logical breakpoints for the No-Build, 2025 and 2045 modeling.

Deliverable 4.4.2: 4.4.2.1 Traffic summary, including traffic tables and exhibits 4.4.2.2 Due: 30 calendar days after Preferred Alternative provided by State 4.4.2.3 State Review: 20 business days 4.4.2.4 FHWA Review: Along with the EA (developed by State). 4.4.2.5 Contractor Update: 10 business days after each review cycle

4.4.3 Visual Impact Assessment Contractor will prepare a Visual Impact Assessment (VIA) in accordance with FHWA’s 2015 “Guidelines for the Visual Impact Assessment of Highway Projects” found at: https://www.environment.fhwa.dot.gov/env_topics/other_topics/VIA_Guidelines_for_Highway_Projects.aspx. The VIA will include identifying the documentation and will compare the No-Build to the Preferred Alternative. The Contractor will summarize the VIA.

Deliverable 4.4.3: 4.4.3.1: VIA Summary 4.4.3.2 Standard: Visual Impact Assessment for Highway projects

https://www.environment.fhwa.dot.gov/env_topics/other_topics/VIA_Guidelines_for_Highway_Projects.aspx

4.4.3.3 State Review: 20 business days. 4.4.3.4 FHWA Review: Along with the EA (developed by State) 4.4.3.5 Contractor Update: 10 business days after each review cycle

4.4.4 Considerations Relating to Pedestrians and Bicyclists Contractor will document how the project incorporates pedestrian and bicycle populations, as part of the preferred alternative.

Deliverable 4.4.4: 4.4.4.1 One electronic Considerations Relating to Pedestrian and Bicyclists summary 4.4.4.2 Due: 30 calendar days after Preferred Alternative provided by State 4.4.4.3 State Review: 20 business days. 4.4.4.4 FHWA Review: Along with the EA (developed by State).

http://www.dot.state.mn.us/planning/program/benefitcost.html#section3https://www.environment.fhwa.dot.gov/env_topics/other_topics/VIA_Guidelines_for_Highway_Projects.aspx



17

4.4.4.5 Contractor Update: 10 business days after each review cycle.

4.4.5 Public and Agency Involvement Contractor will prepare a summary for the environmental document that describes the public and agency involvement in the project. This summary will describe public open house meeting(s), stakeholder meetings, PMT meetings, agency coordination meetings, city council meetings, the project website, project mailings, any newspaper articles, the public hearing, and any other efforts to involve the public. Contractor will prepare text documenting the official comment period and public hearing on the document. Text for this section will note the environmental document distribution and the processes that will continue beyond the public hearing.

Deliverable 4.4.5: 4.4.5.1 One electronic Public and Agency Involvement write-up summary 4.4.5.2 State Review: 20 business days. 4.4.5.3 FHWA Review: Along with the EA (developed by State) 4.4.5.4 Contractor Update: 10 business days after each review cycle.

4.5 Meeting Support (Source Type 1010)

4.5.1 Noise Mitigation Meetings (P6 Activity NOI1055) Contractor will develop a schedule, including locations and online components, for two Community Engagement meetings. Contractor will develop an invite list and a noise wall presentation to be used at meetings. Contractor will develop Noise Wall invite look and language. Contractor will print and mail invites. Contractor will develop material/handouts for meeting and implement and attend Community Noise Engagement meetings (one Contractor staff member to attend meetings). State will complete noise analysis and provide a summary, which will inform the meeting materials.

Deliverable 4.5.1: 4.5.1.1 Meeting summary, meeting materials, invitation mailers and mailing list 4.5.1.2 Format: Standard Meeting Summary Format 4.5.1.3 Due: 5 business days after meetings 4.5.1.4 State Review: 5 business days 4.5.1.5 Contractor Update: not applicable.

Existing Traffic Conditions Report (Source Type 1016) (P6 Activity TOA1000) Contractor will develop an Existing Traffic Conditions Report that discusses the field observations, and explains the existing geometric and operational deficiencies, including those experienced by transit vehicles. Contractor will provide information about locations of existing bottleneck conditions, high weave areas, and mainline queue lengths. Reference work was completed in the 2010 and 2014 studies, and the 2020 traffic review. Contractor will review data for this project that relates to 2017 traffic counts, turning movements, origin/destination data, signal timing, ramp metering, and geometrics as supplied by State and other agencies, by accessing State’s Metro website, and by accessing State’s data extraction workstation, and by accessing StreetLight data. Contractor will conduct field review of the traffic operations during the AM and PM peak periods to aid in the calibration of the base model and to verify geometric and operations. Contractor has the option to review corridor operation from State’s Regional Transportation Management Center (RTMC) facility during both peak periods. To schedule and coordinate corridor operations, contact the RTMC Operations staff at (651) 234-7040.

Deliverable 5:



18

5.1 One electronic Existing Traffic Conditions Report. 5.2 Format: Standard Report Format 5.3 Due: Prior to beginning the traffic modeling. 5.4 State and FHWA Review: 14 calendar days 5.5 Contractor Update: 14 calendar days

Traffic Operations Analyses (Source Type 1250) Contractor will complete a microsimulation model and analyze the MN 77 Corridor from 140th St. to Highway 62. Detector stations (DS) are from the “All Detector Report”, incorporated herein by reference. The modeling limits for the analysis are: 1. TH 77 from 140th Street W to East Lake Nokomis Parkway. 2. I-494 from 34th Avenue (DS 506 and DS 493) to Hwy 100 (DS 194 and DS 1011). 3. TH 62 from Portland Avenue (DS 322 and DS 335) to 28th Avenue (DS 332 and DS 325). Contractor will perform modeling and analysis for morning (AM) and afternoon (PM) peak conditions for: 1. 2017 Existing/Base year Conditions 2. 2045 design year No Build Alternative 3. 2025 opening year Preferred Design Alternative 1 4. 2045 design year Preferred Design Alternative 1 5. 2045 design year Design Alternative 2 6. 2045 design year Design Alternative 3.

The modeling will be performed using VISSIM or another State approved microsimulation software package, referenced herein as VISSIM. The modeling will conform to the current “State Modeling Guidelines” and most recent guidelines either VISSIM , DTA, TDM, or State and FHWA acceptable program intended to be used that can be found at internet website, www.dot.state.mn.us/trafficeng/index.html , and are incorporated herein by reference.

Deliverables 6: See tasks below for specific deliverables. 6.0.1 Format: All files submitted electronically. Reports written in Microsoft Word. Complete package in

Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages.

6.0.2 Due: To be determined upon completion of the schedule, or as noted below. See State’s sample schedule for intent.

6.0.3 Standard: See below. 6.0.4 State Review: See below. 6.0.5 Contractor Update: See below.

6.1 Initial Traffic Operations Meeting (P6 Activity TOA1010) Contractor will attend and facilitate meeting between Contractor and State to finalize traffic analysis criteria and goals. The results of this meeting will be presented to FHWA. Contractor will attend and facilitate meeting between Contractor, State, and FHWA to present results of initial traffic analysis coordination meeting and gain FHWA concurrence on traffic analysis approach.

Deliverable 6.1: 6.1.1 Meeting Summary 6.1.2 Format: Meeting Summary Format 6.1.3 Due: Five days after meeting

6.2 Alternative Evaluation Modeling (P6 Activity TOA1020) Contractor will conduct alternative evaluation modeling that meets, at a minimum, the following objectives:



19

1. MN 77 has been identified as a potential MnPASS corridor. An alternatives analysis to determine whether this is the right solution i.e. General Purpose (GP) Lane Vs High Occupancy Vehicle Lane (HOV) Vs High Occupancy/Toll Lane (HOT/MnPass) should be completed.

2. The evaluation process in this task will also inform the completion of Task 10. This evaluation will consist of high-level travel demand forecasting and VISSIM analysis. Travel time reliability metrics will be based on extrapolating VISSIM model. More detailed analysis will be conducted for the preferred alternative, which is described in upcoming sections of the scope. Assumptions: 1. Existing travel demand modeling (including model validation) will occur before this task begins. 2. No-Build forecasts will be developed before this task begins.

Deliverables 6.2:

6.2.1: Draft electronic reports for review and comment 6.2.2: Electronic final reports 6.2.3: All pertinent modeling files required to replicate all model runs and results. 6.2.4: Meeting Minutes 6.2.5 Format: Standard Report Format or Meeting Summary Format 6.2.6 Standard: In accordance with adopted State and Met Council forecasting and modeling guidelines, including

State’s Revised Guidelines for Twin City Travel Demand Forecasts Prepared for the Metropolitan District Memorandum dated May 10, 2006.

6.2.7 State Review: 14 calendar days 6.2.8 Contractor Update: 14 calendar days.

6.2.1 VISSIM Analysis for Alternative Evaluation Using the existing calibrated VISSIM model, Contractor will develop future models for the No-Build Alternative and Build Alternatives identified in this Section. Results of the analysis will be summarized. Measures of Effectiveness (MOEs) will include Level of Service (LOS), corridor travel time (by vehicle, person and by general purpose lanes and managed lanes), vehicle and person through-put and transit operations and travel time.

6.2.2 VISSIM Analysis Report for Alternative Evaluation Contractor will prepare a report approximately 10 pages in length, which documents the modeling process and results of the VISSIM analysis. The modeling will conform to the current “State Modeling Guidelines” and “CORSIM Calibration Parameters”. The modeling will conform to the modeling process outlined in the current “Advanced CORSIM Training Manual”, incorporated herein by reference.

6.2.3 VISSIM Analysis Meetings Contractor will prepare for and attend up to two meetings with State and FHWA staff to discuss the VISSIM modeling process and results.

6.3 Travel Demand Forecasts (P6 Activity TOA1030) Contractor will: 1. Use the most current version of the Met Council’s Activity-Based Travel Demand Model (ABM). 2. Conduct a validation review of existing base year model, Contractor will validate existing travel demand model using

recommended existing traffic volume data set. Develop validation statistics and graphical results. Review existing model performance for assignment of MnPASS volumes on existing facilities. Review recent versions of MnPASS reports prepared by State. Identify changes in MnPASS usage patterns compared to previous studies provided.

3. Review and correct model networks for coding errors, 4. Document socioeconomic (SE) data assumptions within the study area for the base and horizon years. Confirm SE

data is consistent with Met Council's Thrive 2040 MSP control totals 5. Adjust model calibration parameters within State guidelines as appropriate, and



20

6. Report validation changes based on adjustments. 7. Meet with State and Met Council staff to review travel demand modeling assumptions, methodology, network errors,

validation, and results.

The methodology for developing the 2025 and 2045 traffic forecasts will need to be developed and documented in the Travel Demand Forecasting Report, described below.

Forecasts will be developed to address the requirements of: 1. VISSIM analysis, 2. air analysis, 3. noise analysis, 4. environmental analysis, 5. TMP analysis, and 6. Benefit-cost analysis.

Deliverable 6.3: 6.3.1 Draft electronic travel demand forecasts and draft documentation reports with supporting for review and

comment. 6.3.2: Electronic final forecasts and the documentation report. 6.3.3: All pertinent modeling files required to replicate all model runs and results. 6.3.4 Format: All files submitted electronically. Report that is approximately 10 pages or less written in

Microsoft Word. Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to covert the source file to a pdf whenever possible.

6.3.5 Due: To be determined upon completion of the schedule. See State’s sample schedule for intent. 6.3.6 Standard: In accordance with adopted State and Met Council forecasting and modeling guidelines,

including State’s Revised Guidelines for Twin City Travel Demand Forecasts Prepared for the Metropolitan District memorandum dated May 10, 2006.

6.3.7 State Review: 14 calendar days 6.3.8 Contractor Update: 14 calendar days.

6.3.1 Travel Demand Forecasts for Alternative Evaluation Contractor will develop daily and peak period forecasts for the alternatives described in section 4.3.3. In addition, system-wide Person Hours Traveled (PHT) and Person Miles Traveled (PMT) will be calculated for each alternative modeled. Peak period/hour ramp to ramp origin-destination percentages will be developed for use in the microsimulation modeling. The methodology of which shall be described in the travel demand forecasting memo.

6.3.2 Sensitivity Analysis on Travel Demand Modeling Contractor will conduct up to two sensitivity tests and up to four link analyses to provide origin-destination information, trip length and what-if analysis of potential improvements. Contractor will develop and format outputs for use in freeway and arterial operations analysis, air and noise, other environmental analyses, TMP analysis and costs-benefit analysis. Perform a series of sensitivity tests on existing travel demand model to determine optimal MnPASS assignment methodology. Provide recommendation on preferred MnPASS assignment method. Perform detailed review of DRAFT Met Council TAZ-level land use for study area communities. Compare land use growth patterns to 2030 forecasts from previous corridor studies. Confirm city-level population and employment forecasts for year 2045 and consistence with Met Council's Thrive 2040 MSP totals. Document land use data used to develop traffic forecasts in forecast memorandum.

6.3.3 Travel Demand Forecasting Memorandum/Report Contractor will prepare a report approximately 10 pages in length, documenting travel demand modeling assumptions, validation, and methodologies used in developing each travel demand forecast prepared for the project. The methodology must be consistent with the guidelines and reasonableness checks described in State’s Revised Guidelines for Twin City Travel Demand Forecasts Prepared for the Metropolitan District Memorandum dated May 10, 2006. The report will address each bulleted item in the guidelines Twin City Travel Demand Forecasts Prepared for the State Metro District:



21

“Model and Parameters for Adjustments to Model Inputs” and “Model Output Checks for Reasonableness and Post Processing Adjustments”. Contractor will describe the methodology used to generate the 15-minute volume data for the forecasted AM and PM peak period volumes.

6.3.4 Travel Demand Forecasts Meetings Contractor will prepare for and attend up to three meetings with State, Met Council, and FHWA staff to discuss and obtain concurrence on forecasting assumptions, methodology, validation, results, and conclusions.

6.4 Microsimulation Modeling and Analysis (P6 Activity TOA1040) Contractor will perform VISSIM modeling and analysis and create a report explaining the results of that work. This analysis will include transit modeling completed under the each subtask.

Deliverable 6.4.0: 6.4.0.1 Prepare an analysis report with results of all models described herein, including sensitivity analysis. 6.4.0.2 Format: All files submitted electronically using Standard Report Format. Report written in Microsoft

Word. Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages.

6.4.0.3 Due: To be completed in conjunction with the Alternatives Evaluation. 6.4.0.4 Standard: The modeling will conform to the current “State Modeling Guidelines” and “CORSIM

Calibration Parameters” that can be found at internet website, www.dot.state.mn.us/trafficeng/index.html, and are incorporated herein by reference. The modeling will conform to the modeling process outlined in the current “Advanced CORSIM Training Manual”, incorporated herein by reference.

6.4.0.5 State and FHWA Review: 14 calendar days 6.4.0.6 Contractor Update: 14 calendar days.

6.4.1 Building of Base Model Contractor will: 1. Develop a lane schematic that graphically represents the existing network and includes all key design features. 2. Interpolate bad or missing volume data, convert data into 15-minute volumes, and balance the volume data for the

AM and PM time period. 3. Develop the AM and PM origin-destination (O-D) matrixes for all freeway entrances and exits utilizing

StreetLight data to enhance matrix development. 4. Update the AM and PM base models to reflect the existing freeway and arterials of the modeling limits. This

includes entering volume data and traffic signal and ramp meter control data. 5. Verify that the network data has been coded correctly and develop a freeway quality control worksheet and an

arterial quality control worksheet that lists link information. 6. Submit the base models and any supportive materials to State for review and approval.

6.4.1.1 Base Model Calibration Report Contractor will calibrate the AM and the PM base models according to the current “CORSIM Calibration Parameters”, incorporated herein by reference. Contractor will write a report explaining the process needed to calibrate the model and the changes that were required. Contractor will submit the report, the AM & PM calibrated model, and supportive materials to State and FHWA for review and approval.

Deliverable 6.4.1.1: 6.4.1.1.1 One electronic report. 6.4.1.1.2 Format: Standard Report Format 6.4.1.1.3 Due: Prior to starting the other VISSIM models. 6.4.1.1.4 Standard: The modeling will conform to the current “State Modeling Guidelines” and “CORSIM

Calibration Parameters” that can be found at internet website, www.dot.state.mn.us/trafficeng/index.html,

http://www.dot.state.mn.us/trafficeng/index.htmlhttp://www.dot.state.mn.us/trafficeng/index.html



22

and are incorporated herein by reference. The modeling will conform to the modeling process outlined in the current “Advanced CORSIM Training Manual”, incorporated herein by reference.

6.4.1.1.5 State and FHWA Review: 14 calendar days 6.4.1.1.6 Contractor Update: 14 calendar days.

6.4.2 Year 2025 No-Build Scenario Traffic Analysis Contractor will: 1. Develop a lane schematic of the network. 2. Convert the 2025 forecasted traffic data into AM and PM 15-minute volume data, balance the volume data, and check

the volume data for capacity constraints. 3. Develop AM and PM O-D matrixes for all freeway entrances and exits. 4. Build the AM and PM models. This includes entering volume data, traffic signal and ramp meter control data, and the

appropriate calibration values. 5. Verify that the network data has been coded correctly and develop a freeway quality control worksheet and an arterial

quality control worksheet that lists link information. 6. Perform ten runs on each model using different random seeds for each run. The same random number set will be used

for each model. 7. Develop the arterial and freeway measure of effectiveness tables and graphics.

6.4.3 Year 2045 No-Build Scenario Traffic Analysis Contractor will: 1. Develop a lane schematic of the network. 2. Convert the 2045 forecasted traffic data into AM and PM 15-minute volume data, balance the volume data, and check





6.4.4 Year 2025 Preferred Alternative Traffic Analysis For the selected design alternative, the Contractor will: 1. Develop a lane schematic of the network. 2. Convert the 2025 forecasted traffic data into AM and PM 15-minute volume data, balance the volume data, and check





6.4.5 Year 2045 Design Alternative Traffic Analysis For the two design alternatives, the Contractor will: 1. Develop a lane schematic of the network. 2. Convert the 2045 forecasted traffic data into AM and PM 15-minute volume data, balance the volume data, and check

the volume data for capacity constraints.



23

3. Develop AM and PM O-D matrixes for all freeway entrances and exits. 4. Build the AM and PM models. This includes entering volume data, traffic signal and ramp meter control data, and the




6.4.6 Sensitivity Analysis on Microsimulation Modeling At the State’s direction, the Contractor will: 1. Perform a sensitivity analysis on a maximum of two scenarios (AM and PM). 2. Modify the traffic data as AM and PM 15-minute volume data, balance the volume data, and check the volume data

for capacity constraints. 3. Develop AM and PM O-D matrixes for all freeway entrances and exits. 4. Update the AM and PM models. This includes entering volume data, traffic signal and ramp meter control data, and

the appropriate calibration values. 5. Verify that the network data has been coded correctly and develop a freeway quality control worksheet and an arterial



6.5 Traffic Management Plan (TMP) (Source Type 1254) (P6 Activity TOA1050) State will develop the TMP Report, including the Layout Alternatives TMP, TMP Worksheet, and Red Flag Checklist. Contractor will provide the following tasks to support State’s development of the TMP. Follow the State Metro TMP process described on this website: http://www.dot.state.mn.us/metro/trafficeng/control_striping.html

6.5.1 Staging Alternatives Analysis Report The purpose of this report is to analyze the preferred layout alternative and give enough information to the public stakeholders to make an informed decision that selects a preferred staging alternative that balances the road user costs of restrictions in traffic operations during construction with mitigation costs of alleviating those restrictions. The results will be summarized using metrics that are understandable to the general public. These metrics will demonstrate the advantages and disadvantages of each of the staging alternatives. The main body of the report will include the performance metric for each alternative and the appendices will include a full set of the technical data. Contractor will use calibrated and validated travel demand modeling (for example ABM , STOPS, and/or Dynamic Traffic Assignment Model) to compute road user costs, freeway traffic diversion, and vehicle and transit delay in determining staging alternatives. Contractor will explain the adequacy of the model being used in determining staging impact. Software such as such as QuickZone and FREEVAL may be limited to corridor analysis, and can’t estimate work zone impact to diverted traffic. Contractor will consider the road user costs vs. days of impacts in this analysis. Contractor will consider impact from other construction projects or local projects in considering staging alternatives. Contractor will compute the additional construction costs required to implement different staging alternatives. Contractor will consider impacts to transit operations from detours and delays. Based on the validated Model, Contractor will determine traffic shifts for up to three traffic staging options. State intends for this work to include one model per staging option, with staging phases included in each model. Assume three stages

http://www.dot.state.mn.us/metro/trafficeng/control_striping.html



24

per staging option. Work with State’s PM and Construction Traffic Control Coordinator to identify staging option geometrics and traffic control. Perform regional-level traffic assignment in forecast model for staging options to estimate traffic pattern changes. Document daily traffic pattern changes including reductions along segments of MN 77 through the study area as well as location and magnitude of diversion to parallel routes. Contractor will obtain loop detector data and modify the network to include projects completed prior to 2025 on selected freeway mainline, develop an existing calibrated model (geometry, volumes and speed); determine the impacts to traffic operations for up to three traffic staging options. Reference Highway Capacity Manual 2010 to obtain proper inputs and assumptions for development of the model. Calibrate existing conditions model using free-flow speeds and capacity adjustment factors and comparing to loop detector data, documenting all assumptions and variables. Prepare up to three models and perform runs for each staging option, including geometrics, traffic control, and adjusted traffic forecasts. Report qualitative and quantitative performance measures for each staging option, including queuing, traffic diversion, average vehicle delay, lost vehicle miles traveled (VMT), and total vehicle-hours. Conduct an analysis of road user costs based on vehicle-hours traveled (VHT) results and State benefit-cost guidance. Contractor will prepare a technical memorandum documenting the methods, assumptions, data, and results of the construction staging traffic modeling. Contractor will provide a recommended staging option based on traffic forecast, operational performance, transit operations, and roadway user cost analyses.

Deliverable 6.5.1: 6.5.1.1 One electronic set of modeling files and report. 6.5.1.2 Format: See Section 6. Modeling files in Cube Voyager, QuickZone, FREEVAL, or equivalent. 6.5.1.2 State Review: 14 calendar days 6.5.1.4 Contractor Update: 14 calendar days.

6.5.2 Local Road TMP Analysis Contractor will identify and analyze impacts from construction staging on the local road system and transit operations.

6.5.2.1 Detour Analysis Contractor will coordinate with FHWA to review construction traffic impact analysis methods and prepare travel time calculations (delay). Detour Analysis – Contractor will develop up to three detours for various ramp closure scenarios. Contractor will calculate the approximate detoured traffic volume and length of the detour for State’s use for agreements with local agencies.

6.5.2.2 Travel Demand Modeling Obtain and summarize loop detector data on selected freeway mainline and ramp locations. Download loop detector data for selected freeway mainline and ramp locations through RTMC. The data will be used to validate model being used in Staging Alternative Analysis before continuing to use the model for detour analysis. Obtain and summarize Average Daily Traffic (ADT) data for local street parallel routes or routes that are significantly impacted by Hwy 77 operations within agreed upon study area for comparison to model output volumes. Develop base map showing assumptions for each model run, such as which ramps are open and closed and physical limits of the model. Provide to FHWA for concurrence. Identify other construction projects, including local led projects that may affect diversion and alternative routes and include in construction staging scenarios to account for associated impacts in combination with the MN 77 project.



25

Perform a validation check on the accuracy of the existing conditions model to reflect existing observed conditions. Report locations with substantial differences where adjustments to model outputs may be appropriate to improve the validity of results. Perform highway assignment for up to six alternatives with different construction staging traffic control configurations. Based on feedback received from the PMT and internal State reviews of the first four model runs, perform two additional model runs. These final two runs are meant to explore certain situations, such as, other construction projects in the area or other traffic disrupting events. Produce maps depicting the locations and magnitudes of traffic pattern shifts for the construction staging scenarios. Review findings with State staff to confirm reasonableness of results and identify corridors that would be expected to approach or exceed capacity under these conditions.

Mitigation Development Prepare a "mitigation toolbox" document listing potential modifications that can be made to roadways and intersections in response to increased traffic flows during construction. Participate in agency discussions to refine this toolbox document for use in developing proposed mitigation measures for the MN 77 project. Collect existing AM and PM peak hour turning movement counts at up to 20 intersections along impacted corridors identified from the travel demand modeling. For selected corridors, using Synchro, Highway Capacity Manual (HCM) method or equivalent, develop peak hour traffic forecasts for up to 60 intersection scenarios under construction staging conditions. Perform up to 60 intersection geometric and traffic control evaluations and develop recommendations for operational improvements to accommodate temporary increases in traffic flow. Document the assumptions, methods, results, and findings in a technical memorandum

Deliverable 6.5.2: 6.5.2.1 Document summarizing methodology and assumptions used for TMP traffic analysis, including

validation performance summary, projects scenarios, traffic pattern shifts, impacted locations, and recommended mitigations.

6.5.2.2 Map of local construction projects anticipated during the construction period of the MN 77 project, organized by agency and timeframe for each project.

6.5.2.3 Graphic representation (i.e. maps) of traffic pattern shifts depicting the location and magnitude of traffic impacts. “Mitigation Toolbox” document listing potential modifications that can be made to roadways and intersections in response to increased traffic flows during construction.

6.5.2.4 Map and summary of operational recommendations for up to 20 intersections that would help serve temporary increases in traffic flow under construction staging scenarios.

6.5.2.5 Electronic versions of the Model runs of existing and three construction staging scenarios during AM and PM peak periods.

6.5.2.6 Summary of results for use in updating TMP. 6.5.2.7 Format: 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. All other files submitted electronically. Meeting may be in person, teleconference, or web conference. Send email to State’s Project Manager at completion of meeting documenting that meeting occurred per requirements.

6.5.2.8 Standard: Not applicable. 6.5.2.9 State Review: 14 calendar days 6.5.2.10 Contractor Update: 14 calendar days



26

6.6 Enhanced NEPA Screening Analysis (P6 Activity TOA1060) Contractor is responsible for completing analysis of travel time reliability and transit ridership forecasts to inform the screening of Project alternatives identified under this Task. Assumptions: 1. Reliability analysis will be conducted along MN 77 between 138th Street and Highway 62 2. Year 2040 daily transit ridership forecasts will be reported for the METRO Red Line as well as express service that

operates in the MN 77 corridor.

6.6.1 Coordination Contractor will hold four meetings with State, Met Council, and FHWA traffic staff to provide updates on traffic modeling progress and results for the Alternatives Screening process. Contractor will assume staff preparation time for meetings. Three Contractor’s staff will attend each meeting. Contractor will provide meeting summaries for each meeting. Summaries should be brief and include key issues, decisions, meeting times and dates, and list participants. Details of discussion is not needed as that will eventually be provided in the technical memorandums.

Deliverable 6.6.1: 6.6.1.1 Four coordination meetings with meeting materials and summaries. 6.6.1.2 Standard: Not applicable. 6.6.1.3 Due: 5 business days before meeting 6.6.1.4 State Review: 2 business days 6.6.1.5 Contractor Update: 2 business days

6.6.2 Transit Ridership Forecasts Contractor will coordinate with regional transit providers that operate service on this corridor. Contractor will develop route-level year 2040 average daily ridership forecasts for the corridor routes for the No-Build and Preferred Alternative. Contractor will document the data, methods, and results of the transit ridership forecasts in the traffic forecast technical memorandum and submit for review to Met Council staff and State's Metro District forecaster.

Deliverable 6.6.2: 6.6.2.1 One electronic technical memorandum. 6.6.2.2 Format: Standard Report Format 6.6.2.3 Standard: To be coordinated with Met Council and State staff. 6.6.2.4 State Review: 14 calendar days 6.6.2.5 Contractor Update: 14 calendar days.

6.6.3 Travel Time Reliability Evaluation Contractor will collect one year of travel time and traffic volume data along the MN 77 corridor. Compile data using SHRP2 reliability database tools and incorporate Minnesota Crash Mapping Analysis Tool (MnCMAT) crash data and National Oceanic and Atmospheric (NOAA) weather data. Contractor will separate travel time records by condition and develop demand-speed curves for each condition along the MN 77 corridor. Data will also be collected along existing MnPASS corridors (I-394, I-35W South, I-35E) to develop demand-speed curves for managed lane facilities. Contractor will prepare a custom travel time model using the results of the data collection and analysis task to predict future travel time reliability performance along the MN 77 corridor. This model will allow for future increases in traffic forecasts and geometric changes such as additional general purpose, HOV or MnPASS lanes. Travel time reliability estimates will be developed for the MN 77 corridor under year 2045 conditions for four alternatives: No-Build, General Purpose, HOV, and MnPASS. Results will be reported in terms of average tra