< < TI04 : TI05 : TI06 > >

TI05: Integrated Multi-Modal Electronic Payment

The Integrated Multi-Modal Electronic Payment (IMMEP) service package provides electronic payment capability for transit fares, tolls, road use, parking, and other areas requiring electronic payments. IMMEP enables the provision of payment for transportation services using a single account for multiple public transportation providers. The transportation user establishes an account with a financial service provider (modeled as the Payment Administration Center (PAC)), and the PAC communicates with various public transportation providers to coordinate charges. IMMEP also supports the management of transportation user access rights (i.e., this user can use the subway but not the bus). Payment transactions are centralized; the user provides only a secure, registered token (the 'secureID') to the transportation provider's access control equipment. The transportation provider uses that token and context to initiate transactions with the PAC.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Eligibility Certification Management System Maintainer Eligibility Certification Management System Maintains
Eligibility Certification Management System Manager Eligibility Certification Management System Manages
Eligibility Certification Management System Owner Eligibility Certification Management System Maintainer System Maintenance Agreement
Eligibility Certification Management System Owner Eligibility Certification Management System Manager Operations Agreement
Eligibility Certification Management System Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Eligibility Certification Management System Owner Payment Administration Center Owner Information Exchange Agreement
Eligibility Certification Management System Owner Payment Administration Center User Service Usage Agreement
Eligibility Certification Management System Supplier Eligibility Certification Management System Owner Warranty
Financial Center Maintainer Financial Center Maintains
Financial Center Manager Financial Center Manages
Financial Center Owner Financial Center Maintainer System Maintenance Agreement
Financial Center Owner Financial Center Manager Operations Agreement
Financial Center Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Parking Management Center Owner Information Exchange Agreement
Financial Center Owner Parking Management Center User Service Usage Agreement
Financial Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Payment Administration Center Owner Information Exchange Agreement
Financial Center Owner Payment Administration Center User Service Usage Agreement
Financial Center Owner Shared Use Transportation Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Shared Use Transportation Center Owner Information Exchange Agreement
Financial Center Owner Shared Use Transportation Center User Service Usage Agreement
Financial Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Transit Management Center Owner Information Exchange Agreement
Financial Center Owner Transit Management Center User Service Usage Agreement
Financial Center Supplier Financial Center Owner Warranty
ITS Roadway Payment Equipment Maintainer ITS Roadway Payment Equipment Maintains
ITS Roadway Payment Equipment Manager ITS Roadway Payment Equipment Manages
ITS Roadway Payment Equipment Owner ITS Roadway Payment Equipment Maintainer System Maintenance Agreement
ITS Roadway Payment Equipment Owner ITS Roadway Payment Equipment Manager Operations Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center Owner Information Exchange and Action Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center User Service Usage Agreement
ITS Roadway Payment Equipment Supplier ITS Roadway Payment Equipment Owner Warranty
Light Vehicle OBE Maintainer Light Vehicle OBE Maintains
Light Vehicle OBE Manager Light Vehicle OBE Manages
Light Vehicle OBE Owner ITS Roadway Payment Equipment Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner ITS Roadway Payment Equipment Owner Expectation of Data Provision
Light Vehicle OBE Owner ITS Roadway Payment Equipment User Service Usage Agreement
Light Vehicle OBE Owner Light Vehicle OBE Maintainer System Maintenance Agreement
Light Vehicle OBE Owner Light Vehicle OBE Manager Operations Agreement
Light Vehicle OBE Owner Parking Area Equipment Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner Parking Area Equipment Owner Expectation of Data Provision
Light Vehicle OBE Owner Parking Area Equipment User Service Usage Agreement
Light Vehicle OBE Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner Payment Administration Center Owner Expectation of Data Provision
Light Vehicle OBE Owner Payment Administration Center User Service Usage Agreement
Light Vehicle OBE Supplier Light Vehicle OBE Owner Warranty
Other Payment Administration Centers Maintainer Other Payment Administration Centers Maintains
Other Payment Administration Centers Manager Other Payment Administration Centers Manages
Other Payment Administration Centers Owner Other Payment Administration Centers Maintainer System Maintenance Agreement
Other Payment Administration Centers Owner Other Payment Administration Centers Manager Operations Agreement
Other Payment Administration Centers Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Other Payment Administration Centers Owner Payment Administration Center Owner Information Exchange Agreement
Other Payment Administration Centers Owner Payment Administration Center User Service Usage Agreement
Other Payment Administration Centers Supplier Other Payment Administration Centers Owner Warranty
Parking Area Equipment Maintainer Parking Area Equipment Maintains
Parking Area Equipment Manager Parking Area Equipment Manages
Parking Area Equipment Owner Parking Area Equipment Maintainer System Maintenance Agreement
Parking Area Equipment Owner Parking Area Equipment Manager Operations Agreement
Parking Area Equipment Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Parking Area Equipment Owner Payment Administration Center Owner Information Exchange and Action Agreement
Parking Area Equipment Owner Payment Administration Center User Service Usage Agreement
Parking Area Equipment Supplier Parking Area Equipment Owner Warranty
Parking Management Center Maintainer Parking Management Center Maintains
Parking Management Center Manager Parking Management Center Manages
Parking Management Center Owner Financial Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Financial Center Owner Information Exchange Agreement
Parking Management Center Owner Financial Center User Service Usage Agreement
Parking Management Center Owner Parking Management Center Maintainer System Maintenance Agreement
Parking Management Center Owner Parking Management Center Manager Operations Agreement
Parking Management Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Payment Administration Center Owner Information Exchange Agreement
Parking Management Center Owner Payment Administration Center User Service Usage Agreement
Parking Management Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Personal Information Device Owner Information Provision Agreement
Parking Management Center Owner Personal Information Device User Service Usage Agreement
Parking Management Center Supplier Parking Management Center Owner Warranty
Payment Administration Center Maintainer Payment Administration Center Maintains
Payment Administration Center Manager Payment Administration Center Manages
Payment Administration Center Owner Eligibility Certification Management System Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Eligibility Certification Management System Owner Information Exchange Agreement
Payment Administration Center Owner Eligibility Certification Management System User Service Usage Agreement
Payment Administration Center Owner Financial Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Financial Center Owner Information Exchange Agreement
Payment Administration Center Owner Financial Center User Service Usage Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment Owner Information Provision Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment User Service Usage Agreement
Payment Administration Center Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Light Vehicle OBE Owner Information Provision Agreement
Payment Administration Center Owner Light Vehicle OBE User Service Usage Agreement
Payment Administration Center Owner Other Payment Administration Centers Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Other Payment Administration Centers Owner Information Exchange Agreement
Payment Administration Center Owner Other Payment Administration Centers User Service Usage Agreement
Payment Administration Center Owner Parking Area Equipment Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Parking Area Equipment Owner Information Provision Agreement
Payment Administration Center Owner Parking Area Equipment User Service Usage Agreement
Payment Administration Center Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Parking Management Center Owner Information Exchange Agreement
Payment Administration Center Owner Parking Management Center User Service Usage Agreement
Payment Administration Center Owner Payment Administration Center Maintainer System Maintenance Agreement
Payment Administration Center Owner Payment Administration Center Manager Operations Agreement
Payment Administration Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Personal Information Device Owner Information Provision Agreement
Payment Administration Center Owner Personal Information Device User Service Usage Agreement
Payment Administration Center Owner Shared Use Transportation Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Shared Use Transportation Center Owner Information Exchange Agreement
Payment Administration Center Owner Shared Use Transportation Center User Service Usage Agreement
Payment Administration Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Transit Management Center Owner Information Exchange Agreement
Payment Administration Center Owner Transit Management Center User Service Usage Agreement
Payment Administration Center Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Transit Vehicle OBE Owner Information Provision Agreement
Payment Administration Center Owner Transit Vehicle OBE User Service Usage Agreement
Payment Administration Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Transportation Information Center Owner Information Exchange Agreement
Payment Administration Center Owner Transportation Information Center User Service Usage Agreement
Payment Administration Center Owner Traveler Support Equipment Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Traveler Support Equipment Owner Information Provision Agreement
Payment Administration Center Owner Traveler Support Equipment User Service Usage Agreement
Payment Administration Center Supplier Payment Administration Center Owner Warranty
Payment Device Maintainer Payment Device Maintains
Payment Device Manager Payment Device Manages
Payment Device Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Light Vehicle OBE Owner Information Provision and Action Agreement
Payment Device Owner Light Vehicle OBE User Service Usage Agreement
Payment Device Owner Parking Area Equipment Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Parking Area Equipment Owner Information Provision and Action Agreement
Payment Device Owner Parking Area Equipment User Service Usage Agreement
Payment Device Owner Payment Device Maintainer System Maintenance Agreement
Payment Device Owner Payment Device Manager Operations Agreement
Payment Device Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Transit Vehicle OBE Owner Information Provision and Action Agreement
Payment Device Owner Transit Vehicle OBE User Service Usage Agreement
Payment Device Owner Traveler Support Equipment Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Traveler Support Equipment Owner Information Provision and Action Agreement
Payment Device Owner Traveler Support Equipment User Service Usage Agreement
Payment Device Supplier Payment Device Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Payment Administration Center Owner Information Provision and Action Agreement
Personal Information Device Owner Payment Administration Center User Service Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Shared Use Transportation Center Maintainer Shared Use Transportation Center Maintains
Shared Use Transportation Center Manager Shared Use Transportation Center Manages
Shared Use Transportation Center Owner Financial Center Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Financial Center Owner Information Exchange Agreement
Shared Use Transportation Center Owner Financial Center User Service Usage Agreement
Shared Use Transportation Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Payment Administration Center Owner Information Exchange Agreement
Shared Use Transportation Center Owner Payment Administration Center User Service Usage Agreement
Shared Use Transportation Center Owner Shared Use Transportation Center Maintainer System Maintenance Agreement
Shared Use Transportation Center Owner Shared Use Transportation Center Manager Operations Agreement
Shared Use Transportation Center Supplier Shared Use Transportation Center Owner Warranty
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Financial Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Financial Center Owner Information Exchange Agreement
Transit Management Center Owner Financial Center User Service Usage Agreement
Transit Management Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Payment Administration Center Owner Information Exchange Agreement
Transit Management Center Owner Payment Administration Center User Service Usage Agreement
Transit Management Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Personal Information Device Owner Information Provision Agreement
Transit Management Center Owner Personal Information Device User Service Usage Agreement
Transit Management Center Owner Transit Management Center Maintainer System Maintenance Agreement
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transit Vehicle OBE Maintainer Transit Vehicle OBE Maintains
Transit Vehicle OBE Manager Transit Vehicle OBE Manages
Transit Vehicle OBE Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE Owner Payment Administration Center Owner Expectation of Data Provision
Transit Vehicle OBE Owner Payment Administration Center User Service Usage Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Maintainer System Maintenance Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Manager Operations Agreement
Transit Vehicle OBE Supplier Transit Vehicle OBE Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Payment Administration Center Owner Information Exchange Agreement
Transportation Information Center Owner Payment Administration Center User Service Usage Agreement
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Traveler Support Equipment Maintainer Traveler Support Equipment Maintains
Traveler Support Equipment Manager Traveler Support Equipment Manages
Traveler Support Equipment Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Traveler Support Equipment Owner Payment Administration Center Owner Information Exchange and Action Agreement
Traveler Support Equipment Owner Payment Administration Center User Service Usage Agreement
Traveler Support Equipment Owner Traveler Support Equipment Maintainer System Maintenance Agreement
Traveler Support Equipment Owner Traveler Support Equipment Manager Operations Agreement
Traveler Support Equipment Supplier Traveler Support Equipment Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
ITS Roadway Payment Equipment Roadway Toll Collection Support 7.1.1.4 Check for Advanced Tolls Payment
7.1.2 Produce Roadside Displays
7.1.5 Detect Vehicle for Tolls
Light Vehicle OBE Light Vehicle Payment Service 6.7.5.2 Provide Light Vehicle Driver with Personal Travel Information
6.7.5.3 Provide Light Vehicle Driver Information Interface
7.1.4 Provide Driver Toll Payment Interface
7.1.7 Provide Payment Device Interface for Tolls
7.2.3 Provide Driver Parking Lot Payment Interface
7.2.5 Provide Payment Device Interface for Parking
7.4.4.3 Process Vehicle Electric Charging Payments
7.5.1 Provide Vehicle Payment Device Interface
7.6.3 Provide Driver Road Use Charging Payment Interface
7.6.4 Provide Payment Device Interface for Road Use Charging
Parking Area Equipment Parking Area Electronic Payment 7.2.1.1 Read Parking Lot Vehicle Payment Data
7.2.1.2 Calculate Vehicle Parking Lot Charges
7.2.1.5 Bill Driver for Parking Lot Charges
7.2.2 Produce Parking Lot Displays
Parking Management Center Parking Account and Fee Management 5.4.3 Process Parking Lot Violations
7.2.1.3 Collect Bad Charge Payment Data
7.2.1.4 Check for Advanced Parking Lot Payment
7.2.1.6 Manage Parking Lot Financial Processing
7.2.1.7 Update Parking Lot Data
7.2.1.8 Register for Advanced Parking Lot Payment
Payment Administration Center PAC Payment Administration 5.4.2 Process Violations for Tolls
7.1.1.3 Manage Bad Toll Payment Data
7.1.1.6 Collect Probe Data From Toll Transactions
7.1.1.7 Update Toll Price Data
7.1.1.8 Register for Advanced Toll Payment
7.1.1.9 Manage Toll Processing
7.1.8 Exchange Data with Other Payment Administration
7.4.1.8 Manage Shared Use Payments
7.4.4.1 Process Electric Charging Payments
7.6.1.2 Calculate Vehicle Road Use Payment Charges
7.6.1.4 Manage Road Use Charging Price Data
7.6.1.5 Manage Road Use Charges Processing
7.6.5 Exchange Road Use Charging Data with Other Payment Administration
7.6.6.1 Provide Road Use Charging Services User Interface
7.6.8 Provide Road Use Charging Enforcement Interface
7.7 Administer Multimodal Payments
Personal Information Device Personal Interactive Traveler Information 6.8.1.1.1 Determine Personal Portable Device Guidance Method
6.8.1.1.2 Provide Personal Portable Device Dynamic Guidance
6.8.3.1 Get Traveler Personal Request
6.8.3.2 Provide Traveler with Personal Travel Information
6.8.3.3 Provide Traveler Personal Interface
6.8.3.4 Update Traveler Personal Display Map Data
6.8.3.5 Provide Traveler Transit Services Interface
6.8.3.6 Provide Personal Safety Messages
6.8.3.7 Manage Traveler Personal Social Media Interface
7.5.3 Provide Personal Payment Device Interface
7.6.6.3 Provide Road Use Charging Services Personal Interface
Shared Use Transportation Center Shared Use Account and Fee Management 7.4.1.8 Manage Shared Use Payments
Transit Management Center Transit Center Fare Management 4.2.1.5 Manage Transit Operational Data Store
4.2.1.7 Provide Interface for Other Transit Management Data
4.6.7 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
Transit Vehicle OBE Transit Vehicle On-Board Fare Management 4.6.1 Manage Transit Fare Billing on Vehicle
4.6.2 Determine Traveler Needs on Vehicle
4.6.3 Determine Transit Fare on Vehicle
4.6.4 Provide Traveler Fare Payment Interface on Vehicle
4.6.5 Update Transit Vehicle Fare Data
4.6.6 Provide Transit Vehicle Fare Collection Data
7.3.5 Provide Transit Vehicle Payment Device Interface
Traveler Support Equipment Traveler Fare Management 4.7.2.1 Detect Traveler at Roadside
4.7.2.2 Determine Traveler Needs at Roadside
4.7.2.3 Determine Transit Fare at Roadside
4.7.2.4 Manage Transit Fare Billing at Roadside
4.7.2.5 Provide Traveler Roadside Fare Interface
4.7.2.6 Update Roadside Transit Fare Data
4.7.2.7 Provide Transit Roadside Passenger Data
7.3.4 Provide Remote Terminal Payment Device Interface
7.5.2 Provide Traveler Roadside Payment Device Interface
7.5.4 Provide Traveler Kiosk Payment Device Interface
7.6.6.2 Provide Road Use Charging Services Kiosk Interface

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Eligibility Certification Management System Center The 'Eligibility Certification Management System' verifies that an individual traveler is eligible for discounted transportation or special services (e.g., paratransit, specialized carpools) as a result of local or national policy, and provides the necessary token, crypto-material and/or device for that individual to use the relevant transportation methods at a discounted rate. This object is ostensibly subject to audit policies and procedures, and while that need has been defined in supporting materials, it is outside the scope of ARC-IT.
Financial Center Center The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object.
ITS Roadway Payment Equipment Field 'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration Center).
Light Vehicle OBE Vehicle The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Other Payment Administration Centers Center Representing another Payment Administration Center, 'Other Payment Administration Centers' is intended to provide a source and destination for ITS information flows between payment administration functions. This interface allows reconciliation of toll charges and other payments across different agencies by allowing the exchange of information about clients who have incurred charges in jurisdictions other than their own (billing) customer service center. This interface enables apportioning charges and 'reciprocity' between participating customer service centers.
Parking Area Equipment Field 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
Parking Management Center Center The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Payment Administration Center Center The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
Payment Device Personal The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Shared Use Transportation Center Center The 'Shared Use Transportation Center' manages shared use vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the shared use fleet. It spans contract-driven and centralized dispatch vehicle services such as taxis and ride-hail services, first/last mile automated vehicles as well as personal mobility fleets such as shared-use cars, bicycles, and scooters.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transit Vehicle OBE Vehicle The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Traveler Support Equipment Field 'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms.

Includes Functional Objects:

Functional Object Description Physical Object
Light Vehicle Payment Service 'Light Vehicle Payment Service' supports vehicle payments including VMT- and zone-based payments and payments for other services including fuel/charging services, tolls, and parking. To support VMT-based payment, this application tracks the location of the vehicle at specific times and reports this VMT data along with vehicle identification. A variety of pricing strategies are supported, including strategies that include credits or incentives that reward desired driving patterns and behavior. The onboard equipment supports secure short range communications with connected vehicle roadside equipment to support secure payments. Light Vehicle OBE
PAC Payment Administration 'PAC Payment Administration' provides administration and management of payments associated with electronic toll collection, parking payments, and other e-payments. It provides the back office functions that support enrollment, pricing, reduced fare eligibility, payment reconciliation with financial institutions, and violation notification to enforcement agencies. It also supports dynamic pricing to support demand management, allow/block-list management and token validation. Payment Administration Center
Parking Account and Fee Management 'Parking Account and Fee Management' manages parking fare collection at the Parking Management Center. It provides the back office functions that support control of field parking management systems, supporting payment reconciliation with links to financial institutions. It loads fee data into field systems when those systems are initialized or whenever such information is modified. Parking Management Center
Parking Area Electronic Payment 'Parking Area Electronic Payment' supports electronic payment of parking fees using in-vehicle equipment (e.g., tags) or contact or proximity cards. It includes the field elements that provide the interface to the in-vehicle or card payment device and the back-office functionality that performs the transaction. Parking Area Equipment
Personal Interactive Traveler Information 'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones. Personal Information Device
Roadway Toll Collection Support 'Roadway Toll Collection Support' provides toll plazas the capability to identify properly equipped vehicles, collect electronic tolls, and provide a positive indication to the driver that a toll was collected. Violators are identified and images are collected. Toll transactions are stored and reported to the Payment Administration Center. ITS Roadway Payment Equipment
Shared Use Account and Fee Management 'Shared Use Account and Fee Management' manages user accounts and payments at the Shared Use Transportation Center. It provides the back office functions that support payment reconciliation with links to financial institutions. Shared Use Transportation Center
TIC Payment Support 'TIC Payment Support' supports user payments for traveler services that are provided by or procured through the Transportation Information Center (TIC). Transportation Information Center
Transit Center Fare Management 'Transit Center Fare Management' manages fare collection and passenger load management at the transit center. It provides the back office functions that support transit fare collection, supporting payment reconciliation with links to financial institutions and enforcement agencies for fare violations. It collects data required to determine accurate ridership levels, establish fares, and distribute fare information. It loads fare data into the vehicle prior to the beginning of normal operations and unloads fare collection data from the vehicle at the close out of normal operations. It manages allow/block lists and performs token validation. Transit Management Center
Transit Vehicle On-Board Fare Management 'Transit Vehicle On-board Fare Management' supports fare collection using a standard fare card or other non-monetary fare medium and detects payment violations, manages allow/block lists and performs token validation. Collected fare data are made available to the center. Transit Vehicle OBE
Traveler Fare Management 'Traveler Fare Management' provides the capability for the traveler to access and use a common fare medium for transit fares, tolls, shared use, and/or parking lot charges using a public device at or near the point of service. It accepts a service request and means of payment or smart card, verifies eligibility, calculates the amount due, collects payment (or deducts balance if smart card), manages allow/block lists, performs token validation, and identifies payment problems. It may be implemented using a card reader/dispenser in a point of sale device that includes a communications interface to the financial infrastructure to support payment collection and reconciliation. Traveler Support Equipment

Includes Information Flows:

Information Flow Description
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information.
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction.
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource.
authorization response Notification of status of authorization request.
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies
payment device token information Request for a digital token that can be associated with a credit card number.
payment methods A list of valid payment methods.
payment methods financial institution A list of valid payment methods accepted by a financial center.
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry)
reconciliation response Response indicating that reconciliation of charges using a smart card have been processed.
registered secureIDs Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service.
service registry Catalogue of products and values, access rights and related information.
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges.
smart card reconciliation Detailed list of charges of the form charge/transport provider, taken from a smart card that need to be applied to the listed providers.
traveler eligibility Statement of a traveler's eligibility for discounted transportation
traveler eligibility request Request for status of traveler's eligibility for discounted transportation
traveler payment information Information provided for payment of road use charges, tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.
traveler payment request Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement.
user account coordination Coordination of creation and changes to individual user-centric account information.
user account reports Reports on services offered/provided and associated charges.
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.

Goals and Objectives

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; Improve freight network
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
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; Protect/Enhance the Environment
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; Improve resiliency and reliability
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
Freeway Management: Pricing and Tolling
Integration: Connectivity
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Energy Consumption
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time
System Efficiency: Trip Connectivity
Transit Operations and Management: Automated Fare Collection

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).
Implement an automated fare collection system in Y years for X percent of transit providers in the region. Percent of transit providers using the region's automated fare collection system.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase by X percentage points, every Y years, the percent of transfers performed with automated fare cards. Percent of total transfers performed with automated fare cards.
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 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.
Increase use of system by X percent per year. Percent of fares collected using automated fare collection.
Integrate X additional modes/services into automated fare collection system by Y years. Number of additional modes/service integrated into the fare collection system.
Reduce cost of transfer fees paid by X percent by year Y. Average cost of transfers.
Reduce door-to-door trip time by X percent by year Y. Average door-to-door trip time.
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.

Needs and Requirements

Need Functional Object Requirement
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems. Light Vehicle Payment Service 05 The vehicle shall provide payment information on request under control of the vehicle owner/operator.
PAC Payment Administration 13 The center shall provide secure user account management for the electronic payment system, providing user access to rules and policies, current billing status, invoices, payments, and mechanisms for review and challenge of the collected data.
14 This center shall maintain and publish the prices for the electronic payment system.
16 The center shall receive traveler payment information and compute the cost of using the portion of the transportation system.
17 The center shall process and clear payments from travelers and vehicle owners.
19 The center shall exchange data with other payment administration centers in order to coordinate electronic payments systems use and pricing.
24 The center shall calculate the cost of a complete trip according to a trip plan, accommodating multiple modes if the trip plan uses more than one mode.
25 The center shall be able to authenticate and charge transactions with financial institutions.
26 The center shall be able to charge trips to managed accounts.
27 The center shall provide a bank card / fare pair to a financial processor for conditional approval of fare payment.
28 The center shall approve charges based on a pre-existing white/black list.
29 The Payment Processor needs to collect and aggregate charges over a time period.
30 The Payment Processor needs to provide process charges with financial institutions as a batch process.
31 The Payment Processor needs to learn when a card has been lost.
32 The Payment Processor needs to learn when a card has been used fraudulently.
Parking Area Electronic Payment 01 The parking element shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable features, etc.).
02 The parking element shall read data from the payment device on-board the vehicle or by the traveler.
05 The parking element shall manage the parking lot charges, considering such factors as location, vehicle types, and times of day.
06 The parking element shall process the financial requests and manage an interface to a Financial Institution.
07 The parking element shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments.
10 The parking element shall maintain a list of invalid traveler credit identities.
Roadway Toll Collection Support 01 The field element shall read data from passing vehicles to support toll payment transactions.
Shared Use Account and Fee Management 01 The center shall acquire information from the payment center describing payment methods the institution is willing to accept.
Transit Center Fare Management 04 The center shall support the payment of transit fare transactions using data provided by the traveler cards / payment instruments.
Transit Vehicle On-Board Fare Management 01 The transit vehicle shall read data from the traveler card / payment instrument presented by boarding passengers.
03 The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the traveler's destination.
04 The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well as factors such as the transit routing, transit fare category, traveler history, and route-specific information.
05 The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available to the traveler.
06 The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.
07 The transit vehicle shall include a database on-board the transit vehicle for use in fare processing from which the fares for all possible trips within the transit operational network can be determined.
08 The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares via the traveler card / payment instrument.
09 The transit vehicle shall provide fare statistics data to the center.
02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system. PAC Payment Administration 12 The center shall register users for an electronic payment system, establishing accounts that identify owner billing information and preferences.
Parking Account and Fee Management 02 The center shall support user electronic payment account registration.
Parking Area Electronic Payment 09 The parking element shall process requests for the advanced payment of tolls and transit fares as well as other non-transportation services, e.g. yellow-pages services.
Personal Interactive Traveler Information 19 The personal traveler interface shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system.
Shared Use Account and Fee Management 04 The center shall provide updated user account information to the payment center.
Traveler Fare Management 09 The public interface for travelers shall provide an interface to a transit user payment device in support of a multimodal electronic payment system providing payment for transit fares, tolls, and/or parking lot charges.
03 Regional Transportation Agencies need to be able to perform payment reconciliation in order to obtain their share of payments from the regional payment system. PAC Payment Administration 18 The center shall coordinate with payment administration centers that serve as a clearing house for a regional payment system in order to perform payment reconciliation.
33 The center shall access service metrics for all modes of transport for which they bill. Relevant metrics may include service cost, availability, allowed payments, fare caps and discounts.
34 The center shall provide fare payment to the transport provider when payment for travel on the transport provider vehicles is made with a regional payment system.
TIC Payment Support 01 The center shall coordinate with payment administration centers that serve as a clearing house for a regional payment system in order to perform payment reconciliation.
04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms. Personal Interactive Traveler Information 28 The personal traveler interface shall provide payment information for each segment of a multimodal trip.
Shared Use Account and Fee Management 02 The center shall request payment through the finaincial institution for shared use services when such services are requested by the traveler.
03 The center shall accept information related to balances and debits related to shared use charges.
Transit Vehicle On-Board Fare Management 10 The transit vehicle fare system shall identify for boarding passenger if their payment card is unusable (i.e., blacklisted because it is defective, declared fraudulent, lost or stolen).
11 The transit vehicle fare systems shall determine that the smart card contains sufficient value for the trip it is being used for.
12 The transit vehicle fare system shall deduct the trip fare from the traveler's smart card.
Traveler Fare Management 10 The public interface for travelers shall inform the traveler when a payment card is unusable (i.e., blacklisted because it is defective, declared fraudulent, lost or stolen).
11 The public interface for travelers shall determine that the smart card contains sufficient value for the trip it is being used for.
12 The public interface for travelers shall deduct the trip fare from the traveler's smart card.
05 Travelers need to be able to access transportation modes at a discounted rate, based on their eligibility for the services. PAC Payment Administration 35 The center shall discount a traveler's rate for different segments of a multimodal trip based on the eligibility of the traveler.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
ConOps for Transit Connected Vehicle Draft 3/31/2012
FHWA-JPO-18-744 - Forward-Looking Assessment White Paper: Multimodal and Accessible Travel Standards Assessment – Task 2 Final 4/15/2019
FHWA-JPO-20-822 - Mobility on Demand Marketplace Concept of Operations Blueprint Final 7/1/2020


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Eligibility Certification Management System Moderate Moderate Moderate Class 2
Financial Center Moderate Moderate Moderate Class 2
ITS Roadway Payment Equipment Moderate Moderate High Class 5
Light Vehicle OBE High High High Class 5
Other Payment Administration Centers Moderate High Moderate Class 3
Parking Area Equipment Moderate Moderate High Class 5
Parking Management Center High High Moderate Class 4
Payment Administration Center High High High Class 5
Payment Device Moderate Moderate High Class 5
Personal Information Device High High High Class 5
Shared Use Transportation Center Moderate Moderate Moderate Class 2
Transit Management Center High High Moderate Class 4
Transit Vehicle OBE Moderate Moderate High Class 5
Transportation Information Center Moderate Moderate Moderate Class 2
Traveler Support Equipment Moderate Moderate High Class 5



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Eligibility Certification Management System Payment Administration Center traveler eligibility Moderate Moderate Moderate
Might include PII, at the very least a pseudonym or other proxy, so should be protected for privacy purposes. Must be correct and available so the traveler has access to transport services at the proper fare; if not available might be proxied and in any event will likely affect a subset of travelers, thus LOW availability might be viable. Must be correct and available so the traveler has access to transport services at the proper fare; if not available might be proxied and in any event will likely affect a subset of travelers, thus LOW availability might be viable.
Financial Center Parking Management Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Financial Center Payment Administration Center payment methods financial institution Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Financial Center Payment Administration Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Financial Center Shared Use Transportation Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Financial Center Transit Management Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
ITS Roadway Payment Equipment Payment Administration Center authorization request Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Light Vehicle OBE ITS Roadway Payment Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Light Vehicle OBE Parking Area Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Light Vehicle OBE Payment Administration Center user account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Other Payment Administration Centers Payment Administration Center payment coordination Moderate High Moderate
Contains pricing and reconciliation information shared between agencies. If it includes road use charging information this is MODERATE, as road use charging data is vehicle and owner-specific and can be considered personal. A 3rd party observing this information might learn behavrioral patterns of the individual and use that information in the commission of a crime. If no road use charging information is included, this can be reduced to LOW. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. A delay in reporting this may cause a delay in payment processing, but this is not time critical.
Other Payment Administration Centers Payment Administration Center user account coordination Moderate Moderate Moderate
Contains user PII and must be protected to prevent fraud, identity theft and related malfeasance. Must be correct to ensure correct operations between jurisdictions. Should be available to ensure payment and account processes work betwene jurisdictions; depending on implementation, could be LOW if flow is rarely needed.
Parking Area Equipment Payment Administration Center authorization request Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Parking Management Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Parking Management Center Payment Administration Center account updates Moderate Moderate Moderate
Contains an identifier that can be linked to an account which is in turn likely linked to a person, and thus PII that should be protected. Payment charge and similar information should be correct or it could lead to abuse or incorrect charges. Impact limited to individual accounts however. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Parking Management Center Payment Administration Center service registry Low Moderate Moderate
Much of this information will eventually be widely disseminated to transport users, though there seems little good reason to not obfuscate it. Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect. Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect.
Parking Management Center Personal Information Device registered secureIDs High High Moderate
These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services. Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH. Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Payment Administration Center Eligibility Certification Management System traveler eligibility request Moderate Moderate Moderate
Might include PII, at the very least a pseudonym or other proxy, so should be protected for privacy purposes. Must be correct and available so the traveler has access to transport services at the proper fare; if not available might be proxied and in any event will likely affect a subset of travelers, thus LOW availability might be viable. Must be correct and available so the traveler has access to transport services at the proper fare; if not available might be proxied and in any event will likely affect a subset of travelers, thus LOW availability might be viable.
Payment Administration Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center ITS Roadway Payment Equipment authorization response Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Light Vehicle OBE registered secureIDs High High Moderate
These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services. Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH. Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Payment Administration Center Light Vehicle OBE user account reports High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Payment Administration Center Other Payment Administration Centers payment coordination Moderate High Moderate
Contains pricing and reconciliation information shared between agencies. If it includes road use charging information this is MODERATE, as road use charging data is vehicle and owner-specific and can be considered personal. A 3rd party observing this information might learn behavrioral patterns of the individual and use that information in the commission of a crime. If no road use charging information is included, this can be reduced to LOW. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. A delay in reporting this may cause a delay in payment processing, but this is not time critical.
Payment Administration Center Other Payment Administration Centers user account coordination Moderate Moderate Moderate
Contains user PII and must be protected to prevent fraud, identity theft and related malfeasance. Must be correct to ensure correct operations between jurisdictions. Should be available to ensure payment and account processes work betwene jurisdictions; depending on implementation, could be LOW if flow is rarely needed.
Payment Administration Center Parking Area Equipment authorization response Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Parking Management Center payment methods Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Payment Administration Center Personal Information Device registered secureIDs High High Moderate
These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services. Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH. Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Payment Administration Center Personal Information Device traveler payment request Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Personal Information Device user account reports High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment history information, if corrupted, could lead the user to take action he or she should not take. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. There should be other mechanisms to retrieve this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Payment Administration Center Shared Use Transportation Center payment methods Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Payment Administration Center Transit Management Center payment methods Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Payment Administration Center Transit Management Center reconciliation response Moderate Moderate Moderate
Contains smart card-related information that is personal and if compromised could financially impact the owner of the card. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Transit Vehicle OBE authorization response Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Transportation Information Center reconciliation response Moderate Moderate Moderate
Contains smart card-related information that is personal and if compromised could financially impact the owner of the card. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Traveler Support Equipment authorization response Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Device Light Vehicle OBE actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Payment Device Parking Area Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Payment Device Transit Vehicle OBE actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Payment Device Traveler Support Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Payment Administration Center actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Payment Administration Center payment device token information Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. This flow is necessary in order to properly obfuscate credit card use for transport, but can probably be instantiated offline; if not, there should be alternatives, as it will be difficult to justify HIGH availability as the lack of this flow will inconvenience a limited number of users.
Personal Information Device Payment Administration Center traveler payment information High High Moderate
Contains personal information, potentially including identity, payment information such as account numbers and location. All of this information is personal in nature and acceptable only for the intended destination to receive, as any 3rd party observation could lead to identity theft/compromise and/or payment method theft/compromise. This is information is used to process payment and/or detect fraud. Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. This is information is used to process payment . Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. Availability constrained to MODERATE the fact that alternative mechanisms and compromises exist to ameliorate not completing the flow.
Personal Information Device Payment Administration Center user account setup High High Moderate
Contains user identification and matching vehicle information, which if compromised could lead to identity theft or remote tracking. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. There should be other mechanisms to provide this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Shared Use Transportation Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Shared Use Transportation Center Payment Administration Center account updates Moderate Moderate Moderate
Contains an identifier that can be linked to an account which is in turn likely linked to a person, and thus PII that should be protected. Payment charge and similar information should be correct or it could lead to abuse or incorrect charges. Impact limited to individual accounts however. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Transit Management Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Transit Management Center Payment Administration Center account updates Moderate Moderate Moderate
Contains an identifier that can be linked to an account which is in turn likely linked to a person, and thus PII that should be protected. Payment charge and similar information should be correct or it could lead to abuse or incorrect charges. Impact limited to individual accounts however. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Transit Management Center Payment Administration Center service registry Low Moderate Moderate
Much of this information will eventually be widely disseminated to transport users, though there seems little good reason to not obfuscate it. Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect. Could inconvience travelers if incorrect, and would hamper the operation of payment methods if incorrect or unavailable, which could have widespread network effect.
Transit Management Center Payment Administration Center smart card reconciliation Moderate Moderate Moderate
Contains smart card-related information that is personal and if compromised could financially impact the owner of the card. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Transit Management Center Personal Information Device registered secureIDs High High Moderate
These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services. Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH. Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.
Transit Vehicle OBE Payment Administration Center authorization request Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Transportation Information Center Payment Administration Center smart card reconciliation Moderate Moderate Moderate
Contains smart card-related information that is personal and if compromised could financially impact the owner of the card. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Traveler Support Equipment Payment Administration Center authorization request Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Payment Equipment
Payment Administration Center




System Requirements

System Requirement Need
001 The system shall register users for an electronic payment system, establishing accounts that identify owner billing information and preferences. 02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
002 The system shall provide secure user account management for the electronic payment system, providing user access to rules and policies, current billing status, invoices, payments, and mechanisms for review and challenge of the collected data. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
003 The system shall maintain and publish the prices for the electronic payment system. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
004 The system shall receive traveler payment information and compute the cost of using the portion of the transportation system. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
005 The system shall process and clear payments from travelers and vehicle owners. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
006 The system shall coordinate with payment administration centers that serve as a clearing house for a regional payment system in order to perform payment reconciliation. 03 Regional Transportation Agencies need to be able to perform payment reconciliation in order to obtain their share of payments from the regional payment system.
007 The system shall exchange data with other payment administration centers in order to coordinate electronic payments systems use and pricing. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
008 The system shall support user electronic payment account registration. 02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
009 The system shall support the payment of transit fare transactions using data provided by the traveler cards / payment instruments. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
010 The system shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable features, etc.). 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
011 The system shall read data from the payment device on-board the vehicle or by the traveler. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
012 The system shall manage the parking lot charges, considering such factors as location, vehicle types, and times of day. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
013 The system shall process the financial requests and manage an interface to a Financial Institution. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
014 The system shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
015 The system shall process requests for the advanced payment of tolls and transit fares as well as other non-transportation services, e.g. yellow-pages services. 02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
016 The system shall maintain a list of invalid traveler credit identities. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
017 The system shall read data from passing vehicles to support toll payment transactions. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
03 Regional Transportation Agencies need to be able to perform payment reconciliation in order to obtain their share of payments from the regional payment system.
018 The system shall provide an interface to a transit user payment device in support of a multimodal electronic payment system providing payment for transit fares, tolls, and/or parking lot charges. 02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
03 Regional Transportation Agencies need to be able to perform payment reconciliation in order to obtain their share of payments from the regional payment system.
019 The system shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system. 02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
05 Travelers need to be able to access transportation modes at a discounted rate, based on their eligibility for the services.
020 The system shall read data from the traveler card / payment instrument presented by boarding passengers. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
021 The system shall determine the traveler's travel routing based on the transit vehicle's current location and the traveler's destination. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
022 The system shall calculate the traveler's fare based on the origin and destination provided by the traveler as well as factors such as the transit routing, transit fare category, traveler history, and route-specific information. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
023 The system shall have access to the complete range of transit services (routes and schedules) that are available to the traveler. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
024 The system shall provide a transit fare payment interface that is suitable for travelers with physical disabilities. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
02 Travelers need to be able to set up and update user accounts for a regional multimodal payment system.
025 The system shall include a database on-board the transit vehicle for use in fare processing from which the fares for all possible trips within the transit operational network can be determined. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
026 The system shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares via the traveler card / payment instrument. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
027 The system shall provide fare statistics data to the center. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
028 The system shall provide payment information on request under control of the vehicle owner/operator. 01 Regional Transportation Operations need to have an electronic payment functionality that operates across different modes or systems.
035 The system shall inform the traveler when a payment card is unusable (i.e., blacklisted because it is defective, declared fraudulent, lost or stolen). 04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
037 The system shall provide payment information for each segment of a multimodal trip. 04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
047 The system shall identify for boarding passenger if their payment card is unusable (i.e., blacklisted because it is defective, declared fraudulent, lost or stolen). 04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
048 The system shall determine that the smart card contains sufficient value for the trip it is being used for. 04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
049 The system shall deduct the trip fare from the traveler's smart card. 04 Travelers need to be able to pay for multimodal trips using a variety of payment mechanisms.
 

Implementations


TI05.1 Account-based Implementation

Personal and public transportation, account-based payments.

Account-based Implementation Flows

Information FlowDescriptionInclusion Status
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Optional
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Fundamental
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. At Least One
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource. Optional
authorization response Notification of status of authorization request. Optional
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies Optional
payment device token information Request for a digital token that can be associated with a credit card number. Optional
payment methods A list of valid payment methods. Optional
payment methods A list of valid payment methods. Fundamental
payment methods financial institution A list of valid payment methods accepted by a financial center. Fundamental
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Fundamental
registered secureIDs Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service. Optional
service registry Catalogue of products and values, access rights and related information. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Fundamental
traveler eligibility Statement of a traveler's eligibility for discounted transportation Optional
traveler eligibility request Request for status of traveler's eligibility for discounted transportation Optional
user account coordination Coordination of creation and changes to individual user-centric account information. Optional
user account reports Reports on services offered/provided and associated charges. Optional
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Fundamental
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Optional


Account-based Implementation Functional Objects

Functional Object
Light Vehicle Payment Service
PAC Payment Administration
Parking Account and Fee Management
Parking Area Electronic Payment
Personal Interactive Traveler Information
Roadway Toll Collection Support
Transit Center Fare Management
Transit Vehicle On-Board Fare Management
Traveler Fare Management


Back to Implementation List

TI05.2 Card-based Implementation

Personal and public transportation, card-based payments

Card-based Implementation Flows

Information FlowDescriptionInclusion Status
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. At Least One
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource. Optional
authorization response Notification of status of authorization request. Optional
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies Optional
payment methods A list of valid payment methods. Optional
payment methods financial institution A list of valid payment methods accepted by a financial center. Fundamental
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Fundamental
reconciliation response Response indicating that reconciliation of charges using a smart card have been processed. Optional
service registry Catalogue of products and values, access rights and related information. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Fundamental
smart card reconciliation Detailed list of charges of the form charge/transport provider, taken from a smart card that need to be applied to the listed providers. Optional
traveler eligibility Statement of a traveler's eligibility for discounted transportation Optional
traveler eligibility request Request for status of traveler's eligibility for discounted transportation Optional


Card-based Implementation Functional Objects

Functional Object
Light Vehicle Payment Service
PAC Payment Administration
Parking Account and Fee Management
Parking Area Electronic Payment
Personal Interactive Traveler Information
Roadway Toll Collection Support
Shared Use Account and Fee Management
TIC Payment Support
Transit Center Fare Management
Transit Vehicle On-Board Fare Management
Traveler Fare Management


Back to Implementation List

TI05.3 Pay-as-you-go Implementation

Personal and public transportation, pay-as-you go payments

Pay-as-you-go Implementation Flows

Information FlowDescriptionInclusion Status
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource. Optional
authorization response Notification of status of authorization request. Optional
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies Optional
payment methods A list of valid payment methods. Optional
payment methods financial institution A list of valid payment methods accepted by a financial center. Fundamental
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Fundamental
reconciliation response Response indicating that reconciliation of charges using a smart card have been processed. Optional
service registry Catalogue of products and values, access rights and related information. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Fundamental
smart card reconciliation Detailed list of charges of the form charge/transport provider, taken from a smart card that need to be applied to the listed providers. Optional
traveler eligibility Statement of a traveler's eligibility for discounted transportation Optional
traveler eligibility request Request for status of traveler's eligibility for discounted transportation Optional
traveler payment information Information provided for payment of road use charges, tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives. Fundamental
traveler payment request Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement. Fundamental


Pay-as-you-go Implementation Functional Objects

Functional Object
Light Vehicle Payment Service
PAC Payment Administration
Parking Account and Fee Management
Parking Area Electronic Payment
Personal Interactive Traveler Information
Roadway Toll Collection Support
Shared Use Account and Fee Management
Transit Center Fare Management
Transit Vehicle On-Board Fare Management
Traveler Fare Management


Back to Implementation List

TI05.4 Account-based, personal transport and shared use Implementation

Personal and shared use, account-based

Account-based, personal transport and shared use Implementation Flows

Information FlowDescriptionInclusion Status
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Optional
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Fundamental
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. At Least One
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource. Optional
authorization response Notification of status of authorization request. Optional
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies Optional
payment device token information Request for a digital token that can be associated with a credit card number. Optional
payment methods A list of valid payment methods. Optional
payment methods A list of valid payment methods. Fundamental
payment methods financial institution A list of valid payment methods accepted by a financial center. Fundamental
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Fundamental
registered secureIDs Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service. Optional
service registry Catalogue of products and values, access rights and related information. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Fundamental
traveler eligibility Statement of a traveler's eligibility for discounted transportation Optional
traveler eligibility request Request for status of traveler's eligibility for discounted transportation Optional
user account coordination Coordination of creation and changes to individual user-centric account information. Optional
user account reports Reports on services offered/provided and associated charges. Optional
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Optional


Account-based, personal transport and shared use Implementation Functional Objects

Functional Object
Light Vehicle Payment Service
PAC Payment Administration
Parking Account and Fee Management
Parking Area Electronic Payment
Personal Interactive Traveler Information
Roadway Toll Collection Support
Shared Use Account and Fee Management
Traveler Fare Management


Back to Implementation List

TI05.5 Account-based with all modes Implementation

Personal, public transportation and shared use, account-based

Account-based with all modes Implementation Flows

Information FlowDescriptionInclusion Status
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Optional
account updates Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. Fundamental
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. At Least One
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource. Optional
authorization response Notification of status of authorization request. Optional
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies Optional
payment device token information Request for a digital token that can be associated with a credit card number. Optional
payment methods A list of valid payment methods. Optional
payment methods A list of valid payment methods. Fundamental
payment methods financial institution A list of valid payment methods accepted by a financial center. Fundamental
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Fundamental
registered secureIDs Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service. Optional
registered secureIDs Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service. Fundamental
service registry Catalogue of products and values, access rights and related information. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Fundamental
traveler eligibility Statement of a traveler's eligibility for discounted transportation Optional
traveler eligibility request Request for status of traveler's eligibility for discounted transportation Optional
user account coordination Coordination of creation and changes to individual user-centric account information. Optional
user account reports Reports on services offered/provided and associated charges. Optional
user account reports Reports on services offered/provided and associated charges. Fundamental
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Fundamental
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Optional


Account-based with all modes Implementation Functional Objects

Functional Object
Light Vehicle Payment Service
PAC Payment Administration
Parking Account and Fee Management
Parking Area Electronic Payment
Personal Interactive Traveler Information
Roadway Toll Collection Support
Shared Use Account and Fee Management
Transit Center Fare Management
Transit Vehicle On-Board Fare Management
Traveler Fare Management


Back to Implementation List