< < TI03 : TI04 : TI05 > >

TI04: Trip Planning and Payment

This service package offers the user trip planning and pre-trip guidance services. It generates a trip plan, including a multimodal route and associated service information (e.g., parking information), based on traveler preferences and constraints. Routes may be based on static information or reflect real time network conditions. Unlike TI03, where the user equipment determines the route, the route determination functions are performed by the center in this service package. The trip plan may be confirmed by the traveler and advanced payment and reservations for transit and alternate mode (e.g., airline, rail, and ferry) trip segments, and ancillary services are accepted and processed. The confirmed trip plan may include specific routing information that can be supplied to the traveler as general directions or as turn-by-turn route guidance depending on the level of user equipment.

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
Alternate Mode Transportation Center Maintainer Alternate Mode Transportation Center Maintains
Alternate Mode Transportation Center Manager Alternate Mode Transportation Center Manages
Alternate Mode Transportation Center Owner Alternate Mode Transportation Center Maintainer System Maintenance Agreement
Alternate Mode Transportation Center Owner Alternate Mode Transportation Center Manager Operations Agreement
Alternate Mode Transportation Center Owner TIC Operator Application Usage Agreement
Alternate Mode Transportation Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Alternate Mode Transportation Center Owner Transportation Information Center Owner Information Provision Agreement
Alternate Mode Transportation Center Owner Transportation Information Center User Service Usage Agreement
Alternate Mode Transportation Center Supplier Alternate Mode Transportation Center Owner Warranty
Electric Charging Management Center Maintainer Electric Charging Management Center Maintains
Electric Charging Management Center Manager Electric Charging Management Center Manages
Electric Charging Management Center Owner Electric Charging Management Center Maintainer System Maintenance Agreement
Electric Charging Management Center Owner Electric Charging Management Center Manager Operations Agreement
Electric Charging Management Center Owner TIC Operator Application Usage Agreement
Electric Charging Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Electric Charging Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Electric Charging Management Center Owner Transportation Information Center User Service Usage Agreement
Electric Charging Management Center Supplier Electric Charging Management Center Owner Warranty
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
Light Vehicle Driver Light Vehicle OBE Operates
Light Vehicle OBE Maintainer Light Vehicle OBE Maintains
Light Vehicle OBE Manager Light Vehicle Driver System Usage Agreement
Light Vehicle OBE Manager Light Vehicle OBE Manages
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 TIC Operator Application Usage Agreement
Light Vehicle OBE Owner TIC Operator Vehicle Operating Agreement
Light Vehicle OBE Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner Transportation Information Center Owner Expectation of Data Provision
Light Vehicle OBE Owner Transportation Information Center User Service Usage Agreement
Light Vehicle OBE Supplier Light Vehicle OBE Owner Warranty
Maint and Constr Management Center Maintainer Maint and Constr Management Center Maintains
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Maint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Owner TIC Operator Application Usage Agreement
Maint and Constr Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Transportation Information Center Owner Information Provision Agreement
Maint and Constr Management Center Owner Transportation Information Center User Service Usage Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
Other Transportation Information Centers Maintainer Other Transportation Information Centers Maintains
Other Transportation Information Centers Manager Other Transportation Information Centers Manages
Other Transportation Information Centers Owner Other Transportation Information Centers Maintainer System Maintenance Agreement
Other Transportation Information Centers Owner Other Transportation Information Centers Manager Operations Agreement
Other Transportation Information Centers Owner TIC Operator Application Usage Agreement
Other Transportation Information Centers Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Other Transportation Information Centers Owner Transportation Information Center Owner Information Exchange Agreement
Other Transportation Information Centers Owner Transportation Information Center User Service Usage Agreement
Other Transportation Information Centers Supplier Other Transportation Information Centers Owner Warranty
Parking Management Center Maintainer Parking Management Center Maintains
Parking Management Center Manager Parking Management Center Manages
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 TIC Operator Application Usage Agreement
Parking Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Parking Management Center Owner Transportation Information Center 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 Payment Administration Center Maintainer System Maintenance Agreement
Payment Administration Center Owner Payment Administration Center Manager Operations 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 TIC Operator Application 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 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 Supplier Payment Administration Center Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Manager Traveler System 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 Owner TIC Operator Application Usage Agreement
Personal Information Device Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Transportation Information Center Owner Information Provision and Action Agreement
Personal Information Device Owner Transportation Information Center User Service Usage 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 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 Owner TIC Operator Application Usage Agreement
Shared Use Transportation Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Transportation Information Center Owner Information Provision Agreement
Shared Use Transportation Center Owner Transportation Information Center User Service Usage Agreement
Shared Use Transportation Center Supplier Shared Use Transportation Center Owner Warranty
TIC Operator Transportation Information Center Operates
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Owner TIC Operator Application Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Traffic Management Center Owner Transportation Information Center User Service Usage Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
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 TIC Operator Application 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 Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Transit Management Center Owner Transportation Information Center User Service Usage Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager TIC Operator System Usage Agreement
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Electric Charging Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Electric Charging Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Electric Charging Management Center User Service Usage Agreement
Transportation Information Center Owner Light Vehicle Driver Application Usage Agreement
Transportation Information Center Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Light Vehicle OBE Owner Information Provision Agreement
Transportation Information Center Owner Light Vehicle OBE User Service Usage Agreement
Transportation Information Center Owner Other Transportation Information Centers Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Other Transportation Information Centers Owner Information Exchange Agreement
Transportation Information Center Owner Other Transportation Information Centers User Service Usage Agreement
Transportation Information Center Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Parking Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Parking Management Center User Service Usage Agreement
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 Personal Information Device Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Personal Information Device Owner Information Provision Agreement
Transportation Information Center Owner Personal Information Device User Service Usage Agreement
Transportation Information Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Traffic Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Traffic Management Center User Service Usage Agreement
Transportation Information Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Transit Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Transit Management 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 Owner Traveler Application Usage Agreement
Transportation Information Center Owner Traveler Support Equipment Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Traveler Support Equipment Owner Information Provision Agreement
Transportation Information Center Owner Traveler Support Equipment User Service Usage Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Traveler Personal Information Device Operates
Traveler Traveler Support Equipment Operates
Traveler Support Equipment Maintainer Traveler Support Equipment Maintains
Traveler Support Equipment Manager Traveler System Usage Agreement
Traveler Support Equipment Manager Traveler Support Equipment Manages
Traveler Support Equipment Owner TIC Operator Application Usage Agreement
Traveler Support Equipment Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Traveler Support Equipment Owner Transportation Information Center Owner Information Exchange and Action Agreement
Traveler Support Equipment Owner Transportation Information 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
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 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 Trip Planning and Route Guidance 6.8.1.1.1 Determine Personal Portable Device Guidance Method
6.8.1.1.2 Provide Personal Portable Device Dynamic Guidance
6.8.1.2 Provide Personal Portable Device Guidance Interface
6.8.1.4 Update Traveler Navigable Map Database
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.5 Provide Traveler Transit Services Interface
7.5.3 Provide Personal Payment Device Interface
Transit Management Center Transit Center Connection Protection 4.1.5.2 Manage Transit Vehicle Deviations
4.1.6.1 Process Demand Responsive Transit Trip Request
4.1.8 Manage Individual Service Requests
4.2.1.3 Produce Transit Service Data for External Use
4.2.1.7 Provide Interface for Other Transit Management Data
4.2.1.8 Provide Interface for Transit Service Raw Data
7.4.1.5 Process Traveler Other Services Payments
Transportation Information Center Shared Use Operations 6.4.5 Screen and Match Shared Use Requests
6.4.6 Respond to Shared Use Request
6.4.7 Confirm Traveler Shared Use Request
TIC Data Collection 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.3 Collect Transit Operations Data
6.2.4 Collect Multimodal Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.2.6 Collect Emergency Traveler Data
6.5.4 Process Travel Services Provider Data
6.6.2.3 Provide Route Segment Data for Other Areas
7.4.2 Collect Price Data for Traveler Information Use
TIC Dynamic Ridesharing 6.1.1 Provide Trip Planning Information to Traveler
6.1.2 Confirm Traveler's Trip Plan
6.4.1 Screen Rider Requests
6.4.2 Match Rider and Provider
6.4.3 Report Ride Match Results to Requestor
6.4.4 Confirm Traveler Rideshare Request
7.4.1.7 Process Traveler Rideshare Payments
TIC Trip Planning 6.1.1 Provide Trip Planning Information to Traveler
6.1.2 Confirm Traveler's Trip Plan
6.1.3 Provide Operator Interface for Trip Planning Parameters
6.10 Manage Traveler Profiles
6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.5.4 Process Travel Services Provider Data
6.5.9 Provide Traveler Alert Interface
6.6.1 Provide Multimodal Route Selection
6.6.2.1 Calculate Vehicle Route
6.6.2.2 Provide Vehicle Route Calculation Data
6.6.3 Provide Operator Interface for Route Parameters
6.6.4 Select Transit Route
6.6.5 Select Other Routes
7.1.6 Distribute Advanced Charges and Fares
7.3.2 Distribute Advanced Tolls and Parking Lot Charges
7.4.1.3 Process Driver Map Update Payments
7.4.1.4 Process Traveler Map Update Payments
7.4.1.6 Process Traveler Trip and Other Services Payments
7.4.3 Route Traveler Advanced Payments
Traveler Support Equipment Traveler Trip Planning 6.3.1 Get Traveler Request
6.3.2 Inform Traveler
6.3.3 Provide Public Traveler Interface
Vehicle Light Vehicle Trip Planning and Route Guidance 3.1.3 Process Vehicle On-board Data
6.7.1.1.1 Determine In-Vehicle Guidance Method
6.7.1.1.2 Provide Dynamic In-Vehicle Guidance
6.7.1.2 Provide Driver Guidance Interface
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Get Driver Personal Request
6.7.3.2 Provide Driver with Personal Travel Information

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
Alternate Mode Transportation Center Center The 'Alternate Mode Transportation Center' provides the interface through which non-ITS transportation systems (e.g., airlines, ferry services, passenger-carrying heavy rail) can exchange data with ITS. This two-way interface enables coordination for efficient movement of people across multiple transportation modes. It also enables the traveler to efficiently plan itineraries which include segments using other modes.
Electric Charging Management Center Center The 'Electric Charging Management Center' provides management services for one or more electric vehicle charging stations used to charge hybrid and all-electric vehicles. This includes public charging stations that support consumers, workplace charging stations, and fleet charging stations using plug in (level 1, 2, fast charge, etc.), or inductive charging methods. The center interfaces with traveler information providers to support payment of charging and to disseminate information about the availability and status of their chargers and to coordinate reservations by drivers for the use of a charger. The center also interfaces with the appropriate electric utility that supplies electricity for its chargers to coordinate demand on the power grid.
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.
Light Vehicle Driver Vehicle The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle.
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.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Other Transportation Information Centers Center Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant.
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.
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.
TIC Operator Center This 'TIC Operator' represents the person or people that monitor and manage traveler information services provided by the Transportation Information Center.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
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.
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 Personal The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
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
Electric Charging Management 'Electric Charging Management' monitors electric charging operations for one or more charging stations, monitoring current operational status including current occupancy and rates supporting back office operations. This function also includes support for reservations and payment of electric charging. Electric Charging Management Center
Light Vehicle Trip Planning and Route Guidance 'Light Vehicle Trip Planning and Route Guidance' includes the in-vehicle system that coordinates with a traveler information center to provide a personalized trip plan to the driver. The trip plan is calculated by the Transportation Information Center (TIC) based on preferences and constraints supplied by the driver and provided to the driver for confirmation. Reservations and advanced payment may also be processed to confirm the trip plan. Coordination with the TIC may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including in-vehicle systems that provide a basic trip plan to the driver as well as more sophisticated systems that can provide turn by turn guidance to the driver along the route. 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
Personal Trip Planning and Route Guidance 'Personal Trip Planning and Route Guidance' provides a personalized trip plan to the traveler. The trip plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. Coordination may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including systems that provide a basic trip plan to the traveler as well as more sophisticated systems that can provide transition by transition guidance to the traveler along a multi-modal route with transfers. Devices represented by this functional object include desktop computers at home, work, or at major trip generation sites, plus personal devices such as tablets and smart phones. Personal Information Device
Shared Use Operations 'Shared Use Operations' provides shared use services for eligible travelers, connecting with travelers for specific trips or vehicle usage based on preferences. It also provides the traveler with information about the shared use vehicle (including location information) and provides access codes to either the traveler or directly to the vehicle. Reservations and advanced payment are also supported so that each segment of the shared use/ trip may be confirmed. Shared Use Transportation Center
TIC Data Collection 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. Transportation Information Center
TIC Dynamic Ridesharing 'TIC Dynamic Ridesharing' provides dynamic rideshare matches for eligible travelers, connecting riders and drivers for specific trips based on preferences. This ridesharing/ride matching capability also arranges connections to transit or other multimodal services for portions of a multi-segment trip that includes ridesharing. Reservations and advanced payment are also supported so that each segment of the trip may be confirmed. Transportation Information Center
TIC Trip Planning 'TIC Trip Planning' provides pre-trip and en route trip planning services for travelers. It receives origin, destination, constraints, and preferences and returns trip plan(s) that meet the supplied criteria. Trip plans may be based on current traffic and road conditions, transit schedule information, and other real-time traveler information. Candidate trip plans are multimodal and may include vehicle, transit, and alternate mode segments (e.g., rail, ferry, bicycle routes, and walkways) based on traveler preferences. It also confirms the trip plan for the traveler and supports reservations and advanced payment for portions of the trip. The trip plan includes specific routing information and instructions for each segment of the trip and may also include information and reservations for additional services (e.g., parking) along the route. Transportation Information Center
Transit Center Connection Protection 'Transit Center Connection Protection' manages the coordination of transit transfers between routes within a single transit agency, between routes of different transit agencies, or between different modes (e.g. a bus transit route and a ferry route). This functional object also supports the capability for an individual traveler to obtain connection protection throughout a specific transit trip. This application may be implemented through peer-to-peer sharing between agencies control systems or as a central transit transfer request brokerage that facilitates the management and coordination of transfers across multiple agencies and control systems. Transit Management Center
Traveler Trip Planning 'Traveler Trip Planning' provides a personalized trip plan to the traveler. The trip plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. It represents kiosks and other fixed public interactive displays that may be used by travelers in public areas. 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.
alternate mode information Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network.
electric charging information General electric charging information and status, including current availability, pricing, and status information
electric charging reservation confirmation Confirmation for electric charging reservation
electric charging reservation request Reservation request for use of an electric charging station.
electric charging station information Information provided for electric charging stations identifying the location, operating hours, current availability, charging capacity and standards supported, access restrictions, and rates/fee structure.
incident information for public Report of current desensitized incident information prepared for public dissemination.
light vehicle driver input Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
light vehicle driver updates Information provided to the light vehicle driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
logged vehicle routes Anticipated route information for guided vehicles, special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor's motorcade) that may require changes in traffic control strategy.
maint and constr work plans Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
parking information General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots.
parking reservation confirmation Confirmation for parking reservation.
parking reservation request Reservation request for parking including special requests and needs such as disabled space access, electric vehicle charging, etc.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
roadway maintenance status Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
shared use status Status of usage by shared use providers. Includes asset inventory and status. Could also include information on specific travelers to support multimodal trip planning.
TIC operations information presentation Presentation of information to the TIC Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms.
TIC operator input User input from the TIC system operator including requests to monitor current system operation and inputs to affect system operation including tuning and performance enhancement parameters to traveler information algorithms.
toll data Current toll schedules for different types of vehicles as well as advanced toll payment information.
toll data request Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
transit and fare schedules Transit service information including routes, schedules, and fare information. This also includes on-demand service information.
transit schedule adherence information Dynamic transit schedule adherence and transit vehicle location information.
transit service information Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.
transit trip plan An origin-destination transit trip that may involve multiple modes and connections.
transit trip request Request for a transit trip plan that is responsive to traveler requirements such as schedule, cost, or duration.
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 input User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.
trip access coordination Access token granting the bearer the right to use a given transportation resource; typically used when one payment provider is paid for a trip using multiple travel providers; the token is used by the Traveler to gain access to one or more of the travel provider resource (e.g., a transit ride).
trip confirmation Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. Conversely, this flow may also reject the proposed trip plan. Confirmations include the selected route and subsequent trip confirmation messages will be issued for route changes.
trip feedback Information provided during or at the conclusion of a trip that supports performance monitoring and system optimization. Information provided may include a record of the trip including HOV/HOT lane usage and user provided feedback at the conclusion of the trip.
trip plan A travel itinerary covering single or multimodal travel. The itinerary identifies a route and associated traveler information and instructions identifying recommended trip modes (including indoor and outdoor wayfinding) and transfer information, ride sharing options, and transit and parking reservation information. This flow also includes intermediate information that is provided as the trip plan is interactively created, including identification of alternatives, requests for additional information as well as amenities along the trip.
trip request Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include the requestor's location or a request for transit and parking reservations, electric charging station access, and ridesharing options associated with the trip. The trip request also covers requests to revise a previously planned trip and interim updates that are provided as the trip is interactively planned.
user profile Information provided to register for a travel service and create a user account. The provided information includes personal identification, traveler preferences (e.g., travel mode, micro-mobility options, accessibility needs, and assistance needs), priorities for the preferences, device information, a user ID and password, and information to support payment transactions, if applicable.
work zone information Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.

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
G. Promote efficient system management and operation; Improve efficiency
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
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: Vehicle Miles Traveled
Travel Demand Management: Walking/Bicycling
Traveler Information: Customer Satisfaction
Traveler Information: Trip Planning Tools
Work Zone Management: Traveler Information

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).
Annually update bicycle/pedestrian map for accuracy. Number of months since the last update of the bicycle/pedestrian map.
Enhance regional multimodal trip planning tools to X data sources by year Y. The number of data sources providing information for multi-modal trip planning tools.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase customer satisfaction rating of the timeliness, accuracy, and usefulness of traveler information in the region by W, X, and Z percent, respectively, over Y years. Customer satisfaction ratings of timeliness, accuracy, and usefulness of traveler information.
Increase the ease of use of trip planning tools by X percent by year Y. Trip planning tools ease of use rating.
Increase the number of available tools for travelers that incorporate a bicycle/pedestrian component by X percent by year Y. Number of traveler tools with a bicycle/pedestrian component.
Increase the number of travelers commuting via walking and/or bicycling by X percent over Y years. Number of travelers commuting via walking and/or bicycling.
Increase the number of uses of multimodal trip planning tools by X percent by year Y. Number of uses of trip planning tools.
Provide traveler information regarding work zones using variable message signs (VMS), 511, traveler information websites, and/or Web 2.0 technologies for at least X percent of work zones on major arterials, freeways, and transit routes over the next Y years. Percent of work zones on major arterials, freeways, and transit routes for which traveler information is available via variable message signs (VMS), 511, traveler information websites, and/or Web 2.0 technologies.
Provide travelers with information on multimodal alternatives to avoid work zones for at least X percent of work zones on major arterials, freeways, and transit routes over the next Y years. Percent of work zones on major arterials, freeways, and transit routes for which information on multimodal alternatives to avoid work zones is available to travelers.
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.
Reduce vehicle miles traveled per capita by X percent by year Y. Average VMT per capita per day, per week, or per year.


 
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 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers. Electric Charging Management 05 The center shall provide charging station information to traveler information systems.
TIC Data Collection 01 The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
02 The center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information.
03 The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities.
04 The center shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information.
TIC Trip Planning 10 The center shall exchange route segment information with other centers outside the area served by the local center.
16 The center shall match a travelers trip plan with what is available or is projected to be available at the time of the trip, respecting all parameters the traveler provided.
Transit Center Connection Protection 01 The center shall manage service requests for routing of an individual through the transit system.
02 The center shall provide transit plans for both fixed and demand responsive transit to transit passengers.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible. Electric Charging Management 03 The center shall manage reservations and payment of charging services.
Personal Trip Planning and Route Guidance 04 The personal traveler interface shall present personal trip planning information to the traveler in audible or visual forms consistent with a personal device, and suitable for travelers with hearing and vision physical disabilities.
Shared Use Operations 01 The center shall accept requests for shared use transportation.
05 The center shall provide to traveler information the status of the shared use operations.
TIC Dynamic Ridesharing 01 The center shall accept requests from traveler interface systems for ridesharing as part of a trip plan request.
02 The center shall provide a rideshare match based on origin and destination of the traveler's proposed trip, any routing constraints, preferences specified by the traveler, compatibility of this rideshare with rideshares confirmed by other travelers, the requesting traveler's eligibility data, and traffic data.
03 The center shall process rideshare requests by balancing the relative benefits of the rideshare to each rideshare participant.
05 The center shall provide a confirmation of the traveler's rideshare match and provide the capability to support a payment transaction for the rideshare service.
TIC Trip Planning 04 The center shall support on-line route guidance for drivers in vehicles.
05 The center shall support on-line route guidance for specialty vehicles, such as commercial vehicles.
06 The center shall generate route plans based on current and/or predicted conditions of the road network, scheduled maintenance and construction work activities, and work zone activities.
07 The center shall generate route plans based on transit services, including fares, schedules, and requirements for travelers with special needs.
08 The center shall generate route plans based on current asset restrictions, such as height and weight restrictions on tunnels or bridges.
09 The center shall generate route plans based on ferry, rail, air, or other multimodal transportation data.
11 The center shall generate trips based on the use of more than one mode of transport.
14 The center shall provide the capability for center personnel to control route calculation parameters.
Traveler Trip Planning 01 The public interface for travelers shall receive traffic information from a center and present it to the traveler to support trip planning.
02 The public interface for transit shall receive traffic information from a center and present it to the traveler to support trip planning.
03 The public interface for travelers shall receive event information from a center and present it to the traveler to support trip planning.
05 The public interface for travelers shall support traveler trip planning input in audio or manual form.
06 The public interface for travelers shall present trip planning information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities.
07 The public interface for travelers shall store frequently requested trip planning data.
03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler. Light Vehicle Trip Planning and Route Guidance 01 The vehicle shall provide the capability for a driver to request and confirm multi-modal route guidance from a specified source to a destination.
02 The vehicle shall forward the request for route guidance to a traveler information center for route calculation.
03 The vehicle shall forward user preferences, background information, constraints, and payment information to the supplying traveler information center.
04 The vehicle shall present trip information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
Personal Trip Planning and Route Guidance 01 The personal traveler interface shall allow a traveler to request and confirm multi-modal route guidance from a specified source to a destination.
02 The personal traveler interface shall forward the request for route guidance to a traveler information center for route calculation.
03 The personal traveler interface shall forward user preferences, background information, constraints, and payment information to the supplying traveler information center.
12 The personal traveler interface to identify trip planning parameters: Origin, Destination, departure time, arrival time, acceptable modes, so that they might plan for a single coordinated trip using multiple modes using a single action.
TIC Trip Planning 03 The center shall support on-line route guidance for travelers using personal devices (such as PDAs).
12 The center shall use the preferences and constraints specified by the traveler in the trip request to select the most appropriate mode of transport.
13 The center shall provide the capability for the traveler to confirm the proposed trip plan.
Traveler Trip Planning 04 The public interface for travelers shall base requests to support trip planning on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly.
04 Travelers need to be able to set up and update account information that defines payment parameters for their multimodal trips. Personal Trip Planning and Route Guidance 13 The personal traveler interface shall provide the ability for a traveler to set up and modify a user account for payment for multimodal trips.
14 The personal traveler interface shall be able to save regularly used trips.
15 The personal traveler interface shall be able to associate payment methods with saved trips.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler. PAC Payment Administration 01 The center shall manage toll transactions, including maintaining a log of all transactions and toll pricing structure information.
06 The center shall manage a local billing database for toll customers.
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.
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.
21 The center shall provide toll pricing information to other transportation centers.
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.
Personal Trip Planning and Route Guidance 16 The personal traveler interface shall be able to customize the payment mechanism to support a smart card, credit card, and/or payment account.
17 The personal traveler interface shall be able to prioritize between payment methods, including stored payment mechanisms and cash, generally and for saved trips.
18 The personal traveler interface shall be able to reload method(s) for any reloadable payment account, including by ACH transfer, credit card, debit card.
19 The personal traveler interface shall be able to pay for all aspects of their (potentially multi-modal) journey using a single action.
20 The personal traveler interace shall be able to associate their journey with an existing payment account
21 The personal travler interface shall be able to associate their journey with a payment method (e.g., credit or debit card)
06 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from a personal device. Personal Trip Planning and Route Guidance 22 The personal traveler interface shall be able to perform all multi-modal trip planning and payment actions through the traveler's smart device (e.g., phone, wearable).
23 The personal traveler interface shall be able to download proof of payment for all stages of their journey.
07 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from 3rd party provided traveler support equipment Traveler Trip Planning 05 The public interface for travelers shall support traveler trip planning input in audio or manual form.
06 The public interface for travelers shall present trip planning information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities.
08 The traveler support equipment shall provide a mechanism for its user to create/modify a trip plan including selection of mode, route and parking.
10 The public interface for travelers shall provide the capability for the traveler to pay for transportation services that are part of their trip plan.

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
FHWA-JPO-21-860 - Phase 1 Concept of Operations (ConOps) Buffalo NY ITS4US Deployment Project Final 7/14/2021
ISO 17438-1:2016: Intelligent transport systems Indoor navigation for personal and vehicle ITS station Part 1: General information and use case definition Final 1/1/2016
ISO/TR 22085-1:2019: Intelligent transport systems (ITS) - Nomadic device service platform for micro-mobility Final 5/1/2019


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
Alternate Mode Transportation Center Low Moderate Low Class 1
Electric Charging Management Center Moderate Moderate Moderate Class 2
Eligibility Certification Management System Moderate Moderate Moderate Class 2
Light Vehicle OBE Moderate Moderate Moderate Class 2
Maint and Constr Management Center Low High High Class 5
Other Transportation Information Centers Moderate Moderate Moderate Class 2
Parking Management Center Moderate Moderate Moderate Class 2
Payment Administration Center Moderate Moderate Moderate Class 2
Personal Information Device Moderate Moderate Moderate Class 2
Shared Use Transportation Center Moderate Moderate Moderate Class 2
Traffic Management Center High High Moderate Class 4
Transit Management Center Moderate Moderate Moderate Class 2
Transportation Information Center High Moderate High Class 5
Traveler Support Equipment Moderate Moderate Moderate Class 2



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
Alternate Mode Transportation Center Transportation Information Center alternate mode information Low Moderate Low
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Electric Charging Management Center Transportation Information Center electric charging reservation confirmation Moderate Moderate Moderate
May contain PII, or at least a pseudonym that could be associated with an individual or vehicle with enough additional information. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him.
Electric Charging Management Center Transportation Information Center electric charging station information Low Moderate Moderate
Intended for public use, so no reason to obfuscate. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him.
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.
Light Vehicle Driver Light Vehicle OBE light vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Light Vehicle OBE Light Vehicle Driver light vehicle driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Light Vehicle OBE Transportation Information Center trip confirmation Moderate Moderate Moderate
Predictive of traveler location, includes traveler identity as well as payment information. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent or may not receive correct payment information and not properly serve the traveler. This acknowledgement is part of the real-time feedback for car-pooling services. If this doesn't work, the car-pooling service doesn't work.
Light Vehicle OBE Transportation Information Center trip feedback Moderate Moderate Low
Includes PII including traveler identity, which could be used for identity theft or other crimes. If this data is corrupted, the TIC will not receive the feedback the traveler intended, and fail to react appropriately. Unless feedback mechanisms are seen as a high driver of TIC activities, this can safely be marked LOW. Even if such feedback is high priority, occasional drop outs may be tolerable.
Light Vehicle OBE Transportation Information Center trip request Moderate Moderate Low
Predictive of traveler location, includes traveler identity. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent and not properly serve the traveler. This flow initiates an carp-pooling service. If it doesn't work, the car-pooling service doesn't work.
Light Vehicle OBE Transportation Information Center user profile Moderate Moderate Low
Personal preferences and similar information will be associated with a user id of some kind, which should be protected to avoid identity and related thefts. User configuration information needs to be correct the user is subject to third party manipulation or poor quality of service. Probably many opportunities to exchange this data, and will not need to be done often.
Maint and Constr Management Center Transportation Information Center maint and constr work plans Low High High
This data is eventually intended for public dissemination, and is also shared with many centers. If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway).
Maint and Constr Management Center Transportation Information Center roadway maintenance status Low Moderate Moderate
Roadway maintenance status data is distributed to a host of places including travelers, so there is no justification for obfuscation. Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences.
Maint and Constr Management Center Transportation Information Center work zone information Low Moderate Moderate
Eventually intended for public distribution, so no need to obfuscate. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.; DISC: WYO believes this to be HIGH. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.
Other Transportation Information Centers Transportation Information Center alternate mode information Low Moderate Low
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Other Transportation Information Centers Transportation Information Center electric charging information Low Moderate Moderate
Intended for public use, so no reason to obfuscate. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him.
Other Transportation Information Centers Transportation Information Center incident information for public Low Moderate Moderate
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result.
Other Transportation Information Centers Transportation Information Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Other Transportation Information Centers Transportation Information Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Other Transportation Information Centers Transportation Information Center transit service information Low Moderate Low
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is no signficant impact if this flow is not available.
Parking Management Center Transportation Information Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Parking Management Center Transportation Information Center parking reservation confirmation Moderate Moderate Moderate
Might not have direct PII, but may include a pseudonym. If unavailable, corrupted or modified, could lead to the lack of parking assignment, inconveniencing the parking requestor. If unavailable, corrupted or modified, could lead to the lack of parking assignment, inconveniencing the parking requestor.
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 Shared Use Transportation Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Payment Administration Center Transit Management Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Payment Administration Center Transportation Information Center toll data Low Moderate Low
Should be public information, little benefit to obscuring this information. Since actors may use this information to plan their travels, it must be correct. Corruption or manipulation of this data may lead them to make suboptimal decisions, costing time and/or money. This flow probably does not update often. The information within is distributed via many routes.
Payment Administration Center Transportation Information Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Personal Information Device Transportation Information Center trip confirmation Moderate Moderate Moderate
Predictive of traveler location, includes traveler identity as well as payment information. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent or may not receive correct payment information and not properly serve the traveler. This acknowledgement is part of the real-time feedback for car-pooling services. If this doesn't work, the car-pooling service doesn't work.
Personal Information Device Transportation Information Center trip feedback Moderate Moderate Low
Includes PII including traveler identity, which could be used for identity theft or other crimes. If this data is corrupted, the TIC will not receive the feedback the traveler intended, and fail to react appropriately. Unless feedback mechanisms are seen as a high driver of TIC activities, this can safely be marked LOW. Even if such feedback is high priority, occasional drop outs may be tolerable.
Personal Information Device Transportation Information Center trip request Moderate Moderate Moderate
Predictive of traveler location, includes traveler identity. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent and not properly serve the traveler. This flow initiates an carp-pooling service. If it doesn't work, the car-pooling service doesn't work.
Personal Information Device Transportation Information Center user profile Moderate Moderate Low
Personal preferences and similar information will be associated with a user id of some kind, which should be protected to avoid identity and related thefts. User configuration information needs to be correct the user is subject to third party manipulation or poor quality of service. Probably many opportunities to exchange this data, and will not need to be done often.
Personal Information Device Traveler traveler interface updates Not Applicable Moderate Moderate
Personalized data that includes directions and guidance for an individual, but eventually evident anyway. Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Shared Use Transportation Center Payment Administration Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Shared Use Transportation Center Transportation Information Center shared use status Moderate Moderate Moderate
Contains information for a specific traveler. If no specific traveler data is included, this could be LOW. If this is corrupted or modified the initiator may not receive his shared use booking. If this service is not available then the shared use item may not be reserved, lessening its utility and failing to provide the service the (PID) user needs.
TIC Operator Transportation Information Center TIC operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Traffic Management Center Transportation Information Center incident information for public Low Moderate Moderate
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Incident information will be used to make routing and other travel decisions. Corrupted information may have a significant impac t on travel plans and/or road network conditions. Significant numbers of travelers serve as end users for the information in this flow; lack of availability has a significant effect on their travel decisions.
Traffic Management Center Transportation Information Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Transit Management Center Payment Administration Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Transit Management Center Transportation Information Center transit and fare schedules Low Moderate Moderate
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally, though it could be LOW depending on the level of projected updates.
Transit Management Center Transportation Information Center transit schedule adherence information Low Moderate Moderate
Eventually intended for public consumption, so no need to obfuscate. While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.
Transit Management Center Transportation Information Center transit trip plan Moderate Moderate Low
Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. Typically affects individual users, so LOW. If lots of users are using this service, then MODERATE could be justified.
Transportation Information Center Electric Charging Management Center electric charging reservation request Moderate Moderate Moderate
May contain PII, or at least a pseudonym that could be associated with an individual or vehicle with enough additional information. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him.
Transportation Information Center Light Vehicle OBE trip plan Moderate Moderate Moderate
Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. May also incude payment information. The trip plan will affect the user's interaction with the transit system, and notably can include payment information. If any of this is incorrect, the traveler will be adversely affected. If this is hacked, a traveler may be able to use the system for free. This flow is part of a car-pooling service. If it doesn't work, the car-pooling service doesn't work.
Transportation Information Center Other Transportation Information Centers alternate mode information Low Moderate Low
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Transportation Information Center Other Transportation Information Centers electric charging information Low Moderate Moderate
Intended for public use, so no reason to obfuscate. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him. If this data is incorrect or unavailable a vehicle may not be able to charge when and where expected, potentially stranding the traveler or at least inconveniencing him.
Transportation Information Center Other Transportation Information Centers incident information for public Low Moderate Moderate
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result.
Transportation Information Center Other Transportation Information Centers parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is no signficant impact if this flow is not available.
Transportation Information Center Other Transportation Information Centers road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not
Transportation Information Center Other Transportation Information Centers transit service information Low Moderate Low
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is no signficant impact if this flow is not available.
Transportation Information Center Parking Management Center parking reservation request Moderate Moderate Moderate
Might not have direct PII, but may include a pseudonym. If unavailable, corrupted or modified, could lead to the lack of parking assignment, inconveniencing the parking requestor. If unavailable, corrupted or modified, could lead to the lack of parking assignment, inconveniencing the parking requestor.
Transportation Information 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.
Transportation Information Center Payment Administration Center toll data request Moderate Moderate Moderate
Likely includes an identifier linking to a subscription, account or other unique information that belongs to an individual or corporate entity. Compromise of this identifier could be used to cause financial harm to its owner. Since this includes some kind of identifier that is linked to an account or payment mechanism, it must be correct or the resulting charges may fail or be assigned to the wrong account, causing financial harm to someone. Is not part of the real-time on-road charging, but will be frequently used and impact a large number of users if not available.
Transportation Information Center Payment Administration Center trip access coordination Moderate Moderate Moderate
Content must be protected so the the unique token may not be used by another party, which would deprive the paying traveler from access to the resource they paid for and expect to use. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for. This data must be provided in timely and correct fashion so the traveler can gain access to the transport resource they paid for.
Transportation Information Center Personal Information Device trip plan Moderate Moderate Moderate
Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. May also incude payment information. The trip plan will affect the user's interaction with the transit system, and notably can include payment information. If any of this is incorrect, the traveler will be adversely affected. If this is hacked, a traveler may be able to use the system for free. This flow is part of a car-pooling service. If it doesn't work, the car-pooling service doesn't work.
Transportation Information Center TIC Operator TIC operations information presentation Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transportation Information Center Traffic Management Center logged vehicle routes High Moderate Moderate
These are planned routes that could include predictive information of where a high value target will be at a particular time. A attacker with hostile intent could use this as the basis for an attack. Since this will be used to modify traffic control to support special vehicle movements, and change to or incorrect reception of this data will reduce the effectiveness of those changes to some degree, and could have a substantial negative affect. Consequently, a MODERATE level of integrity checking and consistent availability is justified. Since this will be used to modify traffic control to support special vehicle movements, and change to or incorrect reception of this data will reduce the effectiveness of those changes to some degree, and could have a substantial negative affect. Consequently, a MODERATE level of integrity checking and consistent availability is justified.
Transportation Information Center Transit Management Center transit trip request Moderate Moderate Low
Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. Typically affects individual users, so LOW. If lots of users are using this service, then MODERATE could be justified.
Transportation Information Center Transit Management Center trip confirmation Moderate Moderate Moderate
Predictive of traveler location, includes traveler identity as well as payment information. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent or may not receive correct payment information and not properly serve the traveler. This acknowledgement is part of the real-time feedback for car-pooling services. If this doesn't work, the car-pooling service doesn't work.
Transportation Information Center Traveler Support Equipment trip plan Moderate Moderate Moderate
Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. May also incude payment information. The trip plan will affect the user's interaction with the transit system, and notably can include payment information. If any of this is incorrect, the traveler will be adversely affected. If this is hacked, a traveler may be able to use the system for free. This flow is part of a car-pooling service. If it doesn't work, the car-pooling service doesn't work.
Traveler Personal Information Device traveler input Not Applicable Moderate Low
This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Traveler Traveler Support Equipment traveler input Not Applicable Moderate Low
Publicly available information, while not directly observable, is intended for widespread distribution While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Traveler Support Equipment Transportation Information Center trip confirmation Moderate Moderate Moderate
Predictive of traveler location, includes traveler identity as well as payment information. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent or may not receive correct payment information and not properly serve the traveler. This acknowledgement is part of the real-time feedback for car-pooling services. If this doesn't work, the car-pooling service doesn't work.
Traveler Support Equipment Transportation Information Center trip request Moderate Moderate Low
Predictive of traveler location, includes traveler identity. A third party with hostile intent toward the traveler could use this information against the traveler. If this data is corrupted, the TIC may not understand the traveler's intent and not properly serve the traveler. This flow initiates an carp-pooling service. If it doesn't work, the car-pooling service doesn't work.
Traveler Support Equipment Traveler traveler interface updates Not Applicable Moderate Moderate
Publicly available information, while not directly observable, is intended for widespread distribution Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.

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 Payment Administration Center




System Requirements

System Requirement Need
001 The system shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
002 The system shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
003 The system shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
004 The system shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
005 The system shall support on-line route guidance for travelers using personal devices (such as PDAs). 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
006 The system shall support on-line route guidance for drivers in vehicles. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
007 The system shall support on-line route guidance for specialty vehicles, such as commercial vehicles. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
008 The system shall generate route plans based on current and/or predicted conditions of the road network, scheduled maintenance and construction work activities, and work zone activities. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
009 The system shall generate route plans based on transit services, including fares, schedules, and requirements for travelers with special needs. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
010 The system shall generate route plans based on current asset restrictions, such as height and weight restrictions on tunnels or bridges. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
011 The system shall generate route plans based on ferry, rail, air, or other multimodal transportation data. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
012 The system shall exchange route segment information with other centers outside the area served by the local center. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
013 The system shall generate trips based on the use of more than one mode of transport. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
014 The system shall use the preferences and constraints specified by the traveler in the trip request to select the most appropriate mode of transport. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
015 The system shall provide the capability for the traveler to confirm the proposed trip plan. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
016 The system shall provide the capability for center personnel to control route calculation parameters. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
017 The system shall manage service requests for routing of an individual through the transit system. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
018 The system shall provide transit plans for both fixed and demand responsive transit to transit passengers. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
019 The system shall receive traffic information from a center and present it to the traveler to support trip planning. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
020 The system shall receive event information from a center and present it to the traveler to support trip planning. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
021 The system shall base requests to support trip planning on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
022 The system shall support traveler trip planning input in audio or manual form. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
07 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from 3rd party provided traveler support equipment
023 The system shall present trip planning information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
07 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from 3rd party provided traveler support equipment
024 The system shall store frequently requested to support trip planning data. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
025 The system shall allow a traveler to request and confirm multi-modal route guidance from a specified source to a destination. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
026 The system shall forward the request for route guidance to a traveler information center for route calculation. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
027 The system shall forward user preferences, background information, constraints, and payment information to the supplying traveler information center. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
028 The system shall present personal trip planning information to the traveler in audible or visual forms consistent with a personal device, and suitable for travelers with hearing and vision physical disabilities. 02 Travelers need a complete trip plan from their origin to their destination that is timely, accurate, and reliable in order for them to arrive safely in as little time as possible.
029 The system shall provide the capability for a driver to request and confirm multi-modal route guidance from a specified source to a destination. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
030 The system shall present trip information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
032 The system shall match a travelers trip plan with what is available or is projected to be available at the time of the trip, respecting all parameters the traveler provided. 01 Traveler Information needs access to timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to generate accurate and appropriate routes for travelers.
041 The system shall provide the capability for the traveler to pay for transportation services that are part of their trip plan. 07 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from 3rd party provided traveler support equipment
046 The system shall identify trip planning parameters (origin, destination, departure time, arrival time, acceptable modes) to support planning for a single coordinated trip using multiple modes, using a single action. 03 Traveler Information needs travel parameters from a traveler in order to develop a complete mulitmodal trip plan for the traveler.
047 The system shall provide the ability for a traveler to set up and modify a user account for payment for multimodal trips. 04 Travelers need to be able to set up and update account information that defines payment parameters for their multimodal trips.
048 The system shall be able to save regularly used trips. 04 Travelers need to be able to set up and update account information that defines payment parameters for their multimodal trips.
049 The system shall be able to associate payment methods with saved trips. 04 Travelers need to be able to set up and update account information that defines payment parameters for their multimodal trips.
050 The system shall be able to customize the payment mechanism to support a smart card, credit card, and/or payment account. 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
051 The system shall be able to prioritize between payment methods, including stored payment mechanisms and cash, generally and for saved trips. 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
052 The system shall be able to reload method(s) for any reloadable payment account, including by ACH transfer, credit card, debit card. 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
053 The system shall be able to pay for all aspects of their (potentially multi-modal) journey using a single action. 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
054 The system shall be able to associate their journey with an existing payment account 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
055 The system shall be able to associate their journey with a payment method (e.g., credit or debit card) 05 Traveler Information needs payment information from a traveler in order to develop reservations for a complete mulitmodal trip plan for the traveler.
056 The system shall be able to perform all multi-modal trip planning and payment actions through the traveler's smart device (e.g., phone, wearable). 06 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from a personal device.
057 The system shall be able to download proof of payment for all stages of their journey. 06 The Traveler needs to be able to perform all multi-modal trip planning and payment actions from a personal device.