Transactions:
1)Regular processes occurring on a daily
basis, including:
•CAD/AVL system sending location data for all vehicles in the
system that are eligible for service every 30 seconds via cellular or data radio
communications
•Data messages sent back and forth between Control Center and
Transit Modes (i.e. vehicles) via cellular or data radio communications
•Real time traffic data sent to Control Center
•Manifests or sets of trips are sent from Control Center to
vehicles via cellular or data radio communications (or for fixed route modes are
accessed at driver log on)
•Multiple agencies sending location data to an interface that
“neutralizes” the location data within the scheduling system
2)Rider requests a trip with origin, destination and time (ODT) and return trip using a web enabled mobile device with software
application
3)Request sent to Control Center that has route and schedule data
4)Trip request analyzed:
i.Trip request
approved through scheduling system
ii.Message sent to vehicle that needs to deviate to pick up the
rider Message sent to rider that trip can be made
5)Trip request analyzed but denied:
i.Message sent
to rider with information about private mode and cost of private mode
ii.Rider
approves private trip and cost
iii.Message sent
to Private Mode vehicle
6)Accepted trips are adjusted into remaining,
downstream schedules for vehicles
Scenario #2: Multiple providers
operating in a multimodal environment; if a trip can’t be made on public transportation, it is sent to
private mode; Different providers may use a different CAD/AVL system.
Assumptions: CAD/AVL and
on-board equipment; interface necessary for location data and messaging to vehicles.