6.4.5: Screen and Match Shared Use Requests

This process shall accept and screen traveler requests for shared use transportation. These requests shall be sent to the process as a result of trip plan requests received from travelers by other processes. This process shall use eligibility data from a shared use data store to screen travelers before they are matched with transportation providers or transportation assets for all or part of their proposed 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 shared use with other shared use confirmed by other travelers, the requesting traveler's eligibility data, and traffic data obtained on request. Traveler shared use requests and shared use data from the data store shall be sent to the data archival process.

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

This process is associated with the following functional objects:

• Shared Use Operations

This process is associated with the following data flows:

• traveler_personal_profile
• traveler_shared_use_request
• traveler_shared_use_preferences
• shared_use_requests_for_archive
• user_account_data
• tsutco-shared_use_transaction_outputs
• fsutco-shared_use_operations_inputs
• public_traveler_shared_use_request