Parent Service Package: MC07
< < MC06.2 : MC07.1 : MC07.2 > >

MC07.1: Sensor-Based Safety Monitoring

Use sensors/traffic detectors in the work zone to detect and monitor work zone personnel and vehicles traveling through the work zone. In this implementation, sensors/detectors mounted on maintenance vehicles or positioned in the work zone monitor the perimeter of the work zone and provide warnings when a vehicle is moving in a manner that poses a risk to work zone personnel. Sensors can also monitor field personnel in the work zone in order to warn personnel if they approach the perimeter of the designated work area.

Relevant Regions:

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Vehicle MaintainerBasic Vehicle Maintains
Basic Vehicle ManagerBasic Vehicle Manages
Basic Vehicle ManagerDriver System Usage Agreement
Basic Vehicle OwnerBasic Vehicle Maintainer System Maintenance Agreement
Basic Vehicle OwnerBasic Vehicle Manager Operations Agreement
Basic Vehicle SupplierBasic Vehicle Owner Warranty
Connected Vehicle Roadside Equipment MaintainerConnected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Operator System Usage Agreement
Connected Vehicle Roadside Equipment OperatorConnected Vehicle Roadside Equipment Operates
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment OwnerMaint and Constr Field Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment OwnerPersonnel Device Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment OwnerPersonnel Device Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment OwnerPersonnel Device User Service Usage Agreement
Connected Vehicle Roadside Equipment SupplierConnected Vehicle Roadside Equipment Owner Warranty
DriverBasic Vehicle Operates
DriverVehicle Operates
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 OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerMaint and Constr Vehicle OBE Owner Expectation of Information Provision
ITS Roadway Equipment OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
ITS Roadway Equipment OwnerMaint and Constr Vehicle Operator 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 Field PersonnelPersonnel Device 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 OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE Owner Information Exchange Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Maint and Constr Management Center OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Maint and Constr Management Center SupplierMaint and Constr Management Center Owner Warranty
Maint and Constr Vehicle OBE MaintainerMaint and Constr Vehicle OBE Maintains
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle OBE Manages
Maint and Constr Vehicle OBE ManagerMaint and Constr Vehicle Operator System Usage Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerITS Roadway Equipment User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Center Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Field Personnel Application Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center Owner Information Exchange Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Management Center User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Maintainer System Maintenance Agreement
Maint and Constr Vehicle OBE OwnerMaint and Constr Vehicle OBE Manager Operations Agreement
Maint and Constr Vehicle OBE OwnerOther MCV OBEs Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerOther MCV OBEs Operator Application Usage Agreement
Maint and Constr Vehicle OBE OwnerOther MCV OBEs Operator Vehicle Operating Agreement
Maint and Constr Vehicle OBE OwnerOther MCV OBEs Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerOther MCV OBEs User Service Usage Agreement
Maint and Constr Vehicle OBE OwnerPersonnel Device Maintainer Maintenance Data Exchange Agreement
Maint and Constr Vehicle OBE OwnerPersonnel Device Owner Expectation of Data Provision
Maint and Constr Vehicle OBE OwnerPersonnel Device User Service Usage Agreement
Maint and Constr Vehicle OBE SupplierMaint and Constr Vehicle OBE Owner Warranty
Maint and Constr Vehicle OperatorMaint and Constr Vehicle OBE Operates
Other MCV OBEs MaintainerOther MCV OBEs Maintains
Other MCV OBEs ManagerOther MCV OBEs Manages
Other MCV OBEs ManagerOther MCV OBEs Operator System Usage Agreement
Other MCV OBEs OperatorOther MCV OBEs Operates
Other MCV OBEs OwnerMaint and Constr Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Other MCV OBEs OwnerMaint and Constr Vehicle OBE Owner Expectation of Data Provision
Other MCV OBEs OwnerMaint and Constr Vehicle OBE User Service Usage Agreement
Other MCV OBEs OwnerMaint and Constr Vehicle Operator Application Usage Agreement
Other MCV OBEs OwnerMaint and Constr Vehicle Operator Vehicle Operating Agreement
Other MCV OBEs OwnerOther MCV OBEs Maintainer System Maintenance Agreement
Other MCV OBEs OwnerOther MCV OBEs Manager Operations Agreement
Other MCV OBEs SupplierOther MCV OBEs Owner Warranty
Personnel Device MaintainerPersonnel Device Maintains
Personnel Device ManagerMaint and Constr Field Personnel System Usage Agreement
Personnel Device ManagerPersonnel Device Manages
Personnel Device OwnerPersonnel Device Maintainer System Maintenance Agreement
Personnel Device OwnerPersonnel Device Manager Operations Agreement
Personnel Device SupplierPersonnel Device Owner Warranty
Vehicle MaintainerVehicle Maintains
Vehicle ManagerDriver System Usage Agreement
Vehicle ManagerVehicle Manages
Vehicle OwnerBasic Vehicle Maintainer Maintenance Data Exchange Agreement
Vehicle OwnerBasic Vehicle Owner Expectation of Data Provision
Vehicle OwnerBasic Vehicle User Service Usage Agreement
Vehicle OwnerDriver Application Usage Agreement
Vehicle OwnerDriver Vehicle Operating Agreement
Vehicle OwnerVehicle Maintainer System Maintenance Agreement
Vehicle OwnerVehicle Manager Operations Agreement
Vehicle SupplierVehicle Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Work Zone Safety 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.2.7.15 Process Intersection Safety Data
1.2.7.4 Process In-vehicle Signage Data
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
9.2.3.8 Collect Connected Vehicle Field Equipment Status
ITS Roadway Equipment Roadway Work Zone Safety 1.1.2.11 Control Dynamic Lanes
1.3.1.3 Process Traffic Images
9.3.1.3 Monitor Crew Movement
9.3.4.1 Detect Work Zone Intrusion
9.3.4.2 Provide Work Zone Intrusion Alert
Maint and Constr Management Center MCM Work Zone Safety Management 9.2.3.5 Collect Roadside Equipment Status
9.3.1.1 Operate Work Zone Devices
9.3.2.2 Collect Work Zone Data
9.3.3.2 Monitor Vehicle Speed in Work Zone
Maint and Constr Vehicle OBE MCV Vehicle Safety Monitoring 9.1.2 Collect M&C Vehicle Data On-Board
9.3.1.2 Operate WZ Devices On-Board
9.3.1.4 Monitor Crew Movement On-Board
9.3.2.1 Status Work Zone Activity
9.3.4.3 Detect Work Zone Intrusion On-Board
9.3.4.4 Provide On-Board Work Zone Intrusion Alert
Personnel Device Personnel Work Zone Safety 5.8.7.3 Monitor Emergency Personnel Safety Status
9.3.4.5 Support Personnel Work Zone Safety
Vehicle Vehicle Basic Safety Communication 3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
3.2.3.2 Manage Platoon Following
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.5.1 Process General Vehicle Sensor Data
3.2.4 Process Sensor Data for Automatic Vehicle Operations
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.2 Provide Driver Information Interface
Vehicle Traveler Information Reception 3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.2.3.3 Process Data for Vehicle Actuators
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information Interface

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Basic Vehicle Vehicle 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Maint and Constr Field Personnel Field Represents the people that perform maintenance and construction field activities including vehicle and equipment operators, field supervisory personnel, field crews, and work zone safety personnel. Information flowing from the Maintenance and Construction Field Personnel will include those system inputs specific to maintenance and construction operations, such as information regarding work zone status, or the status of maintenance actions. The field personnel are also monitored within the work zone to enhance work zone safety. Information provided to Maintenance and Construction Field Personnel includes dispatch requests, maintenance and construction actions to be performed, and work zone safety warnings.
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.
Maint and Constr Vehicle OBE Vehicle The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.
Other MCV OBEs Vehicle This represents on-board equipment on other maintenance and construction vehicles. It provides a source and destination for ITS information transfers between maintenance and construction vehicles. These information transfers allow vehicle operational status, environmental information, and work zone intrusion warnings or alarms to be shared between vehicles.
Personnel Device Personal 'Personnel Device' represents devices used by emergency personnel or maintenance and construction personnel in the field. In the case of emergency personnel, the devices would include body cameras or smartphones (and their peripherals) that can be used by emergency personnel to provide images or video as well as send or receive data regarding the incident. The devices could also be used for incident scene safety messages to the personnel. In the case of maintenance and construction field personnel, the devices could be cellular phones or specialized safety devices that would be used for work zone safety messages to the personnel.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Vehicle Characteristics Vehicle 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles, 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 Work Zone Safety Management 'MCM Work Zone Safety Management' remotely monitors work zone safety systems that detect vehicle intrusions in work zones and warns crew workers and drivers of imminent encroachment. Crew movements are also monitored so that the crew can be warned of movement beyond the designated safe zone. Maint and Constr Management Center
MCV Vehicle Safety Monitoring 'MCV Vehicle Safety Monitoring' detects vehicle intrusions in the vicinity of the vehicle and warns crew workers and drivers of imminent encroachment. Crew movements are also monitored so that the crew can be warned of movement beyond the designated safe zone. It can be used for stationary work zones or in mobile applications where a safe zone is maintained around the moving vehicle. Maint and Constr Vehicle OBE
Personnel Work Zone Safety 'Personnel Work Zone Safety' improves maintenance and construction crew safety by providing crew location information to the infrastructure that can be used to avoid collisions involving the work crew. The application may also alert workers if they travel beyond the designated safe zone. The information provided and the user interface delivery mechanism (visual, audible, or haptic) can also be tailored to the needs of the user that is carrying or wearing the device that hosts the application. Personnel Device
Roadway Work Zone Safety 'Roadway Work Zone Safety' includes field elements that detect vehicle intrusions in work zones and warns crew workers and drivers of imminent encroachment. Crew movements are also monitored so that the crew can be warned of movement beyond the designated safe zone. ITS Roadway Equipment
RSE Work Zone Safety 'RSE Work Zone Safety' communicates with Connected Vehicles and Personal Information Devices carried or worn by the work crew to detect vehicle intrusions in work zones and warn crew workers and drivers of imminent encroachment. Crew movements are also monitored so that the crew can be warned of movement beyond the designated safe zone. Connected Vehicle Roadside Equipment
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. Vehicle
Vehicle Traveler Information Reception 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. Vehicle

Includes Information Flows:

Information Flow Description
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
driver update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
personnel monitoring Sensed presence of personnel within a work zone or incident scene that is monitored to enhance safety in work areas proximate to moving traffic.
personnel safety warning Safety alerts and warnings provided to a personnel device. The provided information would identify safety threats (e.g., vehicle encroachment into a work area, personnel infringement into a travel lane)
personnel updates Alerts and warnings provided to emergency personnel or work crew members. This includes visual, audio, and haptic outputs that may be customized to support individual needs.
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.
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.
work zone warning Warnings provided to field personnel, indicating a work zone emergency or safety issue such as the intrusion of a vehicle into the work zone area or movement of personnel into the travel lanes.
work zone warning device control Data used to configure and control work zone safety monitoring and warning devices.
work zone warning notification Notification of a work zone emergency or safety issue. This flow identifies that a work zone emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.
work zone warning status Status of a work zone safety monitoring and warning devices. This flow documents system activations and includes additional supporting information (e.g., an image) that allows verification of the alarm.

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
Basic Vehicle  
Connected Vehicle Roadside Equipment  
ITS Roadway Equipment  
Maint and Constr Management Center  
Maint and Constr Vehicle OBE  
Other MCV OBEs  
Personnel Device  
Vehicle  
Vehicle Characteristics  



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Connected Vehicle Roadside Equipment Personnel Device personnel safety warning Not Applicable High Low
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. A few false warnings should not have a bad consequence. When an emergency personnel receives a warning they can look around and verify whether or not a vehicle is actually headed towards them. However, a message saying it is safe when there is a car coming could lead to an emergency personnel not moving when they were in danger. It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more emergency personnel can rely on it.
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 Field Personnel work zone warning Not Applicable Moderate Low
Human Interfaces do not receive confidentiality ratings. A few false warnings should not have a bad consequence. When field personnel receive a warning they can look around and verify whether or not a vehicle is actually headed towards them. It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more field personnel can rely on it.
ITS Roadway Equipment Maint and Constr 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 Maint and Constr Management Center work zone warning status Moderate Moderate Moderate
There could potentially be sensitive information in the system activation or supporting information. This information flow also contains supporting verification, such as an image, that can also be used to verify the integrity of the message. The system should be able to operate properly if it misses a few messages. If a message is not received, the ITS RE should know. This is not the only source of information regarding an incident. If an incident is severe enough to need an immediate response, there are other indicators (such as someone calling 911) that would help alert people to the situation.
ITS Roadway Equipment Maint and Constr Vehicle OBE 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 Maint and Constr Vehicle OBE 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 Maint and Constr Vehicle OBE traffic images 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. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Often this flow will be used to support personal worker safety, which justifies MODERATE.
Maint and Constr Field Personnel ITS Roadway Equipment personnel monitoring Not Applicable Moderate Low
This is directly observable. Should be correct or the ITS Roadway Equipment may take actions that are inconsistent with personnel's actual location If not available, equipment will likely not take any action. This is the current situation, so until this data is expected to always be there, this should be LOW.
Maint and Constr Field Personnel Maint and Constr Vehicle OBE personnel monitoring Not Applicable Moderate Low
This is directly observable. Should be correct or the ITS Roadway Equipment may take actions that are inconsistent with personnel's actual location If not available, equipment will likely not take any action. This is the current situation, so until this data is expected to always be there, this should be LOW.
Maint and Constr 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
Maint and Constr Management Center ITS Roadway Equipment work zone warning device 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.
Maint and Constr Management Center Maint and Constr Vehicle OBE work zone warning device control Not Applicable Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This information should be accurate, but an incorrect information should not have a direct impact causing the loss of life or limb. The system should be able to operate properly if it misses a few messages. If a message is not received, the ITS RE should know.
Maint and Constr Vehicle OBE Driver driver information Not Applicable Moderate Moderate
This data is sent to all drivers and is also directly observable, by design. There are currently other visual and auditory indicators of an incident. Police will park their car with the lights (and possibly siren) on to indicate that a lane is closed. If incorrect information is sent to the driver, they will still have other cues indicating that an incident has occurred. If the current indicators are fully replaced by this system, then this would be raised to a HIGH. There are currently other visual and auditory indicators of an incident. Police will park their car with the lights (and possibly siren) on to indicate that a lane is closed. If incorrect information is sent to the driver, they will still have other cues indicating that an incident has occurred. If the current indicators are fully replaced by this system, then this would be raised to a HIGH.
Maint and Constr Vehicle OBE 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
Maint and Constr Vehicle OBE 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.
Maint and Constr Vehicle OBE Maint and Constr Field Personnel work zone warning Not Applicable Moderate Low
This is directly observable data. A few false warnings should not have a bad consequence. When field personnel receive a warning they can look around and verify whether or not a vehicle is actually headed towards them. It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more field personnel can rely on it.
Maint and Constr Vehicle OBE Maint and Constr Management Center work zone warning status Moderate Moderate Moderate
There could potentially be sensitive information in the system activation or supporting information. This information flow also contains supporting verification, such as an image, that can also be used to verify the integrity of the message. The system should be able to operate properly if it misses a few messages. If a message is not received, the emergency vehicle OBE should know. This is not the only source of information regarding an incident. If an incident is severe enough to need an immediate response, there are other indicators (such as someone calling 911) that would help alert people to the situation.
Maint and Constr Vehicle OBE Other MCV OBEs work zone warning notification Not Applicable Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This information should be accurate, but an incorrect information should not have a direct impact causing the loss of life or limb. The system should be able to operate properly if it misses a few messages. If a message is not received, the RSE should know.
Maint and Constr Vehicle OBE Personnel Device personnel safety warning Not Applicable High Low
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. A few false warnings should not have a bad consequence. When an emergency personnel receives a warning they can look around and verify whether or not a vehicle is actually headed towards them. However, a message saying it is safe when there is a car coming could lead to an emergency personnel not moving when they were in danger. It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more emergency personnel can rely on it.
Other MCV OBEs Maint and Constr Vehicle OBE work zone warning notification Not Applicable Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This information should be accurate, but an incorrect information should not have a direct impact causing the loss of life or limb. The system should be able to operate properly if it misses a few messages. If a message is not received, the RSE should know.
Personnel Device Maint and Constr Field Personnel personnel updates Low High Moderate
This data is informing the user of safety-related issues in the local transportation environment. It probably does not contain anything sensitive, and should not matter if another person can observe it. This is the information that is presented to the individual in a work zone or incident response area that may be unpredictable in its formation. If the user receives incorrect information, they may act in an unsafe manner. If this information is not made available to the pedestrian, then the user may be endangered. This is the not only mechanism the user may have to avoid potential dangers (they can observe directly).
Vehicle Basic Vehicle driver update information Low Moderate Moderate
This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
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
CTI 4001 RSU Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
Maint and Constr Management Center




System Requirements

No System Requirements