This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:sales [2021/03/15 12:02] rafal [Flight time calculations from Aviapages] |
leon:sales [2023/12/20 19:13] (current) rafal [Price Based] |
||
---|---|---|---|
Line 12: | Line 12: | ||
The main page displays several columns: | The main page displays several columns: | ||
- | [{{ : | + | [{{ : |
* **ID** - quote request ID. | * **ID** - quote request ID. | ||
- | * **Status** - showing the status of the quote: New request, Quoted, Booked, Option, Brief sent, Contract sent, Rejected or Closed. | + | * **Status** - showing the status of the quote: New request, Quoted, Booked, Option, Brief sent, Contract sent, Rejected, or Closed. |
- | * **Requester** - requesting client' | + | * **Requester** - requesting client' |
* **Aircraft** - requested aircraft registration & type. | * **Aircraft** - requested aircraft registration & type. | ||
- | * **Itinerary** - requested itinerary. | + | |
+ | * **Aircraft sold** - displays the registration of the booked aircraft (status BOOK) | ||
+ | * **Checklist** - displays the overall status of the Sales checklist on the booked trip. Hovering the mouse over the dot will display the detailed statuses of each element of the checklist. Only the elements that apply to trip are displayed | ||
+ | | ||
+ | |||
+ | {{: | ||
* **Created** - informs when the request has been created. Switched off by default, can be switched on in the ' | * **Created** - informs when the request has been created. Switched off by default, can be switched on in the ' | ||
* **Updated** - day, month & exact time (LT) of updating the quote as well as the source (Avinode or Leon). | * **Updated** - day, month & exact time (LT) of updating the quote as well as the source (Avinode or Leon). | ||
* **Assignee** - first person who is editing unread RFQ and designated to work with the quote. Underneath the person' | * **Assignee** - first person who is editing unread RFQ and designated to work with the quote. Underneath the person' | ||
- | * **Quote** - list of possible aircraft quotes with prices - the lowest price is always on top. | + | * **Quote** - list of possible aircraft quotes with prices - the lowest price is always on top. |
+ | * **Ferry flight time/PAX flight time** - the values of ferry flight time and PAX flight time. Hovering the mouse over the values, the following information is displayed: **Ferry flight time/PAX flight time, ratio value**. **Ratio** value calculated as 'Ferry flight time/PAX flight time*100%' | ||
+ | * **Booking ratio** - the percentage of booked quotes from the last 90 days. Right next to the percentage value Leon shows in brackets the number of booked quotes and after the slash, the number of all quotes **per a requester** | ||
+ | * **Broker revenue** - the sum of prices (in operator' | ||
+ | * **Avinode price** - column presenting the price from Avinode initial request | ||
* **Messages** - Leon displays all comments added in the quote' | * **Messages** - Leon displays all comments added in the quote' | ||
- | * **Action** - hover the mouse over and there are **3 icons** available: **Trash icon** to delete the quote, **Clone icon** to copy the quote and **Envelope icon** to mark the quote as ' | + | * **Action** - hover the mouse over and there are **3 icons** available: **Trash icon** to delete the quote, **Clone icon** to copy the quote, and **Envelope icon** to mark the quote as ' |
In the top-right corner there is a {{: | In the top-right corner there is a {{: | ||
Line 32: | Line 43: | ||
Use **3** available fields on top of the page to filter the list of quotes: | Use **3** available fields on top of the page to filter the list of quotes: | ||
- | * **Type to search** - you can type any part of the ID or Requester to find the quote. | + | * **Type to search** - you can type any part of the ID, Requester, or Representative |
* **Status** - Leon shows ' | * **Status** - Leon shows ' | ||
- | * **Show** - you can filter the Requests | + | * **Show** - you can filter |
- | * **Show also archived** - checkbox that allows displaying archived requests. The request is considered as ' | + | * **All** - displaying either all requests |
+ | * **With unread messages** - displaying only the requests | ||
+ | * **Empty leg requests** - displaying only requests for empty legs coming | ||
+ | * **Owner requests** - displaying trips requested by the owner in the Owner App ('Owner' | ||
+ | * **Sold only** - displays only booked requests (status BOOK) | ||
+ | * **Updated in OPS** - displays the quotes with the changes applied in the OPS section but not updated in the ' | ||
+ | * **Show also archived** - a checkbox that allows displaying archived requests. The request is considered as ' | ||
+ | * **FILTER** - allows filtering by: | ||
+ | * **Assignees** - sales person(s) assigned to quotes | ||
+ | * **Tags** - tag(s) assigned to quotes | ||
{{: | {{: | ||
+ | [{{ : | ||
+ | In the **Itinerary** column Leon indicates the timeframe to the start of a flight by underlining the specific leg as per below: | ||
+ | |||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | |||
+ | The abovementioned indications only apply to the **new requests**. | ||
It is also possible to **sort the requests** by: | It is also possible to **sort the requests** by: | ||
Line 51: | Line 79: | ||
* **REJECT REQUEST** - allows to quickly reject a request | * **REJECT REQUEST** - allows to quickly reject a request | ||
- | * **CLONE REQUEST** - option to clone specific | + | * **CLONE REQUEST** - option to clone specific |
* **DELETE REQUEST** - option to delete request. Option briefly described below | * **DELETE REQUEST** - option to delete request. Option briefly described below | ||
* **ASSIGN TO** - option to assign the request to a person and base | * **ASSIGN TO** - option to assign the request to a person and base | ||
Line 59: | Line 87: | ||
------------------------ | ------------------------ | ||
- | ==== CLONING REQUESTS ==== | ||
- | [{{ : | ||
- | It is now possible to **clone** the request. | ||
- | It is useful when the quotes are requested from different sources or brokers. | + | ==== Open in Airport Directory |
- | + | ||
- | In that case, rather than inserting one quotation details a number of times, the Sales team can simply clone it (copy it). | + | |
- | + | ||
- | **The process** is quite simple: | + | |
- | + | ||
- | - Press {{: | + | |
- | - In the pop-up window (screenshot on the right-hand side) select ' | + | |
- | - **Cloned request** is opened, automatically saved and the person cloning it is selected as an ' | + | |
- | + | ||
- | The cloned request will always be displayed **at the top** of the ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | **The following data are copied from the source request: | + | |
- | * All the quotes within one request including subcharter | + | |
- | * Pricing and VAT rate assigned to each quote | + | |
- | * The list of PAX as long as set up in the source request | + | |
- | + | ||
- | **The following items are NOT copied from the source request: | + | |
- | * The status of a request. Each copied request is saved with the status **' | + | |
- | * Comments/ | + | |
- | * Old Client' | + | |
- | * Checklists | + | |
- | * Trip number if the source request is with the status ' | + | |
- | * Assignee | + | |
- | + | ||
- | It is possible to clone a request from **Avinode**. The outcome of this operation will be a **Leon** quote. | + | |
- | ----------------------- | + | |
- | + | ||
- | ==== OPEN IN AIRPORT DIRECTORY | + | |
[{{ : | [{{ : | ||
- | It is possible to preview selected airport details from ' | + | It is possible to preview selected airport details from the ' |
- | Simply click with the right click of the mouse on the selected itinerary details and Leon will open a pop-up menu where one of the options is **' | + | Simply click with the right click of the mouse on the selected itinerary details and Leon will open a pop-up menu where one of the options is **' |
Hovering the mouse over the airport code, displays **the airport details and airport notes**. | Hovering the mouse over the airport code, displays **the airport details and airport notes**. | ||
Line 113: | Line 108: | ||
------- | ------- | ||
- | ==== SEND MESSAGE TO CUSTOMER | + | ==== Send Message to Customer |
[{{ : | [{{ : | ||
Line 125: | Line 120: | ||
* attach documents | * attach documents | ||
- | If the quote comes from **Avinode**, | + | If the quote comes from **Avinode**, |
**History of correspondence** will display below the current message. | **History of correspondence** will display below the current message. | ||
---------- | ---------- | ||
- | ==== SHOW STATISTICS ==== | ||
- | [{{ : | ||
- | **Show statistics** option is available from: | ||
- | |||
- | * **Requests/ | ||
- | * **Edit request section** - by editing a specific request and clicking on **SHOW STATS** button located under the itinerary | ||
- | |||
- | |||
- | The purpose of this functionality is to show which ones of the Brokers provide a good conversion rate from the initial request to the sold trip. Also, it provides information on the pricing of a similar quote in the past. | ||
- | |||
- | The statistics window is divided into 2 sections: | ||
- | |||
- | * **Requester statistics** - the top part which indicates the conversion statistics of the requester | ||
- | * **Route statistics** - the bottom part which provides information about rooting | ||
- | |||
- | |||
- | __**Requester statistics**__ | ||
- | |||
- | In this section, ' | ||
- | |||
- | {{: | ||
- | |||
- | In ' | ||
- | |||
- | * **REQUESTED** - Total number of requested trips | ||
- | * **QUOTED** - Number of requests that were actually quoted (status ' | ||
- | * **SOLD** - Number of requests that were sold (went through status ' | ||
- | |||
- | Below these values, there is a percentage of a status vs total number of requests | ||
- | |||
- | |||
- | __**Route statistics**__ | ||
- | |||
- | This part displays information about the pricing of the routing in the past. | ||
- | |||
- | It only includes requests that were quoted (status ' | ||
- | |||
- | The purpose is to ensure that the current pricing is at a similar level to the pricing for the same requester that was done in the past. Also, if this is the new routing for a particular requester, it is possible to see how it was priced for other requesters in the past. | ||
- | |||
- | This section is divided into 2 subsections: | ||
- | |||
- | * **Current requester** - shows up to 5 past sold requests for current requester including the price | ||
- | * **Other customers** - shows up to 10 past sold requests for other requesters on the same routing including the price | ||
- | |||
- | The currency is picked from Settings > General Settings > 'Local currency' | ||
- | -------- | ||
- | ==== TAGGING REQUESTS ==== | ||
- | |||
- | [{{ : | ||
- | It is possible to tag requests in a similar to tagging flights/ | ||
- | [{{ : | ||
- | **Creating the tags** is only possible from the main ' | ||
- | |||
- | In order to **create a new tag** you need to: | ||
- | |||
- | * Make sure that the ' | ||
- | * Click on the ' | ||
- | * In the ' | ||
- | * Insert the name of the new tag and press ' | ||
- | * Click on the new tag colour square and select the prefered colour | ||
- | * Save the changes | ||
- | * The tag is added to the list as well as added to the selected request | ||
- | |||
- | It is possible to **assign multiple tags** to one request following the abovementioned process. When tagging a request it is possible to both add new tags as well as assign already existing tags. Clicking on the ' | ||
- | |||
- | If there are multiple tags added to a request, the list will display it as {{: | ||
- | [{{ : | ||
- | There is a possibility of **filtering by tags**. Simply click on the {{: | ||
- | |||
- | The filter works based on ' | ||
- | |||
- | Additionally, | ||
- | |||
- | < | ||
- | ------- | ||
===== New Quote ===== | ===== New Quote ===== | ||
[{{ : | [{{ : | ||
Line 220: | Line 140: | ||
==== Price Based ==== | ==== Price Based ==== | ||
- | [{{ : | + | [{{ : |
To **add a new quote** you need to perform the following steps: | To **add a new quote** you need to perform the following steps: | ||
Line 227: | Line 147: | ||
**2.** Fill in the information in the **'Add new quote request' | **2.** Fill in the information in the **'Add new quote request' | ||
- | * ' | + | |
- | * 'Min. category' | + | * option is always set to LT by default |
- | * ' | + | * times in the Schedule section are not recalculated upon changing the timezone |
- | * 'Add positionings automatically:' | + | * **' |
- | | + | |
+ | * **'Min. category' | ||
+ | * **Trip Type** - selecting the trip type for the booked trip. By default, it is set to the 'Based on configuration' | ||
+ | | ||
+ | | ||
+ | [{{ : | ||
+ | * **Flight rotation selection options**: | ||
+ | * **'One Way or Multi Leg'** | ||
+ | * adding legs with PAX and using **+** to add multiple legs | ||
+ | * **'Round Trip'** | ||
+ | * the itinerary | ||
+ | * there is no possibility to remove or add any extra rows | ||
+ | * ADEP and ADES of the second leg are always filled in based on the airports in the first leg | ||
+ | * update of ADEP modifies ADES in the opposite | ||
+ | * PAX numbers are synchronised in both legs | ||
+ | * once the request is added, any further modifications of the itinerary are excluded from the abovementioned mechanics | ||
- | **3.** Press 'CREATE' to add the request. You can also press **'SKIP' | + | |
+ | |||
+ | There is also an additional option in General Settings > Sales Module - if a checkbox | ||
+ | |||
+ | * **'Flight time'** - select the flight time calculation method. Methods are explained further down in this section. Once the method is selected, it will be remembered by the system when the next request is created | ||
+ | |||
+ | **3.** Press ' | ||
**4.** Request editing section will open, where: | **4.** Request editing section will open, where: | ||
Line 251: | Line 192: | ||
{{: | {{: | ||
+ | < | ||
---------------- | ---------------- | ||
Line 258: | Line 199: | ||
This quotation method allows quoting based on the cost and increasing the quoted amount by a specified margin. | This quotation method allows quoting based on the cost and increasing the quoted amount by a specified margin. | ||
- | In order to quote using 'Costs & margin' | + | In order to quote using the 'Costs & margin' |
* Insert the costs in the ' | * Insert the costs in the ' | ||
Line 267: | Line 208: | ||
- | Quoting based on this method is very similar to 'Price based' method. | + | Quoting based on this method is very similar to the 'Price based' method. |
Within the quote breakdown, you will see the ' | Within the quote breakdown, you will see the ' | ||
- | [{{ : | + | [{{ : |
The **Discount** and **Additional Fee** elements **do not apply to** 'Costs and margin' | The **Discount** and **Additional Fee** elements **do not apply to** 'Costs and margin' | ||
Values in both ' | Values in both ' | ||
- | The major difference is that in the **summary** section, there are 3 elements: | + | The major difference is that in the **summary** section, there are 5 elements: |
* **Cost** - this is the sum of the total costs | * **Cost** - this is the sum of the total costs | ||
* **Margin** - default margin used to calculate the price. Can be manually overwritten | * **Margin** - default margin used to calculate the price. Can be manually overwritten | ||
- | * **Price** - amount for the Client. Calculated in a way that required margin is achieved: | + | * **Price |
* **Price = Cost /(100% - Margin%)** | * **Price = Cost /(100% - Margin%)** | ||
+ | * **Third Party Commission** - the amount of commission paid to the third party, e.g. a broker | ||
+ | * **Total price** - the price that is a sum of 'Price without commission' | ||
+ | * **Gross price** - not editable and appears only if **VAT value** is inserted. Hovering the mouse over the 'Gross price' amount will display VAT value in the tooltip | ||
- | The **sales documents** will still present | + | **Additionally**, hovering |
- | <box>**In case if the default method changed from 'Costs & margin' | + | * **Flight time** and, |
- | ------------ | + | * **Block time** |
- | ===== Avinode ===== | + | |
- | ==== Empty legs from Avinode ==== | + | {{: |
- | [{{ : | + | < |
- | [{{ :leon:sales:Avinode - EL2.png? | + | The **sales documents** will still present the total price from the ' |
- | Active integration with Avinode allows downloading requests for empty legs. | + | <box>**In case if the default method changed |
- | + | ------------ | |
- | Once the empty leg request is downloaded to Leon, Leon creates the full routing including positioning legs if necessary. The aircraft selected in Leon is the same as sent in the empty leg request. If the aircraft does not exist in Leon, the request **will not be accepted by Leon**. | + | |
- | + | ||
- | Leon also calculates the quotation amount based on the pricelists assigned to the aircraft in Settings | + | |
- | + | ||
- | If the downloaded request is for numerous empty legs and for different aircraft, the routing and the quotation are created for each one of them separately. | + | |
- | + | ||
- | Edited empty leg request contains | + | |
- | + | ||
- | Request sent from Avinode will show on the list as a new request with 'Avinode' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ---------------- | + | |
- | ==== Accepting Avinode requests ==== | + | |
- | [{{ : | + | |
- | [{{ : | + | |
- | + | ||
- | To accept the quote that comes from Avinode, you need to: | + | |
- | + | ||
- | * Edit the Avinode quote | + | |
- | * Select | + | |
- | * In the 'Accept quote?' | + | |
- | * Select the aircraft(s) for which you would like to send the response back to Avinode | + | |
- | * Select email template or type in the additional message, which will appear in Avinode | + | |
- | * Select the attachments that you'd like to send to Avinode. This can be the document template or additional pdf file(s) uploaded to this email | + | |
- | * Press ' | + | |
- | + | ||
- | Once the email is sent, the request status will change to ' | + | |
- | + | ||
- | Message | + | |
- | + | ||
- | It is possible | + | |
- | + | ||
- | It is also possible to add Leon quote by selecting 'ADD QUOTE' button. In this case, Leon would recalculate the quote based on the pricelists assigned to this aircraft in Settings > Fleet > Sales tab. | + | |
- | + | ||
- | The updated | + | |
- | + | ||
- | ------------- | + | |
- | ==== Rejecting requests from the list ==== | + | |
- | [{{ : | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | It is possible to reject requests directly from the list of requests. | + | |
- | + | ||
- | This applies to requests received via **Avinode**, **Owner App**, as well as **inserted directly in Leon** as a New Quote. | + | |
- | + | ||
- | To **reject a request** you need to: | + | |
- | + | ||
- | - Click with the right-click of the mouse on the request you'd like to reject | + | |
- | - Select **REJECT REQUEST** button | + | |
- | - **' | + | |
- | * {{: | + | |
- | * {{: | + | |
- | + | ||
- | + | ||
- | + | ||
- | --------- | + | |
- | ==== Find subcharter/ | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | If a request comes from **Avinode**, | + | |
- | + | ||
- | **The process is quite simple:** | + | |
- | + | ||
- | - Edit Avinode request in ' | + | |
- | - Click on {{: | + | |
- | - You will get redirected to Avinode search engine where the list of available offers by different sellers will be displayed | + | |
- | + | ||
- | + | ||
- | < | + | |
- | + | ||
- | ------ | + | |
- | ==== Accepting subcharters from Avinode ==== | + | |
- | [{{ : | + | |
- | + | ||
- | It is possible to accept subcharter flights requested in Avinode. | + | |
- | + | ||
- | Firstly, you need to make sure that **'Add subcharter quotes automatically' | + | |
- | + | ||
- | The process is as follows: | + | |
- | + | ||
- | * Client requests a trip which shows in Leon on the ' | + | |
- | * If we, as an operator, are unable to perform the request with our own fleet, we can search for subcharter in Avinode (by clicking on 'FIND SUBCHARTER/ | + | |
- | * The request is sent 3rd party operators in Avinode | + | |
- | * Once the 3rd party operator confirms the request in Avinode, then this request appears in Leon as a subcharter | + | |
- | + | ||
- | Subcharted requested from Avinode will contain the details of the aircraft as well as aircraft photos, as long as available in Avinode. | + | |
- | + | ||
- | The subcharter edit window is divided into 2 tabs: | + | |
- | + | ||
- | * **BASIC** | + | |
- | * **MESSAGES** | + | |
- | + | ||
- | + | ||
- | === MESSAGES === | + | |
- | [{{ : | + | |
- | + | ||
- | In this tab, it is possible to reply to the Broker in Avinode or directly to the Operator. | + | |
- | + | ||
- | In order to reply directly to the Operator, Operator' | + | |
- | + | ||
- | If it is available in Avinode, Leon will import it to **Contact email** box in ' | + | |
- | + | ||
- | In order to reply to Operator press **REPLY TO OPERATOR** link and select: | + | |
- | + | ||
- | * **AVINODE** | + | |
- | * **EMAIL** | + | |
- | + | ||
- | Currently, replies from all the brokers will display under one ' | + | |
- | + | ||
- | ===Leon identifier in Avinode === | + | |
- | [{{ : | + | |
- | It is possible to set up messaging in the way where the name of the person sending the reply to Avinode will show correctly in Avinode. | + | |
- | + | ||
- | In order to set it up, edit personal profile (click on your name in the top-right corner of Leon) and go to the tab 'User Settings' | + | |
- | + | ||
- | In the field ' | + | |
- | This will connect both systems, so the next time you reply to the Avinode message, your Avinode name will appear. | ||
- | ----- | ||
===== Managing the RFQ ===== | ===== Managing the RFQ ===== | ||
- | [{{ : | + | [{{ : |
The main page of the **RFQ - Request For Quote** page is divided into **2** sections, which show all details in a transparent way: | The main page of the **RFQ - Request For Quote** page is divided into **2** sections, which show all details in a transparent way: | ||
Line 430: | Line 252: | ||
==== Details of the Request ==== | ==== Details of the Request ==== | ||
- | Top-left part of the page shows details, such as: | + | The top-left part of the page shows details, such as: |
* **Marketplace** - Avinode, HelloJet, Victor or Leon. | * **Marketplace** - Avinode, HelloJet, Victor or Leon. | ||
- | * **Quote request ID** - ID of the quote generated by Marketplace. | + | * **Quote request ID** - ID of the quote generated by Marketplace. |
- | * **Requested by** - client' | + | * **Show changes history** - displays the history of changes within the quote |
+ | * **EDIT REQUEST** - option to edit the initially requested schedule and apply changes so that they reflect in the main Requests/ | ||
+ | * **Requested by** - client or company name. | ||
* **Representative** - client' | * **Representative** - client' | ||
* **Assignee** - a person who is designated to work the quote. | * **Assignee** - a person who is designated to work the quote. | ||
Line 444: | Line 268: | ||
[{{ : | [{{ : | ||
- | It is now possible to **add a new client** (a company or a person) straight from **REQUESTS/ | + | It is now possible to **add a new client** (a company or a person) straight from the **REQUESTS/ |
When creating a new quote, click a **+** icon right next to the ' | When creating a new quote, click a **+** icon right next to the ' | ||
Line 462: | Line 286: | ||
{{: | {{: | ||
- | The changes applied in 'Edit requester/ | + | The changes applied in the 'Edit requester/ |
---- | ---- | ||
Line 470: | Line 294: | ||
It is possible to assign requests to bases. | It is possible to assign requests to bases. | ||
- | This feature only applies to operators that have more that one base. For the operators with **one base only** this functionality will not apply. | + | This feature only applies to operators that have more than one base. For the operators with **one base only** this functionality will not apply. |
Bases can be defined in [[leon: | Bases can be defined in [[leon: | ||
Line 485: | Line 309: | ||
Once this request is edited by a **user with base assigned** then this request will get assigned to the user base automatically. | Once this request is edited by a **user with base assigned** then this request will get assigned to the user base automatically. | ||
- | It is also possible to assign or change original base, including base initially assigned to a Client, **without having to assign a specific user**. | + | It is also possible to assign or change |
[{{ : | [{{ : | ||
The ' | The ' | ||
- | If you select a particular base in the operator selection dropdown (top-right corner of Leon), the Requests/ | + | If you select a particular base in the operator selection dropdown (top-right corner of Leon), the Requests/ |
< | < | ||
-------- | -------- | ||
- | ==== Flight time calculations from Aviapages | + | ==== 'EDIT REQUEST' |
- | It is possible to download | + | It is possible to edit the originally requested schedule and reflect it in the main ' |
- | Flight time calculations from Aviapages | + | **EDIT REQUEST** button is available by the quote number in the quote details section: |
+ | |||
+ | {{: | ||
+ | [{{ : | ||
+ | Clicking on the 'EDIT REQUEST' | ||
- | In order to use this functionality, | + | In the 'Edit quote request' |
- | __**How it works**__ | + | The changes can include: |
- | [{{ :leon: | + | |
- | [{{ : | + | |
- | After the integration is activated, | + | * schedule - routing as well as the number of PAX |
+ | * aircraft - change of aircraft or additional aircraft | ||
+ | * option to include positioning legs | ||
+ | [{{ : | ||
+ | **After the changes are performed and applied (' | ||
- | Clicking on {{: | + | * **IGNORE** |
+ | * **APPLY** | ||
+ | | ||
+ | * **SHOW CHANGES** - displays the history of changes of the request | ||
- | Additionally, | + | The screenshot on the right presents the usage of the **REGENERATE** button. |
- | Clicking on {{: | + | If **the changes are applied** to the schedule, the quotation |
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | < | + | |
+ | Additionally, | ||
+ | {{: | ||
+ | -------- | ||
- | --------------- | ||
==== Auto update of the booked trips ==== | ==== Auto update of the booked trips ==== | ||
[{{ : | [{{ : | ||
- | It is possible to set up an **auto-update** of the booked trips. Once a quote' | + | It is possible to set up an **auto-update** of the booked trips. Once a quote' |
- | **AUTO UPDATE** | + | **AUTO-UPDATE** |
- | To make it work, mark a checkbox **Auto update booked trips in Requests/ | + | To make it work, mark a checkbox **Auto-update booked trips in Requests/ |
**MANUAL UPDATE** | **MANUAL UPDATE** | ||
- | If an auto update is switched off and the booked quote' | + | If an auto-update is switched off and the booked quote' |
- | Click it and select **Update trip using (aircraft reg number) quote** and Leon will update the trip's schedule in OPS panel. | + | Click it and select **Update trip using (aircraft reg number) quote** and Leon will update the trip's schedule in the OPS panel. |
{{: | {{: | ||
Line 548: | Line 376: | ||
In this section, you can find available options for the quote status change. Changing statuses are correlated with actions, among which are: sending emails, documents, etc... | In this section, you can find available options for the quote status change. Changing statuses are correlated with actions, among which are: sending emails, documents, etc... | ||
+ | |||
+ | The statuses available in the request edit section can be **customized** in the [[leon: | ||
- NEW - highlighted when adding a new quote into Requests/ | - NEW - highlighted when adding a new quote into Requests/ | ||
- | - QUOTE - send a quote proposition details with Flight Quotation document - when dealing with Avinode quote, clicking SEND means accepting the quote. | + | - QUOTE - send a quote proposition details with Flight Quotation document - when dealing with Avinode quote, clicking SEND means accepting the quote. It is possible to send **the same message** for all quotes by marking a checkbox **Send same message to all quotes**. |
- | - OPTION - click to add the trip to OPS page with the status ' | + | - OPTION - click to add the trip to the OPS page with the status ' |
- | - CONTRACT - shows a new window for Charter Agreement document sending. | + | - CONTRACT - shows a new window for Charter Agreement document sending. |
- | - BOOK - click to add the trip to OPS page with the status ' | + | - BOOK - click to add the trip to the OPS page with the status ' |
- | - BRIEF - shows a window for Flight Brief document sending. | + | - BRIEF - shows a window for Flight Brief document sending. |
- INVOICE - an option to send an invoice to the client. | - INVOICE - an option to send an invoice to the client. | ||
- DONE - closing the transaction. | - DONE - closing the transaction. | ||
- | - REJECT - reject the client' | + | - REJECT - reject the client' |
- | [{{ : | + | - CANCEL - this status is very similar to the ' |
+ | [{{ : | ||
Independent from the status change actions you can always print sales document or send it via email using options: | Independent from the status change actions you can always print sales document or send it via email using options: | ||
{{: | {{: | ||
- | - DOCUMENT - Flight Quotation, Charter Agreement | + | - DOCUMENT - Flight Quotation, Charter Agreement, Flight Brief, and already created Invoices. |
- SEND EMAIL - for sending sales documents via email or sending custom emails. | - SEND EMAIL - for sending sales documents via email or sending custom emails. | ||
< | < | ||
- | ---- | + | [{{ : |
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | It is possible to set up a **due date and time** when creating a non-confirmed trip (an ' | ||
+ | |||
+ | The Option can be created in 2 ways: | ||
+ | |||
+ | * by selecting the ' | ||
+ | * by selecting the ' | ||
+ | |||
+ | Both ' | ||
+ | |||
+ | Once the email is sent and the date and time are selected, it gives the indication of by when the Client should reply. If there is no reply, both the request, as well as the booked option, are cancelled. | ||
+ | |||
+ | __**EXAMPLE**__ | ||
+ | |||
+ | The email is sent with the date as per the screenshot on the right. | ||
+ | |||
+ | If the response is not received by the date and time the following happens: | ||
+ | |||
+ | **1. Quote status changes from ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **2. The notion booked in OPS is also deleted** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | Additionally, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | It is possible to set up the **due date by default**. More information can be found in the [[leon: | ||
+ | |||
+ | ------- | ||
==== Itinerary details ==== | ==== Itinerary details ==== | ||
Line 580: | Line 448: | ||
It is possible to change the **Currency** and Leon will recalculate the price in the new currency. The new currency will also apply to the quote' | It is possible to change the **Currency** and Leon will recalculate the price in the new currency. The new currency will also apply to the quote' | ||
- | If there is no **aircraft performance data** inserted in ' | + | If there is a discontinuity in the itinerary, and the warning is marked in the 3-dot filter, it is indicated with {{: |
+ | |||
+ | If there is no **aircraft performance data** inserted in the ' | ||
{{: | {{: | ||
- | It is also possible to schedule a **Fuel Stop**. More information in the subsection below. | + | It is also possible to schedule a **Fuel Stop**. More information |
- | [{{ : | + | [{{ : |
[{{ : | [{{ : | ||
In the top-right corner of the itinerary, there is a {{: | In the top-right corner of the itinerary, there is a {{: | ||
* **Commercial** - selection whether the quote should be for a commercial flight or not by using the switch | * **Commercial** - selection whether the quote should be for a commercial flight or not by using the switch | ||
- | * **Show changes history** - access to the history of changes of the quote. More information in section below | + | * **Show changes history** - access to the history of changes of the quote. More information in the section below |
* **Delete** - option to delete the itinerary | * **Delete** - option to delete the itinerary | ||
* **Warnings** - selecting the types of warnings in the feasibility check window | * **Warnings** - selecting the types of warnings in the feasibility check window | ||
Line 606: | Line 476: | ||
Selected elements of the feasibility check filter will be remembered per user. | Selected elements of the feasibility check filter will be remembered per user. | ||
+ | |||
+ | When sending documents to the client, Leon also shows red triangle (alerting feasibility check) next to the ' | ||
+ | |||
+ | {{: | ||
You can also **remove** the leg from the itinerary by clicking on {{: | You can also **remove** the leg from the itinerary by clicking on {{: | ||
Line 613: | Line 487: | ||
{{: | {{: | ||
- | Below trip details you can find **3** options to: | + | Below trip details you can find **4** options to: |
- {{: | - {{: | ||
- | - {{: | + | - {{: |
+ | - {{: | ||
+ | - {{: | ||
- | If you click on this icon Leon will display **Feasibility check information** window which provides specific warning details as presented in the screenshot - all warnings, cautions and notices enabled in Leon, plus the information if on the day of the quote (departure day) no **minimum crew** (defined in the aircraft profile for cockpit & cabin) have been assigned with the **Duty on the aircraft** (registration or type - depending on Duties Setup configuration). Also, a caution **FTL close to limit for Cockpit/ | + | If you click on this icon Leon will display |
=== Modifying timeframes in schedule === | === Modifying timeframes in schedule === | ||
Line 629: | Line 505: | ||
**2**. When changing **Flight time** of the flight, Leon will change **Block time** automatically and will keep initial Taxi times. Leon will ask whether to change ' | **2**. When changing **Flight time** of the flight, Leon will change **Block time** automatically and will keep initial Taxi times. Leon will ask whether to change ' | ||
- | **3**. When changing **STA**, Leon will change the **STD** by the block time value. The same scenario applies to change of the **STD**. Leon will **NOT** require validation. | + | **3**. When changing **STA**, Leon will change the **STD** by the block time value. The same scenario applies to the change of the **STD**. Leon will **NOT** require validation. |
**4**. When changing **ADEP/ | **4**. When changing **ADEP/ | ||
+ | |||
+ | --------- | ||
+ | ==== Updating booked quote ==== | ||
+ | |||
+ | We have **improved** a functionality of __updating quote' | ||
+ | |||
+ | If the quote' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When selecting {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When selecting {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | **Changes will reflect in the main Requests/ | ||
+ | |||
+ | ------------------------------ | ||
+ | ==== Rejecting the quote ==== | ||
+ | [{{ : | ||
+ | [{{ : | ||
+ | |||
+ | Request can be **rejected** in three ways: | ||
+ | |||
+ | * from the pop-up menu in the main ' | ||
+ | * from the edit quote window using the ' | ||
+ | * from Avinode, if the request comes from Avinode. It can be rejected either by the buyer or the seller directly in Avinode | ||
+ | |||
+ | When rejecting the request, the pop-up window will appear. Depending on whether the request has a quote or it hasn' | ||
+ | |||
+ | It is also possible to select the party that is rejecting the request (**Canceled by**) as well as the reason for the rejection (**Reason**) | ||
+ | |||
+ | The following **rejection options** are available: | ||
+ | |||
+ | 1. Canceled by **Seller** reasons: | ||
+ | * No availability | ||
+ | * Inoperable Airport | ||
+ | * Aircraft performance | ||
+ | * Out of the Company Range | ||
+ | * Other | ||
+ | |||
+ | 2. Canceled by **Buyer** reasons: | ||
+ | * Buyer reasons | ||
+ | * Force majeure | ||
+ | * Other | ||
+ | |||
+ | Quote **rejected in Leon** will appear in Avinode as **Declined**. | ||
+ | |||
+ | Quote **rejected in Avinode** will appear in Leon as **Rejected** with the relevant ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Additionally, | ||
--------- | --------- | ||
Line 650: | Line 583: | ||
- Click on a 'Fuel stop' icon | - Click on a 'Fuel stop' icon | ||
- | - In the ' | + | - In the ' |
- | - Select one of the airports from the list and click ' | + | - Select one of the airports from the list and click the ' |
- | - The 'Fuel stop' leg is added to the itinerary. The fuel stop airport is indicated by frame. The feasibility check can be performed by clicking on {{: | + | - The 'Fuel stop' leg is added to the itinerary. The fuel stop airport is indicated by frame. The feasibility check can be performed by clicking on {{: |
{{: | {{: | ||
Line 663: | Line 596: | ||
**In order to assign a Handling Agent to a Client,** you need to: | **In order to assign a Handling Agent to a Client,** you need to: | ||
- | * Edit the Client in Sales module. An agent can also be assigned while adding a new Client in the Sales module | + | * Edit the Client in the Sales module. An agent can also be assigned while adding a new Client in the Sales module |
- | * Select the Agent(s) in the **' | + | * Select the Agent(s) in the **' |
* Airport ICAO/ | * Airport ICAO/ | ||
* Handler Name | * Handler Name | ||
Line 683: | Line 616: | ||
Additionally, | Additionally, | ||
- | If the Handler is changed in the OPS Checklist, updating the trip from Sales panel will affect the Handler selection. | + | If the Handler is changed in the OPS Checklist, updating the trip from the Sales panel will affect the Handler selection. |
- | If the trip is added in OPS section and the Client is assigned in the TRIP tab, the Client' | + | If the trip is added in the OPS section and the Client is assigned in the TRIP tab, the Client' |
< | < | ||
Line 692: | Line 625: | ||
==== Invoice ==== | ==== Invoice ==== | ||
- | [{{ : | + | [{{ : |
[{{ : | [{{ : | ||
Line 704: | Line 637: | ||
{{: | {{: | ||
- | Once it's all set up, edit the Quote that has already been **BOOKED**, click button **INVOICE** and Leon will show a pop-up window where you can select an appropriate Email and Invoice template. Then Invoice details & items should be defined with their Net price and VAT. Below the items list, Leon will show **Total price**. | + | The recipient address for invoice documents is automatically selected in the following order: |
+ | - Default recipient e-mail address set in General Settings / Sales | ||
+ | - Representative' | ||
+ | - Requester' | ||
+ | - Representative' | ||
+ | - Requester' | ||
+ | |||
+ | Once it's all set up, edit the Quote that has already been **BOOKED**, click the button **INVOICE** and Leon will show a pop-up window where you can select an appropriate Email and Invoice template. Then Invoice details & items should be defined with their Net price and VAT. Below the items list, Leon will show **Total price**. | ||
**Three fields with dates** are available in the document: | **Three fields with dates** are available in the document: | ||
Line 712: | Line 652: | ||
* **Due Date** - due date of the payment. If this field is left blank, Leon will assume 10 days in advance from the ' | * **Due Date** - due date of the payment. If this field is left blank, Leon will assume 10 days in advance from the ' | ||
- | Click **DOWNLOAD** icon to preview the template before sending it out. | + | |
+ | Click the **DOWNLOAD** icon to preview the template before sending it out. | ||
{{: | {{: | ||
- | It is very useful when after sending the invoice to the Client, the amount of the quotation changes, be it due to change in the number of items or the calculated price of the items. | + | It is very useful when after sending the invoice to the Client, the amount of the quotation changes, be it due to a change in the number of items or the calculated price of the items. |
In such a scenario, it is sufficient to go to the ' | In such a scenario, it is sufficient to go to the ' | ||
Line 722: | Line 663: | ||
< | < | ||
- | If the quote is created for more than one aircraft, Invoice pop-up will allow to switch between tails and define Invoice items accordingly. | + | If the quote is created for more than one aircraft, |
{{: | {{: | ||
Line 730: | Line 671: | ||
**TAX** | **TAX** | ||
- | It is possible to set up a **default VAT rate** in the main Quotation view in the ' | + | It is possible to set up a **default VAT rate per Country** in the **' |
+ | |||
+ | **Apart from the above mentioned**, | ||
{{: | {{: | ||
Line 748: | Line 691: | ||
**The VAT rate, gross amount, as well as taxes amounts, are included in the available data for Sales documents (including Suncharter) in ' | **The VAT rate, gross amount, as well as taxes amounts, are included in the available data for Sales documents (including Suncharter) in ' | ||
- | Once the invoice has been paid, you can edit the quote again and in Invoice tab mark a checkbox **Paid** - then you can generate a report (in a scope ' | + | Once the invoice has been paid, you can edit the quote again and in the Invoice tab mark a checkbox **Paid** - then you can generate a report (in a scope ' |
- | ---- | + | It is possible to **close** the Invoice (checkbox ' |
+ | |||
+ | It is also possible to exclude TAX from showing on the Invoice by unmarking a checkbox **Include taxes in trip price on invoices** in a section General Settings > Sales Module. | ||
+ | -------------- | ||
+ | |||
+ | === ' | ||
+ | |||
+ | It is now possible to set up a **default 'Due date' | ||
+ | |||
+ | The setting consists of **2 fields**: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | - Input with the number of days | ||
+ | - Dropdown with the following options: | ||
+ | * **after issue date** - number of days after the invoice issue date | ||
+ | * **after invoice date** - number of days after the invoice date | ||
+ | * **before flight** - number of days before the first flight within the request | ||
+ | |||
+ | As you can see in the example below, the Invoice due date was set to 7 days after the invoice date: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | < | ||
+ | |||
+ | -------------- | ||
+ | |||
+ | === Tagging Invoice === | ||
+ | [{{ : | ||
+ | |||
+ | It is possible to **tag an Invoice**. | ||
+ | |||
+ | The option is available on the ' | ||
+ | |||
+ | In order to **add a new tag** you need to: | ||
+ | |||
+ | - Insert the new tag name in the ' | ||
+ | - Click on the colour square and select the colour using the available palette | ||
+ | - Sending / Saving without sending the Invoice will save the tag | ||
+ | |||
+ | Once the tag is saved, it will be available in the dropdown list in the ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Tags added to the Invoice are available in the Report Wizard > Scope ' | ||
+ | |||
+ | ---------------- | ||
==== Recharge Invoice & Credit Note ==== | ==== Recharge Invoice & Credit Note ==== | ||
Line 756: | Line 745: | ||
* **Recharge Invoice** - sent if there was an extra cost for a service not included in an initial trip cost, i.e. deicing or limo. | * **Recharge Invoice** - sent if there was an extra cost for a service not included in an initial trip cost, i.e. deicing or limo. | ||
- | * **Credit Note** - sent to a client, if some part of the agreed cost should be returned to client, due to i.e. cancellation of the flight by a client or if the cost of the trip turned out to be lower than the agreed cost and the difference must be returned to a client. | + | * **Credit Note** - sent to a client, if some part of the agreed cost should be returned to the client, due to i.e. cancellation of the flight by a client or if the cost of the trip turned out to be lower than the agreed cost and the difference must be returned to a client. |
---- | ---- | ||
Line 764: | Line 753: | ||
{{: | {{: | ||
[{{ : | [{{ : | ||
- | Second | + | The second |
{{: | {{: | ||
Line 776: | Line 765: | ||
==== Owner approval ==== | ==== Owner approval ==== | ||
- | **Owner approval** is the functionality | + | **Owner approval** is the functionality |
In order to activate the functionality, | In order to activate the functionality, | ||
Line 784: | Line 773: | ||
[{{ : | [{{ : | ||
- | Once the option is activated, **APPROVAL** button will appear amongst the status buttons. | + | Once the option is activated, |
{{: | {{: | ||
Line 795: | Line 784: | ||
------- | ------- | ||
+ | ==== Flight Brief ==== | ||
+ | [{{ : | ||
+ | |||
+ | ' | ||
+ | |||
+ | When sending the Flight Brief document it is possible to **select the flights** that should be presented on the document. | ||
+ | |||
+ | This is quite useful when the trip consists of numerous flights spread across a number of days and separated by longer periods. | ||
+ | |||
+ | It allows sending the document to the client in stages, based on the itinerary, and include the flights nearest to each other. | ||
+ | |||
+ | As presented in the screenshot on the right, the trip consists of 5 flights between 28th May and 11th June. The functionality allows selecting the nearest flights (28th May) and sending these initially. The remaining ones can be selected and sent closer to the planned departure date. | ||
+ | |||
+ | **Ferry flights** are not presented on the list. | ||
+ | |||
+ | ----------- | ||
==== Quote pricing ==== | ==== Quote pricing ==== | ||
- | [{{ : | + | [{{ : |
There are **2** ways of creating price valuation: manual entering price for an entire quote and using a detailed price list for an aircraft and airports. | There are **2** ways of creating price valuation: manual entering price for an entire quote and using a detailed price list for an aircraft and airports. | ||
Line 803: | Line 808: | ||
You can manually enter the **Price** in the field next to **Aircraft**. This field is only editable when the detailed price list is not added. | You can manually enter the **Price** in the field next to **Aircraft**. This field is only editable when the detailed price list is not added. | ||
- | Be advised that when the quote is imported from Avinode and an aircraft is configured in a section FEES, detailed price list shows automatically and an original **Avinode** price is always displayed next to it and can not be changed. | + | Be advised that when the quote is imported from Avinode and an aircraft is configured in a section FEES, a detailed price list shows automatically and an original **Avinode** price is always displayed next to it and can not be changed. |
- | Once you have added Request & Itinerary details and selected the aircraft, | + | Once you have added Request & Itinerary details and selected the aircraft, |
+ | |||
+ | {{: | ||
In this section you can manage the price list: | In this section you can manage the price list: | ||
- | - Add new item | + | - Add a new item |
- Change the item's name | - Change the item's name | ||
- Change items quantity and their price. | - Change items quantity and their price. | ||
Line 817: | Line 824: | ||
Each item is **editable**, | Each item is **editable**, | ||
- | When you click on the arrow next to the price, Leon will show both airports. The default fee will show for ADEP only but you can still add fees to ADES manually. Another option is adding **new fee** available in the drop-down box below the items. When changing fees manually, Leon shows **Total price** simultaneously changed at the same time. Hover the mouse over the Total price amount to see **the price per hour of the flight**. | + | When you click on the arrow next to the price, Leon will show both airports. The default fee will show for ADEP only but you can still add fees to ADES manually. Another option is adding |
{{: | {{: | ||
Line 831: | Line 838: | ||
There are **2 buttons** available to manage the quote: | There are **2 buttons** available to manage the quote: | ||
- | * **RECALCULATE** | + | * **RECALCULATE** |
- | * **CHANGE PRICING** - should be used when you'd like to recalculate on a different ' | + | * **CHANGE PRICING** - should be used when you'd like to recalculate on a different ' |
=== ' | === ' | ||
Line 861: | Line 868: | ||
* ' | * ' | ||
- | Additionally, | + | Additionally, |
As you can see in the screenshot on the right, Leon recalculates based on the new itinerary but also includes the updated aircraft fees. | As you can see in the screenshot on the right, Leon recalculates based on the new itinerary but also includes the updated aircraft fees. | ||
Line 885: | Line 892: | ||
* ' | * ' | ||
- | Additionally, | + | Additionally, |
As you can see in the screenshot on the right, only the value of the ' | As you can see in the screenshot on the right, only the value of the ' | ||
Line 911: | Line 918: | ||
If you tick the {{: | If you tick the {{: | ||
------ | ------ | ||
+ | ==== Changing the price in ' | ||
- | ==== The Margin ==== | + | It is possible to amend the price in the ' |
+ | There are **two possible scenarios** when the final price is updated: | ||
- | It is important to see the **Margin** between trip-related revenues | + | |
+ | * **Price reduced** | ||
- | When creating an aircraft pricing in Leon, it is now possible to define the **Cost** for each fee of the aircraft. | + | If the price increase/reduction are within |
- | + | ||
- | In a section Sales > Fees, when creating aircraft fees (or editing existing fees), Leon shows a separate column **Cost**. Here you can insert a value of the cost. The currency of the cost is the same as the price' | + | |
- | + | ||
- | [{{ : | + | |
- | {{: | + | |
- | + | ||
- | Once the cost values have been added, in the quote' | + | |
- | + | ||
- | If the cost is **lower** than the price, Leon will show the margin value in green. If the cost is **higher** than the price, Leon will show it in red. Hover the mouse over the margin' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ------ | + | |
- | + | ||
- | + | ||
- | ==== CO2 Emission ==== | + | |
- | + | ||
- | More and more clients travelling by airplanes want to know how much **CO2** will be emitted during the flight they have bought. Meeting this request we have added an option to **show CO2 emission on sales documents**: | + | |
- | + | ||
- | In order to have CO2 on sales documents, follow below steps. | + | |
- | + | ||
- | - In the tab OPS of an aircraft profile (section Settings > Fleet) select **Fuel type** (JETA1 or AVGAS). | + | |
- | - In the tab PERFORMANCE add **Average fuel consumption**. | + | |
- | - In a section **Documents Manager** edit one of the sales documents and add CO2 on it by using an item ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | < | + | |
- | + | ||
- | + | ||
- | ---- | + | |
- | ==== Request changes history ==== | + | |
- | + | ||
- | It is now possible to access **Changes History** of the Quote in the quote's edition panel, under the 3-dot filter. | + | |
- | + | ||
- | {{: | + | |
- | [{{ : | + | |
- | Clicking on **'Show changes history' | + | |
- | + | ||
- | * aircraft changes | + | |
- | * quotation status changes | + | |
- | * price changes | + | |
- | * trip schedule changes | + | |
- | + | ||
- | In the changes history window, Leon shows a 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. | + | |
- | + | ||
- | When you click on the changed detail, Leon highlights previous entrances of the same detail. | + | |
- | ------ | + | |
- | ===== Taxes ===== | + | |
- | + | ||
- | ====Italian Luxury Tax==== | + | |
- | + | ||
- | This is an additional item available only in the Requests/Quotes section. | + | |
- | + | ||
- | 'Italian Luxury Tax' | + | |
- | + | ||
- | The values | + | |
- | + | ||
- | * €10 per PAX for the flights shorter than 100km | + | |
- | * €100 per PAX for the flights between 100km and 1500km | + | |
- | * €200 per PAX for the flights longer than 1500km | + | |
- | + | ||
- | [{{ : | + | |
- | __**Example**__ | + | |
- | + | ||
- | Trip consists of 3 flights to and from Italy. | + | |
- | + | ||
- | Each flight has 3PAX added. | + | |
- | + | ||
- | The distance between the airports on 2 of the flights is greater than 1500km and on the 3rd flight - 800km | + | |
- | + | ||
- | In such case the **calculation is as follow**: | + | |
- | + | ||
- | **(6PAX x €200) + (3PAX x €100) = €1500** | + | |
- | + | ||
- | + | ||
- | ==== UK Air Passenger Duty Tax ==== | + | |
- | + | ||
- | **UK Air Passenger Duty Tax** (UK APD) applies to trips departing from the UK or Northern Ireland and is based on below criteria: | + | |
- | + | ||
- | * **Destination bands** | + | |
- | * **Rate types** | + | |
- | * **Number of PAX** | + | |
- | + | ||
- | All the rates and allowances of the UK APD can be found [[https:// | + | |
- | + | ||
- | **The calculations are performed for the whole trip.** | + | |
- | + | ||
- | __**1. Destination bands**__ | + | |
- | + | ||
- | The rates vary depending on whether the trip starts in the UK or Northern Ireland and the airport of destination. | + | |
- | + | ||
- | **The trips starting in the Scottish Highlands and Island are excluded from UK APD.** | + | |
- | + | ||
- | There are 2 destination bands: | + | |
- | + | ||
- | * **Band ‘A’** where the distance from London/ | + | |
- | * **Band ‘B’** where the distance from London/ | + | |
- | + | ||
- | Additionally, | + | |
- | + | ||
- | The countries falling into each ' | + | |
- | + | ||
- | [{{ : | + | |
- | __**2. Rate types**__ | + | |
- | + | ||
- | There are **3 rates** of duty for each destination band depending on the class of travel: | + | |
- | + | ||
- | * **Reduced rate** | + | |
- | * **Standard rate** | + | |
- | * **Higher rate** | + | |
- | + | ||
- | The rate type can be assigned to the aircraft in the Settings > Fleet > Sales tab of the aircraft edit. | + | |
- | + | ||
- | + | ||
- | __**3. Number of PAX**__ | + | |
- | + | ||
- | Duty is charged on each passenger at the rate for the place where their journey ends (their final destination). | + | |
- | + | ||
- | There are **2 stages** od UKAPD tax calculations. | + | |
- | + | ||
- | The **first stage** is based on a simplified calculation and only takes into consideration | + | |
- | + | ||
- | Once the **PAX names** are added, Leon moves on to the **second stage** of UKAPD tax calculation. Based on the PAX names on each flight, Leon compares the names and calculates the tax based on the actual PAX and their final destination. | + | |
- | + | ||
- | The **recalculation is required**. In order to perform the recalculation, | + | |
- | + | ||
- | * Add PAX names to required flights and delete the quote | + | |
- | * Press 'SAVE & BACK' button | + | |
- | * Edit the request again | + | |
- | * Add new quote calculation | + | |
- | * Save the request with the new quote | + | |
- | + | ||
- | If the journey is made of one flight the final destination is where that flight ends. If the journey includes more than one flight, and the flights are connected, the final destination is where the last flight ends and is not followed by a connected flight. | + | |
- | + | ||
- | < | + | |
- | + | ||
- | [{{ : | + | |
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
- | < | + | Below, there are examples presented for each of the scenarios. |
- | <span style=" | + | |
- | </ | + | |
- | Please see screenshot on the right. | ||
- | |||
- | The trip consists of 3 flights starts in EGGW and finishes in KJFK. | ||
- | |||
- | The aircraft is of higher rate type. | ||
- | |||
- | In the simplified version of the calculations, | ||
- | |||
- | **The calculation is as follow:** | ||
- | |||
- | **3 x GBP78 = GBP234** | ||
- | |||
- | Explanation: | ||
- | |||
- | * rates for the UK based airport of departure | ||
- | * airport of arrival for 3PAX is in Band A (Russian Federation) and higher class aircraft - the rate of GBP78 per PAX | ||
- | |||
- | |||
- | [{{ : | ||
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
- | + | [{{ : | |
- | Please see screenshot on the right. | + | |
- | + | ||
- | The trip consists of 3 flights starts in EGGW and finishes in KJFK. | + | |
- | + | ||
- | The trip starts with 3PAX and finishes with 2 of the initial PAX on the last flight. 1PAX finishes at EPWA. | + | |
- | + | ||
- | The aircraft is of higher rate type. | + | |
- | + | ||
- | In such case the **calculation is as follow:** | + | |
- | + | ||
- | **2 x GBP515 + 1 x GBP78 = GBP1108** | + | |
- | + | ||
- | Explanation: | + | |
- | + | ||
- | * rates for the UK based airport of departure | + | |
- | * airport of arrival for 2PAX is in Band B (USA) and higher class aircraft - the rate of GBP515 per PAX | + | |
- | * airport of arrival for 1PAX is in Band A (Poland) and higher class aircraft - the rate of GBP78 per PAX | + | |
- | * 2PAX arrived at the destination in Band B and 1PAX at destination in Band A | + | |
- | + | ||
- | [{{ : | + | |
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
+ | In the screenshot on the right-hand side, the price is increased from €8600 to €9000. | ||
- | < | + | The 'Extra Fee' element |
- | <span style=" | + | |
- | </ | + | |
- | + | ||
- | Please see screenshot on the right. | + | |
- | + | ||
- | The trip consists | + | |
- | + | ||
- | The aircraft is of higher rate type. | + | |
- | + | ||
- | In the simplified version of the calculations, | + | |
- | + | ||
- | **The calculation is as follow:** | + | |
- | + | ||
- | **2 x GBP78 = GBP156** | + | |
- | + | ||
- | Explanation: | + | |
- | + | ||
- | * rates for Northern Ireland based airport of departure | + | |
- | * airport of arrival for 2PAX is in Band A (Russian Federation) and higher class aircraft - the rate of GBP78 per PAX | + | |
- | [{{ : | + | [{{ : |
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
- | Please see screenshot on the right. | + | In the screenshot on the right-hand side, the price is increased from €8600 to €9100. |
- | The trip consists | + | Because the increase is higher (€600) than the value of the ' |
- | The trip starts with 2PAX and finishes with 3PAX on the last 2 flights. | ||
- | The aircraft is of higher rate type. | ||
- | In such case the **calculation is as follow:** | ||
- | |||
- | **2 x GBP515 = GBP1030** | ||
- | |||
- | Explanation: | ||
- | |||
- | * rates for Northern Ireland based airport of departure | ||
- | * airport of arrival is in Band B (USA) and higher class aircraft - the rate of GBP515 per PAX for indirect flights | ||
- | * 3PAX arrived at the destination: | ||
- | |||
- | ------------- | ||
- | ==== German Aviation Tax ==== | ||
- | |||
- | German Aviation Tax is a departure tax on commercial air transport. | ||
- | |||
- | It is levied on the carriage, from an aerodrome situated in Germany, of passengers on board fixed-wing and rotary-wing aircraft. | ||
- | |||
- | **The amount** due per passenger depends on the distance of the biggest commercial airport in the country of destination from Germany' | ||
- | |||
- | __**Destination bands**__ | ||
- | |||
- | **The destination airports** are divided into 3 bands: | ||
- | |||
- | * **Group A** - listed in [[https:// | ||
- | * **Group B** - listed in [[https:// | ||
- | * **Group C** - countries listed in neither Annex 1 nor Annex 2. These charged at **€41.49** per PAX. This will change to **€59.43** from April 2020 | ||
- | |||
- | Similarly to UK APD TAX, there are **2 stages** od GAT calculations. | ||
- | |||
- | The **first stage** is based on a simplified calculation and only takes into consideration the number of PAX leaving Germany and the airport of destination. Based on this data the simplified tax amount is calculated. | ||
- | |||
- | Once the **PAX names** are added, Leon moves on to the **second stage** of GAT calculation. Based on the PAX names on each flight, Leon compares the names and calculates the tax based on the actual PAX and their final destination. | ||
- | |||
- | The **recalculation is required**. In order to perform the recalculation, | ||
- | |||
- | * Add PAX names to required flights and delete the quote | ||
- | * Press 'SAVE & BACK' button | ||
- | * Edit the request again | ||
- | * Add new quote calculation | ||
- | * Save the request with the new quote | ||
- | |||
- | |||
- | < | ||
- | |||
- | **More information** about the ' | ||
- | |||
- | [{{ : | ||
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
+ | [{{ : | ||
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
- | Please see screenshot on the right. | + | In the screenshot on the right-hand side, the price is reduced from €8600 to €8300. |
- | + | ||
- | The trip consists of 3 flights starts in EDDB and finishes in DNMM. | + | |
- | + | ||
- | In the simplified version of the calculations, we only consider | + | |
- | + | ||
- | **The calculation | + | |
- | + | ||
- | **3 x €7.38 = €22.14** | + | |
- | + | ||
- | Explanation: | + | |
- | * rates for the Germany | + | The ' |
- | * airport of arrival for 3PAX is in Band A (Russian Federation) - the rate of €7.38 per PAX | + | |
- | [{{ : | + | [{{ : |
< | < | ||
- | <span style=" | + | <span style=" |
</ | </ | ||
- | See screenshot on the right. | + | In the screenshot on the right-hand side, the price is reduced from €9100 to €8500. |
- | The trip starts with 3PAX in EDDB. The same PAX continues from UUWW and the trip finishes with 2of the PAX on the last flight. 1PAX finishes at UUWW. | + | Because |
- | In such case the **calculation is as follow:** | + | -------------------- |
- | **2 x €41.49 + 1 x €7.38 | + | ==== The Margin ==== |
- | Explanation: | ||
- | * 2PAX calculated at 'Group C' band (€41.49) because Thailand (VTBS) | + | It is important to see the **Margin** between trip-related revenues and the cost - this way the operator knows whether to increase fees or cut the cost. |
- | | + | |
- | [{{ : | + | When creating an aircraft pricing in Leon, it is now possible to define the **Cost** for each fee of the aircraft. |
- | < | + | |
- | <span style=" | + | |
- | </ | + | |
- | <html> | + | In a section Sales > Fees, when creating aircraft fees (or editing existing fees), Leon shows a separate column **Cost**. Here you can insert a value of the cost. The currency of the cost is the same as the price' |
- | <span style=" | + | |
- | </ | + | |
- | Please see screenshot on the right. | + | [{{ : |
+ | {{: | ||
- | The trip consists of 3 flights starts in EDDB and finishes in EDDB. | + | Once the cost values have been added, on the quote' |
- | In the simplified version of the calculations, we only consider | + | If the cost is **lower** than the price, Leon will show the margin value in green. If the cost is **higher** than the price, Leon will show it in red. Hover the mouse over the margin' |
- | **The calculation is as follow:** | + | {{:leon: |
- | **2 x 3 x €7.38 = €44.28** | ||
- | Explanation: | ||
- | * rates for the Germany based airport of departure | ||
- | * there are 2 flights departing from German airports (EDDB and EDDW) with 3PAX each (6 PAX in total) | ||
- | * airports of arrival for all 6PAX are in Band A (Germany and Russian Federation) - the rate of €7.38 per PAX | ||
- | [{{ : | ||
- | < | ||
- | <span style=" | ||
- | </ | ||
- | See screenshot on the right. | ||
- | The trip starts with 3PAX in EDDB. The same 3PAX continues from EDDW to UUWW. 1PAX leaves in UUWW and 2PAX carry on to EDDB. | ||
- | In such case the **calculation is as follow:** | ||
- | **3 x €7.38 = €22.14** | ||
- | Explanation: | ||
- | * rates for the Germany based airport of departure | ||
- | * 3PAX calculated at 'Group A' band (€7.38) because the same 3PAX from EDDB carried on from EDDW on the second flight | ||
+ | ------ | ||
- | [{{ : | ||
- | < | ||
- | <span style=" | ||
- | </ | ||
+ | ==== CO2 Emission ==== | ||
- | Please see screenshot on the right. | + | More and more clients travelling by aeroplanes want to know how much **CO2** will be emitted during |
- | The trip consists of 2 flights starts in EDDB and finishes in VTBS. | + | In order to have CO2 on sales documents, follow the below steps. |
- | The trip starts with 0PAX and finishes with 2PAX on the last flight. | + | - In the tab OPS of an aircraft profile (section Settings > Fleet) select **Fuel type** (JETA1 or AVGAS). |
+ | - In the tab PERFORMANCE add **Average fuel consumption**. | ||
+ | - In a section **Documents Manager** edit one of the sales documents | ||
- | **In this case, calculations based on PAX number and actual PAX will be the same.** | + | {{: |
- | The **TAX calculated** will amount to **€0**, because there are no PAX departing from the German airport. | + | <box>**To calculate |
- | --------- | + | |
- | ==== Swedish Aviation Tax ==== | ||
- | **Swedish Aviation Tax** is levied on commercial flights carrying passengers and departing from a Swedish airport. | + | ---- |
+ | ==== Request changes history ==== | ||
- | The **tax rate** depends on the passenger’s final destination. Flights to countries listed under Appendix 1 of the Aviation Tax Act pay 61 SEK per passenger (6 € or $ 7.50). Passengers travelling to countries listed under Appendix 2 are charged 255 SEK (25 € or $ 31.50). For destination countries neither listed | + | It is now possible to access |
- | **More information** about the Swedish Aviation Tax including liability, obligations and the list of the countries included in Appendix 1 and Appendix 2 can be found [[https://www.fccaviation.com/ | + | {{:leon: |
+ | [{{ : | ||
+ | Clicking on the **' | ||
- | [{{ : | + | * aircraft changes |
+ | * quotation status changes | ||
+ | * price changes | ||
+ | * trip schedule changes | ||
- | < | + | In the changes history window, Leon shows a 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. |
- | <span style=" | + | |
- | </ | + | |
- | < | + | When you click on the changed detail, Leon highlights previous entrances of the same detail. |
- | <span style=" | + | |
- | </ | + | |
- | Please see screenshot on the right. | + | === Changes requested via App === |
+ | [{{ : | ||
+ | Changes can also be requested in the Owner App. | ||
- | The trip consists of 3 flights starts in EPWA and finishes | + | If a change is requested |
- | In the simplified version of the calculations, | + | * **IGNORE** - does not apply any changes |
+ | * **APPLY** - the update will be accepted and reflected in the updated itinerary | ||
+ | * **CREATE NEW** - new itinerary on the same aircraft will be created within | ||
+ | * **SHOW CHANGES' | ||
- | There are 2PAX assigned | + | Additionally, |
- | **The calculation is as follow:** | + | {{:leon: |
- | **2 x SEK122 + 1 x SEK255 = SEK377** | + | ------ |
- | Explanation: | + | ===== Additional options ===== |
- | * rates for the Sweden based airport | + | The right side of the page shows additional panels, which will allow seeing the quote in the Calendar, view the route on the Map, view & managing Sales checklist items and seeing OPS checklist items, managing PAX, add Notes or Comments. |
- | * 2PAX departing from ESGG to ESSA - band 1 (2 x SEK122) | + | |
- | * 1PAX departing from ESSA to HECA - band 2 (1 x SEK255) | + | |
- | [{{ : | + | ==== CALENDAR ==== |
- | < | + | |
- | <span style=" | + | |
- | </ | + | |
- | See screenshot on the right. | + | [{{ : |
- | The trip starts with 1PAX in EPWA. For the tax calculations, | + | The quote itinerary/trip is imposed on actually confirmed schedule of the selected aircraft. The information displayed shows departure-arrival times & ADEP-ADES. |
- | In such case the **calculation is as follow:** | + | {{:leon: |
- | **1 x SEK255 = SEK255** | + | The current day is always displayed in light-blue and the thin, green line shows actual |
- | Explanation: | + | {{:leon: |
- | * 1PAX starting at EPWA is not included in the calculation due to being considered as a transfer PAX (PAX that arrives | + | The view shows the 7-days period. Click ← or → buttons |
- | | + | |
- | <box>**IMPORTANT! It only applies | + | **Aircraft selection dropdown** allows you to view a different |
- | ------------- | + | **Switching the aircraft registration in the ' |
- | ==== Austrian Air Transport Levy ==== | + | |
- | **Austrian Air Transport Levy (ATL)** is a **departure tax** charged on the carriage, from Austrian airports, of passengers on board aircraft with an **authorized weight of more than 2,000 Kg (4,400 lbs)**. | + | ---- |
+ | ==== SUMMARY ==== | ||
- | Both commercial and non-commercial business aircraft operators are subject to this tax. | ||
- | The **amount due** per passenger depends on the geographical distance | + | The **' |
- | Starting from 1 September 2020, passengers will be taxed **the following rates**: | + | The list is displayed in the same order as the order of the quotes. |
- | * 30 € (GCD < 350km) | + | The highlighted line corresponds to the quote that is currently previewed in the request edit section. |
- | * 12 € (GCD > 350km) | + | |
+ | The tab contains the following columns: | ||
+ | [{{ : | ||
+ | * **No** - order number corresponding to the quote number | ||
+ | * **Aircraft** - Aircraft type and registration assigned to a specific quote | ||
+ | * **Seller** - Name of the airline selling the trip. It could be either the name of the subcharter company or 'Own fleet' label, in case of quoting on own aircraft | ||
+ | * **Operator status** - reply status received from Avinode (< | ||
+ | * **Offered** - displays the information whether the specific quote was included in an email sent to the Client using the ' | ||
+ | * **Operator price** - applies to ' | ||
+ | * **Margin** - this is either the subcharter operator margin or the margin indicated in the quote performed using the 'Cost & Margin' | ||
+ | * **Price** - total quoted price | ||
- | If you carry out **domestic flights in Austria** and are liable to pay VAT for the transport of passengers, the effective tax rate will be slightly lower because VAT can be deducted from air transport levy. | + | === POSSIBILITY TO SORT QUOTES IN 3 DIFFERENT WAYS === |
- | **Under this scenario, the tax rates per passenger are:** | + | [{{ : |
+ | It will be possible to sort the quotes in 6 different ways, using the field available in the Summary tab. | ||
- | * 26.55 € (GCD < 350km) | + | |
- | * 10.62 € (GCD > 350km) | + | - Booked |
+ | - Offered, ordered by the ascending price | ||
+ | - The rest, ordered by the ascending price | ||
+ | | ||
+ | - **Price ascending** - the quotes will be ordered by the price, ascending | ||
+ | - **Operator price ascending** - the sorting method works similarly to the 'Price ascending' | ||
+ | - **Operator status, price** - in this case, the order is following | ||
+ | - Own fleet | ||
+ | - Accepted | ||
+ | - Unanswered | ||
+ | - Rejected | ||
+ | - **Operator status, operator price** - the sorting method works similarly to the ' | ||
- | There are also the following **exemptions** from the ATL due: | + | -------------- |
+ | ==== MAP ==== | ||
- | | + | The **Map** shows the **route** |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
+ | The selected flight shows the arrow in green. Ferry leg shows the arrow in the light blue. | ||
- | More information about Austrian Air Tax Levy can be found [[https:// | + | {{:leon: |
+ | ---- | ||
- | < | + | ==== CHECKLIST ==== |
- | <span style=" | + | |
- | </ | + | |
- | < | + | [{{ : |
- | <span style=" | + | |
- | </ | + | |
- | [{{ : | + | |
- | Please see screenshot on the right. | ||
- | The MTOW of the aircraft is more than 2000kg (4400lbs). | + | **Sales checklist** on the trips/ |
- | The trip consists of 5 flights, 3 of which start in Austria. | + | **Sales checklist** becomes available when the request is created, whether it is a regular fleet or subcharter. |
- | In the simplified version of the calculations, | + | It is possible to add extra items to the checklist by using the **'ADD ITEM' |
- | **The calculation | + | It is possible to service the Sales Checklist from the OPS view if the trip/ |
- | **3 x €12 + 3 x €26.55 = €115.65** | + | **OPS Checklist** appears only once the trip is booked. |
- | Explanation: | + | It is also not possible to service the OPS checklist in the Requests/ |
- | * MTOW of an aircraft is more than 2000kg | + | Elements |
- | * 3 PAX are flying internationally and the GCD is more than 350NM (GCD) - **3 x €12** | + | |
- | * 3 PAX are flying domestically and the distance is less than 350NM (GCD) - **3 x €26, | + | |
- | * Flight | + | |
+ | ----------- | ||
- | < | + | ==== PAX ==== |
- | <span style=" | + | |
- | </ | + | |
- | [{{ : | + | |
- | Please see screenshot | + | [{{ : |
+ | In this tab, you can add passengers | ||
- | The MTOW of the aircraft is more than 2000kg (4400lbs). | + | You can choose either |
- | The trip consists of 5 flights, 3 of which start in Austria. | + | In order to activate the PAX boxes in the " |
- | PAX names are assigned to the flights. | + | {{: |
- | **The calculation | + | The PAX selection dropdown |
- | **3 x €26.55 = €79.65** | + | |
+ | * **OTHER** - other passengers available in the phonebook | ||
- | Explanation: | + | In this section, it is also possible to add new passengers to the Phonebook or edit existing passengers that are already in the database. The process is exactly the same as described [[leon:pax|here]]. |
- | | + | **If the trip is added in the Requests/ |
- | | + | |
- | * Flight from LOWL to EPWA is a positioning leg (FERRY) therefore not included in the calculations | + | |
- | < | + | If a passenger has more than 1 passport you can select which one should be used as default (in PAX profile mark a checkbox ' |
- | <span style=" | + | __This feature is for PAX selected from Leon database |
- | </ | + | |
- | [{{ : | + | |
- | Please see screenshot | + | [{{ : |
+ | It is possible to change the order of passengers by drag& | ||
- | The MTOW of the aircraft is more than 2000kg (4400lbs). | + | Simply click on the name line you'd like to move, hold the left button |
- | The trip consists | + | The change |
+ | < | ||
- | **The calculation is as follow:** | + | ==== Assigning PAX to the flight by scanning Passport or a National ID ==== |
- | **3 x €12 + 3 x €26.55 = €115.65** | + | A new possibility of assigning PAX to the flight, by **scanning the passport/ |
- | Explanation: | + | In the quote' |
- | * MTOW of an aircraft is more than 2000kg | + | {{: |
- | * 3 PAX are flying internationally and the GCD is more than 350NM (GCD) - **3 x €12** | + | |
- | * 3 PAX are flying domestically and the distance is less than 350NM (GCD) but also there is over **24h gap** between EPWA-LOBT and LOBT-LOWL. This is the reason why PAX on LOBT-LOWL are subject to taxation - **3 x €26, | + | |
- | * Flight from LOWL to EPWA is a positioning leg (FERRY) therefore not included in the calculations | + | |
- | < | + | Once the scan has been uploaded, Leon will show a new window with the scan attached. In this new window, it is also possible to **select the flights, to which the person should be assigned** (' |
- | <span style=" | + | |
- | </ | + | |
- | [{{ : | + | {{: |
- | The MTOW of the aircraft | + | Almost all the details are inserted automatically apart from the Place of Birth. Gender |
- | The trip consists of 5 flights, 3 of which start in Austria. | + | To add passenger' |
- | PAX names are assigned to the flights. Domestic flight with an animal and 2PAX. | + | {{: |
- | **The calculation | + | If the quote' |
- | **1 x €12 + 2 x €26.55 = €65.10** | ||
- | Explanation: | + | ---------------------- |
+ | ==== Picking PAX from the contact list ==== | ||
- | * MTOW of an aircraft | + | It is now possible to select |
- | * 2 PAX and 1 animal are flying domestically and the distance is less than 350NM (GCD) - **2 x €26, | + | |
- | * 3 PAX are flying internationally, | + | |
- | * Flight from LOWL to EPWA is a positioning leg (FERRY) therefore not included in the calculations | + | |
- | ------------------- | + | This option allows |
- | ===== Sending contracts | + | |
- | In order to use DocuSign and be able to sign a Charter Agreement using DocuSign, you need to integrate first. | + | Click on the **PICK FROM THE CONTACT LIST** option |
- | The integration process is explained [[https:// | + | {{:leon: |
- | Once the integration is active, each user will have to connect Leon account with own account in DocuSign and then, will be able to use it. | ||
- | ==== Connecting Leon account to DocuSign | + | === ' |
- | [{{ : | + | |
- | The connection between user Leon account | + | The **Select PAX** window is divided into the following sections: |
+ | [{{ : | ||
+ | - **Legs** - allows selecting the flights upon which the action will be taken. Only flights with PAX are listed. Ferry and 0 PAX flights are omitted | ||
+ | - **Search passenger** - option to search for PAX. If the ' | ||
+ | - **Requester** - automatically selected from the quote | ||
+ | - **Available passengers** - list of PAX assigned to the Requester Company and containing the basic details (Name, DoB, Companies one is assigned to). If the requester company is not selected the list is empty. In this case ' | ||
+ | - **Selected passengers** - PAX selected in the ' | ||
+ | - **Action buttons**: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | * if there are more PAX names selected than the PAX number, the number of PAX will increase accordingly, | ||
+ | * adding further PAX to the list will not overwrite already added PAX, i.e. adding 2 new PAX to 2 already assigned PAX will increase the PAX number to 4 | ||
+ | * {{: | ||
- | In order to **connect** own account in Leon to DocuSign account, you need to: | + | ------------- |
- | - Click on ' | + | ==== OPS & CREW ==== |
- | - In 'Send document' | + | |
- | - Click on the blue ' | + | |
- | - In the pop-up window, log in to your DocuSign account | + | |
- | Once you signed in, you should see the following message: | + | [{{ :leon: |
- | **SUCCESS. Your Leon account has been connected | + | This section is to serve two purposes: |
- | This is when you can start using the integration. | + | * to provide |
+ | * to give the Sales team a quick overview of the progress of the basic dispatch elements of the booked trip performed by OPS | ||
- | ------- | + | The tab can be **activated** by switchin the privilege **' |
- | ==== Usage ==== | + | |
- | [{{ : | + | |
- | DocuSign integration works only with ' | + | Each flight within the **OPS & CREW** tab contains |
- | After connecting to DocuSign, each new ' | + | - **Handling** |
+ | - **Crew** | ||
+ | - **Overflight permits** | ||
+ | - **Slots** | ||
- | Once the draft is created, you will be able to **send** the document to DocuSign. | + | Flight times are presented in **LT**. |
- | In 'Send document' | + | The details |
- | Before sending | + | This tab is mainly designed with the **subcharter** flights in mind. |
- | [{{ : | + | |
- | * **SHOW DRAFT IN DOCUSIGN** - which will allow you to preview it in DocuSign | + | === SHARING === |
- | * **UPDATE DRAFT IN DOCUSIGN** - which will allow you to update the document if there are any changes within the request | + | |
- | Once the **'Charter Agreement' | + | [{{ : |
- | The email will also contain the link to DocuSign which will allow **reviewing the document** for the Client. | + | **SHARING** tab allows selecting the data that are to be shared with a requester of subcharter in the ' |
- | Also, the selections | + | It is possible to **select |
- | [{{ : | + | Currently, the following data can be selected: |
- | [{{ : | + | |
- | The client will be able to sign, date and stamp the document without having to print it. | + | |
- | It is possible to include the **signature tabs** in the document so to indicate, where the document should be signed. | + | |
+ | * **Crew** | ||
+ | * **Overflight Permits** | ||
+ | * **Slots** | ||
+ | [{{ : | ||
+ | Apart from the trip data, it is also possible to apply the settings to the future subcharter requester quote by selecting | ||
- | The tab icon can be included in HTML in the Documents Manager - 'Charter Agreement' | + | Once the sharing details are saved, the **Trip data sharing status** will change from 'NOT SHARED' |
- | | + | These settings can be applied |
- | | + | |
- | For example, inserting below code HTML | + | The details are selected per Client and will apply to all the trips requested by the Client. |
- | {{: | + | Once the details are selected and saved, the 'Trip data sharing status' |
- | will insert the following tab in ' | + | __**EXAMPLE**__ |
- | {{:leon: | + | To visualise the purpose of this function we can assume two operators: |
+ | * **Operator A** - requester of the subcharter | ||
+ | * **Operator B** - provider of the subcharter | ||
- | The client can click on the 'Sign' | + | **It is important to mention that in order for the 'Share' |
- | Once Client reviewed it and signed it, Client can press finish which will send a notification | + | * both operators have to use the ' |
- | {{: | + | * the trip has to be booked by the provider of the subcharter ('Operator B' |
- | ------- | ||
- | ===== Additional options ===== | ||
- | The right side of the page shows additional panels, which will allow seeing | + | If ' |
- | ==== CALENDAR ==== | + | Once the data to share is selected on a booked trip by the ' |
- | [{{ : | + | === SHARING TRIP USING LINK === |
+ | [{{ : | ||
+ | It is also possible to **share the trip details via email using link**. | ||
- | The quote itinerary/ | + | This option |
- | {{:leon: | + | Clicking on this button will open a pop-up 'Share the trip' email window in which the following sharing options are available: |
- | The current day is always displayed in light-blue and the thin, green line shows actual | + | |
+ | * **Crew** | ||
+ | * **Overflight permits** | ||
+ | * **Slots** | ||
+ | * **Ferry legs** | ||
- | {{: | + | Additionally, |
- | The view shows the 7-days period. Click ← or → buttons to move for another 7 days backwards or forward, or click TODAY to get back to the current day view. You can also switch between **UTC** & **LT**. | ||
- | **Aircraft selection dropdown** allows you to view a different aircraft activity vs the aircraft used in the RFQ. If you choose a different aircraft in the ' | + | -------- |
- | + | ||
- | **Switching the aircraft registration in the ' | + | |
- | ---- | + | |
- | + | ||
- | ==== MAP ==== | + | |
- | + | ||
- | The **Map** shows the **route** of the trip. You can navigate with the map by clicking **+** or **-** in the top-left corner. | + | |
- | + | ||
- | Selected flight shows the arrow in green. Ferry leg shows the arrow in the light-blue. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | ==== CHECKLIST ==== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | + | ||
- | **Sales checklist** on the trips/ | + | |
- | + | ||
- | **Sales checklist** becomes available when the request is created, whether it is a regular fleet or subcharter. | + | |
- | + | ||
- | It is possible to add extra items of the checklist by using **'ADD ITEM' | + | |
- | + | ||
- | It is possible to service the Sales Checklist from the OPS view if the trip/ | + | |
- | + | ||
- | **OPS Checklist** appears only once the trip is booked. | + | |
- | + | ||
- | It is also not possible to service OPS checklist in the Requests/ | + | |
- | + | ||
- | Elements of the Sales Checklist can be set by default in the [[leon: | + | |
- | + | ||
- | ----------- | + | |
- | + | ||
- | ==== PAX ==== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | In this tab, you can add passengers on a flight. | + | |
- | + | ||
- | You can choose either the PAX you already have in your Phonebook and add them in the " | + | |
- | + | ||
- | In order to activate the PAX boxes in the " | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | In this section, it is also possible to add new passengers to the Phonebook or edit existing passengers that are already in the database. The process is exactly the same as described [[leon: | + | |
- | + | ||
- | **If the trip is added in the Requests/ | + | |
- | + | ||
- | If a passenger has more than 1 passport you can select which one should be used as default (in PAX profile mark a checkbox ' | + | |
- | __This feature is for PAX selected from Leon database and not available when adding PAX from text__. | + | |
- | + | ||
- | < | + | |
- | + | ||
- | ---------------------- | + | |
==== NOTES ==== | ==== NOTES ==== | ||
Line 1656: | Line 1333: | ||
Notes added in this section can be then embedded in Sales documents as all of them have the items available in the Available data. | Notes added in this section can be then embedded in Sales documents as all of them have the items available in the Available data. | ||
- | Once the notes are added, click **SAVE** button in order to save the changes. | + | Once the notes are added, click the **SAVE** button in order to save the changes. |
- | The OPS and Sales notes will be available and can be edited both in Requests/ | + | There are the following ' |
- | **OPS Notes** are not available when the trip is not booked. | + | |
+ | * It should contain any legal regulations applying to the contract | ||
+ | * Note that applies to and can be sent to end-customer | ||
+ | * It can be inserted per quote individually, | ||
+ | * It can be set up as a default note in Settings > General Settings > ' | ||
+ | * Applies per the whole request (or trip - if the request is booked) | ||
+ | * It can be used on Sales Documents (included in the available data in the Documents Manager) | ||
+ | * **CUSTOMER NOTE** | ||
+ | * Inserted by the Sales team and can contain any important information regarding Client' | ||
+ | * Apply per the whole request (or trip - if the request is booked) | ||
+ | * It can be used on Sales Documents (included in the available data in the Documents Manager) | ||
+ | * **CANCELLATION POLICY** | ||
+ | * It should contain the Operator Cancellation policy regulations | ||
+ | * Note that applies to and can be sent to end-customer | ||
+ | * It can be inserted per quote individually, | ||
+ | * It can be set up as a default note in Settings > General Settings > ' | ||
+ | * Applies per the whole request (or trip - if the request is booked) | ||
+ | * It can be used on Sales Documents (included in the available data in the Documents Manager) | ||
+ | * **ADDITIONAL NOTE** | ||
+ | * It can include notes with any additional important information | ||
+ | * Applies per the whole request (or trip - if the request is booked) | ||
+ | * It can be used on Sales Documents (included in the available data in the Documents Manager) | ||
+ | * **SALES NOTES** | ||
+ | * Important notes by Sales Team | ||
+ | * Apply per flight on which it is inserted | ||
+ | * Once the quote is booked and the trip created, the notes can be included in the following documents: Flight Brief (Sales), Charter Agreement (Sales), Crew Tripsheet (OPS), PAX Tripsheet (OPS) | ||
+ | | ||
+ | * Inserted by the Sales team and can contain any important information regarding quoted aircraft, such as Client requirements regarding the aircraft | ||
+ | * Applies per the whole request (or trip - if the request is booked) | ||
+ | * It can be used on Sales Documents (included in the available data in the Documents Manager) | ||
+ | * **OPS NOTES** | ||
+ | * Notes are available | ||
+ | * Apply per flight on which it is inserted | ||
+ | * It can be used to communicate any issues to the OPS Team | ||
+ | * It can also be updated by OPS Team and the update will appear in the Sales Panel on the flight | ||
+ | * Once the quote is booked and the trip created, the notes can be included in the following documents: Flight Brief (Sales), Charter Agreement (Sales), Crew Tripsheet (OPS), PAX Tripsheet (OPS | ||
- | **Sales Notes** are available as soon as the request is created. | + | Additionally, |
+ | * apply to the contractual agreement between the operator performing the trip and the subcharter aircraft provider | ||
+ | * they can be inserted manually if the subcharter details are added on a subcharter aircraft in Leon, or | ||
+ | * if the subcharter is requested via Avinode, the ' | ||
+ | * it can be used on Sales Documents for subcharter (included in the available data in the Documents Manager) | ||
Line 1676: | Line 1392: | ||
* **REPLY TO CUSTOMER** - contains 2 options: | * **REPLY TO CUSTOMER** - contains 2 options: | ||
* **Avinode** - allows replying to messages and quotations sent from Avinode | * **Avinode** - allows replying to messages and quotations sent from Avinode | ||
- | * **Email** - allows sending emails and receive | + | * **Email** - allows sending emails and receiving |
=== ADD INTERNAL MESSAGE === | === ADD INTERNAL MESSAGE === | ||
Line 1704: | Line 1420: | ||
Messages inserted in **Avinode** when sending a request to Leon will also show in this section and will be highlighted green. | Messages inserted in **Avinode** when sending a request to Leon will also show in this section and will be highlighted green. | ||
- | When the request is **received from Avinode**, you can click on **REPLY TO CUSTOMER** button and the message will be sent to the Client in Avinode. | + | When the request is **received from Avinode**, you can click on the **REPLY TO CUSTOMER** button and the message will be sent to the Client in Avinode. |
- | **In Avinode**, the reply will be available in the **' | + | **In Avinode**, the reply will be available in the **' |
Once the message is added you will be able to see who added a message and what day at what time. The times presented in the messages history are in **LT**. | Once the message is added you will be able to see who added a message and what day at what time. The times presented in the messages history are in **LT**. | ||
Line 1714: | Line 1430: | ||
<span style=" | <span style=" | ||
</ | </ | ||
- | < | + | < |
This functionality allows you to send and receive emails directly into Leon and keep the track of your emails in one place. | This functionality allows you to send and receive emails directly into Leon and keep the track of your emails in one place. | ||
Line 1720: | Line 1436: | ||
Before you start using the functionality you need to: | Before you start using the functionality you need to: | ||
- | - Contact [[support@leonsoftware.com]] in order to configure generic mailbox with Leon | + | - Contact |
- | - Create additional 'Sales Panel Message' | + | - Create |
Once you have your mailbox configured, you can go to Settings > Email Templates > Other and create the 'Sales Panel Message' | Once you have your mailbox configured, you can go to Settings > Email Templates > Other and create the 'Sales Panel Message' | ||
- | **It is important that the email address provided to Leon is inserted in ' | + | **It is important that the email address provided to Leon is inserted in the ' |
[{{ : | [{{ : | ||
Once you have everything configured, you can start using the functionality: | Once you have everything configured, you can start using the functionality: | ||
Line 1734: | Line 1450: | ||
* address ' | * address ' | ||
* it is possible to attach and send files | * it is possible to attach and send files | ||
- | * files sent by the Client will be received and available to preview in ' | + | * files sent by the Client will be received and available to preview in the ' |
* new message will move the request to the top of the ' | * new message will move the request to the top of the ' | ||
* ' | * ' | ||
Line 1744: | Line 1460: | ||
------------- | ------------- | ||
- | |||
==== AIRPORT CHARGES ==== | ==== AIRPORT CHARGES ==== | ||
Line 1762: | Line 1477: | ||
- Make sure that the integration with ' | - Make sure that the integration with ' | ||
- | - Add ' | + | - Add the ' |
- | If ' | + | If the ' |
- | If the integration is **not active**, the ' | + | If the integration is **not active**, the ' |
---------------------- | ---------------------- | ||
Line 1775: | Line 1490: | ||
When you use occasionally subcharter aircraft from another operator, our panel **REQUESTS/ | When you use occasionally subcharter aircraft from another operator, our panel **REQUESTS/ | ||
- | In order to use subcharter | + | ==== New Subcharter Quote ==== |
+ | [{{ : | ||
+ | ' | ||
- | The subcharter details edit window is divided into 2 tabs: | + | * **New subcharter request** - added using 'NEW QUOTE' button on the main ' |
+ | * **' | ||
+ | * **' | ||
+ | * **Subcharter in existing request** - quote on a subcharter added to an existing request: | ||
+ | * Click on a **+** next to the last aircraft tab | ||
+ | * Select the ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The subcharter details edit window is divided into 5 tabs: | ||
* **BASIC** - contains subcharter details such as aircraft details, crew details, contact details (email and phone no.) and aircraft photos, as long as available in Avinode | * **BASIC** - contains subcharter details such as aircraft details, crew details, contact details (email and phone no.) and aircraft photos, as long as available in Avinode | ||
- | * **MESSAGES** - possibility to reply directly to the Operator email (as long as it is available in ' | + | * **MESSAGES** - possibility to reply directly to the Operator email (as long as it is available in the ' |
* **AMENITIES** - possibility to select the amenities available on the aircraft as well as the cabin basic measurements and noise levels | * **AMENITIES** - possibility to select the amenities available on the aircraft as well as the cabin basic measurements and noise levels | ||
+ | * **SERVICES** - possibility to select the suppliers of services on the flights within the request | ||
+ | * **DOCUMENTS** - possibility to upload aircraft documents | ||
=== Price === | === Price === | ||
- | [{{ : | + | [{{ : |
The ' | The ' | ||
Line 1791: | Line 1519: | ||
* **Operator price** - the amount charged by the operator (subcharter price) | * **Operator price** - the amount charged by the operator (subcharter price) | ||
- | * **Third party commission** - commission paid to the third-party broker | + | |
- | * **Margin** - income margin calculated on top of the total cost | + | |
Based on the above elements, the total price is calculated as: | Based on the above elements, the total price is calculated as: | ||
- | **Price = (' | + | |
+ | **Price = ' | ||
The total price is not editable and keeps the same currency as the price breakdown. | The total price is not editable and keeps the same currency as the price breakdown. | ||
{{: | {{: | ||
+ | |||
+ | If **VAT value** is inserted, Leon additionally will display **Gross price** value, including VAT. | ||
+ | |||
+ | **Hovering** the mouse over 'Gross price' amount will display **VAT value**. | ||
=== Basic === | === Basic === | ||
- | [{{ : | + | [{{ : |
In a subcharter ' | In a subcharter ' | ||
- | It is also possible to select **Handling agents** for Subcharters. Handlers can be selected from the drop-down list. | + | **Cancellation policy** in the subcharter details section is the policy that applies to the contractual agreement between the operator performing the trip and the subcharter aircraft provider. |
+ | |||
+ | It can be inserted manually if the subcharter details are added on a subcharter aircraft in Leon. | ||
+ | |||
+ | If the subcharter is requested via **Avinode**, | ||
+ | |||
+ | It is also possible to select **Handling agents** for Subcharters. Handlers can be selected from the drop-down list. However, if in a section General Settings > Sales Module a checkbox **Select handling agents on subcharters automatically** is unmarked, Leon will not show handlers automatically. | ||
If we already used subcharter functionality in the past, Leon will search for an aircraft that was previously used. The dropdown list will display both aircraft registration and the operator name in the format **Registration, | If we already used subcharter functionality in the past, Leon will search for an aircraft that was previously used. The dropdown list will display both aircraft registration and the operator name in the format **Registration, | ||
Line 1812: | Line 1551: | ||
Once we select the aircraft, all the data is copied from the previous request, including type, crew, aircraft details and photos. The only input that is **not copied** is the subcharter price. | Once we select the aircraft, all the data is copied from the previous request, including type, crew, aircraft details and photos. The only input that is **not copied** is the subcharter price. | ||
- | Once the subcharter quote is saved you can manage it just like a standard quote. There is one exception - you cannot physically book subcharter quote as option / confirmed flight into OPS module. However, you can still change the status to ' | + | Once the subcharter quote is saved you can manage it just like a standard quote. There is one exception - you cannot physically book subcharter quote as an option / confirmed flight into the OPS module. However, you can still change the status to ' |
You can send **Flight Quotations** containing normal and subcharter quotes. You can send subcharter **Contract** and **Flight Brief** for subchaters using documents templates which can be customized from [[leon: | You can send **Flight Quotations** containing normal and subcharter quotes. You can send subcharter **Contract** and **Flight Brief** for subchaters using documents templates which can be customized from [[leon: | ||
Line 1819: | Line 1558: | ||
[{{ : | [{{ : | ||
- | You can also upload | + | You can also upload photos of the Subcharter aircraft. |
=== Uploading photos === | === Uploading photos === | ||
- | In order to do it, click on **' | + | In order to do it, click on the **' |
A pop-up window will appear with the **' | A pop-up window will appear with the **' | ||
- | Once you selected the photos, in 'Edit pictures' | + | Once you selected the photos, in the 'Edit pictures' |
Clicking ' | Clicking ' | ||
Line 1840: | Line 1579: | ||
In this tab, it is possible to reply directly to the Operator. | In this tab, it is possible to reply directly to the Operator. | ||
- | In order to reply directly to the Operator, Operator' | + | In order to reply directly to the Operator, Operator' |
+ | |||
+ | In order to reply to Operator press **REPLY TO OPERATOR** link and select the **EMAIL** option. The operator' | ||
- | In order to reply to Operator press **REPLY TO OPERATOR** link and select **EMAIL** option. Operator' | ||
Select ' | Select ' | ||
Line 1851: | Line 1591: | ||
=== Amenities === | === Amenities === | ||
- | It is possible to add **Amenities** when creating a quote on **Subcharter** | + | It is possible to add **Amenities** when creating a quote on **Subcharter** |
* **Smoking & Wifi** - mark checkboxes to enable them. | * **Smoking & Wifi** - mark checkboxes to enable them. | ||
- | * **Wifi type** - select between: Internat via Satcom, KA band, KU band, SBB (Swift Broadband) and Iridium. | + | * **Wifi type** - select between Internat via Satcom, KA band, KU band, SBB (Swift Broadband) and Iridium. |
- | * **Cabin details** - width, height, | + | * **Cabin details** - width, height, |
- | * **Baggage capacity** - add number of items. | + | * **Baggage capacity** - add a number of items. |
Line 1865: | Line 1605: | ||
Leon will also show ' | Leon will also show ' | ||
+ | ------------ | ||
+ | === Services === | ||
+ | |||
+ | In this tab, it is possible to select and overview the suppliers of the services on the flights within the request. | ||
+ | |||
+ | The services included are: | ||
+ | |||
+ | * **Handling ADEP** and **Handling ADES** | ||
+ | * **Catering** | ||
+ | * **PAX Transport ADEP** and **PAX Transport ADES** | ||
+ | |||
+ | |||
+ | The providers of the services have to be selected manually. | ||
+ | |||
+ | ---------------- | ||
+ | === Documents === | ||
+ | |||
+ | It is possible to upload the documents to the subcharter aircraft. | ||
+ | |||
+ | These could be the documents provided by the subcharter aircraft operator. | ||
+ | [{{ : | ||
+ | In order to add the new documents, the following steps are required for each document: | ||
+ | |||
+ | - Click on the **UPLOAD FILES** button and select the file to be uploaded | ||
+ | - The fields to insert the document details will appear: | ||
+ | * **Name** - Name of the document will be automatically populated from the uploaded file. It can be changed/ | ||
+ | * **Issue date** - possibility to insert the date of issue | ||
+ | * **Expiry date** - possibility to insert the date of expiry | ||
+ | - Click o **SAVE** button at the bottom of the page to save uploaded details | ||
+ | |||
+ | Once the documents are uploaded, **additional actions** can be performed: | ||
+ | |||
+ | * {{: | ||
+ | * {{: | ||
+ | * {{: | ||
+ | |||
+ | < | ||
+ | |||
+ | ------ | ||
+ | ==== SCHEDULE UPDATE ==== | ||
+ | |||
+ | The requested schedule can be updated using the **EDIT REQUEST** button located next to the ' | ||
+ | [{{ : | ||
+ | After the changes are performed in the 'EDIT REQUEST' | ||
+ | |||
+ | * **IGNORE** - does not apply any changes | ||
+ | * **APPLY** - the update will be accepted and reflected in the updated itinerary | ||
+ | * **CREATE NEW** - new itinerary on the same aircraft will be created within the same request (the second tab with the updated itinerary) | ||
+ | * **SHOW CHANGES** - displays the history of changes of the request | ||
+ | Once the changes are applied, they will reflect in the main ' | ||
+ | ----------------- |