< < TI05 : TI06 : TI07 > >

TI06: Shared Use Mobility and Dynamic Ridesharing

This service package addresses the range of shared use mobility options that support a complete trip for travelers. This service supports planning, reservations, and on-trip guidance for these operations. The complete trip may be arranged and undertaken using an internet connected personal device. The service package includes temporary use of a vehicle or micromobility vehicle by the traveler as well as having a vehicle pick up the traveler at a specific location and take them to another location.

This service package also addresses dynamic ridesharing/ride matching services to travelers. Dynamic ridesharing allows travelers to arrange carpool trips through a personal device with a wireless connection to a ride matching system (e.g., a web-based application). It uses inputs from both passengers and drivers pre-trip, during the trip, and post-trip . These inputs are then translated into "optimal" pairings between passengers and drivers to provide both with a convenient route between their two origin and destination locations. After the trip, information is provided back to the service package to improve the user's experience for future trips.

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
Financial Center Maintainer Financial Center Maintains
Financial Center Manager Financial Center Manages
Financial Center Owner Financial Center Maintainer System Maintenance Agreement
Financial Center Owner Financial Center Manager Operations Agreement
Financial Center Owner TIC Operator Application Usage Agreement
Financial Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Transportation Information Center Owner Information Exchange Agreement
Financial Center Owner Transportation Information Center User Service Usage Agreement
Financial Center Supplier Financial Center 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
Micromobility Vehicle OBE Maintainer Micromobility Vehicle OBE Maintains
Micromobility Vehicle OBE Manager Micromobility Vehicle OBE Manages
Micromobility Vehicle OBE Owner Micromobility Vehicle OBE Maintainer System Maintenance Agreement
Micromobility Vehicle OBE Owner Micromobility Vehicle OBE Manager Operations Agreement
Micromobility Vehicle OBE Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Micromobility Vehicle OBE Owner Personal Information Device Owner Expectation of Data Provision
Micromobility Vehicle OBE Owner Personal Information Device User Service Usage Agreement
Micromobility Vehicle OBE Owner Shared Use Transportation Center Maintainer Maintenance Data Exchange Agreement
Micromobility Vehicle OBE Owner Shared Use Transportation Center Owner Expectation of Data Provision
Micromobility Vehicle OBE Owner Shared Use Transportation Center User Service Usage Agreement
Micromobility Vehicle OBE Owner SUTC Operator Application Usage Agreement
Micromobility Vehicle OBE Owner SUTC Operator Vehicle Operating Agreement
Micromobility Vehicle OBE Owner Traveler Application Usage Agreement
Micromobility Vehicle OBE Owner Traveler Vehicle Operating Agreement
Micromobility Vehicle OBE Supplier Micromobility Vehicle OBE Owner Warranty
Payment Device Maintainer Payment Device Maintains
Payment Device Manager Payment Device Manages
Payment Device Manager Traveler System Usage Agreement
Payment Device Owner Payment Device Maintainer System Maintenance Agreement
Payment Device Owner Payment Device Manager Operations Agreement
Payment Device Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Personal Information Device Owner Information Provision and Action Agreement
Payment Device Owner Personal Information Device User Service Usage Agreement
Payment Device Owner Traveler Application Usage Agreement
Payment Device Owner Traveler Support Equipment Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Traveler Support Equipment Owner Information Provision and Action Agreement
Payment Device Owner Traveler Support Equipment User Service Usage Agreement
Payment Device Supplier Payment Device Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Manager Traveler System Usage Agreement
Personal Information Device Owner Light Vehicle Driver Application Usage Agreement
Personal Information Device Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Light Vehicle OBE Owner Information Provision and Action Agreement
Personal Information Device Owner Light Vehicle OBE User Service Usage Agreement
Personal Information Device Owner Payment Device Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Payment Device Owner Information Provision and Action Agreement
Personal Information Device Owner Payment Device User Service Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Owner Shared Use Transportation Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Shared Use Transportation Center Owner Information Provision and Action Agreement
Personal Information Device Owner Shared Use Transportation Center User Service Usage Agreement
Personal Information Device Owner SUTC Operator Application Usage 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 Owner Traveler Application 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 Manager SUTC Operator System Usage Agreement
Shared Use Transportation Center Owner Light Vehicle Driver Application Usage Agreement
Shared Use Transportation Center Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Light Vehicle OBE Owner Information Provision Agreement
Shared Use Transportation Center Owner Light Vehicle OBE User Service Usage Agreement
Shared Use Transportation Center Owner Micromobility Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Micromobility Vehicle OBE Owner Information Provision Agreement
Shared Use Transportation Center Owner Micromobility Vehicle OBE User Service Usage Agreement
Shared Use Transportation Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Personal Information Device Owner Information Provision Agreement
Shared Use Transportation Center Owner Personal Information Device 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 Transit Management Center Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Transit Management Center Owner Information Provision Agreement
Shared Use Transportation Center Owner Transit Management Center User Service 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 Owner Traveler Application Usage Agreement
Shared Use Transportation Center Owner Traveler Support Equipment Maintainer Maintenance Data Exchange Agreement
Shared Use Transportation Center Owner Traveler Support Equipment Owner Information Provision Agreement
Shared Use Transportation Center Owner Traveler Support Equipment User Service Usage Agreement
Shared Use Transportation Center Supplier Shared Use Transportation Center Owner Warranty
SUTC Operator Shared Use Transportation Center Operates
TIC Operator Transportation Information Center Operates
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
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 Financial Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Financial Center Owner Information Exchange Agreement
Transportation Information Center Owner Financial 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 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 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 Payment Device Operates
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 Payment Device Maintainer Maintenance Data Exchange Agreement
Traveler Support Equipment Owner Payment Device Owner Information Exchange and Action Agreement
Traveler Support Equipment Owner Payment Device User Service Usage Agreement
Traveler Support Equipment Owner Shared Use Transportation Center Maintainer Maintenance Data Exchange Agreement
Traveler Support Equipment Owner Shared Use Transportation Center Owner Information Exchange and Action Agreement
Traveler Support Equipment Owner Shared Use Transportation Center User Service Usage Agreement
Traveler Support Equipment Owner SUTC Operator Application Usage Agreement
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 Application 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
Light Vehicle OBE Light Vehicle Access 6.7.5.4 Manage Light Vehicle Access
Light Vehicle Trip Planning and Route Guidance 6.7.1.1.1 Determine In-Vehicle Guidance Method
6.7.1.1.2 Provide Dynamic In-Vehicle Guidance
6.7.1.1.3 Provide Autonomous In-Vehicle Guidance
6.7.1.2 Provide Driver Guidance Interface
6.7.5.1 Get Light Vehicle Driver Personal Request
6.7.5.2 Provide Light Vehicle Driver with Personal Travel Information
Micromobility Vehicle OBE MMV Access 3.7.2 Manage MMV Access
3.7.3 Provide MMV User Safety Interface
Personal Information Device Personal Shared Use Planning 6.8.3.8 Provide Shared Use Traveler Interface
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.1.3 Provide Personal Portable Device Autonomous Guidance
6.8.1.2 Provide Personal Portable Device Guidance Interface
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
Shared Use Transportation Center Shared Use Account and Fee Management 7.4.1.8 Manage Shared Use Payments
Shared Use Operations 6.4.8 Manage Shared Use Vehicle Access
7.4.1.8 Manage Shared Use Payments
Transit Management Center Transit Center Paratransit Operations 4.1.4 Collect and Process Transit Vehicle Data
4.1.6.1 Process Demand Responsive Transit Trip Request
4.1.6.2 Compute Demand Responsive Transit Vehicle Availability
4.1.6.3 Generate Demand Responsive Transit Schedule and Routes
4.1.6.4 Confirm Demand Responsive Transit Schedule and Route
4.1.8 Manage Individual Service Requests
4.2.1.3 Produce Transit Service Data for External Use
4.5.1 Assess Transit Vehicle Operator Performance
4.5.2 Assess Transit Vehicle Operator Availability
4.5.3 Access Transit Vehicle Operator Cost Effectiveness
4.5.4 Assess Transit Vehicle Operator Eligibility
4.5.5 Generate Transit Vehicle Operator Route Assignments
4.5.6 Report Transit Vehicle Operator Information
4.5.7 Provide Transit Vehicle Operator Information Store Interface
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.2.4 Distribute Advanced Tolls 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

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Part 1 Part 2
PNG Diagrams: Part 1 Part 2


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Financial Center Center The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object.
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.
Micromobility Vehicle OBE Vehicle The Micromobility Vehicle On-Board Equipment (MMV OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The MMV OBE includes general capabilities that apply to bicycles and other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles. The MMV OBE includes the common interfaces and functions that could apply to any low-powered mobility device. The radio(s) supporting V2V and V2I communications are a key component of the MMV OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, and enhanced traveler interfaces (through PIDs), complement traveler information services so that, in addition to making informed mode and route selections, the vulnerable road user travels these routes in a safer and more consistent manner.
Payment Device Personal The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Shared Use Transportation Center Center The 'Shared Use Transportation Center' manages shared use vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the shared use fleet. It spans contract-driven and centralized dispatch vehicle services such as taxis and ride-hail services, first/last mile automated vehicles as well as personal mobility fleets such as shared-use cars, bicycles, and scooters.
SUTC Operator Center This 'SUTC Operator' represents the person or people that monitor and manage shared mobility services provided by the Shared Use Transportation Center.
TIC Operator Center This 'TIC Operator' represents the person or people that monitor and manage traveler information services provided by the Transportation Information Center.
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
Light Vehicle Access 'Light Vehicle Access' provides access to a shared use vehicle either remotely from a center or locally with a traveler device. Light Vehicle OBE
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
MMV Access 'MMV Access' provides access to a micromobility vehicle remotely from a center. It also provides the location of the vehicle to the center as well as its identification information to a local traveler device. Micromobility Vehicle OBE
Personal Shared Use Planning 'Personal Shared Use Planning' provides a personalized connection to arrange person trips that include some kind of shared mobility (e.g., car-sharing, bike-sharing). The shared use plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. 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
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 Account and Fee Management 'Shared Use Account and Fee Management' manages user accounts and payments at the Shared Use Transportation Center. It provides the back office functions that support payment reconciliation with links to financial institutions. Shared Use Transportation Center
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 Paratransit Operations 'Transit Center Paratransit Operations' manages demand responsive transit services, including paratransit services. It supports planning and scheduling of these services, allowing paratransit and other demand response transit services to plan efficient routes and better estimate arrival times. It also supports automated dispatch of paratransit vehicles and tracks passenger pick-ups and drop-offs. Customer service operator systems are updated with the most current schedule information. 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
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction.
demand responsive transit plan Plan regarding overall demand responsive transit schedules and deployment.
demand responsive transit request Request for paratransit support.
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.
MMV access enable Information used to enable access to a shared use MMV.
MMV identification MMV identification (e.g., a QR code) used to access an MMV.
MMV location The current location (latitude, longitude, and elevation) reported by an MMV OBE.
payment device update Information updated concerning traveler's personal data including name, address, user account information, trip records, and profile data.
payment methods financial institution A list of valid payment methods accepted by a financial center.
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry)
request for payment Request to deduct cost of service from user's payment account.
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges.
shared use confirmation Confirmation that traveler is going to use the shared use asset now or at a future time.
shared use request Request for shared use asset (e.g., car or bicycle) now or as a reservation for future use.
shared use response Response from shared use provider regarding availability of the shared use asset now or in the future. Includes any payment requirements.
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.
shared vehicle access enable Information used to enable access to a shared use vehicle.
shared vehicle access request Request for access to a shared use vehicle.
shared vehicle information Detailed information about the vehicle the traveler is going to use as part of a shared use mode. The information could include locations details (e.g. parking space or docking number), as well as details about the vehicle (e.g. model, color, or license plate number), including its current vehicle location and ETA.
SUTC operations information presentation Presentation of information to the SUTC Operator including current operational status of the back office system, the shared mobility assets in the field, current user/client information, and past, current, and future shared use activities.
SUTC operator input User input from the SUTC system operator including requests to monitor current system operation and inputs to affect system operation including operating parameters, asset status, and client status.
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.
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 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 account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.
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.

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

Associated Objective Categories

Objective Category
Special Event Management: Mode Shift from SOV
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Duration of Congestion
System Efficiency: Energy Consumption
System Efficiency: Extent of Congestion
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time
System Efficiency: Vehicle Miles Traveled
System Options: Mode Share
Travel Demand Management: Carpool/Vanpool

Associated Objectives and Performance Measures

Objective Performance Measure
Achieve X percent alternative (non-SOV) mode share in transit station communities (or other destinations) by year Y. Percent of all trips made using alternative modes in transit station communities.
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).
Create and share regional carpool/vanpool database with Z number of employers per year. Number of employers with access to regional carpool/vanpool database.
Decrease the percent of special event attendees traveling to the event in single-occupancy vehicles by X percent in Y years. Percent of special event attendees using single-occupancy vehicles each year for selected events.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase alternative (non-SOV) mode share for all trips by X percent within the next Y years. Share of trips by each mode of travel.
Increase the number of carpools by X percent over the next Y years. Share of household trips by each mode of travel.
Increase the percent of special event attendees using park & ride lots by X percent in Y years. Percent of special event attendees utilizing park & ride lots each year for selected events.
Increase the percent of special events with dedicated shuttle service by X percent in Y years. Percent of special events with dedicated shuttle service for selected events during a 1-year period.
Increase use of vanpools by X percent over the next Y years. Share of household trips by each mode of travel.
Maintain the rate of growth in facility miles experiencing recurring congestion as less than the population growth rate (or employment growth rate). Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Provide carpool/vanpool matching and ridesharing information services by year Y. Availability of carpool/vanpool matching and ridesharing information services.
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 SOV vehicle trips by X percent through travel demand management strategies (e.g., employer or residential rideshare) by year Y. Share of employees walking, biking, telecommuting, carpooling/vanpooling, riding transit, driving alone.
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 daily hours of recurring congestion on major freeways from X to Y by year Z. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the number of hours per day that the top 20 most congested roadways experience recurring congestion by X percent by year Y. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the percentage of facility miles (highway, arterial, rail, etc.) experiencing recurring congestion during the peak period by X percent by year Y. Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
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 trips per year in region by X percent through carpools/vanpools. Number of person trips by carpool/vanpool in region.
Reduce trips per year in region by X percent through carpools/vanpools. Number of trips in region.
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 transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points. TIC Data Collection 18 The center shall collect information concerning members of the population that may require additional assistance in the event of an evacuation, including the names of household members, address, special needs, and any care giver information (nurse or hospice service that may want to keep track of their patient's status).
TIC Dynamic Ridesharing 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.
TIC Trip Planning 01 The center shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points.
02 The center shall include bicycle routes, walkways, skyways, and multi-use trails in the pre-trip and en route directions it provides to travelers.
Transit Center Paratransit Operations 01 The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests may include traveler information service providers.
06 The center shall disseminate up-to-date schedules and route information to other centers for demand responsive transit services (paratransit).
Traveler 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.
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.
02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces. Light Vehicle Trip Planning and Route Guidance 07 The vehicle shall allow a traveler to request and confirm a ridesharing trip from a specified source to a destination.
Personal Trip Planning and Route Guidance 03 The personal traveler interface shall forward user preferences, background information, constraints, and payment information to the supplying traveler information center.
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.
28 The personal traveler interface shall allow a traveler to request and confirm a ridesharing trip from a specified source to a destination.
TIC Dynamic Ridesharing 01 The center shall accept requests from traveler interface systems for ridesharing as part of a trip plan request.
03 The center shall process rideshare requests by balancing the relative benefits of the rideshare to each rideshare participant.
04 The center shall arrange connections to transit or other multimodal services for portions of a multi-segment trip that includes ridesharing.
Transit Center Paratransit Operations 03 The center shall generate demand response transit (including paratransit) routes and schedules based on such factors as parameters input by the system operator, what other demand responsive transit schedules have been planned, the availability and location of vehicles, the relevance of any fixed transit routes and schedules, road network information, and incident information.
Traveler 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.
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.
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 to match riding commuters to drivers. TIC Dynamic Ridesharing 06 The center shall store all rideshare matches and traveler eligibility data.
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.
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.
04 Traveler information needs to provide a mechanism for the confirmation of ride matching. Light Vehicle Trip Planning and Route Guidance 07 The vehicle shall allow a traveler to request and confirm a ridesharing trip from a specified source to a destination.
Personal Trip Planning and Route Guidance 28 The personal traveler interface shall allow a traveler to request and confirm a ridesharing trip from a specified source to a destination.
TIC Dynamic Ridesharing 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.
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.
05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations Personal Shared Use Planning 01 The personal traveler device shall allow the traveler to make a request for a shared use transportation.
02 The personal traveler device shall allow the traveler to confirm a shared use transportation trip.
06 The personal traveler interface shall provide an interface through which travel information requests and traveler information may be input by the traveler.
09 The personal traveler interface shall present shared user traveler information to the traveler upon request.
Shared Use Operations 01 The center shall accept requests for shared use transportation.
06 Travelers need to be able to receive accurate, timely, and reliable information regarding shared use options that support their overall trip plan. Personal Shared Use Planning 03 The personal device shall receive an accurate, timely, and reliable information regarding shared use options that support their overall trip plan.
Shared Use Operations 02 The center shall provide the traveler with a shared use transportation option.
07 Travelers need to receive the location of a shared vehicle they have arranged to use. Personal Shared Use Planning 10 The personal device shall receive the location of a shared use vehicle which the traveler has reserved.
Shared Use Operations 03 The center shall provide to the traveler the location of a shared use vehicle which the traveler has reserved.
08 Travelers need to be able to gain access the shared vehicle they have arranged to use. Light Vehicle Access 01 The vehicle shall allow access based on an input from the traveler device.
02 The vehicle shall allow access based on an input from a center.
MMV Access 01 The micromobility vehicle shall communicate with the traveler device to allow access to the micromobility vehicle.
02 The micromobility vehicle shall allow access based on an input from a center.
Personal Shared Use Planning 11 The personal device shall be able to send an access request to a shared use vehicle to allow the traveler access to the vehicle.
Shared Use Operations 04 The center shall be able to send an access command to a shared use vehicle to allow the traveler to gain access of the vehicle.
10 Travelers need to be able to set up and update user accounts for shared use transportation systems. Personal Shared Use Planning 04 The personal device shall provide updates to the traveler's account as directed by the traveler.
05 The personal device shall provide traveler-specific information sufficient to establish an account for the traveler's use of shared services.
Shared Use Account and Fee Management 01 The center shall accept traveler-specific information sufficient to establish an account for the traveler's use of shared services from the traveler's personal device.
02 The center shall accept updates to the traveler's account as directed by the traveler's personal device.
11 Shared Use Transportation needs to provide shared use operations status to other centers. Shared Use Operations 05 The center shall provide to traveler information the status of the shared use operations.
06 The center shall provide to public transportation the status of the shared use operations.

Related Sources

Document Name Version Publication Date
Report on Functional Requirements and Software Architecture for the IDTO Prototype Phase I Demonstration Site (Columbus) Final 8/30/2013
ITS User Services Document 1/1/2005
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
Integrated Dynamic Transit Operations (IDTO) ConOps Draft v3.0 5/11/2012
Report on Functional and Performance Requirements and High-Level Data and Communication Needs for Integrated Dynamic Transit Operations (IDTO) Final 8/13/2012


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
Financial Center Moderate Moderate Moderate Class 2
Light Vehicle OBE High High Moderate Class 4
Micromobility Vehicle OBE Moderate Moderate Moderate Class 2
Payment Device Moderate Moderate High Class 5
Personal Information Device High High High Class 5
Shared Use Transportation Center High High Moderate Class 4
Transit Management Center Moderate Moderate Moderate Class 2
Transportation Information Center High High Moderate Class 4
Traveler Support Equipment Moderate Moderate High Class 5



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

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Financial Center Transportation Information Center payment methods financial institution Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Financial Center Transportation Information Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
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 account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
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.
Micromobility Vehicle OBE Personal Information Device MMV identification Not Applicable Moderate Moderate
The ID of the vehicle is required for typical shared use use cases, and must be directly accessible. Since this information is required to gain access to the vehicle, it must be timely, correct and authentic to ensure traveler access when they expect it. Since this information is required to gain access to the vehicle, it must be timely, correct and authentic to ensure traveler access when they expect it.
Micromobility Vehicle OBE Shared Use Transportation Center MMV location Moderate Moderate Moderate
As this might indicate the location of a traveler, should be obfuscated for personal privacy purposes. Since this information is required to gain access to the vehicle, it must be timely, correct and authentic to ensure traveler access when they expect it. Since this information is required to gain access to the vehicle, it must be timely, correct and authentic to ensure traveler access when they expect it.
Payment Device Personal Information Device actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Payment Device Traveler Support Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Light Vehicle OBE shared vehicle access enable Moderate Moderate Moderate
Since this allows access to a vehicle, it should be obfuscated so that unentitled parties cannot spoof the enablement and gain access to the vehicle. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access.
Personal Information Device Payment Device payment device update Moderate Moderate High
Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Payment Device request for payment Moderate Moderate High
Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Shared Use Transportation Center shared use confirmation Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
Personal Information Device Shared Use Transportation Center shared use request Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
Personal Information Device Shared Use Transportation Center shared vehicle access request Moderate Moderate Moderate
Will include an identifier and while it might not be PII, will be related to vehicle access and so should be obfuscated to prevent abuse. Since this is related to gaining access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access. Since this is related to gaining access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access.
Personal Information Device Shared Use Transportation Center user account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Personal Information Device Shared Use Transportation 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 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 account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
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 Light Vehicle OBE shared vehicle access enable Moderate Moderate Moderate
Since this allows access to a vehicle, it should be obfuscated so that unentitled parties cannot spoof the enablement and gain access to the vehicle. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access.
Shared Use Transportation Center Micromobility Vehicle OBE MMV access enable Moderate Moderate Moderate
Since this allows access to a vehicle, it should be obfuscated so that unentitled parties cannot spoof the enablement and gain access to the vehicle. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access. Since this allows access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access.
Shared Use Transportation Center Personal Information Device shared use response Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
Shared Use Transportation Center Personal Information Device shared vehicle information Moderate Moderate Moderate
Might not include PII, but will provide information related to vehicle access and possible travel plans, so should be obfuscated to prevent abuse. Since this is related to gaining access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access. Since this is related to gaining access to a vehicle, it must be correct, timely and unmanipulated so that a traveler gets access when they expect to get access.
Shared Use Transportation Center SUTC Operator SUTC 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.
Shared Use Transportation Center Transit Management 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.
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.
Shared Use Transportation Center Traveler Support Equipment shared use response Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
SUTC Operator Shared Use Transportation Center SUTC 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.
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.
Transit Management Center Transportation Information Center demand responsive transit plan Moderate Moderate Moderate
Individual-focused flow, containing the identity of an individual traveler which must be kept confidential. Likely a single individual, which is why MODERATE and not HIGH. Eventually destinated for the traveler requesting service, so needs to be correct and unaltered. Since it contains information the traveler will use to make decisions, needs to be correct. Likely only affects a single individual however, so MODERATE and not HIGH. Needs to arrive to complete an action related to provision of paratransit services to an individual. Not HIGH because focused on a single invdividual.
Transportation Information Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
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 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 Transit Management Center demand responsive transit request Moderate Moderate Moderate
Contains PII of the requestor, and predictive of the requestor's future behavior. This information could be used by an attacker to harm the requestor through a variety of means. Needs to be correct and or the requestor's need will not be serviced. Needs to be correct and or the requestor's need will not be serviced.
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 Payment Device payment device update Moderate Moderate High
Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Traveler Support Equipment Payment Device request for payment Moderate Moderate High
Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Traveler Support Equipment Shared Use Transportation Center shared use confirmation Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
Traveler Support Equipment Shared Use Transportation Center shared use request Moderate Moderate Moderate
Will include some kind of identifier to manage the reservation, which is linked ot an individual and thus related to PII. 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 won't be reserved, lessening its utility and failing to provide the service the PID user needs.
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

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.





System Requirements

System Requirement Need
001 The system shall collect information concerning members of the population that may require additional assistance in the event of an evacuation, including the names of household members, address, special needs, and any care giver information (nurse or hospice service that may want to keep track of their patient's status). 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
002 The system shall accept requests from traveler interface systems for ridesharing as part of a trip plan request. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
003 The system 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. 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
004 The system shall provide to public transportation the status of the shared use operations. 11 Shared Use Transportation needs to provide shared use operations status to other centers.
005 The system shall process rideshare requests by balancing the relative benefits of the rideshare to each rideshare participant. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
006 The system shall provide to traveler information the status of the shared use operations. 11 Shared Use Transportation needs to provide shared use operations status to other centers.
007 The system shall arrange connections to transit or other multimodal services for portions of a multi-segment trip that includes ridesharing. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
008 The system shall provide a confirmation of the traveler's rideshare match and provide the capability to support a payment transaction for the rideshare service. 04 Traveler information needs to provide a mechanism for the confirmation of ride matching.
009 The system shall store all rideshare matches and traveler eligibility data. 03 Traveler Information needs to match riding commuters to drivers.
010 The system shall provide to the traveler the location of a shared use vehicle which the traveler has reserved. 07 Travelers need to receive the location of a shared vehicle they have arranged to use.
011 The system shall be able to send an access command to a shared use vehicle to allow the traveler to gain access of the vehicle. 08 Travelers need to be able to gain access the shared vehicle they have arranged to use.
012 The system shall accept requests for shared use transportation. 05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations
013 The system shall acquire information from the financial institution describing payment methods the institution is willing to accept. 11 Shared Use Transportation needs to provide shared use operations status to other centers.
014 The system shall provide the traveler with a shared use transportation option. 06 Travelers need to be able to receive accurate, timely, and reliable information regarding shared use options that support their overall trip plan.
015 The system shall accept updates to the traveler's account as directed by the traveler's personal device. 10 Travelers need to be able to set up and update user accounts for shared use transportation systems.
017 The system shall accept traveler-specific information sufficient to establish an account for the traveler's use of shared services from the traveler's personal device. 10 Travelers need to be able to set up and update user accounts for shared use transportation systems.
018 The system shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points. 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
019 The system shall include bicycle routes, walkways, skyways, and multi-use trails in the pre-trip and en route directions it provides to travelers. 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
020 The system shall request payment through the financial institution for shared use services when such services are requested by the traveler. 11 Shared Use Transportation needs to provide shared use operations status to other centers.
021 The system shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests may include traveler information service providers. 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
022 The system shall generate demand response transit (including paratransit) routes and schedules based on such factors as parameters input by the system operator, what other demand responsive transit schedules have been planned, the availability and location of vehicles, the relevance of any fixed transit routes and schedules, road network information, and incident information. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
023 The system shall disseminate up-to-date schedules and route information to other centers for demand responsive transit services (paratransit). 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
024 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. 01 Traveler Information needs access to timely, accurate, and reliable transit and multimodal operations data, including available parking, in order to support ride matching by locating and managing meeting and drop-off points.
02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
03 Traveler Information needs to match riding commuters to drivers.
025 The system shall support traveler trip planning input in audio or manual form. 04 Traveler information needs to provide a mechanism for the confirmation of ride matching.
026 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. 04 Traveler information needs to provide a mechanism for the confirmation of ride matching.
03 Traveler Information needs to match riding commuters to drivers.
02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
027 The system shall store frequently requested to support trip planning data. 03 Traveler Information needs to match riding commuters to drivers.
02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
028 The system shall allow the traveler to make a request for a shared use transportation. 05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations
029 The system shall allow the traveler to confirm a shared use transportation trip. 05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations
034 The system shall forward user preferences, background information, constraints, and payment information to the supplying traveler information center. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
035 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 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
036 The system shall provide an interface through which travel information requests and traveler information may be input by the traveler. 05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations
037 The system shall provide a mechanism for its user to create/modify a trip plan including selection of mode, route and parking. 04 Traveler information needs to provide a mechanism for the confirmation of ride matching.
038 The system shall receive the location of a shared use vehicle which the traveler has reserved. 07 Travelers need to receive the location of a shared vehicle they have arranged to use.
039 The system shall request that the traveler card deduct the costs of travel service from the traveler's account. 06 Travelers need to be able to receive accurate, timely, and reliable information regarding shared use options that support their overall trip plan.
041 The system shall be able to send an access request to a shared use vehicle to allow the traveler access to the vehicle. 08 Travelers need to be able to gain access the shared vehicle they have arranged to use.
042 The system shall provide traveler-specific information sufficient to establish an account for the traveler's use of shared services. 10 Travelers need to be able to set up and update user accounts for shared use transportation systems.
044 The system shall allow a traveler to request and confirm a ridesharing trip from a specified source to a destination. 02 Traveler Information needs to accept commuter and driver information for ridesharing, including preferences, payment options, origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.
04 Traveler information needs to provide a mechanism for the confirmation of ride matching.
045 The system shall allow access based on an input from the traveler device. 08 Travelers need to be able to gain access the shared vehicle they have arranged to use.
046 The system shall allow access based on an input from a center. 08 Travelers need to be able to gain access the shared vehicle they have arranged to use.
047 The system shall present shared user traveler information to the traveler upon request. 05 Travelers need to be able to request and confirm shared use transportation, including time for pickup, as well as pickup and drop-off locations
048 The system shall communicate with the traveler device to allow access to the micromobility vehicle. 08 Travelers need to be able to gain access the shared vehicle they have arranged to use.
049 The system shall provide updates to the traveler's account as directed by the traveler. 10 Travelers need to be able to set up and update user accounts for shared use transportation systems.
 

Implementations


TI06.1 Shared Use Mobility Implementation

This implementation addresses the range of shared use transit operations that support a complete trip for travelers. This service supports planning, reservations, and on-trip guidance for these operations. The complete trip may be arranged and undertaken using an internet connected personal device. The implementation includes temporary use of a vehicle or micromobility vehicle by the traveler as well as having a vehicle pick up the traveler at a specific location and take them to another location.

Shared Use Mobility Implementation Flows

Information FlowDescriptionInclusion Status
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
MMV access enable Information used to enable access to a shared use MMV. At Least One
MMV identification MMV identification (e.g., a QR code) used to access an MMV. At Least One
MMV location The current location (latitude, longitude, and elevation) reported by an MMV OBE. Optional
payment device update Information updated concerning traveler's personal data including name, address, user account information, trip records, and profile data. Optional
payment methods financial institution A list of valid payment methods accepted by a financial center. Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
request for payment Request to deduct cost of service from user's payment account. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
shared use confirmation Confirmation that traveler is going to use the shared use asset now or at a future time. Optional
shared use confirmation Confirmation that traveler is going to use the shared use asset now or at a future time. Fundamental
shared use request Request for shared use asset (e.g., car or bicycle) now or as a reservation for future use. Fundamental
shared use request Request for shared use asset (e.g., car or bicycle) now or as a reservation for future use. Optional
shared use response Response from shared use provider regarding availability of the shared use asset now or in the future. Includes any payment requirements. Optional
shared use response Response from shared use provider regarding availability of the shared use asset now or in the future. Includes any payment requirements. Fundamental
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. Optional
shared vehicle access enable Information used to enable access to a shared use vehicle. At Least One
shared vehicle access request Request for access to a shared use vehicle. At Least One
shared vehicle information Detailed information about the vehicle the traveler is going to use as part of a shared use mode. The information could include locations details (e.g. parking space or docking number), as well as details about the vehicle (e.g. model, color, or license plate number), including its current vehicle location and ETA. At Least One
SUTC operations information presentation Presentation of information to the SUTC Operator including current operational status of the back office system, the shared mobility assets in the field, current user/client information, and past, current, and future shared use activities. Optional
SUTC operator input User input from the SUTC system operator including requests to monitor current system operation and inputs to affect system operation including operating parameters, asset status, and client status. Optional
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. Optional
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. Optional
traveler input User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service. Optional
traveler interface updates Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler. Optional
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Optional
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. Optional


Shared Use Mobility Implementation Functional Objects

Functional Object
Light Vehicle Access
MMV Access
Personal Shared Use Planning
Personal Trip Planning and Route Guidance
Shared Use Account and Fee Management
Shared Use Operations
TIC Data Collection
TIC Dynamic Ridesharing
TIC Trip Planning
Transit Center Paratransit Operations
Traveler Trip Planning


Back to Implementation List

TI06.2 Dynamic Ridesharing Implementation

Covers both implementations for dynamic carpooling and Uber/Lift-style ridesharing. The algorithms are similar, with a financial transaction overlay, which might be mandatory in a commercial pay-to-ride service and optional in a carpool service where users may send each other optional micro-payments.

Dynamic Ridesharing Implementation Flows

Information FlowDescriptionInclusion Status
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction. Optional
demand responsive transit plan Plan regarding overall demand responsive transit schedules and deployment. Optional
demand responsive transit request Request for paratransit support. Optional
light vehicle driver input Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. Optional
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. Optional
MMV access enable Information used to enable access to a shared use MMV. Optional
MMV identification MMV identification (e.g., a QR code) used to access an MMV. Optional
MMV location The current location (latitude, longitude, and elevation) reported by an MMV OBE. Optional
payment device update Information updated concerning traveler's personal data including name, address, user account information, trip records, and profile data. Optional
payment methods financial institution A list of valid payment methods accepted by a financial center. Optional
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry) Optional
request for payment Request to deduct cost of service from user's payment account. Optional
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. Optional
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. Optional
shared vehicle access enable Information used to enable access to a shared use vehicle. Optional
shared vehicle access request Request for access to a shared use vehicle. Optional
shared vehicle information Detailed information about the vehicle the traveler is going to use as part of a shared use mode. The information could include locations details (e.g. parking space or docking number), as well as details about the vehicle (e.g. model, color, or license plate number), including its current vehicle location and ETA. Optional
SUTC operations information presentation Presentation of information to the SUTC Operator including current operational status of the back office system, the shared mobility assets in the field, current user/client information, and past, current, and future shared use activities. Optional
SUTC operator input User input from the SUTC system operator including requests to monitor current system operation and inputs to affect system operation including operating parameters, asset status, and client status. Optional
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. Optional
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. Optional
traveler input User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service. Optional
traveler interface updates Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler. Optional
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. Fundamental
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. At Least One
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. Optional
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. Fundamental
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. At Least One
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. At Least One
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. Fundamental
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes. Optional
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. Optional


Dynamic Ridesharing Implementation Functional Objects

Functional Object
Light Vehicle Trip Planning and Route Guidance
Personal Shared Use Planning
Personal Trip Planning and Route Guidance
Shared Use Operations
TIC Data Collection
TIC Dynamic Ridesharing
TIC Trip Planning
Transit Center Paratransit Operations
Traveler Trip Planning


Back to Implementation List