Integrate Active Work Zone Notifications into Traveler Information Dissemination Systems

Transcription

1 Integrate Active Work Zone Notifications into Traveler Information Dissemination Systems ITS Heartland Annual Meeting May 2,

2 DOT Websites with Traveler Information Right lane closed starting tomorrow at 8:30 AM until tomorrow at about 2:30 PM

3 A Common Approach 5th Avenue will be intermittently CLOSED during Phase 1. Phase 1 is anticipated to end early June. 3

4 Background Challenge: Roadwork information is often manually entered into Road Condition Reporting Systems (RCRS) and Advanced Traffic Management Systems (ATMS), for display on traveler information dissemination mechanisms. Lane closure information is general and becomes outdated Labor intensive for agency staff Difficult to accurately predict when closures will occur 4

5 Background Opportunity: Arrow boards in the field display the most current lane closure information to approaching motorists. Capture and transfer information from arrow boards More accurate and real time information to motorists Data captured for future work zone planning Future application to connected vehicles 5

6 Mobile or Stationary Arrow Boards 6

7 Freeways or Arterials E N T E R P R I S E 7

8 ENTERPRISE Pooled Fund FHWA Pooled Fund Study Program States & Canadian Provinces Collaborating on Transportation Technology Research Current Members: Michigan Minnesota Iowa Illinois Texas Kansas Pennsylvania Ministry of Transport, Ontario 8

9 Project Objective Begin the Systems Engineering process to develop an ITS solution that integrates lane closure info from arrow boards into traveler information dissemination systems Capture arrow board position and status, transfer to RCRS and ATMS Display on Traveler Information mechanisms Alerts to field staff, work zone managers Archive data for planning 9

10 System Concept Portable Arrow Board Indicates Lane Closure Location & Status Event Created TMC Systems Database Road Condition Reporting System Database Advanced Traffic Management System Other Data Processing Systems RIGHT LANE CLOSED ON HWY 100 AT 42ND ST DMS Traveler Information Dissemination Systems 511 Phone & Web Mobile Apps Social Media Connected Vehicles 10

11 Phases and Tasks Completed (Phase 1) Project: Systems Engineering Research Existing Similar Systems Utilized by Agencies Project Team Workshop to Define Scenarios and Needs Model Concept of Operations (ConOps) Model System Requirements Future (Phase 2) Project: Demonstration & Evaluation Work with one or more ENTERPRISE agencies to customize systems engineering documents Integration, demonstration, and evaluation 11

12 Project Team Name Agency Area(s) of Expertise Cory Johnson (Project Champion) MnDOT ITS Angie Kremer Michigan DOT Work Zones and TIM Chris Brookes (ATSSA contact) Michigan DOT Work Zones Kristi Ericksen Kansas DOT Work Zones Sheila Johnson/Dave Tody MnDOT Work Zones Luke Biernbaum Michigan DOT ITS Doug Tomlinson Penn DOT ITS Willy Sorenson Iowa DOT Safety & ITS Sinclair Stolle Iowa DOT Traveler Information Kelly Braunig MnDOT Traveler Information John McCellan MnDOT TMC Operations Tim Simodynes Iowa DOT TMC Operations/ITS

13 Project Team Activities Project Team Workshop (August 2016) Define Challenges/Needs/Objectives Discuss Operational Concepts Real world Demo Project Team Webinars (July 2016 Feb 2017) Finalize Model Concept of Operations Finalize Model Functional Requirements Phase 1 Wrap up / Transition to Phase 2 (Feb 2017 / Spring 2017) 13

14 Systems Engineering Documents Model Concept of Operations: Real Time Integration of Arrow Board Messages into Traveler Information Systems Input from Project Team Review by industry reps Complete Model System Requirements: Real Time Integration of Arrow Board Messages into Traveler Information Systems Input from Project Team Complete Both documents available: workzone_notifications_in_travelerinfo.html ENTERPRISE encourages agencies to use these documents for integration, deployment, testing 14

15 Systems Engineering Documents Model documents written to allow for flexibility in deployment Customizable level of automation based on staff comfort level and system reliability Not specific to any RCRS, ATMS, or Arrow Board Optional requirements include preferences that agencies may opt to include now or reserve for a future deployment, e.g., DSRC capabilities Requirements separated for Arrow Board and TMC Systems» Some functions could be executed by either the Arrow Board or TMC Systems, depending on TMC System setup and capabilities 15

16 Examples of Potential Approaches 16

17 Examples of Potential Approaches 17

18 Phase 2: Integration, Deployment, Evaluation Potential Test Deployments by ENTERPRISE Agencies: Minnesota DOT Iowa DOT Kansas DOT Michigan DOT ENTERPRISE Phase 2 Demonstration and Evaluation: Timeline TBD, Spring/Summer

19 Phase 2: Integration, Deployment, Evaluation Customize system engineering documents according to agency preferences and capabilities For procurement, agencies may integrate TMC capabilities with existing staff or support contracts, separate from Arrow Board vendor Collaboration between multiple deploying agencies will promote: Peer exchange for system deployment and issues A standard approach for this type of system More comprehensive evaluation of impacts 19

20 Additional Considerations Possible secondary benefits for future deployments Foundational communication technology for Arrow Boards to broadcast display status and lane closurerelated information to Connected and Automated Vehicles Potential for faster response time in the field for maintenance needs given notifications to field staff of system functionality, when: Hit by a passing vehicle Blown out of place by strong winds 20

21 Contacts Project Information: Contacts: Dean Deeter, Athey Creek Consultants Cory Johnson, MnDOT (Project Champion) Chris Brookes, Michigan DOT (Project Team) 21