Transit Operations Decision Support Systems (TODSS) Dmitriy Vanchugov Trapeze, ITS Sales Consultant San Francisco, CA

Transcription

1 Transit Operations Decision Support Systems (TODSS) Dmitriy Vanchugov Trapeze, ITS Sales Consultant San Francisco, CA March 30, 2012

2 Agenda Agenda What is CAD AVL? TODSS Project Background Next Generation CAD AVL (What is different?) Results and Lessons Learned

3 Fixed End In the Field Computer Aided Dispatch Traveler Information Systems (CAD) And Automatic Vehicle Location (AVL) Systems Communication Systems Private Radio or Cellular On-Board Systems Prioritized Queue (1 100) Action Plans Research Lists Info Computer Aided Dispatch Network Infrastructure Existing Systems Integration: Scheduling Operations Management

4 Agenda Agenda What is CAD AVL? TODSS Project Background Next Generation CAD AVL (What is different?) Results and Lessons Learned

5 Project Participants, Goals and Results of the TODSS R&D Participants Federal Transit Administration Pace Bus Booz Allen Hamilton Trapeze Project Core Goals Configurable vs Customizable External Sources of Information Results Succeeded in Developing Next Generation CAD 2010 ITS America Award Winner for Most Innovative ITS Development of the Year

6 The Project Started 4/06 and the Operational Test Ended 5/2009 Pace and FTA defined the Project Plan Pace and Trapeze entered into contract that included the Statement of Work This was difficult process due to all parties unfamiliar with mechanics of an R&D project Pace Developed Concept of Operations and Local Requirements for TODSS Operational Scenarios A series of Team TODSS meetings identified the needs and operational requirements Trapeze developed Detailed Requirements and System Architecture April 08 through Sep 08 System Development and Testing July 2008 through February 2009 Implementation and Operational Test Period Went live March 3, 2009

7 Agenda Agenda What is CAD AVL? TODSS Project Background Next Generation CAD AVL (What is different?) Results and Lessons Learned

8 Legacy CAD Systems Emergency Queue Adherence Queue Other Queue Computer Aided Dispatch Sources Of Information Archive (Historic Data)

9 The Problem Late! All Routes Early! Off Route Malfunction ALARM! Request To Talk HELP! Where is the nearest replacement bus? Do we have extra drivers? How can I fix Each Problem? v?!?!? What is causing these problems! What problem is most important? What are the impacts to later service? Has there been an accident? Transit dispatchers using traditional CAD/AVL systems often are faced with too much information competing for their attention. Trapeze ITS U.S.A., LLC Proprietary and confidential. Distribution only by express authority of Constellation Software Inc. or its subsidiaries. 9

10 Pre TODSS Queue Menu Bar Tool Bar Tab Bar Emergency Messages Talk Requests Tab Area Adherence Messages Other Messages Status Bar March 30, 2012

11 Additional Sources of Information Emergency Queue Adherence Queue Other Queue Computer Aided Dispatch Sources Of Information Archive (Historic Data)

12 TODSS trigged over the Internet Traffic message from Traffic.com Incoming RSS feed from Internet Trapeze ITS U.S.A., LLC Proprietary and confidential. Distribution only by express authority of Constellation Software Inc. or its subsidiaries. 1 2

13 Additional Sources of Information Emergency Queue Adherence Queue Other Queue Computer Aided Dispatch Sources Of Information Archive (Historic Data)

14 Intelligent Decision Support Engine Agency Business Rules Work Assignments Emergency Queue Adherence Queue Other Queue Computer Aided TODSS Dispatch Sources Of Information Archive (Historic Data)

15 11/2 008 ITS America Expo Chart No.15

16 Intelligent Decision Support Engine Agency Business Rules Work Assignments Emergency Queue Adherence Queue Other Queue Computer Aided TODSS Dispatch Sources Of Information Archive (Historic Data)

17 Intelligent Decision Support Engine Agency Business Rules Work Assignments Emergency Queue Prioritized Queue (1 100) Adherence Queue Other Research Queue Lists Action Plans Info TODSS Audit Trails Sources Of Information Archive (Historic Data)

18 TODSS View Trapeze ITS U.S.A., LLC Proprietary and confidential. Distribution only by express authority of Constellation Software Inc. or its subsidiaries. 1 8

19 Several techniques are available to provide options and handle unusual operational scenarios Multiple Action Plans can be assigned to an incident for dispatcher options within TODSS Through IDS Administration individual rules can be enabled/disabled in realtime Complete sets of rules centered around specific operational scenarios can be created and saved and loaded when needed Special Events Emergency Operations Weather Disruptions Or Work Assignment Roles can be configured for specific operational scenarios

20 Agenda Agenda What is CAD AVL? TODSS Project Background Next Generation CAD AVL (What is different?) Results and Lessons Learned

21 Operational Test for 60 Days Team TODSS process to configure TODSS Decide what incidents dispatchers must actively manage and provide oversight Decide what triggers each incident Build an Action Plan(s) to assign to each incident Build a Research List to assign to each incident Create a set of Action Items that could be re-used wherever possible Create a set of Research Lists and Action Plans that could be re-used wherever possible Pace re-defined the driver initiated (canned) data messaging to improve safety and fit within the TODSS concept

22 r y a n d TODSS proved that managing the flow of information and providing decision support increases CAD/AVL impact... c o n f i d e n t i a l. D i s t r i b u t i o n Statistic... leading to better use of the system capabilities by dispatchers Number of Data Messages displayed to dispatchers (even greater if accounting for adherence messages) Voice communications between drivers and dispatchers RTT Response Time Average (hmm...) TODSS Outcome Reduced by 60% Reduced by 30% No change RTT Response Time Standard Deviation (but...) Reduced by 33% Number of Reports created (Automated notifications had big impact) Drivers use of canned service messages (no training and 2/3 fewer messages) Reduced by 36% Increased 7% o n l y 2 2

23 Changes in over 40 Pace Dispatcher's responses to the before and after survey were significant I have time to explore all the CAD information ( significantly) I know where to go to get the information I m looking for ( significantly) I know how to easily access related information ( significantly) When I need information it is often hard to find ( significantly). Positive dispatcher response validated FTA requirements and prompted the decision to include TODSS within the CAD AVL environment

24 Lessons Learned Integrated internet and capabilities provide immediate internal and external operations communications, where management and line staff become more directly informed and involved in the day-to-day operations Training for system administrators, dispatchers, and operators is critical to sustain the TODSS effort Color coding of priority and unique audible cues are relied on by dispatcher more than was initially understood Required restoration strategies, through action plans, result in a more uniform response within and throughout the divisions Setup of TODSS is much easier when an agency has a theory of service management articulated in defined standard operating procedures reporting was duplicating other dispatcher actions and was not needed as much as it was previously

25 TODSS Conclusion Tools (in this case software programs) tend to be only as powerful as their users In order to achieve maximum user adoption of new tools or technology, its important to: Manage the feature set Manage Content TODSS Achieves this with Intelligent Decision Support Business Logic (Based March 30, 2012 on Agency Best Practices)

26 Several Early Adopters Pace Bus, Chicago Pilot site and System Power User Mississauga, ON Early stages of TODSS Configuration Dallas, TX Nearing project completion Cincinnati, OH Nearing project completion Des Moines, IA Project Deployment Phase San Antonio, TX Project Deployment Phase Delaware Project Design Phase March 30, 2012

27 Thank You Final Report and Requirements TODSS_Report_V3.pdf Dmitriy Vanchugov (319) March 30, 2012