Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These are the main features introduced by the use of the SchedulingEngine Scheduling Engine as the new NuvolOps FTL Engine for FTL crew scheduling.

Next

...

Minimum Rest After

The next minimum rest or rest after Next Minimum Rest or Rest After will now serve as the master rest. It will be the one rest extended after longer duty periods or due to TZ crossing time zones.

The duration of the rest before Rest Before the FDP will only depend only on whether the departure is from or away from home base.

Example:

If the crew is crossing several TZ time zones during a rotation, then the next minimum rest the Next Minimum Rest after the FDP will be extended.

...

These new fields, which can be found inside the Flight Duty Period (FDP) record, offer comprehensive information regarding FDPs and rest durations as well as any scheduling unfeasibility information.

Example:
In this example, the min rest after Next Minimum Rest after the FDP is extended because of an FDP crossing TZ. he logs will explain why it time zones.

...

The Log History in Crew Board will also explain why the FDP has been increased and the amount of crossed TZtime zones.

...

New

...

Nomenclature

Scheduling

...

Options

The Scheduling Engine can calculate several scheduling options which correspond to different Maximum Daily FDP scenarios allowed by the AOC FTL rules:

...

Basic

A non-extended max FDP.

...

Split Duty

The use of Split Duty during an FDP.

...

Extension

The max FDP 1h planned extension.

...

Absorption

...

Options

Standalone

The flight leg is the only event in the FDP.

...

Absorbed

...

Left

The flight leg is included in the previous FDP (gets is absorbed into the FDP immediately on the left).

...

Absorbed

...

Right

The flight leg is included in the next FDP (gets is absorbed into the FDP immediately on the right).

...

Error

...

Messages

The Scheduling Engine system runs several calculations in parallel to increase the system’s efficiency. This might lead to situations when a long error message is displayed to the user. We have planned in the next weeks some enhancements, based on your feedback, to only display the key FTL error messages.

The error message will show the list of scheduling and absorption options as a title, for easier spotting. Amy Jo how can we phrase that the huge error message is divided into “sections” with titles so the. users can find the info on why their desired option is not feasible?

...

For this reason, error messages are longer than those seen in the past.

To assist schedulers, the error message displays all the potential scheduling options grouped by their option titles, as explained above, along with the reason that option is not feasible.

...

Based on your feedback, we will have some enhancements in the coming weeks to only display the key FTL error messages.

Mandatory Weekly Rest (only active for some AOCs)

A crew member is not allowed to be scheduled on a flight without a valid planned weekly rest. The following error is returned:

Warning

Never more than 168 hours between the end of one weekly rest period and the start of the next.

Events that counts count as weekly rest (if they are longer than 36h and if they include 2 local nightnights):

  • Rest Period

  • Days Off

  • Vacation

  • SDO

Observer event after FDP not included in the FDP

The new system configuration does not consider a Crew Member operating as an Observer on a FL part of the Flight Crew.
Hence, an Observer count as a flight duty period only if performed immediately prior to a flight or prior to a series of flight.

If you have any concerns about the accuracy of the configuration, please feel free to raise them, and we can have a discussion to address any discrepancies