NJTPA Regional 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: Transit Center Fare and Load Management

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 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 equipment package builds on basic capabilities provided by the Transit Center Tracking and Dispatch equipment package.
Included In: NJT Fare Management System
NJTPA Counties/Municipalities Transit Fare Management Systems
NJTPA Region TMA Fare Management Systems
NJTPA Regional Fare Reciprocity Network
PANYNJ PATH Fare Management System
Private Demand Response Operators Central Systems
Private Demand Response Operators Fare Management Systems
Private Ferry Operators Fare Management Systems
Private Fixed-Route Bus/Shuttle Operators Fare Management Systems
Processes: 4.2.3.5 - Manage Transit Operational Data Store
4.2.3.7 - Provide Interface for Other Transit Management Data
4.6.8 - Manage Transit Vehicle Advanced Payments
5.4.4 - Process Fare Payment Violations
5.4.5 - Process Vehicle Fare Collection Violations
5.4.7 - Process Roadside Fare Collection Violations
7.3.1.1 - Register for Advanced Transit Fare Payment
7.3.1.2 - Determine Advanced Transit Fares
7.3.1.3 - Manage Transit Fare Financial Processing
7.3.1.4 - Check for Advanced Transit Fare Payment
7.3.1.5 - Bill Traveler for Transit Fare
7.3.1.6 - Collect Bad Transit Fare Payment Data
7.3.1.7 - Update Transit Fare Data
7.3.3 - Get Traveler Image for Violation
7.4.1.5 - Process Traveler Other Services Payments
User Service Requirements: 1.0 - TRAVEL AND TRAFFIC MANAGEMENT
1.3 - ROUTE GUIDANCE
1.3.0 - ITS 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.3 - RG shall include a Real-Time Mode for issuing information to travelers.
1.3.3.2 - The Real-Time Mode shall include the capability to operate in either or both of the following two configurations:
1.3.3.2.1 - Real-Time Mode Mobile Based systems shall include the capability to receive infrastructure information and use it in determining routing.
1.8.0 - ITS 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.1 - TDM shall include a communications function.
1.8.1.2 - The 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.3 - TDM 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.4 - The 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.2 - TDM shall include a processing function.
1.8.2.10 - The 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.0 - PUBLIC TRANSPORTATION MANAGEMENT
2.1.0 - ITS shall include a Public Transportation Management (PTM) function.
2.1.2 - PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
2.1.2.1 - The PSS shall include a Planning capability.
2.1.2.1.1 - PSS Planning shall be performed off-line from stored data that were collected in real-time.
2.2.0 - ITS 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.1 - TI shall include an Information Distribution function that disseminates information to travelers.
2.2.1.1 - Information Distribution shall include an Information Network capability.
2.2.1.1.4 - The Information Network shall provide all users with information that is from a single source in order to ensure consistency across all 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.
2.3.3.3 - Data Collection shall support the off-line billing for fares paid by agencies.
2.3.4 - The PPT shall include an Information Processing function.
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.1.4 - ETC shall include the capability to identify those vehicles and/or operators that violate its toll collection process.
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.8 - EFC shall provide the capability for passengers to pay fares without stopping.
3.1.4 - ITS shall include an Electronic Payment Services Integration (EPSI) feature.

Last updated: 02-11-05