This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
leon:report-ftl-sheet [2020/04/15 05:51] bartek [FTL Sheet] |
leon:report-ftl-sheet [2020/12/31 13:39] bartek |
||
---|---|---|---|
Line 17: | Line 17: | ||
It is possible to view block hours per sector. Mark **Show block times** checkbox in the filter and the column will appear in the report. The data will be displayed in the following format: hh:mm - hh:mm. | It is possible to view block hours per sector. Mark **Show block times** checkbox in the filter and the column will appear in the report. The data will be displayed in the following format: hh:mm - hh:mm. | ||
- | Another | + | Another |
Values such as 'Rest before duty - Min' or 'FDP - Max' are explained when you hover the mouse over the value (see below). | Values such as 'Rest before duty - Min' or 'FDP - Max' are explained when you hover the mouse over the value (see below). | ||
Line 73: | Line 73: | ||
< | < | ||
+ | ---- | ||
+ | |||
+ | ==== Weekly Rest Alternative Options ==== | ||
+ | |||
+ | ----- | ||
+ | |||
+ | Most FTL regulations contain a requirement for scheduling an extended recovery recurrent rest period once every few days, usually called a **weekly rest**. For example: | ||
+ | |||
+ | //" | ||
+ | |||
+ | or, more precisely: | ||
+ | |||
+ | //(…) weekly rest period, being a 36-hour period including two local nights, such that there shall never be more than 168 hours between the end of one weekly rest period and the start of the next.// | ||
+ | |||
+ | It is reflected in Leon’s FTL Settings by weekly_rest_min_length (in this case, 36 hours) and weekly_rest_max_separation (in this case, 168 hours). Other settings can be used to specify whether the weekly rest should include local nights, or whether it can be reduced, or performed outside the crew member’s home base. | ||
+ | |||
+ | However, this is rarely that simple. Some regulations allow for an alternative rest instead of the regular one, for example: | ||
+ | |||
+ | //(…) rest periods will be extended at least//: | ||
+ | |||
+ | * //to the **36 hours** uninterrupted rest period including **2 local nights** in the course of **7 consecutive days**//, or | ||
+ | |||
+ | * //to the **60 hours** uninterrupted rest period including **3 local nights** in the course of **10 consecutive days**// | ||
+ | |||
+ | which often leads to some confusion, especially in the case of alternating 36/60 “weekly” rest patterns. | ||
+ | |||
+ | So far this has been implemented in Leon in a way that FTL would require the basic (36-hour) rest to happen within the first 7 days following the previous weekly rest. If such rest is not scheduled in that period, FTL starts to require the alternative (longer) extended rest period. It can be illustrated with the following example: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | ------- | ||
+ | |||
+ | Recently, we encountered a **different phrasing of the weekly rest regulations**, | ||
+ | |||
+ | //Before beginning an FDP or standby, an FCM must have had at least 1 of the following:// | ||
+ | |||
+ | * //in any consecutive 7-day period before the projected end of the assigned FDP or standby: 1 off-duty period of at least 36 consecutive hours, including 2 local nights//; **or** | ||
+ | * //in any consecutive 10-day period before the projected end of the assigned FDP or assigned standby: 1 off-duty period of at least 60 consecutive hours, including 3 local nights//. | ||
+ | |||
+ | From the previous example, one can infer that the FDPs on 14-DEC and 15-DEC are actually not permitted, since there is neither a 36-hour rest in the previous 7 days (08-DEC–14-DEC) nor a 72-hours in the previous 10 days (05-DEC–14-DEC). The correct illustration would be as follows: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | < | ||
+ | |||
+ | This new “**forward**” mode of calculating weekly rest can be enabled by setting **// | ||