Regional Architecture Logo
 

Send Your Comments

E-Mail

Transit Center Fare and Load Management Equipment Package

Architecture Geographic Scope

Description:

Management of fare collection at the center - includes setting and distributing fare information, central processing of fares for transit as well as other ITS services, links to financial institutions and enforcement agencies.

 

Included in:

BTD Transit Dispatch

Functional Requirements:

1The center shall manage the actual value of transit fares for each segment of each regular transit route, including the transmission of the information to transit vehicles and transit stops or stations.
2The center shall provide the capability for a system operator to manage the transit fares and control the exchange of transit fare information.
3The center shall process the financial requests from the transit vehicles or roadside and manage an interface to a Financial Institution.
4The center shall support the payment of transit fare transactions using data provided by the traveler cards / payment instruments.
5The center shall collect data on fare payment violations and send the data, including images of the violator, to the appropriate enforcement agency.
6The center shall process requests for transit fares to be paid in advance.
7The center shall process requests for the advanced payment of tolls and parking lot charges as well as other non-transportation services, e.g. yellow-pages services.
8The center shall be capable of establishing emergency fare structures to override all other fares during disasters, states of emergency, or evacuations.
9The center shall maintain a list of invalid traveler credit identities, or bad tag lists that can be forwarded to transit vehicles and transit stops or stations.
10The center shall collect passenger loading and fare statistics data to implement variable and flexible fare structures.
11The center shall exchange fare and load information with other transit management centers, including potential Centralized Payments facilities.
12The center shall provide transit fare information to other centers, including traveler information providers upon request.
  

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.0ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options.
1.8.1TDM shall include a communications function.
1.8.1.2The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.2(c)Transit centers.
1.8.1.3TDM shall provide the capability to receive information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.3(c)Transit centers.
1.8.1.4The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(c)Parking availability.
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.0PUBLIC TRANSPORTATION MANAGEMENT
2.1.0ITS shall include a Public Transportation Management (PTM) function.
2.1.2PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
2.1.2.1The PSS shall include a Planning capability.
2.1.2.1.1PSS Planning shall be performed off-line from stored data that were collected in real-time.
2.2.0ITS shall include an En-Route Transit Information (TI) function. En-Route Transit Information provides travelers with real-time transit and high-occupancy vehicle information allowing travel alternatives to be chosen once the traveler is en-route. It consists of three major functions, which are, (1) Information Distribution, (2) Information Receipt, and (3) Information Processing. This capability integrates information from different transit modes and presents it to travelers for decision making.
2.2.1TI shall include an Information Distribution function that disseminates information to travelers.
2.2.1.1Information Distribution shall include an Information Network capability.
2.2.1.1.4The Information Network shall provide all users with information that is from a single source in order to ensure consistency across all 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.
2.3.3.3Data Collection shall support the off-line billing for fares paid by agencies.
2.3.4The PPT shall include an Information Processing function.
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 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.