Skip to content
SkyRosterBook a discovery call

EUROCONTROL case studies

What changes when the roster changes?

See how SkyRoster was used to explore staffing, overtime and shift swaps. These five studies come from EUROCONTROL’s rostering guideline, with the method and context alongside each result.

The source document

Air Traffic Services Operations staff/personnel Rostering Best Practices and Tools Guidelines

Reference
NMD/SAF/2653
Edition
Edition 1.0, 26 April 2023
Classification
Green
Published by
EUROCONTROL, Network Management Directorate

“The source of Use cases is SkyRoster.” , page 20

Open the primary guideline (PDF)

Citations refer to printed page numbers. The PDF viewer’s page counter includes the front matter.

What else the guideline attributes to SkyRoster →
  1. Case study 1 · page 21 · 75 ATCOs

    10% workforce cost reduction

    Published source

    Simulation and extrapolation

    Source: NMD/SAF/2653, printed page 21

    The problem, as the guideline states it

    The ANSP wanted to optimize their rosters in one of their ATC units.

    The result, as the guideline states it

    The application managed to cover the same traffic demand and accommodated the same number of leave days during a 30-days cycle using 1 less ATCO.
    Extrapolating the simulations to other units, the ANSP managed to cut annual costs with the workforces with 8-12% per ATC unit, translating in an economy of 750.000 EUR / year.
  2. Case study 2 · page 22 · 96 ATCOs in 12 teams of 8

    1-month Tactical Roster Simulation with the baseline headcount

    Published source

    Simulation

    Source: NMD/SAF/2653, printed page 22

    The problem, as the guideline states it

    An ATC Unit with 96 ATCOs rostered in teams on a fixed shift pattern sees significant variations in terms of overtime distribution per individual staff and increased staff leakage during the night shifts.

    The result, as the guideline states it

    Compared to the previous simulation, in which 24 additional ATCOs were used to reduce overtime to under 300 hours per month, how is the workload distributed when deploying only the current headcount of 96 ATCOs?
  3. Case study 3 · page 34 · 55 ATCOs

    94.3% less overtime

    Published source

    Simulation

    Source: NMD/SAF/2653, printed page 34

    The problem, as the guideline states it

    The ANSP is understaffed, scheduling overtime shifts to cover the demand. Due to overtime shifts, staff is overworked, resulting in alarming fatigue scores.

    The result, as the guideline states it

    The team designed 5 rostering simulations to model their staffing plans in different scenarios.
    In the scenario with the best result, the application managed to decrease the number of overtime days from 247 to only 14 during a 35-day roster cycle.
    With the new design shift roster and same amount of staff the number of overtime has been reduced but also the number of shifts and consequently the ATCOs have a better fatigue index scores.
  4. Case study 4 · page 35 · 450 operational ATCOs

    Automating 60.000 shift swaps to save a ~360 000 EUR/year

    Published source

    Reported deployment and derived saving

    Source: NMD/SAF/2653, printed page 35

    The problem, as the guideline states it

    The customer was experiencing a high number of shift swap requests - 60.000 per year. For each shift swap request, the planning manager wasted 15 minutes of his time to fill in paper forms and update the roster in a spreadsheet. The customer was paying 5 full-time employees only to manage these shift swaps.

    The result, as the guideline states it

    By deploying the application inside their environment, the shift swapping process was reduced to 1.5 minutes on average, counting since the manager receives the swap request in the system.
    Employees were also empowered to swap their shifts self-service, without involving their manager, the Rostering Engine taking care of the responsibility to maintain a safe, compliant roster with every shift swap approved.
    Only by automating the entire shift swapping process, the customer was able to cut costs by 360.000 EUR/year.
  5. Case study 5 · page 36 · 120 ATCOs in 12 teams of 10

    1-month Team-based Roster Simulation with 120 ATCOs

    Published source

    Simulation

    Source: NMD/SAF/2653, printed page 36

    The problem, as the guideline states it

    An ATC Unit with 96 ATCOs rostered in teams on a fixed shift pattern sees significant variations in terms of overtime distribution per individual staff, and increased staff leakage during the night shifts. This simulation focused to look at difference by adding 24 more ATCOs to arrive at 120 ATCOs in total.

    The result, as the guideline states it

    How can the roster balance overtime shifts between available employees for a one month period (April 202z) and minimise leakage?

Evaluation

Define the comparison for your unit.

Use the studies to define useful comparisons and acceptance criteria for your own evaluation.

Establish a baseline

Record your current staffing demand, roster cycle, overtime and administrative workload. Results from another unit are context for comparison, not a forecast.

Separate the variables

Studies 2 and 5 compare staffing scenarios. Study 3 changes the roster design with the same headcount. Distinguish changes in staffing from changes in scheduling.

Test representative workloads

These studies do not provide a production solve-time benchmark. Agree a performance test using your headcount, rules and planning horizon.

Plan a comparison with your own roster.

Book a discovery call to discuss your staffing demand, roster patterns and evaluation criteria.