innovative transit signal priority enhancements · innovative transit signal priority enhancements...
Post on 22-May-2020
5 Views
Preview:
TRANSCRIPT
Innovative Transit Signal Priority Enhancements
Presented byDavid Kobayashi
2017 ITS California Annual Meeting
Wednesday, September 20, 2017
2
Outline
1. Objectives
2. Existing TSP Systems
3. TSP Tools
4. Data Integration
5. Lessons Learned
6. Next Steps
3
Objectives
• Improve travel time
• Implement automated
data collection
• Improve diagnostic
toolset
Existing Systems
4
5
Bus TSP System Timeline
2005Rapid 522•50+ intersectionsusing loops
2008Rapid 522•40+ intersections using GPS
2010Rapid 522•Conversion of 50+ using GPS
2016Limited 323•36 intersections using GPS
2016Rapid 522•8 intersections using GPS
Total Current Locations: 138
10-20% Travel Time Savings10-20% Increased Ridership
6
Light Rail TSP System Timeline
1987•First constructed using loops
•Mainly pre-emptive
1999• Implemented early TSP principles
2008• Implemented modern TSP
2018•Conversion of 97 intersections from loops to GPS
Total Current Locations: 97
7
TSP Equipped Vehicles• 103 Light Rail Vehicles (planned)
• 65 Bus Vehicles (29 Line 522, 36 Line 323)
TSP Tools
8
9
Existing TSP Tools
• Time Points check-ins used in scheduling
• Operator and Public complaints
• Automated People Counter (APC)
• Automatic Vehicle Location (AVL)
• Vehicle TSP log
10
Existing Efforts to Meet VisionUse existing the gateway (Moovbox) used to provide internet to our customers to pull positioning data in realtime to the Transittime/Swifty API
Moovbox cellular antennaPC
Staff End User
Transittime/Swiftly API
11
Use case of Switfly Data – Light Rail Systems Speed Map
Existing TSP Tools - AVL
0:03:14, 29%
0:05:09, 46%
0:02:51, 25%
LRV Travel Time Pie ChartTasman Drive, Santa Clara
dwell travel time stop delay
12
Existing TSP Tools - AVL
13
Existing Efforts to Meet Vision
0:00:000:01:000:02:000:03:000:04:000:05:000:06:000:07:000:08:000:09:000:10:000:11:000:12:000:13:000:14:000:15:000:16:000:17:000:18:000:19:000:20:000:21:00
5241
9717
7352
5197
1773
5251
9717
5052
6197
1771
5251
9717
6452
5197
1730
5231
9717
6352
4197
1744
5251
9717
6952
5197
1742
5241
9717
3352
6197
1758
5261
9717
7852
3197
1782
5231
9717
3452
6197
1746
5261
9717
5152
7197
1771
5231
9717
5752
4197
1756
5241
9717
6952
4197
1746
5261
9717
3452
5197
1757
5261
9717
3052
5197
1729
5251
9717
5252
3197
1767
5241
9717
5152
3197
1758
5251
9717
3352
4197
1748
5241
9717
6752
5197
1765
5271
9717
5252
5197
1726
5261
9717
3752
4197
1752
5261
9717
5652
7197
1732
5261
9717
2452
6197
1750
5231
9717
3852
6197
1768
5231
9717
4952
7197
1749
5261
9717
5952
7197
1740
5241
9717
4352
3197
1750
5231
9717
4452
7197
1726
Light Rail Travel times Reamwood to Champion Westbound
May 2016
dwell travel stop
14
New TSP Tools
Central System
• Automated data collection
• Alerts
• Remote access
15
Planned Efforts to Meet VisionUse existing the gateway (Moovbox) used to provide internet to our customers to pull TSP logs.
Moovbox cellular antenna
PC/Server in
VTA Network
TSP Monitoring System
Data Integration
16
O&M
TransitVehicle
Planning
17
Data Integration
Information Silos
Traffic Signal
CustomerService
Traffic Signal Logs
Vehicle Logs, AVL
Customer Complaints
Operator Complaints
AVLAnalysis
Data Integration
Customer Service/Public
Engagement
VTA Transit Reporting
VTA-Planning
VTAIntegratedMonitoring
& PerformanceMonitoring
Bus Coach/Light Rail Vehicle O&M
VTA Board of Directors
Local Agency Traffic Engineering
VTATSP Staff
Work orderRespond back
To work order
Vision for Centralizing Data
19
Why Integrate Performance Monitoring? Ability to Cross Query
• Patterns in data
• Failure points
• Relationships
Management
• Processing and notification
• Tracking
20
Lessons Learned
Less Reactive More Proactive
• Stakeholders Concerns:
• Difficult to Pin Point Issue:
21
Next Steps
• Continue Stakeholder Outreach
• Build a Common Repository for Data
• Seek Funding and Staff Resources
22
Questions?
David Kobayashi
Senior Transportation Engineer
David.Kobayashi@VTA.org
top related