Traffic Operations Personnel --> Traffic Management Center:
traffic operator input
Definitions
traffic operator input (Information 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.
Traffic Operations Personnel (Source Physical Object): 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Traffic Management Center (Destination Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Included In
This Triple is in the following Service Packages:
- PS08: Roadway Service Patrols
- PS09: Transportation Infrastructure Protection
- PS10: Wide-Area Alert
- PS11: Early Warning System
- PS12: Disaster Response and Recovery
- PS13: Evacuation and Reentry Management
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST04: Roadside Lighting
- ST06: HOV/HOT Lane Management
- ST07: Eco-Lanes Management
- ST10: Low Emissions Zone Management
- TI07: In-Vehicle Signage
- TM01: Infrastructure-Based Traffic Surveillance
- TM03: Traffic Signal Control
- TM04: Connected Vehicle Traffic Signal System
- TM05: Traffic Metering
- TM06: Traffic Information Dissemination
- TM07: Regional Traffic Management
- TM08: Traffic Incident Management System
- TM09: Integrated Decision Support and Demand Management
- TM12: Dynamic Roadway Warning
- TM16: Reversible Lane Management
- TM18: Drawbridge Management
- TM19: Roadway Closure Management
- TM20: Variable Speed Limits
- TM21: Speed Harmonization
- TM22: Dynamic Lane Management and Shoulder Use
- TM24: Tunnel Management
- TM25: Wrong Way Vehicle Detection and Warning
- TM26: Signal Enforcement
- VS07: Road Weather Motorist Alert and Warning
- VS08: Queue Warning
- VS10: Restricted Lane Warnings
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
- WX01: Weather Data Collection
- WX03: Spot Weather Impact Warning
- WX04: Roadway Micro-Prediction
This triple is associated with the following Functional Objects:
- TMC Barrier System Management
- TMC Basic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Environmental Monitoring
- TMC Evacuation Support
- TMC Incident Detection
- TMC Incident Dispatch Coordination
- TMC In-Vehicle Signing Management
- TMC Lighting System Control
- TMC Multimodal Crossing Management
- TMC Regional Traffic Management
- TMC Restricted Lanes CV Application
- TMC Reversible Lane Management
- TMC Roadway Equipment Monitoring
- TMC Roadway Warning
- TMC Safeguard System Management
- TMC Service Patrol Management
- TMC Signal Control
- TMC Signal Enforcement
- TMC Traffic Information Dissemination
- TMC Traffic Management Decision Support
- TMC Traffic Metering
- TMC Traffic Network Performance Evaluation
- TMC Variable Speed Limits
This Triple is described by the following Functional View 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-dynamic_lane_mgmt_control
- 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-infrastructure_sensor_control
- 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-roadway_warning_system_control
- ftop-signal_enforcement_device_control
- ftop-static_data
- ftop-strategy_override
- ftop-time_dependent_operations_input
- ftop-traffic_data_parameter_updates
- ftop-traffic_information_requests
- ftop-update_defined_incident_responses
- ftop-variable_speed_limit_control_parameters
- ftop-vehicle_signage_input
- ftop-vehicle_speed_sensor_control
- ftop-video_camera_strategy_change
- ftop-weather_request_information
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Traffic Management Center | Traffic Operations Personnel | traffic operator data |
Communication Solutions
No communications solutions identified.Characteristics
None defined |
Interoperability | Description |
---|---|
Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | High | High | |
Basis | Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. |