Type: Safety

Groups:

Transit Safety

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 Vehicle at Station/Stop Warnings

The Transit Vehicle at Station/Stop Warnings application inform nearby vehicles of the presence of a transit vehicle at a station or stop. The application also indicates the intention of the transit vehicle in terms of pulling into or out of a station/stop.

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:

Transit Vehicle at Station/Stop Warnings Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Transit Vehicle Operator	Personal Pedestrian Safety Provider	RSE Intersection Management Provider	Traveler	Transit Fleet Manager	Vehicle Basic Safety Provider	Vehicle Roadside Information Reception Provider	Transit Vehicle V2V Safety Provider
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement											Application Usage Agreement	Application Usage Agreement
Driver	Vehicle Usage Agreement		Expectation of Information Provision
Vehicle OBE Owner	Vehicle OBE Usage Agreement	Expectation of Information Provision			Expectation of Information Provision								Expectation of Data Provision
Roadway Owner					Service Delivery Agreement
RSE Owner			Expectation of Information Provision	Service Delivery Agreement		Operations Agreement	Information Exchange and Action Agreement				Application Usage Agreement		Expectation of Information Provision
RSE Operator					Operations Agreement
ITS Roadway Equipment Owner					Information Exchange and Action Agreement			Operations Agreement
ITS Roadway Operator							Operations Agreement
Transit Vehicle Operator												Expectation of Action	Vehicle Usage Agreement
Personal Pedestrian Safety Provider												Application Usage Agreement
RSE Intersection Management Provider					Application Usage Agreement
Traveler									Expectation of Action	Application Usage Agreement			Expectation of Data Provision
Transit Fleet Manager			Expectation of Data Provision		Expectation of Information Provision				Vehicle Usage Agreement			Expectation of Data Provision				Application Usage Agreement
Vehicle Basic Safety Provider	Application Usage Agreement
Vehicle Roadside Information Reception Provider	Application Usage Agreement
Transit Vehicle V2V Safety Provider													Application 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.
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.
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.)
ITS Roadway Equipment Owner	The entity that owns the Roadway ITS equipment.
ITS Roadway Operator	The entity that operates the Roadway ITS equipment.
Personal Pedestrian Safety 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 Pedestrian Safety 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 Pedestrian Safety 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.
Roadway Traffic Information Dissemination 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.
Roadway Traffic Information Dissemination 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.
Roadway Traffic Information Dissemination 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.
RSE Deployer	The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Intersection Management 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.
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 Traveler Information Communications 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 Traveler Information Communications 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 Traveler Information Communications 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 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 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 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.
Transit Vehicle V2V Safety 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 V2V Safety 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 V2V Safety 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.
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 Basic Safety 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 Basic Safety 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 Basic Safety 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.
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 Roadside Information Reception 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 Roadside Information Reception 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 Roadside Information Reception 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.
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 Development System	The system used in a backoffice environment to develop and test the field component of the application.
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.
ITS Field Component Development System	The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System	The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System	The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Equipment	'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
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 Pedestrian Safety	The "Personal Pedestrian Safety" application improves pedestrian safety by providing pedestrian location information to the infrastructure that can be used to avoid collisions involving pedestrians. The application may also alert the pedestrian of unsafe conditions, augmenting or extending information provided by signals and signs. The information provided and the user interface delivery mechanism (visual, audible, or haptic) can also be tailored to the needs of the user that is carrying or wearing the device that hosts the application.
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.
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.
Roadway Traffic Information Dissemination	"Roadway Traffic Information Dissemination" includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios.
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 Traveler Information Communications	"RSE Traveler Information Communications" includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles.
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 V2V Safety	"Transit Vehicle V2V Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to predict vehicle paths, and notifies the driver when the potential for an impending collision is detected. Information from on-board sensors (e.g., radars and image processing) are used to augment the V2V communications, if available. In addition to notifying the driver, control information can also be provided to support automated control functions that can avoid the collision. This object is similar to the "Vehicle Basic V2V Safety", but it accounts for crash scenarios that are unique to transit vehicles (e.g., Vehicle Turning Right in Front of Bus). It is also stop-aware since stop locations pose specific crash threats for transit vehicles. Finally, the detection and control algorithms, filters, and timing account for bus performance and risk profiles associated with remote vehicles that are unique to transit.
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 Basic Safety	"Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.
Vehicle Databus	The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
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 Roadside Information Reception	"Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information.

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.
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.
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 Data Provision	Expectation	An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
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 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.
Installation Agreement	Agreement	An agreement whereupon one entity installs an application component on a device controlled by another entity.
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 Agreement	Agreement	An agreement in which one entity maintains the operational status of a system 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.
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 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
1.1	Provide Traffic Surveillance	Collection
1.1.1	Process Sensor Data	Collection
1.1.1.6	Collect Vehicle Roadside Safety Data	Pspec	- RSE Traveler Information Communications
1.1.2	Process and Store Traffic Data	Collection
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Traveler Information Communications
1.2	Provide Device Control	Collection
1.2.7	Provide Roadside Control Facilities	Collection
1.2.7.1	Process Indicator Output Data for Roads	Pspec	- Roadway Traffic Information Dissemination
1.2.7.4	Process In-vehicle Signage Data	Pspec	- RSE Traveler Information Communications
1.2.7.5	Process Indicator Output Data for Freeways	Pspec	- Roadway Traffic Information Dissemination
1.2.7.7	Process Vehicle Safety and Environmental Data for Output	Pspec	- RSE Traveler Information Communications
1.2.7.9	Process Roadway Information Data	Pspec	- Roadway Traffic Information Dissemination
3.1	Monitor Vehicle Status	Collection
3.1.1	Produce Collision and Crash Avoidance Data	Pspec	- Vehicle Basic Safety
3.1.3	Process Vehicle On-board Data	Pspec	- Vehicle Roadside Information Reception - Vehicle Basic Safety
3.1.4	Communicate with Remote Vehicles	Pspec	- Vehicle Basic Safety
4.1	Operate Transit Vehicles and Facilities	Collection
4.1.1	Process On-Board Systems Data	Pspec	- Transit Vehicle V2V Safety
4.1.2	Determine Transit Vehicle Service Status	Pspec	- Transit Vehicle V2V Safety
4.1.3	Provide Transit Vehicle Location Data	Pspec	- Transit Vehicle V2V Safety
6.7	Provide Driver Personal Services	Collection
6.7.3	Provide Traveler Services in Vehicle	Collection
6.7.3.2	Provide Driver with Personal Travel Information	Pspec	- Vehicle Roadside Information Reception
6.7.3.3	Provide Driver Information Interface	Pspec	- Vehicle Roadside Information Reception - Vehicle Basic Safety
6.8	Provide Traveler Personal Services	Collection
6.8.2	Provide Traveler Personal Security	Collection
6.8.2.3	Monitor Pedestrian Safety Status	Pspec	- Personal Pedestrian Safety
6.8.3	Provide Traveler Services at Personal Devices	Collection
6.8.3.3	Provide Traveler Personal Interface	Pspec	- Personal Pedestrian Safety
6.8.3.6	Provide Personal Safety Messages	Pspec	- Personal Pedestrian Safety
9.2	Manage Roadway M&C Activities	Collection
9.2.3	Determine M&C Needs	Collection
9.2.3.8	Collect Connected Vehicle Field Equipment Status	Pspec	- RSE Traveler Information Communications

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Collect Vehicle Roadside Safety Data	vehicle_safety_input_data	Process Collected Vehicle Safety Data
Communicate with Remote Vehicles	safety_message_data_from_remote_vehicles	Process Vehicle On-board Data
Communicate with Remote Vehicles	intersection_infringement_from_remote_vehicle	Produce Collision and Crash Avoidance Data
Determine Transit Vehicle Service Status	transit_vehicle_status_for_signing	Provide Driver with Personal Travel Information
Monitor Pedestrian Safety Status	traveler_roadside_pedestrian_indicator	Collect Vehicle Roadside Safety Data
Monitor Pedestrian Safety Status	traveler_roadside_location_data	Collect Vehicle Roadside Safety Data
Monitor Pedestrian Safety Status	traveler_transit_location_data	Process On-Board Systems Data
Monitor Pedestrian Safety Status	traveler_transit_pedestrian_indicator	Process On-Board Systems Data
Monitor Pedestrian Safety Status	personal_alert_message	Provide Personal Safety Messages
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_freeways	Process Indicator Output Data for Freeways
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_roads	Process Indicator Output Data for Roads
Process Collected Vehicle Safety Data	vehicle_safety_data_indication	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_geometry_location_data	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_intersection_geometry_data	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Freeways	signage_traffic_metering_data_from_roadway	Process In-vehicle Signage Data
Process Indicator Output Data for Freeways	dms_traffic_metering_data_from_roadway	Process Roadway Information Data
Process Indicator Output Data for Freeways	traffic_metering_data_for_roadside	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_indication	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_timing	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_response_state	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_priority_preempt	Process Vehicle Safety and Environmental Data for Output
Process In-vehicle Signage Data	vehicle_sign_equip_status_for_m_and_c	Collect Connected Vehicle Field Equipment Status
Process In-vehicle Signage Data	transit_vehicle_signage_lanes_data	Determine Transit Vehicle Service Status
Process In-vehicle Signage Data	vehicle_signage_hri_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_individual_vehicle_speed	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_roadway_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_alert_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_evacuation_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_output_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_speed_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_barrier_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_emissions_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_traffic_data_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_traffic_metering_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_variable_speed_limit_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_zone_definition	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_zone_timing	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_weather_advisory	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_infrastructure_restriction_ahead	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_infrastructure_restriction_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_pedestrian_presence	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_intersection_infringement	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_rail_crossing_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_stop_sign_gap_assist	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_work_zone_intrusion	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_work_zone_information	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_intersection_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_queue_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_incident_work_zone	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_dynamic_lane_configuration	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_lane_closure_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_configuration_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_closure_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_diversion_data	Provide Driver 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_on_board_data	Provide Transit Vehicle Location Data
Process Roadway Information Data	dms_status_for_roadside	Collect Connected Vehicle Field Equipment Status
Process Roadway Information Data	dms_status_for_roadside	Process Vehicle Safety and Environmental Data for Output
Process Vehicle On-board Data	vehicle_roadside_location_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_speed_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_size_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_current_status_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	safety_message_data_for_remote_vehicles	Communicate with Remote Vehicles
Process Vehicle On-board Data	vehicle_ped_current_status_data	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_ped_location_data	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_ped_size_data	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_ped_speed_data	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_ped_device_identity	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_ped_time_data	Monitor Pedestrian Safety Status
Process Vehicle On-board Data	vehicle_roadside_control_event_data	Process Collected Vehicle Safety Data
Process Vehicle On-board Data	collision_data	Produce Collision and Crash Avoidance Data
Process Vehicle On-board Data	vehicle_status_details_for_broadcast	Provide Driver with Personal Travel Information
Process Vehicle On-board Data	vehicle_to_transit_current_status_data	Provide Transit Vehicle Location Data
Process Vehicle On-board Data	vehicle_to_transit_device_identity	Provide Transit Vehicle Location Data
Process Vehicle On-board Data	vehicle_to_transit_location_data	Provide Transit Vehicle Location Data
Process Vehicle On-board Data	vehicle_to_transit_size_data	Provide Transit Vehicle Location Data
Process Vehicle On-board Data	vehicle_to_transit_speed_data	Provide Transit Vehicle Location Data
Process Vehicle On-board Data	vehicle_to_transit_time_data	Provide Transit Vehicle Location Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_indication_to_transit_vehicle	Determine Transit Vehicle Service Status
Process Vehicle Safety and Environmental Data for Output	signal_phase_response_state_to_transit_vehicle	Determine Transit Vehicle Service Status
Process Vehicle Safety and Environmental Data for Output	signal_phase_timing_to_transit_vehicle	Determine Transit Vehicle Service Status
Process Vehicle Safety and Environmental Data for Output	roadside_pedestrian_crossing_data	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	roadside_intersection_details_to_pedestrians	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	roadside_intersection_lanes_to_pedestrians	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	signal_phase_indication_to_pedestrian	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	signal_phase_response_state_to_pedestrian	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	signal_phase_timing_to_pedestrian	Monitor Pedestrian Safety Status
Process Vehicle Safety and Environmental Data for Output	env_sensor_data_for_advisory_message	Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output	vehicle_safety_and_roadway_data	Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output	dms_data_from_roadside	Process Roadway Information Data
Process Vehicle Safety and Environmental Data for Output	dms_transit_vehicle_movement_message_from_roadside	Process Roadway Information Data
Process Vehicle Safety and Environmental Data for Output	roadside_safety_data_to_vehicle	Process Vehicle On-board Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_indication_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_timing_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_response_state_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	queue_warning_from_roadside	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	vehicle_env_sensor_data_output	Provide Driver with Personal Travel Information
Produce Collision and Crash Avoidance Data	intersection_infringement_for_remote_vehicle	Communicate with Remote Vehicles
Produce Collision and Crash Avoidance Data	position_warnings	Provide Driver with Personal Travel Information
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 Personal Safety Messages	personal_mobile_location_data	Collect Vehicle Roadside Safety Data
Provide Personal Safety Messages	personal_mobile_time_data	Collect Vehicle Roadside Safety Data
Provide Personal Safety Messages	personal_mobile_device_identity	Collect Vehicle Roadside Safety Data
Provide Personal Safety Messages	personal_mobile_device_identity_for_veh	Produce Collision and Crash Avoidance Data
Provide Personal Safety Messages	personal_mobile_location_data_for_veh	Produce Collision and Crash Avoidance Data
Provide Personal Safety Messages	personal_mobile_time_data_for_veh	Produce Collision and Crash Avoidance Data
Provide Transit Vehicle Location Data	tr_vehicle_roadside_current_status_data	Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data	tr_vehicle_roadside_location_data	Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data	tr_vehicle_roadside_size_data	Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data	tr_vehicle_roadside_speed_data	Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data	transit_roadside_path_prediction_data	Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data	transit_to_vehicle_current_status_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_device_identity	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_location_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_size_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_speed_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_time_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_to_vehicle_path_prediction_data	Communicate with Remote Vehicles
Provide Transit Vehicle Location Data	transit_vehicle_location_for_eta	Determine Transit Vehicle Service Status
Provide Transit Vehicle Location Data	transit_ped_current_status_data	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_device_identity	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_location_data	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_size_data	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_speed_data	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_time_data	Monitor Pedestrian Safety Status
Provide Transit Vehicle Location Data	transit_ped_path_prediction_data	Monitor Pedestrian Safety Status

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.
ITS Roadway Equipment	Field	'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
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.
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 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.
Vehicle Databus	Vehicle	The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
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 Pedestrian Safety	The "Personal Pedestrian Safety" application improves pedestrian safety by providing pedestrian location information to the infrastructure that can be used to avoid collisions involving pedestrians. The application may also alert the pedestrian of unsafe conditions, augmenting or extending information provided by signals and signs. The information provided and the user interface delivery mechanism (visual, audible, or haptic) can also be tailored to the needs of the user that is carrying or wearing the device that hosts the application.	Personal Information Device
Roadway Traffic Information Dissemination	"Roadway Traffic Information Dissemination" includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios.	ITS Roadway Equipment
RSE Traveler Information Communications	"RSE Traveler Information Communications" includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles.	Roadside Equipment
Transit Vehicle V2V Safety	"Transit Vehicle V2V Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to predict vehicle paths, and notifies the driver when the potential for an impending collision is detected. Information from on-board sensors (e.g., radars and image processing) are used to augment the V2V communications, if available. In addition to notifying the driver, control information can also be provided to support automated control functions that can avoid the collision. This object is similar to the "Vehicle Basic V2V Safety", but it accounts for crash scenarios that are unique to transit vehicles (e.g., Vehicle Turning Right in Front of Bus). It is also stop-aware since stop locations pose specific crash threats for transit vehicles. Finally, the detection and control algorithms, filters, and timing account for bus performance and risk profiles associated with remote vehicles that are unique to transit.	Transit Vehicle OBE
Vehicle Basic Safety	"Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.	Vehicle OBE
Vehicle Roadside Information Reception	"Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
driver information	Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
driver update information	Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
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.
host transit vehicle status	Information provided to the Connected Vehicle on-board equipment from other systems on the Transit Vehicle Platform.
host vehicle status	Information provided to the connected vehicle on-board equipment from other systems on the vehicle platform. This includes data from on-board sensors, the current status of the powertrain, steering, and braking systems, and status of safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the Connected Vehicle environment.
personal location	The current location (latitude, longitude, and elevation) reported by the personal information device
roadway information system data	Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.
roadway information system status	Current operating status of dynamic message signs, highway advisory radios, or other configurable field equipment that provides dynamic information to the driver.
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.
vehicle location and motion	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
vehicle path prediction	The predicted future vehicle path of travel. This flow includes an indication of the future positions of the transmitting vehicle that can be used by receiving vehicles to enhance in-lane and out-of-lane threat classification.
vehicle signage data	In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, and warnings).

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	ITS Roadway Equipment	Driver	driver information
	ITS Roadway Equipment	Roadside Equipment	roadway information system status
	Personal Information Device	Transit Vehicle OBE	personal location
None: Human interface	Personal Information Device	Traveler	traveler interface updates
	Roadside Equipment	ITS Roadway Equipment	roadway information system data
	Roadside Equipment	Vehicle OBE	vehicle signage data
	Transit Vehicle Databus	Transit Vehicle OBE	host transit vehicle status
None: Human interface	Transit Vehicle OBE	Transit Vehicle Operator	transit vehicle operator display
	Transit Vehicle OBE	Roadside Equipment	vehicle location and motion
	Transit Vehicle OBE	Vehicle OBE	vehicle location and motion
	Transit Vehicle OBE	Personal Information Device	vehicle location and motion
	Transit Vehicle OBE	Vehicle OBE	vehicle path prediction
	Transit Vehicle OBE	Personal Information Device	vehicle path prediction
	Transit Vehicle OBE	Roadside Equipment	vehicle path prediction
None: Human interface	Transit Vehicle Operator	Transit Vehicle OBE	transit vehicle operator input
None: Human interface	Traveler	Personal Information Device	traveler input
	Vehicle Databus	Vehicle OBE	host vehicle status
	Vehicle OBE	Vehicle Databus	driver update information
None: Human interface	Vehicle OBE	Driver	driver updates
	Vehicle OBE	Transit Vehicle OBE	vehicle location and motion

Requirements

Need		Requirement
N3.100	Transit Vehicle at Station/Stop Warnings (TVSSW) needs to inform Vehicles of the presence and behavior of a nearby Transit Vehicle to help prevent collisions.	3.197	Transit Vehicle at Station/Stop Warnings (TVSSW) shall determine the predicted trajectories of transit vehicles.
N3.100		3.198	TVSSW shall inform vehicles of the predicted trajectories of nearby transit vehicles.
N3.101	TVSSW needs to determine the location of transit vehicles so that it may inform other vehicles of the transit vehicles' location and behavior.	3.199	TVSSW shall be able to acquire vehicle position information.
N3.102	TVSSW needs to determine the behavior of transit vehicles so that it can communicate that information to other vehicles and pedestrians.	3.200	TVSSW shall be able to acquire vehicle trajectory information.
		3.201	TVSSW shall be able to acquire transit vehicle behavior broadcasts (pulling out, about to stop etc.).
		3.202	TVSSW shall broadcast host transit vehicle behavioral information (pulling out, about to stop, etc.)
N3.103	TVSSW needs to inform Pedestrians of the nearby Presence and Behavior of a Transit Vehicle to help prevent collisions.	3.203	TVSSW shall acquire the locations of transit vehicle stops.
		3.204	TVSSW shall inform roadside devices near transit vehicle stops of the nearby presence and behavior of transit vehicles.
		3.205	TVSSW shall be able to receive pedestrian location information from pedestrians near transit vehicle stops.
		3.206	TVSSW shall inform pedestrians near transit vehicle stops of the nearby presence and behavior of transit vehicles.

Related Sources

ConOps for Transit Connected Vehicle, Draft, 3/31/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.