Roadway (Subsystem*)

Subsystem Interfaces Diagram

Terminator Interfaces Diagram

Functionality: Equipment Packages* and PSpecs*

• Advanced Rail Crossing (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.4-Process In-vehicle Signage Data
  • 1.6.1.1-Detect Roadway Events
  • 1.6.1.2.4-Provide HSR Device Controls
  • 1.6.1.4.1-Generate Alerts and Advisories
  • 1.6.1.4.3-Report Alerts and Advisories
  • 1.6.1.5-Detect HRI Hazards
  • 1.6.1.6.1-Close HRI on Detection
  • 1.6.1.6.2-Detect Imminent Vehicle/Train Collision
  • 1.6.3.1-Interact with Wayside Systems
  • 1.6.3.2-Advise and Protect Train Crews
  • 1.6.3.3-Provide ATS Alerts
  • 1.6.5.1-Provide Interactive Interface

• Field Barrier System Control (Equipment Package*)
  PSpecs:
  • 1.2.7.10-Control Barrier Systems

• Field Management Stations Operation (Equipment Package*)
  PSpecs:
  • 1.2.7.13-Provide Device Interface for Field Management Stations

• Field Safeguard System Control (Equipment Package*)
  PSpecs:
  • 5.7.6.1-Control Safeguard Systems

• Multimodal Crossing Control (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults
  • 1.2.7.5-Process Indicator Output Data for Freeways
  • 1.2.7.9-Process Roadway Information Data

• Roadside Lighting System Control (Equipment Package*)
  PSpecs:
  • 1.2.7.11-Control Lighting System

• Roadway Automated Treatment (Equipment Package*)
  PSpecs:
  • 9.2.6.2-Control Roadway Automated Treatment System

• Roadway Automated Vehicle Operations (Equipment Package*)
  PSpecs:
  • 3.2.5-Check Vehicle for Automated Operations Eligibility
  • 3.2.6-Manage Check-in and Check-out
  • 3.2.8-Provide Automated Lane Changing

• Roadway Basic Surveillance (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.3.1.3-Process Traffic Images

• Roadway Data Collection (Equipment Package*)
  PSpecs:
  • 1.1.1.4-Manage Data Collection and Monitoring

• Roadway Dynamic Lane Management and Shoulder Use (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.1.2.11-Control Dynamic Lanes

• Roadway Emissions Monitoring (Equipment Package*)
  PSpecs:
  • 1.2.7.9-Process Roadway Information Data
  • 1.5.5-Detect Vehicle Emissions Levels
  • 1.5.6-Detect Pollution Levels

• Roadway Environmental Monitoring (Equipment Package*)
  PSpecs:
  • 1.1.1.3-Process Environmental Sensor Data

• Roadway Equipment Coordination (Equipment Package*)
  PSpecs:
  • 1.1.1.5-Provide Sensor Interface to Other Roadway Devices
  • 1.2.7.8-Provide Device Interface to Other Roadway Devices

• Roadway Field Device Monitoring (Equipment Package*)
  PSpecs:
  • 9.2.3.6-Collect Field Equipment Status for Repair

• Roadway HOV Control (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.1.2.11-Control Dynamic Lanes
  • 1.2.7.5-Process Indicator Output Data for Freeways

• Roadway Incident Detection (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.3.1.3-Process Traffic Images

• Roadway Infrastructure Monitoring (Equipment Package*)
  PSpecs:
  • 1.1.1.2-Collect Infrastructure Sensor Data

• Roadway Intersection Safety Warning (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.6-Provide Intersection Collision Avoidance Data

• Roadway Mixed Use Sensing (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.1.1.7-Process Road User Protection
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults
  • 1.2.7.9-Process Roadway Information Data

• Roadway Probe Data Communications (Equipment Package*)
  PSpecs:
  • 1.1.6-Collect Vehicle Traffic Probe Data
  • 1.1.7-Collect Vehicle Environmental Probe Data

• Roadway Reversible Lanes (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.1.2.11-Control Dynamic Lanes
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults
  • 1.2.7.5-Process Indicator Output Data for Freeways
  • 1.3.1.3-Process Traffic Images

• Roadway Safety Warning System (Equipment Package*)
  PSpecs:
  • 1.1.1.6-Collect Vehicle Roadside Safety Data
  • 1.1.2.6-Process Collected Vehicle Safety Data
  • 1.2.7.4-Process In-vehicle Signage Data
  • 1.2.7.7-Process Vehicle Safety and Environmental Data for Output

• Roadway Short Range Traveler Information Communications (Equipment Package*)
  PSpecs:
  • 1.1.2.6-Process Collected Vehicle Safety Data
  • 1.2.7.4-Process In-vehicle Signage Data
  • 1.2.7.7-Process Vehicle Safety and Environmental Data for Output
  • 6.7.3.5-Provide Short Range Traveler Information

• Roadway Signal Controls (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults

• Roadway Signal Preemption (Equipment Package*)
  PSpecs:
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults
  • 1.2.7.3-Manage Local Signal Preemption Requests

• Roadway Signal Priority (Equipment Package*)
  PSpecs:
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.14-Manage Local Signal Priority Requests
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults

• Roadway Speed Monitoring and Warning (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.4-Process In-vehicle Signage Data
  • 1.2.7.9-Process Roadway Information Data
  • 9.3.3.1-Collect Vehicle Speed
  • 9.3.3.4-Support Vehicle Speed Enforcement

• Roadway Traffic Information Dissemination (Equipment Package*)
  PSpecs:
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.2.7.5-Process Indicator Output Data for Freeways
  • 1.2.7.9-Process Roadway Information Data

• Roadway Traffic Metering (Equipment Package*)
  PSpecs:
  • 1.2.7.2-Monitor Roadside Equipment Operation for Faults
  • 1.2.7.5-Process Indicator Output Data for Freeways

• Roadway Variable Speed Limits (Equipment Package*)
  PSpecs:
  • 9.3.3.1-Collect Vehicle Speed

• Roadway Warning (Equipment Package*)
  PSpecs:
  • 1.2.7.12-Control Roadway Warning System
  • 9.3.3.1-Collect Vehicle Speed

• Roadway Work Zone Safety (Equipment Package*)
  PSpecs:
  • 9.3.1.3-Monitor Crew Movement
  • 9.3.4.1-Detect Work Zone Intrusion
  • 9.3.4.2-Provide Work Zone Intrusion Alert

• Roadway Work Zone Traffic Control (Equipment Package*)
  PSpecs:
  • 1.2.7.10-Control Barrier Systems
  • 1.2.7.9-Process Roadway Information Data
  • 1.3.1.3-Process Traffic Images

• Standard Rail Crossing (Equipment Package*)
  PSpecs:
  • 1.1.1.1-Process Traffic Sensor Data
  • 1.2.7.1-Process Indicator Output Data for Roads
  • 1.6.1.2.1-Control HRI Traffic Signals
  • 1.6.1.2.2-Control HRI Warnings and Barriers
  • 1.6.1.2.3-Provide SSR Device Controls
  • 1.6.1.2.5-Manage Device Control
  • 1.6.1.2.6-Maintain Device State
  • 1.6.1.3-Perform Equipment Self-Test
  • 1.6.1.4.2-Provide Closure Parameters
  • 1.6.1.4.4-Report HRI Status on Approach
  • 1.6.1.7.1-Control Traffic Volume at Active HRI
  • 1.6.1.7.2-Close HRI on Command
  • 1.6.3.1-Interact with Wayside Systems
  • 1.6.5.1-Provide Interactive Interface
  • 1.6.5.2-Determine HRI Status
  • 1.6.5.3-Maintain HRI Closure Data

Inputs/Outputs: Architecture Flows* and Data Flows*

Archived Data Management Roadway

• data collection and monitoring control (Architecture Flow*) - Information used to configure and control data collection and monitoring systems.
  Data Flows*:
  • data_collection_device_control
  • roadside_archive_control

Emergency Vehicle Roadway

• barrier system control (Architecture Flow*) - Information used to configure and control barrier systems that are represented by gates, barriers and other automated or remotely controlled systems used to manage entry to roadways.
  Data Flows*:
  • barrier_system_control_from_emerg_veh

• local signal preemption request (Architecture Flow*) - Direct control signal or message to a signalized intersection that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
  Data Flows*:
  • emergency_vehicle_preemptions

Emissions Management Roadway

• emissions sensor control (Architecture Flow*) - Data used to configure and control vehicle emissions sensors.
  Data Flows*:
  • vehicle_emissions_sensor_control

• pollution sensor control (Architecture Flow*) - Data used to configure and control area pollution and air quality sensors.
  Data Flows*:
  • pollution_sensor_control

Enforcement Agency Roadway

• speed monitoring control (Architecture Flow*) - Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems.
  Data Flows*:
  • fea-enforcement_parameters
  • fea-speed_sensor_control

Environment Roadway

• pollutant levels (Architecture Flow*) - Atmospheric pollutant levels as monitored by air quality sensors.
  Data Flows*:
  • fe-pollutant_levels

Information Service Provider Roadway

• broadcast traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
  Data Flows*:
  • field_broadcast_border_data
  • field_broadcast_event_information
  • field_broadcast_incident_information
  • field_broadcast_multimodal_data
  • field_broadcast_parking_data
  • field_broadcast_price_data
  • field_broadcast_traffic_data
  • field_broadcast_transit_data
  • field_broadcast_weather_data

• emergency traveler information (Architecture Flow*) - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.
  Data Flows*:
  • field_emergency_traveler_information
  • field_evacuation_traveler_information
  • field_transportation_system_status
  • field_wide_area_alert_information

Maintenance and Construction Field Personnel Roadway

• crew movements (Architecture Flow*) - Visual or sensed presence of field crew location within a work zone that is monitored to enhance work zone safety.
  Data Flows*:
  • fmcfp-crew_movements

• field device status request (Architecture Flow*) - User input from field personnel requesting operational status of field equipment (sensors, signals, signs, controllers, etc.).
  Data Flows*:
  • fmcfp-field_equip_status_request

Maintenance and Construction Management Roadway

• barrier system control (Architecture Flow*) - Information used to configure and control barrier systems that are represented by gates, barriers and other automated or remotely controlled systems used to manage entry to roadways.
  Data Flows*:
  • barrier_system_control_from_m_and_c

• environmental sensors control (Architecture Flow*) - Data used to configure and control environmental sensors.
  Data Flows*:
  • environmental_sensor_control_for_roadway_sensors

• infrastructure monitoring sensor control (Architecture Flow*) - Data used to configure and control infrastructure monitoring sensors.
  Data Flows*:
  • infrastructure_sensor_control_from_m_and_c

• roadway information system data (Architecture Flow*) - Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio, beacon systems). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.
  Data Flows*:
  • dms_auto_treat_data_from_maint
  • dms_data_from_m_and_c
  • har_data_from_m_and_c
  • work_zone_info_for_display

• roadway treatment system control (Architecture Flow*) - Control data for remotely located, automated devices, that affect the roadway surface (e.g. de-icing applications).
  Data Flows*:
  • roadway_treatment_system_control

• speed monitoring control (Architecture Flow*) - Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems.
  Data Flows*:
  • speed_sensor_control_from_m_and_c

• video surveillance control (Architecture Flow*) - Information used to configure and control video surveillance systems.
  Data Flows*:
  • video_control_from_m_and_c

• work zone warning device control (Architecture Flow*) - Data used to configure and control work zone safety monitoring and warning devices.
  Data Flows*:
  • intrusion_alert_device_control
  • intrusion_detection_device_control

Maintenance and Construction Vehicle Roadway

• barrier system control (Architecture Flow*) - Information used to configure and control barrier systems that are represented by gates, barriers and other automated or remotely controlled systems used to manage entry to roadways.
  Data Flows*:
  • barrier_system_control_from_mcv

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • environmental_sensor_data_for_roadway

• environmental sensors control (Architecture Flow*) - Data used to configure and control environmental sensors.
  Data Flows*:
  • environmental_sensor_control_for_roadway

• infrastructure monitoring sensor control (Architecture Flow*) - Data used to configure and control infrastructure monitoring sensors.
  Data Flows*:
  • infrastructure_sensor_control_from_mcv

• roadway information system data (Architecture Flow*) - Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio, beacon systems). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.
  Data Flows*:
  • dms_data_from_mcv

Multimodal Crossings Roadway

• multimodal crossing status (Architecture Flow*) - Indication of operational status and pending requests for right-of-way from equipment supporting the non-highway mode at multimodal crossings.
  Data Flows*:
  • fmmc-crossing_close_duration
  • fmmc-crossing_close_time
  • fmmc-crossing_status_for_highways
  • fmmc-crossing_status_for_roads

Other Roadway Roadway

• roadway equipment coordination (Architecture Flow*) - The direct flow of information between field equipment. This includes transfer of information between sensors and driver information systems (e.g., DMS, HAR, variable speed limit signs, dynamic lane signs) or control devices (e.g., traffic signals, ramp meters), direct coordination between adjacent control devices, interfaces between detection and warning or alarm systems, and any other direct communications between field equipment.
  Data Flows*:
  • fors-device_control
  • fors-device_status
  • fors-roadway_info_data_from_devices
  • fors-roadway_info_data_from_sensors
  • fors-sensor_control
  • fors-sensor_data
  • fors-sensor_status

• signal control data (Architecture Flow*) - Information used to configure local traffic signal controllers.
  Data Flows*:
  • fors-signal_control
  • fors-signal_fault
  • fors-signal_status

Pedestrians Roadway

• crossing call (Architecture Flow*) - Pedestrian request to cross the roadway. This may be an overt (e.g., push button) request from a pedestrian or the physical presence of a pedestrian that can be detected by sensors or surveillance systems.
  Data Flows*:
  • fp-pedestrian_data
  • fp-pedestrian_images

• non-vehicular presence (Architecture Flow*) - Sensed presence of pedestrians and other non-motor vehicle travelers at roadway crossing or control points.
  Data Flows*:
  • fp-pedestrian_presence

Potential Obstacles Roadway

• physical presence (Architecture Flow*) - Detection of an obstacle. Obstacle could include animals, vehicles, pedestrians, rocks in roadway etc.
  Data Flows*:
  • From_Potential_Obstacles

Roadway Archived Data Management

• probe archive data (Architecture Flow*) - Probe data that allows calculation of travel times, volumes, and other measures that support transportation planning. Optionally, this flow also includes origin and destination information for vehicles that opt to provide this information.
  Data Flows*:
  • traffic_probe_data_from_vehicles_archive_data

• roadside archive data (Architecture Flow*) - A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any identified sensor faults.
  Data Flows*:
  • data_collection_device_status
  • roadside_archive_data

Roadway Basic Vehicle

• broadcast advisories (Architecture Flow*) - General broadcast advisories that are provided over wide-area wireless communications direct to the vehicle radio. These analog advisory messages may provide similar content to ITS broadcast information flows, but include no digital data component. Existing Highway-Advisory Radio (HAR) advisory messages are a prime example of this flow.
  Data Flows*:
  • tbv-har_broadcast

Roadway Driver

• driver information (Architecture Flow*) - Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
  Data Flows*:
  • td-dms_indication
  • td-dynamic_lane_control
  • td-intersection_safety_data
  • td-lane_use_indication_for_highways
  • td-lane_use_indication_for_roads
  • td-ramp_state_indication
  • td-roadway_warning
  • td-signal_indication
  • td-work_zone_intrusion_alert

Roadway Emergency Vehicle

• barrier system status (Architecture Flow*) - Current operating status of barrier systems. Barrier systems represent gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. Status of the systems includes operating condition and current operational state.
  Data Flows*:
  • barrier_system_status_to_emerg_veh

Roadway Emissions Management

• area pollution data (Architecture Flow*) - Measured air quality data, including measured levels of atmospheric pollutants including ozone, particulate matter, carbon monoxide, and nitrogen oxides, and operational status of the sensors.
  Data Flows*:
  • pollution_sensor_data
  • pollution_sensor_status

• vehicle emissions data (Architecture Flow*) - Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
  Data Flows*:
  • vehicle_emissions_alert
  • vehicle_emissions_sensor_data
  • vehicle_emissions_sensor_status

Roadway Enforcement Agency

• speed monitoring information (Architecture Flow*) - System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records.
  Data Flows*:
  • tea-speed_sensor_status

• traffic violation notification (Architecture Flow*) - Notification to enforcement agency of a detected traffic violation including speed violations, HOV violations, and dynamic lane violations.
  Data Flows*:
  • tea-lane_violation_notification_from_roadway
  • tea-shoulder_violation_notification_from_roadway
  • tea-speed_violation_notification

Roadway Information Service Provider

• environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, 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. 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.
  Data Flows*:
  • vehicle_env_probe_data_for_isp
  • vehicle_env_probe_status_for_isp

• short range communications status (Architecture Flow*) - Status of the short range communications equipment including the current state or mode of operation and the current equipment status.
  Data Flows*:
  • trav_info_equip_status_for_isp_operator

• traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows*:
  • vehicle_traffic_probe_data_for_isp
  • vehicle_traffic_probe_status_for_isp

Roadway Maintenance and Construction Field Personnel

• field device status presentation (Architecture Flow*) - Presentation of operational status of field equipment (sensors, signals, signs, controllers, etc.) to field personnel.
  Data Flows*:
  • tmcfp-field_equip_status

• work zone warning (Architecture Flow*) - Warnings provided to maintenance and construction field personnel, indicating a work zone emergency or safety issue such as the intrusion of a vehicle into the work zone area or movement of field crew into the travel lanes.
  Data Flows*:
  • tmcfp-work_zone_intrusion_alert
  • tmcfp-work_zone_intrusion_warning

Roadway Maintenance and Construction Management

• barrier system status (Architecture Flow*) - Current operating status of barrier systems. Barrier systems represent gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. Status of the systems includes operating condition and current operational state.
  Data Flows*:
  • barrier_system_status_to_m_and_c

• environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, 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. 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.
  Data Flows*:
  • vehicle_env_probe_data_for_infrastructure_maint
  • vehicle_env_probe_data_for_maint
  • vehicle_env_probe_status_for_maint

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • environmental_sensor_data_from_roadway_sensors
  • environmental_sensor_status_from_roadway_sensors

• field device status (Architecture Flow*) - Reports from field equipment (sensors, signals, signs, controllers, etc.) which indicate current operational status.
  Data Flows*:
  • field_equip_status_for_m_and_c

• infrastructure monitoring sensor data (Architecture Flow*) - Data read from infrastructure-based sensors that monitor the condition or integrity of transportation infrastructure including bridges, tunnels, interchanges, pavement, culverts, signs, transit rail or guideway, and other roadway infrastructure. Includes sensor data and the operational status of the sensors.
  Data Flows*:
  • infrastructure_sensor_data_for_m_and_c
  • infrastructure_sensor_status_for_m_and_c

• roadway information system status (Architecture Flow*) - Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field equipment that provides dynamic information to the driver.
  Data Flows*:
  • dms_auto_treat_status_to_maint
  • dms_status_for_m_and_c
  • har_status_for_m_and_c

• roadway treatment system status (Architecture Flow*) - Current operational status of automated roadway treatment devices (e.g., anti-icing systems).
  Data Flows*:
  • roadway_treatment_system_status

• speed monitoring information (Architecture Flow*) - System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records.
  Data Flows*:
  • speed_data_for_m_and_c_speed_monitoring
  • speed_sensor_log_for_m_and_c
  • speed_sensor_status_for_m_and_c
  • speed_violation_notification_for_m_and_c

• traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
  Data Flows*:
  • video_device_status_for_m_and_c
  • work_zone_images

• work zone warning status (Architecture Flow*) - Status of a work zone safety monitoring and warning devices. This flow documents system activations and includes additional supporting information (e.g., an image) that allows verification of the alarm.
  Data Flows*:
  • intrusion_alert_device_status
  • intrusion_detection_device_status
  • roadside_crew_warning_given
  • work_zone_intrusion_alert
  • work_zone_intrusion_detected
  • work_zone_intrusion_video_image

Roadway Maintenance and Construction Vehicle

• barrier system status (Architecture Flow*) - Current operating status of barrier systems. Barrier systems represent gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. Status of the systems includes operating condition and current operational state.
  Data Flows*:
  • barrier_system_status_to_mcv

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • environmental_sensor_data_from_roadway
  • environmental_sensor_status_from_roadway

• infrastructure monitoring sensor data (Architecture Flow*) - Data read from infrastructure-based sensors that monitor the condition or integrity of transportation infrastructure including bridges, tunnels, interchanges, pavement, culverts, signs, transit rail or guideway, and other roadway infrastructure. Includes sensor data and the operational status of the sensors.
  Data Flows*:
  • infrastructure_sensor_data_for_mcv
  • infrastructure_sensor_status_for_mcv

• roadway information system status (Architecture Flow*) - Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field equipment that provides dynamic information to the driver.
  Data Flows*:
  • dms_status_for_mcv

• work zone warning notification (Architecture Flow*) - Notification of a work zone emergency or safety issue. This flow identifies that a work zone emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.
  Data Flows*:
  • work_zone_intrusion_detection_for_on_board

Roadway Map Update Provider

• traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows*:
  • tmup-traffic_probe_data

Roadway Multimodal Crossings

• highway control status (Architecture Flow*) - Current traffic control equipment status that indicates operational status and right-of-way availability to the non-highway transportation mode at a multimodal crossing.
  Data Flows*:
  • tmmc-crossing_clear_at_highways
  • tmmc-crossing_clear_at_roads
  • tmmc-highway_equipment_status
  • tmmc-road_equipment_status
  • tmmc-stop_alternate_mode_at_highways
  • tmmc-stop_alternate_mode_at_roads

Roadway Other Roadway

• roadway equipment coordination (Architecture Flow*) - The direct flow of information between field equipment. This includes transfer of information between sensors and driver information systems (e.g., DMS, HAR, variable speed limit signs, dynamic lane signs) or control devices (e.g., traffic signals, ramp meters), direct coordination between adjacent control devices, interfaces between detection and warning or alarm systems, and any other direct communications between field equipment.
  Data Flows*:
  • tors-device_control
  • tors-device_status
  • tors-roadway_info_data_from_devices
  • tors-roadway_info_data_from_sensors
  • tors-sensor_control
  • tors-sensor_data
  • tors-sensor_status

• signal control data (Architecture Flow*) - Information used to configure local traffic signal controllers.
  Data Flows*:
  • tors-signal_control
  • tors-signal_fault
  • tors-signal_status

Roadway Pedestrians

• crossing permission (Architecture Flow*) - Signal to pedestrians indicating permission to cross roadway.
  Data Flows*:
  • tp-cross_request_received
  • tp-cross_road
  • tp-dms_indication

Roadway Surface Transportation Weather Service

• environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, 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. 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.
  Data Flows*:
  • tstws-vehicle_env_probe_data
  • tstws-vehicle_env_probe_status

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • tstws-roadway_env_sensor_data
  • tstws-roadway_env_sensor_status

Roadway Traffic Management

• automated roadway status (Architecture Flow*) - Current operational status of an automated vehicle operations facility, including the status of the field equipment and vehicles using the facility.
  Data Flows*:
  • avo_checking_details
  • avo_device_status

• barrier system status (Architecture Flow*) - Current operating status of barrier systems. Barrier systems represent gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. Status of the systems includes operating condition and current operational state.
  Data Flows*:
  • barrier_system_device_status
  • barrier_system_status

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • environment_sensor_data
  • environmental_sensor_status

• hov data (Architecture Flow*) - Current HOV lane information including both standard traffic flow measures and information regarding vehicle occupancy in HOV lanes, and operational status of the HOV monitoring equipment.
  Data Flows*:
  • hov_lane_data_input
  • hov_sensor_data
  • hov_sensor_status

• hri status (Architecture Flow*) - Status of the highway-rail intersection equipment including both the current state or mode of operation and the current equipment condition.
  Data Flows*:
  • hri_guidance_for_roadway_info
  • hri_status
  • hri_traffic_data
  • rail_operations_message
  • traffic_management_request

• intersection blockage notification (Architecture Flow*) - Notification that a highway-rail intersection is obstructed and supporting information.
  Data Flows*:
  • hri_blockage
  • intersection_blocked

• lane management information (Architecture Flow*) - System status including current operational state, violations, and logged information.
  Data Flows*:
  • dynamic_lane_sensor_data
  • lane_management_device_status
  • lane_management_status
  • lane_violation_notification_for_traffic

• lighting system status (Architecture Flow*) - Status of roadside lighting controls including operating condition and current operational state.
  Data Flows*:
  • lighting_system_device_status
  • lighting_system_status

• reversible lane status (Architecture Flow*) - Current reversible lane status including traffic sensor and surveillance data and the operational status and mode of the reversible lane control equipment.
  Data Flows*:
  • reversible_lane_control_device_status_from_highways
  • reversible_lane_control_device_status_from_roads
  • reversible_lane_sensor_data
  • reversible_lane_sensor_status
  • reversible_lane_video_images

• right-of-way request notification (Architecture Flow*) - Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.
  Data Flows*:
  • multimodal_crossing_sensor_data
  • multimodal_crossing_sensor_status
  • pedestrian_sensor_data
  • pedestrian_sensor_status
  • signal_preemption_override
  • signal_priority_override

• road user protection data (Architecture Flow*) - Current data as well as operational status from mixed roadway and right-of-way systems.
  Data Flows*:
  • road_user_protection_data_for_traffic
  • road_user_protection_device_status

• roadway information system status (Architecture Flow*) - Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field equipment that provides dynamic information to the driver.
  Data Flows*:
  • dms_status
  • har_status

• roadway warning system status (Architecture Flow*) - Current operating status of roadway warning systems.
  Data Flows*:
  • roadway_warning_device_status
  • roadway_warning_system_status

• safeguard system status (Architecture Flow*) - Current operating status of safeguard systems (remotely controlled equipment used to mitigate the impact of incidents on transportation infrastructure, such as blast shields, exhaust systems, etc.). Status of the systems includes operating condition and current operational state.
  Data Flows*:
  • safeguard_system_device_status
  • safeguard_system_status

• short range communications status (Architecture Flow*) - Status of the short range communications equipment including the current state or mode of operation and the current equipment status.
  Data Flows*:
  • vehicle_sign_status

• shoulder management information (Architecture Flow*) - System status including current operational state, violations and logged information.
  Data Flows*:
  • shoulder_management_device_status
  • shoulder_management_status
  • shoulder_violation_notification_for_traffic

• signal control status (Architecture Flow*) - Operational and status data of traffic signal control equipment including operating condition and current indications.
  Data Flows*:
  • indicator_input_data_from_signals
  • indicator_status_from_signals

• signal fault data (Architecture Flow*) - Faults from traffic signal control equipment.
  Data Flows*:
  • field_management_station_fault_indication
  • indicator_faults_from_signals

• speed monitoring information (Architecture Flow*) - System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records.
  Data Flows*:
  • speed_data_for_traffic_speed_monitoring
  • speed_sensor_log_for_traffic
  • speed_sensor_status
  • speed_violation_notification_for_traffic

• traffic flow (Architecture Flow*) - Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors.
  Data Flows*:
  • incident_analysis_data
  • traffic_image_data
  • traffic_sensor_data
  • traffic_sensor_status

• traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
  Data Flows*:
  • dynamic_lane_video_image
  • incident_video_image
  • traffic_video_image
  • traffic_video_image_for_display
  • video_device_status

• traffic metering status (Architecture Flow*) - Current operational status and operating parameters for ramp meters, interchange meters, mainline meters and other control equipment associated with roadway metering operations.
  Data Flows*:
  • indicator_input_data_from_traffic_meters
  • indicator_status_from_traffic_meters

• traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows*:
  • vehicle_traffic_probe_data_for_traffic
  • vehicle_traffic_probe_equip_status

• variable speed limit status (Architecture Flow*) - Current operating status of the variable speed limit systems including the state of the equipment.
  Data Flows*:
  • variable_speed_limit_status

Roadway Vehicle

• access permission (Architecture Flow*) - Information returned indicating whether permission for access is granted and instructions for proceeding.
  Data Flows*:
  • vehicle_barrier_access_status

• automated vehicle control data (Architecture Flow*) - Instructions and control parameters for automated vehicle operation including current system conditions and advisories, control parameters (e.g., speed and performance profiles, headways), maneuver coordination, and check in/checkout instructions.
  Data Flows*:
  • avo_check_response
  • lane_change_details
  • lane_change_strategy

• broadcast traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
  Data Flows*:
  • field_to_vehicle_broadcast_border_data
  • field_to_vehicle_broadcast_event_information
  • field_to_vehicle_broadcast_incident_information
  • field_to_vehicle_broadcast_multimodal_data
  • field_to_vehicle_broadcast_parking_data
  • field_to_vehicle_broadcast_price_data
  • field_to_vehicle_broadcast_traffic_data
  • field_to_vehicle_broadcast_transit_data
  • field_to_vehicle_broadcast_weather_data

• emergency traveler information (Architecture Flow*) - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.
  Data Flows*:
  • field_to_vehicle_emergency_traveler_information
  • field_to_vehicle_evacuation_traveler_information
  • field_to_vehicle_transportation_system_status
  • field_to_vehicle_wide_area_alert_information

• intersection status (Architecture Flow*) - Intersection status including current operational status, signal phase and timing information, intersection geometry, surface conditions, warnings of potential violations or hazardous conditions, and approaching vehicle information. This may include information about the position, velocity, acceleration, and turning status of approaching vehicles.
  Data Flows*:
  • intersection_collision_avoidance_data
  • intersection_status_data_for_vehicle

• roadway safety data (Architecture Flow*) - Information about potential safety hazards in the vehicle path such as stalled vehicles, wrong way drivers, debris, or standing water.
  Data Flows*:
  • roadside_safety_data_to_vehicle

• traffic probe reporting management (Architecture Flow*) - Data used to manage probe data reporting by vehicles. This flow indicates to the vehicle when to report probe data, the type of probe data to send, and thresholds for nominal conditions when sending data can be skipped.
  Data Flows*:
  • vehicle_traffic_probe_configuration

• vehicle signage data (Architecture Flow*) - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows*:
  • intrusion_alert_for_in_vehicle_signing
  • vehicle_env_probe_data_output
  • vehicle_signage_data
  • vehicle_signage_emissions_testing_results

Roadway Wayside Equipment

• hri operational status (Architecture Flow*) - Status of the highway-rail grade crossing equipment including both the current state or mode of operation and the current equipment condition.
  Data Flows*:
  • twe-hri_status

• intersection blockage notification (Architecture Flow*) - Notification that a highway-rail intersection is obstructed and supporting information.
  Data Flows*:
  • twe-stop_highway_indication
  • twe-stop_train_indication

Roadway Weather Service

• environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, 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. 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.
  Data Flows*:
  • tws-vehicle_env_probe_data
  • tws-vehicle_env_probe_status

• environmental sensor data (Architecture Flow*) - 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.
  Data Flows*:
  • tws-roadway_env_sensor_data
  • tws-roadway_env_sensor_status

Roadway Environment Roadway

• environmental conditions (Architecture Flow*) - 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.
  Data Flows*:
  • fre-environmental_conditions
  • fre-physical_conditions
  • fre-roadway_infrastructure_characteristics

Surface Transportation Weather Service Roadway

• environmental sensors control (Architecture Flow*) - Data used to configure and control environmental sensors.
  Data Flows*:
  • fstws-roadway_env_sensor_control

Traffic Roadway

• traffic characteristics (Architecture Flow*) - Physical traffic characteristics which are monitored and translated into macroscopic measures like occupancy, volume, density, and average speed. Point measures support presence detection and individual vehicle measures like speed.
  Data Flows*:
  • ftrf-traffic_data
  • ftrf-traffic_images
  • ftrf-vehicle_pollutant_levels
  • ftrf-vehicle_presence

Traffic Management Roadway

• automated roadway control data (Architecture Flow*) - Control commands and operating parameters provided to field equipment that controls and monitors automated vehicle operations.
  Data Flows*:
  • automated_lane_changing_control_data
  • avo_control_data_changes

• barrier system control (Architecture Flow*) - Information used to configure and control barrier systems that are represented by gates, barriers and other automated or remotely controlled systems used to manage entry to roadways.
  Data Flows*:
  • barrier_system_control

• environmental sensors control (Architecture Flow*) - Data used to configure and control environmental sensors.
  Data Flows*:
  • env_sensor_control_to_roadway

• hri control data (Architecture Flow*) - Data required for HRI information transmitted at railroad grade crossings and within railroad operations.
  Data Flows*:
  • hri_traffic_surveillance
  • indicator_sign_control_data_for_hri
  • rail_operations_advisories
  • rail_operations_device_command

• hri request (Architecture Flow*) - A request for highway-rail intersection status or a specific control request intended to modify HRI operation.
  Data Flows*:
  • rail_operations_requests
  • tms_requests

• lane management control (Architecture Flow*) - Information used to configure and control dynamic lane management systems.
  Data Flows*:
  • lane_management_control

• lighting system control data (Architecture Flow*) - Information used to configure and control roadside lighting systems.
  Data Flows*:
  • lighting_system_control

• reversible lane control (Architecture Flow*) - Control of automated reversible lane configuration and driver information systems.
  Data Flows*:
  • reversible_lane_control_for_highways
  • reversible_lane_control_for_roads

• road user protection device control (Architecture Flow*) - Control requests and operating parameters for mixed roadway and right-of-way systems.
  Data Flows*:
  • road_user_protection_device_configuration

• roadway information system data (Architecture Flow*) - Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio, beacon systems). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.
  Data Flows*:
  • dms_control_data
  • dms_data
  • dms_traffic_metering_data
  • dms_variable_speed_limit_data
  • dms_wide_area_alert_information
  • har_data
  • har_wide_area_alert_information

• roadway warning system control (Architecture Flow*) - Information used to configure and control roadway warning systems.
  Data Flows*:
  • roadway_warning_system_control

• safeguard system control (Architecture Flow*) - Data that controls safeguard systems (remotely controlled equipment used to mitigate the impact of incidents on transportation infrastructure, such as blast shields, exhaust systems, etc.).
  Data Flows*:
  • safeguard_system_control

• shoulder management control (Architecture Flow*) - Information used to configure and control systems that allow use of a shoulder as a lane for vehicular traffic.
  Data Flows*:
  • shoulder_management_control

• signal control commands (Architecture Flow*) - Control of traffic signal controllers or field masters including clock synchronization.
  Data Flows*:
  • indicator_control_data_for_signal_control

• signal control device configuration (Architecture Flow*) - Data used to configure traffic signal control equipment including local controllers and system masters.
  Data Flows*:
  • indicator_control_configuration_data_for_signal_control

• signal control plans (Architecture Flow*) - Traffic signal timing parameters including minimum green time and interval durations for basic operation and cycle length, splits, offset, phase sequence, etc. for coordinated systems.
  Data Flows*:
  • signal_system_timing_plan

• signal system configuration (Architecture Flow*) - Data used to configure traffic signal systems including configuring control sections and mode of operation (time based or traffic responsive).
  Data Flows*:
  • signal_system_configuration

• speed monitoring control (Architecture Flow*) - Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems.
  Data Flows*:
  • speed_sensor_control_from_traffic

• traffic metering control (Architecture Flow*) - Control commands and operating parameters for ramp meters, interchange meters, mainline meters, and other systems equipment associated with roadway metering operations.
  Data Flows*:
  • indicator_control_data_for_traffic_metering
  • indicator_control_monitoring_data_for_traffic_metering

• traffic sensor control (Architecture Flow*) - Information used to configure and control traffic sensor systems.
  Data Flows*:
  • sensor_configuration_data

• variable speed limit control (Architecture Flow*) - Information used to configure and control variable speed limit systems including the equipment used to provide current speed limits and other information to drivers and the equipment used to monitor traffic and environmental conditions along the roadway.
  Data Flows*:
  • variable_speed_limit_control

• vehicle signage data (Architecture Flow*) - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows*:
  • vehicle_sign_data

• video surveillance control (Architecture Flow*) - Information used to configure and control video surveillance systems.
  Data Flows*:
  • incident_video_image_control

Transit Vehicle Roadway

• local signal priority request (Architecture Flow*) - Request from a vehicle to a signalized intersection for priority at that intersection.
  Data Flows*:
  • transit_vehicle_roadway_priorities

Vehicle Roadway

• access request (Architecture Flow*) - Request for access to an access-controlled transportation facility.
  Data Flows*:
  • vehicle_barrier_access_request

• automated vehicle status (Architecture Flow*) - Data provided by an automated vehicle identifying it's current mode and operational status, current position and motion, preferred route, and information provided to support checking/checkout and coordinated maneuvers while on the automated facility.
  Data Flows*:
  • avo_route_data
  • avo_vehicle_condition

• environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, 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. 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.
  Data Flows*:
  • vehicle_env_probe_data

• probe archive data (Architecture Flow*) - Probe data that allows calculation of travel times, volumes, and other measures that support transportation planning. Optionally, this flow also includes origin and destination information for vehicles that opt to provide this information.
  Data Flows*:
  • vehicle_guidance_probe_data_for_archive
  • vehicle_traffic_probe_data_for_archive

• traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows*:
  • vehicle_guidance_probe_data
  • vehicle_traffic_probe_data

• vehicle diagnostics data (Architecture Flow*) - Information about the vehicle and its current operational status that supports vehicle performance monitoring, service, and repair. The flow identifies the vehicle and vehicle type and provides information about the vehicle's current operational status, the current performance of engine-related components, and notification of any identified malfunctions.
  Data Flows*:
  • vehicle_status_details_for_emissions

• vehicle intersection safety data (Architecture Flow*) - Vehicle path and acceleration data provided by vehicles approaching or occupying an intersection. It identifies the intersection, vehicle position and motion, the anticipated lane and movement that will be used in the intersection, and notification of potential violations or other detected safety hazards.
  Data Flows*:
  • vehicle_status_for_intersection

• vehicle occupancy (Architecture Flow*) - The number of occupants detected by the vehicle.
  Data Flows*:
  • vehicle_occupants_detected

• vehicle profile (Architecture Flow*) - Information about a vehicle including vehicle type and equipment capabilities.
  Data Flows*:
  • vehicle_characteristics_for_roadway

• vehicle safety data (Architecture Flow*) - Vehicle safety data indicating vehicle location, vehicle motion (speed, heading, acceleration), vehicle control (brakes, steering, throttle, exterior lights), basic vehicle characteristics (length, width). May also include additional vehicle status (e.g., anti-lock brake activation, stability control system activation).
  Data Flows*:
  • vehicle_roadside_safety_data

Vehicle Characteristics Roadway

• vehicle characteristics (Architecture Flow*) - The physical or visible characteristics of an individual vehicle that can be measured to classify a vehicle and imaged to uniquely identify a vehicle.
  Data Flows*:
  • From_Vehicle_Characteristics

Wayside Equipment Roadway

• arriving train information (Architecture Flow*) - Information for a train approaching a highway-rail intersection that may include direction and allow calculation of approximate arrival time and closure duration.
  Data Flows*:
  • fwe-train_data

• track status (Architecture Flow*) - Current status of the wayside equipment and notification of an arriving train.
  Data Flows*:
  • fwe-approaching_train_announcement
  • fwe-wayside_equipment_status

Weather Service Roadway

• environmental sensors control (Architecture Flow*) - Data used to configure and control environmental sensors.
  Data Flows*:
  • fws-roadway_env_sensor_control