This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Previous revision Last revision Both sides next revision | ||
leon:checklist [2019/09/30 09:21] |
leon:checklist [2024/03/11 15:40] bartek [Permits requesting] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Checklist ====== | ||
+ | <box tutorial> | ||
+ | [{{ : | ||
+ | |||
+ | Once the flight is created, both **OPS** and **Sales** departments can start preparing the flight for dispatch by working on particular sectors of the **Checklist**. | ||
+ | |||
+ | To access the checklist you have to either open right-hand filter, tab ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | Checklist tab is devided to 2 sections depending on the department preparing the flight: | ||
+ | |||
+ | - **Ops** | ||
+ | - **Sales** | ||
+ | |||
+ | It is possible to **roll up the sub-section of a checklist**. Each sub-section has a **coloured dot** indicating summarised status of items in the sub-section: | ||
+ | |||
+ | * < | ||
+ | <span style=" | ||
+ | </ | ||
+ | * < | ||
+ | <span style=" | ||
+ | </ | ||
+ | * < | ||
+ | <span style=" | ||
+ | </ | ||
+ | * < | ||
+ | <span style=" | ||
+ | </ | ||
+ | If the flight has more than one sector, you can edit each one of them and switch between them in the OPS view. **It is important to remember to save the changes made to the checklist, otherwise they will be lost.** It is possible to **add a note** and **upload a file** to each item of the checklist. An alternative way of uploading files is to drag & drop it into the checklist item. In order to do that you have to click on the name of the checklist item, for example CARGO. You will see space for notes and {{: | ||
+ | |||
+ | [{{ : | ||
+ | After a **file is uploaded** it will show with underlined name and the tickbox i.e. {{: | ||
+ | |||
+ | By clicking the icon {{: | ||
+ | |||
+ | - **RESET STATUSES** - all items which have been set up to yellow or green statuses will turn back to {{: | ||
+ | - **DOWNLOAD ALL FILES** - all files attached to the particular flight will be downloaded in the **ZIP** format. | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | |||
+ | ===== Automatic adding/ | ||
+ | |||
+ | There is an automatic algorithm for adding or removing items in the checklist when they are required or not. This algorithm is run each time the flight is saved (created or changed). | ||
+ | |||
+ | **Adding items automatically: | ||
+ | |||
+ | An item will be automatically added to the checklist when **both** conditions are met: | ||
+ | - The item is enabled in Settings -> Flight Editing | ||
+ | - The activity meets the rule set for this item | ||
+ | |||
+ | For example, the item " | ||
+ | |||
+ | The default status for the items added automatically is **Untouched**. If you don't change it, the item can be automatically deleted from the checklist if any changes to the flight are made, as described below. | ||
+ | |||
+ | **Removing items automatically: | ||
+ | |||
+ | An item will be automatically removed from the checklist when the item's status is **Untouched**, | ||
+ | |||
+ | - The item is disabled in Settings -> Flight Editing | ||
+ | - The activity doesn' | ||
+ | |||
+ | For example, the item " | ||
+ | |||
+ | |||
+ | |||
+ | ===== Manual adding/ | ||
+ | |||
+ | |||
+ | It is possible to add additional items and remove not-needed ones while preparing the flight. | ||
+ | [{{ : | ||
+ | To **add** a checklist item you simply need to click on the **+ ADD ITEM** button located on the top-right part of the filter. You will get a list of items that are not ticked in the Operator Settings section but are still available. Click on the item that you need and this item will be added to this particular leg of the trip. Finally, press the " | ||
+ | |||
+ | < | ||
+ | |||
+ | If after pressing **+ ADD ITEM** bottom you see "No items left to add" message, it simply means that all available items are added to the checklist. | ||
+ | |||
+ | |||
+ | If there are items that you do not need in your checklist, you can **remove** them. Removing items is as simple as adding one. You just need to click on {{: | ||
+ | |||
+ | |||
+ | ===== Ops checklist ===== | ||
+ | |||
+ | The items which should get displayed inside the ' | ||
+ | |||
+ | Some of the available sections include: | ||
+ | |||
+ | * **ATC Flight Plan** - all information relevant to the specific planned flight. | ||
+ | * **Operational Flight Plan** - which is prepared for the crew with fuel details, point names, winds, etc. | ||
+ | [{{ : | ||
+ | * **Landing permission** - you can simply add permit information by clicking on the " | ||
+ | * **Overflight permission** - it can be added in the same way as landing permission (see above). | ||
+ | * **Crew aware of trip** - once the crew is assigned to the trip you can set the status to ' | ||
+ | * **Airport slots** - split into 2 sections: ADEP & ADES. Times inserted in the slots change in accordance with changes of the schedule if the status of the Slot is set to red (' | ||
+ | * **PPR** - Prior Permit Required. | ||
+ | {{ : | ||
+ | * **Fuel** - divided into 4 sections: Block, Burn, MRF (Minimum Required Fuel), Requested, and Flight Time. It is possible to include value inserted in the ' | ||
+ | * **Handling** - described further down in this section | ||
+ | [{{ : | ||
+ | * **Crew transport** - here you can specify the way of transportation details for your crew. Notes added to these items will show in the Trip Sheet. | ||
+ | * **Hotel** - in the Hotel section of [[leon: | ||
+ | * **Pax catering** - in the notes section you can add some extra information regarding Passengers. This information will show in the Trip Sheet. For more specific information on Passengers see section [[leon: | ||
+ | * **Pax transport** - divided into 2 sections: ADEP & ADES transport. Notes added here will show in the Trip Sheet. | ||
+ | * **Sanctions List** - allows searching for sanctioned PAX. More information can be found in the [[leon: | ||
+ | * **Sponsor** - this item will allow indicating whether there is a person or organization that pays for or contributes to the costs involved in the visit. The element can be selected by default in the ' | ||
+ | |||
+ | * **GAR sent** - applies to UK destinations only. Located in the **Customs** section of the checklist allows sending GAR emails to the relevant authorities. Clicking on "Send GAR" opens an email window. It is possible to insert two GAR emails separated by a comma in the ' | ||
+ | * **Cargo** - a section where you can insert the cargo value.**Cargo value input** is only available for **Non-Cargo Operators**. **Cargo Operators** will only be able to insert the cargo values in the 'EDIT TRIP' section as **Cargo value input** has been removed from the ' | ||
+ | * **ACC3** - the item can be selected in the ' | ||
+ | |||
+ | When sending **Requests** for ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ----------- | ||
+ | |||
+ | ===== Changes history ===== | ||
+ | |||
+ | To check the history of changes done in a particular item you need to **click on the item name** and then click on the {{: | ||
+ | |||
+ | In the changes history window, Leon shows the chronological list of all changes (the latest on top). The colours indication shows added data in green, changed data in yellow and removed data in red. | ||
+ | |||
+ | You can also trace a history of one item changes by clicking on the status. Leon will then highlight the initial entrance of the details as well as all the changes that applied. Below you can see it by example of the Handling Request status changes: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | You can also click the icon {{: | ||
+ | |||
+ | ------------------ | ||
+ | ===== Get Country List in Overflight Permits ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | |||
+ | It is now possible to **search for the list of countries** for Overflight permit purposes using alternatively Route Finder calculated route, or your actual FPL routing. | ||
+ | |||
+ | In order to search for the countries, the **following steps** need to be performed: | ||
+ | |||
+ | - Go to 'OPS Checklist' | ||
+ | - In the " | ||
+ | - Click on the 'GET COUNTRY LIST' button within the ' | ||
+ | - If FPL routing is entered, it will be used to generate the country list | ||
+ | - If the routing was empty, the route and country list will be generated using Route Finder | ||
+ | - When the list of countries appears, check if all the necessary countries are listed, and remove unnecessary ones. **Additionally**, | ||
+ | - ' | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | < | ||
+ | --------------------- | ||
+ | ===== Permits requesting ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | |||
+ | |||
+ | It is possible to **request** directly from Leon **Landing permit** and **Overflight permit**. | ||
+ | |||
+ | In order to make this work, follow these steps. | ||
+ | |||
+ | **1**. **Defining email templates** | ||
+ | |||
+ | In a section Settings > Email Templates click {{: | ||
+ | |||
+ | On the new page you can insert email **Subject** and below you can re-arrange the default **Body**, by using **Available Data** items from the right filter. Another tab **Recipients** allows to define default email addresses: From, Reply to, CC and BCC. Once it's all set up you can use sending permits requests from the section OPS. | ||
+ | |||
+ | **2**. **Adding permits details** | ||
+ | |||
+ | [{{ : | ||
+ | [{{ : | ||
+ | |||
+ | In the **Checklist** panel click button | ||
+ | |||
+ | Once a new pop-up window got displayed (see screenshot on the right), fill it in with details, such as: | ||
+ | |||
+ | - Country | ||
+ | - Supplier | ||
+ | - Number | ||
+ | - Validity | ||
+ | - Revalidation | ||
+ | - Note | ||
+ | - Status (select from the drop-down box) | ||
+ | |||
+ | You can also mark a checkbox 'Short notice 72h', if necessary. Clicking **+** button allows adding another permit' | ||
+ | [{{ : | ||
+ | **3**. **Requesting permits** | ||
+ | |||
+ | The last step is **sending a permit email**. Click a button {{: | ||
+ | |||
+ | There, you can also request permits for multiple countries, by selecting the checkboxes by the country names. The names on of the countries can be automatically included in the email content, depending on the Overflight Permit email template setting. | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | Once the correspondence is triggered from Leon, and the 'Reply to' email address is connected to the mailboxes, the history of emails is kept in this tab. | ||
+ | |||
+ | When requesting for landing or overflight permit, there will be an option to attach aircraft documents to the message. | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | In the requesting permit window Leon will show documents to be attached at the bottom, however, only documents defined in the Fleet Documents section with uploaded files will be visible in the attachments list. | ||
+ | |||
+ | |||
+ | |||
+ | ---------- | ||
+ | ===== Handling ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Handling Requests section of the checklist is split into 2 parts, same as ' | ||
+ | |||
+ | **Here is the explanation for the icons showing in HANDLING section:** | ||
+ | |||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | |||
+ | Handlers can also be **assigned automatically** when creating a trip, in the following order: | ||
+ | |||
+ | - **Requester** - applies when the trip is created from the ' | ||
+ | - **Fleet** - Handler selected in the Admin Panel > Fleet > SALES tab section | ||
+ | - **Airport Directory - Favourite** - Handler marked as ' | ||
+ | - **Airport Directory - Approved** - Approved date selected in the Airport Directory | ||
+ | |||
+ | |||
+ | In HANDLING section you can also check what changes have been made to the flight that affected handling request status. To check it simply hover the mouse over the HR status and the information will be displayed in a tooltip. | ||
+ | |||
+ | |||
+ | Notes added in this section will also show in the Trip Sheet document. More information on Handling Request functionality can be found [[leon: | ||
+ | |||
+ | ==== Attaching extra documents to HR email ==== | ||
+ | |||
+ | GenDec and/or PAX Manifest can be attached to a Handling Requests email by marking a checkboxes: ' | ||
+ | |||
+ | It is now also possible to attach an **additional document** when sending out Handling Requests email. By default this document is named ' | ||
+ | |||
+ | |||
+ | |||
+ | Go to Settings > Documents Manager panel, click {{: | ||
+ | [{{ : | ||
+ | Below you can find an example of a custom document ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once it's saved you will find this document as unpublished (indicated with the white dot, if you change in the upper filter from YES to NO). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Edit the document and re-arrange it in Documents Manager panel according to your needs by using ' | ||
+ | |||
+ | In a section OPS > Checklist > Handling, when sending a new Handling Requests email, it will be possible to attach new document along with GenDec (see screenshot on the right). | ||
+ | |||
+ | ---- | ||
+ | ==== Tagging Handling agents ==== | ||
+ | |||
+ | We have added a new option of **tagging** Handling agents/ | ||
+ | |||
+ | The first step that needs to be taken in order to set it up is creating tags for a particular handler. Go to **Airport Directory**, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When assigning handlers in the **checklist**, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The next step is connecting already added tags to **Crew Trip Sheet** document, in **Documents Manager** panel by using the item ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== GAR ===== | ||
+ | [{{ {{ : | ||
+ | [{{ : | ||
+ | |||
+ | |||
+ | |||
+ | Sending **GAR** documents is very similar to sending Handling Requests. When the PAX list is ready you should click **Send GAR** button in the Checklist tab (right-hand filter). | ||
+ | |||
+ | You will find two 'Send GAR' buttons which 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 **Preview GAR -->** link. | ||
+ | |||
+ | A default email content for GAR can be defined in section Settings > Handling Requests, field ' | ||
+ | |||
+ | It is possible to add **information** such as: Visit reason and Visit address into the editable screen, which will get exported onto the GAR sheet. | ||
+ | |||
+ | **Visit reason** can also be selected from the drop-down box, where options are: Short-term visit, Based, Maintenance, | ||
+ | |||
+ | An option to select between **XLS** and **PDF** formats when sending GAR is also available. In a section Settings > Handling Requests you can define a default GAR format. | ||
+ | |||
+ | As for the **Channel Islands' | ||
+ | |||
+ | - Crew Hotel selected in the Checklist | ||
+ | - Crew home address if crew Home Base is either Jersey or Guernsey. As for PAX, the home address will appear if the country is selected as Jersey or Guernsey | ||
+ | - ' | ||
+ | |||
+ | Channel Islands GAR's are only available in the PDF format. | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | ===== Sales checklist ===== | ||
+ | |||
+ | Sections directly related to **Sales** are separately divided in [[leon: | ||
+ | |||
+ | **2 items** are particularly important in SALES checklist: | ||
+ | [{{ : | ||
+ | |||
+ | ^ Invoice | ||
+ | | The applicable statuses and their colours in this item are as below | This item has been added to separate typical ' | ||
+ | | | ||
+ | |||
+ | Each section has its own drop-down menu where the status {{: | ||
+ | |||
+ | The colour of the dot on the ' | ||
+ | |||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | |||
+ | **If an item concerns the entire trip (not a single leg) Leon will show TRIP right below the item's name.** | ||
+ | |||
+ | ==== Payments ==== | ||
+ | |||
+ | |||
+ | |||
+ | If you use an item **Payments** in your Sales checklist, Leon will show in the CALENDAR section an additional icon **$** in the flight' | ||
+ | |||
+ | The colour of the icon **$** corresponds with the colour of the ' | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Positioning checklist ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | By clicking on a **Positioning** checklist dot in a section OPS (right-hand filter), Leon shows 3 default items of which statuses can be set up. | ||
+ | | ||
+ | A button **+ADD ITEM** allows adding more items (previously defined in a section Settings > Flight Editing) in the same way as with OPS or sales checklist. | ||
+ | |||
+ | **RESET STATUSES** button turns all items statuses back to ' | ||
+ | |||
+ | ---- | ||
+ | < |