This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:settings-flight [2016/12/28 11:19] rafal removed |
leon:settings-flight [2016/12/28 11:48] (current) rafal |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Flight | + | ====== Flight ====== |
- | + | ||
- | In this section you can **define admin settings** for your flights data displaying in ' | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ====== Flight editing ====== | + | |
- | + | ||
- | All the options/ | + | |
- | + | ||
- | * **Default flight type** - each added flight, when edited, will have a chosen type: S-schedule, N-Non-schedule, | + | |
- | * **Display FDP preview on "Trip Edit" form** - when editing a flight where FDP has got exceeded, Leon will display a message< | + | |
- | <span style=" | + | |
- | </ | + | |
- | <span style=" | + | |
- | </ | + | |
- | <span style=" | + | |
- | </ | + | |
- | * **Show ' | + | |
- | <span style=" | + | |
- | </ | + | |
- | * **Allow crew suggestion box in Edit Flight** - a very useful option when planning crew for a flight (especially when there is lots of crew-members available). | + | |
- | [{{ : | + | |
- | * **Rest facility** - depending on your OM7 (Flight Time Limitations) you can choose between 3 options: " | + | |
- | * **Default Trip Note** - If set, new flight is initialised with this trip note text. This text will be displayed in ' | + | |
- | * **Allow not completed JL to be entered** - this option allows you to add not completed ' | + | |
- | * **Show in Journey Log** - there is a variety of check-boxes to choose from when it comes to adjusting your ' | + | |
- | * **OPS checklist** - by ticking particular check-boxes you can define what sections will be available in your 'Legs Info' screen. Adding further elements will NOT apply to the past flights but to new flights only. We can extend this list if required by the operator. | + | |
- | * **Sales checklist** - a list of check-boxes related to ' | + | |
- | * **Custom Delay Codes** - here you can define your own Delay Codes which then will be used in Journey Log and Flight Watch. | + | |
- | + | ||
- | + | ||
- | ---- | + | |
- | + | ||
- | ====== Notifications ====== | + | |
- | + | ||
- | + | ||
- | The main task of the ' | + | |
- | + | ||
- | 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), | + | |
- | + | ||
- | 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). | + | |
- | + | ||
- | ===== Notification Properties ===== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ==== Grouping ==== | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | * 1. **None** - flights are not grouped, which means that each flight is being sent individually. | + | |
- | * 2. **Crew** - if the recipient of the notification is a crew member of the changed flight, they will receive information about all his flights in a given day (all recipients who are not planned on the flight will not receive the notification). | + | |
- | + | ||
- | __Example__: | + | |
- | + | ||
- | * 3. **Trip** - the entire trip of the modified flight is sent (even if particular legs are on different days). | + | |
- | + | ||
- | __Example__: | + | |
- | + | ||
- | * 4. **Aircraft** - all flights for the same aircraft from the same day (including the modified flight) are grouped into one notification email. | + | |
- | + | ||
- | __Example__: | + | |
- | + | ||
- | * 5. **Day** - all flights for the same day for ALL aircraft, including the modified flight, are grouped into one notification message. | + | |
- | + | ||
- | 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). | + | |
- | + | ||
- | ==== Format ==== | + | |
- | + | ||
- | * 1. **Simplified HTML** - new flight schedule details, crew codes, status, created by - are all in bold; all changes in flights are in bold; the size of email ~5 kB. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * 2. **Full HTML** - deleted legs appear as < | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== Displaying changes ==== | + | |
- | + | ||
- | 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 ' | + | |
- | + | ||
- | * **Bold** - all changes are in bold. | + | |
- | * **Red** - all changes in red font. | + | |
- | * **In square brackets** - all changes in normal font, in square brackets. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== Flight/Trip ==== | + | |
- | + | ||
- | 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 ' | + | |
- | + | ||
- | ==== Positionings ==== | + | |
- | + | ||
- | Leon will send a notification email if a positioning duty is added to Leon and the checkbox **Positioning** is ticked in ' | + | |
- | + | ||
- | **30-JAN NEW positioning (EGCC-EGSS)** | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== Trigger for Schedule and Details ==== | + | |
- | + | ||
- | **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). | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | < | + | |
- | <span style=" | + | |
- | </ | + | |
- | + | ||
- | ==== Include/ | + | |
- | + | ||
- | In the new version you can **include** and/or **exclude** recipients of the partucilar notification. | + | |
- | + | ||
- | Click on the < | + | |
- | <span style=" | + | |
- | </ | + | |
- | <span style=" | + | |
- | </ | + | |
- | + | ||
- | Once it's saved, you can see in the field ' | + | |
- | + | ||
- | Click {{: | + | |
- | + | ||
- | ===== Managing notifications ===== | + | |
- | + | ||
- | Every time you create a new notification, | + | |
- | + | ||
- | You can also select a ' | + | |
- | + | ||
- | Each notification can be deactivated (simply click {{: | + | |
- | + | ||
- | Below you can find various **examples** of notifications, | + | |
- | + | ||
- | * **New flight - schedule only** - no checklist details included. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | * **Checklist details** - both ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Scheduled maintenance** - maintenance added in ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Movements** - sent out if ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Option** - flight status set as ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Office duty** - either the flight status in 'Edit Flight' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Reminder** - enable the trigger for schedule or/and details, define time and tick 'Send reminders' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **Local time** - tick the checkbox 'Use local time' to get notification emails in local time. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | * **" | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | ====== Handling requests ====== | + | |
- | + | ||
- | 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 [[leon: | + | |
- | + | ||
- | It also allows you to integrate with **MyHandling** facility via **MyHandling GUIDE** field. For more information on **MyHandling** see [[leon: | + | |
- | + | ||
- | ===== Handling Request Status changes ===== | + | |
- | + | ||
- | + | ||
- | [{{ : | + | |
- | Below **Test settings...** you can see a table called **' | + | |
- | + | ||
- | 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 {{: | + | |
- | [{{: | + | |
- | + | ||
- | -------- | + | |
- | + | ||
- | < | + | |
- | + | ||
- | ===== Default definitions ===== | + | |
- | + | ||
- | + | ||
- | To enable the module tick box 'HR available (items below are applicable only when this field is enabled)' | + | |
- | * **Email " | + | |
- | * **Handling Request Email " | + | |
- | * **GAR Email " | + | |
- | * **Email " | + | |
- | * **Send copy of HR email to** - it can be the same as email " | + | |
- | + | ||
- | A field 'Email subject' | + | |
- | + | ||
- | I.e. **Handling Request\\[DATE]\\[ACFT_REG]/ | + | |
- | + | ||
- | * [DATE] - trip date | + | |
- | * [ACFT_REG] - aircraft registration | + | |
- | * [ACFT_DEF_FLIGHT_NUMBER] - default flight number for aircraft (if you don't have set up default flight number for aircraft, you can change it to [FLIGHT_NUMBER] | + | |
- | * [ADES_ICAO] - ICAO code of airfield (you can change it to [ADES_IATA] | + | |
- | * [VERSION] - handling request version | + | |
- | + | ||
- | When the handling email is sent out, the 'Email subject' | + | |
- | + | ||
- | **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/ | + | |
- | + | ||
- | ^ 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: | + | |
- | + | ||
- | * your email address | + | |
- | * SITA | + | |
- | * phone number | + | |
- | * FAX number | + | |
- | ---- | + | |
- | + | ||
- | ====== Quotations ====== | + | |
- | + | ||
- | This section offers you useful options that can be used in contacting with clients or brokers you deal with. | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | * **' | + | |
- | * **Sending quotations to Avinode options** - add this option to send quotations from Leon to Avinode (visit section [[leon: | + | |
- | * **Send messages about aircraft movements to clients** - tick box ' | + | |
- | * **Flight Brief** - fill in email fields along with the content, which will be used when sending out ' | + | |
- | * **Charter Agreement** - this document can be added optionally by Leon Software - if you wish to have it, please contact [[support@leonsoftware.com]] | + | |
- | + | ||
- | + | ||
- | To send ' | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | ====== Flight codes ====== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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 [[leon: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | **Flight codes (colours) have higher priority on the flights list than [[leon: | + | |
+ | Section Flight is divided into 5 sub-sections where you can configure options and settings that are global for all users. It allows to set up the default elements of the Checklist, Handling Requests and Quotations email templates as well as Flight Notifications. | ||
+ | {{: |