Load factor control by class (Load Factor)

Objectives and scope of functionality LOAD FACTOR CONTROL


  • The objective of this functionality is to control the automatic closing or opening of the classes according to their percentage load factor.

  • For this, a percentage per class can be configured, which indicates when that class will be closed for sale.

  • The configured percentage acts on the authorized capacity of the flight.

  • It is obtained from the AU column by subtracting the capacity configured in the KAM (If it has configuration thereof).

  • It can also be configured to contemplate the values ā€‹ā€‹of oversold logic (OS) and Block Space (BS).

  • If the company wishes to consider these values, the sum of the column AU + OS - BS - KAM would remain.

  • Based on this result, the percentage of occupancy of the affected classes will be calculated with the value of Load Factor (LF).

The configuration of this indicator is in process:

  • In order to contemplate the percentage of the AU - BS, it has a default configuration that will always take it into account, unless the contrary is defined and configured.

  • In order to contemplate the percentage of AU + OS it has a default configuration that will not take it into account, unless it is defined and configured otherwise.

How does it apply?


A percentage is configured for a class. This percentage indicates that, when the flight reaches that occupancy percentage, the indicated class will be closed for sale.

Application commands for Flight Loading process


Command:

KSLF/<origin><destination>/<classes>/<value or STOP/OFF>

Description:

KSLF

Fixed command

<origin><destination>

Origin and destination of the segment to apply or ALLALL or OriginALL or ALLDestination

<classes>

Single class or several classes that are placed one after the other

<value or STOP/OFF>

  • You can put a value that will be the percentage of occupation of one or all the selected classes.

  • In case of placing several classes with different percentages, a value per class separated by a point will be indicated.

  • For example, if BNX is placed in classes and they all have different values, 50.20.10 will be indicated, corresponding to each class accordingly.

  • The STOP or OFF indicators are to remove a previously configured value.

Examples:

KSLF/AEPMJR/B/50

KSLF/AEPALL/BNX/50.20.10

Configuration process


  1. The flight to be modified is retrieved with the command KA * flight number

  2. The item is displayed with the command KS. Item number

  3. Indicators are applied with the KSLF /ā€¦

  4. Changes are saved with the KSAVE command

Case of use


When configuring a percentage in a class it will be shown in the LFC column as shown in the graph:

In the inventory, the LFC column with the configured value will be seen and the LF% column where it will indicate the percentage of total occupation of the flight.

When the flight reaches 10% of its total occupancy, class X will automatically close, placing the C in the STATUS column and closing the class in availability.

Example:

Load factor control by class per Spaces Control module (CRC)


The objective of this functionality is to control the automatic closing or opening of the classes according to their percentage load factor. For this, a percentage per class can be configured, which indicates when that class will be closed for sale. The configured percentage acts on the authorized capacity of the flight. It is obtained from the AU column by subtracting the capacity configured in the KAM (If it has configuration thereof). It can also be configured to contemplate the values ā€‹ā€‹of oversold logic (OS) and Block Space (BS). If the company wishes to consider these values, the sum of the column AU + OS - BS - KAM would remain. Based on this result, the percentage of occupancy of the affected classes will be calculated with the value of Load Factor (LF).

It can be applied using space control commands (CRC). They have the same considerations as the rest of the CRC commands, if the flight that has indicators configured by this process undergoes a modification through the flight loading process (Schedule change), the data loaded by CRC (VM commands) will be deleted.

The configuration commands are:

VMLF <flight><classes><dated-date h><value or STOP/OFF>

Description:

VMLF

Fixed command

<flight>

Flight number

<classes>

Single class or several classes that are placed one after the other

<dated-date h>

Date to apply. It can also be a parameter of dates, in which case the start date - end date is placed in the DDMMM format.

<value or STOP/OFF>

  • The value is either STOP or OFF to remove the previous values.

  • In this case, multiple classes can be placed but only the same value that is configured for it applies.

  • Multiple values ā€‹ā€‹are not allowed if there are 2 or more classes.

Ā 

Ā 

Ā 

Related pages