sp 2785-330b june 2012 exhibit a draft scope of …demand forecast model (tcrm). the study area...

SP 2785-330B I-494/I-35W Interchange Vision Layout Development

June 2012

1

EXHIBIT A DRAFT SCOPE OF SERVICES FOR INTERSTATE 494/INTERSTATE 35W INTERCHANGE

w/ INTERSTATE 35W BRT STATION VISION LAYOUT DEVELOPMENT

SP 2785-330B Background The Contractor is required to conduct all tasks as described below on Interstate 494 (I-494) from the west ramp of Penn Avenue to the east ramps of Lyndale Avenue and on Interstate 35W (I-35W) from 90th Street to 76th Street. The project length is approximately 1.5 miles on I-494 approximately 1.5 miles on I-35W. MnDOT completed the I-494/I-35W Interchange Preliminary Design Report in March of 2010 that reviewed the design of the I-494/I-35W interchange. The study produced two additional concepts, a clover-leaf design and a turbine design for the interchange. The study also developed three concepts for the development of an in-line I-35W Bus Rapid Transit (BRT) Station and/or a park and ride facility at or between 82nd Street and American Boulevard. This study is available at: http://www.dot.state.mn.us/metro/projects/494and35wrichfield/docs.html MnDOT would like to determine a “Vision Layout” or preferred alternative for the design for the entire I-494/I-35W interchange. This Vision Layout would include proposed improvements within the proposed limits described above. MnDOT anticipates carrying the turbine alternative forward that came from the Preliminary Design Report, SP 2785-350 from March 30, 2010, for further refinement and analysis, 2001 Final Environmental Impact Statement (FEIS) alternative and up to two additional alternatives or variations that may come forward into this Vision Layout phase. The clover-leaf design as a part of the Preliminary Design Report from May, 2010 was ruled out due to the inability to phase the design. Any alternative brought forward should: • To provide a phased implementation of the interchange components, providing for more

flexibility while reducing the overall project impacts • Have the ability to accommodate an in-line I-35W BRT station and/or a park and ride facility

located at or between American Boulevard and 82nd Street The goal of this study is to further analyze the concepts, and move forward with a preferred alternative for the entire I-494/I-35W interchange as well as select and locate an in-line I 35W Bus Rapid Transit Station and/or a park and ride facility preliminary layout between 82nd Street and American Boulevard. In addition, MnDOT is interested in developing the first phase of the Vision Layout into a concept layout. This first phase shall include the northbound I-35W to westbound I-494 movement. The tasks associated with this contract shall include the following elements: • Water Resources preliminary design

http://www.dot.state.mn.us/metro/projects/494and35wrichfield/docs.html


June 2012

2

• Traffic Analysis and Modeling • Bridge Preliminary Design Plans • Public and Stakeholder Involvement • Bus Rapid Transit Station and/or Park and Ride coordination/design • Vision Layout Development • Project Management

In addition to the above work packages, the Contractor may need to coordinate with other MnDOT functional areas to develop the associated work packages such as MnDOT Right of Way, Surveys, Utilities, Environmental, Materials and Foundations Units.


June 2012

3

Table of Contents 1.0 Water Resources Work Package 2.0 Traffic Analysis and Modeling Work Package 3.0 Bridge Preliminary Design Plans Work Package 4.0 Public and Stakeholder Involvement Work Package 5.0 BRT Work Package 6.0 Vision Layout Work Package 7.0 Project Management Work Package


June 2012

4

1.0 Water Resources Work Package (Activity Code 1141) Previous studies (e.g. Penn Avenue to the Minnesota River: Interstate 494 Drainage Feasibility Study from May 31, 2007) have documented the deficiencies of the existing I-494 storm sewer. This study can be found at http://www.dot.state.mn.us/metro/projects/494and35wrichfield/docs.html 1.1 Surface Drainage Design associated with both the Vision Layout and Phase I of the I-

494/I-35W Project. This contract’s storm water study is to provide an analysis of the overall impact of the recommended full interchange development to the existing I-494 storm sewer system. The impact of the phased improvements are also to be analyzed separately to determine if there are “low-cost/high-benefit” improvements that can be implemented as an interim improvement, rather than constructing a major storm water improvement for I-494 from Penn Avenue to the Minnesota River.

1.1a A regional storm water pond near I494 at Wentworth Avenue/Nicollet Avenue as part of this project together with future regional storm water ponds at I-494/Portland Avenue and I-494 near 12th Avenue-TH 77 could be developed such that most of the existing I-494 storm sewer would be sufficient (substantially as documented in Alternate 2C of Penn Avenue to the Minnesota River: Interstate 494 Drainage Feasibility Study of May 2007). This project surface drainage design study shall provide separate cost estimates for the I-494 at Wentworth/Nicollet Avenue storm water pond and trunk storm sewer to be constructed as part of the I-494/I-35W interchange project and for the other two future storm water ponds and reconstructed trunk storm sewer. 1.1b Based upon the Vision Layout configuration of the proposed I-35W/I-494 interchange and existing impervious area or eight lanes, whichever is greater, for I-35W and I-494 beyond the limits of the interchange project, detailed preliminary designs for at least two site options for each of the three regional storm water ponds shall be developed that minimize the local impact for the options.

This detailed preliminary design for both 1.1a and 1.1b includes site grading plans, preliminary profiles of trunk sewer, calculations, drainage models and cost estimates. The cost estimates should include right of way costs. Design Criteria: The three storm water ponds shall provide dead pool equal to or greater than the runoff from all tributary MnDOT pavement from a 2.5” event. The storm water ponds and alternate storm water tunnel shall attenuate flow or provide additional conveyance capacity such that there is no surcharging of the trunk storm sewer during the 50-year event and the HGL during the 100-year event is below ground surface. Furthermore, the storm water ponds shall limit flow such that rate discharged at the outlet for the 2-year, 10-year, and 100-year events are less than or equal to existing rates. Current Nine Mile Creek Watershed District volume control

http://www.dot.state.mn.us/metro/projects/494and35wrichfield/docs.html


June 2012

5

requirements for 1” runoff from increase in impervious pavement from existing conditions to ultimate configuration shall be met with infiltration/filtration basins adjacent to the proposed storm water ponds. Infiltration/filtration basin for the discharge to the I494 storm sewer to the Minnesota River consistent with Lower Minnesota River Watershed District rules shall also be configured. The proposed ponds and associated infiltration/filtration basins shall utilize retaining walls, as consistent with facilitating future maintenance, if it is determined to be cost effective to reduce the extent and cost of property acquisition. Ponds and basins may not be buried structures and shall be located such that construction does not necessitate closure of lane(s) on I-494 or I-35W other than for construction of connecting trunk storm sewer. In addition to the pond sites at Penn Avenue and at Nicollet Avenue that are shown in the Penn Avenue to the Minnesota River: Interstate 494 Drainage Feasibility Study, several other nearby sites shall also be evaluated. The consultant in conjunction with MnDOT staff shall seek input from the City of Richfield and City of Bloomington regarding the least objectionable/most plausible sites within each city for property acquisition needed to construct proposed ponds and basins. Detailed site/ grading plans (which are predicated upon available groundwater data) for the, at least two, sites for each of the three storm water pond/basin sites shall be developed. Detailed preliminary profiles of trunk storm sewers needed to convey flow from the low point of the tributary area to the pond/basin, and then convey flow to existing storm sewer or discharge point shall be developed and analyzed. 1.2 Optional Work Task: Storm water Tunnel

1.2a This work task assumes only the required volume control basin with pre-treatment at I-494 near Wentworth Avenue/Nicollet Avenue and provide a storm water tunnel from there to the Minnesota River. With only future volume control and pre-treatment at I-494/Portland Avenue and I-494/12th Avenue/TH 77, this is somewhat as envisioned in Alternate 5A of Penn Avenue to the Minnesota River: Interstate 494 Drainage Feasibility Study except that the western terminus of the tunnel would only extend to Wentworth Avenue/Nicollet Avenue and no provision would be made for future extension to the Wood Lake Pump Station or the Penn Avenue Pump Station as previously envisioned by the 2007 I-494 Drainage Feasibility Study.

1.3 Metro Water Resource Coordination Meetings The Water Resources Work Package shall be coordinated with oversight and input from the MnDOT Metro Water Resources Unit and will include a minimum of four meetings scheduled periodically at MnDOT Water’s Edge during the project development stage of the project. These meetings are necessary such that oversight, review and input may be incorporated into the work to help guide the appropriate drainage design. MnDOT will perform and/or provide the following items: • Interstate 494 Improvements: Penn Avenue to the MN River: Interstate 494 Drainage

Feasibility Study, Stanley Consultants, May 2007


June 2012

6

• Existing As-builts, as available

Contractor Deliverables: • Detailed site/ grading plans – MicroStation Format • Detailed preliminary profiles of trunk storm sewers – MicroStation Format • All calculations and drainage models • Detailed cost estimates

All deliverables will be submitted in both electronic and hardcopy formats.


June 2012

7

2.0 Traffic Analysis and Modeling Work Package (Activity Code 1015)

2.1 Traffic Demand Modeling Develop daily and AM/PM peak hour forecasts for alternatives for the re-construction and reconfiguration of the I-494/I-35W interchange, using the Twin Cities Regional Travel Demand Forecast Model (TCRM). The study area includes the I-494 between East Bush Lake Road in Bloomington to the Minnesota River in Bloomington, and from the Minnesota River in Bloomington to 66th Street NE in Richfield on I-35W. The travel demand model shall include the proposed 77th Street Underpass in the TH 77 corridor. This Contract shall include all tasks required to complete the traffic forecasting, traffic modeling, interstate access request, and intersection control evaluations. 2.1.1 The following travel demand volumes will be developed for the interchange study

area: • 2040 No Build (existing network plus planned improvements from current

TPP) • 2040 Build Alternative 1 • 2040 Build Alternative 2 • Year of Opening Build (2020) (Preferred Concept)

2.1.2 Highway network assumptions and transit network assumptions for the 2040 No Build forecast will be consistent with the Metropolitan Council 2010 Transportation Policy Plan. The travel demand forecasting process and files used to conduct the 34th Avenue Study completed in 2008 will be provided for use in this study. A Sensitivity Analysis using 77th Street Underpass shall be completed. The impacts of the TH 77 BRT Study and the TH77 Traffic Management Study shall also be included in the travel demand forecasting.

2.1.3 Socio-economic data assumptions will be consistent with the Metropolitan

Council 2010 Transportation Policy Plan.

2.1.4 A technical memorandum summarizing the travel demand forecasting methodology, assumptions, and findings will be prepared for review by MnDOT’s Metro District and Met Council. This document will adhere to the guidelines and address the reasonableness checks as indicated in the May 10, 2006 MnDOT Memo "Revised Guidelines for Twin City Travel Demand Forecasts Prepared for the Metropolitan District". Traffic forecasts are not complete until the travel demand methodology, assumptions, and checks for reasonableness, described within the Traffic Forecasting Memo, are reviewed and approved by MnDOT. Traffic forecasting documentation needs to be reviewed by the Metro District Traffic Forecaster and traffic forecasts must be approved prior to use in the CORSIM modeling and analysis.


June 2012

8

2.2 CORSIM Modeling and Analysis

The Contractor shall model and analyze the I-494 corridor from TH 100 to TH 77 and I-35W from 66th Street to 90th Street The modeling limits for the analysis are:

• I-494 from Valley View Road (detector stations 486 and 472) to TH 5 (detector

stations 505 and 494). • I-35W from 90th Street (detector stations 27 and 40) to 66th Street (detector stations

19 and 48). • TH 77 from Old Shakopee Road (detector stations 543 and 522) to 66th Street

(detector stations 536 and 529).

Detector stations are from the “All Detector Report”, incorporated herein by reference.

MnDOT will provide modeling files developed in 2009. This includes CORSIM files, link-node diagrams, and lane schematics for the existing conditions and builds scenarios studied. The modeling shall conform to the current “State Modeling Guidelines” and “CORSIM Calibration parameters.” The modeling shall conform to the modeling process outlined in the current “Advanced CORSIM Training Manual,” incorporated herein by reference. The Contractor shall use the results of the previous modeling, developed in 2009, for the 2007 existing conditions (calibrated model), 2020 No Build scenario, 2040 FEIS interchange scenario, and the 2040 Turbine interchange scenario.

2.2.1 Design Year Traffic Analysis (No Build and Build Scenarios)

2.2.1.1 Develop a link node diagram and lane schematic of the network for the

design year Build and No Build scenarios. 2.2.1.2 Convert the 2040 forecasted traffic data into AM and PM 15-minute

volume data, balance the volume data, and check the volume data for capacity constraints for the Build and No Build scenarios.

2.2.1.3 Develop AM and PM design year (2040) O-D matrixes for all freeway entrances and exits for the Build and No Build scenarios.

2.2.1.4 Build the AM and PM design year models to reflect the Build and No Build scenarios. This includes entering volume data, traffic signal and ramp meter control data, and the appropriate calibration values.

2.2.1.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 for the Build and No Build scenarios.

2.2.1.6 Perform five runs on each model using different random seeds for each run. The same random number set shall be used for each model


June 2012

9

2.2.1.7 Develop the design year (2040) arterial and freeway measure of effectiveness tables and graphics for the Build and No Build scenarios. Present modeling results of the design year Build and No Build scenarios to MnDOT and FHWA and highlight any operational issues and concerns.

2.2.1.8 Conduct alternative analysis to address operational issues and develop arterial and freeway measure of effectiveness tables and graphics. Present findings of alternative analysis.

2.2.2 Opening Year Traffic Analysis (Build Scenarios)

The modeling for the opening year will include the preferred Build scenario from task 2.2.4.

2.2.2.1 Develop a link node diagram and lane schematic of the network for the

opening year Build and No Build scenarios. 2.2.2.2 Convert the 2020 forecasted traffic data into AM and PM 15-minute

volume data, balance the volume data, and check the volume data for capacity constraints for the Build and No Build scenarios.

2.2.2.3 Develop AM and PM opening year (2020) O-D matrixes for all freeway entrances and exits for the Build and No Build scenarios.

2.2.2.4 Build the AM and PM opening year models to reflect the Build and No Build scenarios. This includes entering volume data, traffic signal and ramp meter control data, and the appropriate calibration values.

2.2.2.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 for the Build and No Build scenarios.

2.2.2.6 Perform five runs on each model using different random seeds for each run. The same random number set shall be used for each model.

2.2.2.7 Develop the opening year (2020) arterial and freeway measure of effectiveness tables and graphics for review and final approval by Mn/DOT and FHWA.

2.3 Traffic Office Coordination Meetings

The Traffic Work Package shall be coordinated with oversight and input from the MnDOT Traffic Unit and will include a minimum of four meetings scheduled periodically at MnDOT Water’s Edge during the project development stage of the project. These meetings are necessary such that oversight, review and input may be incorporated into the work to help guide the appropriate drainage design.


June 2012

10

MnDOT will perform and/or provide the following items: • Review and comment on the simulation results of the proposed freeway design within

fifteen (15) work days after receipt of the MnDOT delivered the items. • Provide existing CORSIM modeling files. • Provide existing turning movement and tube counts provided these are not more than

two years old. • Provide website links to the Data Extract and Data Plot programs for extracting detector

data. • Provide existing signal timings (State signals only). Contractor shall obtain data from City

and County signals. • Review and comment on the simulation results of the proposed freeway design within

fifteen working days after receipt of the MnDOT delivered items. • Provide website links to the Data Extract and Data Plot programs for extracting detector

data. • Provide existing signal timings (Mn/DOT signals only). City and County signals shall be the

responsibility of consultant to request this information. • Provide ramp metering information. • Provide a sample of a link-node diagram. • Provide a sample quality control worksheet. • Provide Calibration Procedure and Modeling Guidelines • Provide meeting space for project meetings.

Contractor Deliverables: • Document summarizing methodology and assumptions used to develop forecasts and

subsequent reasonableness checks. • Five draft copies of the forecasts for 2040 No Build, 2040 Alt 1, 2040 Alt 2, and 2020

Build, presented for review/comment accompanied by draft documentation reports including average annual daily traffic, AM peak hour and PM peak hour, and estimated heavy commercial vehicle traffic. This should include average annual daily traffic, AM peak hour, PM peak hour, and estimated heavy commercial vehicle traffic for the interstate mainline, system ramps, service interchange ramps, collector distributor roadways, cross streets.

• Five copies of the final forecasts and the documentation report for 2040 No Build, 2040 Alt 1, 2040 Alt 2, and 2020 Build,, (4 bound and 1 unbound suitable for photocopying), one pdf file and one electronic copy including average annual daily traffic, AM peak hour and PM peak hour, and estimated heavy commercial vehicle traffic. This should include average annual daily traffic, AM peak hour, PM peak hour, and estimated heavy commercial vehicle traffic for the interstate mainline, system ramps, service interchange ramps, collector distributor roadways, cross streets.

• Three draft copies of the charts or other easily understood form, showing traffic lane assignments and turning volumes for 2040 No Build, 2040 Alt 1, 2040 Alt 2, and 2020 Build presented for review/comment.


June 2012

11

• Three final copies of traffic lane assignments and turning volumes for 2040 No Build, 2040 Alt 1, 2040 Alt 2, and 2020 Build (2 bound and 1 unbound suitable for photocopying), one pdf file and one electronic copy.

• One paper and one electronic copy in MS Word of the draft report, three copies of the final report plus one electronic copy in pdf and one MS Word copy.

• Graphic representations (i.e. maps) of existing and forecast for all scenarios. • Technical memorandums. • Signal information not provided by MnDOT. • Heavy vehicle information. • Link-node diagrams and lane schematics. • Balanced arterial and freeway traffic volume data sets. • O-D Matrices. • Arterial and freeway quality control worksheets. • Arterial and freeway MOE graphics, tables and summaries. • Final Modeling documentation. • SYNCHRO and CORSIM electronic files for all scenarios. • Meeting agendas plus any other materials required for the meetings. • Meeting minutes.



June 2012

12

3.0 Bridge Preliminary Type Study Work Package (Activity Code 1250)

Task Overview: This task includes development of Concept Preliminary Bridge Plan Sheets, Scoping Level Bridge Cost Estimates, and a brief Bridge Type Study Report for each bridge structure included in the Project Layout. Develop Concept Preliminary Bridge Plan Sheets to illustrate the preferred bridge type(s) including preliminary alignments and draft profile grades that were developed with the layout for this project. Information specific to each particular bridge should be developed for depicting the preferred bridge structure type(s) including span layouts, substructure locations, vertical clearances, and horizontal clearances in compliance with required Design Standards.

Develop Scoping Level Bridge Cost Estimates based on specific approximate quantity-based unit price cost estimates for each bridge. Consult the MnDOT Bridge Cost Estimates Unit for typical historic bid unit prices for the purpose of the approximate quantity based estimates.

Develop Brief Bridge Type Study Reports to document general project considerations with regard to complex geometrics leading to viable alternative bridge type(s) at each bridge location within the revised and updated Project Layout. The Study Report is intended to summarize the particular project attributes that were considered that led to and support the preferred bridge type(s). The intent would be a preferred bridge type or short list of bridge type(s) that are should be considered and carried forward into the next project phase of the project.

Temporary Bridge Structure Numbers have been assigned for each conceptual level bridge for the purpose of establishing the approximate magnitude of the expected effort and includes 16 new concept level bridges and 1 reconstructed existing bridge. It is anticipated that layout revisions will result in revisions to the limits of the bridges as depicted in the turbine design. Concept Bridge numbers will be assigned as follows with the understanding that the level of effort for the Bridge Preliminary Type Study would include between 16 and 18 bridges.

Bridge No. 27-S1 Bridge No. 27-S2 Bridge No. 27-S3 Bridge No. 27R05 (reconstructed) Bridge No. 27-S4 Bridge No. 27-S5 Bridge No. 27-S6 Bridge No. 27-S7 Bridge No. 27-S8 Bridge No. 27-S9 Bridge No. 27-S10 Bridge No. 27-S11 Bridge No. 27-S12 Bridge No. 27-S13 Bridge No. 27-S14 Bridge No. 27-S15 Bridge No. 27-S16 The Bridge Preliminary Type Study Work Package shall be coordinated with oversight and input from the MnDOT Bridge Office and will include a minimum of four meetings scheduled periodically at the MnDOT Bridge Office during the project development stage so that oversight, review, and input may be incorporated into the work to help guide the appropriate selection of preferred bridge type(s).


June 2012

13

Design Standards and Plan Preparation Concept Preliminary Bridge Plans sheets will be prepared in accordance with the following Standards and documents, all incorporated by reference: • MnDOT LRFD Bridge Design Manual • American Association of State Highway and Transportation Officials (AASHTO) LRFD Bridge

Design Specifications • American Segmental Bridge Institute (ASBI) • MnDOT Road Design Manual • MnDOT Surveying and Mapping Manual • MnDOT Drainage Manual • MnDOT Computer Assisted Design and Drafting (CADD) Standards • MnDOT Summary of Recommended Drafting Standards • MnDOT Staff Approved Layout (Provided by Contractor) • MnDOT Environmental Documents and Design Memorandums 3.1 Concept Preliminary Bridge Plan Sheets

3.1.1 Perform necessary engineering and design to determine the type, size, and location for each Bridge including specific geometrics of each bridge. This work should occur concurrently with development of Project Layout.

3.1.2 Perform the necessary number of concept iterations adjusting alignments and

profiles to cause uniform span layout for each structure and for the project as a whole. Contractor should plan to revise the layout to accommodate adjustments to the spans in an effort to maximize uniform and balanced span layouts.

3.1.3 Structure depths and profile grades shall be iterated together to provide the

minimum required vertical clearance while not providing excessive additional clearance above the minimum requirements.

3.1.4 Progress update meetings shall be scheduled with the MnDOT Bridge Office

during the development stage as the layout is evolving to obtain input for ongoing iterations. Information shown at intermittent project development stages shall include bridge cross-sections for each structure, potential pier placement locations, and any special bridge pier type considerations such as integral and/or straddle bent type locations. An initial effort shall be made to standardize bridge cross sections for consideration of various bridge types appropriate to the curved ramp geometry.

3.1.5 Concept Preliminary Bridge Plan Sheets shall be developed in accordance with

MnDOT CAdd Standards using Micro station and GEOPAK.


June 2012

14

3.1.6 The Concept Preliminary Plan Sheets shall include sufficient information to carry

forward for development of the complete Preliminary Bridge Plans and as a minimum shall include:

• General Plan and Elevation • Profile of Finished Bridge Deck • Bridge Deck Cross Section showing # lanes and shoulder width • Design Data • Proposed Type of Structure Block • Projected Traffic Volumes • Title Block • Proposed alignment data and profile grades • Preferred Structure Type(s) • Proposed Span Layouts and substructure locations • Depth of Structure information

3.2 Bridge Cost Estimates

3.2.1 Scoping Level Bridge Cost Estimates may be supplemented with historical comparable bridge types, but shall not be the basis for the Bridge Cost Estimates.

3.2.2 Prepare Quantity-based unit price cost estimates should for each bridge that is developed with the Project Layout. This shall require approximately 16-18 separate bridge cost estimates for this project based on partial quantity based unit price approach for each bridge.

3.2.3 Consult the MnDOT Bridge Cost Estimates Unit for typical historic bid unit prices for the purpose of the approximate quantity based estimates.

3.2.4 Foundations information should be gathered with input from the MnDOT Foundations Unit to establish likely foundation types and corresponding pile lengths to be used for the scoping level estimates.

3.3 Structure Type Studies 3.3.1a Consider bridge types that offer structural advantages to the project specific

conditions of curved ramp alignments with limited space for substructure placement.

3.3.1b Adjust curved ramp alignments to create opportunities for substructure

placement that result in uniform and balanced span layouts within individual structures and within the overall project so that a family of typical span lengths are the end result for the project as a whole.


June 2012

15

3.3.2 For crossings with large spans resulting from skewed supports, radial substructure placement with integral pier caps shall be considered.

3.3.3 Concept drawings of each structure type shall be submitted for review specific to

each bridge location proposed.

3.3.4 For the bridge type studies, consideration shall be given to skewed support placement verses radial support placement and use of post-tensioning as appropriate to avoid fracture critical type supports.

3.3.5 The limits of the retaining walls shall be shown on the Project Layout and the

portion of the retaining walls (wingwalls) included within the Concept Preliminary Bridge Plan shall be clearly shown to identify which portions of the retaining walls are included in the bridge cost estimates. Use 25’ of wingwall as a guide for maximum retaining wall costs that are include with the bridge wingwalls. The limits of walls beyond 25’ behind the bridge abutments should be identified, but included in a separate cost tabulation and separate cost estimate.

3.4 Bridge Office Coordination Meetings

3.4.1 The Bridge Preliminary Type Study Work Package shall be coordinated with oversight and input from the MnDOT Bridge Office and shall include a minimum of four meetings scheduled periodically at the MnDOT Bridge Office during the project development stage of the project.

3.4.2 Coordinate meetings at the Bridge Office with the MnDOT Preliminary Bridge

Plans Engineer so that oversight, review, and input may be incorporated into the work to help guide the appropriate selection of preferred bridge type(s).

3.4.3 Two copies of the 30% Preliminary Plan, electronic Micro Station and Geopak files

(coordinate correct); Structure Type Study reports, concept sketches, and preliminary cost estimates will be submitted to State for review. State is expected to return the 30% Preliminary Plan with red-lined comments within 15 working days from the date of receipt by MnDOT. Agreed-upon revisions shall be incorporated for inclusion in the Aesthetic Design Review submittal.

3.5 Final Preliminary Plans are not the intent of this Project Deliverable The Final Preliminary Plan would be included in the next phase of the project development and concurrent with completion of 30% roadway plans. This Contract is intended to provide sufficient Preliminary Bridge Engineering Support that is to be conducted concurrent with the development of the Project Layout and Profile Grades, which effectively result in “Draft Concept Preliminary Bridge Plans” that represent the approximate 30% completion.


June 2012

16

MnDOT will perform and/or provide the following items: • List of Unit Prices for Major Bridge Components for use in Bridge Cost Estimates • Foundation Borings Information at selected locations sufficient to establish like foundation

types, pile lengths, and information for use in bridge cost estimates • T.H. 494 Aesthetic Design Guide; • Oversight of Layout Development for conformance with Design Standards • MnDOT Bridge Office Oversight during layout development • Review and Comments of Concept Preliminary Bridge Plans, Cost Estimates, and Bridge Type

Study Reports for inclusion in Final Project Deliverables

Contractor Deliverables: • Concept Preliminary Bridge Plan Sheets for Each Bridge - two hard copy plan sets (11"x17"

paper), including alignment tabulations and preliminary profile grades. • Bridge Cost Estimates, including submittal of electronic copies of spreadsheets, quantity

tabulations, and unit price cost estimates for each bridge type • Brief Bridge Type Study Reports for up to 18 Bridges developed as part of Project Layout

Development • Electronic copies of Micro Station Layout including all GEOPAK files: GPK, TIN, APL, PLN, and

FIP files developed for the project



June 2012

17

4.0 Public/Stakeholder Involvement Work Package (Activity Code 0054)

4.1 Prepare Public Involvement Plan

4.1.1 Prepare a draft Public Involvement Plan that supports MnDOT in developing and maintaining a consistent level of public communication with the goal of establishing trust, public awareness and understanding of the Project. The Public Involvement Plan will identify stakeholders and their 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 shall align activities with major milestones and decisions as determined in the overall project schedule. The public involvement plan shall also include a listing a media contacts, publication dates and procedures, and address how information requests and inquiries will be handled. The draft Plan shall be submitted for MnDOT, Metropolitan Council, City of Bloomington, City of Richfield review and revised in response to comments.

4.1.2 The Public Involvement Plan will be continually updated through a stakeholder database (mailing list) and issues matrix.

4.2 Monthly Progress Reports

4.2.1 Prepare monthly reports of progress and such other reports related to

public/stakeholder involvement as needed for administration of the project.

4.3 Talking Points

4.3.1 Prepare talking points summarizing project progress to date, next steps and key messages at each of five project phases: project initiation, evaluation and selection of a systems interchange concept, FEIS re-evaluation, preliminary interchange design and EA, and project completion.

4.4 Public Open Houses

4.4.1 Conduct two open house public information meetings. This work includes

meeting attendance, preparation of meeting materials including sign-in sheets, handouts and displays and preparation of a brief PowerPoint presentation (approximately 20 slides.) Attend and assist MnDOT in presenting at the meeting and prepare open house summary, documenting materials presented, attendance and comments received. Three copies of the report in a hard copy format along with a copy of the report in an electronic format, designated by MnDOT’s Project Manager, shall be submitted to MnDOT’s Project Manager within ten days after of each open house meeting.


June 2012

18

4.4.2 Attend two (2) pre-open house meeting conferences (one before each open house) with MnDOT, City of Bloomington, City of Richfield and Metropolitan Council to prepare the agenda and agree on presentation materials.

4.4.3 Attend two (2) post-open house meeting conferences (one after each open house)

with MnDOT, City of Bloomington, City of Richfield and Metropolitan Council to review the comments made at these meetings and decide on the necessary course of action.

4.5 City Council of Bloomington and Richfield Meetings/Workshops

4.5.1 Attend four meetings/workshops with City Council and/or Hennepin County Board

and prepare the necessary graphics and figures etc, to assist in presenting the various aspects of the project.

4.5.2 Prepare a brief summary of concerns and needs expressed at these

meetings/workshops. Three copies of this report in a hard copy format along with a copy of this report in an electronic format, will be submitted to MnDOT’s Project Manager within ten days after each meeting or before the next meeting, whichever is earlier. Three copies of this report in a hard copy format along with a copy of the report in an electronic format, will be submitted to MnDOT’s Project Manager within ten days after each meeting or before the next meeting, whichever is earlier.

4.5.3 Attend up to four pre-meeting/workshop conferences with MnDOT, the City of

Bloomington, City of Richfield and Metropolitan Council to prepare the agenda and agree on presentation materials.

4.5.4 Attend up to four post-meeting/workshop conferences with MnDOT, the City of

Bloomington, City of Richfield and Metropolitan Council to review the comments received and decide on the necessary course of action. Provide summary of meeting(s).

4.6 Meetings with Special Interest Groups

4.6.1 Attend up to eight special interest group meetings to assist MnDOT staff with

explaining issues, answering questions and recording the concerns and needs of the these groups.

4.6.2 Prepare a brief summary of concerns and needs expressed at these meetings.

Three copies of this report in a hard copy format along with a copy of the report in an electronic format, shall be submitted to MnDOT’s Project Manager within ten days after each meeting or before the next meeting, whichever is earlier. Three copies of this report in a hard copy format along with a copy of the report


June 2012

19

in an electronic format, shall be submitted to MnDOT’s Project Manager within ten days after each meeting or before the next meeting, whichever is earlier.

4.7 Press Releases, Public Inquiries, etc.

4.7.1 As requested by State’s Project Manager prepare draft versions of press releases,

response to public inquiries, local bulletin board announcements, and letters to property owners or interested parties. Six press releases, public inquiries and/or bulletin board announcements shall be assumed.

MnDOT will perform and/or provide the following items: • Provide project oversight and direction • Furnish pertinent project correspondence and project data • Attend key project meetings

Contractor Deliverables: • Maintain project log of all special interest groups, local, state, and federal agency

meetings • Prepare for and attend the meetings identified in other work tasks (including

preparation of agendas (three days prior) and meeting minutes (within seven days of the meeting completion) and send to all attendees.



June 2012

20

5.0 I-35W Bus Rapid Transit Station Work Package (Activity Code 1080)

Bus Rapid Transit has become a significant element to transportation system solutions in addressing congestion in major corridors on the interstate and state highways. I-35W is a heavily congested corridor which was recently enhanced with HOV/HOT lanes from Lakeville to downtown Minneapolis as a part of the 2009 Urban Partnership Agreement project. In addition, a new in-line BRT station at the 46th Street overpass on I-35W in Minneapolis was recently constructed. In effort to help alleviate congestion, the Contractor will lead and develop consensus regarding the design and location of another in-line Bus Rapid Transit station located at or between 82nd Street and American Boulevard. The 2010 Preliminary Design Report for the I-494/I-35W interchange developed three alternatives for the incorporation of the I-35W BRT station and/or Park and Ride Facility. The Contractor may need to develop up to two more alternatives to consider in the development of a preferred location. Upon the development of consensus regarding the design and location of the in-line I-35W Bus Rapid Transit Station and/or park and ride facility, the contractor will develop the final geometrics associated with the proposed design. The Contractor will coordinate the development of these concepts with the State, the City of Bloomington, the City of Richfield, Federal Highway Administration (FHWA), the Metropolitan Council, Metropolitan Transit, Minnesota Valley Transit Authority, and other stakeholders.

Assumptions: Construction cost estimates based upon dollars from most resent calendar year bid

information Electronic CADD files (Micro Station/GEOPAK) including plot files on compact discs

(CDs), to follow State's CADD data standards dated December 2010 located at http://www.dot.State.mn.us/caes/cadd/pdf/mndot-cdstds-a1-gencomm.pdf

Right of way estimate based upon the county tax assessor value plus a factor indicating current market value

5.1 I-35W BRT Station Concepts

The Contractor shall develop and further refine concept sketches for the three identified I-35W BRT Station and/or park and ride facility alternatives and up to two additional concepts. The Contractor shall coordinate review of the design elements by MnDOT, the Cities of Bloomington and Richfield, Metro Transit, Minnesota Valley Transit Authority, the Federal Highway Administration (FHWA), and other agencies.

5.2 I-35W BRT Station Impact Matrix

http://www.dot.state.mn.us/caes/cadd/pdf/mndot-cdstds-a1-gencomm.pdf


June 2012

21

The Contractor shall identify the impacts associated for the each (up to 5) concepts developed and compare them with the alternative developed in the 2001 Final Environmental Impact Statement for the purposes of performing impact analysis. These impacts shall include but are not limited to Right-of-Way acquisition, Utility Impacts, Railroad Coordination, required storm water management and infiltration, permits, and project cost. 5.2.1 The Contractor shall develop an alternatives impact matrix to compare each concept

developed. 5.2.2 The Contractor shall develop cost estimates for each concept developed. 5.3 Preliminary I-35W BRT Station Layout

5.3.1 Upon gaining consensus of a preferred alternative, the Contractor shall develop a

preliminary BRT Station layout including profiles, cross sections and preliminary construction limits. Identify and refine right of way and easement needs. Incorporate preliminary drainage design into layouts. Incorporate utility information, label and denote as needed.

5.3.2 The Contractor shall identify and refine the phased implementation opportunities

to confirm short term (within 5 years of project construction) versus long term solutions and prepare layout depicting the timing of the short term and long term solutions.

5.3.3 The Contractor shall present layout to the Project Team, receive comments and

revise layout.

5.3.4 The Contractor shall provide for layout QA/QC activities 5.3.5 The Contractor shall develop the concepts using current MnDOT standards 5.3.6 (Including Bentley MicroStation - Version 08.05.02.27 and Bentley GEOPAK 2004 Edition Version 08.05.01.56) for layout development and in accordance with

the HPDP handbook. 5.4 Cost Estimates for Preliminary I-35W BRT Station Layout

5.4.1 Prepare estimate of construction cost for the preferred I-35W BRT Station and/or

park and ride facility preliminary layout which will include all construction elements associated with the I-35W BRT Station Construction including American Boulevard bus and pedestrian connections contributions, including, but not limited to roadway elements, platform, elevators, stairwell, mechanical elements, and electrical elements.


June 2012

22

MnDOT will perform and/or provide the following items: • Planimetric mapping, TIN model, right of way and utility information from previous work,

and any other base map information available, including approved 2001 Official Map for southwest quadrant of the existing interchange.

• CADD and Geopak files for previous alternatives, including layouts, profiles and cross sections

• Review and comment on alternatives, layouts, matrices, profiles, estimates, and other layout activities.

Contractor Deliverables: • Concept Sketches for concepts being considered • Alternative impact matrix • Cost Estimates (both for the developed concepts and for the Preliminary I-35W BRT

Station Layout) • Concept alternatives refinements and evaluations to identify preferred alternative • Preliminary I-35W BRT Station Layout



June 2012

23

6.0 Vision Interchange Layout Development Work Package (Activity Code 1080) The Contractor shall lead and develop consensus regarding the design of the interchange at I-494 and I-35W. The May 2010 Preliminary Design Report study for the I-494/I-35W interchange developed two alternatives for the interchange. The Contractor may need to develop up to two more alternatives to consider in the development of a preferred alternative. Upon the development of consensus regarding the design and configuration of the interchange, the contractor shall develop the final geometrics associated with the proposed design. The Contractor shall coordinate the development of these concepts with MnDOT, the City of Bloomington, the City of Richfield, Federal Highway Administration (FHWA), the Metropolitan Council, Metropolitan Transit, and other stakeholders. Assumptions: Construction cost estimates based upon dollars from most resent calendar year bid

information. Electronic CADD files (Micro Station/GEOPAK) including plot files on compact discs (CDs), to

follow MnDOT’s CADD data standards dated December 2010 located at http://www.dot.State.mn.us/caes/cadd/pdf/mndot-cdstds-a1-gencomm.pdf

Right of way estimate based upon the County tax assessor value plus a factor indicating current market value

6.1 Vision Layout Concept Development/Refinement

6.1.1 The Contractor shall identify the impacts associated for the refined concepts and

the alternative developed in the 2001 Final Environmental Impact Statement for the purposes of performing impact analysis. These impacts will include but are not limited to Right-of-Way acquisition, Utility Impacts, Railroad Coordination, required ponding and infiltration, permits, and project cost.

6.1.2 The Contractor shall develop and provide an impact matrix that will compare each

alternative developed. 6.2 Design Memorandum

6.2.1 The Contractor shall develop the Design Memorandum for the preferred

alternative documenting the current and proposed design standards, identification of exceptions to the current design standards, and documentation of the exceptions to the current design standards.

6.2.2 The Contractor shall provide hard copies of the draft Design Memorandum, an

electronic copy of the Design Memorandum in PDF format, and the electronic copy of the files for the Design Memorandum.

http://www.dot.state.mn.us/caes/cadd/pdf/mndot-cdstds-a1-gencomm.pdf


June 2012

24

6.2.3 The Contractor shall incorporate comments received from the review of the draft

Design Memorandum 6.2.4 The Contractor shall provide hard copies of the final Design Memorandum, the

electronic copy of the Design Memorandum in PDF format, and the electronic copy of the files for the Design Memorandum.

6.3 Cost Estimates

6.3.1 The Contractor shall prepare estimate of construction cost for the preferred Vision

Layout which shall include all construction elements associated with the interchange. This will include preliminary cost sharing for the local municipalities.

6.4 Vision Layout Development

This work includes further developing the selected preferred alternative to be move forward as the Vision Layout. This work shall also include the I-35W BRT Station and/or Park and Ride location and layout(s). This work shall include alignments, profiles, cross-sections, construction limits, retaining walls and surface area calculations.

6.4.1 The Contractor shall incorporate comments received from the review of the geometrics of the preferred concept for the I-35W BRT station.

6.4.2 The Contractor shall identify the impacts with the Vision Layout and will include

but are not limited to Right-of-Way acquisition, Utility Impacts, Railroad Coordination, required ponding and infiltration, permits, and project cost.

6.4.3 The Contractor shall provide hard copies of the Vision Layout, an electronic copy

of the Vision Layout in PDF format, and the electronic dopy of the files for the Vision Layout.

6.5 Phasing Breakout

This work shall include developing Phase 1 (a northbound I-35W to westbound I-494 layout) including a cost estimate and layout associated with the preferred I-35W BRT Station and/or Park and Ride preferred location and layout. MnDOT will perform and/or provide the following items: • Planimetric mapping, TIN model, right of way and utility information from previous work,

and any other base map information available, including the 2001 MnDOT Official Map for the southwest quadrant of existing interchange.

• CADD and Geopak files for previous alternatives, including layouts, profiles and cross sections


June 2012

25

• Review and comment on alternatives, layouts, matrices, profiles, estimates, and other layout activities.

• In terms of survey information, MnDOT will be able to provide existing information for the following: eastbound and westbound I-494, northbound and southbound I-35W, ramps, loops and frontage roads at I-35W/I-494, ramps and loops at Lyndale Avenue and Penn Avenue, ramps at 76th, 82nd, 86th, and 90th, crossing alignments of Lyndale Avenue, Penn Avenue, 76th, American Boulevard, 82nd and 90th. MnDOT will also provide the existing right of way from along I 494 from Penn Avenue to Lyndale Avenue and on I-35W from 92nd to 70th. MnDOT can provide construction plans for the recent projects along I-35W and I-494 (SP 2785-367) for the consultant to use to obtain storm sewer information. As-builts may also be available.

Contractor Deliverables: • Concept Sketches for concepts being considered • Alternative impact matrix • Cost Estimates (both for the developed concepts and for the Vision Layout) • Concept alternatives refinements and evaluations to identify preferred alternative • Vision Layout • Phasing Breakout (Phase 1 layout and estimated costs)



June 2012

26

7.0 Project Management Work Package (Activity Code 1010) 7.1 Prepare work-planning schedule, to be updated monthly, and coordinate all

required tasks.

7.1.1 The Contractor shall establish ongoing project coordination with all stakeholders including MnDOT, MnDOT Project Manager, MnDOT Functional Groups, City of Bloomington, City of Richfield, Governmental agencies, Metropolitan Transit, Minnesota alley Transit Authority, Metropolitan Council, businesses and local residences in project area, other agencies, MPCA and contaminated site inventory and Department of Health Well Inventory.

7.2 Ongoing Project Coordination

This task focuses on effective communication and coordination of the contract work to expedite the decision-making process and maintain the scheduled completion dates. Contractor involvement shall be for 12 months from Authorization to Proceed. Contractor shall be responsible for overall project management and management of sub-consultants. Each sub-consultant shall be responsible for their own internal management and quality control. Each sub-consultant has included cost for that effort in their fee estimate. The Contractor shall prepare for, attend, and document the following meetings:

7.2.1 One Project Kick-off Meeting 7.2.2 Identifying roles of key personnel and establishing communication procedures. 7.2.3 Review and concurrence of responsibilities of the Contractor and the State. 7.2.4 Establishment of submittal requirements, review dates, and overall project

schedule. 7.2.5 Establishment of the frequency of ongoing project team meeting/reviews. 7.2.6 Project Development Meetings as deemed necessary by the MnDOT’s Project

Manager 7.2.7 Two Public Information Meetings 7.2.8 Four meetings to discuss design issues with outside agencies, businesses, and

property owners as necessary.

7.3 Project Team Meetings

7.3.1 The contractor shall conduct up to ten Project Team meetings during the project. The project coordination meetings shall be attended by MnDOT Project Manager and Functional Groups, City of Bloomington, City of Richfield, Metro Transit (not limited to Minnesota Valley Transit Authority, Metropolitan Council and other agencies as required and shall focus on work package decisions and policy issues. This Task includes agenda preparation, meeting facilitation, follow-up, and a


June 2012

27

summary of outcomes from each meeting (distributed electronically within five days of meeting).

7.4 Periodic Meetings with State Functional Units

7.4.1 Conduct up to 12 functional unit meetings to discuss work package progress,

unusual problems, changes in conditions or other problems, and/or other issues. Task includes time for pre-planning of meeting with MnDOT staff, agenda preparation, meeting facilitation, follow-up, and a summary of outcomes from each meeting (distributed electronically within five days of meeting).

7.5 Monthly Progress Reports, Invoices and File Keeping

The Contractor shall prepare monthly progress reports (assumes 12 months). Work shall include the following: 7.5.1 Prepare a work summary for reporting period including work completed items to

be resolved, items pending that require action by MnDOT, present stage of project (percent completed), and next major deliverables to be submitted.

7.5.2 Prepare deliverables status report that includes provides the following information - 1) ahead of schedule, under budget; 2) ahead of schedule, over budget; 3) behind schedule, over budget; 4) behind schedule, under budget; 5) on schedule on budget; If behind schedule, provide explanation for how to get back on schedule, as well as impact to other deliverables.

7.5.3 Log of external meetings with local, state, and federal agencies 7.5.4 Financial billings and budget status that meets MnDOT requirements 7.5.5 Filing and record keeping, project logs and correspondence

7.6 Sub-consultant Management and Oversight

7.6.1 Manage coordinate, direct and monitor subconsultant activities including

schedule, progress reports, deliverables and invoices. (Assumes 12 months) 7.7 Development and Maintenance of Project Critical Path Method (CPM) Schedule

7.7.1 Develop CPM schedule using Primavera for the project within 30 days of Notice to

Proceed. The schedule shall include an estimate of hours loaded for each role or resource, connected tasks and key deliverable dates. The Contractor shall be requir4ed to provide quarterly updates of this schedule and provide the updates


June 2012

28

to the management team. Perform independent review of the CPM schedule deliverables.

7.8 Internal and External Team Coordination

7.8.1 Manage day-to-day project coordination activities of individual work packages

and coordination with State Project Managers. This includes phone calls, e-mails and other correspondence.

7.9 Develop a project-specific Quality Management Plan (QMP)

7.9.1 The Contractor shall detail specific quality control 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 QMP deliverables.

7.9.2 Administer the project QMP 7.9.3 Verify and document QC reviews of all deliverables.

7.9.4 Coordinate with MnDOT on audit of the quality control process. (Assumes

quarterly audits)

MnDOT will perform and/or provide the following items: • Provide project oversight and direction • Review and approve submittals in a timely manner • Furnish pertinent project correspondence and project data • Attend key project meetings • Provide Work Breakdown Structure (WBS) if applicable

Contractor Deliverables: • Provide baseline CPM schedule within 30 days of Notice to Proceed • Schedule and attend PDMT meeting • Maintain project log of all local, state, and federal agency meetings Submit invoices in timely manner • Monitor progress and manage Contractor staff and sub-consultants • Prepare and submit monthly status reports on project progress • Provide timely inputs regarding issues that must be resolved regarding the design on

an as-needed basis. • Implement and oversee quality control plan. • Prepare for and attend the meetings identified in other work tasks (including

preparation of agendas (three days prior) and meeting minutes (within seven days of the meeting completion) and submit to all attendees).


June 2012

29
