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

Size: px
Start display at page:

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

Transcription

1 SHRP II R-11 Strategic Approaches at the Corridor and Network Levels to Minimize Disruptions From the Renewal Process A Web Presentation to the Technical Committee March 21, 2012

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

3 Primary Target Audiences DOT Program Managers in moderately urbanized States. MPO Program Managers Without Sophisticated Modeling Tools.

4 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 The tool MUST NOT replicate existing capabilities

5 Phase II Software Development Workzone Implementation Strategies Estimator (WISE)

6 An Engine in Two Parts Planning (Project Sequencing Optimization Engine). Operations (DynusT)

7 Planning Engine

8 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 DynusT to run Base Scenario and individual Project Scenarios to determine Work Zone Volumes with and without Projects. Diversion Results are fed back to Planning Mode.

9 The G.U.I.

10 Planning Inputs

11 Importing A Network

12 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

13 Importing A Network

14 Planning Inputs Planning Characteristics Project Strategies Project Info

15 Planning Characteristics

16 Project Strategies

17 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

18 Project Info

19 A Six Project Load to the Network

20 Running the Algorithm

21 WISE Behind the Scenes Table 1 Project profiles Project Earliest start time Latest completion time Duration (months) Duration Strategy Actual duration Precedance 1 Jun, 2012 May, Jun, 2012 May, Jun, 2012 May, Jun, 2012 May, Jun, 2012 May, Jun, 2012 May, Project Capacity reduction Original posted speed limit New posted speed limit Construction mode Both Both Day Day Day Day

22 Sequencing Results

23 Planning / Operations Interaction Operation Mode is Built From Planning Information Operation uses the same Network, Planning Characteristics and Projects as the Planning Mode. Operation Mode intent is to provide an Operation Diversion for each project within the Planning Mode to be applied to the WISE Analysis Engine. Operation Diversion is calculated in the Operation Mode: Operational Diversion is made available to the user in the Project Information Section once the Base and Project Scenarios have been run for a given Project. This can be accessed by the following: Select Planning Tab -> Project Info Tab -> Go To Project for the Project desired. Operation Supplied will display the amount

24 The Operations Engine

25 DynusT and D.T.A.

26 Dynamic Traffic Assignment

27 More Refined Diversion Analysis DynusT provides a more refined estimate of traffic diversion based upon: Additional Project Information What-if Scenarios Interactions With Nearby Links

28 Now, Back to Planning

29 Now Re-Run the Sequence

30 Next Steps Field Validation and Calibration. Continued Rigorousness Testing and Code Stabilization. Enhancement of Capabilities

31 Questions?