ATMS10-Electronic Toll Collection (Service Package*)

Description

This service package provides toll operators with the ability to collect tolls electronically and detect and process violations. The fees that are collected may be adjusted to implement demand management strategies. Field-Vehicle Communication between the roadway equipment and the vehicle is required as well as Fixed Point-Fixed Point interfaces between the toll collection equipment and transportation authorities and the financial infrastructure that supports fee collection. Toll violations are identified and electronically posted to vehicle owners. Standards, inter-agency coordination, and financial clearinghouse capabilities enable regional, and ultimately national interoperability for these services. Two other service packages, APTS04: Transit Fare Collection Management and ATMS16: Parking Facility Management also provide electronic payment services. These three service packages in combination provide an integrated electronic payment system for transportation services.

The vehicle equipment and roadside readers that these systems utilize can also be used to collect road use statistics for highway authorities. This data can be collected as a natural by-product of the toll collection process or collected by separate readers that are dedicated to probe data collection.

Service Package Graphic

Infrastructure Provided Trip PlanningToll Plaza Toll CollectionToll AdministrationFleet AdministrationISP Traveler Data CollectionVehicle Toll/Parking InterfaceRoadway PaymentEnforcement AgencyInformation Service ProviderPayment AdministrationFinancial InstitutionFleet and Freight ManagementTraveler CardVehicletoll data requesttoll datatoll probe datavehicle payment updatepayment violation notificationtoll transactionspayment requesttoll datatoll data requesttransaction statustoll datatoll data requesttoll instructionspaymentrequest for paymentvehicle payment information

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
About this Graphic

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
DMV registration Payment Administration No
Driver request for service Vehicle No
Emergency Management toll service change request Payment Administration No
Financial Institution transaction status Payment Administration Yes
Fleet and Freight Management toll data request Information Service Provider Yes
Fleet and Freight Management toll data request Payment Administration Yes
Information Service Provider toll data Fleet and Freight Management Yes
Information Service Provider toll data request Payment Administration Yes
Other Payment Administration toll coordination Payment Administration No
Payment Administration license request DMV No
Payment Administration toll service change response Emergency Management No
Payment Administration payment violation notification Enforcement Agency Yes
Payment Administration payment request Financial Institution Yes
Payment Administration toll data Fleet and Freight Management Yes
Payment Administration toll data Information Service Provider Yes
Payment Administration toll probe data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Payment Administration toll coordination Other Payment Administration No
Payment Administration payment information presentation Payment Administrator No
Payment Administration toll instructions Roadway Payment Yes
Payment Administration toll probe data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Payment Administration toll service change response Traffic Management No
Payment Administrator payment administration requests Payment Administration No
Roadway Payment roadside transaction status Driver No
Roadway Payment toll transactions Payment Administration Yes
Roadway Payment toll operator information presentation Toll Operator No
Roadway Payment vehicle payment request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle No
Roadway Payment vehicle payment update Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
Toll Operator toll operator requests Roadway Payment No
Traffic Management toll service change request Payment Administration No
Traveler Card payment Vehicle Yes
Vehicle in-vehicle transaction status Driver No
Vehicle vehicle payment information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Payment Yes
Vehicle request for payment Traveler Card Yes
Vehicle Characteristics vehicle characteristics Roadway Payment No
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Support regional economic productivity and development
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Reduce environmental impacts
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
Freeway Management: Pricing and Tolling
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Energy Consumption
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time

Associated Objectives and Performance Measures

Objective Performance Measure
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase the percentage of users carrying electronic toll collection (ETC) transponders by X percent by year Y. Percentage of drivers with ETC transponders.
Increase the share of freeways that are priced to X percent by year Y. Lane miles that are priced.
Increase the share of toll roadways and bridges that are using variable pricing (e.g., congestion pricing) to X percent by year Y. Share of toll roads and bridges using variable pricing.
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce the regional average travel time index by X percent per year. Travel time index (the average travel time during the peak period, using congested speeds, divided by the off-peak period travel time, using posted or free-flow speeds).
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Infrastructure Electronic Payment & Pricing Multi-use Payment
Intelligent Infrastructure Electronic Payment & Pricing Pricing
Intelligent Infrastructure Electronic Payment & Pricing Toll Collection

User Services related to this Service Package:

User Service
1.8 Travel Demand Management
3.1 Electronic Payment Services

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 2 TSDs and so only a portion of the numbered items below refer to the TSD.
ATMS10 transaction set diagrams: Part 1, Part 2,



The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here: TSD Part 1, TSD Part 2,

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. In preparation for paying tolls, the Driver requests payment of the toll (request for service) from the Vehicle. The Roadway Payment Subsystem monitors (vehicle characteristics) the physical characteristics of a passing vehicle so it can be classified and then records an image to uniquely identify it.

  2. When the Roadway Payment Subsystem detects a vehicle, a (vehicle payment request) is made to the Vehicle. The Vehicle issues a request for payment from the Traveler Card. When payment is received from the Traveler Card, a response (vehicle payment information) is sent to the Roadway Payment Subsystem that responds with a vehicle payment update. A message (in-vehicle transaction status) may be sent by the Vehicle to the Driver to confirm payment.

  3. When a toll payment is made, the status of the payment (roadside transaction status) may be displayed to the Driver with a signal, sign, or other equipment. Tolls that are collected (toll transactions) are sent to the Payment Administration Subsystem. The tolls can be sent as collected or can be aggregated and sent on a set schedule or as warranted. The Payment Administration Subsystem can provide information such as speed and travel time on vehicles paying tolls (toll probe data) to the Information Service Provider and Traffic Management Subsystem.

  4. Whenever there is any type of significant regional event that requires evacuation, the Emergency Management Subsystem can send a toll service change request to the Payment Administration Subsystem in order to temporarily reduce or drop the toll charges to facilitate rapid evacuation via a toll road. The Payment Administration Subsystem makes the appropriate changes and then indicates what has been done or will be done in a toll service change response to the Emergency Management Subsystem.

  5. An Information Service Provider can provide the current and advanced toll schedules for different types of vehicles (toll data) to the Fleet and Freight Management Subsystem. This information can be requested (toll data request) or can be provided on a set schedule or as revised.

  6. To assist in travel demand management, the Traffic Management Subsystem may make a toll service change request to change toll prices or procedures. The Payment Administration Subsystem may send a toll service change response to indicate when the request was or will be honored.

  7. The toll collection process is under the asynchronous setting of tolls (toll instructions) by the Payment Administration Subsystem.

  8. The Information Service Provider and the Fleet and Freight Management Subsystem receive current and advanced toll schedules for different types of vehicles (toll data). This information can be requested (toll data request) or it can be sent on a set schedule or as revisions warrant.

  9. Tolls that are collected (toll transactions) by the Roadway Payment Subsystem are sent to the Payment Administration Subsystem. The tolls can be sent as collected or can be aggregated and sent on a set schedule or as warranted. The Payment Administration Subsystem sends the payments (payment request) to a Financial Institution. The Financial Institution may respond with transaction status. When an invalid payment is detected, the Payment Administration Subsystem may contact the DMV (license request) to determine the registered owner of the offending vehicle (registration). Violations (payment violation notification) are reported to an Enforcement Agency.

  10. The Payment Administrator can request (payment administration requests) information on payment operation. When requested or on a set schedule, the Payment Administration Subsystem provides a payment information presentation to the Payment Administrator.

  11. The Toll Operator can make toll operator requests for information on toll operations. When requested or on a set schedule, the Roadway Payment Subsystem provides a toll operator information presentation to the Toll Operator.

  12. The Payment Administration Subsystem can support reciprocity between toll agencies/service centers. The Payment Administration Subsystem exchanges information (toll coordination) to support reconciliation of toll charges by customers that are enrolled with Other Payment Administrations. Additionally, toll schedule information, customer information and other toll service information are provided to coordinate toll operations.