TM12: Dynamic Roadway Warning
This service package includes systems that dynamically warn drivers and other road users of hazards on a roadway. Such hazards include roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway and any other transient event that can be sensed. These dynamic roadway warning systems can alert approaching drivers and other road users via warning signs, flashing lights, in-vehicle messages, etc. Such systems can increase the safety of a roadway by reducing the occurrence of incidents. The system can be centrally monitored and controlled by a traffic management center or it can be autonomous.
Speed warnings that consider the limitations of a given vehicle for the geometry of the roadway (e.g., rollover risk for tall vehicles) are not included in this service package but are covered by the TM17 – Speed Warning and Enforcement service package.
Roadway warning systems, especially queue warning systems are an Active Traffic Management (ATM) strategy and are typically used in conjunction with other ATM strategies (such as TM20-Variable Speed Limits and TM22-Dynamic Lane Management and Shoulder Use).
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
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 | Other ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
ITS Roadway Equipment Owner | Other ITS Roadway Equipment Owner | Information Exchange and Action Agreement |
ITS Roadway Equipment Owner | Other ITS Roadway Equipment 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 Owner | Traffic Operations Personnel | Application Usage Agreement |
ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
Other ITS Roadway Equipment Maintainer | Other ITS Roadway Equipment | Maintains |
Other ITS Roadway Equipment Manager | Other ITS Roadway Equipment | Manages |
Other ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
Other ITS Roadway Equipment Owner | ITS Roadway Equipment Owner | Information Exchange and Action Agreement |
Other ITS Roadway Equipment Owner | ITS Roadway Equipment User | Service Usage Agreement |
Other ITS Roadway Equipment Owner | Other ITS Roadway Equipment Maintainer | System Maintenance Agreement |
Other ITS Roadway Equipment Owner | Other ITS Roadway Equipment Manager | Operations Agreement |
Other ITS Roadway Equipment Supplier | Other ITS Roadway Equipment Owner | Warranty |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Manager | Traffic Operations Personnel | System 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 |
Traffic Operations Personnel | Traffic Management Center | Operates |
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 |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
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. |
MMV User | Personal | The 'MMV User' represents the person that operates a micromobility vehicle (MMV). Included are cyclists and operators of other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The MMV User participates in ITS services that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, and in particular bicyclists that sometimes share motor vehicle lanes, these MMV users provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety. The MMV User originates requests and receives information that reflects the interactions which might be useful to all users, regardless of vehicle type. |
Other ITS Roadway Equipment | Field | Representing another set of ITS Roadway Equipment, 'Other ITS Roadway Equipment' supports 'field device' to 'field device' communication and coordination, and provides a source and destination for information that may be exchanged between ITS Roadway Equipment. The interface enables direct coordination between field equipment. Examples include the direct interface between sensors and other roadway devices (e.g., Dynamic Message Signs) and the direct interface between roadway devices (e.g., between a Signal System Master and Signal System Local equipment) or a connection between an arterial signal system master and a ramp meter controller. |
Potential Obstacles | Field | 'Potential Obstacles' represents any object that possesses the potential of being sensed and struck and thus also possesses physical attributes. Potential Obstacles include roadside obstructions, debris, animals, infrastructure elements (barrels, cones, barriers, etc.) or any other element that is in a potential path of the vehicle. Note that roadside objects and pieces of equipment that can become obstacles in a vehicle's path can include materials, coatings, or labels (e.g., barcodes) that will improve the performance of the vehicle-based sensors that must detect and avoid these obstacles. See also 'Vulnerable Road Users' that more specifically represents the physical properties of shared users of the roadway that must also be detected. |
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. |
Traffic Operations Personnel | Center | 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario. |
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. |
Vulnerable Road Users | Personal | 'Vulnerable Road Users' represents any roadway user not in a motorized vehicle capable of operating at the posted speed for the roadway in question, and also any roadway user in a vehicle not designed to encase (and thus protect) its occupants. This includes pedestrians, cyclists, wheelchair users, two-wheeled scooter micromobility users, as well as powered scooters and motorcycles. Note that this terminator represents the physical properties of vulnerable road users and their conveyance that may be sensed to support safe vehicle automation and traffic management in mixed mode applications where a variety of road users share the right-of-way. See also 'Pedestrian' and 'MMV User' Physical Objects that represent the human interface to these vulnerable road users. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
Roadway Basic Surveillance | 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. | ITS Roadway Equipment |
Roadway Warning | 'Roadway Warning' includes the field equipment used to warn drivers approaching hazards on a roadway. Warnings may be generated in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. The equipment monitors traffic and roadway conditions and may send data to a Traffic Management Center for processing or may process it to determine when a warning should be issued. When it is determined that a warning should be issued, the equipment is used to alert approaching drivers via dynamic warning signs, flashing lights, in-vehicle messages, etc. | ITS Roadway Equipment |
TMC Basic Surveillance | 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. | Traffic Management Center |
TMC Roadway Warning | 'TMC Roadway Warning' remotely monitors and controls the systems used to warn drivers approaching hazards on a roadway. It monitors data on roadway conditions from sensors in the field and generates warnings in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. | Traffic Management Center |
Includes Information Flows:
Information Flow | Description |
---|---|
driver information | Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. |
physical presence | Detection of an obstacle. Obstacle could include animals, incident management and construction elements such as cones, barrels and barriers, rocks in roadway, etc. |
roadway warning coordination | The direct flow of information between field equipment. This includes information used to configure and control roadway warning systems and the current operating status of roadway warning systems. |
roadway warning system control | Information used to configure and control roadway warning systems. |
roadway warning system status | Current operating status of roadway warning systems. |
traffic detector control | Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. |
traffic detector coordination | The direct flow of information between field equipment. This includes information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors Raw and/or processed traffic detector data is returned that allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors |
traffic detector data | Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. |
traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. |
traffic operator data | Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
traffic operator input | User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
traveler safety information | Regulatory, warning, guidance, and other information provided to the traveler or vulnerable road user (VRU) to support safe and efficient travel. |
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. |
video surveillance control | Information used to configure and control video surveillance systems. |
video surveillance coordination | The direct flow of information between field equipment. This includes information used to configure and control video surveillance systems and the high fidelity, real-time traffic images and associated meta data that are returned. |
vulnerable road user presence | Detection of pedestrians, cyclists, and other vulnerable road users. This detection is based on physical characteristics of the user and their conveyance, which may be enhanced by design and materials that facilitate sensor-based detection and tracking of vulnerable road users. |
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
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Traffic Operations need to be able to dynamically warn drivers approaching hazards on a roadway in order to increase the safety of a roadway by reducing the occurrence of incidents. | Roadway Warning | 05 | The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists. |
06 | The field element shall receive commands from the controlling center that activate warning signs to approaching motorists. | |||
TMC Roadway Warning | 05 | The center shall issue control commands to field equipment warning drivers approaching the identified hazardous conditions. | ||
02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. | Roadway Basic Surveillance | 02 | The field element shall collect, process, and send traffic images to the center for further analysis and distribution. |
Roadway Warning | 01 | The field element shall monitor for hazardous traffic conditions, including queues. | ||
02 | The field element shall monitor for hazardous road surface and local weather conditions. | |||
03 | The field element shall monitor for debris, animals, or other objects in the travel lanes. | |||
04 | The field element shall provide collected sensor data to the controlling center. | |||
07 | The field element shall collect operational status of the warning system field equipment and report the operational status to the controlling center. | |||
08 | The field element shall monitor the warning devices and report faults to the controlling center. | |||
TMC Basic Surveillance | 02 | The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center. | ||
04 | The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers. | |||
TMC Roadway Warning | 01 | The center shall monitor data on traffic, environmental conditions, and other hazards collected from sensors along the roadway. | ||
02 | The center shall identify hazardous road weather and surface conditions. | |||
03 | The center shall identify hazardous traffic conditions including queues. | |||
04 | The center shall identify debris, animals, or other encroachment on the roadway dangerous to approaching motorists. | |||
06 | The center shall monitor the operational status of the dynamic warning equipment, including fault reports. | |||
03 | Traffic Operations needs to detect and warn micromobility vehicle users of hazards that could affect them. | Roadway Warning | 08 | The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching micromobility users. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 | |
FHWA-JPO-23-986 - Enhancing the Safety of Vulnerable Road Users at Intersections | Final | 2/1/2023 |
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 |
ITS Roadway Equipment | Moderate | Moderate | Moderate | Class 2 |
Other ITS Roadway Equipment | Moderate | Moderate | Moderate | Class 2 |
Potential Obstacles | ||||
Traffic Management Center | Moderate | High | Moderate | Class 3 |
Vehicle Characteristics | ||||
Vulnerable Road Users |
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 | |||
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 | MMV User | traveler safety information | Not Applicable | High | Low |
This data is intentionally transmitted to everyone via a broadcast. | Although pedestrians and other travelers have a responsibility to make sure the road is safe before they cross, they may react instinctively to incorrect information and be led to cross at unsafe times if they get incorrect information. Also, if the traffic signals are wrong and an accident happens, the traveler involved could sue, causing financial loss and other undesirable outcomes. | Depending on the information distributed it might be easy to tell whether this information flow is available. MODERATE might be justifiable if the information shared is not directly observable. | |||
ITS Roadway Equipment | Other ITS Roadway Equipment | roadway warning coordination | Moderate | Moderate | Moderate |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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 | Other ITS Roadway Equipment | traffic detector coordination | Moderate | Moderate | Low |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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 | Other ITS Roadway Equipment | video surveillance coordination | Moderate | Moderate | Moderate |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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 | Traffic Management Center | roadway warning system status | Moderate | Moderate | Moderate |
Device status information should not be available, as those with criminal intent may use this information toward their own ends. | Inaccurate or unavailable information may suggest inappropriate maintenance actions, costing time and money. | Inaccurate or unavailable information may suggest inappropriate maintenance actions, costing time and money. | |||
ITS Roadway Equipment | Traffic Management Center | traffic detector data | Low | Moderate | Moderate |
No impact if someone sees the data | Some minimal guarantee of data integrity is necessary for all C-ITS flows. THEA believes this to be LOW.only limited adverse effect if raw/processed traffic detector data is bad/compromised; DISC: WYO believes this to be HIGH | Only limited adverse effect of info is not timely/readily available, however without this information it will be difficult to perform traffic management activities, thus MODERATE. If not used for management, may be LOW. | |||
ITS Roadway Equipment | Traffic Management Center | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
ITS Roadway Equipment | Traffic Management Center | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Other ITS Roadway Equipment | ITS Roadway Equipment | roadway warning coordination | Moderate | Moderate | Moderate |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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. | |||
Other ITS Roadway Equipment | ITS Roadway Equipment | traffic detector coordination | Moderate | Moderate | Low |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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. | |||
Other ITS Roadway Equipment | ITS Roadway Equipment | video surveillance coordination | Moderate | Moderate | Moderate |
Any control flow has some confidentiality requirement, as observation of the flow may enable an attacker to analyze and learn how to assume control. MODERATE for most flows as the potential damage is likely contained, though anything that could have a significant safety impact may be assigned HIGH. | Since this directly impacts device control, we consider it the same as a control flow. 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. | Since this directly impacts device control, we consider it the same as a control flow. 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 | ITS Roadway Equipment | roadway warning system 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. | 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 | ITS Roadway Equipment | traffic detector control | Moderate | Moderate | 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: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen | 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: should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with traffic sensor data received and be detrimental to operations | 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 delayed information will not be severe; should be able to operate from a previous/default control/config. DISC: WYO believes this to be MODERATE | |||
Traffic Management Center | ITS Roadway Equipment | video surveillance control | Moderate | Moderate | 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. | 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 | Traffic Operations Personnel | traffic operator data | Moderate | Moderate | Moderate |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. | The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take. | |||
Traffic Operations Personnel | Traffic Management Center | traffic operator input | Moderate | High | High |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. |
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 |
---|---|---|
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 |
Traffic Management Center |
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
002 | The system shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
003 | The system shall monitor data on traffic, environmental conditions, and other hazards collected from sensors along the roadway. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
004 | The system shall identify hazardous road weather and surface conditions. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
005 | The system shall identify hazardous traffic conditions including queues. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
006 | The system shall identify debris, animals, or other encroachment on the roadway dangerous to approaching motorists. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
007 | The system shall issue control commands to field equipment warning drivers approaching the identified hazardous conditions. | 01 | Traffic Operations need to be able to dynamically warn drivers approaching hazards on a roadway in order to increase the safety of a roadway by reducing the occurrence of incidents. |
008 | The system shall monitor the operational status of the dynamic warning equipment, including fault reports. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
009 | The system shall collect, process, and send traffic images to the center for further analysis and distribution. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
010 | The system shall monitor for hazardous traffic conditions, including queues. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
011 | The system shall monitor for hazardous road surface and local weather conditions. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
012 | The system shall monitor for debris, animals, or other objects in the travel lanes. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
013 | The system shall provide collected sensor data to the controlling center. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
014 | The system shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists. | 01 | Traffic Operations need to be able to dynamically warn drivers approaching hazards on a roadway in order to increase the safety of a roadway by reducing the occurrence of incidents. |
015 | The system shall receive commands from the controlling center that activate warning signs to approaching motorists. | 01 | Traffic Operations need to be able to dynamically warn drivers approaching hazards on a roadway in order to increase the safety of a roadway by reducing the occurrence of incidents. |
016 | The system shall collect operational status of the warning system field equipment and report the operational status to the controlling center. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
017 | The system shall monitor the warning devices and report faults to the controlling center. | 02 | Traffic Operations need to be able to receive and process data from multiple sources in order to generate warning for drivers based on the collected traffic and road conditions. |
03 | Traffic Operations needs to detect and warn micromobility vehicle users of hazards that could affect them. |