Low Level Function
3.2.6 Assess Incidents and Devise Responses

Overview

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 not 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.

Functional Requirements

(a) continuously monitor for the receipt of the inter-urban traffic data for incidents, urban traffic data for incidents and incident strategy data flows
(b) when any of the data flows in (a) is received, store the data that they contain internally for future use
(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
(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
(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
(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
(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
(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
(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 which ever 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
(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
(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
(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
(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
(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
(o) when the response in (n) is received, the strategy in (m) shall be implemented, this shall be achieved by sending which ever 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
(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
(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.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 3.2 Manage Incidents
  • Functional tree 3.2

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    7.1.3.6
    The system shall be able to implement planned control strategies for planned events (e.g. sport, cultural, etc.).
    7.2.0.1
    The system shall detect and respond to various incidents on the road network.
    7.2.0.10
    The system shall be able to co-ordinate the implementation of incident management strategies between associated TCCs.
    7.2.0.2
    The system shall not do anything to reduce road safety.
    7.2.0.3
    The system shall not do anything that might aggravate, or cause, an incident.
    7.2.0.4
    The system shall assist the emergency services to provide an effective response to road traffic incidents.
    7.2.0.8
    The system shall be able to suggest one or more responses for dealing with an incident.
    7.2.0.9
    The system shall be able to run (pre-)defined incident mitigation strategies automatically.
    7.2.4.1
    The system shall be able to minimise the consequences of an incident on the road network for those travellers who are not involved.
    7.4.1.17
    (X)FCD - The system shall be able to communicate with another vehicle either directly, or via an road-side device. (Communications).
    7.4.1.31
    Traffic Condition Warning - The system shall be able to warn drivers in a timely manner of moving incidents (e.g. road/winter maintenance vehicles, long/wide loads) via an in-vehicle display.
    7.4.1.35
    Hazardous Location Notification - The system shall be able to warn drivers in a timely manner of incidents ahead (e.g. road works, accident, traffic queue) via an in-vehicle display.  Where available and relevant this information shall include lane(s)/road section(s) affected and expected delay.
    7.4.1.36
    Hazardous Location Notification - The system shall be able to warn the driver in a timely manner, via an in-vehicle display, of adverse road surfaces and weather conditions along the planned route.
    7.4.1.43
    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).
    7.4.1.44
    Hazardous Location Notification - The system shall be able to send information about incidents ahead in the next section from a road-side device to drivers via an in-vehicle device.
    7.4.1.47
    Hazardous Location Notification - The system shall be able to send information about incidents on the road network ahead from the TCC to drivers via an in-vehicle device.
    7.4.1.48
    Hazardous Location Notification - The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display.
    7.4.2.5
    The system shall provide "copies" of the traffic signs that are relevant to the current section of the road (e.g. speed limit, road hazards, junctions) to the driver at all times via an in-vehicle display.
    7.4.3.7
    The system shall be able to advise a driver, via an in-vehicle device, which lane to use when passing an incident/accident.
    7.4.3.8
    The system shall be able to advise a driver, via an in-vehicle device, where to stop safely (e.g. an appropriate exit lane, hard shoulder).
    7.4.5.1
    The system shall enable the TCC to calculate recommended headways for the current traffic and environment conditions.
    7.5.1.20
    The system shall enable the TCC to instruct drivers, via an in-vehicle device, of an alternative route that should be followed (to avoid an incident).
    7.5.1.3
    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.
    7.5.1.8
    The system shall enable the TCC to inform drivers, via an in-vehicle device, about (foreseen and unexpected) incidents on the driver’s planned route.
    7.5.1.9
    The system shall be able to warn the driver, via an in-vehicle device, of incidents in the urban road network as they are detected.
    7.6.2.4
    The system shall enable the traveller information service provider to receive current inter-urban traffic management, and weather, conditions and planned events.
    9.5.6.5
    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.