F3.2.11 Provide Operator Interface for Incident Management

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.11 Provide Operator Interface for Incident Management

Project:

F3.2 Manage Incidents

F3.2.11 Provide Operator Interface for Incident Management : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:29
Modified:	08.09.2021 11:24:32

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{ADA498C2-ED42-42bf-97C6-B0DB656A3409}
Appears In:	DFD F3.2 Manage Incidents, Functional Tree of F3.2 Manage Incidents

This Function shall be capable of providing the following facilities: (1) A HMI through which the Road Network Operator can control the management of incidents and the implementation of incident strategies. (2) The HMI shall enable the Road Network Operator to confirm the implementation of incident management strategies if needed, to input and update incident data in the store of Incident Data, and to manage the development of new incident management strategies. (3) The HMI shall enable the Road Network Operator to request and receive statistical reports on the occurrence of incidents and the use strategies.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» to.rno-confirm_incident_strategy_implementation FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_implement_requested_strategy FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_incident_strategy_creation FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_command_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_statistics_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.rno-requested_incident_data_analysis FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.2 Manage Incidents FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_implementation_confirmed FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.rno-incident_strategies_removed FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.rno-requested_incident_statistics FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_operator_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.rno-incident_strategy_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_confirm_incident_strategy_implementation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.rno-request_incident_statistics FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.rno-create_incident_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.rno-request_incident_data_analysis FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_implemented FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_created FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategies_removed FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.rno-implement_incident_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_command_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_statistics_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) when the first trigger input data flow is received, the command shall be checked for syntax and consistency;<br/>(b) when (a) is complete, the action needed shall be determined;<br/>(c) if the result of (b) is that the action needed is to output incident data or produce a statistical report, the request for the retrieval of the data and preparation of the report shall be sent to the Manage Store of Incident Data function using the first trigger output data flow;<br/>(d) when the result of (c) is received through the third trigger input data flow, the contents shall be output directly to the Operator;<br/>(e) if the result of (b) is that implementation of an incident management strategy is to be confirmed, or a new strategy is being provided, the data shall be sent to the incident assessment Function using the second trigger output data flow;<br/>(f) if the result of (b) is that new incident data or assessment "rules" are being provided then the data shall be sent to the Identification and Classification function using the third trigger output data flow;<br/>(g) when the third trigger input data flow is received, the contents shall be output to the operator using the other output data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0