Traffic Management (Subsystem*)

Diagrams for Traffic Management Subsystem (TMS):

• Subsystem Interfaces
• Terminator Interfaces

Functionality: Equipment Packages* and PSpecs*

• Barrier System Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.4.5-Manage Barrier Systems

• Collect Traffic Surveillance (Equipment Package*)
  PSpecs:
  • 1.1.2.1-Process Traffic Data for Storage
  • 1.1.2.2-Process Traffic Data
  • 1.1.2.3-Update Data Source Static Data
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.1.4.4-Update Traffic Display Map Data
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface
  • 1.3.4.6-Process Video Data

• HRI Traffic Management (Equipment Package*)
  PSpecs:
  • 1.6.2.1-Exchange Data with Rail Operations
  • 1.6.2.2-Manage Alerts and Advisories
  • 1.6.4.1-Manage HRI Closures
  • 1.6.4.2-Exchange Data with Traffic Management

• Rail Operations Coordination (Equipment Package*)
  PSpecs:
  • 1.1.3-Generate Predictive Traffic Model
  • 1.6.2.1-Exchange Data with Rail Operations
  • 1.6.2.3-Manage Rail Traffic Control Data

• Safeguard System Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 5.7.6.2-Manage Safeguard Systems

• TMC Automated Vehicle Operations (Equipment Package*)
  PSpecs:
  • 3.2.7-Manage Automatic Vehicle Operations

• TMC Demand Management Coordination (Equipment Package*)
  PSpecs:
  • 1.1.2.1-Process Traffic Data for Storage
  • 1.1.2.2-Process Traffic Data
  • 1.2.1-Select Strategy
  • 1.2.6.1-Maintain Traffic and Sensor Static Data
  • 1.2.6.2-Provide Static Data Store Output Interface
  • 1.4.1-Provide Traffic Operations Personnel Demand Interface
  • 1.4.2-Collect Demand Forecast Data
  • 1.4.4-Implement Demand Management Policy

• TMC Environmental Monitoring (Equipment Package*)
  PSpecs:
  • 1.1.2.8-Process Roadway Environmental Data
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.3.2.1-Store Possible Incident Data
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface

• TMC Evacuation Support (Equipment Package*)
  PSpecs:
  • 1.1.5-Exchange Data with Other Traffic Centers
  • 1.2.1-Select Strategy
  • 1.3.6-Traffic Disaster Response Control
  • 1.3.7-Traffic Evacuation Control

• TMC Freeway Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.1-Select Strategy
  • 1.2.2.1-Determine Indicator State for Freeway Management
  • 1.2.3-Determine Ramp State
  • 1.2.4.2-Output Control Data for Freeways

• TMC HOV Lane Management (Equipment Package*)
  PSpecs:
  • 1.1.2.4-Monitor HOV lane use
  • 1.2.4.2-Output Control Data for Freeways
  • 5.4.1-Process TM Detected Violations

• TMC Incident Detection (Equipment Package*)
  PSpecs:
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.3.1.1-Analyze Traffic Data for Incidents
  • 1.3.1.2-Maintain Static Data for Incident Management
  • 1.3.2.1-Store Possible Incident Data
  • 1.3.2.2-Review and Classify Possible Incidents
  • 1.3.2.3-Review and Classify Planned Events
  • 1.3.2.4-Provide Planned Events Store Interface
  • 1.3.2.5-Provide Current Incidents Store Interface
  • 1.3.3-Respond to Current Incidents
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface
  • 1.3.4.6-Process Video Data

• TMC Incident Dispatch Coordination/Communication (Equipment Package*)
  PSpecs:
  • 1.1.2.2-Process Traffic Data
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.5-Exchange Data with Other Traffic Centers
  • 1.2.1-Select Strategy
  • 1.3.2.1-Store Possible Incident Data
  • 1.3.2.2-Review and Classify Possible Incidents
  • 1.3.2.3-Review and Classify Planned Events
  • 1.3.2.6-Manage Traffic Routing
  • 1.3.3-Respond to Current Incidents
  • 1.3.4.1-Retrieve Incident Data
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface
  • 1.3.4.3-Provide Media Incident Data Interface
  • 1.3.4.4-Update Incident Display Map Data
  • 1.3.4.5-Manage Resources for Incidents
  • 1.3.4.6-Process Video Data
  • 1.3.5-Manage Incident Response Planning
  • 1.3.6-Traffic Disaster Response Control
  • 1.3.7-Traffic Evacuation Control
  • 1.6.2.1-Exchange Data with Rail Operations

• TMC In-Vehicle Signing Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.4.3-Output In-vehicle Signage Data
  • 1.2.8-Collect Traffic Field Equipment Fault Data

• TMC Lighting System Control (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.4.6-Manage Lighting System

• TMC Multimodal Coordination (Equipment Package*)
  PSpecs:
  • 1.2.2.1-Determine Indicator State for Freeway Management
  • 1.2.2.2-Determine Indicator State for Road Management
  • 1.2.3-Determine Ramp State
  • 1.4.2-Collect Demand Forecast Data

• TMC Multimodal Crossing Management (Equipment Package*)
  PSpecs:
  • 1.1.2.2-Process Traffic Data
  • 1.1.4.1-Retrieve Traffic Data
  • 1.2.4.1-Output Control Data for Roads
  • 1.2.4.4-Output Roadway Information Data
  • 1.3.2.2-Review and Classify Possible Incidents

• TMC Probe Information Collection (Equipment Package*)
  PSpecs:
  • 1.1.2.1-Process Traffic Data for Storage
  • 1.1.2.5-Process Traffic Probe Data
  • 1.1.4.1-Retrieve Traffic Data

• TMC Regional Traffic Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.1.5-Exchange Data with Other Traffic Centers

• TMC Reversible Lane Management (Equipment Package*)
  PSpecs:
  • 1.1.2.2-Process Traffic Data
  • 1.1.2.7-Monitor Reversible Lanes
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.4.1-Output Control Data for Roads
  • 1.2.4.2-Output Control Data for Freeways
  • 1.3.1.1-Analyze Traffic Data for Incidents
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface

• TMC Signal Control (Equipment Package*)
  PSpecs:
  • 1.1.2.2-Process Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.1-Select Strategy
  • 1.2.2.2-Determine Indicator State for Road Management
  • 1.2.4.1-Output Control Data for Roads

• TMC Speed Monitoring (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 9.3.3.3-Monitor Vehicle Speed on Roadway

• TMC Traffic Information Dissemination (Equipment Package*)
  PSpecs:
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.1.4.3-Provide Direct Media Traffic Data Interface
  • 1.2.4.4-Output Roadway Information Data

• TMC Traffic Management Decision Support (Equipment Package*)
  PSpecs:
  • 1.3.4.2-Provide Traffic Operations Personnel Incident Data Interface
  • 1.3.5-Manage Incident Response Planning

• TMC Traffic Network Performance Evaluation (Equipment Package*)
  PSpecs:
  • 1.1.2.1-Process Traffic Data for Storage
  • 1.1.2.2-Process Traffic Data
  • 1.1.3-Generate Predictive Traffic Model
  • 1.1.4.1-Retrieve Traffic Data
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.1.5-Exchange Data with Other Traffic Centers
  • 1.2.6.1-Maintain Traffic and Sensor Static Data
  • 1.2.6.2-Provide Static Data Store Output Interface
  • 1.3.2.1-Store Possible Incident Data
  • 1.4.1-Provide Traffic Operations Personnel Demand Interface
  • 1.4.2-Collect Demand Forecast Data
  • 1.4.3-Update Demand Display Map Data
  • 1.4.5-Calculate Forecast Demand

• TMC Transportation Operations Data Collection (Equipment Package*)
  PSpecs:
  • 1.1.2.1-Process Traffic Data for Storage
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface

• TMC Work Zone Traffic Management (Equipment Package*)
  PSpecs:
  • 1.1.4.2-Provide Traffic Operations Personnel Traffic Data Interface
  • 1.2.4.4-Output Roadway Information Data
  • 1.3.1.1-Analyze Traffic Data for Incidents
  • 1.3.2.1-Store Possible Incident Data
  • 1.3.2.2-Review and Classify Possible Incidents

• Traffic Data Collection (Equipment Package*)
  PSpecs:
  • 1.1.4.5-Manage Traffic Archive Data

• Traffic Maintenance (Equipment Package*)
  PSpecs:
  • 1.1.4.4-Update Traffic Display Map Data
  • 1.2.8-Collect Traffic Field Equipment Fault Data

Inputs/Outputs: Architecture Flows* and Data Flows*

Alerting and Advisory Systems Traffic Management

• alerts and advisories (Architecture Flow*) - Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system.
  Data Flows*:
  • faas-alerts_and_advisories_for_traffic

Archived Data Management Subsystem Traffic Management

• archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
  Data Flows*:
  • traffic_management_archive_request

• archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
  Data Flows*:
  • traffic_management_archive_status

• archived data products (Architecture Flow*) - Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
  Data Flows*:
  • traffic_archive_data_product

Border Inspection Systems Traffic Management

• border incident information (Architecture Flow*) - Notification of existence of incident in the vicinity of the border. Information would include expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided.
  Data Flows*:
  • fbis-border_traffic_incident

• lane management inputs (Architecture Flow*) - This flow provides inputs to traffic operations dynamic message signs on the types of vehicles to allow in each lane as well as other lane management messages that might be used by traffic operations.
  Data Flows*:
  • fbis-border_lane_management

• remote surveillance control (Architecture Flow*) - The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.
  Data Flows*:
  • fbis-border_remote_video_control

DMV Traffic Management

• registration (Architecture Flow*) - Registered owner of vehicle and associated vehicle information.
  Data Flows*:
  • fdmv-traffic_violation_state_identity
  • fdmv-traffic_violation_vehicle_registration

Emergency Management Traffic Management

• alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This flow may also identify specific information that should not be released to the public.
  Data Flows*:
  • deactivate_traveler_information_restrictions_for_traffic
  • traveler_information_restrictions_for_traffic
  • wide_area_alert_notification_for_traffic

• emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
  Data Flows*:
  • disaster_response_plan_coordination_to_traffic
  • evacuation_plan_coordination_to_traffic

• emergency route request (Architecture Flow*) - Request for access routes for emergency response vehicles and equipment. This may be a request for ingress or egress routes or other emergency routes.
  Data Flows*:
  • emergency_route_request

• emergency traffic control request (Architecture Flow*) - Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign.
  Data Flows*:
  • barrier_system_activation_request_from_emerg
  • emergency_traffic_control_request
  • roadway_information_data_to_traffic
  • safeguard_system_activation_request_from_emerg

• evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows*:
  • evacuation_information_for_traffic_management

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • incident_details

• incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
  Data Flows*:
  • incident_response_status

• remote surveillance control (Architecture Flow*) - The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.
  Data Flows*:
  • remote_video_image_control

• resource deployment status (Architecture Flow*) - Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included.
  Data Flows*:
  • em_resource_response_to_traffic

• resource request (Architecture Flow*) - A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency.
  Data Flows*:
  • resource_request
  • traffic_evacuation_resource_request

• threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
  Data Flows*:
  • threat_info_for_traffic

• transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • disaster_transportation_system_status_for_traffic
  • evacuation_transportation_system_status_for_traffic
  • infrastructure_integrity_status_for_traffic

Emissions Management Traffic Management

• widearea statistical pollution information (Architecture Flow*) - Aggregated region-wide measured emissions data and possible pollution incident information.
  Data Flows*:
  • pollution_incident
  • pollution_state_data
  • wide_area_pollution_data

Event Promoters Traffic Management

• event plans (Architecture Flow*) - Plans for major events possibly impacting traffic.
  Data Flows*:
  • fevp-event_information

Information Service Provider Traffic Management

• fare and price information (Architecture Flow*) - Current transit, parking, and toll fee schedule information.
  Data Flows*:
  • parking_lot_charge_details
  • toll_price_details
  • transit_fare_details

• logged vehicle routes (Architecture Flow*) - Anticipated route information for guided vehicles, special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor's motorcade) that may require changes in traffic control strategy.
  Data Flows*:
  • current_other_routes_use
  • current_transit_routes_use
  • logged_special_vehicle_route
  • route_segment_use_prediction
  • special_vehicle_priority_routing

• road network traffic probe data (Architecture Flow*) - Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions.
  Data Flows*:
  • current_road_network_use
  • traffic_probe_info_from_isp_for_traffic

• transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
  Data Flows*:
  • transportation_information_for_traffic_operations

Intermodal Freight Depot Traffic Management

• intermodal freight event information (Architecture Flow*) - Plans for movement of intermodal freight from the depot area possibly impacting traffic. May also include requests for special treatment at traffic signals.
  Data Flows*:
  • fifd-intermodal_freight_event

Maintenance and Construction Management Traffic Management

• current asset restrictions (Architecture Flow*) - Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
  Data Flows*:
  • asset_restrictions_for_traffic

• equipment maintenance status (Architecture Flow*) - Current status of field equipment maintenance actions.
  Data Flows*:
  • field_equip_maint_status

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • incident_info_for_traffic

• maint and constr resource response (Architecture Flow*) - Current status of maintenance and construction resources including availability and deployment status. General resource inventory information covering vehicles, equipment, materials, and people and specific resource deployment status may be included.
  Data Flows*:
  • m_and_c_resource_response_to_traffic

• maint and constr work plans (Architecture Flow*) - Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
  Data Flows*:
  • m_and_c_work_plans_for_traffic

• road network status assessment (Architecture Flow*) - Assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • m_and_c_status_assessment_for_traffic

• road weather information (Architecture Flow*) - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
  Data Flows*:
  • road_weather_info_for_traffic

• roadway maintenance status (Architecture Flow*) - Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
  Data Flows*:
  • roadway_maint_status_for_traffic

• work zone information (Architecture Flow*) - Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
  Data Flows*:
  • work_zone_images_for_traffic
  • work_zone_info_for_traffic

Map Update Provider Traffic Management

• map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
  Data Flows*:
  • fmup-demand_display_update
  • fmup-incident_display_update
  • fmup-traffic_display_update

Media Traffic Management

• external reports (Architecture Flow*) - Traffic and incident information that is collected by the media through a variety of mechanisms (e.g., radio station call-in programs, air surveillance).
  Data Flows*:
  • fm-incident_information

Multimodal Crossings Traffic Management

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

Other Traffic Management Traffic Management

• traffic control coordination (Architecture Flow*) - Information transfers that enable remote monitoring and control of traffic management devices. This flow is intended to allow cooperative access to, and control of, field equipment during incidents and special events and during day-to-day operations. This flow also allows 24-hour centers to monitor and control assets of other centers during off-hours, allows system redundancies and fail-over capabilities to be established, and otherwise enables integrated traffic control strategies in a region.
  Data Flows*:
  • fotm-device_control_request
  • fotm-traffic_control_and_status

• traffic information coordination (Architecture Flow*) - Traffic information exchanged between TMC’s. Normally would include incidents, congestion data, traffic data, signal timing plans, and real-time signal control information.
  Data Flows*:
  • fotm-data_request
  • fotm-transfer_data
  • request_local_current_incidents_data

Parking Management Traffic Management

• parking demand management response (Architecture Flow*) - Response to parking demand management change requests indicating level of compliance with request.
  Data Flows*:
  • parking_lot_charge_change_response
  • parking_lot_charge_direct_details

• parking information (Architecture Flow*) - General parking information and status, including current parking availability.
  Data Flows*:
  • dynamic_parking_information_for_traffic
  • parking_information_for_dissemination
  • parking_lot_current_state
  • static_parking_information_for_traffic

Rail Operations Traffic Management

• railroad advisories (Architecture Flow*) - Real-time notification of railway-related incident or advisory.
  Data Flows*:
  • fro-incident_notification

• railroad schedules (Architecture Flow*) - Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
  Data Flows*:
  • fro-maintenance_schedules
  • fro-train_schedules

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

• freeway control status (Architecture Flow*) - Current operational status and operating parameters for ramp meters, mainline metering/lane controls and other control equipment associated with freeway operations.
  Data Flows*:
  • indicator_input_data_from_highways
  • indicator_status_from_highways

• 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

• 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

• request for right-of-way (Architecture Flow*) - Forwarded request from 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_override_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

• 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

• 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

• signal control status (Architecture Flow*) - Status of surface street signal controls including operating condition and current operational state.
  Data Flows*:
  • indicator_input_data_from_roads
  • indicator_status_from_roads

• 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. This flow includes the images and the operational status of the surveillance system.
  Data Flows*:
  • incident_video_image
  • traffic_video_image
  • traffic_video_image_for_display
  • video_device_status

• 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

Surface Transportation Weather Service Traffic Management

• environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included.
  Data Flows*:
  • fstws-env_sensor_data_for_traffic

• transportation weather information (Architecture Flow*) - Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making.
  Data Flows*:
  • fstws-surface_trans_weather_forecasts
  • fstws-surface_trans_weather_observations

Toll Administration Traffic Management

• toll probe data (Architecture Flow*) - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
  Data Flows*:
  • toll_probe_data_for_traffic

• toll service change response (Architecture Flow*) - Response to toll service change requests indicating level of compliance with request.
  Data Flows*:
  • toll_price_changes_response
  • toll_price_direct_details

Traffic Management Archived Data Management Subsystem

• archived data product requests (Architecture Flow*) - A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
  Data Flows*:
  • traffic_archive_data_product_request

• traffic archive data (Architecture Flow*) - Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
  Data Flows*:
  • traffic_management_archive_data

Traffic Management Border Inspection Systems

• border incident information (Architecture Flow*) - Notification of existence of incident in the vicinity of the border. Information would include expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided.
  Data Flows*:
  • tbis-traffic_border_incident

• traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and the operational status of the surveillance system.
  Data Flows*:
  • tbis-traffic_border_incident_video

Traffic Management DMV

• license request (Architecture Flow*) - Request supporting registration data based on license plate read during violation.
  Data Flows*:
  • tdmv-traffic_violation_identity_code
  • tdmv-traffic_violation_vehicle_license

Traffic Management Emergency Management

• alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
  Data Flows*:
  • alert_notification_status_from_traffic

• emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
  Data Flows*:
  • disaster_response_plan_coordination_from_traffic
  • evacuation_plan_coordination_from_traffic

• emergency routes (Architecture Flow*) - Suggested ingress and egress routes for access to and between the scene and staging areas or other specialized emergency access routes.
  Data Flows*:
  • emergency_route_response

• emergency traffic control information (Architecture Flow*) - Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status.
  Data Flows*:
  • barrier_system_status_to_emerg
  • emergency_traffic_control_response
  • roadway_information_status_from_traffic
  • safeguard_system_status_to_emerg
  • traffic_evacuation_status

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • incident_alert_details
  • incident_response_clear
  • planned_events_for_em_response
  • wrong_way_vehicle_detection

• incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
  Data Flows*:
  • current_traffic_incident_response

• resource deployment status (Architecture Flow*) - Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included.
  Data Flows*:
  • resource_deployment_status

• resource request (Architecture Flow*) - A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency.
  Data Flows*:
  • em_resource_request_from_traffic

• road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
  Data Flows*:
  • roadway_detours_and_closures_for_em
  • roadway_detours_and_closures_for_em_response
  • traffic_data_for_em_response
  • traffic_data_for_emergency_services

• road network status assessment (Architecture Flow*) - Assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • network_status_from_traffic_for_disaster
  • network_status_from_traffic_for_evacuation

• traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and the operational status of the surveillance system.
  Data Flows*:
  • incident_video_for_emergency_services

Traffic Management Emissions Management

• pollution state data request (Architecture Flow*) - Aggregated emissions data information request.
  Data Flows*:
  • pollution_state_data_request

Traffic Management Enforcement Agency

• request for enforcement (Architecture Flow*) - Request for traffic enforcement to address safety issues in a work zone or other special situations.
  Data Flows*:
  • tea-enforcement_request_from_traffic

• traffic violation notification (Architecture Flow*) - Notification to enforcement agency of a detected traffic violation including speed violations and HOV violations.
  Data Flows*:
  • tea-traffic_violation_data

Traffic Management Event Promoters

• event confirmation (Architecture Flow*) - Confirmation that special event details have been received and processed.
  Data Flows*:
  • tevp-event_confirmation

Traffic Management Information Service Provider

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • planned_events
  • traffic_incident_data_for_isp

• road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
  Data Flows*:
  • current_highway_network_state
  • current_road_network_state
  • link_data_for_guidance
  • prediction_data
  • reversible_lane_signal_state_for_freeways
  • reversible_lane_signal_state_for_roads
  • roadway_detours_and_closures_for_isp
  • traffic_data_for_isp
  • traffic_road_weather_data_for_isp

Traffic Management Intermodal Freight Depot

• intermodal freight traffic confirmation (Architecture Flow*) - Confirmation that details concerning the movement of intermodal freight on the roadway network have been received and processed. May also include information on traffic conditions affecting the depot.
  Data Flows*:
  • tifd-intermodal_freight_event_confirmation
  • tifd-traffic_data_for_intermodal_freight

Traffic Management Maintenance and Construction Management

• field equipment status (Architecture Flow*) - Identification of field equipment requiring repair and known information about the associated faults.
  Data Flows*:
  • field_equipment_status_from_traffic

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • incident_info_from_traffic
  • planned_events_for_maint

• maint and constr resource request (Architecture Flow*) - Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of resources.
  Data Flows*:
  • m_and_c_resource_request_from_traffic
  • roadway_maint_action_req_from_traffic
  • winter_maint_action_req_from_traffic

• road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
  Data Flows*:
  • environmental_sensor_data_from_traffic_management
  • road_network_info_from_traffic
  • roadway_detours_and_closures_for_m_and_c

• road network status assessment (Architecture Flow*) - Assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
  Data Flows*:
  • disaster_network_status_from_traffic_to_m_and_c

• work plan feedback (Architecture Flow*) - Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system.
  Data Flows*:
  • m_and_c_plan_feedback_from_traffic

Traffic Management Map Update Provider

• map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
  Data Flows*:
  • tmup-map_static_data
  • tmup-request_demand_display_update
  • tmup-request_incident_display_update
  • tmup-request_traffic_display_update

Traffic Management Media

• incident information for media (Architecture Flow*) - Report of current desensitized incident information prepared for public dissemination through the media.
  Data Flows*:
  • tm-incident_data

• road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
  Data Flows*:
  • tm-traffic_data

Traffic Management Other Traffic Management

• traffic control coordination (Architecture Flow*) - Information transfers that enable remote monitoring and control of traffic management devices. This flow is intended to allow cooperative access to, and control of, field equipment during incidents and special events and during day-to-day operations. This flow also allows 24-hour centers to monitor and control assets of other centers during off-hours, allows system redundancies and fail-over capabilities to be established, and otherwise enables integrated traffic control strategies in a region.
  Data Flows*:
  • totm-device_control_request
  • totm-traffic_control_and_status

• traffic information coordination (Architecture Flow*) - Traffic information exchanged between TMC’s. Normally would include incidents, congestion data, traffic data, signal timing plans, and real-time signal control information.
  Data Flows*:
  • totm-data_request
  • totm-transfer_data

Traffic Management Parking Management

• parking demand management request (Architecture Flow*) - Request to change the demand for parking facility use through pricing or other mechanisms.
  Data Flows*:
  • parking_lot_charge_change_request
  • parking_lot_charge_direct_request

• parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
  Data Flows*:
  • parking_lot_dynamic_information_request_by_traffic
  • parking_lot_static_information_request_by_traffic

• parking lot inputs (Architecture Flow*) - Instructions for operation of local parking facilities to support regional traffic management objectives (e.g. which parking lot exits to use). Also, includes inputs from traffic sensors to support calculation of parking lot occupancy and support more effective management of parking entrances and exits.
  Data Flows*:
  • parking_lot_input_data
  • selected_parking_lot_control_strategy
  • static_data_for_parking_lots

Traffic Management Rail Operations

• hri advisories (Architecture Flow*) - Notification of Highway-Rail Intersection equipment failure, intersection blockage, or other condition requiring attention, and maintenance activities at or near highway rail intersections.
  Data Flows*:
  • tro-equipment_status
  • tro-event_schedules
  • tro-incident_notification

Traffic Management Roadway Subsystem

• 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

• freeway control data (Architecture Flow*) - Control commands and operating parameters for ramp meters, mainline metering/lane controls and other systems associated with freeway operations.
  Data Flows*:
  • indicator_control_data_for_highways
  • indicator_control_monitoring_data_for_highways

• 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

• 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

• 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_wide_area_alert_information
  • har_data
  • har_wide_area_alert_information

• 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

• signal control data (Architecture Flow*) - Information used to configure and control traffic signal systems.
  Data Flows*:
  • indicator_control_data_for_roads
  • indicator_control_monitoring_data_for_roads

• 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 sensor control (Architecture Flow*) - Information used to configure and control traffic sensor systems.
  Data Flows*:
  • sensor_configuration_data

• 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

Traffic Management Surface Transportation Weather Service

• environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included.
  Data Flows*:
  • tstws-env_sensor_data_from_traffic

• transportation weather information request (Architecture Flow*) - A request for transportation weather information that may specify the area of interest (a geographic region, particular routes within a region, specific road segments), the type of information that is required, the desired spatial resolution of the information, and time horizon.
  Data Flows*:
  • tstws-trans_weather_info_request

Traffic Management Toll Administration

• toll service change request (Architecture Flow*) - Request to change pricing, modify restrictions, or modify operations of a toll road facility
  Data Flows*:
  • toll_price_changes_request
  • toll_price_direct_request

Traffic Management Traffic Operations Personnel

• traffic operator data (Architecture Flow*) - 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.
  Data Flows*:
  • ttop-archive_status
  • ttop-barrier_safeguard_status
  • ttop-current_field_equip_fault_data
  • ttop-deactivate_information_restrictions
  • ttop-defined_incident_responses_data
  • ttop-demand_data
  • ttop-demand_forecast_data
  • ttop-demand_forecast_result
  • ttop-demand_policy_activation_result
  • ttop-demand_policy_information
  • ttop-device_control_request_from_other_center
  • ttop-disaster_response_plan_input_request
  • ttop-env_sensor_status
  • ttop-evacuation_plan_input_request
  • ttop-incident_information_display
  • ttop-incident_video_image_output
  • ttop-lighting_system_status
  • ttop-possible_defined_response_output
  • ttop-possible_incidents_data
  • ttop-resource_response
  • ttop-roadway_incident_status
  • ttop-roadway_info_status
  • ttop-traffic_control_information_display
  • ttop-traveler_information_restrictions
  • ttop-undefined_response_details
  • ttop-vehicle_signage_status
  • ttop-vehicle_speed_sensor_data
  • ttop-video_device_status
  • ttop-video_image_output
  • ttop-weather_information
  • ttop-wide_area_alert_notification
  • ttop-wrong_way_detection

Traffic Management Transit Management

• incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
  Data Flows*:
  • current_incidents_data_for_transit
  • incident_response_log_for_transit
  • planned_events

• request transit information (Architecture Flow*) - Request for transit service information and current transit status.
  Data Flows*:
  • transit_conditions_demand_request
  • transit_fare_direct_request
  • transit_services_demand_request

• road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
  Data Flows*:
  • prediction_data
  • roadway_detours_and_closures_for_transit
  • traffic_data_for_transit

• traffic control priority status (Architecture Flow*) - Status of signal priority request functions at the roadside (e.g. enabled or disabled).
  Data Flows*:
  • transit_highway_priority_given
  • transit_ramp_priority_given
  • transit_road_priority_given

• transit demand management request (Architecture Flow*) - Request to change the demand for transit facility use through pricing or other mechanisms.
  Data Flows*:
  • transit_services_changes_request

Traffic Management Weather Service

• environmental conditions 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 and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included.
  Data Flows*:
  • tws-env_sensor_data_from_traffic

Traffic Operations Personnel Traffic Management

• traffic operator inputs (Architecture Flow*) - 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.
  Data Flows*:
  • ftop-alert_notification_status
  • ftop-archive_command
  • ftop-barrier_safeguard_control_parameters
  • ftop-decision_support_parameters
  • ftop-defined_incident_response_data_request
  • ftop-defined_incident_response_data_update
  • ftop-demand_data_request
  • ftop-demand_data_update_request
  • ftop-demand_forecast_request
  • ftop-demand_policy_activation
  • ftop-demand_policy_information_request
  • ftop-demand_policy_updates
  • ftop-device_control_request_to_other_center
  • ftop-disaster_response_plan_input
  • ftop-env_sensor_control
  • ftop-evacuation_plan_input
  • ftop-field_equip_fault_data_input
  • ftop-field_equip_fault_data_request
  • ftop-hov_control_parameters
  • ftop-imbalance_parameters
  • ftop-incident_camera_action_request
  • ftop-incident_data_amendment
  • ftop-incident_information_requests
  • ftop-lighting_system_control_parameters
  • ftop-output_possible_defined_responses
  • ftop-request_possible_incidents_data
  • ftop-resource_request
  • ftop-reversible_lane_restriction_data
  • ftop-roadway_characteristics
  • ftop-roadway_incident_input
  • ftop-roadway_info_input
  • ftop-static_data
  • ftop-strategy_override
  • ftop-traffic_data_parameter_updates
  • ftop-traffic_information_requests
  • ftop-update_defined_incident_responses
  • ftop-vehicle_signage_input
  • ftop-vehicle_speed_sensor_control
  • ftop-video_camera_strategy_change
  • ftop-weather_request_information

Transit Management Traffic Management

• emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
  Data Flows*:
  • emergency_transit_schedule_information_for_traffic
  • evacuation_transit_schedule_information_for_traffic

• traffic control priority request (Architecture Flow*) - Request for signal priority at one or more intersections along a particular route.
  Data Flows*:
  • transit_highway_overall_priority
  • transit_ramp_overall_priority
  • transit_road_overall_priority

• transit demand management response (Architecture Flow*) - Response to transit demand management change requests indicating level of compliance with request.
  Data Flows*:
  • transit_services_changes_response

• transit probe data (Architecture Flow*) - Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
  Data Flows*:
  • transit_probe_data_for_traffic

• transit system data (Architecture Flow*) - Current transit system operations information indicating current transit routes, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.
  Data Flows*:
  • transit_fare_direct_details
  • transit_running_data_for_demand
  • transit_services_for_demand

Weather Service Traffic Management

• environmental conditions data status (Architecture Flow*) - 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.
  Data Flows*:
  • fws-traffic_environment_sensor_data_status

• qualified environmental conditions 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) 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.
  Data Flows*:
  • fws-env_sensor_data_for_traffic

• weather information (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
  Data Flows*:
  • fws-current_weather_observations
  • fws-weather_forecasts