Low Level Function
3.2.13 Classify and Identify Incidents
Overview
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.
Functional Requirements
(a) continuously monitor for receipt of any of the input data flows
(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
(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
(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
(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
(f) when any of the data flows containing maintenance data is received in (a) convert it into roadworks data
(g) when the data flow containing event data is received from the event organiser actor, determine its likely impact on the flow if traffic in the road network so that it can become an incident when the event occurs
(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
(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
(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
(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.
Diagrams
Parent Higher Level Function
Input logical dataflows
Output logical dataflows
User needs
Number | Description |
| The system shall minimise the time between the occurrence of an incident and its detection. |
| The system shall be able to validate that an incident has occurred in order to minimise false alarms. |
| The system shall be able to collect and store data on each incident, e.g. location, type, severity, number & type of vehicles involved, the emergency/rescue vehicles needed etc. |
| The system shall be able to identify and classify all incidents on the road network. |
| The system shall be able to monitor the aftermath of an incident. |
| The system shall be able to detect "non-vehicle" incidents before they can escalate into traffic accidents, e.g. bad weather conditions, objects on the road, ghost drivers, etc.
|
| Hazardous Location Notification - The system shall enable a road-side device to select and activate a traffic management strategy in the event of an incident (including poor driving conditions). |
| The system shall be able to monitor the current inter-urban traffic and weather/environmental conditions, identify incidents, assess their impact, make short term predictions, and select and initiate an appropriate mitigation strategy. |
| The system shall enable the TCC to receive information about emergencies, e.g. eCall, ghost drivers. |
| The system shall enable the relevant authority to detect incidents within its area and to re-route any vehicle carrying hazardous goods that will be affected by the consequences of that incident. |