1.3.4.2: Provide Traffic Operations Personnel Incident Data Interface
This process shall provide the interface between the traffic operations personnel and the Manage Incidents facility of the Manage Traffic function. It shall enable the personnel to request and amend details of current incidents, planned events, wide area alerts, and predetermined incident responses. The process shall provide an interface to a decision support process that identifies the potential regional impact of recommended courses of action to traffic operations personnel, and shall accept control parameters from personnel. This process shall allow personnel to manually reclassify incidents as possible or current or a planned event. It shall also output to the traffic operations personnel incident details to which no predetermined response currently exists. The process shall support inputs from and outputs to the traffic operations personnel. Where appropriate and/or requested by the traffic operations personnel, the process shall provide the output 'display' in a form incorporating a map of the relevant part(s) of the freeways, surface street and rural roadways served by the function. The process shall obtain the map from a local data store, which it shall request to be updated by another process as and when required. This process shall also receive advisory data from outside of ITS via the Alerting and Advisory Systems terminator. Advisories may cause the response plans to be established and activated based on the type or timing of the advisory.
This process is associated with the Traffic Management Center physical object.
This process is associated with the following application objects:
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
- TMC Traffic Information Dissemination
- TMC Traffic Surveillance
This process is associated with the following data flows:
- alert_notification_status_from_traffic - Out
- deactivate_traveler_information_restrictions_for_traffic - In
- decision_support_parameters - Out
- defined_incident_response_data - In
- defined_incident_response_data_request - Out
- defined_incident_response_update_request - Out
- defined_incident_response_updates - Out
- faas-alerts_and_advisories_for_traffic - In
- ftop-alert_notification_status - In
- ftop-decision_support_parameters - In
- ftop-defined_incident_response_data_request - In
- ftop-defined_incident_response_data_update - In
- ftop-incident_camera_action_request - In
- ftop-incident_data_amendment - In
- ftop-incident_information_requests - In
- ftop-output_possible_defined_responses - In
- ftop-request_possible_incidents_data - In
- ftop-resource_request - In
- ftop-roadway_incident_input - In
- ftop-update_defined_incident_responses - In
- incident_video_image_control_by_traffic_operator - Out
- incident_video_image_for_traffic_operator - In
- operations_incident_data_updates - Out
- operator_log_for_incidents_data - In
- operator_log_for_incidents_data - Out
- possible_defined_responses_output - In
- possible_defined_responses_output_request - Out
- reclassify_incidents - Out
- request_incident_map_display_update - Out
- request_incident_operations_data - Out
- retrieved_incident_operations_data - In
- roadway_info_alert_data - Out
- traffic_operations_resource_request - Out
- traffic_operations_resource_response - In
- traveler_information_restrictions_for_traffic - In
- ttop-deactivate_information_restrictions - Out
- ttop-defined_incident_responses_data - Out
- ttop-incident_information_display - Out
- ttop-incident_video_image_output - Out
- ttop-possible_defined_response_output - Out
- ttop-possible_incidents_data - Out
- ttop-resource_response - Out
- ttop-roadway_incident_status - Out
- ttop-traveler_information_restrictions - Out
- ttop-undefined_response_details - Out
- ttop-video_device_status - Out
- ttop-wide_area_alert_notification - Out
- ttop-wrong_way_detection - Out
- undefined_incident_response - In
- video_device_status_for_traffic_operator - In
- wide_area_alert_notification_for_traffic - In
- wrong_way_vehicle - In