This is an old revision of the document!
In this section you can define admin settings for your flights data displaying in 'Flight Edition' screen, flight documents, set default flight or trip type, etc…
You can also define email notifications regarding schedule or crew changes.
Important settings can also be found here regarding OPS and Sales checklist items as well as Journey Log.
Custom delay codes (from 00 to 05) can be defined here and used when inserting Flight Watch or Journey Log.
All the options/tools in this section relate directly to flight editing. Some of the options are as follow:
The main task of the 'Notifications' panel is to inform via emails about any changes done in flights added to Leon as well as about creating and deleting flights. It is Leon users (OPS, Admins) who decide what sort of notifications are being sent out and to whom by defining settings.
It is possible to define any number of notifications and from the point of user's view - each one of them will work independently.
In order to decrease the number of emails outgoing from Leon (which is beneficial for recipients), notifications are not being sent out immediately after the first change in the flight but after 10 minutes from the last change. So if there was another change done to the same flight within 10 minutes - time is calculated from the beginning.
For example: you changed STD at 12:00 UTC, then STA at 12:08, ADEP at 12:15, ADES at 12:22 (ADES change was the last one - the notification email about these changes would be sent out at approximately 12:32 (10 minutes after the last change).
As you can see in the screenshot there is a number of sections that influence the type of notification and the time when it was sent but also the content of such notification. Main areas of influence are explained below.
You can set a notification so that flights added to Leon are grouped. If a flight from the selected group is changed, the notification will include the schedule of all flights from this particular group (including unchanged flights). If more than one flight is changed, one notification will be sent containing information about the changed flights along with other flights from the same group.
There are 4 options in grouping:
Example: a pilot is scheduled for 2-legs flight STN-AMS-STN and on the same day he is scheduled for 1-leg flight STN-MAN. If there are changes made to the first flight, they will get a notification including details of the later flight as well.
Example: a 4-leg trip is added to Leon and changes are made on the 4th leg - the notification email will contain details of the changed leg (in bold) as well as the details of all other legs of the trip.
Example: the 1st trip on aircraft A-BCDE is: 04-02, 10:00 WRO AMS 11:00. The 2nd trip is: 04-02, 12:30 AMS VKO 16:30
Both are separated trips for different clients. If changes are made to the 1st trip, in the notification email there will be also details of the 2nd trip (as it's on the same aircraft, on the same day).
You can decide how you wish to receive notifications about flight changes.
When you edit your notifications in this section you can find 3 checkboxes under 'Display changes as:
You can combine the above 3 options, i.e. mark all 3 checkboxes, or 2 of them, or just 1 (see examples below).
Also when date of flight is changed, the notification that is sent in Full HTML email format will have a new date highlighted red in the flight information table.
You can define what details of either the flight or the trip you want included in the notification email. You can add various checkboxes (which represent Leon 3.0 checklist) in sections such as:
tab Flight: Ops, Handling, Crew, Pax
tab Trip: Flight, Contract, Notes (notes added in 'PLanned Flights', tab 'Notes')
Leon will send a notification email if a positioning duty is added to Leon and the checkbox Positioning is ticked in 'Notification' screen (see below):
30-JAN NEW positioning (EGCC-EGSS)
Schedule
Specify how many minutes before scheduled departure time you want to receive reminder email + notifications about further schedule changes (ADEP, ADES, STD, STA, PAX, Flight status - see screenshot below). For example, if you want to set trigger time for one day (24h), please enter 1440 minutes.
All flight details will be sent together with the schedule but notification will be triggered only for schedule changes, pax number and flight status.
Details
Specify how many minutes before scheduled departure time you want to receive reminder email + notifications about further changes in flight details (all except flight schedule). The typical value here is something short - e.g. 45 minutes (see example below).
IMPORTANT INFORMATION
In the new version you can include and/or exclude recipients of the partucilar notification.
Click on the include icon and select a person from the list of Leon users at your company. Choose the icon exclude if someone should not get notification emails.
Once it's saved, you can see in the field 'People' names included i.e.: or excluded:
Click to remove names from this section.
Every time you create a new notification, you can set it up in a different way. You can include options, positionings or office duties. You can include scheduled maintenance and aircraft movements. You can select crew: cabin, cockpit or maintenance. You can add appropriate checkboxes related to 'Legs Info' checklist.
You can also select a 'Client' and save a particular notification only for this particular client. You still need to add his email address in the field 'E-mail addresses', if you want him to receive notification emails.
Each notification can be deactivated (simply click and save). You will be able to activate it back in the future, if necessary (click and save). Of course, you can completely any notification as well.
Below you can find various examples of notifications, which can be sent out by Leon.
This tool allows you to configure default handling requests and GAR patterns which will be used in preparing and sending emails to handling agents or GAR offices (see Handling Requests and GAR).
It also allows you to integrate with MyHandling facility via MyHandling GUIDE field. For more information on MyHandling see Handling Requests.
Below Test settings… you can see a table called 'Handling Request Status changes'. The checklist consists of a list of items as shown in the screenshot, which when ticked will affect the status and change it to and vice-versa (unticked - changes made to a flight will not change the status). “Time change treshold” allows to set a time buffer. If the schedule is changed by fewer minutes than indicated in this option, the HR status will not change.
All the elements of the checklist are ticked by default. Schedule checkbox is ticked and cannot be modified.
This checklist applies to New Handling Request status changes only.
Changes to the fligt that affect the status of Handling Request, apart from changing status to , will also change HR link to Airport Name Update. When hovering the mouse over this link, it will display a list of changes in the tooltip.
To enable the module tick box 'HR available (items below are applicable only when this field is enabled)' and untick 'Test settings (if marked, HR will be sent to user's email address instead of handling agent)' which is turned on by default. Next step is filling in email details, such as:
A field 'Email subject' contains what is later shown in the subject of 'Handling Request' email.
I.e. Handling Request\\[DATE]\\[ACFT_REG]/[ACFT_DEF_FLIGHT_NUMBER]\\[ADES_ICAO]\\[VERSION]
When the handling email is sent out, the 'Email subject' text turns to:
Handling Request\\26-06-2013\\M-LEON\\EGSS\\(ver 1)
Default email contents
Default email contents are particulary important because they include the default email contents for new, amended, and canceled handling requests as well as default GAR content, requested items, HOTAC details, Billing info and Footer. What all these fields contain is only email text messages - NOT handling requests/GARs themselfs - as documents are attached separately as PDFs files. You can add in these particular fields your default phone/fax number, email address, etc… See below examples of default email contents.
Default HR email content |
---|
Dear OPS,
We kindly request handling as per attached request.
Please acknowledge the receipt of this email.
Regards,
Default GAR email content |
---|
Dear Ops,
See attached GAR for the flight we are operating.
Regards,
Default amended request email content |
---|
Dear Ops,
Please see attached amended handling request for the flight we are operating.
All updates are marked in red on the attached document.
Please acknowledge and advise all confirmed to ops@address.com
Regards,
Default cancelation request email content |
---|
Dear Ops,
Please find attached handling cancellation.
Please confirm by return of email to ops@address.com
Regards,
Default requested items |
---|
Standard Handling,
Airport Slots if required,
Customs'
Refueling as advised by OPS
Default HOTAC details |
---|
4* Hotel where possible, with suitable facilities,
Budget 150EUR per room minimum,
Transport to/from HOTAC
Billing Info |
---|
Please forward all invoices to: address, VAT No., Company Reg.
Footer |
---|
Please provide us with an estimated cost and email your confirmation to @email or fax @fax .
Alternatively contact us on @phone .
Regards, @sender
There are also 4 available fields where you can add details which will be included in PDF of the handling request:
—-
This section offers you useful options that can be used in contacting with clients or brokers you deal with.
To send 'Flight Brief' to the client, please go to Planned Flights and after editing the flight, go to tab Docs, where you will find a 'Flight Brief' window. This is where email details with email content, previously added in 'Quotations' section, can be found.
This function allows you to distinguish one trip from any other trips on the flights list by assigning a different colour to it. It is very useful when you have a type of operation that occurs occasionally but on a different aircraft. Normally this would display different colour on the flights list. With Flight codes facility you can assign one colour pattern for one type of operation.
The process is very simple. In this page you create a code name and assign colour to it. Once this is saved, you can use this code when creating or editing flight, in the codespace. Once this code is assigned to a trip - this trip will inherit the colour coding from this section. Example of the process is visualised in the screenshot below:
Flight codes (colours) have higher priority on the flights list than Fleet colour codes. You can create as many patterns as you need.