Regional Architecture Logo
 

Send Your Comments

 E-Mail

Remote Transit Fare Management Equipment Package

 Architecture Geographic Scope

Description:

 This Equipment package provides the capability for the traveler to use a common fare medium for all applicable surface transportation services, to pay without stopping, have payment media automatically identified as void and/or invalid and eligibility verified. This may be implemented as a payment instrument reader at a kiosk. In addition, capability to provide expansion into other uses for payment medium such as retail and telephone and for off-line billing for fares paid by agencies shall be supported.

 

Included in:

 EZ Rider Transit Point of Sale / Customer Information Systems

Processes:
4.7.2.1Detect Transit User at Roadside
4.7.2.2Determine Transit User Needs at Roadside
4.7.2.3Determine Transit Fare at Roadside
4.7.2.4Manage Transit Fare Billing at Roadside
4.7.2.5Provide Transit User Roadside Fare Interface
4.7.2.6Update Roadside Transit Fare Data
4.7.2.7Provide Transit Roadside Passenger Data
7.3.4Provide Remote Terminal Traveler Card Interface
7.5.2Provide Transit User Roadside Traveler Card Interface
  

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 01-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.