We will introduce the update to the 'Floating Base' positioning flight functionality.

'Floating Base' positioning flight policy allows setting up the behavior of the sales module regarding the automated application of FERRY flights.

The 'Floating Base' option will allow setting up 2 threshold values:

• Positioning - threshold value for the positioning before the 1st sector with PAX/0PAX within the request
• Repositioning - threshold value for the repositioning after the last sector with PAX/0PAX within the request

The values in the 'Floating Base' settings are inserted in the HH format, e.g. 10 for 10 hours.

Inserting 0 will indicate that, depending on the field, the Positioning/Repositioning does not apply.

Threshold-wise, the following checks will be made:

• Positioning
  • number of hours between the last sector, other than FERRY, booked and the beginning of the first sector with PAX/0PAX within the quote, and
  • 'NOW' against the beginning of the first sector with PAX/0PAX within the quote

• Repositioning:
  • number of hours between the last sector with PAX/0PAX within the quote and the beginning of the next booked flight, other than the FERRY flight

If the abovementioned conditions are met, as well as the 'Add positionings automatically' checkbox is ticked when adding/updating the request, or the 'ADD POSITIONING' option within the quote is selected, the positionings will be added to the request.

'Positioning flight policy' values for 'Floating Base' are set as below:

Positioning before departure

In this scenario, as presented in the screenshot on the right-hand side, the positioning is added before the first flight with PAX within the request because:

• 'Positioning' threshold is set to 24h
• Preceding flight with PAX lands in LPPR at 1600LT on the 26th
• The following flight with PAX from the request is set to depart from LPPT at 1000LT on the 27th
• Since the difference is less than 24h, the positioning from LPPR to LPPT is added

Positioning and Repositioning applied

In this scenario, as presented in the screenshot on the right-hand side, both positioning and repositioning are added to the request because:

• 'Positioning' threshold is set to 24h and the 'Repositioning' threshold is set to 10h
• Preceding flight with PAX lands in LPPR at 1600LT on the 26th
• The following flight with PAX from the request is set to depart from LPPT at 1000LT on the 27th
• Since the difference is less than 24h, the positioning from LPPR to LPPT is added
• The last flight with PAX within the request lands in LIRA at 0915LT on the 1st
• The following booked flight with 0PAX is set to depart from EPWA at 1400LT on the 1st
• Since the difference is less than 10h, the repositioning from LIRA to EPWA is added

Repositioning after arrival

In this scenario, as presented in the screenshot on the right-hand side, the repositioning is added after the last flight with PAX within the request because:

• 'Repositioning' threshold is set to 10h
• The last flight with PAX within the request lands in LIRA at 0915LT on the 1st
• The following booked flight with 0PAX is set to depart from EPWA at 1400LT on the 1st
• Since the difference is less than 10h, the repositioning from LIRA to EPWA is added