WX01: Weather Data Collection
This service package collects current road and weather conditions using data collected from environmental sensors deployed on and about the roadway. It also collects data from vehicles in the road network that can be used to directly measure or infer current environmental conditions. It leverages vehicle on-board systems that measure temperature, sense current weather conditions (rain and sun sensors) and also can monitor aspects of the vehicle operational status (e.g., use of headlights, wipers, and traction control system) to gather information about local environmental conditions. In addition, environmental sensor systems located on Maintenance and Construction Vehicles are also potential data sources. The collected environmental data is used by the Weather Information Processing and Distribution service package to process the information and make decisions on operations. The collected environmental data may be aggregated, combined with data attributes and sent to meteorological systems for data qualification and further data consolidation. The service package may also request and receive qualified data sets from meteorological systems.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
- Implementations
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 | Maint and Constr Management Center Owner | Information Provision Agreement |
Connected Vehicle Roadside Equipment Owner | Traffic Management Center Owner | Information Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle OBE Owner | Expectation of Information Provision |
Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
ITS Roadway Equipment Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
ITS Roadway Equipment Owner | Maint and Constr Vehicle OBE Owner | Expectation of Information Provision |
ITS Roadway Equipment Owner | Surface Transportation Weather Service Owner | Information Provision Agreement |
ITS Roadway Equipment Owner | Traffic Management Center Owner | Information Exchange Agreement |
ITS Roadway Equipment Owner | Weather Service System Owner | Information Provision Agreement |
ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
Maint and Constr Center Personnel | Maint and Constr Management Center | Operates |
Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
Maint and Constr Management Center Manager | Maint and Constr Center Personnel | System Usage Agreement |
Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
Maint and Constr Management Center Owner | ITS Roadway Equipment Owner | Information Exchange Agreement |
Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
Maint and Constr Management Center Owner | Maint and Constr Vehicle OBE Owner | Information Exchange Agreement |
Maint and Constr Management Center Owner | Surface Transportation Weather Service Owner | Information Exchange Agreement |
Maint and Constr Management Center Owner | Traffic Management Center Owner | Information Exchange Agreement |
Maint and Constr Management Center Owner | Transportation Information Center Owner | Information Exchange Agreement |
Maint and Constr Management Center Owner | Weather Service System Owner | Information Exchange Agreement |
Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
Maint and Constr Vehicle OBE Maintainer | Maint and Constr Vehicle OBE | Maintains |
Maint and Constr Vehicle OBE Manager | Maint and Constr Vehicle OBE | Manages |
Maint and Constr Vehicle OBE Owner | ITS Roadway Equipment Owner | Expectation of Data Provision |
Maint and Constr Vehicle OBE Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
Maint and Constr Vehicle OBE Owner | Maint and Constr Vehicle OBE Maintainer | System Maintenance Agreement |
Maint and Constr Vehicle OBE Owner | Maint and Constr Vehicle OBE Manager | Operations Agreement |
Maint and Constr Vehicle OBE Supplier | Maint and Constr Vehicle OBE Owner | Warranty |
Surface Transportation Weather Service Maintainer | Surface Transportation Weather Service | Maintains |
Surface Transportation Weather Service Manager | Surface Transportation Weather Service | Manages |
Surface Transportation Weather Service Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
Surface Transportation Weather Service Owner | Surface Transportation Weather Service Maintainer | System Maintenance Agreement |
Surface Transportation Weather Service Owner | Surface Transportation Weather Service Manager | Operations Agreement |
Surface Transportation Weather Service Owner | Traffic Management Center Owner | Information Exchange Agreement |
Surface Transportation Weather Service Supplier | Surface Transportation Weather Service Owner | Warranty |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Manager | Traffic Operations Personnel | System Usage Agreement |
Traffic Management Center Owner | Connected Vehicle Roadside Equipment Owner | Information Exchange Agreement |
Traffic Management Center Owner | ITS Roadway Equipment Owner | Information Exchange Agreement |
Traffic Management Center Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
Traffic Management Center Owner | Surface Transportation Weather Service Owner | Information Exchange Agreement |
Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
Traffic Management Center Owner | Weather Service System Owner | Information Exchange Agreement |
Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
Traffic Operations Personnel | Traffic Management Center | Operates |
Transportation Information Center Maintainer | Transportation Information Center | Maintains |
Transportation Information Center Manager | Transportation Information Center | Manages |
Transportation Information Center Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
Vehicle OBE Maintainer | Vehicle OBE | Maintains |
Vehicle OBE Manager | Vehicle OBE | Manages |
Vehicle OBE Owner | Connected Vehicle Roadside Equipment Owner | Expectation of Data Provision |
Vehicle OBE Owner | Transportation Information Center Owner | Information Provision Agreement |
Vehicle OBE Owner | Vehicle OBE Maintainer | System Maintenance Agreement |
Vehicle OBE Owner | Vehicle OBE Manager | Operations Agreement |
Vehicle OBE Supplier | Vehicle OBE Owner | Warranty |
Weather Service System Maintainer | Weather Service System | Maintains |
Weather Service System Manager | Weather Service System | Manages |
Weather Service System Owner | Maint and Constr Management Center Owner | Information Exchange Agreement |
Weather Service System Owner | Traffic Management Center Owner | Information Exchange Agreement |
Weather Service System Owner | Weather Service System Maintainer | System Maintenance Agreement |
Weather Service System Owner | Weather Service System Manager | Operations Agreement |
Weather Service System Supplier | Weather Service System Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram

Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. 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. |
ITS Roadway Equipment | Field | 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included. |
Maint and Constr Center Personnel | Center | The people that directly interface with a Maintenance and Construction Management Center. These personnel interact with fleet dispatch and management systems, road maintenance systems, incident management systems, work plan scheduling systems, and work zone 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. |
Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
Maint and Constr Vehicle OBE | Vehicle | The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles. |
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. |
Surface Transportation Weather Service | Center | The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions. |
Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Traffic Operations Personnel | Center | 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario. |
Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
Vehicle OBE | Vehicle | The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. 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 OBE 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 OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. 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. |
Weather Service System | Center | The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
MCM Environmental Information Collection | 'MCM Environmental Information Collection' collects current road and weather conditions using data collected from environmental sensors deployed on and about the roadway. In addition to fixed sensor stations at the roadside, this functional object also collects environmental information from sensor systems located on Maintenance and Construction Vehicles. It also collects current and forecast environmental conditions information that is made available by other systems. The functional object aggregates the sensor system data and provides it, along with data attributes to other applications. | Maint and Constr Management Center |
MCV Environmental Monitoring | 'MCV Environmental Monitoring' collects current road and surface weather conditions from sensors on-board the maintenance and construction vehicle or by querying fixed sensors on or near the roadway. Environmental information including road surface temperature, air temperature, and wind speed is measured and spatially located and time stamped, and reported back to a center. | Maint and Constr Vehicle OBE |
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 |
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 |
TIC Data Collection | 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. | Transportation Information 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 |
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 OBE |
Includes Information Flows:
Information Flow | Description |
---|---|
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 conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included. |
environmental conditions data status | Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided. |
environmental monitoring application info | Environmental monitoring application parameters and thresholds that control the filtering, aggregation, and range of measures that are collected, derived, and reported. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
environmental monitoring application status | Environmental monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation. |
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 sensors control | Data used to configure and control environmental sensors. |
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. |
maint and constr center personnel input | User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination. |
maint and constr operations information presentation | Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning. |
qualified environmental conditions 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) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included. |
road network environmental situation data | Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region. |
traffic operator data | Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
traffic operator input | User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
vehicle 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 situation data parameters | A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
Associated Objective Categories 
Objective Category |
---|
Travel Weather Management: Disseminating Information |
Travel Weather Management: Road Weather Information System Coverage |
Associated Objectives and Performance Measures 

Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. | MCM Environmental Information Collection | 01 | The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. |
02 | The center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
07 | The center shall respond to control data from center personnel regarding environmental sensor control and weather data collection. | |||
08 | The center shall collect operational status for the roadside and vehicle-based environmental sensor equipment. | |||
09 | The center shall collect fault data for the roadside and vehicle-based environmental sensor equipment for repair. | |||
10 | The center shall collect environmental data from sensors that measure road surface temperature, moisture, icing, salinity, and other measures. | |||
Roadway Environmental Monitoring | 01 | The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. | ||
02 | The field element shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
04 | The field element's environmental sensors shall be remotely controlled by a traffic management center. | |||
06 | The field element's environmental sensors shall be remotely controlled by a maintenance and construction vehicle. | |||
07 | The field element shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle. | |||
08 | The field element shall provide environmental sensor equipment fault indication to the controlling center or maintenance vehicle. | |||
09 | The field element shall remotely aggregate environmental sensor data with environmental data collected from maintenance and construction vehicles. | |||
10 | The field element shall provide weather and road surface condition data to centers. | |||
11 | The field element shall provide weather and road surface condition data to maintenance and construction vehicles. | |||
12 | The field equipment shall provide environmental sensor data to the Connected Vehicle Roadside Equipment. | |||
RSE Environmental Monitoring | 03 | The field element shall collect environmental monitoring data from sensors, including ambient air quality, emissions, temperature, precipitation, and other road weather information. | ||
04 | The field element shall provide application status to the center for monitoring. | |||
TMC Environmental Monitoring | 01 | The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. | ||
02 | The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | |||
02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. | MCV Environmental Monitoring | 01 | The maintenance and construction vehicle shall collect environmental data from on-board sensors, including air temperature, wind speed, surface temperature, traction conditions, etc. |
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. | ||
02 | The field element shall aggregate and forward collected environmental probe information to the center. | |||
05 | The field element shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center. | |||
TIC Data Collection | 23 | The center shall acquire environmental data from vehicles. | ||
Vehicle Environmental Monitoring | 01 | The vehicle shall collect and process environmental sensor data, including air temperature and rain sensors. | ||
02 | The vehicle shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems. | |||
03 | The vehicle shall transmit environmental probe data to the center along with location and timestamp information. | |||
04 | The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications. | |||
03 | Traffic operations and maintenance and construction operations need to share collected environmental data with each other. | MCM Environmental Information Collection | 11 | The center shall provide weather and road condition information to traffic management operations. |
TMC Environmental Monitoring | 06 | The traffic center shall share the collected environmental data with Maintenance and construction operations. | ||
04 | Traffic operations and Maintenance and construction need to be able to receive environmental data from Weather operations. | TMC Environmental Monitoring | 04 | The traffic center shall receive road condition information from weather service providers. |
05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. | MCM Environmental Information Collection | 03 | The center shall remotely control environmental sensors on-board maintenance and construction vehicles that measure road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and other measures. |
04 | The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from short range communications equipment that communicates with appropriately equipped probe vehicles. | |||
MCV Environmental Monitoring | 01 | The maintenance and construction vehicle shall collect environmental data from on-board sensors, including air temperature, wind speed, surface temperature, traction conditions, etc. | ||
02 | The maintenance and construction vehicle shall transmit environmental sensor data to the center. The sensor data includes location and timestamp information. | |||
05 | The maintenance and construction vehicle shall collect environmental data from sensors located at the roadway but are monitored on-board a maintenance and construction vehicle. | |||
06 | The maintenance and construction vehicle shall be capable of accepting sensor control data from the center. | |||
07 | The maintenance and construction vehicle shall provide control signals to environmental sensors located at the roadway. | |||
08 | The maintenance and construction vehicle shall transmit environmental sensor data to roadside equipment. The sensor data includes location and timestamp information. | |||
Roadway Environmental Monitoring | 09 | The field element shall remotely aggregate environmental sensor data with environmental data collected from maintenance and construction vehicles. | ||
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. | ||
Vehicle Environmental Monitoring | 04 | The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications. | ||
06 | Weather Systems need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. | Roadway Environmental Monitoring | 05 | The field element's environmental sensors shall be remotely controlled by weather service providers such as the National Weather Service or value-added sector specific meteorological services. |
TIC Data Collection | 07 | The center shall collect, process, and store current and forecast road conditions and surface weather conditions. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 |
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 |
ITS Roadway Equipment | Moderate | High | Moderate | Class 3 |
Maint and Constr Management Center | Moderate | High | Moderate | Class 3 |
Maint and Constr Vehicle OBE | Moderate | Moderate | Moderate | Class 2 |
Roadway Environment | Not Applicable | Low | Low | Class 1 |
Surface Transportation Weather Service | Low | Moderate | Moderate | Class 1 |
Traffic Management Center | Moderate | Moderate | Moderate | Class 2 |
Transportation Information Center | Low | High | Moderate | Class 3 |
Vehicle OBE | Low | Moderate | Moderate | Class 1 |
Weather Service System | Low | Moderate | Moderate | Class 1 |
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 | Maint and Constr 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 | environmental 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 | 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 | Vehicle OBE | vehicle situation data parameters | Low | Moderate | Moderate |
This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation. | Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data | Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not | |||
ITS Roadway Equipment | Maint and Constr Management Center | environmental sensor data | Low | High | Moderate |
Little to no impact if this data is observed | WYO believes this to be MODERATE or HIGH depending on the application | Updates are valuable only if they are timely. | |||
ITS Roadway Equipment | Maint and Constr Vehicle OBE | environmental sensor data | Low | Moderate | Moderate |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | Updates are valuable only if they are timely. | |||
ITS Roadway Equipment | Surface Transportation Weather Service | environmental sensor data | Low | Moderate | Moderate |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | Updates are valuable only if they are timely. | |||
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 desirable but slightly outdated information will not be catastrophic. | |||
ITS Roadway Equipment | Weather Service System | environmental sensor data | Low | Moderate | Moderate |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | Updates are valuable only if they are timely. | |||
Maint and Constr Center Personnel | Maint and Constr Management Center | maint and constr center personnel input | High | High | High |
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. | 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. | |||
Maint and Constr Management Center | ITS Roadway Equipment | environmental sensors control | Moderate | Moderate | Moderate |
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: WYO believes this to be MODERATE. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Maint and Constr Management Center | Maint and Constr Center Personnel | maint and constr operations information presentation | Not Applicable | Moderate | Moderate |
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment | 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. | |||
Maint and Constr Management Center | Maint and Constr Vehicle OBE | environmental sensors control | Moderate | High | Moderate |
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: WYO believes this to be MODERATE. | 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. DISC: WYO believes this to be HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Maint and Constr Management Center | Surface Transportation Weather Service | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Maint and Constr Management Center | Traffic Management Center | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Maint and Constr Management Center | Transportation Information Center | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Maint and Constr Management Center | Weather Service System | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Maint and Constr Vehicle OBE | ITS Roadway Equipment | environmental sensor data | Low | Moderate | Moderate |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | |||
Maint and Constr Vehicle OBE | ITS Roadway Equipment | environmental sensors control | Moderate | Moderate | Moderate |
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: WYO believes this to be MODERATE. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Maint and Constr Vehicle OBE | Maint and Constr Management Center | environmental sensor data | Low | Moderate | Moderate |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | Updates are desirable but slightly outdated information will not be catastrophic. | |||
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 conclusions. | 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 conclusions. | |||
Roadway Environment | Vehicle OBE | 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 conclusions. | 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 conclusions. | |||
Surface Transportation Weather Service | Maint and Constr Management Center | environmental conditions data status | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Surface Transportation Weather Service | Maint and Constr Management Center | qualified environmental conditions data | Low | Moderate | Moderate |
If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW. | Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data. | This flow is used to help determine what road treatments should be performed. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimation; if that estimate fails to suggest the correct treatment method, the cost to mobility and maintenance could be significant. | |||
Surface Transportation Weather Service | Traffic Management Center | environmental conditions data status | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Surface Transportation Weather Service | Traffic Management Center | qualified environmental conditions data | Low | Moderate | Moderate |
If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW. | Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data. | This flow is used to help determine what road operations actions should be taken. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimation; if that estimate fails to suggest the correct actions, the cost to mobility could be significant. | |||
Traffic Management Center | Connected Vehicle Roadside Equipment | environmental monitoring application info | 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. | |||
Traffic Management Center | ITS Roadway Equipment | environmental sensors 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 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 | Maint and Constr Management Center | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Traffic Management Center | Surface Transportation Weather Service | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might 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 Management Center | Weather Service System | environmental conditions data | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as it may be used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
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. | |||
Transportation Information Center | Maint and Constr Management Center | road network environmental situation data | Low | High | Moderate |
Aggregated data, but indicates the types of systems and status of those systems on vehicles. Should be LOW, but if identifiers are preserved could be MODERATE. | Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality. MODERATE or HIGH depending on the context; if critical to some operation then HIGH, if not critical then MODERATE. | Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality. | |||
Vehicle OBE | 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 OBE | Transportation Information Center | vehicle environmental data | Low | Moderate | Moderate |
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. | This could be used for safety applications, and in areas of severe weather a corrupted field could have significant consequences; however, any vehicle will use other inputs before triggering automatic safety facilities, so MODERATE should be sufficient. DISC: WYO believes this to be HIGH. | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |||
Weather Service System | Maint and Constr Management Center | environmental conditions data status | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Weather Service System | Maint and Constr Management Center | qualified environmental conditions data | Low | Moderate | Moderate |
If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW. | Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data. | This flow is used to help determine what road treatments should be performed. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimation; if that estimate fails to suggest the correct treatment method, the cost to mobility and maintenance could be significant. | |||
Weather Service System | Traffic Management Center | environmental conditions data status | Low | Moderate | Low |
Little to no impact if this data is observed | This data should be correct, as the base data this reports on is used to establish safe speeds and determine road treatments. | There should be other mechanisms for determining this data; in areas and times of severe weather this might be MODERATE. | |||
Weather Service System | Traffic Management Center | qualified environmental conditions data | Low | Moderate | Moderate |
If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW. | Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data. | This flow is used to help determine what road operations actions should be taken. If unavailable then other mechanisms would be used, but these would degrade the overall quality of road condition estimation; if that estimate fails to suggest the correct actions, the cost to mobility could be significant. |
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 | Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) | Connected Vehicle Roadside Equipment |
ITE ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | ITS Roadway Equipment |
Maint and Constr Management Center | ||
Traffic Management Center |
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
002 | The system shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
003 | The system shall remotely control environmental sensors on-board maintenance and construction vehicles that measure road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and other measures. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
004 | The system shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from short range communications equipment that communicates with appropriately equipped probe vehicles. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
005 | The system shall respond to control data from center personnel regarding environmental sensor control and weather data collection. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
006 | The system shall collect operational status for the roadside and vehicle-based environmental sensor equipment. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
007 | The system shall collect fault data for the roadside and vehicle-based environmental sensor equipment for repair. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
008 | The system shall collect environmental data from sensors that measure road surface temperature, moisture, icing, salinity, and other measures. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
009 | The system shall provide weather and road condition information to traffic management operations. | 03 | Traffic operations and maintenance and construction operations need to share collected environmental data with each other. |
010 | The system shall acquire environmental data from vehicles. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
011 | The system shall collect, process, and store current and forecast road conditions and surface weather conditions. | 06 | Weather Systems need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
012 | The system shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
013 | The system shall receive road condition information from weather service providers. | 04 | Traffic operations and Maintenance and construction need to be able to receive environmental data from Weather operations. |
014 | The system shall share the collected environmental data with Maintenance and construction operations. | 03 | Traffic operations and maintenance and construction operations need to share collected environmental data with each other. |
015 | The system shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
016 | The system shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
017 | The system shall be remotely controlled by weather service providers such as the National Weather Service or value-added sector specific meteorological services. | 06 | Weather Systems need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
018 | The system shall be remotely controlled by a maintenance and construction vehicle. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
019 | The system shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
020 | The system shall provide environmental sensor equipment fault indication to the controlling center or maintenance vehicle. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
021 | The system shall remotely aggregate environmental sensor data with environmental data collected from maintenance and construction vehicles. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. | ||
022 | The system shall provide weather and road surface condition data to centers. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
023 | The system shall provide weather and road surface condition data to maintenance and construction vehicles. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
024 | The system shall provide environmental sensor data to the Connected Vehicle Roadside Equipment. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
025 | The system shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. | ||
026 | The system shall aggregate and forward collected environmental probe information to the center. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
027 | The system shall collect environmental monitoring data from sensors, including ambient air quality, emissions, temperature, precipitation, and other road weather information. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
028 | The system shall provide application status to the center for monitoring. | 01 | Traffic operations or maintenance and construction operations need be able to collect road conditions and weather data from environmental sensors on or in the vicinity of the roadway. |
029 | The system shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
030 | The system shall collect environmental data from on-board sensors, including air temperature, wind speed, surface temperature, traction conditions, etc. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. | ||
031 | The system shall transmit environmental sensor data to the center. The sensor data includes location and timestamp information. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
032 | The system shall collect environmental data from sensors located at the roadway but are monitored on-board a maintenance and construction vehicle. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
033 | The system shall accept sensor control data from the center. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
034 | The system shall provide control signals to environmental sensors located at the roadway. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
035 | The system shall transmit environmental sensor data to roadside equipment. The sensor data includes location and timestamp information. | 05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
036 | The system shall collect and process environmental sensor data, including air temperature and rain sensors. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
037 | The system shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
038 | The system shall transmit environmental probe data to the center along with location and timestamp information. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
039 | The system shall transmit environmental probe data to field equipment located along the roadway using short range communications. | 02 | Traffic operations need to be able to collect road conditions and weather data from vehicle on-board sensors. |
05 | Maintenance and construction operations need to be able to collect road conditions and weather data from maintenance vehicle on-board sensors. |
Implementations
- WX01.1 Environmental Sensor Stations
- WX01.2 Maint and Constr Vehicle Reported
- WX01.3 C-ITS Vehicle Reported


WX01.1 Environmental Sensor Stations Implementation
Environmental sensors deployed on or about the roadway are used to collect current road weather conditions.
Environmental Sensor Stations Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
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. | Optional |
environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included. | Optional |
environmental conditions data status | Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided. | Optional |
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. | At Least One |
environmental sensors control | Data used to configure and control environmental sensors. | At Least One |
maint and constr center personnel input | User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination. | Optional |
maint and constr operations information presentation | Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning. | Optional |
qualified environmental conditions 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) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included. | Optional |
road network environmental situation data | Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region. | Optional |
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. | Optional |
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. | Optional |
Environmental Sensor Stations Implementation Functional Objects
Functional Object |
---|
MCM Environmental Information Collection |
Roadway Environmental Monitoring |
TIC Data Collection |
TMC Environmental Monitoring |
Back to Implementation List
WX01.2 Maint and Constr Vehicle Reported Implementation
This implementation supports data collection from equipped maintenance and construction vehicles that include environmental sensors that provide a rich set of environmental condition data to the infrastructure.
Maint and Constr Vehicle Reported Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
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. | Optional |
environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included. | Optional |
environmental conditions data status | Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided. | Optional |
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. | Optional |
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. | Fundamental |
environmental sensors control | Data used to configure and control environmental sensors. | Optional |
environmental sensors control | Data used to configure and control environmental sensors. | Fundamental |
maint and constr center personnel input | User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination. | Optional |
maint and constr operations information presentation | Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning. | Optional |
qualified environmental conditions 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) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included. | Optional |
road network environmental situation data | Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region. | Optional |
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. | Optional |
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. | Optional |
Maint and Constr Vehicle Reported Implementation Functional Objects
Functional Object |
---|
MCM Environmental Information Collection |
MCV Environmental Monitoring |
Roadway Environmental Monitoring |
TIC Data Collection |
TMC Environmental Monitoring |
Back to Implementation List
WX01.3 C-ITS Vehicle Reported Implementation
Vehicle on-board systems measure temperature, precipitation, and other vehicle status with environmental implications (e.g., traction control status, headlight status, windshield wiper status) and share this information with the infrastructure.
C-ITS Vehicle Reported Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
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. | Optional |
environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included. | Optional |
environmental conditions data status | Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided. | Optional |
environmental monitoring application info | Environmental monitoring application parameters and thresholds that control the filtering, aggregation, and range of measures that are collected, derived, and reported. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. | Fundamental |
environmental monitoring application status | Environmental monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation. | Fundamental |
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. | At Least One |
maint and constr center personnel input | User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination. | Optional |
maint and constr operations information presentation | Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning. | Optional |
qualified environmental conditions 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) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included. | Optional |
road network environmental situation data | Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region. | At Least One |
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. | Optional |
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. | Optional |
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. | At Least One |
vehicle situation data parameters | A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval. | Optional |
C-ITS Vehicle Reported Implementation Functional Objects
Functional Object |
---|
MCM Environmental Information Collection |
RSE Environmental Monitoring |
TIC Data Collection |
TMC Environmental Monitoring |
Vehicle Environmental Monitoring |
Back to Implementation List