Regional Architecture Logo
 

Send Your Comments

 E-Mail

On-board Transit Fare and Load Management Equipment Package

 Architecture Geographic Scope

Description:

 On-board systems provide variable and flexible fare collection using a travelers fare medium (stored value cards or other payment instrument). Collect data required to determine accurate ridership levels and fare statistics.

 

Included in:

 BTD Demand Response Transit Vehicles
BTD Fixed Route Transit Vehicles

Functional Requirements:

1The transit vehicle shall detect embarking travelers on-board a transit vehicle and read data from the traveler card / payment instrument that they are carrying.
2The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not have a traveler card / payment instrument or whose transit fare transaction fails.
3The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the traveler's destination.
4The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well as factors such as the transit routing, transit fare category, traveler history, and route-specific information.
5The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available to the traveler.
6The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.
7The transit vehicle shall include a database on-board the transit vehicle for use in fare processing from which the fares for all possible trips within the transit operational network can be determined.
8The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during disasters, states of emergency or evacuations.
9The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares via the traveler card / payment instrument.
10The transit vehicle shall provide passenger loading and fare statistics data to the center.
  

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