Presentation is loading. Please wait.

Presentation is loading. Please wait.

The MnDOT Metro District Microsimulation Experience Kevin Sommers, PE Minnesota Department of Transportation 651-234-7844.

Similar presentations


Presentation on theme: "The MnDOT Metro District Microsimulation Experience Kevin Sommers, PE Minnesota Department of Transportation 651-234-7844."— Presentation transcript:

1 The MnDOT Metro District Microsimulation Experience Kevin Sommers, PE Minnesota Department of Transportation Kevin.Sommers@DOT.state.mn.us 651-234-7844

2 In the Beginning…. Models were developed according to user preferences. Models were developed according to user preferences. Several items considered optional including model calibration. Several items considered optional including model calibration. Typical model was 1 time period of 60 minutes without origin-destination data. Typical model was 1 time period of 60 minutes without origin-destination data. Reported values based on a single run of model. Reported values based on a single run of model.

3 CORSIM Training Manual Developed By Mn/DOT & FHWA to: Developed By Mn/DOT & FHWA to:  Clarify modeling process.  Produce reusable and verifiable products.  Meet Federal operational analysis requirements for the Interstate Access Request.

4 CORSIM Training Manual Lists 21 items to be followed on all modeling projects. Lists 21 items to be followed on all modeling projects. Categories: Categories:  Model Requirements  Data Requirements  Calibration Requirements  Quality Control Requirements

5 CORSIM Training Manual Lists 11 required deliverables. Lists 11 required deliverables. The most critical are: The most critical are:  Link-Node Diagrams.  Lane Schematics.  QA/QC Sheets.  O-D Matrixes.  Balanced Traffic Demand Dataset.  MOE Tables.

6 The Freeway Lane Schematic Graphical representation of freeway made modeling results easier to understand. Graphical representation of freeway made modeling results easier to understand. Color is used to highlight congested sections. Color is used to highlight congested sections.

7 Design Selection Typically several designs developed for a freeway corridor. Typically several designs developed for a freeway corridor. 2, 3, or 4 design options are tested using microsimulation to determine best option. 2, 3, or 4 design options are tested using microsimulation to determine best option. Design Options Design Options  TH 610 at I-94  Partial Build vs. Full Build  TH 169 at I-494  Ring Road System (3 designs)

8 Design Selection Interchange Type Interchange Type  I-494 at Lyndale Ave.  Single Point vs. Tight Diamond Traffic Control Traffic Control  TH 610 at Zachary Lane  Signals vs. Roundabouts Collector-Distributor Roads Collector-Distributor Roads  I-35E at CSAH 14  Connect SB entry ramps to CD Road or Interstate

9 Tweaking the Design Sometimes the accepted design needs a little help. Sometimes the accepted design needs a little help. Auxiliary Lanes Auxiliary Lanes  I-35 at CSAH 70  Auxiliary Lane Between CSAH 70 and CSAH 60 Turn Bays Turn Bays  TH 62 at I-494  Dual Left vs. Triple Left

10 Freeways Modeled To Date 210 miles of freeway modeled including: 210 miles of freeway modeled including:  40 miles of I-35W  31 miles of I-494  28 miles of I-94  16 miles of I-694  14 miles of I-35E  10 miles of I-35  10 miles of I-394

11 Modeling Website Advanced CORSIM Manual Advanced CORSIM Manual Freeway Modeling Workshop Presentations Freeway Modeling Workshop Presentations Modeling Resource Materials Modeling Resource Materials FHWA Traffic Analysis Toolbox FHWA Traffic Analysis Toolbox Link to MnDOT Data Extraction Tools Link to MnDOT Data Extraction Tools Link to MnDOT Turning Movement Information Link to MnDOT Turning Movement Information http://www.dot.state.mn.us/trafficeng/modeling/index.html

12 Thank You


Download ppt "The MnDOT Metro District Microsimulation Experience Kevin Sommers, PE Minnesota Department of Transportation 651-234-7844."

Similar presentations


Ads by Google