• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

4.6.1: Manage Transit Fare Billing on Vehicle

This process shall manage the traveler fare payments on-board a transit vehicle. This process shall detect embarking travelers on-board a transit vehicle and read data from the traveler card / payment device that they are carrying. The process shall provide an image of all travelers which shall be used for violation processing of those who do not have a traveler card / payment device or whose transit fare transaction fails. It shall obtain an image of the required accuracy under all lighting conditions and over the range of speeds with which travelers will pass through the fare collection point on a transit vehicle. The process shall receive information about the fare that is to be paid and the method of payment adopted by the traveler. It shall always support two modes of operation to complete the back end financial processing: infrastructure interactive, or semi-autonomous batch processing. The interactive method shall be used for individual transactions, such as those in paratransit type operations where value/volume ratios are high. It shall send traveler fare payment data to processes in the Provide Electronic Payment Services function for financial authorization and transaction processing, plus the return of the result for display to the traveler. A failed transaction shall result in the transmission of an image of the traveler to another process. Batch processing shall be used by the process for routes where value/volume ratios are low. It shall be performed using all the same data flows and processes as in the interactive method, except that transaction records are queued in a transaction buffer store which shall be maintained by this process. The accumulated data for the fare transactions shall be sent to the Provide Electronic Payment Services function to request payment processing of one or more transit fare transactions from on-board a transit vehicle. The accumulated data shall be sent on command from the transit vehicle operator, or when the transit vehicle has reached a convenient point on its route. The transit vehicle operator shall be notified when batch processing has completed successfully. In either mode of operation, a record of the status of all transit fare processing shall be sent to an interface process for the fare collection storage database.

This process is associated with the Transit Vehicle OBE physical object.

This process is associated with the following application objects:

• Transit Vehicle On-Board Fare Management

This process is associated with the following data flows:

• bad_tag_list_request - Out
• bad_tag_list_update - In
• bad_transit_tag_data - In
• bad_transit_tag_data - Out
• confirm_vehicle_fare_payment - In
• fare_collection_vehicle_violation_information - Out
• ft-boarding_and_alighting - In
• ft-traveler_vehicle_image - In
• ftvo-fare_transaction_mode_set_up - In
• ftvo-request_batch_mode_data_transfer - In
• request_traveler_vehicle_image - In
• request_vehicle_fare_payment - Out
• traveler_transaction_buffer - In
• traveler_transaction_buffer - Out
• traveler_vehicle_fare - In
• traveler_vehicle_image - Out
• traveler_vehicle_payment_response - Out
• traveler_vehicle_processed_fare_data - Out
• traveler_vehicle_tag_data - In
• traveler_vehicle_tag_identity - Out
• tt-vehicle_access_message - Out
• ttvo-batch_mode_data_transfer_status - Out
• ttvo-request_fare_transaction_mode_set_up - Out