< < TM16 : TM17 : TM18 > >

TM17: Speed Warning and Enforcement

This service package monitors vehicle speeds and supports warning drivers when their speed is excessive. Also the service includes notifications to an enforcement agency to enforce the speed limit of the roadway. Speed monitoring can be made via spot speed or average speed measurements. Roadside equipment can display the speed of passing vehicles and/or suggest a safe driving speed. Environmental conditions and vehicle characteristics may be monitored and factored into the safe speed advisories that are provided to the motorist. For example, warnings can be generated recognizing the limitations of a given vehicle for the geometry of the roadway such as rollover risk for tall vehicles.

This service focuses on monitoring of vehicle speeds and enforcement of the speed limit while the variable speed limits service (covered in TM20-Variable Speed Limits service package) focuses on varying the posted speed limits to create more uniform speeds along a roadway, to promote safer driving during adverse conditions (such as fog) and/or to reduce air pollution.

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
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 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 Vehicle Operates
Enforcement Center Maintainer Enforcement Center Maintains
Enforcement Center Manager Enforcement Center Manages
Enforcement Center Owner Enforcement Center Maintainer System Maintenance Agreement
Enforcement Center Owner Enforcement Center Manager Operations Agreement
Enforcement Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Enforcement Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Enforcement Center Owner ITS Roadway Equipment User Service Usage Agreement
Enforcement Center Supplier Enforcement Center Owner Warranty
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 Enforcement Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Enforcement Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Enforcement Center 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 Maint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Maint and Constr Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Maint and Constr Management Center User Service Usage 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 Enforcement Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Enforcement Center Owner Information Provision Agreement
Maint and Constr Management Center Owner Enforcement Center User Service Usage Agreement
Maint and Constr Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Maint and Constr Management Center Owner ITS Roadway Equipment User Service Usage Agreement
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 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 Enforcement Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Enforcement Center Owner Information Provision Agreement
Traffic Management Center Owner Enforcement Center 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 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.3 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 Speed Monitoring and Warning 1.1.1.1 Process Traffic Sensor Data
1.2.7.9 Process Roadway Information Data
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
9.3.3.4 Support Vehicle Speed Enforcement
Maint and Constr Management Center MCM Reduced Speed Zone Warning 9.2.3.5 Collect Roadside Equipment Status
9.2.5 Provide M&C Center Personnel Interface for Maint
9.3.1.1 Operate Work Zone Devices
9.3.2.3 Generate Work Zone Information for Distribution
9.3.3.2 Monitor Vehicle Speed in Work Zone
Traffic Management Center TMC Speed Warning 1.1.2.5 Process Vehicle Situation Data
1.2.4.3 Output In-vehicle Signage Data
1.2.4.4 Output Roadway Information Data
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.6.2 Provide Static Data Store Output Interface
1.2.8 Collect Traffic Field Equipment Fault Data
9.3.3.3 Manage Vehicle Speed on Roadway
Vehicle 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.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information 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
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.
Enforcement Center Center The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
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 Reduced Speed Zone Warning 'MCM Reduced Speed Zone Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. Maint and Constr Management Center
Roadway Speed Monitoring and Warning 'Roadway Speed Monitoring and Warning' includes the field elements that monitor vehicle speeds. If the speed is determined to be excessive, an advisory or warning is displayed. Current environmental conditions and other factors that may reduce safe operating speeds may also be taken into account. The operational status (state of the device, configuration, and fault data) is provided to the center. This application can also provide an enforcement function, reporting speed violations to an enforcement agency. 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
TMC Speed Warning 'TMC Speed Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides the location and extent of the reduced speed zone, the posted speed limit(s) with information about the applicability of the speed limit(s) (e.g., time of day, day of week, seasonality, relevant vehicle types) and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. 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
automated enforcement parameters Includes setup information that identifies rules to be enforced, identification of violators, vehicle/user clearance lists, and other information that supports automated enforcement using roadside systems.
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 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.
request for enforcement Request for traffic enforcement of speed limits, lane controls, etc. on a roadway including in a work zone or other special situations.
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.
speed monitoring control Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems.
speed monitoring information System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records.
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 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).
vehicle signage local data Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.
violation notification Notification to enforcement agency of detected traffic violations. This notification identifies the vehicle and documents the infraction date, time, and location, the violation, and associated information that documents the violation. For example, for a speed violation, this flow includes the measured speed and current posted speed limit.

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

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities

Associated Objectives and Performance Measures

Objective Performance Measure
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 speed differential Number of crashes and fatalities related to excessive speeding
Reduce speed differential Number of speed violations
Reduce the number of fatalities in crashes involving a driver or motorcycle operator with a BAC of.08 and above by X percent by Y year. Number of fatalities in crashes involving a driver or motorcycle operator with a BAC of.08 and above
Reduce the number of motorcyclist fatalities by X percent by year Y. Number of motorcyclist fatalities
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the number of speeding-related fatalities by X percent by year Y. Number of speeding-related fatalities
Reduce the rate fatalities in the region by X percent by year Y. Rate of fatalities (rate per vehicle miles travelled (VMT))
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 crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries 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 Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive. MCM Reduced Speed Zone Warning 01 The center shall be capable of remotely control and monitor reduced speed zone warning roadside equipment operations.
Roadway Speed Monitoring and Warning 01 The field element shall include sensors to detect vehicle speeds, under traffic or maintenance center control.
06 The field element shall return operational status for the vehicle speed sensors to the controlling traffic or maintenance center; including measured speeds, warning messages displayed, and violation records.
TMC Speed Warning 02 The center shall province the capability to control automated speed monitoring and speed warning systems.
02 Traffic Operations need to be able to warn drivers when their speed is excessive. MCM Reduced Speed Zone Warning 02 The center shall provide reduced speed zone posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts for display on roadside devices.
Roadway Speed Monitoring and Warning 03 If the speed detected by vehicle speed sensors is determined to be excessive, the field element shall provide a safe speed advisory to passing drivers via a driver information system (such as portable messages signs, field to vehicle communications to in-vehicle signing systems, etc.).
RSE Traveler Information Communications 01 The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control.
02 The field element shall distribute advisory information, such as evacuation information, wide-area alerts, incident information, work zone intrusion information, recommended speed limit and other special information to passing vehicles using short range communications, under center control.
03 The field element shall distribute 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 states and local conditions warnings identified by local environmental sensors) to equipment on-board vehicles under center control.
04 The field element shall return system operational status to the controlling center.
Vehicle Traveler Information Reception 01 The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
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
03 Traffic Operations need to be able to notify an enforcement agency that vehicles are traveling at excessive speed and to be able to request that the enforcement agency respond to the excessive speed. TMC Speed Warning 01 The center shall provide the capability to notify an enforcement agency when vehicle speeds in the work zone are in excess of the posted speed limit or are creating an unsafe condition based upon the current environmental or traffic conditions.
04 Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive. Roadway Speed Monitoring and Warning 02 The field element shall include sensors to detect vehicle speeds, under enforcement agency control.
05 The field element shall monitor notify an enforcement agency when a speed violation is detected.
07 The field element shall return operational status for the vehicle speed sensors to the enforcement agency.
08 The field element shall return fault data for the vehicle speed sensors to the controlling center for repair.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005


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
Connected Vehicle Roadside Equipment Low Moderate Moderate Class 1
Enforcement Center Moderate High Moderate Class 3
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Maint and Constr Management Center Moderate High Moderate Class 3
Traffic Management Center Moderate High Moderate Class 3
Vehicle Low Low 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
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.
Enforcement Center ITS Roadway Equipment automated enforcement parameters Low Moderate Low
Should cause no harm if this information were public. Corruption or manipulation of this flow could cause inaccurate violations, which would be a significant inconvenience (if set to generate more violations that it should). If this flow cannot function then automated enforcement may in the worst case pause, which has little negative effect on roadway operation.
Enforcement Center ITS Roadway Equipment speed monitoring 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. 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. 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.
ITS Roadway Equipment Connected Vehicle Roadside Equipment vehicle signage local 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. This information impacts the vehicle signage data sent to neighboring ASDs and should be trusted to avoid sending wrong information. DISC: WYO believes this to be HIGH. 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 Enforcement Center speed monitoring information Moderate Moderate Moderate
Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.
ITS Roadway Equipment Enforcement Center violation notification Moderate Moderate Moderate
Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.
ITS Roadway Equipment Maint and Constr Management Center 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 Maint and Constr Management Center speed monitoring information Moderate Moderate Moderate
Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.
ITS Roadway Equipment Traffic Management Center 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 Traffic Management Center speed monitoring information Moderate Moderate Moderate
encrypted, authenticated, violation records included info that should not be tampered with, especially violation records and operational state but the rest is aggregate info want updates but outdated information will not be catastrophic; would want to know about the speeds, warnings, etc. to be able to reconfigure speed warning info as necessary
Maint and Constr Management Center Enforcement Center request for enforcement Moderate Moderate Low
If this request were intercepted by a third party, that party may learn where enforcement assets would be and so could use that information to avoid such assets in the commission of a crime. Inaccurate or corrupted information here could lead to enforcement in areas not requested, and/or no enforcement in the area that was requested. Given that the request is possibly safety-based, this can negatively impact safety and/or mobility in that area. The setup of enforcement in a given area will likely be given and granted at low frequency; that is on the order of instances/week, not a real time request, so this flow does not need to be continuously available.
Maint and Constr Management Center 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.
Maint and Constr Management Center ITS Roadway Equipment speed monitoring 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. 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. 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.
Traffic Management Center Enforcement Center request for enforcement Moderate Moderate Low
If this request were intercepted by a third party, that party may learn where enforcement assets would be and so could use that information to avoid such assets in the commission of a crime. Inaccurate or corrupted information here could lead to enforcement in areas not requested, and/or no enforcement in the area that was requested. Given that the request is possibly safety-based, this can negatively impact safety and/or mobility in that area. The setup of enforcement in a given area will likely be given and granted at low frequency; that is on the order of instances/week, not a real time request, so this flow does not need to be continuously available.
Traffic Management Center 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.
Traffic Management Center ITS Roadway Equipment speed monitoring control Moderate High Moderate
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. From THEA: encrypted, authenticated, proprietary but shouldn't cause substantial risk but does control speed enforcement systems 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 THEA: proprietary info that should not be tampered with; could directly affect safety if compromised posting unsafe speed limits, etc. 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 THEA: want updates but outdated information will not be catastrophic; should be able to use previous/default config
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 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
Maint and Constr Management Center
Traffic Management Center
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 remotely control and monitor reduced speed zone warning roadside equipment operations. 01 Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive.
002 The system shall provide reduced speed zone posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts for display on roadside devices. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
003 The system shall provide the capability to notify an enforcement agency when vehicle speeds in the work zone are in excess of the posted speed limit or are creating an unsafe condition based upon the current environmental or traffic conditions. 03 Traffic Operations need to be able to notify an enforcement agency that vehicles are traveling at excessive speed and to be able to request that the enforcement agency respond to the excessive speed.
004 The system shall province the capability to control automated speed monitoring and speed warning systems. 01 Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive.
005 The system shall include sensors to detect vehicle speeds, under traffic or maintenance center control. 01 Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive.
006 The system shall include sensors to detect vehicle speeds, under enforcement agency control. 04 Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive.
007 The system shall provide a safe speed advisory to passing drivers via a driver information system (such as portable messages signs, field to vehicle communications to in-vehicle signing systems, etc.). 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
008 The system shall monitor notify an enforcement agency when a speed violation is detected. 04 Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive.
009 The system shall return operational status for the vehicle speed sensors to the controlling traffic or maintenance center; including measured speeds, warning messages displayed, and violation records. 01 Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive.
010 The system shall return operational status for the vehicle speed sensors to the enforcement agency. 04 Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive.
011 The system shall return fault data for the vehicle speed sensors to the controlling center for repair. 04 Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive.
012 The system shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
013 The system shall distribute advisory information, such as evacuation information, wide-area alerts, incident information, work zone intrusion information, recommended speed limit and other special information to passing vehicles using short range communic 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
014 The system shall distribute 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 states and local conditions wa 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
015 The system shall return system operational status to the controlling center. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
016 The system shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
017 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 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
018 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 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
019 The system shall store a translation table for road sign and message templates used for in-vehicle display. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
020 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. 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
021 The system shall present to the driver a visual display of static sign information or dynamic roadway conditions information 02 Traffic Operations need to be able to warn drivers when their speed is excessive.
022 The system shall provide to the driver an audible presentation of static sign information or dynamic roadway conditions information 02 Traffic Operations need to be able to warn drivers when their speed is excessive.