< < VS07.2 : VS08.1 : VS08.2 > >
VS08.1: Traditional ITS Queue Warning Implementation
Traffic detectors/speed sensors in the infrastructure measure vehicle speeds and traditional ITS assets like DMS are used to provide driver warnings. This basic implementation does not include the CVRSE and does not include any direct OBE interface.
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 |
|---|---|---|
| Driver | Roadway Owner | Expectation of Roadway Condition Management |
| ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
| ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
| ITS Roadway Equipment Manager | Maint and Constr Field Personnel | System Usage Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Owner | Information Exchange 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 |
| Maint and Constr Field Personnel | ITS Roadway Equipment | Operates |
| Other Traffic Management Centers Maintainer | Other Traffic Management Centers | Maintains |
| Other Traffic Management Centers Manager | Other Traffic Management Centers | Manages |
| Other Traffic Management Centers Manager | Other Traffic Management Centers Operator | System Usage Agreement |
| Other Traffic Management Centers Operator | Other Traffic Management Centers | Operates |
| Other Traffic Management Centers Owner | Other Traffic Management Centers Maintainer | System Maintenance Agreement |
| Other Traffic Management Centers Owner | Other Traffic Management Centers Manager | Operations Agreement |
| Other Traffic Management Centers Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| Other Traffic Management Centers Owner | Traffic Management Center Owner | Information Exchange Agreement |
| Other Traffic Management Centers Owner | Traffic Management Center User | Service Usage Agreement |
| Other Traffic Management Centers Owner | Traffic Operations Personnel | Application Usage Agreement |
| Other Traffic Management Centers Supplier | Other Traffic Management Centers Owner | Warranty |
| Roadway Maintainer | Roadway Environment | Maintains |
| Roadway Manager | Roadway Environment | Manages |
| Roadway Owner | Roadway Maintainer | System Maintenance Agreement |
| Roadway Owner | Roadway Manager | Operations Agreement |
| TIC Operator | Transportation Information Center | Operates |
| 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 Exchange Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment User | Service Usage Agreement |
| Traffic Management Center Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Traffic Management Center Owner | Other Traffic Management Centers Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | Other Traffic Management Centers Operator | Application Usage Agreement |
| Traffic Management Center Owner | Other Traffic Management Centers Owner | Information Exchange Agreement |
| Traffic Management Center Owner | Other Traffic Management Centers User | Service Usage Agreement |
| Traffic Management Center Owner | TIC Operator | Application 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 Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
| Traffic Management Center Owner | Transportation Information Center User | Service Usage Agreement |
| Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
| Traffic Operations Personnel | Traffic Management Center | Operates |
| Transportation Information Center Maintainer | Transportation Information Center | Maintains |
| Transportation Information Center Manager | TIC Operator | System Usage Agreement |
| Transportation Information Center Manager | Transportation Information Center | Manages |
| Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
| Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
| Transportation Information Center Supplier | Transportation Information Center 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. |
| Other Traffic Management Centers | Center | Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas. |
| Roadway Environment | Field | 'Roadway Environment' represents the physical condition and geometry of the road surface, markings, signs, and other objects on or near the road surface. It also represents the environmental conditions immediately surrounding the roadway. The roadway environment must be sensed and interpreted to support automated vehicle services. Surrounding conditions may include fog, ice, snow, rain, wind, etc. which will influence the way in which a vehicle can be safely operated on the roadway. The roadway environment must be monitored to enable corrective action and information dissemination regarding roadway conditions which may adversely affect travel. Infrastructure owner/operators can improve the roadway environment to improve the performance and accuracy of vehicle-based sensors that must sense and interpret this environment. Improvements could include changes in the shape, size, design, and materials used in signs, pavement markings, and other road features. |
| 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. |
| Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
| 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, occupants, emissions) 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 |
|---|---|---|
| Roadway Environmental Monitoring | 'Roadway Environmental Monitoring' measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed or to other field devices to support communications to vehicles. A broad array of weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other metrics. | ITS Roadway Equipment |
| Roadway Surveillance | 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors, CCTV cameras, , RADARs and LIDARs. | 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 |
| TIC Situation Data Management | 'TIC Situation Data Management' manages connected vehicle situation data collection, quality controls, filtering, aggregation, and storage. Through this process, raw data reported by connected vehicles are transformed into information products that can be accessed and used to support transportation operations and traveler information. | Transportation Information Center |
| 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 Environmental Monitoring | 'TMC Environmental Monitoring' assimilates current and forecast road conditions and surface weather information using a combination of weather service provider information, information collected by other centers such as the Maintenance and Construction Management Center, data collected from environmental sensors deployed on and about the roadway, and information collected from connected vehicles. The collected environmental information is monitored and presented to the operator. This information can be used to issue general traveler advisories and support location specific warnings to drivers. | 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. |
| environmental conditions | Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that are measured by environmental sensors. |
| environmental sensor control | Data used to configure and control environmental sensors. |
| environmental sensor data | Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors. Operational status of the sensors is also included. |
| road network conditions | Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included. |
| 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 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. |
| 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 and characterize their performance (e.g., speed, occupants, emissions). |
| video surveillance control | Information used to configure and control video surveillance systems. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; | Improve freight network |
| B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
| D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
| E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; | Protect/Enhance the Environment |
| F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
| G. Promote efficient system management and operation; | Improve efficiency |
| I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; | Improve resiliency and reliability |
| J. Enhance travel and tourism. | Support travel and tourism |
Associated Objective Categories 
Associated Objectives and Performance Measures
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.
Needs and Requirements
| Need | Functional Object | Requirement | ||
|---|---|---|---|---|
| 01 | Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information. | Roadway Surveillance | 01 | The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. |
| 02 | The field element shall collect, process, and send traffic images to the center for further analysis and distribution. | |||
| 04 | The field element shall return sensor and CCTV system operational status to the controlling center. | |||
| Roadway Warning | 01 | The field element shall monitor for hazardous traffic conditions, including queues. | ||
| 05 | The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists. | |||
| 08 | The field element shall collect operational status of the warning system field equipment and report the operational status to the controlling center. | |||
| TMC Basic Surveillance | 01 | The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. | ||
| 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. | |||
| 05 | The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. | |||
| 06 | The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each). | |||
| 07 | The center shall remotely control devices to detect traffic. | |||
| TMC Environmental Monitoring | 01 | The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. | ||
| 02 | The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
| 03 | The traffic center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway. | |||
| 05 | The traffic center shall receive aggregated and processed vehicle environmental data collected from vehicle safety and convenience systems through the connected vehicle roadside equipment. | |||
| TMC Roadway Warning | 01 | The center shall monitor data on traffic, environmental conditions, and other hazards collected from sensors along the roadway. | ||
| 07 | The center shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles. | |||
| 02 | Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information. | Roadway Environmental Monitoring | 01 | The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. |
| 02 | The field element shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
| 04 | The field element's environmental sensors shall be remotely controlled by a traffic management center. | |||
| 07 | The field element shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle. | |||
| 10 | The field element shall provide weather and road surface condition data to centers. | |||
| Roadway Surveillance | 01 | The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. | ||
| 02 | The field element shall collect, process, and send traffic images to the center for further analysis and distribution. | |||
| 04 | The field element shall return sensor and CCTV system operational status to the controlling center. | |||
| TMC Basic Surveillance | 01 | The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. | ||
| 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. | |||
| 05 | The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. | |||
| 06 | The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each). | |||
| 07 | The center shall remotely control devices to detect traffic. | |||
| TMC Environmental Monitoring | 01 | The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. | ||
| 02 | The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
| 03 | The traffic center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway. | |||
| 05 | The traffic center shall receive aggregated and processed vehicle environmental data collected from vehicle safety and convenience systems through the connected vehicle roadside equipment. | |||
| TMC Roadway Warning | 09 | The center shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic. | ||
| 03 | Traffic Operations needs to be able to generate queue warning response strategies, including speed reduction, lane change, or diversion. | TMC Roadway Warning | 08 | The center shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions. |
| 05 | The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles | Roadway Warning | 05 | The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists. |
| 07 | The field element shall receive commands from the controlling center that activate warning signs to approaching motorists. | |||
| TIC Situation Data Management | 01 | The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment. | ||
Related Sources
| Document Name | Version | Publication Date |
|---|---|---|
| None |
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 Traffic Management Centers | Low | Moderate | Moderate | Class 1 |
| Roadway Environment | Not Applicable | Low | Low | Class 1 |
| Traffic Management Center | Moderate | High | Moderate | Class 3 |
| Transportation Information Center | 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 | |||
| ITS Roadway Equipment | Driver | driver information | Not Applicable | High | Moderate |
| This data is sent to all drivers and is also directly observable, by design. | This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents could happen. | If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections. | |||
| ITS Roadway Equipment | Traffic Management Center | environmental sensor data | Low | Moderate | Moderate |
| Little to no impact if this data is observed | info should be correct to determine safe speeds etc.; DISC: WYO believes this to be HIGH | Updates are desireable but slightly outdated information will not be catastrophic. | |||
| 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 Traffic Management Centers | Traffic Management Center | road network conditions | Low | Moderate | Moderate |
| No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
| Roadway Environment | ITS Roadway Equipment | environmental conditions | Not Applicable | Low | Low |
| Sensor-based information flows by definition have no confidentiality concerns. | While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions. | While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions. | |||
| Traffic Management Center | ITS Roadway Equipment | environmental sensor 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 | 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 environmental sensor data received and be detrimental to operations; DISC: WYO believes this may be HIGH for some applications | 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 THEAwant 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 | 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 | Other Traffic Management Centers | road network conditions | Low | Moderate | Moderate |
| encrypted; but no harm should come from seeing this data | info needs to be accurate and should not be tampered but should be able to cope with some bad data; should be able to confirm conditions by other mechanisms | condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not | |||
| 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 Management Center | Transportation Information Center | road network conditions | Low | Moderate | Moderate |
| No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
| 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. | |||
| Vehicle Characteristics | ITS Roadway Equipment | vehicle characteristics | |||
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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.
| Name | Title | Known Issues | Physical Object |
|---|---|---|---|
| ISO 24100 Probe Vehicle Data Protection | Intelligent transport systems -- Basic principles for personal data protection in probe vehicle information services | Traffic Management Center | |
| Transportation Information Center | |||
| ITE 5301 ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment | |
| NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | ITS Roadway Equipment | |
| Traffic Management Center |
System Requirements
| No System Requirements |