The Module Daily Flight Plan

In the module Daily Flight Plan, daily flight schedules are created, administered and edited. Flight events can either be recorded manually or imported from an external flight scheduling system. How the schedule creation is realised depends on individual preferences and options and can thus not be described here.

Generally, daily flight schedules are automatically provided by a seasonal flight scheduling software (e.g. Seasonal Flight Plan).

The module is based on the concept of rotations. Each entry in the table represents one rotation. Such an entry may consist of an arrival and a departure, as well as it may consist of only a single-leg arrival or only a single-leg departure. This nature of rotation is indicated by the attribute Rotation Type, which can be Rotation, Arrival or Departure.

By using the button Create a New Object always a complete rotation consisting of arrival and departure leg is created. In the rare case that only a single-leg is supposed to be created, a complete rotation needs to be created first and then it needs to be split. The superfluous leg can then be deleted. The STA of the newly created rotation is set to the current time. The STD is calculated by adding the applicable MGTR (Minimum Ground Time of Rotation) to the STA. As any other flight time, these times can then be changed manually.

The following special function buttons are available in the module Flights:

Unchain the Selected Rotation: Clicking this button will delete the chaining (link between arrival and departure) of the currently selected flight. If multiple flights are selected, all their chainings will be removed. During unchaining, transit load data is allocated to both legs in case the data source does not clearly relate to one leg.

Chain Both Selected Flights: After you have selected an arriving and a departing flight from the table, you can use this button for chaining both flights to a rotation. During chaining, all available information from all sources is allocated to both legs of the rotation and evaluated according to their priorities.

Interchange Chains: After selecting two flights which are already chained with different flights, clicking this button will swap the corresponding chainings between the selected flights.

Edit Load Data: Using this button will open a new window containing flight load data. The title line displays FLNA/D and the own station of the selected data record. In this window, the user may edit load data in a more convenient way than via the table Rotations -> Route -> Loads -> Manual FlightLoads.

Jump To…: If a flight record is selected, you can use this button to jump to the corresponding flight record in the table Services Flights -> Flight Events.

Export Flight Plan: Using this button allows data export.

Import: Using this button allows data import.

Project environments which do not work with Ready flag: If the billing event for a flight has the state Invoicing, certain buttons and fields in the module Flights are disabled to ensure that flight legs set to Invoicing cannot be edited anymore. Example: If an arrival leg has been set to Invoicing, all data referring to this leg may not be edited any longer. Record data referring to the corresponding departure leg still has to be editable though.

In project environments with Ready flag the setting "ReadyFlagMandatory" set to true in master data General makes sure that buttons and fields for billing events with state Invoicing cannot be edited anymore in case the Ready flag has been set.

The module consists of the following tables: