Schedule Parameters
General Flight Schedule Parameters
A flight number is a flight ID, a unique name.
A flight number consists of the following components:
- Carrier code
- Numerical number
- Operational suffix.
A carrier code is presented in a flight number:
- Two-symbolic code is an IATA code or an internal code.
- Three-symbolic code is an ICAO code.
Numerical number contains not more than 4 symbols. An operational suffix consists of one letter.
A carrier code and a numerical number are obligatory while assigning a number to a flight.
 |
An operational suffix is recommended to assign to additional flights or regular flights delayed with date change. |
Suffix describes the original departure day of a delayed flight.
List of suffixes of the days of the week is presented below:
| Suffix | Day of the week |
|---|---|
| P | Monday |
| М | Tuesday |
| S | Wednesday |
| R | Thursday |
| L | Friday |
| N | Saturday |
| T | Sunday |
|
Suffixes assigned to delayed flights are not available for editing in manual mode. |
 |
Not more than one departure or arrival of flights with the identical numbers should be planned in any point of a route within one day. |
A route is a range of geographical objects (airports) listed in order of departure and arrival of an aircraft with the same flight number.
A route is divided into the following components in the System:
- Leg is a part of a route without any arrival waypoints. A flight over a leg of a route is performed by one aircraft.
- Segment is a part of a route between two points consisting of one or more legs. A flight over a segment of a route may be performed by several aircrafts if an aircraft replacement is carried out in a waypoint.
One-leg route is a route containing only one departure airport and one arrival airport.
Multiple-leg route is a route containing one or several waypoints between origin and final points.
|
Flights with different numbers may be performed on the same route and at the same period. |
Calendar period of a flight is defined by the Flight period parameter.
The parameter consists of following elements:
- Starting date of flight period
- Ending date of flight period
- Flight frequency (days of week)
- Weekly cycle.
A regular flight with a two-week cycle (that is, every other week) is specified by the Weekly cycle element. The element is not applied to a period consisting of one date.
A flight may use several identical or different routes. Every route may use several operation periods. Periods should not intersect within one flight route.
Regular period of a flight is called basic period.
 |
Combination of basic periods forms basic flight schedule. |
It is possible to specify flight parameters for a particular date without any change in basic schedule. Ad-hoc period is used for this purpose. Ad-hoc period is a special flight period consisting of one date.
Ad-hoc period parameters are priority parameters. If Ad-hoc period and basic period parameters are specified for the same date then a flight is performed according to Ad-hoc period parameters.
Ad-hoc period can be divided into two types:
- Ad-hoc period within basic schedule period is a period whose date is included into flight period according to basic schedule (taking into account frequency). For example, if basic schedule period is specified as 01.01.14-07.01.14/1234567 then Ad-hoc period within this period will be any date between 01.01.14 and 07.01.14 inclusive.
- Independent Ad-hoc period is a period whose date is not included into flight period according to basic schedule (taking into account frequency). For example, if basic schedule period is specified as 01.01.14-07.01.14/135 then Ad-hoc period within this period may be any date between 01.01.14 and 07.01.14 inclusive except for Monday, Wednesday, Friday or any date above this period.
|
If Ad-hoc is created for a flight that has already departed within the past 24 hours, then a re-accommodation plan is created. This plan has to be approved manually. For more information see re-accommodation management chapter. |
Internal comment is a text of random content intended for service purposes.
A comment of this type is not published in external systems.
The parameter is managed by the "SCD internal comments" business rule.
Route Leg Parameters
A terminal is a point of passenger embarkation and disembarkation.
A terminal is defined by a terminal code in the System. Terminal codes present normative reference information and has a link to an airport.
A terminal code can be set by the "Airport arrival terminal" and the "Airport departure terminal" business rules in advance if the same terminal of an airport is used on regular basis.
Two types of time parameters of a flight schedule are presented in the System:
- Departure time is departure time of an aircraft from a departure airport.
- Arrival time is arrival time of an aircraft at an arrival airport.
The HH:MM time format is used. When forming a schedule it is necessary to specify local time of departure and arrival airports.
While automatic loading a schedule, messages containing departure / arrival time in UTC are processed automatically by converting UTC to local time of an airport.
Date shift is a change of departure / arrival date in all points of a route except for origin one.
The following parameter values are presented:
- Zero value indicates flight arrival / departure on the same day.
- Negative value indicates flight arrival / departure in previous days (in accordance with specified value of the parameter).
- Positive value indicates flight arrival / departure in specified number of days.
Aircraft configuration is the schedule parameter defining a number and capacity of aircraft cabins.
Aircraft configuration is set on a route leg. If a flight is multiple-leg it is possible to replace an aircraft in the point of landing. It should be fixed in the schedule. Aircraft configurations are presented in the form of reference book in the System.
Partnership agreement is the schedule parameter containing information about a flight which is a flight of joint operation and is performed on terms of an agreement made between two and more carriers.
Two types of partnership agreements are managed by The System:
- Franchise is an agreement of usage of another carrier's aircraft for performing a flight.
- Codeshare is an agreement of joint usage of aircraft capacity.
In a flight schedule, the information about availability of partnership agreements is added from the “Partnership agreements” section. The information about partnership agreement relates to a route leg of a flight.
It is possible to send additional information about a schedule on a route leg to external systems by DEI (Designator Element Information).
The parameter is managed by the "DEI by Leg" business rule.
Route Segment Parameters
Flight service type is the schedule parameter classifying flights by flight regularity and air transportation (passenger, passenger-and-freight).
Service type codes present normative reference information assigned by IATA.
Service type J (passenger, regular) is assigned to a flight by default. It is possible to change this value.
SSIM service codes are supported in the System. To find a list of codes, please refer to SSIM documentation.
Flight status is the schedule parameter classifying a flight regarding state belonging of route points.
The following IATA flight status coding is presented:
- D (Domestic / Domestic): a flight with departure and arrival airports located in the same state.
- I (International / International): a flight with departure and arrival airports located in different states.
The Flight status parameter is active on a route segment. The same flight may be both domestic and international at the same time if it is multiple-leg, and one part of the route is in the same state that the flight set off from and another part is in a different state.
Value of the Flight status parameter is defined and assigned to flights automatically in accordance with state belonging of route airports. It is possible to change automated defined value manually or by the "Flight status" business rule if carrier business policy requires such decision.
Electronic ticket is the schedule parameter which allows electronic ticketing application to be available. Management of the Electronic ticket parameter is carried out by the "E-Ticket" business rule.
Electronic ticketing is directly connected to availability and resources of registration system in airports.
Electronic ticketing application on long route segments is limited by the System settings.
Meal service is the schedule parameter defining meal type and its providing on route segments.
The Meal service parameter is specified in accordance with a booking class or a cabin. It is possible to specify several meal service codes for a booking class or a cabin on a route segment.
The parameter is managed by the "Meal service note" business rule.
Value of the parameter on a long route segment is automatically calculated as the sum of parameter values used on short route segments.
List of the meal service codes managed by the System is presented in Table
Table - IATA meal service codes.
| Code | Meal service description |
|---|---|
| B | Breakfast |
| C | Alcoholic Beverages |
| D | Dinner |
| F | Food for Purchase |
| G | Food and Beverages for Purchase |
| H | Hot Meal |
| K | Continental Breakfast |
| L | Lunch |
| M | Meal |
| N | No Meal Service |
| O | Cold Meal |
| P | Alcoholic Beverages for Purchase |
| R | Refreshments |
| S | Snack or Brunch |
| V | Refreshments for Purchase |
In-flight service is the schedule parameter defining service types provided to a passenger on board.
In-flight service is specified on a route leg as it corresponds to the information about an aircraft. List of service types presents normative reference information and is stored in the form of reference book in the System.
The parameter is managed by the "In-flight service" business rule.
List of the in-flight service codes managed by the System is presented in Table:
Table - IATA In-flight service codes.
| Service code | Service description |
|---|---|
| 1 | Movie |
| 2 | Telephone |
| 3 | Currently unused |
| 4 | Audio programming |
| 5 | Television |
| 6 | Reservation booking service |
| 7 | Duty Free sales |
| 8 | Smoking |
| 9 | Non-smoking |
| 10 | Short feature video |
| 11 | No Duty Free sales |
| 12 | In-seat power source |
| 13 | Internet access |
| 14 | Currently unused |
| 15 | In-seat video player / Library |
| 16 | Lie-flat seat |
| 17 | Additional services |
| 18 | Wi-Fi |
Booking classes present the schedule parameter defining class codes set. Quoting of aircraft capacity for sale and its further sale are provided by this set.
The Booking classes parameter is managed by the "Booking classes" business rule.
List of the IATA booking class codes managed by the System is presented in Table - IATA booking class codes.
| Booking class | IATA code |
|---|---|
| Special codes | G |
| U | |
| E | |
| O | |
| R | |
| First class | P |
| F | |
| A | |
| Business class | J |
| C | |
| D | |
| I | |
| Z | |
| Economy class | W |
| S | |
| Y | |
| B | |
| H | |
| K | |
| L | |
| M | |
| N | |
| Q | |
| T | |
| V | |
| X |
Traffic restrictions present the schedule parameter which allows to apply restrictions to a sale segment of a flight or participation of a flight in connections.
List of the IATA traffic restriction codes managed by the System is presented in Table- Traffic restriction codes.
| Traffic Restriction Codes | ||
|---|---|---|
| Code | Description | |
| A | No traffic may be enplaned at the board point for carriage to, and subsequent deplaning at the off point. See also Restriction I | |
| B | No restriction applies, but the segment is not to be used as part of any published connection | |
| C | No restriction applies, but the segment is not to be used as part of any published connection where the preceding connecting segment or the following connecting segment is an international flight segment | |
| D | The D restriction equals the Q restriction in that it D, E or G restriction exists into and out of all online connect points for the carriers filing the restriction | |
| E | The E restriction equals the X restriction in that it restricts the segment to online connecting and online stopover traffic only. Additionally, the trip will be invalid if the D, E or G restriction exists into and out of all online connect points for the carriers filing the restriction | |
| F | No restriction applies, but the segment is not to be used as part of any published interline connecting segment | |
| G | The G restriction equals the Y restriction in that it restricts the segment to online connecting traffic only. Additionally, the trip will be invalid if the D, E or G restrictions exist into and out of all online connect points for the carriers filing the restriction | |
| H | No restriction applies, but the segment is not to be displayed or used as part of any published connection | |
| I | Due to non-commercial (technical) landing no traffic may be enplaned at the board point for carriage to, and subsequent deplaning at the off point. All segments where the board point and/or off point is a technical stop should be restricted using Traffic Restriction Code I | |
| K | Carriage is limited to connecting traffic only. The segment must have at least one connection | |
| M |
Carriage is limited to international online stopover traffic only; traffic may be carried if all conditions are satisfied. In respect of carriage of cargo and/or mail, this code is interpreted as Traffic Restriction Code A |
|
| N | Carriage is limited to international connecting traffic only. The segment must have at least one international connection. All connecting segments must be from/to a station in another country | |
| O | Carriage is limited to international online connecting traffic only. The segment must have at least one international online connection. All connecting segments must be from/to a station in another country with the same airline designator | |
| Q | Carriage is limited to international online connecting or international online stopover traffic only; traffic may be carried if either set of conditions is satisfied. In respect of carriage of cargo and/or mail, this code is interpreted as Traffic Restriction Code O | |
| T | Carriage is limited to online stopover traffic only. The segment must have at least one online stopover. All stopover segments must be online. In respect of carriage of cargo and/or mail, this code is interpreted as Traffic Restriction Code A | |
| V | Carriage is limited to connecting or stopover traffic only; traffic may be carried if either condition is satisfied. In respect of the carriage of cargo and/or mail, this code is interpreted as Traffic Restriction Code K | |
| W | Carriage is limited to international connecting or international stopover traffic only; traffic may be carried if either set of conditions is satisfied. In respect of the carriage of a cargo and/or mail, this code is interpreted as Traffic Restriction Code A | |
| X | Carriage is limited to online connecting or online stopover traffic only; traffic may be carried if either set of conditions is satisfied. In respect of carriage of cargo and/or mail, this code is interpreted as Traffic Restriction Code Y | |
| Y | Carriage is limited to online connecting traffic only. The segment must have at least one online connection. All connecting segments must be online | |
| Z | Traffic restrictions do not apply equally to passenger/cargo/mail and/or multiple traffic restrictions apply |
The Traffic restrictions parameter is managed by the "Traffic restrictions (Traffic restriction note)" business rule.
It is possible to send additional information about a schedule on a route segment to external systems by DEI (Designator Element Information).
The parameter is managed by the "DEI by Seg" business rule.
Flight Schedule Management
Flight schedule management is held out manually by configuring schedule parameters for a specific flight. You may also configure parameters of several flights at a time using business-rules. Besides, schedule might be changed automatically on receiving and processing schedule telegrams from external systems.
| Parameter | Configuring |
|---|---|
| Common Parameters | |
| Flight number | Manually |
| Route | Manually |
| Period | Manually |
| Internal comment | Manually and business-rule |
| Leg Parameters | |
| Departure point terminal | Manually and business-rule |
| Arrival point terminal | Manually and business-rule |
| Departure and arrival time | Manually |
| Date change | Manually |
| AC configuration | Manually |
| Commercial agreements | Manually |
| DEI (Designator Element Information) by leg | Manually and business-rule |
| Segment Parameters | |
| Service type | Manually |
| Flight status | Manually and business-rule |
| E-ticket | Manually and business-rule |
| Meals on board | Manually and business-rule |
| In-flight service | Manually and business-rule |
| Booking classes | Manually and business-rule |
| Traffic restrictions | Manually and business-rule |
| DEI (Designator Element Information) by segment | Manually and business-rule |
The following operations are available in the System:
- Creation of basic period of a flight schedule. A flight schedule may contain one or several flight periods. Schedule parameters may be varied for each period.
- Modification of basic period contains:
- Change of starting and ending dates of a period.
- Change of schedule parameters for a specified period.
- Creating an Ad-hoc period.
- Ad-hoc period modification. Schedule parameters modification for a specified date.
- Deleting Ad-hoc period. While deleting “Ad-hoc” indication from a date within basic schedule period, this date is returned to the basic period with essential elements of the basic schedule. While deleting independent Ad-hoc period, “Ad-hoc” indication is removed from a date and the date is returned to the basic schedule without changing parameters. To cancel Ad-hoc period, it is required to use the Cancellation of a period operation.
- Cancellation of a period without further restoration. Deleting a period from a flight schedule.
- Cancellation of a date with its further restoration. A specified date will be marked in Ad-hoc period, and all the schedule parameters, which were specified for this date before cancellation, will be saved. Within the created Ad-hoc period, the flight is not performed.
- Flight delay. Change of flight departure time during the day before the scheduled departure date. Flight scheduled departure date is a date of departure from the first route point.
See also
- Searching Information on Flight Schedule
- Creating a New Flight Period
- Flight Schedule Modification
- Flight Delay
- Flight Schedule Period Cancellation
- Downloading Schedule from External Systems
- Publication of Schedule to External Systems
- Business Rules on Schedule Management
- Other Operations