Parent Service Package: VS09
< < VS08.3 : VS09.1 : VS09.2 > >

VS09.1: Traditional Reduced Speed Warning

Traffic detectors/speed sensors in the infrastructure measure vehicle speeds and traditional ITS assets like DMS are used to provide warnings to drivers approaching reduced speed zones and segments with lane closures. This basic implementation does not include direct communications with approaching vehicles. The more advanced implementations build on this basic implementation, providing backwards compatibility for unequipped vehicles approaching the reduced speed zone.

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
ITS Roadway Equipment MaintainerITS Roadway Equipment Maintains
ITS Roadway Equipment ManagerITS Roadway Equipment Manages
ITS Roadway Equipment ManagerMaint and Constr Field Personnel System Usage Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment OwnerMaint and Constr Center Personnel Application Usage Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center Owner Information Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Management Center User Service Usage Agreement
ITS Roadway Equipment OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerTraffic Management Center Owner Information Exchange Agreement
ITS Roadway Equipment OwnerTraffic Management Center User Service Usage Agreement
ITS Roadway Equipment OwnerTraffic Operations Personnel Application Usage Agreement
ITS Roadway Equipment SupplierITS Roadway Equipment Owner Warranty
Maint and Constr Center PersonnelMaint and Constr Management Center Operates
Maint and Constr Field PersonnelITS Roadway Equipment Operates
Maint and Constr Management Center MaintainerMaint and Constr Management Center Maintains
Maint and Constr Management Center ManagerMaint and Constr Center Personnel System Usage Agreement
Maint and Constr Management Center ManagerMaint and Constr Management Center Manages
Maint and Constr Management Center OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerITS Roadway Equipment Owner Information Exchange Agreement
Maint and Constr Management Center OwnerITS Roadway Equipment User Service Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Field Personnel Application Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center OwnerMaint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerTraffic Management Center Owner Information Exchange Agreement
Maint and Constr Management Center OwnerTraffic Management Center User Service Usage Agreement
Maint and Constr Management Center OwnerTraffic Operations Personnel Application Usage Agreement
Maint and Constr Management Center SupplierMaint and Constr Management Center Owner Warranty
Traffic Management Center MaintainerTraffic Management Center Maintains
Traffic Management Center ManagerTraffic Management Center Manages
Traffic Management Center ManagerTraffic Operations Personnel System Usage Agreement
Traffic Management Center OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerITS Roadway Equipment Owner Information Exchange Agreement
Traffic Management Center OwnerITS Roadway Equipment User Service Usage Agreement
Traffic Management Center OwnerMaint and Constr Center Personnel Application Usage Agreement
Traffic Management Center OwnerMaint and Constr Field Personnel Application Usage Agreement
Traffic Management Center OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Traffic Management Center OwnerMaint and Constr Management Center User Service Usage Agreement
Traffic Management Center OwnerTraffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center OwnerTraffic Management Center Manager Operations Agreement
Traffic Management Center SupplierTraffic Management Center Owner Warranty
Traffic Operations PersonnelTraffic Management Center Operates

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
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Vehicle 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
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
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

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.
field device coordination Coordination between operating centers that share control of the same field devices. This flow supports coordination to prevent conflicts and allow cooperative management of shared devices.
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 and characterize their performance (e.g., speed, occupants, emissions).

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective Performance Measure

 
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

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
Maint and Constr Management Center Moderate High Moderate Class 3
Traffic Management Center Moderate High Moderate Class 3
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 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 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.
Maint and Constr Management Center Traffic Management Center field device coordination Low Moderate Moderate
There should be little harm to come from knowing who controls what field device in most instances. For security monitoring objects such as security cameras this might be MODERATE, but the flow is marked as low since it is unlikely that those kinds of objects have shared control. If this flow is incorrect or manipulated then an unauthorized party may be able to gain control of a device, which can have significant effects. This is not a control flow however, so actual control is unlikely, thus MODERATE. Depends on the sharing arrangement, but generally interfaces between centers should provide timely response to enable proper decision making and action.
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
Traffic Management Center Maint and Constr Management Center field device coordination Low Moderate Moderate
There should be little harm to come from knowing who controls what field device in most instances. For security monitoring objects such as security cameras this might be MODERATE, but the flow is marked as low since it is unlikely that those kinds of objects have shared control. If this flow is incorrect or manipulated then an unauthorized party may be able to gain control of a device, which can have significant effects. This is not a control flow however, so actual control is unlikely, thus MODERATE. Depends on the sharing arrangement, but generally interfaces between centers should provide timely response to enable proper decision making and action.
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.

NameTitlePhysical Object
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
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

No System Requirements