Scenario #1: Single transit
provider operating multiple modes with the same on-board systems and data communications systems; If a trip
cannot be met on public transportation, it is sent to a private mode.
Assumptions: CAD/AVL and on-board systems; Data and
voice communications; New or modified Scheduling System; New or modified Customer Messaging
System
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
Real-time traffic data sent to Control Center, and real-time
probe data sent to Traffic Management Center
Data messages sent back and forth between Control Center and
Transit Modes (i.e. vehicles) via cellular or data radio communications
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)
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 received in Control Center that has
route and schedule data available
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
iii.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