Differences

This shows you the differences between two versions of the page.

--- leon:flight-checklist [2015/06/03 10:06]
bartek [Handling requests]
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Flight checklist ======
-Once the flight has been added to Leon, OPS team can start preparring it for dispatch by working on particular sectors in '**Legs Info**' screen. From 'Flights list' page you can go to 'Legs Info' screen by clicking on the dot, in the column '__Status__'. From 'Planned flights' page you can get there by editing a flight and clicking on the 'Legs Info' icon at the bottom-right corner of the window.
-If the flight has more than one sector, you can edit each one of them and switch between them on the legs status edit page without going back to the flights view. It can be usefull if there is a lot of data that needs to be changed at the same time. In such case you can tick the box 'Save data after leg change' above the tabs to avoid losing stored data. If you do not mark this box, Leon will require you to click 'Update leg'.
-===== Checklist =====
-[{{ :leon:flight-checklist:checklist-tooltip.png?300|Checklist tooltip}}]
-Which tabs should be displayed inside the 'Checklist' window can be selected in **Admin** > **Operator settings** > **Flight Editing** tab. Some of the available sections include:
-  * **FPL** - Flight Plan (ATC) -  all information relevant to the specific planned flight.
-  * **OFPL** - Operational Flight Plan, which is prepared for the crew with fuel details, point names, winds, etc.
-  * **A/C performance**
-  * **Crew aware of trip** - once the crew is assigned to the trip you can set the status to 'ACK'. If you make any changes in crew assigment for that flight, the 'Crew aware of trip' status in 'Legs Info' will turn from 'ACK” to '?'
-  * **Overflight permission** - in the tab 'Ops' you can either add it by clicking on 'add new permit' and choose the country from the list (recommended) or just paste it in the notes-field.
-  * **Landing permission** - it can be added in the same way as overflight permission (see above).
-  * **Airport slots** - split into 2 sections: ADEP & ADES.
-  * **PPR** - Prior Permit Required.
-  * **Ops notes** - for internal usage (do not appear on any documents).
-  * **Notes** - these notes will appear on the 'Trip Sheet' document.
-  * **Fuel** - you can add fuel prices and the amount as well as upload your own fuel prices (check tab 'Fuel' or section [[manual:handling|Handling]]).
-  * **Handling** - split into 2 sections as 'Airport slots'. For each particular airport you can choose a handling agent you wish to use (also see section [[manual:airport-directory|Airport Directory]] for more information as to how to set default handling agents).
-  * **Crew transport** - you can specify the mode of transportation, hotel or other HOTAC details for your crew (see tab 'Crew').
-  * **Pax** - list of passengers, which can be added in 2 ways: text or database (you can set default pax list type in **Admin** > **Operator settings** > **General**. Pax can also be added from 'Planned Flights' page. When the number of passengers added to the flight exceedes aircraft capacity (inserted in 'Fleet edit' screen), Leon will issue a warning (see screenshot on the right).
-  * **Pax transport** - divided into 2 sections: ADEP & ADES transport (also can be specified from 'Planned Flights' page).
-Sections directly related to '**Sales**' are separately divided in **Admin** > **Operator settings** > **Flight editing** page where you can select the sales checklist statuses to be included in overall trip status.
-  * **Flight briefing** - details including: take-off & enroute data, aerodrome forecast or remarks.
-  * **Catering** - add information that will be available to your crew about pax food/drinks preferences. You can also specify different catering preferences in the [[manual:phonebook|Phonebook]].
-  * **Crew transport** - transport for crew from /to ADEP & ADES airport.
-  * **Hotel** - available in the tab 'Crew' - you can select a hotel for crew (or it can appear automatically if set as default/favourite in 'Airport Directory' screen, when editing a particular airport) and also you can mark if **breakfast, lunch or dinner** are provided.
-  * **Ground transport** - transport for pax from /to ADEP & ADES airport (it can be also set in 'Planned Flights' screen).
-  * **Contract signed** - signed by a client or a broker.
-  * **Invoice** - whether it has been sent and if payment is received.
-<box>All sections from the tab 'Checklist' are also available in separate tabs: Ops, Fuel, Handling, Crew, Pax, Catering and additional Flight watch, where more details can be edited. Changes in tab 'Checklist' affect other tabs and vice-versa.</box>
-----
-Each section has its own drop down menu where, by default, the status {{:leon:icons:checklist default.png?nolink&50|}} (untouched) is selected (nothing was done about this item). Various sections have different options with different colours assigned.
-The colour of dot on the 'Flights list' page gives you a quick information about flight preparation status.
-  * {{:leon:icons:green dot.png?nolink&30|}} - flight is ready - everything has been prepared.
-  * {{:leon:icons:yellow dot.png?nolink&30|}} - flight is not ready - some items are waiting to be confirmed.
-  * {{:leon:icons:red dot.png?nolink&30|}} - flight is not ready - some items require work done.
-===== Handling Requests and GARs =====
-<html>
-<span style="color:red;font-size:150%;">IMPORTANT!</span>
-</html>
-<box>In the new version of Leon it is possible to use a **NEW HANDLING REQUESTS** module. The new module works **independently** from the current one. It is advised that you **use only one module** (not to skip between them) to avoid confusion. The new module will eventually replace the current one. More information can be found [[man:handling-requests|here]].</box>
-[{{ :leon:flight-checklist:Handling Requests main screen.png?300|Old 'Handling Requests' version - the main screen}}]
-This tool allows you to save a lot of time on preparing and sending emails to **handling agents** and/or preparing **GARs** (General Aviation Reports). In order to use this tool you need to configure default handling requests by going to **Admin** > **Operator Settings** > **Handling Requests** (follow steps described in details [[manual:operator-settings|here]]). Once this is set up handling requests document can be sent out.
-After opening the handling tab from **Legs Info** page, you can see the __default__ items that were previously entered in '**Operator Settings**' page. You can always edit these fields and add or delete some items. Uploading of documents is also available.
-To include **HOTAC** information in handling request, click the appropriate check box in **Crew** tab. It is also possible to add HOTAC default details in **Admin** > **Operator Settings** > **Handling Requests** as well as to add additional information if breakfast, lunch or dinner is provided (tick appropriate check-boxes).
-If **passengers data** has been added in the tab '**Pax**' it will also be displayed on HR and GAR document.
-==== Handling requests ====
-When the flight planning is done you can send handling requests by clicking proper button. It will change the colour to red each time you **modify any information** that is important for handling agent, including flight cancellation or PAX list change (which is particularly important for sending GARs - the status will be changed to {{:leon:icons:znak zapytania.png?nolink&60|}}
-[{{ :leon:flight-checklist:HR email.png?300|'Handling Requests' sending emails panel}}]
-After clicking {{:manual:icons:HR button.png?nolink&100|}} button a new window will appear on the screen. Here you can find names of selected agents along with airport codes, statuses of the requests, and links that allow you to preview requests and email messages that are to be sent. By using email view, you can also upload some additional documents that should be sent with handling requests. There are also check boxes that allow you to select which agents should receive the requests.
-If you want to send documents in other way than by Leon HR module (i.e. by using your private email) you can update the status of HR button without sending documents by clicking on the appropriate icon.
-{{:leon:flight-checklist:HR button.png|}}
-Once the handling requests email has been sent the handling status will change to {{:leon:icons:RQS.png?nolink&55|}} and the colour of the HR button will become grey. By cliking on it you will notice that the 'new request' icon colour is green now. There is also an information about who and at what time has sent HR email.
-[{{ :leon:flight-checklist:HR sent.png?300|'Handling Requests' status changed after the email has been sent}}]
-<box> If there are any important changes done to the flight, such as: **Time change**, **Date change**, **Aircraft change**, **Destination/Departure change** - the colour of the HR button will turn to red  {{:leon:icons:HR button.png?nolink&100|}} and also handling agent status will become {{:leon:icons:znak zapytania.png?nolink&55|}}. All the other changes, such as: Crew change, Pax change, etc... will make the colour of the HR button turn to orange {{:leon:icons:HR orange.png?nolink&100|}} </box>
-When you click on the HR button, an icon 'Amended Request' will be available. Click on 'show' to check what changes have been applied to the flight - they will be visible on the document in the column 'DETAILS', i.e. flight number changed. All changes are displayed in red.
-It is also possible to view history of emails/documents previously sent out, by clicking on the icon 'history'.
-==== New Handling Requests ====
-[{{ :manual:flight-preparation-checklist:New handling req.png?300|New 'Handling Requests' panel}}]
-The main difference between sending **Handling Requests** emails in the current version and the **new version** is that right now a handling agent does not get the information about the next departure times, or details about which handling agent should make services for the departure flight: should it be the same handling agent or a different one?
-In the new version sending handling requests emails **always** concern only the airport where the email is sent.
-**New Handling Requests** are available from Handling tab in OPS Checklist and are located next to {{:manual:icons:HR button.png?nolink&100|}}.
-Clicking on one of the links will open new Handling Request email window and also it will give access to HR History.
-Handling Request window is fully editable. Let's use EPPO Airport as an example.
-{{:manual:flight-preparation-checklist:New-HR.png?500|}}
-[{{ :manual:flight-preparation-checklist:update-new.png?300|Updating handling requests}}]
-You also see that when sending HR email to a handling agent at the airport EPPO not only there are **details about the arrival flight** to EPPO, but also **details about the next departure flight** __from__ EPPO
-Once handling request is sent, the status will change to {{:manual:flight-preparation-checklist:rqs.png?55|}} and the link will change its status from **EPPO New Request** to **EPPO Show History**.
-In a situation when a handler has to be changed on one of multiple leg trip, **New Handling Request** facility will allow to simultaneously send Update email to old handler and new request email to a New Handler:
-In case when one leg of a trip has to be deleted Leon will populate cancellation email ready to send.
-{{:manual:flight-preparation-checklist:cancellation.png?500|}}
-As mentioned before, the history of changes is easily accessible from History section via New Handling Request Link for the Airport (EPPO as an example)
-{{:manual:flight-preparation-checklist:History.png?500|}}
-[{{ :manual:flight-preparation-checklist:Change of status.png?300|Updating the status of handling requests without sending actual email}}]
-If you are **sending emails to Handling Agents from external company email and only update manually statuses in Leon**, new version of Handling Requests will automatically update to **EPPO Show History** and the status in the history section.
-Clicking on the **EPPO Show History** will display **There are no changes to this flight** message. **Clicking on it enables an option to send Handling email with an update.**
-**Updating Handling Status also updates the Airport Slots to** {{:manual:flight-preparation-checklist:rqs.png?55|}}.
-If one leg is **cancelled** the status will change to {{:manual:flight-preparation-checklist:question mark.png?55|}} and **New Handling section** will display **EPPO Update** information. Clicking on it will allow to send **Handling request cancellation email**. Once the **cancellation email** was sent, the status will update to {{:manual:flight-preparation-checklist:RQS szary.png?55|}}.
-**All the changes will update Handling Request History as shown in a screenshot below**
-{{:manual:flight-preparation-checklist:Manual HR.png?500|}}
-As you can see in the screenshot, Handling Request with teh status updated manually will have no email information and will only display a message **This email wasn't sent to an agent**.
-==== GAR ====
-Sending GAR documents is very similar to sending Handling Requests. When the PAX list is ready you should click 'Send GAR' button on Checklist or OPS tab on Legs Info page. You will find two 'Send GAR' buttons that allow you to send this document to handling agent at selected airport separately. After clicking the proper button a new window will appear on the screen. It allows you to edit default email content and preview GAR document by clicking view link.
-**GAR document** sent to **UK based airport** looks slightly different from **non-UK based Airport** as shown below.
-[{{:man:handling-requests:UK GAR1.jpg?500|GAR for UK based airport}}]
-[{{:man:handling-requests:Non UK GAR.jpg?500|GAR for non-UK based airport}}]
-=====Flight Status=====
-[{{ :manual:flight-preparation-checklist:flight status.png?300|Flight Status - flight preparation view}}]
-This view is useful to have overview of preparation stage of all up-coming legs. You can hover the computer mouse over the selected field to view information added in 'Legs Info' screen under the check-field.
-By clicking on the particular flight number you will be re-directed to the 'Legs Info' page.
-----
-<box nav-left>[[manual:editing-schedule|< Editing schedule]]</box> <box nav-right>[[manual:flight-watch|Flight Watch >]]</box>

Leonsoftware Wiki

User Tools

Site Tools

Differences

Page Tools