Regional Architecture Logo
 

Send Your Comments

E-Mail

Toll Administration Equipment Package

Architecture Geographic Scope

Description:

Management of toll collection for private and commercial vehicles, dynamic pricing, payment reconciliation with financial institutions, and violation notification to enforcement agencies.

 

Included in:

Regional Mobility Authority Toll Road Customer Service Center

Functional Requirements:

1The center shall manage toll transactions, including maintaining a log of all transactions and toll pricing structure information.
2The center shall dynamically price tolls based on current traffic condition information.
3For electronic toll payments requiring financial payment, the center shall process the financial information from toll plazas and manage an interface to a Financial Institution.
4The center shall manage a local billing database for toll customers.
5The center shall manage the details of toll payment violations based on tag information from the toll plaza, vehicle registration information from the Department of Motor Vehicles, invalid tag information from a Financial Institution, and previous violation information stored locally, and report such violations to appropriate law enforcement agencies.
6The center shall calculate traffic flow based on timestamped toll transactions for vehicle travel between successive toll plazas and send to other agencies.
7The center shall respond to changes in toll prices from the Toll Administrator.
8The center shall exchange data with other toll agencies to coordinate toll transactions and pricing.
9The center shall support requests for advanced toll payment and provide this information to its toll plazas.
10The center shall support wide-area alerts from emergency centers by passing on the information to its toll plazas and the Toll Administrator.
11The center shall support toll transactions by commercial fleet operators.
  

User Service Requirements (fully or partially addressed):

1.8.2TDM shall include a processing function.
1.8.2.1The processing function shall provide the capability to generate management and control strategies that facilitate the implementation of policies and regulations designed to address the following:
1.8.2.1(f)Public awareness of travel alternatives.
1.8.2.4The processing function shall provide the capability generate guidance for the pricing and control for locations of action that include, but are not limited to, the following:
1.8.2.4(e)Toll facilities.
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.
1.8.2.12The processing function's dynamically generated management and control strategies shall include the capability to respond to the need for control of pollution by generating messages for variable signs that include, but are not limited to, the following:
1.8.2.12(a)Informing of higher tolls.
3.0ELECTRONIC PAYMENT
3.1ELECTRONIC PAYMENT SERVICES
3.1.1Electronic Payment shall provide an Electronic Toll Collection (ETC) capability.
3.1.1.1ETC shall provide the capability for vehicle operators to pay tolls without stopping their vehicles.
3.1.1.2ETC shall provide the capability to implement pricing structures for locally determined needs.
3.1.1.4ETC shall include the capability to identify those vehicles and/or operators that violate its toll collection process.
3.1.1.5ETC shall accommodate single billing to commercial carriers.
3.1.1.6ETC shall provide the capability to automatically access and process each commercial vehicle's required documentation.
3.1.4ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.2EPSI shall provide the capability to integrate fare and toll pricing structures of multiple agencies.
3.1.4.3EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.
3.1.4.4EPSI shall be implemented in a manner that ensures that it may be deployed across multiple agency political boundaries without degrading the services it provides.
5.0EMERGENCY MANAGEMENT
5.3DISASTER RESPONSE AND EVACUATION
5.3.0ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.5Disaster Response shall include a Manage Area Transportation (MAT) function that manages the transportation system in the vicinity of the disaster. Depending on the nature of the disaster and the status of the infrastructure, the following actions may be taken.
5.3.5.3Transit and transit fare schedules and toll schedules shall be modified.
  
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-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.