Regional Architecture Logo
 

Send Your Comments

 E-Mail

On-board Transit Fare and Load Management Equipment Package

 Architecture Geographic Scope

Description:

 This Equipment package provides the capability to collect data required to determine accurate ridership levels and implement variable and flexible fare structures. Support shall be provided for the traveler for use of a 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, and allow for third party payment. 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. This Equipment package also supports the capability for two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis if desired. These capabilities require integration with an existing On-board Trip Monitoring Equipment package.

 

Included in:

 BUS Transit Vehicles
Lower RGV Development Council Transit Vehicles
Rainbow Lines Transit Vehicles
The Wave Transit Vehicles

Processes:
4.6.1Detect Transit User on Vehicle
4.6.2Determine Transit User Needs on Vehicle
4.6.3Determine Transit Fare on Vehicle
4.6.4Manage Transit Fare Billing on Vehicle
4.6.5Provide Transit User Fare Payment Interface on Vehicle
4.6.6Update Transit Vehicle Fare Data
4.6.7Provide Transit Vehicle Passenger Data
7.3.5Provide Transit Vehicle Traveler Card Interface
  

User Service Requirements (fully or partially addressed):

2.0PUBLIC TRANSPORTATION MANAGEMENT
2.1PUBLIC TRANSPORTATION MANAGEMENT
2.1.1PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities.
2.1.1.1To enable the automation of the vehicle and facilities operations OVF shall provide the capability to gather the needed data to include, but not be limited to, the following:
2.1.1.1(a)Vehicle passenger loading by bus stop and trip segment.
2.1.1.1(c)Fare collection by fare category.
2.2.1.2.2User Interface shall provide the capability for users to access travel related information at mobile locations.
2.2.1.2.2.1Mobile Location user interfaces shall provide the capability for users, either one passenger at a time or to a group environment, to access travel related information while on board transit vehicles.
2.2.1.2.2.2Mobile user interfaces shall provide the capability for users to access travel related information while in transit vehicles through the use of variable message signs.
2.2.1.2.2.3Mobile user interfaces shall provide the capability for users to access travel related information via personal portable devices.
2.2.1.2.2.4Mobile user interfaces shall include the capability to provide audible messages to the on-board users.
2.3.0ITS shall include a Personalized Public Transit (PPT) function.
2.3.3The PPT shall include a Data Collection function.
2.3.3.1Data Collection shall include on-board sensors to monitor, but not be limited to, the following:
2.3.3.1(c)Fare collection.
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 07-16-2003 using Ronald C. Ice and Associates Web Spinner Technology.