New Jersey Statewide ITS Architecture
Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: On-board Transit Fare and Load Management

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 operator 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: NJT Access Link Vehicles
NJT Bus Vehicles
NJT Fare Card Reader
NJT Rail Trains
Processes: 4.6.1 - Detect Traveler on Vehicle
4.6.2 - Determine Traveler Needs on Vehicle
4.6.3 - Determine Transit Fare on Vehicle
4.6.4 - Manage Transit Fare Billing on Vehicle
4.6.5 - Provide Traveler Fare Payment Interface on Vehicle
4.6.6 - Update Transit Vehicle Fare Data
4.6.7 - Provide Transit Vehicle Passenger Data
7.3.5 - Provide Transit Vehicle Traveler Card Interface
User Service Requirements: 2.0 - PUBLIC TRANSPORTATION MANAGEMENT
2.1 - PUBLIC TRANSPORTATION MANAGEMENT
2.1.1 - PTM 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.1 - To 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.2 - User Interface shall provide the capability for users to access travel related information at mobile locations.
2.2.1.2.2.1 - Mobile 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.2 - Mobile 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.3 - Mobile user interfaces shall provide the capability for users to access travel related information via personal portable devices.
2.2.1.2.2.4 - Mobile user interfaces shall include the capability to provide audible messages to the on-board users.
2.3.0 - ITS shall include a Personalized Public Transit (PPT) function.
2.3.3 - The PPT shall include a Data Collection function.
2.3.3.1 - Data Collection shall include on-board sensors to monitor, but not be limited to, the following:
2.3.3.1(c) - Fare collection.
3.0 - ELECTRONIC PAYMENT
3.1 - ELECTRONIC PAYMENT SERVICES
3.1.0 - ITS 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.1 - Electronic Payment shall provide an Electronic Toll Collection (ETC) capability.
3.1.2 - Electronic Payment shall include an Electronic Fare Collection (EFC) capability.
3.1.2.1 - EFC 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.2 - EFC shall provide the capability to implement variable and flexible fare structures.
3.1.2.3 - EFC shall be capable of identifying voided and/or invalid payment media.
3.1.2.4 - EFC shall provide the capability for third party payment of transportation services.
3.1.2.5 - For those systems requiring special eligibility, EFC shall provide the capability to verify the eligibility of riders.
3.1.2.6 - EFC 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.7 - EFC shall include the capability to collect the data required to determine accurate ridership levels.
3.1.2.8 - EFC shall provide the capability for passengers to pay fares without stopping.
3.1.3 - Electronic Payment shall include an Electronic Parking Payment (EPP) capability.
3.1.3.1 - EPP shall provide the capability to pay for parking without the use of cash.
3.1.4 - ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.3 - EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.

Last updated: 02-11-05