This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
leon:table [2019/11/22 14:37] rafal [GCR Messages] |
leon:table [2021/01/15 13:06] rafal [Flight documents] |
||
---|---|---|---|
Line 22: | Line 22: | ||
If the flight is added as **Ambulance, | If the flight is added as **Ambulance, | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **FLIGHT ORDER printing/ | ||
+ | |||
+ | Leon informs if the Flight Order document was not printed/ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
- | **Tip**: when you set the filter to show desired type of information, | ||
---- | ---- | ||
Line 43: | Line 54: | ||
An additional option in Editing Trip panel is possibility of entering **Cargo** value. Switch to Cargo or PAX & Cargo in Settings > Flight Editing section in **Trip edit scheme** drop-down. | An additional option in Editing Trip panel is possibility of entering **Cargo** value. Switch to Cargo or PAX & Cargo in Settings > Flight Editing section in **Trip edit scheme** drop-down. | ||
+ | |||
+ | Leon will mark a cargo flight as ' | ||
==== Positionings ==== | ==== Positionings ==== | ||
Line 96: | Line 109: | ||
---- | ---- | ||
+ | ==== Simulators ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | To add a new **Simulator** as the plan, click on {{: | ||
+ | |||
+ | **Initially, | ||
+ | |||
+ | Crew positions which can be added to SIM duty are CPT, FO, LTC, TRI, TRE, FE, FE2. | ||
+ | |||
+ | 'Night T/O', 'Night LDG', ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once the SIM duty is done you can add details: T/O, LDG, Landings, Pilot Flying, Approach and Notes and Leon will show SIM duty in OPS with the grey colour indication and green dot. | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | In order to **edit** the Simulator, you need to click on it and the pop-up 'Edit Simulator' | ||
+ | |||
+ | |||
+ | |||
+ | <box> **Crew currency feature will work properly only when the field 'Pilot Flying' | ||
+ | <box> **It is possible to add SIM session on a virtual aircraft. This could be useful when the crew have to be trained on an aircraft that is not yet a part of the fleet (purchase in progress).** </ | ||
+ | ----- | ||
===== Adding a New Trip ===== | ===== Adding a New Trip ===== | ||
Line 140: | Line 180: | ||
---------- | ---------- | ||
- | |||
- | ---- | ||
==== View Settings ==== | ==== View Settings ==== | ||
Line 207: | Line 245: | ||
{{: | {{: | ||
- | ---- | + | ---------- |
< | < | ||
Line 221: | Line 259: | ||
If you select only one leg of a multiple-legged trip and right-click with the mouse, you will see 2 available buttons on top: TRIP and LEG. Select LEG to print documents for just that marked leg. | If you select only one leg of a multiple-legged trip and right-click with the mouse, you will see 2 available buttons on top: TRIP and LEG. Select LEG to print documents for just that marked leg. | ||
+ | |||
+ | [{{ : | ||
+ | To send the documents to the crew assigned to a flight you simply click on the envelope icon next to the document you wish to send. | ||
+ | |||
+ | A pop-up window will open as per screenshot. | ||
+ | |||
+ | If you created the email template in the [[leon: | ||
+ | |||
+ | You can additionally include **ADEP/ADES Handler** when sending the OPS/ | ||
It is also possible to send the documents to CrewBriefing. More information can be found [[leon: | It is also possible to send the documents to CrewBriefing. More information can be found [[leon: | ||
Line 230: | Line 277: | ||
=== Flight Order === | === Flight Order === | ||
- | [{{ : | ||
- | **Flight Order** is an internal document generated for each trip required by CAA. In Leon, the format of this document can be customised. The Flight Order number looks like a date format, however, its number is a consecutive ' | ||
+ | **Flight Order** is an internal document generated for each trip required by CAA. In Leon, the format of this document can be customised. The Flight Order number looks like a date format, however, its number is a consecutive ' | ||
- | Flight Order pattern available in Leon is filled in by the data entered while adding a new flight: | ||
- | | + | Flight Order patterns are available in **Documents Manager** panel - click {{: |
- | | + | |
- | | + | |
- | | + | |
- | * Schedule details | + | |
- | * After-flight report (data imported from 'Journey Log') | + | |
- | + | ||
- | The other columns/ | + | |
- | + | ||
- | * Crew duties/rest details | + | |
- | * Flight order attachments (tick appropriate boxes) | + | |
- | * Remarks | + | |
- | * COM signature | + | |
---- | ---- | ||
Line 257: | Line 290: | ||
[{{ : | [{{ : | ||
- | This document lists __inbound and outbound flight details__ and crew names. It is being requested by the __immigration authorities__ at some airports of arrival. | + | This document lists __inbound and outbound flight details__ and crew names. It is being requested by the __immigration authorities__ at some airports of arrival. The pattern of ' |
- | + | ||
- | + | ||
- | The pattern of ' | + | |
- | < | + | It is possible to have a General Declaration document including |
---- | ---- | ||
- | === Trip Sheet === | + | === Crew Trip Sheet === |
[{{ : | [{{ : | ||
Line 272: | Line 302: | ||
This document includes basic information about the flight, which is important for the crew and must be acknowledged by the crew before the flight. | This document includes basic information about the flight, which is important for the crew and must be acknowledged by the crew before the flight. | ||
- | 'Trip Sheet' in Leon is divided into two sections: **Trip Sheet** and **Flight Service Notices** - both can be listed either on the same page or on separate pages (this can be set in [[leon: | ||
- | * **Trip Sheet** - information such as: crew names & functions, FDP details, clients, registration marks and call signs of the aircraft, OPS contact data, flight schedule details, handling agents contact details, fuel info and overflight/ | + | * **Crew Trip Sheet** - information such as: crew names & functions, FDP details, clients, registration marks and call signs of the aircraft, OPS contact data, flight schedule details, handling agents contact details, fuel info and overflight/ |
* **Flight Service Notices** - PAX names, passport numbers & expiry dates, nationality details. Information about PAX catering, transport, special requests, crew HOTAC, crew transport and additional info can also be included. | * **Flight Service Notices** - PAX names, passport numbers & expiry dates, nationality details. Information about PAX catering, transport, special requests, crew HOTAC, crew transport and additional info can also be included. | ||
+ | < | ||
---- | ---- | ||
Line 316: | Line 346: | ||
---- | ---- | ||
- | === Pax Information | + | === Pax Trip Sheet === |
[{{ : | [{{ : | ||
Line 403: | Line 433: | ||
- Once all send, you should be anle to view them in CrewBriefing in PPS. The documents sent form Leon are merged into a file generated for Crew in CrewBriefing page. | - Once all send, you should be anle to view them in CrewBriefing in PPS. The documents sent form Leon are merged into a file generated for Crew in CrewBriefing page. | ||
- | It also is possible to upload files for **multiple trips**. To do so simply mark the trips you would like to send the documents for, open the documents menu and click on the relevant 'PPS icon'. If some of the documents fail to upload, the window will display message as per below | + | It also is possible to upload files for **multiple trips**. To do so simply mark the trips you would like to send the documents for, open the documents menu and click on the relevant 'PPS icon'. If some of the documents fail to upload, the window will display |
{{: | {{: | ||
- | When sending documents to PPS you have an option between doing it for **First Flight** or **Per Flight**. | + | When sending documents to PPS you have an option between doing it for **First Flight** or **Per Flight**. |
{{: | {{: | ||
+ | [{{ : | ||
- | **First Flight** will attach all the documents to the first leg of the trip in the CrewBriefing. **Per Flight** option will match the relevant | + | There are **few scenarios possible** of sending |
- | <box>**In order to send documents to PPS Crew Briefing, in PPS the flight needs to be dispatched | + | * **In LEG mode to First Flight** - all the documents |
+ | * **In TRIP mode to First Flight** - all the documents attached | ||
+ | * **In LEG mode and Per Flight** - each document attached | ||
+ | | ||
- | < | + | After the documents are sent, in CrewBriefing, |
+ | |||
+ | . | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
< | < | ||
+ | |||
+ | < | ||
--------- | --------- | ||
+ | |||
+ | ===== SLOT & ASM messages ===== | ||
==== GCR Messages ==== | ==== GCR Messages ==== | ||
Line 531: | Line 575: | ||
Another drop-down box allows to select between **airports**. | Another drop-down box allows to select between **airports**. | ||
+ | |||
+ | **IATA schedules seasons** – there are two seasons: Summer(**S**) and Winter (**W**). The season changes when the clocks change in Europe between daylight savings time and standard time. | ||
+ | |||
+ | • **Summer** starts on the last Sunday in March through to the Saturday of the last weekend in October | ||
+ | |||
+ | • **Winter** starts on the last Sunday in October through to the Saturday of the last weekend in March | ||
< | < | ||
--------- | --------- | ||
+ | ==== ASM messages ==== | ||
+ | |||
+ | [{{ : | ||
+ | It is now possible to send **Ad Hoc Schedules Message (ASM)** from 'Show Schedule' | ||
+ | |||
+ | In order to send the message, you need to go to 'Show Schedule' | ||
+ | |||
+ | ' | ||
+ | |||
+ | * **NEW - Insertion of New Flight Information** - used to send the information about the new flights | ||
+ | * **CNL - Cancellation** - used to send the information about cancelled flights | ||
+ | * **RPL - Replacement of Existing Flight Information** - used to send the information about changes on the flights | ||
+ | |||
+ | < | ||
+ | ---------------- | ||
+ | |||
+ | **DCS** & **PSS** systems. | ||
+ | |||
+ | **SSIM** (Standard Schedules Information Manual) panel in Leon (available in Settings), allows to send **ASM** (Adhoc Scheduled Message) messages to **DCS** (Departure Control System) & **PSS** (Passenger Service System) from a section **OPS**. | ||
+ | |||
+ | The __1st step__ to make it work is adding default email addresses in Settings > SSIM panel. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The __2nd step__ is sending ASM message to DCT & PSS systems from the **checklist** section of the panel OPS. | ||
+ | |||
+ | Each operator has 2 checklist items DCS & PSS available in the Settings > Flight Editing > OPS Checklist Items section. The items are not marked, so either need to be marked to appear on each single flight, or added from 'ADD ITEM' panel of the checklist in OPS section. Once added, they will appear with the **SEND** button. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== Sending ASM messages to DCS & PSS ==== | ||
+ | |||
+ | By clicking SEND button for DCS or PSS item, Leon shows a new pop-up window, which shows pre-defined message. Leon shows **3** types of messages in formats as on screenshots below (formats are the same for DCS & PSS systems). If no default email address has been added in Settings > SSIM, Leon will show a warning information: | ||
+ | |||
+ | **1**. **NEW - Insertion of New Flight Information** - displayed when sending ASM message for the new flight. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **2**. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **3**. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once ASM message has been sent out, Leon will change the checklist item's status **automatically** to ' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Filters ===== | ||
+ | |||
==== Filter - Tab SCHEDULE ==== | ==== Filter - Tab SCHEDULE ==== | ||
This tab is divided into several sections, such as: | This tab is divided into several sections, such as: |