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.

Transit Stop Request

The Transit Stop Request application allows a transit passenger to send a stop request to an approaching transit vehicle. This application allows a transit vehicle to know that a passenger has requested a transit stop from an infrastructure device.

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:

Transit Stop Request Operations Stage
Roadway OwnerRSE OwnerRSE OperatorTransit Vehicle OperatorTravelerTransit Fleet ManagerKiosk ProviderRSE Transit User Guidance ProviderTransit Vehicle On-Board Trip Monitoring Provider
Roadway OwnerService Delivery AgreementExpectation of Action
RSE OwnerService Delivery AgreementOperations AgreementExpectation of Information ProvisionApplication Usage Agreement
RSE OperatorOperations Agreement
Transit Vehicle OperatorExpectation of ActionVehicle Usage Agreement
TravelerExpectation of ActionExpectation of ActionExpectation of Information Provision
Transit Fleet ManagerVehicle Usage AgreementExpectation of Information ProvisionInformation Exchange AgreementApplication Usage Agreement
Kiosk ProviderExpectation of Information ProvisionInformation Exchange Agreement
RSE Transit User Guidance ProviderApplication Usage Agreement
Transit Vehicle On-Board Trip Monitoring ProviderApplication Usage Agreement

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.
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.
ITS Certification Entity The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
Kiosk Provider The entity that deploys and operates public information devices.
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.
Roadway Owner The owner of the roadway proximate to which roadside equipment will be/is installed.
RSE Deployer The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Operator The entity that operates roadside equipment in the transportation environment.
RSE Owner The owner of roadside equipment.
RSE Provider The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research.
RSE Transit User 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.
RSE Transit User 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.
RSE Transit User 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.
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.
Traffic Manager The entity responsible for the management of traffic, both freeway and arterial.
Transit Center Information Services 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.
Transit Center Information Services 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.
Transit Center Information Services 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.
Transit Stop Information Services 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 Vehicle Manufacturer The entity which builds transit vehicles. This entity is complementary to the Vehicle Manufacturer entity in that it represents those aspects of vehicle manufacture which are unique to transit vehicles.
Transit Vehicle OBE Manufacturer The Transit Vehicle OBE Manufacturer is the provider of the transit vehicle on-board equipment. This entity may design and build the OBE, or may integrate other components to form the OBE, or may use some combination of approaches to provide the on-board equipment. Since the OBE could be aftermarket, retrofit, built-in or nomadic, this entity is the one that builds whatever that-is. In some cases it may be a smart phone manufacturer, or in others a top tier parts supplier, or any other entity in the production chain, depending on the device and commercial vehicle in question.
Transit Vehicle On-Board Information Services 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.
Transit Vehicle On-Board Information Services 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.
Transit Vehicle On-Board Information Services 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 Vehicle On-Board Trip Monitoring 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.
Transit Vehicle On-Board Trip Monitoring 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.
Transit Vehicle On-Board Trip Monitoring 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 Vehicle Operator The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.
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.

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.
Field Component Installation System The system used to install a field component of a connected vehicle application.
Field Component Maintenance System The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Certification Requirements The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation 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.
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.
Public Information Device The Public Information Device 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, the Public Information Device also supports security and safety monitoring of public areas. This monitoring includes traveler activated silent alarms, as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras) and/or audio systems. The sensor equipment includes threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors (e.g. metal detectors).
Roadside Equipment 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
RSE Development System The system used in a backoffice environment to develop and test the roadside equipment.
RSE Installation System The system used to install and configure the roadside equipment.
RSE Maintenance System The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance.
RSE Transit User Guidance "RSE Transit User Guidance" uses short range communications to provide terminal or stop-specific guidance to transit user devices that assists users in finding the right stop and the right bus. Optionally, this object can collect the transit user location and planned itinerary so that tailored guidance can be provided.
Transit Center Information Services "Transit Center Information Services" collects the latest available information for a transit service and makes it available to transit customers and to Transportation Information Centers for further distribution. Customers are provided information at transit stops and other public transportation areas before they embark and on-board the transit vehicle once they are enroute. Information provided can include the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, yellow pages, and special events. In addition to general service information, tailored information (e.g., itineraries) are provided to individual transit users.
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.
Transit Stop Information Services "Transit Stop Information Services" furnishes transit users with real-time travel-related information at transit stops, multi-modal transfer points, and other public transportation areas. It provides transit users with information on transit routes, schedules, transfer options, available services, fares, and real-time schedule adherence. In addition to tailored information for individual transit users, it supports general annunciation and/or display of imminent arrival information and other information of general interest to transit users.
Transit Vehicle The vehicle that provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. This includes buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles.
Transit Vehicle Databus The 'Transit Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a transit vehicle. It is a specialized and extended form of the Vehicle Databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers. In CVRIA, the 'Transit Vehicle Databus' is used to represent the onboard interactions between the Transit Vehicle OBE and the other systems included in a host transit vehicle.
Transit Vehicle OBE The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transit Vehicle On-Board Information Services "Transit Vehicle On-board Information Services" furnishes en-route transit users with real-time travel-related information on-board a transit vehicle. Current information that can be provided to transit users includes transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, non-motorized transportation services, and special events are provided. In addition to tailored information for individual transit users, it also supports general annunciation and/or display of general schedule information, imminent arrival information, and other information of general interest to transit users.
Transit Vehicle On-Board Trip Monitoring "Transit Vehicle On-Board Trip Monitoring" tracks vehicle location, monitors fuel usage, collects operational status (doors opened/closed, running times, etc.) and sends the collected, time stamped data to the Transit Management Center.

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 Agreement Agreement An agreement in which one entity maintains the operational status of a software 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.
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.
Device Placement and Operations Agreement Agreement An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Expectation of Action Expectation An expectation where one party expects another party to take a specific action, typically in response to data or information provided by the first party, but without any formal agreement.
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.
Field Component Installation Agreement Agreement An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party.
Field Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the field 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.
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.
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.
Operations Agreement Agreement An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
RSE Deployment Agreement Agreement Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data Information Sharing Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data Information Sharing Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data Information Sharing Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
RSE Procurement Agreement Agreement An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process.
Service Delivery Agreement Agreement A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
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 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.1 Operate Transit Vehicles and Facilities Collection
4.1.1 Process On-Board Systems Data Pspec - Transit Vehicle On-Board Information Services
- Transit Vehicle On-Board Trip Monitoring
4.1.2 Determine Transit Vehicle Service Status Pspec - Transit Vehicle On-Board Information Services
- Transit Vehicle On-Board Trip Monitoring
4.1.3 Provide Transit Vehicle Location Data Pspec - Transit Vehicle On-Board Trip Monitoring
4.1.4 Manage Transit Vehicle Deviations Pspec - Transit Center Information Services
4.1.6 Manage Transit Vehicle Operations Pspec - Transit Center Information Services
4.1.7 Provide Transit Advisory Interface on Vehicle Pspec - Transit Vehicle On-Board Information Services
4.1.8 Manage Individual Service Requests Pspec - Transit Center Information Services
4.6 Collect Transit Fares in the Vehicle Collection
4.6.2 Determine Traveler Needs on Vehicle Pspec - Transit Vehicle On-Board Information Services
- Transit Vehicle On-Board Trip Monitoring
4.7 Provide Traveler Roadside Facilities Collection
4.7.1 Provide Traveler Roadside & Vehicle Data Interface Pspec - Transit Stop Information Services
4.7.3 Provide Transit Traveler Roadside Interface Pspec - RSE Transit User Guidance
6.8 Provide Traveler Personal Services Collection
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

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Determine Transit Vehicle Service Status transit_vehicle_deviations_from_schedule Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_vehicle_passenger_connection_request Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_vehicle_connection_request_mode Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_service_status Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_schedule_deviation Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_eta Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_service_update Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_passenger_connection_response Provide Transit Advisory Interface on Vehicle
Determine Transit Vehicle Service Status transit_vehicle_eta_for_advisory Provide Transit Advisory Interface on Vehicle
Determine Traveler Needs on Vehicle transit_vehicle_traveler_service_requests Determine Transit Vehicle Service Status
Determine Traveler Needs on Vehicle transit_user_information Manage Individual Service Requests
Determine Traveler Needs on Vehicle individual_transit_user_connection_request Manage Individual Service Requests
Get Traveler Personal Request transit_stop_request_from_user_to_vehicle Determine Traveler Needs on Vehicle
Get Traveler Personal Request transit_stop_request_from_user Manage Individual Service Requests
Get Traveler Personal Request traveler_personal_information_request_for_response Provide Traveler with Personal Travel Information
Manage Individual Service Requests individual_transit_user_trip_plan Determine Traveler Needs on Vehicle
Manage Individual Service Requests individual_transit_user_connection_response Determine Traveler Needs on Vehicle
Manage Individual Service Requests request_for_deviation_to_protect_connection Manage Transit Vehicle Deviations
Manage Individual Service Requests transit_trip_plan_for_user Provide Traveler with Personal Travel Information
Manage Transit Vehicle Deviations signal_priority_rules Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_response Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_response_constraints Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_instructions Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations approved_corrective_plan Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_stop_requests_from_center Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations deviation_response_to_protect_connection Manage Individual Service Requests
Manage Transit Vehicle Deviations transit_vehicle_deviation_update Manage Transit Vehicle Operations
Manage Transit Vehicle Operations schedule_change_for_connection_protection Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations road_network_info_for_transit Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations transit_vehicle_service_enable Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations operations_input_for_deviations Manage Transit Vehicle Deviations
Manage Transit Vehicle Operations transit_vehicle_collected_maintenance_data_request Process On-Board Systems Data
Manage Transit Vehicle Operations transit_vehicle_advisory_eta Provide Transit Advisory Interface on Vehicle
Manage Transit Vehicle Operations transit_vehicle_arrival_time_for_roadside Provide Transit Traveler Roadside Interface
Manage Transit Vehicle Operations transit_vehicle_arrival_time Provide Traveler Roadside & Vehicle Data Interface
Manage Transit Vehicle Operations parking_facility_information Provide Traveler Roadside & Vehicle Data Interface
Manage Transit Vehicle Operations transit_vehicle_user_data Provide Traveler Roadside & Vehicle Data Interface
Manage Transit Vehicle Operations transit_vehicle_arrival_time Provide Traveler with Personal Travel Information
Manage Transit Vehicle Operations personal_parking_facility_information Provide Traveler with Personal Travel Information
Process On-Board Systems Data transit_vehicle_arrival_times Determine Transit Vehicle Service Status
Process On-Board Systems Data transit_vehicle_collected_maintenance_data Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_passenger_loading Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_running_times Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_on_board_data Provide Transit Vehicle Location Data
Provide Transit Advisory Interface on Vehicle transit_passenger_connection_request Determine Transit Vehicle Service Status
Provide Transit Advisory Interface on Vehicle transit_advisory_vehicle_information Determine Traveler Needs on Vehicle
Provide Transit Advisory Interface on Vehicle vehicle_to_roadside_transit_information Provide Transit Traveler Roadside Interface
Provide Transit Advisory Interface on Vehicle vehicle_to_roadside_transit_vehicle_information Provide Transit Traveler Roadside Interface
Provide Transit Advisory Interface on Vehicle vehicle_to_traveler_transit_information Provide Traveler with Personal Travel Information
Provide Transit Advisory Interface on Vehicle vehicle_to_traveler_transit_vehicle_information Provide Traveler with Personal Travel Information
Provide Transit Traveler Roadside Interface transit_stop_request_from_roadside Determine Traveler Needs on Vehicle
Provide Transit Traveler Roadside Interface roadside_to_traveler_transit_information Provide Traveler Roadside & Vehicle Data Interface
Provide Transit Traveler Roadside Interface roadside_to_traveler_transit_vehicle_information Provide Traveler Roadside & Vehicle Data Interface
Provide Transit Vehicle Location Data transit_vehicle_location_for_eta Determine Transit Vehicle Service Status
Provide Transit Vehicle Location Data transit_vehicle_location_for_deviation Manage Transit Vehicle Deviations
Provide Transit Vehicle Location Data transit_vehicle_location_for_store Manage Transit Vehicle Operations
Provide Transit Vehicle Location Data transit_vehicle_location_for_advisories Provide Transit Advisory Interface on Vehicle
Provide Traveler Personal Interface traveler_personal_trip_planning_requests Get Traveler Personal Request
Provide Traveler Roadside & Vehicle Data Interface transit_stop_request_from_traveler_to_center Manage Individual Service Requests
Provide Traveler Roadside & Vehicle Data Interface local_transit_information_for_roadside Provide Transit Traveler Roadside Interface
Provide Traveler Roadside & Vehicle Data Interface transit_stop_request_at_roadside Provide Transit Traveler Roadside Interface
Provide Traveler with Personal Travel Information transit_trip_confirmation_from_user Manage Individual Service Requests
Provide Traveler with Personal Travel Information transit_trip_request_from_user Manage Individual Service Requests
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

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
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.
Public Information Device Traveler The Public Information Device 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, the Public Information Device also supports security and safety monitoring of public areas. This monitoring includes traveler activated silent alarms, as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras) and/or audio systems. The sensor equipment includes threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors (e.g. metal detectors).
Roadside Equipment Field 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
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.
Transit Vehicle Databus Vehicle The 'Transit Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a transit vehicle. It is a specialized and extended form of the Vehicle Databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers. In CVRIA, the 'Transit Vehicle Databus' is used to represent the onboard interactions between the Transit Vehicle OBE and the other systems included in a host transit vehicle.
Transit Vehicle OBE Vehicle The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transit Vehicle Operator Vehicle The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.
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.

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
RSE Transit User Guidance "RSE Transit User Guidance" uses short range communications to provide terminal or stop-specific guidance to transit user devices that assists users in finding the right stop and the right bus. Optionally, this object can collect the transit user location and planned itinerary so that tailored guidance can be provided. Roadside Equipment
Transit Center Information Services "Transit Center Information Services" collects the latest available information for a transit service and makes it available to transit customers and to Transportation Information Centers for further distribution. Customers are provided information at transit stops and other public transportation areas before they embark and on-board the transit vehicle once they are enroute. Information provided can include the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, yellow pages, and special events. In addition to general service information, tailored information (e.g., itineraries) are provided to individual transit users. Transit Management Center
Transit Stop Information Services "Transit Stop Information Services" furnishes transit users with real-time travel-related information at transit stops, multi-modal transfer points, and other public transportation areas. It provides transit users with information on transit routes, schedules, transfer options, available services, fares, and real-time schedule adherence. In addition to tailored information for individual transit users, it supports general annunciation and/or display of imminent arrival information and other information of general interest to transit users. Public Information Device
Transit Vehicle On-Board Information Services "Transit Vehicle On-board Information Services" furnishes en-route transit users with real-time travel-related information on-board a transit vehicle. Current information that can be provided to transit users includes transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, non-motorized transportation services, and special events are provided. In addition to tailored information for individual transit users, it also supports general annunciation and/or display of general schedule information, imminent arrival information, and other information of general interest to transit users. Transit Vehicle OBE
Transit Vehicle On-Board Trip Monitoring "Transit Vehicle On-Board Trip Monitoring" tracks vehicle location, monitors fuel usage, collects operational status (doors opened/closed, running times, etc.) and sends the collected, time stamped data to the Transit Management Center. Transit Vehicle OBE

Includes Information Flows:

Information Flow Description
host transit vehicle status Information provided to the Connected Vehicle on-board equipment from other systems on the Transit Vehicle Platform.
transit stop request Notification that a transit stop has been requested by a transit user at a roadside stop. This flow identifies the route, stop, and the time of the request.
transit user information Information about individual transit users boarding a transit vehicle, used to track a user's progress on a scheduled transit trip.
transit vehicle information Information about the transit vehicle route and stops, including current location along the route and next stop.
transit vehicle operator display Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services.
transit vehicle operator input Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data.
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.

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

Requirements

Need Requirement
N2.182 Transit Stop Request (TSR) needs to accept stop requests from transit users at roadside stops. 2.388 Transit Stop Request (TSR) shall be able to accept stop requests from travelers at roadside stops.
N2.183 TSR needs to notify transit vehicles of stop requests along the transit vehicle's route. 2.392 TSR shall compare the location of a stop request to all transit routes.
2.393 TSR shall identify the transit vehicle that is following the matched route/stop request.
2.394 TSR shall forward stop requests to the transit vehicle on the route where the stop was requested.
N2.184 TSR needs transit routes so it can forward stop requests to the correct transit vehicle. 2.389 TSR shall request transit routes from the transit management center.
2.390 TSR shall be able to receive transit routes from the transit management center.
2.391 TSR shall maintain a list of transit routes, including timing and stops.

Related Sources

  • SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods, 8/15/2014

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
Basis Basis Basis
Security levels have not been defined yet.