Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Next minimum rest after

The next minimum rest or rest after will now serve as the master rest. It will the one extended after longer duty periods or due to TZ crossing.

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

Example:

If the crew is crossing several TZ during a rotation, then the min rest after the FDP will be extended.

Logs

The FDP Log History contains the calculations logs to help the user to understand the calculations behind the scheduling.

Example:
In case a min rest after is extended because of an FDP crossing TZ, the logs will explain why it has been increased and the amount of TZ crossed.

New nomenclature

Scheduling options

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

  • a non-extended maxFDP (Basic)

  • a 1h planned maxFDP extension (Extension) with a rest before and after 2h extension

  • a 1h planned maxFDP extension (Extension) with a rest after 4h extension

  • a max FDP extended by Split Duty (Split Duty)

  • a max FDP by the use of extensions due to In-flight Rest (Augmented Crew)

Basic

A non-extended max FDP.

Split Duty

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 absorbed into the FDP immediately on the left).

Absorbed right

The flight leg is included in the next FDP (gets 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?


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:

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

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

  • Rest Period

  • Days Off

  • Vacation

  • SDO

  • No labels