Regional Architecture Logo
 

Send Your Comments

 E-Mail

Transit Center Fare and Load Management Equipment Package

 Architecture Geographic Scope

Description:

 This Equipment package provides the capability to accept collected 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 shall be provided through a workstation type processor with GUI, high capacity storage, ride share software housed in a building with dialup lines and wireline telephone and require integration with an existing Transit Center Tracking and Dispatch Equipment package.

 

Included in:

 BMT Transit Dispatch
City of Port Arthur Transit System Dispatch

Processes:
4.6.8Manage Transit Vehicle Advanced Payments
5.4.4Process Fare Payment Violations
5.4.5Process Vehicle Fare Collection Violations
5.4.7Process Roadside Fare Collection Violations
7.3.1.1Register for Advanced Transit Fare Payment
7.3.1.2Determine Advanced Transit Fares
7.3.1.3Manage Transit Fare Financial Processing
7.3.1.4Check for Advanced Transit Fare Payment
7.3.1.5Bill Transit User for Transit Fare
7.3.1.6Collect Bad Transit Fare Payment Data
7.3.1.7Update Transit Fare Data
7.4.1.5Process Transit User Other Services Payments
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.3ROUTE GUIDANCE
1.3.0ITS shall include a Route Guidance (RG) function. Route Guidance will provide travelers with directions to selected destinations. Four functions are provided, which are, (1) Provide Directions, (2) Static Mode, (3) Real-Time Mode, and (4) User Interface.
1.3.3RG shall include a Real-Time Mode for issuing information to travelers.
1.3.3.2The Real-Time Mode shall include the capability to operate in either or both of the following two configurations:
1.3.3.2.1Real-Time Mode Mobile Based systems shall include the capability to receive infrastructure information and use it in determining routing.
1.8.2TDM shall include a processing function.
1.8.2.10The processing function's dynamically generated management and control strategies shall include the parking management and controls to include, but not be limited to, the following:
1.8.2.10(a)Price structure.
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.
2.3.3.3Data Collection shall support the off-line billing for fares paid by agencies.
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.1.4ETC shall include the capability to identify those vehicles and/or operators that violate its toll collection process.
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.8EFC shall provide the capability for passengers to pay fares without stopping.
3.1.4ITS shall include an Electronic Payment Services Integration (EPSI) feature.
  
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 12-12-2003 using Ronald C. Ice and Associates Web Spinner Technology.