Illustration 26: Realization strips: aircraft in the air
First screen shot presents the airborne aircraft. Blue or red border indicates whether the aircraft departed on time or not. Also the estimated time of arrival is calculated and displayed at the right edge of the strips. There is no right strip border and blue background indicates that aircraft is in the air.
Illustration 27: Realization strips: aircraft on the ground
When the aircraft has BLON value entered, it is assumed that it is on the ground. When the aircraft is on the ground, strips become closed and its background color becomes light orange.
The closing border of the strip indicates whether there was a delay or not.
If there is enough space, flight number is displayed inside the strips. Also the codes of the airports are displayed on the both sides of strips.
If the aircraft landed at the airport of destination, there will be no airport information in the second row of strips (realization). If the aircraft landed on other airport then it was planned (for example on an alternate),
red
airport name will be displayed in the second row.
3.4 Notifications
Before you read on please watch our video tutorial regarding notification system .
Notification system in Leon allows your crew, sales department and other interested parties to be notified about some important changes in the system. There is no need to constantly monitor the application in order to check if something has changed. It is far more comfortable to setup the notification system instead.
Go to the menu
Flights > Notifications
in order to see notification list defined in the application
© Leon Software Leon User's Manual Page 31
Illustration 28: Notifications list
Every notification has some kind of name (for you to recognize it) and recipients. Adding new notification or editing existing (by clicking on appropriate row in notifications list view) will bring the pop up window.
Illustration 29: Notification settings
© Leon Software Leon User's Manual Page 32
Below you can find all fields described:
Basic Meaning
Name
Operator
Name of the notification. This name is never used anywhere except on the notifications list. You can use some short description of that notification, e.g. 'Notify crews about schedule change'
Typically, this is not editable and is set to your operator name. This option is available if two or more companies work together and use Leon to share information between themselves (for example you could have OPS department outsourced). This field determines for which operator you want to define notification rules
Send also if changed by ....
This option is usable with more than one company using
Leon as described above. If notification is added by operator A for actions in operator's B data, checking this option will send notification also if operator A changed something inside operator's B data.
Notify only about new operations
Trigger notification only for new operations and not for further changes
Send options
Send maintenance/offices
Trigger
Send notification email when changes are made in option status of a flight
Send notification about new maintenance/office duty and its modifications
Insert the number of hours in advance of which the notification is to be sent.
Use Local Time
Recipients
Cockpit
Cabin
Engineer
Mails
Reply to:
Notify about
Schedule
Crew
Order Issued
If trigger is set to 48 and somebody changes something in a flight which is scheduled more than two days in the future, this notification will not be sent. This is useful when it is close to departure time and there is a chance that someone may not check the latest information in Leon.
The notifications will be sent with local time instead of UTC
Meaning
Send to cockpit crew planned for the particular leg for which the data has been changed
Send to cabin crew planned for the particular leg which data has been changed
Send to FE assigned to a particular flight for which the data has been changed
Specify other emails separated by comma to add some other recipients
E-mail address from which notification will be sent and to which a reply can be forwarded.
Meaning
Notify if scheduled times (STD or STA) has changed
Crew has changed
Flight Order has been created for operation
© Leon Software Leon User's Manual Page 33
Operation status
FO suppl. info
FPL
OFPL
Operation status has changed (for example from 'Option' to
'Flight' meaning that flight has been confirmed)
Flight Order supplementary info - if that changes, notification will be sent
Flight Plan has been changed
Operational Flight Plan has been changed
Block fuel, Hotel,
Handling, Overflight permission, PPR,
ADEP slot, ADES slot,
PAX list, PAX No,
Catering, PAX transport, Notes,
CTOT, ETD etc.
Appropriate values have been changed in legs info (when you click the color dot you will be redirected to legs info page)
Notifications is format friendly for mobile phones so it is easy to read them. Only important messages, changes made and the information who made the change appears.
Changes are placed between [ and ] brackets inside notification email.
Please find some notification example below.
Email title: N12345 CHANGES in FLIGHT TAT-WAW-ZRH-TAT-KTW-WAW on 21-01-2010
FLTNO1 11:00 TAT-WAW 12:00, 9 PAX
FLTNO2 13:00 WAW-ZRH [14:45], 0 PAX
FLTNO3 [Cancelled]
FLTNO4 [Cancelled]
FLTNO5 [Cancelled]
Crew: AAA BBB [CCC]
---FLTNO2---
Notes: ZRH/LSZH - Avcard, supplier Jet Aviation, 3.39 usd/usg
TAT/LZTT - Avcard, supplier Airport Authority, 3.4 usd/usg
Changed by: Sierra Papa
In example above, operation was previously planned to be on the route TAT-WAW-ZRH-TAT-
KTW-WAW. The hour of arrival of the second leg to ZRH changed, 3 last legs canceled and the flight attendant changed to CCC. All those changes were made by user named 'Sierra Papa'.
Crew codes appear in the same order as they are in operation edit. The most typical order is CPT, FO, FA1, FA2, ...., FA n
Notice that not only changes are being sent but also all the other data about the whole operation. This is so you don't need to combine emails to understand what a particular
© Leon Software Leon User's Manual Page 34
