Type: Safety
Groups:- Transit Safety
Vehicle Turning Right in Front of a Transit Vehicle
The Vehicle Turning Right in Front of a Transit Vehicle (VTRFTV) application determines the movement of vehicles near to a transit vehicle stopped at a transit stop and provides an indication to the transit vehicle operator that a nearby vehicle is pulling in front of the transit vehicle to make a right turn. This application will help the transit vehicle determine if the area in front of it will not be occupied as it begins to pull away from a transit stop.
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
Business Interaction Matrix:
Vehicle Turning Right in Front of a Transit Vehicle Operations Stage | ||||
---|---|---|---|---|
Transit Vehicle Operator | Remote Vehicle OBE Owner | Transit Fleet Manager | Transit Vehicle V2V Safety Provider | |
Transit Vehicle Operator | Presumption of Correct Operation | Vehicle Usage Agreement | ||
Remote Vehicle OBE Owner | Presumption of Correct Operation | Expectation of Data Provision | ||
Transit Fleet Manager | Vehicle Usage Agreement | Expectation of Data Provision | 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. |
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. |
Remote Vehicle OBE Owner | The owner of the Remote Vehicle OBE |
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. |
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. |
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. |
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. |
Remote Vehicle OBEs | 'Remote Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. In CVRIA, this object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA. |
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. |
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 Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
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. |
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. |
Includes | Includes | Indicates that one component is entirely contained within another component. |
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. |
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. |
Presumption of Correct Operation | Expectation | The assumption made by one party that another party operates their device in a similar and correct fashion. Specific to devices in the transportation environment, this assumption is relevant when devices interact, where one party's device receives information from another's. The operator of the device implicitly trusts that the other device is operating according to a similar set of governing rules as its device. |
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 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 |
Includes Data Flows:
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
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Remote Vehicle OBEs | Vehicle | 'Remote Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. In CVRIA, this object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA. |
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. |
Includes Application Objects:
Application Object | Description | Physical Object |
---|---|---|
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 |
Includes Information Flows:
Information Flow | Description |
---|---|
collision warning information | Information provided to support computer-based intervention of vehicle controls. Analogous to driver warnings, these are warnings issued to on-board control systems of an impending collision or other situation detected by the Vehicle OBE that may require control intervention. |
host transit vehicle status | Information provided to the Connected Vehicle on-board equipment from other systems on the Transit Vehicle Platform. |
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. |
vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. |
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 | Remote Vehicle OBEs | Transit Vehicle OBE | vehicle location and motion | Transit Vehicle Databus | Transit Vehicle OBE | host transit vehicle status | Transit Vehicle OBE | Transit Vehicle Databus | collision warning information | None: Human interface | Transit Vehicle OBE | Transit Vehicle Operator | transit vehicle operator display | Transit Vehicle OBE | Remote Vehicle OBEs | vehicle location and motion | None: Human interface | Transit Vehicle Operator | Transit Vehicle OBE | transit vehicle operator input |
---|
Requirements
Need | Requirement | ||
---|---|---|---|
N3.091 | Vehicle Turning Right in Front of a Transit Vehicle (VTRFTV) needs to inform Vehicles of the presence and behavior of a nearby Transit Vehicle to help prevent collisions. | 3.189 | Vehicle Turning Right in Front of a Transit Vehicle (VTRFTV) shall be able to acquire transit vehicle behavior information. |
3.190 | VTRFTV shall broadcast host transit vehicle behavioral information (pulling out, about to stop, etc.) | ||
N3.092 | VTRFTV needs to determine the location of transit vehicles so that it may inform other vehicles of the transit vehicles' location and behavior. | 3.191 | VTRFTV shall be able to acquire transit vehicle trajectory information. |
N3.093 | VTRFTV needs to determine the behavior of transit vehicles so that it can communicate that information to other vehicles. | 3.192 | VTRFTV shall determine the behavior of the host transit vehicle. |
N3.094 | VTRFTV needs to inform Vehicles of the presence of a nearby Transit Vehicle involved in a collision. | 3.193 | VTRFTV shall inform vehicles of the presence of a transit vehicle involved in a collision. |
3.194 | VTRFTV shall determine the location of the transit vehicle. | ||
N3.095 | VTRFTV needs to determine if a transit vehicle has been involved in a collision so that it may communicate that information to vehicles near the transit vehicle. | 3.195 | VTRFTV shall receive on-board vehicle status information describing transit vehicle performance. |
3.196 | VTRFTV shall analyze on-board vehicle status information and determine from that information if the transit vehicle has been involved in a collision. | ||
N3.096 | VTRFTV needs the locations, speed and heading of vehicles nearby a transit vehicle so that it can determine if those vehicles pose a risk of crash to the transit vehicle. | 3.185 | VTRFTV shall be able to acquire vehicle trajectory information. |
N3.097 | VTRFTV needs to determine the possibility that a nearby vehicle may cross in front of a transit vehicle in such a way as to cause an crash. | 3.186 | VTRFTV shall analyze vehicle trajectory and transit vehicle trajectory information to determine if there is a risk of crash between the transit vehicle and another vehicle. |
N3.098 | VTRFTV needs the transit vehicle's location, speed and heading. | 3.187 | VTRFTV shall acquire transit vehicle trajectory information. |
N3.099 | VTRFTV needs to warn the transit vehicle driver of a potential collision (caused by another vehicle moving in front of the transit vehicle and slowing to make a turn). | 3.188 | VTRFTV shall warn the transit vehicle operator of a potential collision. |
Related Sources
- Transit Safety Retrofit Package Development Applications Requirements Document, Final, 5/28/2014
- Transit Safety Retrofit Package Development Architecture and Design Specifications, Final, 5/19/2014
- Transit Safety Retrofit Package Development TRP Concept of Operations, Final, 5/28/2014
- ConOps for Transit Connected Vehicle, Draft, 3/31/2012
- 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. |