Time-limit for Flight Segments
Time-limit for flight segments allows to set a moment of time after route count inquiry and action that is to be done, when “false” bookings (with no ticket for a segment) is processed:
- cancel PNR segment
- send a telegram with such PNR to a queue so that operator may notice “false” booking and decide what to do with it
- both: cancel PNR and send message to the queue.
You may also configure search range for flights and booking offices for “false” bookings search, and time-limit for any booking period starting from sale start date and till a moment of flight departure.
Actions are defined by time-limit rules in the Intergity → Time-limit for segments section.
Main window is shown in the figure below.
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
| Parameter | Obligatory | Description | Format |
|---|---|---|---|
| Default time zone | Yes | Time zone for a moment at which time limit is applied to the booking | Select from the drop-down list. You may also check the Agent time zone box to use time zone of an agency, where a specific “false” booking was made |
| Delay processing time limit | Yes | How much time there is from the moment of segment booking before the booking is analyzed and processed. This is the time for an agent to finish all operations with the booking. As this time tuns out, the booking will be checked and processed | Amount of minutes from 2 to 720 |
| ADTK текст | Yes | Text of SSR ADTK, which is added to PNR on processing the booking as “false” | Free text with the following masks:
|
| RFISC for disabling time limit | No | If there is purchased service with this RFISC in PNR, then the time limit for flight segments will be disabled | Select RFISC from the drop-down list |
| Time limit processing | Yes | An action, that is to be done if the booking is processed as “false” booking | Select an action:
|
Rule Parameters
| Parameter | Obligatory | Description | Format |
|---|---|---|---|
| Description | No | Free text describing the rule | Up to 256 symbols |
| PNR type | Yes | PNR types, which are to be analyzed | Select a type: any, individual, group |
 |
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.:
 |
Segment Parameters
| 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.:
|
| 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
|
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
|
Time Limit Volume. Booking Intervals
Time limit volume is set for each booking interval separately. Intervals may start with booking start date (then leave the From field empty) and end with the moment of flight departure.
For each interval a lime limit is set as a number of days, hours and minutes before flight departure or after a moment of segment booking. The From option means that in the specified amount of time before departure “false” bookings are to be processed with an action specified in the Time limit processing field.
The After option means that after the specified amount of time after a moment of segment booking, “false” bookings are to be processed with an action specified in the Time limit processing field.
In the example shown on the picture:
- bookings made from the moment of sale start and until 8 days before departure are to be cancelled 2 days after segment booking, if no ticket was issued.
- bookings made from 7 to 5 days before departure are to be cancelled 1 day after segment booking, if no ticket was issued.
- bookings made from 24 to 12 hours before departure, are to be cancelled in an hour and a half before flight departure if no ticket was issued.
Intervals should be specified in a chronological order, from earlier to later.
Leave the From field empty to set the From moment to a start of sale moment.
|
ATTENTION! If a time interval does not fit any of the specified periods (e.g., 20 to 10 days before perature and then 5 to 3 days before perature in the next line is stated), then time limit for the missing interval (in this example: 9 to 6 days before departure) is counted automatically based on the values specified for the adjacent periods using straight-line interpolation, so that the time limit value is changing gradually. To avoid that, specify time limit value for each moment of time for all days before flight departure. |
If the specified time limit is more than 48 hours after booking, then 24 hours before it expands, if no ticket has been issued still, then an SSR ADTK %S TO %A BY %T OTHERWISE WILL BE XLD is sent to the reservation system once again 1).
Example
A time limit for flight segment rule is created with the following settings:
PNR which has been processed is presented in the figure below. An SSR ADTK and time limit for segment has been added to the PNR.
Booking period, which includes the time of segment booking and time limit value, is presented in the figure below.
Other Integrity sections:
- Time Limit for Special Services
- Duplicate PNR
- Black and White lists
- Fictitious names
- Duplicate segments
- NO-SHOW postprocessing
- Churning
- Implicit Groups
- Time-limit for Group Names
- Mandatory PNR Elements
1) Where %S is for reservation system code, %А is for airline using Revenue.Integrity system code, and %T is for time zone and time of time limit.