Introduction
The original functionality and user interface, of the Flight seat regulation, has undergone some amendments to the user dialog and therefore this revision has been created.
Definitions
Term | Description |
Allotment | Purchased number of seats/rooms |
Available | Purchased – sold |
Flight seat regulation
Flight seat regulation means that available seats can be limited for specific travel durations, in order to obtain the highest possible occupancy on flights.
Without regulation there exists the possibility that available seats on outbound flights cannot be sold because there may not exist available seats, on the corresponding inbound flights.
Since, the majority of bookings will be made for durations up to, and including 15 days, tour operators wish to make sure that the maximum occupancy is reached for these durations.
Flight seat regulation settings
With in the DaVinci settings the Project manager would define the durations that shall be calculated for the flight seat regulation interface, and activate this functionality
To restrict/set the number and length of duration with in the interface results: i.e. 8, 11, 12, 15, 22, and 29 days the user has to enter the nights for the duration calculation.
Calculation of Departures
Thursday and Saturday departures
Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
Duration calculations for return flights:
Possible durations for Thursday departures | From 01/07 – till? |
3 day | 01 – 03/07 |
8 day | 01 – 08/07 |
10 day | 01 – 10/07 |
15 day | 01 – 15/07 |
17 day | 01 – 17/07 |
22 day | 01 – 22/07 |
24 day | 01 – 24/07 |
29 day | 01 – 29/07 |
31 day | 01 – 31/07 |
Etc. | 01/07 + |
Possible durations for Saturday departures | From 03/07- till? |
6 day | 03 – 08/07 |
8 day | 03 – 10/07 |
13 day | 03 – 15/07 |
15 day | 03 – 17/07 |
20 day | 03 – 22/07 |
22 day | 03 – 24/07 |
27 day | 03 – 29/07 |
29 day | 03 – 31/07 |
Etc. | 03/07 + |
Wednesday and Saturday departures
Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
30/06 | 1 | 2 | 3 | |||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
Duration calculations for return flights:
Possible durations for Wednesday departures | From 30/06 – till? |
4 day | 30/06 – 03/07 |
8 day | 30/06 – 07/07 |
11 day | 30/06 – 10/07 |
15 day | 30/06 – 14/07 |
18 day | 30/06 – 17/07 |
22 day | 30/06 – 21/07 |
25 day | 30/06 – 24/07 |
29 day | 30/06 – 28/07 |
32 day | 30/06 – 31/07 |
Etc. | 30/06 + |
Possible durations for Saturday departures | From 03/07- till? |
5 day | 03 – 07/07 |
8 day | 03 – 10/07 |
12 day | 03 – 14/07 |
15 day | 03 – 17/07 |
19 day | 03 – 21/07 |
22 day | 03 – 24/07 |
26 day | 03 – 28/07 |
29 day | 03 – 31/07 |
Etc. | 03/07 + |
Maintenance of flight seat regulation
Flight seat regulation is complex for the end user and there needs to be a user-friendly interface that gives an overview of the available seats (outbound and inbound) for a specific city pairs. Within this interface user will be able to limit the available seats on inbound flights for a specific duration.
Booking Code Settings
For regulating of destination, or booking codes, the user will have to assign to the booking codes an origin and destination. The definitions of these values are taken from the statistic codes – Destination.
For an outbound flight i.e. PRG RHO/QSA the origin should be PRG and destination RHO.
The inbound flight RHO PRG/QSA would therefore have the origin RHO and destination PRG.
This functions as the initial pairing for flights, as there can exist more than one flight (Booking code), or more seat classes with similar or unique allotments.
Flight rotations do not have to be set up for flight regulation functionality.
However, if it would be preferred to link corresponding flights (Booking codes) flag the corresponding flights, and the Flight Destination will change to Corresponding flights. Where as, in the drop down box you will then have the choices of booking codes rather than Statistical codes. Important: the booking code linked must also be linked to this booking code for this to function in the regulation dialog! Additionally, these results will not be listed with those of the Destination in the flight regulation, and vice versa.
Dialog Flight Seat Regulation
Upon opening the Dialog the user will have to enter the departure (Origin) and Arrival (Destination) locations for the destination that is desired to be regulated.
Important: The catalog must be selected, and only regulate from Outbound to destination, and not from the Destination to original Outbound location. Do not leave the fields date from and to blank, as the calculation will take longer. Pick as close to the specific departure dates (from outbound location) that you wish to regulate as possible.
Column | Description |
Dep. Date | Date of departure |
Days | Which day of the week the departure occurs |
Class out | Service class |
Flight | Outbound Flight - Kontikopf Description |
Sub allot.out | Outbound flight sub allotment |
Departure Gar | Amount of defined Guaranteed allotments for the outbound flight for specific class, date, and allotment |
Departure Non | Amount of defined Non-Guaranteed allotments for the outbound flight for specific class, date, and allotment |
Class in | The inbound flight service class (must be identical to outbound) |
Flight in | Inbound flight – Kontikopf description (must be cooresponding to outbound description) |
Sub allot.in | Inbound flight sub allotment – must be identical to outbound sub allotment |
Result Gar | Sum of Guaranteed allotments for inbound flights in the row |
Result Non | Sum of Non-Guaranteed allotments for inbound flights in the row |
Departure duration | 7, 10, 11, 14, 21… |
Gar | Amount of Guaranteed allotments defined/available for this duration |
Non | Amount of Non-Guaranteed allotments defined/available for this duration |
Lim | The amount of seats that the user wishes limit for a specific duration. The limitation is placed on the inbound flight. |
Occ. | The number of occupied seats (allotments) with in the matching combination of allotments on the specified duration. |
For the departure on 27/06/2008, duration length 14, there are 170 seats defined. From this amount 12 have been occupied in this combination of out and inbound allotments and there exists a limitation of 38 seats. This means that there cannot be more than 38 seats sold for the 14 night duration.
A user can also see other departures that share the same return date (highlighted in Blue, when a field is selected). Additionally, the return date is shown in the lower right hand corner of the dialog, for the selected return.
- Actual status Radio button
This will display the actual bookable status for you allotments. It is not recommended to limit flights from this view; only from the total view is recommended.
Of the 38 limited seats for this duration and combination, 12 have been reserved. In the actual status the amount is converted for user reference.
Package finder
The limitation of seats is visible in the package finder transport availability fields.
Mandatory to display the amount limited are the following fields:
Catalog, Destination, Transportation, departure date, and (important) Nights
In the below example, duration is not filled. Therefore, Flight seat regulation is not checked. Reason for this is that system requires what the expected duration to calculate is. Below, there is only one departure date (however there could have been more) and the return date for a 14 night departure can be the same as a 7 or 21 night duration. Thus, to see the limitation, a user must enter the requested nights in the field "Nights".
Once the duration is used, then Flight seat regulation is able to display the actual status of the limited flight pairs.
For the 7 night duration, there had not been any limitation set. Thus all of the remaining allotments are still valid for sale in this departure and duration
There also exists the possibility to close duration, by setting the limitation amount to 0. If seats have already been sold, then the limitation should equal the amount of occupied.
Once a limitation has been reached, the booking, or rebooking into, flight pair that no longer possesses available seats, based upon limitation is no longer possible.
The error message "K521 Service sold out – Check alternatives" is displayed, and the outbound flight is highlighted.
Bookings that already possess allotments from the limited flight pairs are possible to be rebooked after the limitation. However, additional seats cannot be requested as the limitation has been reached.
What is not checked by Flight Seat Regulation?
If there exists more than one flight to and/or from a destination then the booking of non-matching service pairs will not be checked, by the flight seat regulation functionality.
OUTBOUND | CLASS | INBOUND | CLASS | 7 NIGHT LIMITATION | CHECKED |
PRG RHO/QSA | Y | RHO PRG/QSA | Y | 0 | Y |
PRG RHO/QSB | Y | RHO PRG/QSB | Y | 0 | Y |
PRG RHO/QSA | Y | RHO PRG/QSB | Y | N/A to limit | N |
PRG RHO/QSB | Y | RHO PRG/QSA | Y | N/A to limit | N |