< < ST01 : ST02 : ST03 > >

ST02: Eco-Traffic Signal Timing

The Eco-Traffic Signal Timing service package is similar to current adaptive traffic signal control systems; however, the service package's objective is explicitly to optimize traffic signals for the environment rather than the current adaptive systems' objective, which is to enhance the intersection level of service or throughput, which might improve the intersection's environmental performance. The Eco-Traffic Signal Timing service package processes real-time and historical connected vehicle data at signalized intersections to reduce fuel consumption and overall emissions at the intersection, along a corridor, or for a region. It evaluates traffic and environmental parameters at each intersection in real time and adapts so that the traffic network is optimized using available green time to serve the actual traffic demands while minimizing the environmental impact.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Connected Vehicle Roadside Equipment Maintainer Connected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Operations Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Driver Roadway Owner Expectation of Roadway Condition Management
Driver Vehicle Operates
Emissions Management Center Maintainer Emissions Management Center Maintains
Emissions Management Center Manager Emissions Management Center Manages
Emissions Management Center Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Emissions Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Emissions Management Center Owner Emissions Management Center Maintainer System Maintenance Agreement
Emissions Management Center Owner Emissions Management Center Manager Operations Agreement
Emissions Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Traffic Management Center Owner Information Provision Agreement
Emissions Management Center Owner Traffic Management Center User Service Usage Agreement
Emissions Management Center Owner Traffic Operations Personnel Application Usage Agreement
Emissions Management Center Supplier Emissions Management Center Owner Warranty
ITS Roadway Equipment Maintainer ITS Roadway Equipment Maintains
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
ITS Roadway Equipment Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Emissions Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Emissions Management Center User Service Usage Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Traffic Management Center User Service Usage Agreement
ITS Roadway Equipment Owner Traffic Operations Personnel Application Usage Agreement
ITS Roadway Equipment Supplier ITS Roadway Equipment Owner Warranty
Roadway Maintainer Roadway Environment Maintains
Roadway Manager Roadway Environment Manages
Roadway Owner Roadway Maintainer System Maintenance Agreement
Roadway Owner Roadway Manager Operations Agreement
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 Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Traffic Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Traffic Management Center Owner ITS Roadway Equipment User Service Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Vehicle Characteristics Maintainer Vehicle Characteristics Maintains
Vehicle Characteristics Manager Vehicle Characteristics Manages
Vehicle Characteristics Owner Vehicle Characteristics Maintainer System Maintenance Agreement
Vehicle Characteristics Owner Vehicle Characteristics Manager Operations Agreement
Vehicle Characteristics Supplier Vehicle Characteristics Owner Warranty
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Vehicle Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Emissions Monitoring 1.5.10 Collect Vehicle Emissions Messages
RSE Environmental Monitoring 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.1.7 Collect Vehicle Environmental 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
1.5.10 Collect Vehicle Emissions Messages
1.5.12 Manage Eco Roadway Usage in Roadway
6.7.3.3 Provide Short Range Traveler Information
RSE Intersection Management 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.2.7.14 Manage Connected Signal Priority and Preemption Requests
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
1.5.10 Collect Vehicle Emissions Messages
RSE Traffic Monitoring 1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.1.7 Collect Vehicle Environmental Data
1.2.7.15 Process Intersection Safety Data
1.2.7.4 Process In-vehicle Signage Data
6.7.3.3 Provide Short Range Traveler Information
9.3.3.5 Manage Speeds at Roadside
Emissions Management Center Emissions Connected Vehicle Monitoring 1.5.1 Provide Emissions Operations Personnel Interface
1.5.11 Process Connected Vehicle Emissions Data
1.5.2 Process Pollution Data
1.5.3 Manage Pollution State Data Store
1.5.7 Manage Emissions and Pollution Reference Data Stores
1.5.8 Manage Emissions Archive Data
1.5.9 Manage Emissions State Data Store
5.4.8 Process Emissions Violations
Emissions Data Management 1.5.1 Provide Emissions Operations Personnel Interface
1.5.11 Process Connected Vehicle Emissions Data
1.5.2 Process Pollution Data
1.5.3 Manage Pollution State Data Store
1.5.6 Process Vehicle Emissions Data
1.5.7 Manage Emissions and Pollution Reference Data Stores
1.5.9 Manage Emissions State Data Store
5.4.8 Process Emissions Violations
ITS Roadway Equipment Roadway Basic Surveillance 1.1.1.1 Process Traffic Sensor Data
1.1.1.7 Process Road User Protection
1.1.2.11 Control Dynamic Lanes
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.3.1.3 Process Traffic Images
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
Roadway Emissions Monitoring 1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.2.7.9 Process Roadway Information Data
1.5.4 Detect Vehicle Emissions Levels
1.5.5 Detect Pollution and Noise Levels
Roadway Environmental Monitoring 1.1.1.3 Process Environmental Sensor Data
1.2.7.1 Process Indicator Output Data for Roads
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.2.7.9 Process Roadway Information Data
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
Roadway Field Management Station Operation 1.1.1.5 Provide Sensor Interface to Other Roadway Devices
1.2.7.13 Provide Device Interface for Field Management Stations
Roadway Signal Control 1.1.1.1 Process Traffic Sensor Data
1.2.7.1 Process Indicator Output Data for Roads
1.2.7.13 Provide Device Interface for Field Management Stations
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
Traffic Management Center TMC Basic Surveillance 1.1.2.1 Process Traffic Data for Storage
1.1.2.2 Process Traffic Data
1.1.2.3 Update Data Source Static Data
1.1.2.5 Process Vehicle Situation Data
1.1.2.8 Process Roadway Environmental Data
1.1.3 Generate Predictive Traffic Model
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.5 Exchange Data with Other Traffic Centers
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data
1.3.1.1 Analyze Traffic Data for Incidents
1.3.2.1 Store Possible Incident Data
1.3.2.5 Provide Current Incidents Store Interface
1.3.2.6 Manage Traffic Routing
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.5 Process Video Data
TMC Environmental Monitoring 1.1.2.5 Process Vehicle Situation Data
1.1.2.8 Process Roadway Environmental Data
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.4.4 Manage Traffic Archive Data
1.1.5 Exchange Data with Other Traffic Centers
1.2.4.3 Output In-vehicle Signage Data
1.2.4.7 Manage Roadway Warning System
1.2.8 Collect Traffic Field Equipment Fault Data
TMC Roadway Equipment Monitoring 1.2.8 Collect Traffic Field Equipment Fault Data
1.3.2.6 Manage Traffic Routing
TMC Signal Control 1.1.2.2 Process Traffic Data
1.1.2.5 Process Vehicle Situation Data
1.1.4.1 Retrieve Traffic Data
1.1.4.4 Manage Traffic Archive Data
1.1.5 Exchange Data with Other Traffic Centers
1.2.1 Select Strategy
1.2.2.2 Determine Indicator State for Road Management
1.2.4.1 Output Control Data for Roads
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data
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 Emissions Monitoring 3.1.3 Process Vehicle On-board Data
3.1.7 Process Vehicle Emissions Status
3.2.3.5.1 Process General Vehicle Sensor Data
6.7.1.4 Update Vehicle Navigable Map Database
Vehicle Environmental Monitoring 3.1.3 Process Vehicle On-board Data
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.1 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information Interface

Physical

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


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (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.
Emissions Management Center Center The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
MMV User Personal The 'MMV User' represents the person that operates a micromobility vehicle (MMV). Included are cyclists and operators of other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The MMV User participates in ITS services that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, and in particular bicyclists that sometimes share motor vehicle lanes, these MMV users provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety. The MMV User originates requests and receives information that reflects the interactions which might be useful to all users, regardless of vehicle type.
Pedestrian Personal The 'Pedestrian' represents a person traveling on foot. Pedestrians participate in ITS services that support safe, shared use of the transportation network. Included are visually impaired travelers who travel through portions of the transportation network and interact with ITS systems. They provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety
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.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Vehicle Characteristics Vehicle 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management.

Includes Functional Objects:

Functional Object Description Physical Object
Emissions Connected Vehicle Monitoring 'Emissions Connected Vehicle Monitoring' collects emissions data reported by passing vehicles and uses this data to support air quality management and planning. Coordination with traffic management supports air quality-responsive management of traffic. Emissions Management Center
Emissions Data Management 'Emissions Data Management' collects and stores air quality and vehicle emissions information by remotely monitoring and controlling area wide and point sensors. General air quality measures are distributed as general traveler information and also may be used in demand management programs. Collected roadside emissions are analyzed and used to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards. Emissions Management Center
Roadway Basic Surveillance 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. ITS Roadway Equipment
Roadway Emissions Monitoring 'Roadway Emissions Monitoring' monitors emissions and general air quality and communicates the collected information back to the Emissions Management Center where it can be monitored, analyzed, and used. This functional object supports point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures. ITS Roadway Equipment
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 Field Management Station Operation 'Roadway Field Management Station Operation' supports direct communications between field management stations and the local field equipment under their control. ITS Roadway Equipment
Roadway Signal Control 'Roadway Signal Control' includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. ITS Roadway Equipment
RSE Emissions Monitoring 'RSE Emissions Monitoring' collects emissions data from passing vehicles that are equipped with short range communications capability and have the capability to collect and report emissions data. The collected data includes current emissions as measured or calculated by on-board equipment. The functional object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. Connected Vehicle Roadside Equipment
RSE Environmental Monitoring 'RSE Environmental Monitoring' collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The functional object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This functional object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications. Connected Vehicle Roadside Equipment
RSE Intersection Management 'RSE Intersection Management' uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner. Connected Vehicle Roadside Equipment
RSE Traffic Monitoring 'RSE Traffic Monitoring' monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident. Connected Vehicle Roadside Equipment
TMC Basic Surveillance 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. Traffic Management Center
TMC 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 Equipment Monitoring 'TMC Roadway Equipment Monitoring' monitors the operational status of field equipment and detects failures. It presents field equipment status to Traffic Operations Personnel and reports failures to the Maintenance and Construction Management Center. It tracks the repair or replacement of the failed equipment. The entire range of ITS field equipment may be monitored including sensors (traffic, infrastructure, environmental, security, speed, etc.) and devices (highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security surveillance equipment, etc.). Traffic Management Center
TMC Signal Control 'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. Traffic Management Center
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, 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. Vehicle
Vehicle Emissions Monitoring 'Vehicle Emissions Monitoring' directly measures or estimates current and average vehicle emissions and makes this data available to the driver and connected vehicle infrastructure systems. Vehicle
Vehicle Environmental Monitoring 'Vehicle Environmental Monitoring' collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control systems. Vehicle

Includes Information Flows:

Information Flow Description
crossing call Non-motorized user request to cross the roadway. This is an overt request from a pedestrian, micromobility vehicle user (e.g., cyclist), or other vulnerable road user. This overt request may be a physical button push or hovering or gesturing in the vicinity of the button that supports contactless activation.
crossing permission Information provided to guide and warn pedestrians, micromobility vehicle users (e.g., cyclists), and other crosswalk users. It includes crossing request acknowledgment, current crossing permission, crossing time remaining, and real-time warnings of safety threats.
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
emissions monitoring application information Data used to configure and control roadside equipment applications that monitor emissions-related data reported by passing vehicles. The parameters include identification of the emissions-related data to be monitored and thresholds for aggregating, filtering, and reporting the collected data.
emissions monitoring application status Emissions monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of emissions data collected.
emissions situation data Emissions-related data as measured and reported by connected vehicles. This flow carries aggregated and filtered data including average and current emissions reported by vehicles as well as associated data (vehicle profiles and speeds) that can be used to estimate aggregate emissions.
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.
environmental situation data Aggregated and filtered vehicle environmental data collected from vehicle safety and convenience systems including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. This information flow represents the aggregated and filtered environmental data sets that are provided by the RSE to the back office center. Depending on the RSE configuration and implementation, the data set may also include environmental sensor station data collected by the RSE.
intersection control status Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection management application info Intersection and device configuration data, including intersection geometry, and warning parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
intersection management application status Infrastructure application status reported by the RSE. This includes current operational state and status of the RSE and a log of operations.
mobile source emissions data Measured and/or estimated emissions at point locations from mobile sources including cars and light trucks, heavy trucks and buses. Where applicable, this flow may also include emissions measures or estimates from non-road engines and portable equipment at the location.
right-of-way request notification Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.
signal control commands Control of traffic signal controllers or field masters including clock synchronization.
signal control device configuration Data used to configure traffic signal control equipment including local controllers and system masters.
signal control plans Traffic signal timing parameters including minimum green time and interval durations for basic operation and cycle length, splits, offset, phase sequence, etc. for coordinated systems.
signal control status Operational and status data of traffic signal control equipment including operating condition and current indications.
signal fault data Faults reported by traffic signal control equipment.
signal service request A call for service or extension for a signal control phase that is issued by the RSE for connected vehicles approaching an intersection and/or pedestrians at a crosswalk. This flow identifies the desired phase and service time.
signal system configuration Data used to configure traffic signal systems including configuring control sections and mode of operation (time based or traffic responsive).
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 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.
traffic situation data Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection.
vehicle characteristics The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles.
vehicle emissions data Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
vehicle environmental data Data from vehicle safety and convenience systems that can be used to estimate environmental and infrastructure conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, vertical acceleration and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle reported emissions Current and average vehicle emissions data as measured by vehicle diagnostics systems and reported by the vehicle.

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

Associated Objective Categories

Objective Category
Arterial Management: Delay
Arterial Management: Reliability
Arterial Management: Traffic Signal Management
Environment: Clean Air and Climate Change
System Efficiency: Energy Consumption

Associated Objectives and Performance Measures

Objective Performance Measure
Crash data for all arterials in the region is reviewed every X years to determine if signal adjustments can be made to address a safety issue. Number of years between reviews of crash data on all arterials for possible signal timing impacts.
Decrease the seconds of control delay per vehicles on arterial roads by X percent in Y years. (Control delay is defined as the portion of the total delay attributed to traffic signal operation for signalized intersections). Control delay seconds per vehicle.
Increase the miles of arterials in the region operating at level of service (LOS) Z by X percent in Y years. Percent of arterial miles in region operating at LOS Z.
Increase the number of intersections running in a coordinated, closed-loop, or adaptive system by X percent in Y years. Number of intersections running in a coordinated, closed-loop, or adaptive system.
Maintain a program of evaluating X percent of signals for retiming every Y years. Number of traffic signals evaluated for retiming.
Reduce buffer index on arterials during peak and off-peak periods by X percent in Y years. The buffer index (represents the extra time (buffer) travelers add to their average travel time when planning trips in order to arrive on-time 95 percent of the time).
Reduce carbon dioxide (CO2) emissions to X percent below year Y by year Z. Carbon dioxide emissions - tons per day
Reduce delay associated with incidents on arterials by X percent by year Y. Hours of delay associated with incidents.
Reduce emissions of coarse particulates (PM10) by X percent by year Y. Course particular (PM10) levels - micrograms per cubic meter
Reduce emissions of coarse particulates (PM10) by X percent by year Y. Course particulate (PM10) emissions - tons per day
Reduce emissions of fine particulates (PM2.5) by X percent by year Y. Fine particulate (PM2.5) emissions - tons per day
Reduce emissions of fine particulates (PM2.5) by X percent by year Y. Fine particulate (PM2.5) levels - micrograms per cubic meter
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.
Special timing plans are available for use during freeway incidents, roadway construction activities, or other special events for X miles of arterials in the region by year Y. Number of miles of arterials that have at least one special timing plan for incidents, construction, or events.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system. Emissions Connected Vehicle Monitoring 01 The center shall collect emissions data reported by passing connected vehicles.
Emissions Data Management 05 The center shall provide the measured and/or estimated emissions collected from mobile sources to traffic management.
Roadway Basic 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.
04 The field element shall return sensor and CCTV system operational status to the controlling center.
Roadway Emissions Monitoring 01 The field element shall include emissions sensors that detect levels of emissions from individual vehicles, under center control.
02 The field element shall collect vehicle emissions data from passing vehicles.
03 The field element shall analyze collected vehicle emissions data against reference data to determine whether or not a vehicle is violating the acceptable levels of emissions, and shall return this analysis to a center for possible enforcement action.
10 The field element shall provide vehicle emission data to centers.
Roadway Environmental Monitoring 10 The field element shall provide weather and road surface condition data to centers.
RSE Emissions Monitoring 01 The field element shall collect emissions data including current emissions as measured or calculated by on-board equipment, from passing connected vehicles that have the capability to collect and report emissions data.
03 The field element shall send the collected information back to a center for processing and distribution.
RSE Environmental Monitoring 01 The field element shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
RSE Traffic Monitoring 01 The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
02 The field element shall aggregate and forward collected probe information to the 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.
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 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 Equipment Monitoring 01 The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.
02 The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.
05 The center shall collect environmental sensor operational status.
Vehicle Basic Safety Communication 06 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Emissions Monitoring 02 The vehicle shall provide the vehicle emissions information to infrastructure systems.
Vehicle Environmental Monitoring 04 The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications.
02 Traffic Operations need to process collected data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system. TMC Signal Control 13 The center shall process collected traffic and environmental data from sensors and connected vehicles.
03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections. Roadway Field Management Station Operation 01 The field element shall accept configuration information from the center.
02 The field element shall pass data provided by the center to local field devices and report data from the field devices back to the center.
Roadway Signal Control 01 The field element shall control traffic signals under center control.
02 The field element shall respond to pedestrian crossing requests by accommodating the pedestrian crossing.
03 The field element shall provide the capability to notify the traffic management center of pedestrian calls and pedestrian accommodations.
04 The field element shall report the current signal control information to the center.
06 The field element shall return traffic signal controller operational status to the center.
07 The field element shall return traffic signal controller fault data to the center.
16 The field element shall receive request for signal change from an emissions/environmental field device.
17 The field element shall report current emissions/environmental priority status to the center.
RSE Intersection Management 03 The field element shall send the infrastructure application status to the operations center.
08 The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
RSE Traffic Monitoring 03 The field element shall aggregate and forward collected probe information to other field elements.
TMC Signal Control 09 The center shall implement control plans to coordinate signalized intersections based on data from sensors and connected vehicles.
12 The center shall adjust signal timing in respond to traffic and environmental parameters at each intersection in real time and adapts so that the traffic network is optimized using available green time to serve the actual traffic demands while minimizing the environmental impact.

Related Sources

Document Name Version Publication Date
Eco-Signal Operations: Operational Concept Final 10/1/2013


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
Emissions Management Center Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate High Moderate Class 3
Roadway Environment Not Applicable Low Low Class 1
Traffic Management Center Moderate High Moderate Class 3
Vehicle Moderate Moderate Moderate Class 2
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 Emissions Management Center emissions monitoring application status Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases. If this is compromised, it could send unnecessary maintenance workers, or worse report plausible data that is erroneous. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning.
Connected Vehicle Roadside Equipment Emissions Management Center emissions situation data Low Moderate Low
Probably not sensitive information, no harm in this data being captured by unintended party. This flow does not correlate specific vehicles with any emissions data. At least some guarantee of correctness should be had with this data. It could be used to modify transit/traffic strategies over a large area ("its a code ORANGE day out there, don't run") that change behavior for a large number of people. This could be MODERATE if emissions information is critical to decision making.
Connected Vehicle Roadside Equipment ITS Roadway Equipment signal service request Not Applicable Moderate Low
info is not confidential or encrypted requests should be accurate and not tampered with, otherwise incorrect or malicious requests could be granted which could lead to delays requests should be timely and available immediately but availability cannot be guaranteed over a wireless medium; also worst case scenario is the vehicle or pedestrian has to wait for the appropriate signal
Connected Vehicle Roadside Equipment ITS Roadway Equipment traffic situation data Moderate Moderate Moderate
Aggregated messages may have more privacy implications than individual ones, especially if an attacker can attack more than one RSE-to-TMC connection at once. This information is used to help with incident detection. It should be verified to ensure that it is not incorrectly influencing this.THEA: only limited adverse effect if raw/processed connected vehicle data is bad/compromised; could be LOW for ISIG This information is used as supplemental information. It should operate correctly if not every single message is received. THEA: only limited adverse effect if info is not timely/readily available, could be LOW for ISIG
Connected Vehicle Roadside Equipment Traffic Management Center environmental situation data Low Moderate Moderate
Little to no impact if this data is observed Only limited adverse effect if environmental data from vehicle safety and convenience systems is bad/compromised; can cope with some bad data; DISC: WYO believes this to be MODERATE HIGH. Changed from THEA's LOW inferring severity of weather data in Wyoming Only limited adverse effect of info is not timely/readily available. DISC: WYO believes this to be MODERATE. Changed from THEA's LOW inferring severity of weather data in Wyoming
Connected Vehicle Roadside Equipment Traffic Management Center intersection management application status Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases. If this is compromised, it could send unnecessary maintenance workers, or worse report plausible data that is erroneous. From THEA: should be able to cope with some bad information on the status and record of alerts/warnings; aggregate info; however could cause appearance of excessive traffic violations or unnecessary maintenance caused if data is compromised (operational state, status, log); should not affect the application functionality Incident status information should be presented in timely fashion as large scale mobility and safety issues are related. There are other mechanisms for reporting this information however, thus MODERATE. From THEA: Only limited adverse effect of info is not timely/readily available
Connected Vehicle Roadside Equipment Traffic Management Center traffic situation data Moderate Moderate Low
Aggregated messages may have more privacy implications than individual ones, especially if an attacker can attack more than one RSE-to-TMC connection at once. only limited adverse effect if raw/processed connected vehicle data is bad/compromised; DISC: NYC believes this to be MODERATE: As investigation might be triggered if RF quality is reported as low, this data should be trusted. RES: Agree wih NYC. only limited adverse effect of info is not timely/readily available. NYC: This data is purely for statistical purposes so low availability does not harm the [RSE RF Monitoring] application.
Driver Vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Emissions Management Center Connected Vehicle Roadside Equipment emissions monitoring application information Moderate Moderate Low
This is a control flow, so should be obfuscated to make it more difficult for a 3rd party to manipulate the RSE. Control parameters need to be correct and not corrupted so that the owner of the RSE and the receiver of the RSE's data get what they need from it. This information probably does not need to be changed very often, and if it is not available then likely the flow it controls (emissions data flows to the DDS/EMC) are down as well.
Emissions Management Center Traffic Management Center mobile source emissions data Low Moderate Moderate
Probably not sensitive information, no harm in this data being captured by unintended party if this flow does not correlate specific vehicles with any emissions data. If specific vehicles are associated with data, this would be MODERATE. At least some guarantee of correctness should be had with this data. It could be used to modify transit/traffic strategies over a large area ("its a code ORANGE day out there, don't run") that change behavior for a large number of people. While the source flows from RSEs are considered LOW, this is an aggregated flow, so the impact of an outage is larger. If this flow exists, it is probably used for decision-making and any loss of this flow has an impact.
ITS Roadway Equipment Connected Vehicle Roadside Equipment intersection control status Low High Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. If this is compromised, the Roadway Equipment and Roadside Equipment will be sending messages that are inconsistent with each other, leading to confusion and possible accidents. If this is down, the RSE doesn't get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability could be interpreted as having the same value as Integrity. However, this data is semi-predictable and there are other indicators (such as the lights themselves) of the intersection status.
From NYC, who believe this should be HIGH for some applications: If this is down, the RSE doesn't get the information it needs to stay in synch with the actual signal state, reducing or eliminating the value add from having this application. The RSE must detect a lack of availability and choose not to send out-of-date information, so a failure of availability cannot have worse consequences than a failure of integrity which we have previously assessed at HIGH.
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 Emissions Management Center vehicle emissions data Moderate Moderate Low
Contains vehicle identity, which should be protected from casual viewing, and maps that to various emissions parameters. As this may imply legal issues (over-emitting etc.), the data should be kept confidential to protect the vehicle owner. As this contains information that could be used to grant permitting (emissions passing) or issue penalites (over-emitting), a corruption of this data could result in the wrong action being taken, revenue lost or inappropriately gained, permit incorrectly granted or denied. Could be MODERATE for those areas where emissions are high priority items. Generally LOW given that most emissions testing is done in person now. As systems come to rely on remote sensing, this may become MODERATE.
ITS Roadway Equipment MMV User crossing permission Not Applicable High Low
This data is intentionally transmitted to everyone via a broadcast. Although pedestrians have a responsibility to make sure the road is safe before they cross, they may react instinctively to incorrect information and be led to cross at unsafe times if they get incorrect information. Also, if the traffic signals are wrong and an accident happens, the pedestrian involved could sue, causing financial loss and other undesirable outcomes. It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service.
ITS Roadway Equipment Pedestrian crossing permission Not Applicable High Low
This data is intentionally transmitted to everyone via a broadcast. Although pedestrians have a responsibility to make sure the road is safe before they cross, they may react instinctively to incorrect information and be led to cross at unsafe times if they get incorrect information. Also, if the traffic signals are wrong and an accident happens, the pedestrian involved could sue, causing financial loss and other undesirable outcomes. It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service.
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 right-of-way request notification Low Moderate Moderate
This can be reasonably guessed based on observing the ITS RE's environment. It is obvious when a bus approaches an intersection. Invalid messages could lead to an unauthorized user gaining signal priority at an intersection. This could also be used to delay traffic, which could lead to a financial impact on the community. However, the traffic signal will have controls in place to ensure that it does not display an illegal configuration (such as green in every direction). Even if all of the Right-of-way Requests are not passed along from an ITS RE, the intersection will still operate as normal. There are other existing methods to assist a right-of-way requesting vehicle safely traveling through an intersection, such as lights and sirens, which prevent this from being a HIGH. DISC: THEA and NYC believe this to be LOW: "not necessary for the app to work; can cope with not having immediately available data"
ITS Roadway Equipment Traffic Management Center signal control status Low High Moderate
The current conditions of an ITS RE are completely observable, by design. This influences the TMC response to a right-of-way request. It should be as accurate as the right-of-way request themselves. For some applications (ISIG) this need only be moderate. Per THEA: info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC. DISC: THEA believes this to be MODERATE: "info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC; should be as accurate as the right of way request". NYC:TMC doesn't play an active role in this application, i.e. even if the information contained in this flow were incorrect, it is unlikely to affect the outcome of this application one way or the other. On some applications NYC has this MODERATE though. RES: This value can obviously change a lot depending on the application context. The TMC will need the current status of the ITS RE in order to make an educated decision. If it is unavailable, the system is unable to operate. However, a few missed messages will not have a catastrophic impact. From NYC: TMC doesn't play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This value can change a lot depending on the application context.
ITS Roadway Equipment Traffic Management Center signal fault data Low High Moderate
The current conditions of an ITS RE are completely observable, by design. 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.
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.
MMV User ITS Roadway Equipment crossing call Not Applicable High Low
The "Not Applicable" group includes information flows that do not actually carry information; for example, flows that represent the physical environment. Although pedestrians have a responsibility to make sure the road is safe before they cross, and should ensure that they are detected by pedestrian detection systems, they may not always be detected and be led to cross at unsafe times if the ITS RE obtains incorrect information. It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service.
Pedestrian ITS Roadway Equipment crossing call Not Applicable High Low
The "Not Applicable" group includes information flows that do not actually carry information; for example, flows that represent the physical environment. Although pedestrians have a responsibility to make sure the road is safe before they cross, and should ensure that they are detected by pedestrian detection systems, they may not always be detected and be led to cross at unsafe times if the ITS RE obtains incorrect information. It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service.
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 Connected Vehicle Roadside Equipment intersection management application info Moderate High Low
proprietary configuration data with warning parameters and thresholds should be accurate and not be tampered with; could enable outside control of application should be timely and readily available or may not be able to restart/reset; however, should be able to operate on a default configuration and/or stop sending messages
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 signal control commands 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. DISC: NYC believes this to be LOW: "The result of this will be directly observable." Invalid messages could lead to an unauthorized user gaining control of an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community. DISC: NYC believes this to be MODERATE: The signal timing is critical to the intersection operation; incorrect signal timing can lead to significant congestion and unreliable operation; while unsafe operation is controlled by the cabinet monitoring system, attackers could "freeze" the signal or call a preemption. RES: This will vary depending on the application and implementation. These messages are important to help with preemption and signal priority applications. Without them, these applications mayl not work. However, if these signals are not received, the ITS RE will continue to function using its default configuration. The TMC should have an acknowledgement of the receipt of a message. DISC: NYC blieves this to be LOW: TMC doesn't play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other.
RES: This will vary depending on the application and implementation.
Traffic Management Center ITS Roadway Equipment signal control device configuration 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. DISC: THEA believes this to be LOW: "encrypted, authenticated, proprietary; however will not cause harm if seen, traffic light information is visible." 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; includes local controllers and system masters; tampering with configurations could cause delays along with major safety issues 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: should be timely and readily available; however, should be able to function using a default configuration
Traffic Management Center ITS Roadway Equipment signal control plans 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. DISC: THEA believes this to be LOW: "encrypted, authenticated, proprietary; but the result is directly observable from traffic lights 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; tampering with these plans could cause delays along with major safety issues 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: should be timely and readily available; coordinated with other systems; however, should be able to function using a default configuration
Traffic Management Center ITS Roadway Equipment signal system configuration Low High Moderate
encrypted, authenticated, proprietary; however, the result is directly observable from traffic lights proprietary info that should not be tampered with; data used to configure traffic signal systems; could cause significant delays and traffic issues if compromised should be readily available; configurations can be time
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 Traffic Operations Personnel traffic operator data Moderate Moderate Moderate
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Traffic Operations Personnel Traffic Management Center traffic operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Vehicle Connected Vehicle Roadside Equipment vehicle environmental data Low Moderate Low
Little abusive potential for capturing the information in this flow as designed. Could be moderate if this contains PII related information, but considered for now to not include any PII; DISC: WYO believes Vehicle to Center versions of this flow to be MODERATE as center penetrations could more easily garner aggregate user data that might be used for mischief. Some minimal guarantee of data integrity is necessary for all C-ITS flows. DISC THEA believes this to be LOW: Data should be accurate and not tampered with but should be able to cope with some bad data in traffic/environmental condition monitoring; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE data should be timely and readily available, but limited adverse effect; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE
Vehicle Connected Vehicle Roadside Equipment vehicle location and motion for surveillance Not Applicable Moderate Moderate
This is directly observable data; DISC: WYO believes this to be MODERATE Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW
Vehicle Connected Vehicle Roadside Equipment vehicle reported emissions Moderate Moderate Moderate
Contains PII describing the vehicle and its operating characteristics, which if observed could be used against the vehicle owner. Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Initially MODERATE, unlikely to be set to HIGH unless emissions operations are the highest priority. Important for low emissions zone operations; without accurate and timely information, applications relying on this data will not function. While initially MODERATE, could be LOW if the priority for emissions-related applications are similarly low.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
CTI 4001 RSU Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5201 ATC Advanced Transportation Controller ITS Roadway Equipment
ITE 5202 ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE 5401 ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Emissions Management Center
ITS Roadway Equipment
Traffic Management Center
NEMA TS2 Traffic Controller Assemblies Traffic Controller Assemblies with NTCIP Requirements ITS Roadway Equipment




System Requirements

System Requirement Need
001 The system shall collect emissions data reported by passing connected vehicles. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
002 The system shall provide the measured and/or estimated emissions collected from mobile sources to traffic management. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
003 The system shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
004 The system shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
005 The system 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). 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
006 The system shall remotely control devices to detect traffic. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
007 The system 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. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
008 The system shall receive aggregated and processed vehicle environmental data collected from vehicle safety and convenience systems through the connected vehicle roadside equipment. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
009 The system shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
010 The system shall collect and store CCTV surveillance system (traffic, pedestrian) operational status. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
011 The system shall collect environmental sensor operational status. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
012 The system shall implement control plans to coordinate signalized intersections based on data from sensors and connected vehicles. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
013 The system shall adjust signal timing in respond to traffic and environmental parameters at each intersection in real time and adapts so that the traffic network is optimized using available green time to serve the actual traffic demands while minimizing the environmental impact. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
014 The system shall process collected traffic and environmental data from sensors and connected vehicles. 02 Traffic Operations need to process collected data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
015 The system shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
016 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
017 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
018 The system shall include emissions sensors that detect levels of emissions from individual vehicles, under center control. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
019 The system shall collect vehicle emissions data from passing vehicles. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
020 The system shall analyze collected vehicle emissions data against reference data to determine whether or not a vehicle is violating the acceptable levels of emissions, and shall return this analysis to a center for possible enforcement action. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
021 The system shall provide vehicle emission data to centers. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
022 The system shall provide weather and road surface condition data to centers. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
023 The system shall accept configuration information from the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
024 The system shall pass data provided by the center to local field devices and report data from the field devices back to the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
025 The system shall control traffic signals under center control. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
026 The system shall respond to pedestrian crossing requests by accommodating the pedestrian crossing. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
027 The system shall provide the capability to notify the traffic management center of pedestrian calls and pedestrian accommodations. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
028 The system shall report the current signal control information to the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
029 The system shall return traffic signal controller operational status to the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
030 The system shall return traffic signal controller fault data to the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
031 The system shall receive request for signal change from an emissions/environmental field device. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
032 The system shall report current emissions/environmental priority status to the center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
033 The system shall collect emissions data including current emissions as measured or calculated by on-board equipment, from passing connected vehicles that have the capability to collect and report emissions data. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
034 The system shall send the collected information back to a center for processing and distribution. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
035 The system shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
036 The system shall send the infrastructure application status to the operations center. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
037 The system shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
038 The system shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
039 The system shall aggregate and forward collected probe information to the center. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
040 The system shall aggregate and forward collected probe information to other field elements. 03 Traffic Operations need to be able to manage and implement control plans using collected data, including environmental data, in order to coordinate signalized intersections.
041 The system shall exchange location and motion information with roadside equipment and nearby vehicles. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
042 The system shall provide the vehicle emissions information to infrastructure systems. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.
043 The system shall transmit environmental probe data to field equipment located along the roadway using short range communications. 01 Traffic Operations need to collect data, including environmental data, to accurately know current and forecasted conditions in order to improve the traffic signal system.