• 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.7.2.4: Manage Transit Fare Billing at Roadside

This process shall generate the data necessary to enable the financial transaction between the traveler and the transit provider to be completed at the roadside, i.e., at a transit stop. The process shall accept and process current transit passenger fare collection information. The process shall perform the front end transaction between the traveler and the transit system, and use the infrastructure interactive mode of operation to complete the back end processing. This means that the process shall send data about each transaction to processes in the Provide Electronic Payment Services function for the back end financial authorization and transaction processing. The process shall then await the return of the result for display to the traveler before accepting the next transaction. A failed transaction shall result in the transmission of an image of the traveler to another process. A record of the status of all transit fare processing shall be sent to another process for storage in a fare collection database.

This process is associated with the Public Information Device physical object.

This process is associated with the following application objects:

• Terminal Fare Management

This process is associated with the following data flows:

• confirm_roadside_fare_payment - In
• fare_collection_roadside_violation_information - Out
• ft-traveler_roadside_image - In
• request_roadside_fare_payment - Out
• traveler_roadside_fare - In
• traveler_roadside_payment_response - Out
• traveler_roadside_processed_fare_data - Out
• traveler_roadside_tag_identity - In
• tt-roadside_access_message - Out