Scenario 2-
Assumptions and Elements
•Assumptions:
▫Ridematch is requested by the passenger
using a personal hand-held device application or an internet form.
▫Ridematch is requested by the driver
through an in-vehicle application system using DSRC or wireless mobile
technology.
▫D-RIDE Data Center is capable of processing
various types of data sent through the ridematching applications
and can also process payment.
▫D-RIDE Data Center is capable of
interfacing with traffic data center’s traffic data for the routes being requested by
the travelers.
▫T-DISP Control Center is equipped with
scheduling, CAD/AVL, traffic, and messaging systems that allow for transit
trips and/or private modes to be scheduled.
▫In this scenario, the D-RIDE Data Center
and the T-DISP Control Center are separate entities that can communicate with
one another. *An alternative
scenario would be that the D-RIDE or T-DISP application could function as one combined control center
(not displayed in this scenario).*
•Description of elements:
▫Traveler: Both the passenger
requesting a ride as well as the traveler accepting passengers
▫Passenger: Traveler in need of a
ride
▫Driver: Traveler in need of
passengers
▫D-RIDE Data Center: Processes ridematch
requests and requestor route and location data
▫Traffic Data Center: May also be a TMC;
provides traffic data
▫T-DISP Control Center: Processes transit and
private mode requests from requestor location and route data
▫Transit: Includes fixed-route bus,
BRT, rail, DR, flex, and deviated
▫Private Mode: Includes taxi, shuttle,
and volunteer services