Traveler Card (Terminator*)

This terminator represents the entity that enables the actual transfer of electronic information from the user of a service (I.e. a traveler) to the provider of the service. This may include the transfer of funds through means of an electronic payment instrument. The device, like a smart card, may also hold and update the traveler's information such as personal profiles or trip histories.

Inputs/Outputs
Interfaces Diagram

Terminator Interfaces Diagram

This is a context diagram for the entity Traveler Card 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*

Parking Management Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*:
- ttc-debited_traveler_parking_payment
- ttc-request_traveler_parking_payment

Personal Information Access Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*:
- ttc-debited_payment_at_personal_device
traveler card update (Architecture Flow*) - Information updated concerning traveler's personal data including items such as address, trip records, and profile data.
Data Flows*:
- ttc-traveler_personal_information_update

Remote Traveler Support Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*:
traveler card update (Architecture Flow*) - Information updated concerning traveler's personal data including items such as address, trip records, and profile data.
Data Flows*:
- ttc-traveler_remote_personal_information_update

Transit Vehicle Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*:

Traveler Card Parking Management

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:
- ftc-confirm_traveler_parking_payment
- ftc-traveler_parking_input_credit_identity

Traveler Card Personal Information Access

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:
- ftc-traveler_personal_input_credit_identity
traveler card information (Architecture Flow*) - The traveler personal information such as name, address, license number, and trip records and profile data.
Data Flows*:
- ftc-traveler_personal_information

Traveler Card Remote Traveler Support

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:
traveler card information (Architecture Flow*) - The traveler personal information such as name, address, license number, and trip records and profile data.
Data Flows*:
- ftc-traveler_remote_personal_information

Traveler Card Transit Vehicle

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:

Traveler Card Vehicle

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:

Vehicle Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*: