Please note: This use case originates from the predecessor project PJ.10-W2-73 FCA as part of the SESAR2020 Programme and is not considered in the current project.
This Use Case describes the actions to be taken in a Flight Centric Area in case of fallback from main (primary) system to fallback system.
Preconditions
Failure of important segments of the main system.
Postconditions: Success end state
The Fallback System is working properly, Flight Centric ATCOs continue their work.
Trigger
Failure of two important modules of the main system. The main system may no longer be used for operations.
Main Flow
- The CMMC displays failure of two important modules of the main system. A Technical Systems Operator detects this warning and informs the Supervisor.
- All Flight Centric ATCOs are informed by the Supervisor and the Supervisor informs the Local Traffic Manager, the Flight Centric PC with EAP role and the EoD and they analyse quickly the situation (situation assessment).
- All the surrounding sectors/units are informed (for example by the Flight Centric ATCOs) about the failure (according to their training concerning such situations) and the possibility of the switch to the fallback system.
- The result of the situation assessment is that the main system cannot be used any longer and a switch to the fallback system must be done.
- The Local Traffic Manager arranges the agreed Traffic Flow Measures.
- All Flight Centric ATCOs are informed about the upcoming switch to the fallback system.
- All surrounding sectors/units are informed (for example by the Supervisor) about the upcoming switch to the fallback system.
- The fallback system gets started and runs properly