Scenario
2- Data Flows (Cont.)
4.The
passenger accepts the addition of the transit leg to their trip. This message is sent to the T-DISP Control Center via
internet or wifi/DSRC/mobile
network.
5.The
T-DISP Control Center utilizes scheduling, CAD/AVL, and messaging systems to schedule a transit or private mode
trip. The selected trip is sent to
the D-RIDE Data Center to add as part of the overall ridematch output.
6.The
center provides a combined driver + transit rideshare match based on data from the travelers proposed trips, any routing
constraints, preferences
specified by the traveler, compatibility of this rideshare with other travelers, eligibility data, and traffic data.
This combined driver + transit
rideshare match is reported back to the travelers and accepting transit
7.The
travelers confirm the rideshare match and the confirmation is sent back to the center.
8.The
center stores all rideshare matches and traveler eligibility data and sends a message back to the travelers that their
ridematch has been accepted. The
center also supports payment transactions for the service.