F3.2.9 Send Incident Details to Information Providers

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.9 Send Incident Details to Information Providers

Project:

F3.2 Manage Incidents

F3.2.9 Send Incident Details to Information Providers : 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:	{87CF97FD-DF01-4d54-A339-ECA9B0E3B794}
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 output of information to External Service Providers as part of an incident strategy in response to incidents that have been detected by other functionality . (2) The ability for the Providers to also request a repeat of the output of the information and of incident data, where this applies to current or future events, i.e. not incidents involving the Emergency Services. (3) The ability for the output of the information to begin as soon as the strategy information is received. (4) The ability to keep a local store of the incident management strategies currently being implemented and delete them when their expiry time has passed, or when a strategy modification or removal indication arrives from the incident management functionality.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» tesp.b-requested_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_incident_data 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» tesp.b-incident_strategy_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.ttip-incident_strategy_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_reqeust_incident_strategies_for_external FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.ttip-requested_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» fesp.ttip-request_current_incident_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.3 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.2.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_requested_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_strategy_for_external FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.ttip-request_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.b-request_current_incident_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.2.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.5.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.3.6 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.6.2.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.b-request_incident_data 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 receipt of the fourth and/or fifth input trigger data flows:<br/>(b) when either of the data flows in (a) is received send the strategy for external data flow;<br/>(c) on completion of (b) continuously monitor for receipt of the incident strategy for externals data data flow:<br/>(d) when the data flow in (c) is received, send the fourth and/or fifth output data flows, depending on which data flows were received in (b);<br/>(e) continuously monitor for receipt of the third and/or sixth input trigger data flows;<br/>(f) on receipt of either or both of the data flows in (e), send the request incident data flow;<br/>(g) on completion of (f) continuously monitor for receipt of the requested incident data flow:<br/>(h) when the data flow in (g) has been received, send the third and/or fourth output data flows, depending on which data flows were received in (f).<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0