1: Rider requests for a transfer using
personal device from when Vehicle 1 is late. Information is received by the Agency 1
Control Center (CC1)
2: CC1 queries the current location and route
and schedule adherence (RSA) information for Vehicle 1
3: CC1 calculates the predicted arrival at
Transfer Point. for Vehicle 1
3A: CC1 corrects the predicted arrival
information for Vehicle 1 based on real-time traffic data, if available
4: CC1 forwards the transfer request to Agency 2 Control Center
(CC2)
5: CC1 queries the current location and RSA information for Vehicle 2
6: CC2 calculates
the predicted arrival at Transfer
Point. for Vehicle 2
6A: CC1 corrects the predicted arrival information for Vehicle 2 based on real-time traffic data, if available
7: CC1 rejects the
transfer request due to expected downstream delays and sends the request to Dispatcher queue for manual
approval
8: Once Dispatcher approves the transfer, CC1
automatically notifies the driver of Vehicle 2 to wait for Vehicle 1 for x minutes
9: At the same time as Step 7, CC1 notifies
the Rider of the successful transfer
10: At the same time as Step 7, CC1 notifies the CC1 of the successful transfer
11a and 11B : Vehicle 1 and Vehicle 2 arrive at the
Transfer Point and Rider completes the successful transfer
Description: Fixed-route buses (Vehicle 1 and Vehicle 2) operated by multiple agencies (Agency 1 and Agency 2) are involved. Transfer is requested by the Rider on Vehicle 1 using personal device but denied because Agency 2 does not have
the current location and RSA data for Vehicle 2. Consequently, Agency 2 dispatcher intervenes and
approves based on operational knowledge.