F3.2.12 Detect Incidents from Data

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.12 Detect Incidents from Data

Project:

F3.2 Manage Incidents

F3.2.12 Detect Incidents from Data : 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:	{133EE41B-40A5-49ad-9DB1-822D07A77EEA}
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 analyse the data that it receives about traffic conditions in the road network to see if can detect that possibly incidents have occurred. (2) In the analysis of the data to detect incidents, the ability to enable the use of both data provided by other functionality and video image data as inputs. (3) The ability to analyse all types of data for patterns that suggest the occurrence of an incident and the ability for such patterns to be linked to the same incident if they occur in adjacent sections of the road network. (4) The ability for the term "incident" to include anything that is likely to impede the normal flow of traffic, including such things as wide/long loads and "ghost drivers", i.e. Vehicles travelling against the proscribed direction of traffic flow. (5) The ability to send details of a detected incident occurrence to the classification and storage functionality.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_incident_detection_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:

Element	Source Role	Target Role
«FRAME_User_Need» 7.5.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.2.4.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.28 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.27 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.4.1.22 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_data_for_incident_detection 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» mt_urban_xfcd_for_incident_detection FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ftrfc-presence_indication FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_traffic_data_for_incident_detection FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_xfcd_for_incident_detection FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 9.5.6.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for the receipt of data flows containing traffic data from other functionality;<br/>(b) when any of the data flows in (a) are received, store the data internally and analyse it against other data already received to see if there is any abnormality in the flow of traffic using standard forms of analysis;<br/>(c) if any abnormality is found as a result of (b) check that it is not related to other abnormalities elsewhere in the road network, e.g. in an adjacent downstream road segment;<br/>(d) if related occurrences are found in (c) combine them together as part of the same incident;<br/>(e) as a result of (b) and (d) store the possible incident occurrence locally for future use in the analysis of data that is subsequently received in (b);<br/>(f) also continuously monitor the input of data about traffic flow in the presence indication data flow;<br/>(g) analyse it to determine if there is any abnormality in the flow of traffic including vehicles travelling against the proscribed flow, i.e. "ghost drivers", using standard forms of analysis;<br/>(h) if a possible incident is detected in (g) store the possible incident occurrence locally for future use in the analysis of data that is subsequently received in (f);<br/>(i) as a result of (e) and (h) send details of the detected possible incident to the Classify and Identify Incidents function in the data flow containing incident detection data.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0