Time-limit for Group Names

The function is designed to track the situation when fewer reservations are actually made in PNR than in a group booking. The basis of the function is the control of group bookings, in which fewer passenger names are entered than seats reserved.

If such bookings are found, there is a set moment before departure, by which all names (special and/or real) must be indicated, otherwise if the number of names is still less than the number of reserved seats, the action specified in the settings of this function is applied to the booking.

How it works:

the function is launched for each group booking, in which the number of passenger names is less than the number of reserved seats;
upon such booking is found, a search is made for the rule suitable for this booking according to the criteria of segment parameters and reservation parameters;
when a suitable rule is found, depending on the value of the Time before departure parameter (this is time-limit) the following actions are performed:

if there are more than 12 hours remaining before the time limit expires, PLS PROVIDE ALL PAX NAMES BY [DATETIME] [TIMEZONE] remark is added to the PNR.
if there are 12 hours or less remaining before the time limit expires, PLS PROVIDE ALL PAX NAMES BY [DATETIME] [TIMEZONE] IMMEDIATELY remark is added to PNR and a message is sent to the queue with the text Timelimit soon will be exceeded.
if the time limit has already expired, the remark XLD DUE TO GROUP NAMES TIMELIMIT EXCEEDED is added to the PNR and the action specified in the rule settings is applied to PNR: queue/cancel/cancel and a message with the text Timelimit has been exceeded is sent to the queue.

In the left part of the window a list of created time-limit rules is shown.

Rules are processed in the descending order from the beginning of the list and downwards. If the booking matches rules parameters, then time limit is set according to the first found matching rule settings. Other rules are not analyzed for this booking after one matching rule was found. That is why more specific rules are recommended to be placed in the beginning of the list to avoid situation, when time limit is set by a rule with less specific criteria as it was found first and matched.

New rules are by default placed in the end of the list and may be moved to any other place of the list by drag and drop at any moment 3 when configuring the rule or after saving.

Attention! After you finish configuring, editing, or moving the rule in the list, click Save button. Otherwise all changes will be lost after you close the tab.

Here you may also rename the rule. To do that, double-click on the Input reule name… field.

Rule name is in the upper line, and a short rule description in in the bottom line.

Settings parameters are described in the tables below.

Time Limit Processing Settings

The parameter Time limit processing defines an action made to PNR which is applies if by the moment of time indicated in the Time before departure parameter the number of passenger names is less than the number of reserved seats (some of the passenger names are missing):

Cancel;
Add to queue;
Cancel and add to queue.

Rule Parameters

The Description may contain free text describing the rule. Field length is up to 256 symbols.

Time Limit Configuration

Time limit un this function defines a moment of time by which the number of special and/or real names in the group booking should match with the number of reserved seats. Depending on how much time is left before this moment arrives, different actions are made to PNRs:

if there are more than 12 hours remaining before the time limit expires, PLS PROVIDE ALL PAX NAMES BY [DATETIME] [TIMEZONE] remark is added to the PNR.
if there are 12 hours or less remaining before the time limit expires, PLS PROVIDE ALL PAX NAMES BY [DATETIME] [TIMEZONE] IMMEDIATELY remark is added to PNR and a message is sent to the queue with the text Timelimit soon will be exceeded.
if the time limit has already expired, the remark XLD DUE TO GROUP NAMES TIMELIMIT EXCEEDED is added to the PNR and the action specified in the rule settings is applied to PNR: queue/cancel/cancel and a message with the text Timelimit has been exceeded is sent to the queue.

Time limit is configured in the Time before departure field in the DDD HH:MM format. For example: 002 15:20 value means 2 days 15 hours 20 minutes before departure.

Segment Parameters

use the flags (

) and (

) to set type of processing the values of the fields below! Minus means exception for bookings with the specified criteria. Bookings with this criteria will not be analyzed. Plus is for including the bookings with specified criteria into the list for analysis. E.g.:

According to the setting above, all flights arriving to France will be analyzed, except for the flights arriving to the CDG airport. In the short rule description in the list of rules, included parameters are marked with green color, excluded — with red.

Parameter	Obligatory	Description	Format
Flights	No	Flights that are to be included () into the rule or excluded () from the rule	A list of flights: separated by a comma, or as a range of flights (hyphenated). To include the odd/even flight numbers in the range only, use `«/2»` flag, e.g.: `300-400/2` — all odd flight numbers from 300 to 400 `301-401/2` all even flight numbers from 301 to 401. The range with `«/2»` flag should start and end with odd or even number. Do not start the range with even number and end with odd, or vice versa
Departure countries	No	Departure countries, that are to be included () into the rule or excluded () from the rule	Latin country codes separated by a comma, e.g.: `FR, BY`
Departure points	No	Departure points, that are to be included () into the rule or excluded () from the rule, located in the countries specified in the Departure countries field	Latin port codes separated by a comma, e.g.: `DME, LED`
Arrival countries	No	Arrival countries, that are to be included () into the rule or excluded () from the rule	Latin country codes separated by a comma, e.g.: `FR, BY`
Arrival points	No	Arrival points, that are to be included () into the rule or excluded () from the rule, located in the countries specified in the Arrival countries field	Latin port codes separated by a comma, e.g.: `DME, LED`
Cabins	No	Cabins, that are to be included () into the rule or excluded () from the rule	A list of latin cabin names without separators, e.g., `CYZ`
RBDs	No	RBDs, that are to be included () into the rule or excluded () from the rule	A list of latin cabin names without separators, e.g., `KMN`
Mkt partners	No	List of airline codes – marketing partners	Airline codes separated by a comma, e.g.: `7R, YU, HG`

Booking Agency Parameters

Parameter	Obligatory	Description	Format
Reservation systems	No	Reservation systems, in which the booking was made	A list of latin system names separated by a comma, e.g. `1H, 1A, 1B`
Countries	No	A list of countries, where the booking agency is located	Latin country codes separated by a comma, e.g.: `FR, BY`
Location	No	A list of cities or port codes, where the booking agency is located	A list of latin port or city codes separated by a comma, e.g.: `DME, LED`
Agencies	No	A list of agencies, where booking was made	A list of agency codes separated by a comma, e.g.: `AGENCY1, AGENCY2`
Points of sale	No	A list of POS, where booking was made	A list of POS codes separated by a comma, e.g.: `POS1, POS2`
Terminals	No	A list of terminals, where booking was made	A list of terminals codes separated by a comma, e.g.: `TRM1, TRM2`

Other Integrity sections: