F3.2.13 Classify and Identify Incidents

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.13 Classify and Identify Incidents

Project:

F3.2 Manage Incidents

F3.2.13 Classify and Identify Incidents : 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:	{E04909A4-37EE-452e-841B-C7C27E8C4C34}
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 identify and classify incidents. (2) The ability to use data about potential incidents that is provided by other functionality in other parts of the System, or data that it collects directly for itself. (3) The ability for the data from other parts of the System to have been received directly from terminators, or has been processed by other functionality from inputs that it has received. (4) The ability to determine that there is a good chance that the received data shows that an incident has occurred. (5) The ability to process the data to identify and classify the particular type of incident that it has been detected, according to the source using its own internal "rules" that may relate to some form of approved standard. (6) As part of the identification process, the ability to combine data that sensibly belongs to the same incident, e.g. the progressive advance of congestion following an accident. (7) The ability to analyse data about the weather to see if it will create a hazard for Vehicles. (8) When the identification and classification of the incident has been completed, the ability to send the data about it for storage and subsequent assessment of the necessary mitigation strategies by other functionality.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_High_Level_Function» F3.2 Manage Incidents FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_new_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.2.4.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fv-incident_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fws-weather_data_for_incidents FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_bridge_dangerous_conditions FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_roadworks_information_for_incident_management FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.peo-event_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psef.mt_incident_data_update FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-accident_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo.mt_FTEP_abnormal_load_incident FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.2.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_tunnel_exceptional_conditions FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.0.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.5.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft-incident_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.43 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_icing_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_operator_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo.mt_declare_FTEP_implementation_incident FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 9.5.6.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd-incident_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_environmental_incident_inputs FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.mt_data_for_vehicles_as_incidents FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pepf.mt_accident_warning FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psef.mt_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-strike_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_detection_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 any of the input data flows;<br/>(b) when any of the data flows containing incident data is received in (a) analyse the data compare it with other data and build a "picture" of a possible incident;<br/>(c) the analysis in (b) shall include the amalgamation of data that appears to be about two incidents into that for a single incident, e.g. the progressive formation of congestion due to a single incident;<br/>(d) when the strike details or accident information data flows are received from the Multi-Modal System Terminator, convert their contents into an incident in terms of the likely effect on road congestion and then make it an incident;<br/>(e) when the weather data for incidents data flow is received from the Weather Systems Terminator, analyse its contents to see if the expected weather conditions are likely to cause a hazard to drivers and if so, convert the data into that for an incident;<br/>(f) when any of the data flows containing maintenance data is received in (a) convert it into roadworks data;<br/>(g) when the data flow containing event data is received from the Planned Event Organiser Terminator, determine its likely impact on the flow of traffic in the road network so that it can become an incident when the event occurs;<br/>(h) when the data flow containing data from vehicles that are reporting themselves as incidents is received in (a), convert this data into data into that for an incident;<br/>(i) when the environmental incident inputs data flow is received, analyse its contents to see if the consequences of the environmental incident are likely to cause a hazard to drivers and if so, convert the data into that for an incident;<br/>(j) when the data flow containing incident detection data is received, check to see if it is related to data previously processed and if so amalgamate into that data so that "duplicate" incidents are not reported;<br/>(k) as a result of (b) to (j) send the data about the incident in the data flow containing new incident data to the Manage Store of Incident Data function.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0