< < VS10 : VS11 : VS12 > >

VS11: Oversize Vehicle Warning

This service package uses external measurements taken by the roadside infrastructure, and transmitted to the vehicle, to support in-vehicle determination of whether an alert/warning is necessary. Specifically, the infrastructure data equipment detects and measures the approaching vehicle's height and width. The infrastructure component of the service package transmits the vehicle measurements, along with bridge, overpass, or tunnel geometry, to the oversize vehicle. The vehicle application utilizes this data to determine whether the vehicle can clear the bridge or tunnel. If deemed necessary, the driver is alerted to the impending low height and/or narrow horizontal clearance bridge or tunnel prior to a decision point, enabling the vehicle to reroute and avoid a collision. If the driver ignores the alert and continues along the route, the vehicle will generate a warning indicating an impending collision at a point near the bridge or tunnel approach. To support unequipped vehicles the infrastructure will display warning or reroute information when the measurements indicate that a vehicle does not have adequate height or width clearance. This service package can be expanded to consider weight as well as height and width.

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 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 Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center 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 Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Traffic Management Center User Service Usage Agreement
ITS Roadway Equipment Supplier ITS Roadway Equipment Owner Warranty
Maint and Constr Management Center Maintainer Maint and Constr Management Center Maintains
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Maint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Traffic Management Center Owner Information Provision Agreement
Maint and Constr Management Center Owner Traffic Management Center User Service Usage Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Traffic Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Traffic Management Center Owner ITS Roadway Equipment User Service Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Vehicle Characteristics Maintainer Vehicle Characteristics Maintains
Vehicle Characteristics Manager Vehicle Characteristics Manages
Vehicle Characteristics Owner Vehicle Characteristics Maintainer System Maintenance Agreement
Vehicle Characteristics Owner Vehicle Characteristics Manager Operations Agreement
Vehicle Characteristics Supplier Vehicle Characteristics Owner Warranty
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 Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Vehicle Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Vehicle Owner Driver Application Usage Agreement
Vehicle Owner Driver Vehicle Operating Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

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 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 (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. 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.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
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.
Vehicle Characteristics Vehicle 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management.

Includes Functional Objects:

Functional Object Description Physical Object
MCM Work Activity Coordination 'MCM Work Activity Coordination' disseminates work activity schedules and current asset restrictions to other agencies. Work schedules are coordinated with operating agencies, factoring in the needs and activities of other agencies and adjacent jurisdictions. Work schedules are also distributed to Transportation Information Centers for dissemination to the traveling public. Maint and Constr Management Center
Roadway Restriction Monitoring and Warning 'Roadway Restriction Monitoring and Warning' measures the size and weight of passing vehicles and displays warnings to vehicles if the size exceeds the current infrastructure restrictions. The measured vehicle dimensions are also made available to other applications. ITS Roadway Equipment
RSE Infrastructure Restriction Warning 'RSE Infrastructure Restriction Warning' uses short range communications to warn vehicles of infrastructure dimensional and weight restrictions. Connected Vehicle Roadside Equipment
TMC Infrastructure Restriction Warning 'TMC Infrastructure Restriction Warning' controls and monitors RSEs that support Infrastructure Restriction Warnings. It configures the RSEs to define tunnel/bridge geometry and design and temporary size and weight restrictions. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel. Traffic Management Center
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
current infrastructure restrictions Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
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 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.
infrastructure restriction warning Vehicle size (height, width, length) and weight as measured by infrastructure sensors and the infrastructure restriction warning message currently displayed on roadside signs.
infrastructure restriction warning control Information used to configure and control infrastructure-based sensors that measure the size and weight of passing vehicles and associated signage that provides infrastructure restriction advisories and warnings to drivers.
infrastructure restriction warning info Roadway configuration data and warning parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. Configuration data includes facility design height, width, and weight restrictions, including special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
infrastructure restriction warning notification Notification to vehicle on-board equipment (OBE) that includes vehicle size (height, width, length) and weight as measured by infrastructure sensors, current infrastructure size and weight restrictions, and infrastructure restriction warning message(s) currently displayed on roadside signs.
infrastructure restriction warning status Infrastructure restriction warning application status reported by field equipment. This includes current operational state and status of the field equipment and a record of measured vehicle dimensions and alerts and warnings issued.
vehicle characteristics The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles.
vehicle profile Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
G. Promote efficient system management and operation; Improve efficiency

Associated Objective Categories

Objective Category
Freeway Management: Efficiency
Safety: Vehicle Crashes and Fatalities
System Efficiency: Travel Time

Associated Objectives and Performance Measures

Objective Performance Measure
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driver inattention and distraction
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driving while intoxicated
Reduce crashes due to unexpected congestion Number of crashes and fatalities related to unexpected congestion
Reduce crashes due to unsafe drivers, vehicles and cargo on the transportation system Number of crashes and fatalities due to commercial vehicle safety violations
Reduce the number of person hours (or vehicle hours) of delay experienced by travelers on the freeway system. Hours of delay (vehicle-hours or person-hours).
Reduce the number of person hours (or vehicle hours) of delay experienced by travelers on the freeway system. Hours of delay per capita or driver.
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the share of freeway miles at Level of Service (LOS) X by Y by year Z. Miles at LOS X or V/C > 1.0 (or other threshold).
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 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 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action. Roadway Restriction Monitoring and Warning 02 The field element shall display warnings to vehicles if the size exceeds the current infrastructure restrictions.
04 The field element shall send weight and size measurements as well as vehicle warning to the roadside equipment for transmission to connected vehicles.
RSE Infrastructure Restriction Warning 01 The roadside equipment shall provide infrastructure restriction warnings to connected vehicles.
TMC Infrastructure Restriction Warning 01 The center shall provide infrastructure restriction information, including temporary size and weight restrictions, to connected vehicles.
02 The center shall provide infrastructure restriction information, including temporary size and weight restrictions, to drivers.
04 The center shall monitor the traffic approaching a size-restricted roadway or tunnel.
05 The center shall provide warnings to connected vehicles if the measured height or width exceeds the dimensions for safe passage through the roadway or tunnel.
Vehicle Traveler Information Reception 11 The vehicle shall warn the driver of a vehicle whose weight exceeds the weight limit for a bridge or roadway sufficiently before entering the bridge or roadway so that the driver may take action to avoid going on the road segment for which the vehicle is overweight.
21 The vehicle shall receive the infrastructure size and weight restrictions warning messages.
02 Traffic Operations needs to be able to determine if a vehicle exceeds the height or weight restrictions of a tunnel, bridge, overpass, or section of roadway in order to provide warning to the vehicle or driver. Roadway Restriction Monitoring and Warning 01 The field element shall measure the weight, height and width of passing vehicles.
03 The field element shall send weight and size measurements to the controlling center.
TMC Infrastructure Restriction Warning 03 The center shall use infrastructure measurements of vehicle characteristics to determine if a vehicle exceeds the roadway or tunnel dimensions.
Vehicle Traveler Information Reception 12 The vehicle shall warn the driver of a potential crash due to overheight/overwidth, sufficiently before the potential crash's occurrence that the driver may take action to avoid the crash.
03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations. MCM Work Activity Coordination 04 The center shall collect and disseminate asset restriction information levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
Vehicle Traveler Information Reception 13 The vehicle shall calculate whether or not the vehicle is at risk of crash by entering the size-restricted roadway.
14 The vehicle shall calculate whether or not the vehicle is at risk of entering the weight-restricted roadway.
15 The vehicle shall determine the host vehicle's weight.
16 The vehicle shall determine the host vehicle's physical size characteristics (height, width).
17 The vehicle shall determine the roadway's size characteristics (clearance height, width, geometry).
18 The vehicle shall determine the location of the vehicle relative to the location of the size-restricted or weight restricted roadway.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods 8/15/2014
Vehicle-to-Infrastructure (V2I) Safety Applications Concept of Operation Document Draft 8/10/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 Vehicle  
Connected Vehicle Roadside Equipment Low Moderate Moderate Class 1
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Maint and Constr Management Center Low High High Class 5
Traffic Management Center Moderate High High Class 5
Vehicle Low Moderate Moderate Class 1
Vehicle Characteristics  



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 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 Traffic Management Center infrastructure restriction warning status Low Moderate Low
This information is directly observable The TMC will react based on current status of ITS-RE and thus this information should be trusted The information should be available to ensure timely response from TMC
Connected Vehicle Roadside Equipment Vehicle infrastructure restriction warning notification Low Moderate Low
This information is directly observable. The TMC will react based on current status of ITS-RE and thus this information should be trusted The information should be available to ensure timely response from TMC
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 infrastructure restriction warning Low Moderate Moderate
This information is directly observable This information impacts the vehicle signage data sent to neighboring ASDs and should be trusted to avoid sending wrong information The system should know if these messages are not received
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.
ITS Roadway Equipment Traffic Management Center infrastructure restriction warning status Low Moderate Moderate
This information is directly observable The TMC will react based on current status of ITS-RE and thus this information should be trusted The information should be available to ensure timely response from TMC
Maint and Constr Management Center Traffic Management Center current infrastructure restrictions Low High High
This information is intended to be publicly distributed, so there is no reason to obfuscate. If this flow is compromised a vehicle may enter an area that it should not, potentially placing it at risk of an incident due to oversize. Moving violations are possible as well, but the impact of those is trivial compared to the potential of a container impacting a low bridge for example. While the eventual flow to the vehicle will be wireless and likely cannot achieve HIGH, setting this HIGH ensures that compromise of this flow is difficult and thus not to blame for the vehicle to not receive the wireless flow. (NYC set this MODERATE)
Traffic Management Center Connected Vehicle Roadside Equipment infrastructure restriction warning info Low Moderate Moderate
This information is directly observable The TMC will react based on current status of ITS-RE and thus this information should be trusted The information should be available to ensure timely response from TMC
Traffic Management Center ITS Roadway Equipment infrastructure restriction warning control Moderate High Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: NYC believes this to be low: "This information is directly observable." Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed "announcement". Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From NYC: The ITS-RE can work accordingly or in fail-safe if information is not available.
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 Connected Vehicle Roadside Equipment vehicle profile Low Moderate Moderate
Includes no PII and probably includes information that could be observed, so no need for obfuscation. As this information will be used to determine the vehicle's ability to access services or be charged usage fees, it must be correct and not easily forgeable. This flow enables various services; if the flow is not available the vehicle may not be able to use those services, and also may be charged incorrectly.
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 Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
Traffic Management Center




System Requirements

System Requirement Need
001 The system shall collect and disseminate asset restriction information levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction. 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
002 The system shall provide infrastructure restriction information, including temporary size and weight restrictions, to connected vehicles. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
003 The system shall provide infrastructure restriction information, including temporary size and weight restrictions, to drivers. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
004 The system shall use infrastructure measurements of vehicle characteristics to determine if a vehicle exceeds the roadway or tunnel dimensions. 02 Traffic Operations needs to be able to determine if a vehicle exceeds the height or weight restrictions of a tunnel, bridge, overpass, or section of roadway in order to provide warning to the vehicle or driver.
005 The system shall monitor the traffic approaching a size-restricted roadway or tunnel. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
006 The system shall provide warnings to connected vehicles if the measured height or width exceeds the dimensions for safe passage through the roadway or tunnel. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
007 The system shall measure the weight, height and width of passing vehicles. 02 Traffic Operations needs to be able to determine if a vehicle exceeds the height or weight restrictions of a tunnel, bridge, overpass, or section of roadway in order to provide warning to the vehicle or driver.
008 The system shall display warnings to vehicles if the size exceeds the current infrastructure restrictions. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
009 The system shall send weight and size measurements to the controlling center. 02 Traffic Operations needs to be able to determine if a vehicle exceeds the height or weight restrictions of a tunnel, bridge, overpass, or section of roadway in order to provide warning to the vehicle or driver.
010 The system shall send weight and size measurements as well as vehicle warning to the roadside equipment for transmission to connected vehicles. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
011 The system shall provide infrastructure restriction warnings to connected vehicles. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
012 The system shall receive the infrastructure size and weight restrictions warning messages. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
013 The system shall warn the driver of a vehicle whose weight exceeds the weight limit for a bridge or roadway sufficiently before entering the bridge or roadway so that the driver may take action to avoid going on the road segment for which the vehicle is overweight. 01 Traffic Operations needs to be able to warn potential violators of weight- or size- restricted roadways (e.g. roads or bridges, overpasses) in time for the driver to take appropriate action.
014 The system shall warn the driver of a potential crash due to overheight/overwidth, sufficiently before the potential crash's occurrence that the driver may take action to avoid the crash. 02 Traffic Operations needs to be able to determine if a vehicle exceeds the height or weight restrictions of a tunnel, bridge, overpass, or section of roadway in order to provide warning to the vehicle or driver.
015 The system shall calculate whether or not the vehicle is at risk of crash by entering the size-restricted roadway. 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
016 The system shall calculate whether or not the vehicle is at risk of entering the weight-restricted roadway. 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
017 The system shall determine the host vehicle's weight. 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
018 The system shall determine the host vehicle's physical size characteristics (height, width). 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
019 The system shall determine the roadway's size characteristics (clearance height, width, geometry). 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.
020 The system shall determine the location of the vehicle relative to the location of the size-restricted or weight restricted roadway. 03 Maintenance Operations needs to be able to provide height or weight restriction information on tunnels, bridge, overpass, or section of roadway to other centers to support their operations.