User rights
The user rights shown below need to be enabled in order to view the EASA Roster Disruption Report:
Using the report
First, you need to define the disruption rules.
- Name: This is a mandatory field.
- Shortcode: This is a mandatory field.
- From: Roster filter specifying what was assigned.
- To: Roster filter specifying what it was changed to.
- Diff Type:
- Ignore: Ignore difference values.
- CI: Difference to Check In.
- CO: Difference to Check Out.
- CICO: Difference to Check In and/or Check Out.
- DS: Difference to Duty Start.
- DE: Difference to Duty End.
- Diff Value: Specifies the tolerance in minutes - if the time of the roster’s event (i.e., check-in time) is changed by more than this value in the succeeding roster - that would qualify this change as a disruption.
- Time Span: Specifies the time in days - how long before the time of the roster’s event (i.e. check-in time) can the roster be changed in order to avoid disruption. If the roster is changed shorter ahead of its actual occurrence - that would qualify this change as a disruption.
- Valid From/To: When the rule is valid.
Example
Let's analyze a simple scenario, where one of the flight-related roster activities was changed by the planner. It will be analyzed against the rule presented above.
- The name and shortcode do not affect the result.
- Roster filters "From" and "To" chosen certainly must be specified separately, but let's assume that the name "Flights/SBY" means that this filter would pick up regular flights both from "previous" and "changed" roster. This means they are taken into account and can be evaluated further.
- Diff Type tells us that the event we should be looking at is check-in time. It got changed from 2:30 to 3:30 on the same day, which gives us a 60-minute difference.
- Diff Value defines that disruption occurs only if the roster got changed by more than 70 minutes; therefore in the present case, we do not violate rules - changed roster differs by 60 minutes.
- Even if we are sure that there was no violation due to a small check-in time change, let us check the Time Span field. Change in roster was introduced on 24AUG17 1419, while roster activity will take place 27AUG17 0230, which means that change was done approximately 2.5 days ahead. The Time Span field value was 3 days, which means that in terms of this condition, there was a violation.
- Active and Valid From - Due to the values of those fields this rule is considered.
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 analyzed against every active and period-valid rule. If one rule is violated for that "cell" - further processing is stopped and the algorithm is proceeding to the next one.
The outcome:
The final report contains disruption occurrences per crew as well as some basic statistics:
- Disruption percentage per crew (count of days with disruption occurrence divided by analyzed days count expressed in %).
- Total # of crew analyzed.
- Total # of crew with disruption in analyzed period (1 occurrence is enough for crew to be counted in).
- Overall Disruption Percentage - roster days (crew-day cell) with disruption divided by overall roster days analyzed.
In the example below:
- 1 crew times 8 days = 8 roster days
- 2 disrupted days
In total (2/8)*100% = 25%
