Type: Mobility

Groups:

Transit

Diagrams are based on the most recently available application concepts that the CVRIA team has access to, and do not necessarily reflect prototypes or other in-development activities.

Dynamic Ridesharing

The Dynamic Ridesharing application allows travelers to arrange carpool trips through a stand-alone personal device with a wireless connection and/or an automated ridematching system (e.g., call center or web-based application loaded on a personal computer or kiosk at a transit facility). The application 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 application to improve the user's experience for future trips and monitor use of high-occupancy lanes.

Enterprise
Functional
Physical
A-Interconnect
Communications
Requirements
Sources
Security

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification

Display Legend in SVG or PNG

Business Interaction Matrix:

Dynamic Ridesharing Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Information Service Provider	Traveler	Transit Fleet Manager	Personal Trip Planning and Route Guidance Provider	Vehicle Trip Planning and Route Guidance Provider
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement					Application Usage Agreement
Driver	Vehicle Usage Agreement		Expectation of Information Provision
Vehicle OBE Owner	Vehicle OBE Usage Agreement	Expectation of Information Provision		Information Exchange Agreement
Information Service Provider			Information Exchange Agreement		Information Exchange Agreement	Information Exchange and Action Agreement
Traveler				Information Exchange Agreement			Application Usage Agreement
Transit Fleet Manager				Information Exchange and Action Agreement
Personal Trip Planning and Route Guidance Provider					Application Usage Agreement
Vehicle Trip Planning and Route Guidance Provider	Application Usage Agreement

Dynamic Ridesharing Certification Stage
	Vehicle OBE Manufacturer	Vehicle Manufacturer	Application Certification Entity	Federal Regulatory	State Regulatory	Device Certification Entity	PID Provider
Vehicle OBE Manufacturer			Member			Member
Vehicle Manufacturer			Member			Member
Application Certification Entity	Member	Member		Member	Member
Federal Regulatory			Member			Member
State Regulatory			Member			Member
Device Certification Entity	Member	Member		Member	Member		Member
PID Provider						Member

Includes Enterprise Objects:

Enterprise Object	Description
Application Certification Entity	The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications.
Device Certification Entity	The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type.
Driver	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Federal Regulatory	Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
Information Service Provider	The "Information Service Provider" represents the owner of the Transportation Information Center. The Information Service Provider is responsible for collecting and disseminating information relevant to the traveling public.
Payment Device Manufacturer	The entity responsible for the design, manufacture and distribution of the Payment Device.
Personal Trip Planning and Route Guidance Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Personal Trip Planning and Route Guidance Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Personal Trip Planning and Route Guidance Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
PID Provider	The entity that designs, manufacturers and provides (either to the end user or to a reseller) the personal information device, including its hardware and base operating software.
State Regulatory	State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies.
TIC Data Collection Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Data Collection Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Data Collection Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TIC Dynamic Ridesharing Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Dynamic Ridesharing Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Dynamic Ridesharing Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TIC Trip Planning Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Trip Planning Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TIC Trip Planning Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Fleet Manager	The agency or organization that operates transit vehicles. This includes administration, routing, driver instruction, maintenance and any other responsibilities associated with the operations and maintenance of a transit system.
Traveler	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.
Vehicle Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle in which the Vehicle OBE will eventually operate.
Vehicle OBE Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
Vehicle OBE Owner	The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner	The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.
Vehicle Trip Planning and Route Guidance Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Trip Planning and Route Guidance Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Trip Planning and Route Guidance Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.

Includes Resources:

Resource	Description
Application Component Certification Requirements	The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE.
Backoffice Service Development System	The systems used to develop backoffice (center) hardware and software components of applications.
Backoffice Service Installation System	The systems used to install and configure backoffice (center) hardware and software components.
Backoffice Service Maintenance System	The systems used to maintain and upgrade backoffice (center) hardware and software components.
Device Certification Requirements	The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment.
Mobile Component Development System	The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System	The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System	The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Payment Device	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	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 connected vehicle on-board equipment.
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 application object include desktop computers at home, work, or at major trip generation sites, plus personal devices such as tablets and smart phones.
PID Component Development System	The system used in a backoffice environment to develop and test the PID component of the application.
PID Component Installation System	The system used to install the PID component of a connected vehicle application.
PID Component Maintenance System	The system used to configure changes and updates to the PID component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
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.
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.
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.
Transit Management 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 allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information 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.
Vehicle	The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types.
Vehicle OBE	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Vehicle Trip Planning and Route Guidance	"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.

Includes Roles:

Role	Description
Certifies	An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements.
Constrains	A Resource or Enterprise applies requirements, constraints and associated tests to another Resource.
Develops	An Enterprise creates the target Resource or Document.
Installs	An Enterprise performs the initial delivery, integration and configuration of the target Resource.
Maintains	An Enterprise administers the hardware and software that comprise the target Resource.
Member	An Enterprise is part of another larger, target Enterprise.
Operates	An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible.
Owns	An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable.

Includes Coordination:

Coordination	Type	Description
Application Installation Agreement	Agreement	An agreement that grants one party permission to install an application component on a device controlled by the other party.
Application Installation Data	Information Sharing	Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification	Agreement	The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Maintenance Data	Information Sharing	Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data	Information Sharing	Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement	Agreement	An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement	Agreement	An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Backoffice Component Installation Agreement	Agreement	An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Backoffice Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Expectation of Information Provision	Expectation	An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Includes	Includes	Indicates that one component is entirely contained within another component.
Information Exchange Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Information Exchange and Action Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Interface Description	Agreement	Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator.
Maintenance Data Exchange Agreement	Agreement	An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement	Agreement	An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement	Agreement	An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Mobile Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Vehicle Data Access Agreement	Agreement	An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle OBE Usage Agreement	Agreement	An agreement that grants one entity permission to use a Vehicle OBE that the other party controls.
Vehicle Procurement Agreement	Agreement	The exchange of a vehicle for compensation. One entity purchases the vehicle from the other.
Vehicle Usage Agreement	Agreement	An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle.
Warranty	Agreement	A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component.

Functional

Includes Processes:

Level	Name	Type	Allocated to Application Object
4.2	Plan and Schedule Transit Services	Collection
4.2.1	Provide Demand Responsive Transit Service	Collection
4.2.1.1	Process Demand Responsive Transit Trip Request	Pspec
6.1	Provide Trip Planning Services	Collection
6.1.1	Provide Trip Planning Information to Traveler	Pspec	- TIC Trip Planning - TIC Dynamic Ridesharing
6.1.2	Confirm Traveler's Trip Plan	Pspec	- TIC Trip Planning - TIC Dynamic Ridesharing
6.4	Manage Ridesharing	Collection
6.4.1	Screen Rider Requests	Pspec	- TIC Dynamic Ridesharing
6.4.2	Match Rider and Provider	Pspec	- TIC Dynamic Ridesharing
6.4.3	Report Ride Match Results to Requestor	Pspec	- TIC Dynamic Ridesharing
6.4.4	Confirm Traveler Rideshare Request	Pspec	- TIC Dynamic Ridesharing
6.5	Provide Traveler Information Services	Collection
6.5.4	Process Travel Services Provider Data	Pspec	- TIC Data Collection - TIC Trip Planning
6.5.9	Provide Traveler Alert Interface	Pspec	- TIC Trip Planning
6.6	Provide Guidance and Routing Services	Collection
6.6.1	Provide Multimodal Route Selection	Pspec	- TIC Trip Planning
6.6.2	Select Vehicle Route	Collection
6.6.2.1	Calculate Vehicle Route	Pspec	- TIC Trip Planning
6.7	Provide Driver Personal Services	Collection
6.7.1	Provide On-line Vehicle Guidance	Collection
6.7.1.1	Provide Vehicle Guidance	Collection
6.7.1.1.1	Determine In-Vehicle Guidance Method	Pspec	- Vehicle Trip Planning and Route Guidance
6.7.1.1.2	Provide Dynamic In-Vehicle Guidance	Pspec	- Vehicle Trip Planning and Route Guidance
6.7.1.2	Provide Driver Guidance Interface	Pspec	- Vehicle Trip Planning and Route Guidance
6.7.3	Provide Traveler Services in Vehicle	Collection
6.7.3.1	Get Driver Personal Request	Pspec	- Vehicle Trip Planning and Route Guidance
6.7.3.2	Provide Driver with Personal Travel Information	Pspec	- Vehicle Trip Planning and Route Guidance
6.7.3.3	Provide Driver Information Interface	Pspec
6.8	Provide Traveler Personal Services	Collection
6.8.1	Provide On-line Traveler Guidance	Collection
6.8.1.1	Provide Traveler Guidance	Collection
6.8.1.1.1	Determine Personal Portable Device Guidance Method	Pspec	- Personal Trip Planning and Route Guidance
6.8.1.1.2	Provide Personal Portable Device Dynamic Guidance	Pspec	- Personal Trip Planning and Route Guidance
6.8.1.2	Provide Personal Portable Device Guidance Interface	Pspec	- Personal Trip Planning and Route Guidance
6.8.3	Provide Traveler Services at Personal Devices	Collection
6.8.3.1	Get Traveler Personal Request	Pspec	- Personal Trip Planning and Route Guidance
6.8.3.2	Provide Traveler with Personal Travel Information	Pspec	- Personal Trip Planning and Route Guidance
6.8.3.3	Provide Traveler Personal Interface	Pspec	- Personal Trip Planning and Route Guidance
6	Provide Driver and Traveler Services	Collection
6.10	Manage Traveler Profiles	Pspec	- TIC Trip Planning
7.5.3	Provide Personal Payment Device Interface	Pspec	- Personal Trip Planning and Route Guidance

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Calculate Vehicle Route	vehicle_guidance_route	Provide Dynamic In-Vehicle Guidance
Calculate Vehicle Route	vehicle_route	Provide Multimodal Route Selection
Confirm Traveler Rideshare Request	rideshare_confirmation	Confirm Traveler's Trip Plan
Confirm Traveler Rideshare Request	rideshare_confirmation_data	Match Rider and Provider
Confirm Traveler's Trip Plan	traveler_rideshare_confirmation	Confirm Traveler Rideshare Request
Confirm Traveler's Trip Plan	paratransit_service_confirmation	Process Demand Responsive Transit Trip Request
Confirm Traveler's Trip Plan	vehicle_payment_confirmation	Provide Driver with Personal Travel Information
Confirm Traveler's Trip Plan	traveler_personal_payment_confirmation	Provide Traveler with Personal Travel Information
Determine In-Vehicle Guidance Method	vehicle_guidance_route_accepted	Calculate Vehicle Route
Determine In-Vehicle Guidance Method	driver_input_request	Provide Driver Guidance Interface
Determine In-Vehicle Guidance Method	driving_guidance_instructions	Provide Driver Guidance Interface
Determine In-Vehicle Guidance Method	dynamic_vehicle_guidance_data_request	Provide Dynamic In-Vehicle Guidance
Determine Personal Portable Device Guidance Method	traveler_route_accepted	Provide Multimodal Route Selection
Determine Personal Portable Device Guidance Method	dynamic_traveler_guidance_data_request	Provide Personal Portable Device Dynamic Guidance
Determine Personal Portable Device Guidance Method	traveler_guidance_instructions	Provide Personal Portable Device Guidance Interface
Determine Personal Portable Device Guidance Method	traveler_input_request	Provide Personal Portable Device Guidance Interface
Get Driver Personal Request	vehicle_payment_information	Confirm Traveler's Trip Plan
Get Driver Personal Request	vehicle_trip_confirmation	Confirm Traveler's Trip Plan
Get Driver Personal Request	vehicle_profile	Manage Traveler Profiles
Get Driver Personal Request	vehicle_transaction_request	Process Travel Services Provider Data
Get Driver Personal Request	vehicle_payment_information_for_services	Process Travel Services Provider Data
Get Driver Personal Request	vehicle_travel_services_data_request	Process Travel Services Provider Data
Get Driver Personal Request	vehicle_information_request_for_response	Provide Driver with Personal Travel Information
Get Driver Personal Request	vehicle_alert_subscriptions	Provide Traveler Alert Interface
Get Driver Personal Request	vehicle_trip_request	Provide Trip Planning Information to Traveler
Get Traveler Personal Request	traveler_personal_payment_information	Confirm Traveler's Trip Plan
Get Traveler Personal Request	traveler_personal_trip_confirmation	Confirm Traveler's Trip Plan
Get Traveler Personal Request	traveler_personal_profile	Manage Traveler Profiles
Get Traveler Personal Request	personal_freight_traveler_information_profile	Manage Traveler Profiles
Get Traveler Personal Request	traveler_personal_transaction_request	Process Travel Services Provider Data
Get Traveler Personal Request	traveler_personal_payment_information_for_services	Process Travel Services Provider Data
Get Traveler Personal Request	traveler_personal_travel_services_data_request	Process Travel Services Provider Data
Get Traveler Personal Request	traveler_personal_alert_subscriptions	Provide Traveler Alert Interface
Get Traveler Personal Request	traveler_personal_information_request_for_response	Provide Traveler with Personal Travel Information
Get Traveler Personal Request	traveler_personal_trip_request	Provide Trip Planning Information to Traveler
Manage Traveler Profiles	profiles_for_route_guidance	Calculate Vehicle Route
Manage Traveler Profiles	profiles_for_travel_services	Process Travel Services Provider Data
Manage Traveler Profiles	profiles_for_route_selection	Provide Multimodal Route Selection
Manage Traveler Profiles	profiles_for_alerts	Provide Traveler Alert Interface
Manage Traveler Profiles	profiles_for_trip_planning	Provide Trip Planning Information to Traveler
Match Rider and Provider	rideshare_selection	Report Ride Match Results to Requestor
Process Demand Responsive Transit Trip Request	paratransit_personal_schedule	Provide Trip Planning Information to Traveler
Process Travel Services Provider Data	vehicle_transaction_confirmation	Provide Driver with Personal Travel Information
Process Travel Services Provider Data	vehicle_travel_services_provider_data	Provide Driver with Personal Travel Information
Process Travel Services Provider Data	traveler_personal_transaction_confirmation	Provide Traveler with Personal Travel Information
Process Travel Services Provider Data	traveler_personal_travel_services_provider_data	Provide Traveler with Personal Travel Information
Provide Driver Guidance Interface	vehicle_trip_feedback	Confirm Traveler's Trip Plan
Provide Driver Guidance Interface	driver_guidance_accepted	Determine In-Vehicle Guidance Method
Provide Driver Guidance Interface	driver_guidance_request	Determine In-Vehicle Guidance Method
Provide Driver Guidance Interface	driver_guidance_data	Determine In-Vehicle Guidance Method
Provide Driver Information Interface	vehicle_trip_planning_requests	Get Driver Personal Request
Provide Driver Information Interface	vehicle_display_type	Provide Driver with Personal Travel Information
Provide Driver with Personal Travel Information	vehicle_advisory_information	Provide Driver Information Interface
Provide Driver with Personal Travel Information	vehicle_traveler_information	Provide Driver Information Interface
Provide Driver with Personal Travel Information	vehicle_trip_planning_responses	Provide Driver Information Interface
Provide Dynamic In-Vehicle Guidance	vehicle_route_request	Calculate Vehicle Route
Provide Dynamic In-Vehicle Guidance	dynamic_vehicle_guidance_data	Determine In-Vehicle Guidance Method
Provide Multimodal Route Selection	get_vehicle_route	Calculate Vehicle Route
Provide Multimodal Route Selection	paratransit_route_confirm	Confirm Traveler's Trip Plan
Provide Multimodal Route Selection	traveler_guidance_route	Provide Personal Portable Device Dynamic Guidance
Provide Multimodal Route Selection	paratransit_route_request	Provide Trip Planning Information to Traveler
Provide Multimodal Route Selection	supplied_route	Provide Trip Planning Information to Traveler
Provide Personal Payment Device Interface	traveler_personal_data	Provide Personal Portable Device Guidance Interface
Provide Personal Payment Device Interface	traveler_personal_data	Provide Traveler Personal Interface
Provide Personal Portable Device Dynamic Guidance	dynamic_traveler_guidance_data	Determine Personal Portable Device Guidance Method
Provide Personal Portable Device Dynamic Guidance	traveler_route_request	Provide Multimodal Route Selection
Provide Personal Portable Device Guidance Interface	traveler_personal_trip_feedback	Confirm Traveler's Trip Plan
Provide Personal Portable Device Guidance Interface	traveler_guidance_request	Determine Personal Portable Device Guidance Method
Provide Personal Portable Device Guidance Interface	traveler_guidance_accepted	Determine Personal Portable Device Guidance Method
Provide Personal Portable Device Guidance Interface	traveler_guidance_data	Determine Personal Portable Device Guidance Method
Provide Personal Portable Device Guidance Interface	traveler_personal_map_update_cost	Provide Personal Payment Device Interface
Provide Traveler Alert Interface	vehicle_border_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_event_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_incident_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_multimodal_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_parking_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_traffic_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_transit_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	vehicle_weather_alert	Provide Driver with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_border_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_event_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_incident_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_multimodal_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_parking_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_traffic_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_transit_alert	Provide Traveler with Personal Travel Information
Provide Traveler Alert Interface	traveler_personal_weather_alert	Provide Traveler with Personal Travel Information
Provide Traveler Personal Interface	traveler_personal_trip_planning_requests	Get Traveler Personal Request
Provide Traveler Personal Interface	traveler_personal_data_update	Provide Personal Payment Device Interface
Provide Traveler with Personal Travel Information	personal_traveler_information	Provide Traveler Personal Interface
Provide Traveler with Personal Travel Information	traveler_personal_trip_planning_responses	Provide Traveler Personal Interface
Provide Trip Planning Information to Traveler	paratransit_trip_request	Process Demand Responsive Transit Trip Request
Provide Trip Planning Information to Traveler	vehicle_trip_information	Provide Driver with Personal Travel Information
Provide Trip Planning Information to Traveler	paratransit_route_response	Provide Multimodal Route Selection
Provide Trip Planning Information to Traveler	trip_route_request	Provide Multimodal Route Selection
Provide Trip Planning Information to Traveler	traveler_personal_trip_information	Provide Traveler with Personal Travel Information
Provide Trip Planning Information to Traveler	traveler_rideshare_request	Screen Rider Requests
Report Ride Match Results to Requestor	rideshare_response	Provide Trip Planning Information to Traveler
Screen Rider Requests	rideshare_request_from_eligible_traveler	Match Rider and Provider
Screen Rider Requests	rideshare_ineligible_status_notification	Report Ride Match Results to Requestor

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
Driver	Vehicle	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Payment Device	Traveler	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	Traveler	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 connected vehicle on-board equipment.
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 allow for 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	Traveler	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.
Vehicle OBE	Vehicle	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Application Objects:

Application Object	Description	Physical Object
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 application 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
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
Vehicle Trip Planning and Route Guidance	"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.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
demand responsive transit plan	Plan regarding overall demand responsive transit schedules and deployment.
demand responsive transit request	Request for paratransit support.
driver input	Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates	Information provided to the 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.
payment	Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
request for payment	Request to deduct cost of service from user's payment account.
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.
trip feedback	Information provided 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 identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
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 and ridesharing options associated with the trip.
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., maximum transfer wait time, maximum walking distance, mode preferences, special needs), device information, a user ID and password, and information to support payment transactions, if applicable.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
None: Human interface	Driver	Vehicle OBE	driver input
	Payment Device	Personal Information Device	payment
	Personal Information Device	Payment Device	request for payment
None: Human interface	Personal Information Device	Traveler	traveler interface updates
	Personal Information Device	Transportation Information Center	trip confirmation
	Personal Information Device	Transportation Information Center	trip feedback
	Personal Information Device	Transportation Information Center	trip request
	Personal Information Device	Transportation Information Center	user profile
	Transit Management Center	Transportation Information Center	demand responsive transit plan
	Transportation Information Center	Transit Management Center	demand responsive transit request
	Transportation Information Center	Vehicle OBE	trip plan
	Transportation Information Center	Personal Information Device	trip plan
None: Human interface	Traveler	Personal Information Device	traveler input
None: Human interface	Vehicle OBE	Driver	driver updates
	Vehicle OBE	Transportation Information Center	trip confirmation
	Vehicle OBE	Transportation Information Center	trip feedback
	Vehicle OBE	Transportation Information Center	trip request
	Vehicle OBE	Transportation Information Center	user profile

Requirements

Need		Requirement
N2.051	Dynamic Ridesharing (D-RIDE) needs to accept profile information from a traveler to understand that traveler's preferences and process payment.	2.118	Dynamic Ridesharing (D-RIDE) shall provide a mechanism to accept traveler travel preferences.
N2.051		2.119	D-RIDE shall maintain traveler preferences and payment information.
N2.052	D-RIDE needs to accept commuter and driver information, including origin/destination, arrival time, departure time, number of riders, number of available passenger spaces.	2.120	D-RIDE shall accept carpool requests from T-CONNECT.
		2.121	D-RIDE shall provide a mechanism for commuters to input their travel needs.
		2.122	D-RIDE shall provide a mechanism for drivers to input their commuting capabilities.
N2.053	D-RIDE needs to match riding commuters to drivers	2.123	D-RIDE shall maintain a listing of all commuters that are seeking rides.
		2.124	D-RIDE shall maintain a listing of all drivers that may provide rides.
		2.125	D-RIDE shall match commuter's needed rides with drivers available to provide rides.
N2.054	D-RIDE needs to provide ride matching information to commuters.	2.126	D-RIDE shall notify drivers of their pickups, including pickup name, location and desired time.
N2.054		2.127	D-RIDE shall notify commuters of their rides including driver name, location of pickup and scheduled time.
N2.055	D-RIDE needs to provide a mechanism for the confirmation of ride matching.	2.128	D-RIDE shall accept ride-match confirmation from commuters.
		2.129	D-RIDE shall accept ride-match confirmation from drivers.
		2.130	D-RIDE shall notify all parties of a declined ride match.

Related Sources

Report on Functional Requirements and Software Architecture for the IDTO Prototype Phase I Demonstration Site (Columbus), Final, 8/30/2013
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 application, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Security levels have not been defined yet.

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

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Security levels have not been defined yet.