Interface: Private Vehicles - Private Mobility on Demand Shuttle Services
Information Flow Definitions
trip confirmation (Existing)
Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. Conversely, this flow may also reject the proposed trip plan. Confirmations include the selected route and subsequent trip confirmation messages will be issued for route changes.
trip feedback (Existing)
Information provided at the conclusion of a trip that supports performance monitoring and system optimization. Information provided may include a record of the trip including HOV/HOT lane usage and user provided feedback at the conclusion of the trip.
trip plan (Existing)
A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information. This flow also includes intermediate information that is provided as the trip plan is interactively created, including identification of alternatives, requests for additional information.
trip request (Existing)
Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include the requestor's location or a request for transit and parking reservations and ridesharing options associated with the trip. The trip request also covers requests to revise a previously planned trip and interim updates that are provided as the trip is interactively planned.
user account setup (Existing)
Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.
user profile (Existing)
Information provided to register for a travel service and create a user account. The provided information includes personal identification, traveler preferences (e.g., maximum transfer wait time, maximum walking distance, mode preferences, special needs), device information, a user ID and password, and information to support payment transactions, if applicable.