Physical Object: Traveler Support Equipment
Traveler Fare Management
Overview
'Traveler Fare Management' provides the capability for the traveler to access and use a common fare medium for transit fares, tolls, shared use, and/or parking lot charges using a public device at or near the point of service. It accepts a service request and means of payment or smart card, verifies eligibility, calculates the amount due, collects payment (or deducts balance if smart card), manages allow/block lists, performs token validation, and identifies payment problems. It may be implemented using a card reader/dispenser in a point of sale device that includes a communications interface to the financial infrastructure to support payment collection and reconciliation.
This functional object is included in the "Traveler Support Equipment" physical object.
This functional object is included in the following service packages:
This functional object is mapped to the following Functional View PSpecs:
- 4.7.2.1: Detect Traveler at Roadside
- 4.7.2.2: Determine Traveler Needs at Roadside
- 4.7.2.3: Determine Transit Fare at Roadside
- 4.7.2.4: Manage Transit Fare Billing at Roadside
- 4.7.2.5: Provide Traveler Roadside Fare Interface
- 4.7.2.6: Update Roadside Transit Fare Data
- 4.7.2.7: Provide Transit Roadside Passenger Data
- 7.3.4: Provide Remote Terminal Payment Device Interface
- 7.5.2: Provide Traveler Roadside Payment Device Interface
- 7.5.4: Provide Traveler Kiosk Payment Device Interface
- 7.6.6.2: Provide Road Use Charging Services Kiosk Interface
Requirements
| # | Requirement |
|---|---|
| 01 | The public interface for travelers shall accept and process current transit passenger fare collection information. |
| 02 | The public interface for travelers shall calculate a fare based on the origin and destination provided by the traveler, in conjunction with transit routing, transit fare category, and transit user history. |
| 03 | The public interface for travelers shall provide an interface to a transit user traveler card in support of payment for transit fares, tolls, and/or parking lot charges. The stored credit value data from the card shall be collected and updated based on the fare or other charges, or the credit identity shall be collected. |
| 04 | The public interface for travelers shall provide information to the center for financial authorization and transaction processing. |
| 05 | The public interface for travelers shall provide an image of all travelers purchasing rides or services to be used for violation processing. |
| 06 | The public interface for travelers shall determine the routing based on the traveler's destination and the location of the closest transit station/stop from which a route request is being made. |
| 07 | The public interface for travelers shall create fare statistics data based upon data collected at a transit stop. |
| 08 | The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical disabilities. |
| 09 | The public interface for travelers shall provide an interface to a transit user payment device in support of a multimodal electronic payment system providing payment for transit fares, tolls, and/or parking lot charges. |
| 10 | The public interface for travelers shall inform the traveler when a payment card is unusable (i.e., blacklisted because it is defective, declared fraudulent, lost or stolen). |
| 11 | The public interface for travelers shall determine that the smart card contains sufficient value for the trip it is being used for. |
| 12 | The public interface for travelers shall deduct the trip fare from the traveler's smart card. |
Information Flows
Standards
Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.