This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:flight-checklist [2015/06/03 10:06] bartek [Handling requests] |
leon:flight-checklist [2021/04/07 06:05] bartek removed |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Flight | + | ====== Flight's Checklist |
- | Once the flight has been added to Leon, OPS team can start preparring | + | Once the flight has been added to Leon, OPS team can start preparing |
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' | 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' | ||
- | ===== Checklist ===== | ||
- | [{{ : | ||
- | 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: | + | ===== The Checklist |
+ | |||
+ | |||
+ | The tabs you need displayed inside the ' | ||
+ | |||
+ | |||
+ | |||
+ | Some of the available sections include: | ||
+ | [{{ : | ||
* **FPL** - Flight Plan (ATC) - all information relevant to the specific planned flight. | * **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. | * **OFPL** - Operational Flight Plan, which is prepared for the crew with fuel details, point names, winds, etc. | ||
Line 21: | Line 27: | ||
* **Ops notes** - for internal usage (do not appear on any documents). | * **Ops notes** - for internal usage (do not appear on any documents). | ||
* **Notes** - these notes will appear on the 'Trip Sheet' document. | * **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** - you can add fuel prices and the amount as well as upload your own fuel prices (more information |
- | * **Handling** - split into 2 sections as ' | + | * **Handling** - split into 2 sections, same as ' |
* **Crew transport** - you can specify the mode of transportation, | * **Crew transport** - you can specify the mode of transportation, | ||
- | * **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** - list of passengers, which can be added in 2 ways: text or database (you can set default pax list type in [[leon: |
- | * **Pax transport** - divided into 2 sections: ADEP & ADES transport (also can be specified from ' | + | * **Pax transport** - divided into 2 sections: ADEP & ADES transport (also can be specified from Sales > Calendar |
- | Sections directly related to '**Sales**' | + | Sections directly related to Sales are separately divided in [[leon: |
* **Flight briefing** - details including: take-off & enroute data, aerodrome forecast or remarks. | * **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: | + | * **Catering** - add information that will be available to your crew about pax food/drinks preferences. You can also specify different catering preferences in the [[leon: |
* **Crew transport** - transport for crew from /to ADEP & ADES airport. | * **Crew transport** - transport for crew from /to ADEP & ADES airport. | ||
* **Hotel** - available in the tab ' | * **Hotel** - available in the tab ' | ||
- | * **Ground transport** - transport for pax from /to ADEP & ADES airport (it can be also set in 'Planned Flights' screen). | + | * **Ground transport** - transport for pax from /to ADEP & ADES airport (it can be also set in 'Calendar' screen). |
* **Contract signed** - signed by a client or a broker. | * **Contract signed** - signed by a client or a broker. | ||
- | * **Invoice** - whether it has been sent and if payment | + | * **Invoice** - whether it has been sent and if payment |
< | < | ||
- | ---- | + | |
- | Each section has its own drop down menu where, by default, the status {{: | + | Each section has its own drop down menu where by default the status {{: |
The colour of dot on the ' | The colour of dot on the ' | ||
- | * {{: | + | * {{: |
- | * {{: | + | * {{: |
- | * {{: | + | * {{: |
- | + | ||
- | ===== Handling Requests and GARs ===== | + | |
- | + | ||
- | < | + | |
- | <span style=" | + | |
- | </ | + | |
- | + | ||
- | < | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | After opening the handling tab from **Legs Info** page, you can see the __default__ items that were previously entered in ' | + | |
- | + | ||
- | 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 ' | + | |
- | + | ||
- | ==== 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 {{: | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | After clicking {{: | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | Once the handling requests email has been sent the handling status will change to {{: | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | <box> If there are any important changes done to the flight, such as: **Time change**, **Date change**, **Aircraft change**, **Destination/ | + | |
- | + | ||
- | When you click on the HR button, an icon ' | + | |
- | + | ||
- | It is also possible to view history of emails/ | + | |
- | + | ||
- | ==== New Handling Requests ==== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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 {{: | + | |
- | + | ||
- | + | ||
- | + | ||
- | 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. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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 {{: | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | 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) | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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** {{: | + | |
- | + | ||
- | If one leg is **cancelled** the status will change to {{: | + | |
- | + | ||
- | **All the changes will update Handling Request History as shown in a screenshot below** | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | [{{: | + | |
- | + | ||
- | [{{: | + | |
- | =====Flight Status===== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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> |