Regional Architecture Logo
 

Send Your Comments

 E-Mail

Remote Transit Fare Management Equipment Package

 Architecture Geographic Scope

Description:

 Public traveler interface, such as a kiosk, that provides the capability for the traveler to use a common fare medium for transit fares, tolls, and/or parking lot charges, to calculate the amount due and identify payment problems.

 

Included in:

 BTD Information Display / Point of Sale

Functional Requirements:

1The public interface for travelers shall accept and process current transit passenger fare collection information.
2The 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.
3The 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.
4The public interface for travelers shall provide information to the center for financial authorization and transaction processing.
5The public interface for travelers shall provide an image of all travelers purchasing rides or services to be used for violation processing.
6The public interface for travelers shall determine the routing based on the traveler's destination and the location of the closest transit stop from which a route request is being made.
7The public interface for travelers shall create passenger loading and fare statistics data based upon data collected at a transit stop.
8The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical disabilities.
  

User Service Requirements (fully or partially addressed):

3.0ELECTRONIC PAYMENT
3.1ELECTRONIC PAYMENT SERVICES
3.1.0ITS shall include an Electronic Payment capability. Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions are provided, which are, (1) Electronic Toll Collection, (2) Electronic Fare Collection, (3) Electronic Parking Payment, and (4) Electronic Payment Services Integration.
3.1.1Electronic Payment shall provide an Electronic Toll Collection (ETC) capability.
3.1.2Electronic Payment shall include an Electronic Fare Collection (EFC) capability.
3.1.2.1EFC shall be implemented in a manner that the traveler is able to use a compatible fare medium for all applicable surface transportation services.
3.1.2.2EFC shall provide the capability to implement variable and flexible fare structures.
3.1.2.3EFC shall be capable of identifying voided and/or invalid payment media.
3.1.2.4EFC shall provide the capability for third party payment of transportation services.
3.1.2.5For those systems requiring special eligibility, EFC shall provide the capability to verify the eligibility of riders.
3.1.2.6EFC shall be implemented in a manner that permits expansion into other uses for the payment medium such as payment of retail, telephone, etc.
3.1.2.7EFC shall include the capability to collect the data required to determine accurate ridership levels.
3.1.2.8EFC shall provide the capability for passengers to pay fares without stopping.
3.1.3Electronic Payment shall include an Electronic Parking Payment (EPP) capability.
3.1.3.1EPP shall provide the capability to pay for parking without the use of cash.
3.1.4ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.3EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.