slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
June 10, 2014 Webinar PowerPoint Presentation
Download Presentation
June 10, 2014 Webinar

Loading in 2 Seconds...

play fullscreen
1 / 47

June 10, 2014 Webinar - PowerPoint PPT Presentation

  • Uploaded on

SHRP II R-11 Strategic Approaches at the Corridor and Network Levels to Minimize Disruptions From the Renewal Process. June 10, 2014 Webinar. Project Purpose. Phase I of this project identified widely varying levels of effort and sophistication in sequencing renewal projects.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'June 10, 2014 Webinar' - ronni

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

SHRP II R-11Strategic Approaches at the Corridor and Network Levels to Minimize Disruptions From the Renewal Process

June 10, 2014 Webinar

project purpose
Project Purpose
  • Phase I of this project identified widely varying levels of effort and sophistication in sequencing renewal projects.
  • A need for a software tool was identified.
primary target audiences
Primary Target Audiences
  • DOT Program Managers in moderately and densely urbanized States, experiencing congestion, and with an active Renewal program.
  • Planners and Program Managers in moderate and large MPO’s, with an active Renewal program.
primary requirements
Primary Requirements
  • The tool MUST NOT require user to abandon work done on management systems (PMS, BMS, etc.)
  • The tool MUST NOT require user to collect new data or require additional personnel
phases ii iii software development
Phases II & III– Software Development

Workzone Implementation Strategies Estimator


an engine in two parts
An Engine in Two Parts
  • Planning (Project Sequencing Optimization Engine).
  • Operational Software
  • A converted Network and data sets are the only pre-requisites.

Microsimulation software is used to create diversion estimates to feed back into the Planning Module- described in Phase IV

common terms
Common Terms
  • Program : One complete instance of WISE consisting of the Strategies, Planning Characteristics, Project information, Planning analysis and Operation Analysis.
  • WorkSpace : The folder which contains all of the material for ONE Program(from above). This is an active directory for all activity within the current Program.
  • Project : One instance of construction with a Program. Each Program must have between 2 and 5 Projects.
  • NeXTA: Network Explorer for Traffic Analysis which is used to import Networks to WISE.
  • Network : The NeXTA generated network which contains the model where the WISE Program exists.
  • Planning Mode :Mode which allows user to generate a Program and run WISE Analysis Engine
  • Operation Mode : Mode which allows users to interface with microcomputer softwareto run Base Scenario and individual Project Scenarios to determine Work Zone Volumes with and without Projects. Diversion Results are fed back to Planning Mode.
data requirements are minimal
Data Requirements are Minimal
  • Link – Node Network With Basic Geometry
  • Basic Traffic Flow Numbers
  • NeXTA Utilizes .xml Spreadsheet Formats
  • Additional Data can be Utilized, if Available
planning inputs1
Planning Inputs
  • Planning Characteristics
  • Project Strategies
  • Project Info
identified in phase i
Identified in Phase I
  • Demand Based Strategies: designed to reduce the demand upon a given link
  • Duration Based Strategies: designed to reduce the duration of the disruption
wise behind the scenes
WISE Behind the Scenes

Table 1 Project profiles

the operations engine
The Operations Engine *

* Users can employ their own traffic simulation models to estimate diversion as explained in Phase IV. In such a case, diversion estimates would be entered into the Planning Module manually.

more refined diversion analysis
More Refined Diversion Analysis
  • Microsimulation provides a more refined estimate of traffic diversion based upon:
    • Additional Project Information
    • What-if Scenarios
    • Interactions With Nearby Links
phase iv field validation and calibration
Phase IV- Field Validation and Calibration
  • Field Validation and Calibration
    • Validation- test in locations with completed projects
      • Des Moines, IA
      • Phoenix, AZ
    • Pilot tests- test in locations with project plans
      • Orlando, FL
      • Worcester, MA
  • Continued Testing and Code Stabilization
desmoines iowa validation
DesMoines, Iowa Validation
  • Project Description
    • I-235 through DesMoines- reconstruction, median widening, operational improvement
  • WISE Application
    • Parallel Route 6 defined as alternate route
    • Reconstruction re-defined as 6 segments
    • 8 scenarios tested
desmoines iowa validation cont
DesMoines, Iowa Validation (cont.)
  • WISE Data Preparation (same as other cases)
    • Coded network and TAZ file obtained from travel analysis model (in this case iTRAM)
    • Links and TAZs for study area selected (in this case using Transcad)
    • Links and TAZs consolidated to meet WISE limitations – in this case ~ 55; redefine centroids & connectors
    • Convert all one-way roads to 2-way roads
    • Re-number centroids and nodes sequentially
desmoines iowa validation cont1
DesMoines, Iowa Validation (cont.)
  • Figure on left: Iowa Code Network 1
  • Figure on right: IA I-235 and Route 6 Blowup
desmoines iowa validation cont2
DesMoines, Iowa Validation (cont.)
  • Software & GUI Modifications
    • Re-write code to preserve user and agency costs for each scenario
    • Modify user costs comparable to agency costs
  • 8 Scenarios Tested
    • User-supplied diversion @ 0, 5%, 10%, 20%, 40%
    • Day or Night construction for 1 segment (4 each)
    • Public information strategies for 3 segments
    • Shorten time for 1 segment with 10% > cost
desmoines iowa validation cont3
DesMoines, Iowa Validation (cont.)
  • Highlight Findings: Outputs performing in directions and approximate ranges expected
    • Total user cost for diversion > where diversion > and limited route options available
    • Total user cost declines with night construction
phoenix az validation
Phoenix, AZ Validation
  • The Phoenix program of projects includes six projects:
    • A: 202L Red Mountain Fwy– 101L to Gilbert Rd. 3 lnfwy, adding HOV Lane
    • B: 202L SantanFwy– I-10 to Gilbert Rd. 3 lnfwy, adding HOV lane, HOV directional ramps at I-10 and 101L
    • C: SR 101 HOV Addition – SR 202 Red Mountain to Princess Dr.
    • D: Twin Peaks T.I. – I-10 at MP 245 Add traffic interchange to I-10 / MP 245 for access to I-10 from Teaks Peaks Rd.
    • E: I-10 Kino Blvd to Valencia Rd
    • F: 202 Red Mountain Design Build –Addition of EB:I-10 to 101, WB 101 to Scottsdale Rd
  • WISE Application
    • 202 (approx. 14 miles long) and 101 (approx. 15 miles long) corridors are freeways with limited access
    • Interchanges are predominantly closer than one mile
    • Each corridor represented by dozens of key roadway segments.
  • Data Preparation: Same steps as DesMoines, Iowa
phoenix az validation cont
Phoenix, AZ Validation (cont.)
  • 6 Scenarios Tested
    • Daytime Base Scenario
    • Scheduling Project 1 after Project 8 with diversion @ 5%, 10%, 5%, 15% with demand strategy for Project 8
    • Diversion developed in TransModeler and fed back into WISE for comparison of scenarios
phoenix az validation cont1
Phoenix, AZ Validation (cont.)
  • Highlight Findings:
    • As expected, Scenarios 3 and 4 have the highest values and are almost identical
    • Diversion varies greatly by segment, depending on congestion, availability of alternative routes, etc.
orlando fl pilot test
Orlando, FL Pilot Test
  • Project Description
    • Reconstruction of I-4, SR 400 to accommodate 3 General Use Lanes, auxiliary lanes, and 2 Managed Lanes for eastbound and westbound (affects 14 interchanges, 5 bridges). Project corridor is approx. 20 miles long.
    • WISE Application
    • 4 key roadway segments selected from project corridor.
  • Data Preparation- same steps as DesMoines and Phoenix
orlando fl pilot test cont
Orlando, FL Pilot Test (cont.)
  • Orlando Code Network
orlando fl pilot test cont1
Orlando, FL Pilot Test (cont.)
  • 5 Scenarios Tested
    • Base Scenario
    • Project 1 and 3 with user-supplied diversion @ 5%
    • Project 1 and 3 with user-supplied diversion @ 5% and 2% demand reductions for 5 mile radius
    • Project 1 and 3 with night construction
    • Diversion calculated by TransModeler
transmodeler i 4 hybrid traffic simulation approach
TransModeler I-4 Hybrid Traffic Simulation Approach
  • High-fidelity, microscopic treatment of 21-mile I-4 corridor
  • Mesoscopic simulation of alternative routes
  • Speed reduction at project locations to reflect work zones
  • Dynamic traffic assignment (DTA) to estimate diversion
potential extensions of the analysis
Potential Extensions of the Analysis
  • Analyze impacts of work zone and work zone scheduling
  • Test ITS strategies to mitigate their effects
  • Assess needs on alternative, parallel facilities during construction
  • Analyze performance and operation of managed lanes after construction
orlando fl pilot test cont2
Orlando, FL Pilot Test (cont.)
  • Highlight Findings:
    • Increased user cost when diversion forced, with no viable alternate routes
    • Total user cost declines with night construction
    • Same user costs when no viable alternate routes available, without the intervention of night construction
worcester ma pilot test
Worcester, MA Pilot Test
  • Project Description
    • Reconstruction of 4 areas along Route 9: re-docking or replacement of bridges, intersection improvement
  • WISE Application
    • Washington Square traffic circle defined as intersection
    • I-290 coded as 2-way intersections instead of interchange
  • Data Preparation- Same steps as other pilot and validations
worcester ma pilot test cont
Worcester, MA Pilot Test (cont.)
  • Highlight Findings:
    • Simultaneous construction of neighboring projects increases congestion and makes diversion more difficult
    • Total user cost declines with night construction
summary findings
Summary Findings
  • WISE adequately optimizes the sequence of a program of projects across a network
  • WISE facilitates testing of different scenarios and strategies, permitting comparison of user and agency costs and customization of agency-defined values and inputs
  • WISE NexTA limitations (e.g. 2-way road stick network) inhibits its easy application, as identified in the Phase IV Validation and Pilot
implementation recommendations
Implementation Recommendations
  • Modify the WISE tool to interface directly with virtually any commercial or non-proprietary network system, rather than require conversion to meet WISE specifications
  • Increase WISE flexibility to define construction projects/ roadway segments
  • Increase WISE capacity to handle more zones
  • Improve Planning Module’s diversion estimates, with feedback from network models if available