Overview

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.

Functional Requirements

(a) on receipt of the first input trigger data flow all of the output data flows shall be sent
(b) on receipt of any of the second to fifth input trigger data flows, the appropriate output data flows requesting strategy or incident data shall be sent
(c) when the responses to (b) have been received, all of the output data flows shall be sent.

Diagrams

Parent Higher Level Function

• 3.2 Manage Incidents

Input logical dataflows

• fesp.b-request_current_incident_strategies
• fesp.b-request_incident_data
• fesp.ttip-request_current_incident_strategies
• fesp.ttip-request_incident_data
• mt_incident_strategy_for_external
• mt_requested_incident_data

Output logical dataflows

• mt_reqeust_incident_strategies_for_external
• mt_request_incident_data
• tesp.b-incident_strategy_information
• tesp.b-requested_incident_data
• tesp.ttip-incident_strategy_information
• tesp.ttip-requested_incident_data

User needs