6.4.2: Match Rider and Provider

This process shall match travelers for ridesharing trips. The process shall attempt to achieve a match by considering some or all of the following: the origin and destination of the traveler's proposed trip, any routing constraints, preferences specified by the traveler, compatibility of this rideshare with rideshares confirmed by other travelers, the requesting traveler's eligibility data, and traffic data obtained on request. The process shall consider the possible disbenefits to other travelers who will be part of the same rideshare when finding the rideshare best suited to the traveler's requirements. The process shall store data about selected rideshares in the rideshare data store, and shall update the data when confirmation of the rideshare acceptance is received from another process.

This process is associated with the Transportation Information Center physical object.

This process is associated with the following application objects:

TIC Dynamic Ridesharing

This process is associated with the following data flows:

rideshare_confirmation_data - In
rideshare_data - In
rideshare_data - Out
rideshare_request_from_eligible_traveler - In
rideshare_selection - Out
traffic_data_for_ridesharing - In
traffic_data_request_from_ridesharing - Out

OST-R's privacy policies and procedures do not necessarily apply to external web sites.
We suggest contacting these sites directly for information on their data collection and distribution policies.

Last Updated 6/7/2016