Travel Services Provider (Terminator*)

This terminator represents the individual organizations that provide any service oriented towards the Traveler. Example services that could be included are gas, food, lodging, vehicle repair, points of interest, and recreation areas. Also included are services specifically directed toward bicyclists and pedestrians such as bicycle shops and parking locations and bicycle and pedestrian rest areas. The Service Providers may pay a fee to have their services advertised to travelers. The interface with the Service Provider is necessary so that accurate, up-to-date service information can be provided to the traveler and to support electronic reservation capabilities included in the ITS User Services.

Inputs/Outputs
Interfaces Diagram

Terminator Interfaces Diagram

This is a context diagram for the entity Travel Services Provider Terminator that shows every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Inputs/Outputs: Architecture Flows* and Data Flows*

Information Service Provider Travel Services Provider

travel service information request (Architecture Flow*) - Requests for travel service information. This flow supports initial registration of service providers and requests for additional traveler service information from registered providers.
Data Flows*:
- ttsp-provider_update_confirm
- ttsp-travel_services_info_request
travel service reservation request (Architecture Flow*) - Reservation request for traveler services (e.g. for a hotel or restaurant) including billing information when applicable.
Data Flows*:
- ttsp-transaction_request

Travel Services Provider Information Service Provider

travel service information (Architecture Flow*) - Information supplied by a service provider (e.g., a hotel or restaurant) that identifies the service provider and provides details of the service offering. This flow covers initial registration of a service provider and subsequent submittal of new information and status updates so that data currency is maintained.
Data Flows*:
travel service reservations (Architecture Flow*) - Traveler service (e.g., for a hotel or restaurant) reservation information and status, including information on associated billing transactions, when applicable.
Data Flows*:
- ftsp-transaction_confirmation