Prerequisite
One has to define disruption rules
| ![]() ![]() | ||||||||||||||||||||||||||||
Example: Let's analyze simple scenario, where one of flight-related roster activities was changed by the planner. It will be analyzed against the rule presented above.
Final outcome: there was no disruption on that day for this crew. | ![]() | ||||||||||||||||||||||||||||
Algorithm: This kind of assessment is performed for every crew chosen (or all crew that fall into the crew filter) for every day within the range. Such day-crew "cells" are analysed against every active and period-valid rule. If one rule is violated for that "cell" - further processing is stopped and algorithm is proceeding to the next one. The outcome Final report will contain disruption occurences per crew as well as some basic statistics.
In the example below: - 1 crew times 8 days = 8 roster days - 2 disrupted days In total (2/8)*100% = 25% | |||||||||||||||||||||||||||||
![]() |