[WIP] Actual Rest vs Possible Rest

NuvolOps way of computing crew member’s rest is changing in April 2023 from Actual Rest to Possible Rest.

Actual Rest (former method)

This is what has been used in the past in the Staff Center, both in the Stats section and the FTL Report. Actual rest used only rest events (days off, vacation, etc.) to get the total number of days off a crew has had.

This relies heavily on the automatic creation of Days Off events.

What is the automatic creation of Days off?

The days off are automatically created by what we call the ‘'Days Off scheduled process.’'

The ‘'Days Off scheduled process’' is a process that gets triggered every night and creates past Days Off calendar events in every crew member’s calendar, filling in all the empty space between duty events.

This was done to count all the rest a crew member has had. Even though they are not needed now with the new implementation, the scheduled process will continue to run for a few months to ensure a smooth transition to the new system.

Possible Rest (new method)

This is what the Crew Board has been using since it went live in Jan 2021. It uses all rest events + empty space to compute how many days off a crew member has had. Therefore, it doesn't rely on the creation of days off events (less complexity of the system → fewer places where things can go wrong).

Starting in April 2023, this will also be used in the Staff Center in both the Stats page and FTL Report.

Comparison between Possible Rest and Actual Rest

Here's an example of the differences in a crew member's mock schedule:

What we can see in this calendar’s month:

The Crew member is scheduled on several flight legs
The Crew member is scheduled in a few flight training events during the month
There are no rest events

Stats page

In the following screenshot, we see how the stats page looks using possible rest based on the calendar shown above:

In this screenshot, we see how it appeared previously using actual rest. We can see that it is missing days off since the rest events don’t exist or don’t fully encroach the local nights:

Keep in mind that the sections on these screenshots will depend on each operator’s configuration, so the information displayed will change.

FTL Report

This will only affect those operators where the total number of days off and/or hours since the weekly rest are shown.

In this screenshot, we see that the rest time and hours since weekly rest have values that are much more accurate to the reality of the crew member’s schedule and no warnings (highlighted cells) are shown.

Similarly, the cumulative rest in the FTL Report is also impacted by this change.

Automatic Days Off

Even though days off events are no longer needed, we will continue creating automatic Days Off events in the past to have a smoother transition.