F3.2.6 Assess Incidents and Devise Responses

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.6 Assess Incidents and Devise Responses

Project:

F3.2 Manage Incidents

F3.2.6 Assess Incidents and Devise Responses : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:28
Modified:	22.12.2021 12:37:48

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{E7385835-A669-4853-8BCC-770578F75E6D}
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) The ability to manage the assessment of incident data and to devise strategies in response to incidents that have been detected by other functionality. (2) The ability to periodically review the data that has been collected about incidents and decide if any mitigation action is needed. (3) When mitigation action is needed the ability to either use an existing incident management strategy, or devise a new one. (4) The ability for an incident management strategy to involve a number of measures including changes to the current traffic management strategy, output of warning messages, plus the sending of comments and warnings to other functionality within the System. (5) The ability for the recipients of the warnings and comments shall be defined by the Road Network Operator through the functionality providing the HMI. (6) The ability for the recipients of the warnings and comments to vary from one strategy to another. (7) The ability to check the data and information that it sends for output as part of a strategy to ensure that it is consistent, i.e. all of the actions and warning messages are coherent and do not contradict each other. (8) Before implementing a strategy, the ability to require that confirmation of its use is received from the functionality providing the HMI for the Road Network Operator. (9) The ability to create incident management strategies either in anticipation of an incident or event, or because none of the existing strategies are suitable, following a request from the Road Network Operator received through the functionality providing their HMI. (10) The ability to continually monitor the data that is being collected so that it can remove strategies when incidents or events are no longer in progress. (11) When all the strategies that have been implemented for a particular incident or event have been removed the ability to inform the Road Network Operator to signify that the incident or event has finished, using the functionality providing their HMI.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_for_external 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_for_others FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_for_internal FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategies_removed FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_updated_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_for_vehicles FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_confirm_incident_strategy_implementation FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_load_incident_strategies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_command_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_implemented FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_for_stored_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tors.itms-incident_strategy FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_created FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.2.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.48 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fors.itms-incident_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.5.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.3.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 9.5.6.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_command_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_data_for_assessment FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.44 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.2.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.47 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_implementation_confirmed FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.3.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.36 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.17 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_reqeust_incident_strategies_for_external FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.31 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.43 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.35 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.20 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.3.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.4.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_data_for_incidents FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_traffic_data_for_incidents FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_implement_requested_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_read_incident_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_incident_strategy_creation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for the receipt of the inter-urban traffic data for incidents, urban traffic data for incidents and incident strategy data flows;<br/>(b) when any of the data flows in (a) is received, store the data that they contain internally for future use;<br/>(c) periodically send the data flow containing the request for stored incident data to the Manage Store of Incident Data function to collect new incident data from storage;<br/>(d) when the response to (c) the incident data for assessment data flow is received, the data it contains shall be assessed for the need to take action on current or future incidents taking into account the data received in (a), tunnel conditions and the strategies being implemented by other incident management functionality;<br/>(e) if as a result of (d) an incident management strategy needs to be implemented, the load incident strategies data flow shall be sent to retrieve the strategies that already exist;<br/>(f) as a result of (e) the contents of the read incident strategies data flow shall be assessed to see if there is an appropriate incident strategy to implement;<br/>(g) if no suitable strategy is found (f) the operator shall be informed by sending a no suitable strategy indication in the incident command response data flow to the Provide Operator Interface for Incident Management function;<br/>(h) is as a result of (f) a strategy is found, then the confirm incident strategy implementation data flow shall be sent to the Provide Operator Interface function;<br/>(i) if as a result of (h) the incident strategy implementation confirmed data flow is received, indicating that the strategy in (h) shall be implemented, this shall be achieved by sending whichever of the incident strategy for.... data flows will send implementation commands to the appropriate functionality and to other incident management functionality through the incident strategy data flow;<br/>(j) whilst carrying out (i), the contents of each of the output data flows shall be checked to ensure that their contents are consistent, compatible and coherent;<br/>(k) following (h), (i) and (j) details of the action taken shall be sent back to the Manage Store of Incident Data function for storage using the data flow containing updated incident data and the incident strategy implemented data flow sent to the Provide Operator Interface function;<br/>(l) following (k), if the incident data for assessment data flow is received, (d) shall be repeated and if necessary (h) to (j) shall be repeated;<br/>(m) if as a result of (g), request incident strategy creation data flow is received, an appropriate strategy shall be created, taking account of the contents of the data flows identified in (a), and shall be sent to the store of Incident Strategy Data using the load incident strategies data flow;<br/>(n) as a result of (m) the incident strategy created data flow shall be sent to the Provide Operator Interface function and a response awaited in the implement requested strategy data flow;<br/>(o) when the response in (n) is received, the strategy in (m) shall be implemented, this shall be achieved by sending whichever of the incident strategy for.... data flows will send implementation commands to the appropriate functionality and to other incident management functionality through the incident strategy data flow;<br/>(p) if the implement requested strategy data flow is received, the strategy shall be retrieved from the store of Incident Strategy Data and (h) through (k) repeated;<br/>(q) if the implementation strategy command is received containing the identity of a strategy to be deleted, it shall be removed from the store of Incident Strategy Data and the incident strategy removed data flow sent to the Provide Operator Interface function.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0