< < PT11 : PT12 : PT13 > >

PT12: Transit Vehicle at Station/Stop Warnings

The Transit Vehicle at Station/Stop Warnings service package informs nearby vehicles of the presence of a transit vehicle at a station or stop. The service package also indicates the intention of the transit vehicle in terms of pulling into or out of a station/stop. The transit vehicle also exchanges information with nearby Personal Information Devices so that travelers in the vicinity of the transit vehicle are aware of imminent transit vehicle movement and the vehicle driver is aware of nearby pedestrians and other vulnerable road users.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Transit Vehicle Maintainer Basic Transit Vehicle Maintains
Basic Transit Vehicle Manager Basic Transit Vehicle Manages
Basic Transit Vehicle Manager Transit Vehicle Operator System Usage Agreement
Basic Transit Vehicle Owner Basic Transit Vehicle Maintainer System Maintenance Agreement
Basic Transit Vehicle Owner Basic Transit Vehicle Manager Operations Agreement
Basic Transit Vehicle Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Basic Transit Vehicle Owner Transit Vehicle OBE Owner Expectation of Data Provision
Basic Transit Vehicle Owner Transit Vehicle OBE User Service Usage Agreement
Basic Transit Vehicle Owner Transit Vehicle Operator Application Usage Agreement
Basic Transit Vehicle Owner Transit Vehicle Operator Vehicle Operating Agreement
Basic Transit Vehicle Supplier Basic Transit Vehicle Owner Warranty
Basic Vehicle Maintainer Basic Vehicle Maintains
Basic Vehicle Manager Basic Vehicle Manages
Basic Vehicle Manager Driver System Usage Agreement
Basic Vehicle Owner Basic Vehicle Maintainer System Maintenance Agreement
Basic Vehicle Owner Basic Vehicle Manager Operations Agreement
Basic Vehicle Owner Driver Application Usage Agreement
Basic Vehicle Owner Driver Vehicle Operating Agreement
Basic Vehicle Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Basic Vehicle Owner Vehicle Owner Expectation of Data Provision
Basic Vehicle Owner Vehicle User Service Usage Agreement
Basic Vehicle Supplier Basic Vehicle Owner Warranty
Connected Vehicle Roadside Equipment Maintainer Connected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Driver Application Usage Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Vehicle User Service Usage Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Driver Basic Vehicle Operates
Driver Vehicle Operates
ITS Roadway Equipment Maintainer ITS Roadway Equipment Maintains
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment Supplier ITS Roadway Equipment Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Manager Traveler System Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Transit Vehicle OBE Owner Information Provision and Action Agreement
Personal Information Device Owner Transit Vehicle OBE User Service Usage Agreement
Personal Information Device Owner Transit Vehicle Operator Application Usage Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Transit Management Center Maintainer System Maintenance Agreement
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Transit Vehicle OBE Owner Information Provision Agreement
Transit Management Center Owner Transit Vehicle OBE User Service Usage Agreement
Transit Management Center Owner Transit Vehicle Operator Application Usage Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transit Vehicle OBE Maintainer Transit Vehicle OBE Maintains
Transit Vehicle OBE Manager Transit Vehicle OBE Manages
Transit Vehicle OBE Manager Transit Vehicle Operator System Usage Agreement
Transit Vehicle OBE Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Transit Vehicle OBE Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Transit Vehicle OBE Owner Driver Application Usage Agreement
Transit Vehicle OBE Owner Driver Vehicle Operating Agreement
Transit Vehicle OBE Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE Owner Personal Information Device Owner Expectation of Data Provision
Transit Vehicle OBE Owner Personal Information Device User Service Usage Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Maintainer System Maintenance Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Manager Operations Agreement
Transit Vehicle OBE Owner Traveler Application Usage Agreement
Transit Vehicle OBE Owner Traveler Vehicle Operating Agreement
Transit Vehicle OBE Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE Owner Vehicle Owner Expectation of Data Provision
Transit Vehicle OBE Owner Vehicle User Service Usage Agreement
Transit Vehicle OBE Supplier Transit Vehicle OBE Owner Warranty
Transit Vehicle Operator Basic Transit Vehicle Operates
Transit Vehicle Operator Transit Vehicle OBE Operates
Traveler Personal Information Device Operates
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Basic Vehicle Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Basic Vehicle Owner Expectation of Data Provision
Vehicle Owner Basic Vehicle User Service Usage Agreement
Vehicle Owner Driver Application Usage Agreement
Vehicle Owner Driver Vehicle Operating Agreement
Vehicle Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Transit Vehicle OBE Owner Expectation of Data Provision
Vehicle Owner Transit Vehicle OBE User Service Usage Agreement
Vehicle Owner Transit Vehicle Operator Application Usage Agreement
Vehicle Owner Transit Vehicle Operator Vehicle Operating Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Traveler Information Communications 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.2.7.4 Process In-vehicle Signage Data
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
1.5.10 Collect Vehicle Emissions Messages
2.8.4.6 Exchange Border Clearance Roadside Information
6.7.3.5 Provide Short Range Traveler Information
9.2.3.8 Collect Connected Vehicle Field Equipment Status
9.3.3.5 Manage Speeds at Roadside
ITS Roadway Equipment Roadway Traffic Information Dissemination 1.2.7.1 Process Indicator Output Data for Roads
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.5 Process Indicator Output Data for Freeways
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.2.7.9 Process Roadway Information Data
Personal Information Device Personal Pedestrian Safety 6.8.1.3 Process Personal Portable Device Location Data
6.8.1.4 Update Traveler Navigable Map Database
6.8.2.3 Monitor Pedestrian Safety Status
6.8.2.4 Provide Pedestrian Personal Interface
6.8.3.3 Provide Traveler Personal Interface
6.8.3.6 Provide Personal Safety Messages
Transit Management Center Transit Center Fixed-Route Operations 4.1.5.1 Manage Transit Vehicle Operations
4.1.5.2 Manage Transit Vehicle Deviations
4.2.1.1 Generate Transit Routes
4.2.1.2 Generate Transit Schedules
4.2.1.3 Produce Transit Service Data for External Use
4.2.1.4 Provide Transit Operations Personnel Interface for Services Generation
4.2.1.5 Manage Transit Operational Data Store
4.2.1.6 Produce Transit Service Data for Manage Transit Use
4.2.2 Provide Transit Plans Store Interface
4.5.1 Assess Transit Vehicle Operator Performance
4.5.2 Assess Transit Vehicle Operator Availability
4.5.3 Access Transit Vehicle Operator Cost Effectiveness
4.5.4 Assess Transit Vehicle Operator Eligibility
4.5.5 Generate Transit Vehicle Operator Route Assignments
4.5.6 Report Transit Vehicle Operator Information
4.5.7 Provide Transit Vehicle Operator Information Store Interface
Transit Vehicle OBE Transit Vehicle Pedestrian Safety 4.1.3 Provide Transit Vehicle Location Data
Transit Vehicle V2V Safety 4.1.1 Process On-Board Systems Data
4.1.2 Determine Transit Vehicle Service Status
4.1.3 Provide Transit Vehicle Location Data
Vehicle Vehicle Basic Safety Communication 3.1.1 Produce Collision and Crash Avoidance Data
3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.1.4 Communicate with Remote Vehicles
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
3.2.3.2 Manage Platoon Following
3.2.3.2 Manage Platoon Following
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.5 Process Vehicle Sensor Data
3.2.3.5 Process Vehicle Sensor Data
3.2.4 Process Sensor Data for Automatic Vehicle Operations
3.2.4 Process Sensor Data for Automatic Vehicle Operations
6.7.1.2 Provide Driver Guidance Interface
6.7.1.2 Provide Driver Guidance Interface
6.7.1.3 Process Vehicle Location Data
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.3 Provide Driver Information Interface
6.7.3.3 Provide Driver Information Interface
Vehicle Traveler Information Reception 3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.2.3.3 Process Data for Vehicle Actuators
6.7.1.2 Provide Driver Guidance Interface
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Get Driver Personal Request
6.7.3.2 Provide Driver with Personal Travel Information
6.7.3.3 Provide Driver Information Interface
7.1.4 Provide Driver Toll Payment Interface

Physical

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
Basic Transit Vehicle Vehicle The 'Basic Transit Vehicle' represents the transit vehicle that hosts the on-board equipment that provides ITS functions. It includes a specialized and extended 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. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers.
Basic Vehicle Vehicle 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV 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.
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. 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 Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
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. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities 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 Personal The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
Personal Pedestrian Safety 'Personal Pedestrian Safety' improves pedestrian, cyclist, and other vulnerable road user safety by providing personal location information to the infrastructure that can be used to avoid collisions involving vulnerable road users. It may also alert the vulnerable road user 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. Connected Vehicle Roadside Equipment
Transit Center Fixed-Route Operations 'Transit Center Fixed-Route Operations' manages fixed route transit operations. It supports creation of schedules, blocks and runs for fixed and flexible route transit services. It allows fixed-route and flexible-route transit services to disseminate schedules and automatically updates customer service operator systems with the most current schedule information. It also supports automated dispatch of transit vehicles. Current vehicle schedule adherence and optimum scenarios for schedule adjustment are also provided. It also receives and processes transit vehicle loading data. Transit Management Center
Transit Vehicle Pedestrian Safety 'Transit Vehicle Pedestrian Safety' exchanges current location and motion information with pedestrian-carried devices in the vicinity and uses that information to warn the driver of pedestrians in the vehicle's path. Information from on-board sensors (e.g., radars and image processing) are used to augment the short range 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. Transit Vehicle OBE
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 Communication 'Vehicle Basic Safety Communication' 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
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' 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
Vehicle Traveler Information Reception 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers 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

Includes Information Flows:

Information Flow Description
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
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 ITS on-board equipment from other systems on the Transit Vehicle Platform.
host vehicle status Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other 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 ITS environment.
personal location The current location (latitude, longitude, and elevation) reported by the personal information or safety device
roadway dynamic signage data Information used to initialize, configure, and control dynamic message signs. 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 devices.
roadway dynamic signage status Current operating status of dynamic message signs.
transit stop locations The current geographic location and dimensions of transit stops. This flow may also include the road geometry in the vicinity of the stops as needed to support transit vehicle safety applications when arriving at or departing from stops.
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 support coordinated driving maneuvers and 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., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings).

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve security
D. Increase the accessibility and mobility of people and for freight; Reduce congestion

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities
Transit Operations and Management: Safety

Associated Objectives and Performance Measures

Objective Performance Measure
Decrease the number of personal safety incidents by X percent within Y years. Number of reported personal safety incidents.
Increase personal safety ratings by X percent within Y years. Personal safety and customer service ratings.
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y. Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y. Number of serious injuries

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle. Personal Pedestrian Safety 07 The personal traveler interface shall provide the traveler with an indication that a nearby transit vehicle is preparing to leave a station or stop.
Roadway Traffic Information Dissemination 01 The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
RSE Traveler Information Communications 04 The field element shall return system operational status to the controlling center.
13 The field element shall provide data about transit vehicle movement to approaching vehicles
Transit Center Fixed-Route Operations 01 The center shall generate transit routes and schedules based on such factors as parameters input by the system operator, road network conditions, incident information, operational data on current routes and schedules, and digitized map data.
04 The center shall dispatch fixed route or flexible route transit vehicles.
Transit Vehicle Pedestrian Safety 01 The transit vehicle shall determine if pedestrians are near a transit vehicle.
02 The transit vehicle shall determine if pedestrians are at risk of crash due to proximity of transit vehicle.
04 The transit vehicle shall collect pedestrian presence information from equipped personal devices.
07 The transit vehicle shall send vehicle identification information to nearby equipped personal devices.
10 The vehicle shall determine the predicted trajectories of transit vehicles.
Transit Vehicle V2V Safety 01 The transit vehicle shall exchange current vehicle location and motion information with other vehicles in the vicinity.
02 The transit vehicle shall provide to other vehicles an indication of its intent to leave a transit stop.
03 The transit vehicle shall provide a warning to the transit vehicle operator if a nearby vehicle is a collision threat as the transit vehicle prepares to leave a stop or station.
Vehicle Basic Safety Communication 06 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Traveler Information Reception 02 The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special information.
03 The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors).
04 The vehicle shall store a translation table for road sign and message templates used for in-vehicle display.
05 The vehicle shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
06 The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information
07 The vehicle shall be capable of providing to the driver an audible presentation of static sign information or dynamic roadway conditions information

Related Sources

Document Name Version Publication Date
ConOps for Transit Connected Vehicle Draft 3/31/2012


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Basic Transit Vehicle  
Basic Vehicle  
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Personal Information Device Not Applicable High Moderate Class 3
Transit Management Center Low Moderate Moderate Class 1
Transit Vehicle OBE Low High Moderate Class 3
Vehicle Low High Moderate Class 3



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

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Basic Transit Vehicle Transit Vehicle OBE host transit vehicle status Moderate Moderate Moderate
This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. DISC THEA believes this to be LOW: "sensor data is not confidential; harm should not come from seeing status." This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. DISC: THEA believes this should be HIGH: "sensor data needs to be accurate and should not be tampered with." This information would need to be available immediately for the application to work.DISC: THEA believes this should be HIGH: "sensor data must be consistently available to feed BSMs broadcast at 10Hz, notifications, etc.."
Basic Vehicle Vehicle host vehicle status Low Moderate High
Unlikely that this includes any information that could be used against the originator. This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety.
Connected Vehicle Roadside Equipment ITS Roadway Equipment roadway dynamic signage data Moderate Moderate Moderate
Device control information should not be available, as those with criminal intent may use this information toward their own ends. Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts.
Connected Vehicle Roadside Equipment Vehicle vehicle signage data Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means. These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues.
Driver Vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
ITS Roadway Equipment Connected Vehicle Roadside Equipment roadway dynamic signage status Moderate Moderate Moderate
Device status information should not be available, as those with criminal intent may use this information toward their own ends. Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances.
ITS Roadway Equipment Driver driver information Not Applicable High Moderate
This data is sent to all drivers and is also directly observable, by design. This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it's wrong, accidents could happen. If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections.
Personal Information Device Transit Vehicle OBE personal location Not Applicable High Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. An incorrect location message could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity. There are other visual indicators about the geofenced areas. PID users in dynamic environments (incident and work zones) should know when they are leaving a geofenced area. As long as they remain in the geofenced area, this information is not as necessary. Not all pedestrians will carry a personal information device, and the system should be able to operate without this information.
Personal Information Device Traveler traveler interface updates Not Applicable Moderate Moderate
Personalized data that includes directions and guidance for an individual, but eventually evident anyway. Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Transit Management Center Transit Vehicle OBE transit stop locations Low Moderate Moderate
This information is not sensitive. It is generally made public, to support transit system functionality. This information is most necessary to support safety use cases surrounding stop locations. If this information is inaccurate or unavailable, those use cases may not function correctly, decreasing safety. This information is most necessary to support safety use cases surrounding stop locations. If this information is inaccurate or unavailable, those use cases may not function correctly, decreasing safety.
Transit Vehicle OBE Connected Vehicle Roadside Equipment vehicle path prediction Not Applicable High Moderate
This is intended for broadcast. Path prediction is intended for collision avoidance applications, which have high integrity requirements to avoid potentially catastrophic consequences. Path prediction is intended for collision avoidance applications, which ideally would have HIGH availability requirements, but given the constraints of the wireless medium are reduced to MODERATE.
Transit Vehicle OBE Personal Information Device vehicle path prediction Not Applicable High Moderate
This is intended for broadcast. Path prediction is intended for collision avoidance applications, which have high integrity requirements to avoid potentially catastrophic consequences. Path prediction is intended for collision avoidance applications, which ideally would have HIGH availability requirements, but given the constraints of the wireless medium are reduced to MODERATE.
Transit Vehicle OBE Transit Vehicle Operator transit vehicle operator display Low Moderate Low
This should not include any sensitive information. It would be possible for a person standing behind the driver to observe the information transmitted. Some minimal guarantee of data integrity is necessary for all C-ITS flows. This entire application should not directly affect the drivers driving habits. The operator should still be slowing and stopping at yellow or red lights, along with observing all other driving regulations. DISC: Original V2I analysis classified this as LOW. Even if the operator is not made aware of the signal preemption, the system should still operate correctly. The operator should be using the traffic lights to influence their decision about whether or not to stop, not the display.
Transit Vehicle Operator Transit Vehicle OBE transit vehicle operator input Low Moderate Low
This information is transmitted through systems on board the Transit Vehicle. Even if the vehicle were compromised and these communications monitored, most of this information is directly observable. Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this is compromised, it could result in an incorrect signal priority request, which has minimal impact. DISC: Original V2I analysis classified this as LOW. A delay in reporting this may result in a signal priority request not going through, which has minimal impact.
Traveler Personal Information Device traveler input Not Applicable Moderate Low
This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Vehicle Basic Vehicle driver update information Low Moderate Moderate
This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
CTI 4001 RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment
ITE ATC Advanced Transportation Controller ITS Roadway Equipment
ITE ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
ITE ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
NEMA TS2 Traffic Controller Assemblies Traffic Controller Assemblies with NTCIP Requirements ITS Roadway Equipment
NEMA TS4 Hardware Standards for DMS Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements ITS Roadway Equipment




System Requirements

System Requirement Need
001 The system shall generate transit routes and schedules based on such factors as parameters input by the system operator, road network conditions, incident information, operational data on current routes and schedules, and digitized map data. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
002 The system shall dispatch fixed route or flexible route transit vehicles. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
003 The system shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle r 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
004 The system shall return system operational status to the controlling center. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
005 The system shall provide data about transit vehicle movement to approaching vehicles 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
006 The system shall provide the traveler with an indication that a nearby transit vehicle is preparing to leave a station or stop. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
007 The system shall determine if pedestrians are near a transit vehicle. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
008 The system shall determine if pedestrians are at risk of crash due to proximity of transit vehicle. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
009 The system shall collect pedestrian presence information from equipped personal devices. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
010 The system shall send vehicle identification information to nearby equipped personal devices. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
011 The system shall determine the predicted trajectories of transit vehicles. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
012 The system shall exchange current vehicle location and motion information with other vehicles in the vicinity 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
013 The system shall provide to other vehicles an indication of its intent to leave a transit stop. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
014 The system shall provide a warning to the transit vehicle operator if a nearby vehicle is a collision threat as the transit vehicle prepares to leave a stop or station. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
015 The system shall exchange location and motion information with roadside equipment and nearby vehicles. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
016 The system shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special i 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
017 The system shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
018 The system shall store a translation table for road sign and message templates used for in-vehicle display. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
019 The system shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
020 The system shall present to the driver a visual display of static sign information or dynamic roadway conditions information 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.
021 The system shall provide to the driver an audible presentation of static sign information or dynamic roadway conditions information 01 Transit Operations needs to be able to alert other vehicles that a transit vehicle is preparing to leave a station or stop in order to reduce risk of accidents with the departing transit vehicle.