This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
leon:ftl-settings [2020/01/03 11:15] rafal [Cumulative Duty Notification] |
leon:ftl-settings [2020/08/24 10:29] rafal [Settings explanation] |
||
---|---|---|---|
Line 33: | Line 33: | ||
---- | ---- | ||
+ | ===== FDP extension options ===== | ||
+ | [{{ : | ||
+ | It is possible to select an extension mode. In order to do that please contact [[support@leonsoftware.com]] | ||
+ | Each of the modes will affect how' | ||
+ | |||
+ | There are **3 modes** to choose from in 'FTL Settings': | ||
+ | |||
+ | * **at any FDP violation** - FTL extension mode that applies FDP+ whenever FDP violation appears during realization, | ||
+ | * **at planned FDP violation** - FTL extension mode that applies FDP+ whenever FDP violation appears during both plan and realization. This means that FDP+ must be planned in order to be applied | ||
+ | * ** always unless manually disabled** - FTL extension mode that applies FDP+ always, even if not needed. This mode works best with " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ------------------- | ||
+ | ===== Particular settings explanation ===== | ||
+ | |||
+ | In this section, we explain the purpose of some of the settings: | ||
+ | |||
+ | - **use_planned_reporting_in_case_of_small_delay** - applies to the following rule in OM7: //Where the delay is 4 hours or more, the maximum FDP shall be based on the more limiting time band of the planned and the actual report time and the FDP starts 4 hours after the original report | ||
+ | time.// It works correctly when the checkboxes are marked in the FTL settings but also original STD must be kept, delayed departure inserted in ' |