This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:fleet [2016/01/21 09:38] rafal [Edit Aircraft Data] |
leon:fleet [2023/10/06 18:55] (current) rafal |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Fleet ====== | ====== Fleet ====== | ||
- | Managing the fleet in Leon is easy and handy. | + | This section is considered, along with the 'Fleet' and the ' |
+ | In order to have access to all three abovementioned sections, the **Admin - System Administrator** privilege has to be set to EDIT in the [[leon: | ||
- | {{: | + | The following sections |
- | + | ||
- | + | ||
- | You can also see Airframe information. TAH and TAC values | + | |
- | + | ||
- | When you hover the mouse over the {{: | + | |
- | + | ||
- | If the aircraft is highlighted blue it means that it is excluded from billing. This is subject to Terms and conditions, and aggreement with Leon Software Ltd. | + | |
- | ===== Edit Aircraft Data ===== | + | |
- | [{{ : | + | |
- | + | ||
- | To add a new aircraft you need to enter 4 **mandatory** details in 'Add new aircraft' | + | |
- | + | ||
- | * **Aircraft type** - simply enter the 1st letter of the type and Leon will display a drop-down list of all aircraft types available | + | |
- | + | ||
- | * **Short name** - once you have added aircraft type, its 'Short name' will appear automatically. | + | |
- | + | ||
- | * **Registration** - add your aircraft reg number. | + | |
- | + | ||
- | * **Colour** - by clicking on the colour field, you can choose the one that will represent a particular aircraft. If not chosen, default colour (grey) will be assigned. | + | |
- | + | ||
- | The other fields can be filled out **optionally**, | + | |
- | + | ||
- | * **Default flight number** - it would show up in the 'Edit flight' | + | |
- | + | ||
- | * **Increase flight number** - when this option is turned on, if adding a new flight within one trip, the new flight number will be **increased by one** to the last added leg. I.e. 1st leg's number is ABC001. That means when you add a new flight, its number will be ABC002. The next one would be ABC003 and so on. | + | |
- | + | ||
- | * **MTOW** - ' | + | |
- | + | ||
- | * **Aircraft deleted** - when **Aircraft** is marked as **deleted**, | + | |
- | + | ||
- | * **Minimum cabin/ | + | |
- | + | ||
- | * **RF** - Rest Facility with 3 options available: **S** - Suitable, **A** - Adequate, **N** - None. RF set up here will automatically assigned to the aircraft when adding a flight. | + | |
- | + | ||
- | * **CAM Data** - fields "FH/FC exceed warning" | + | |
- | + | ||
- | * **Performance fields** - ' | + | |
- | + | ||
- | * **Minimum Ground Time** - once it is set, when you add a new trip and the difference between STA of the last leg and STD of the new leg is less than ' | + | |
- | + | ||
- | * **Aircraft speeds** - here you can insert the ' | + | |
- | + | ||
- | * **Aircraft brochure** - here you can upload aircraft brochure (i.e. aircraft inside view photos etc) which then are automatically sent with quotation documents, such as: Flight Brief, Charter Contract and Flight Quotation. You can upload 1 file of maximum of 5MB in PDF format. | + | |
- | + | ||
- | * **Notes** - here you can add information or procedures related to a specific aircraft, such as: preffered handling agents or personal contacts. All information inserted into this field will be visible in 'Legs Info' section, in the top-right corner. If the checkbox below the field is ticked, this information will also show on te Trip Sheet. | + | |
- | + | ||
- | * **Billing info** - address from this section will be displayed in Handling Requests as Billing Address and it will override information from Admin > Operator | + | |
- | + | ||
- | ===== Aircraft docs ====== | + | |
- | + | ||
- | In this section you can see all the documents assigned to the aircraft - for more information go [[leon: | + | |
- | + | ||
- | + | ||
- | ===== MVT emails ===== | + | |
- | + | ||
- | This section allows you to enable and set up [[leon: | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ===== CAM ===== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | Here you can define such values for each aircraft, | + | |
- | + | ||
- | * **Start date** - the date of the first flight. | + | |
- | * **Start TAH** - total number of accumulated hours. | + | |
- | * **Start TAC** - total number of accumulated cycles. | + | |
- | + | ||
- | Section ' | + | |
- | + | ||
- | __Leon calculates TAH & TAC data from 00:00 of each particular day__. So if i.e. you have set start TAH = 100:00, start TAC = 50, start date as 27-11 and on that day there are 2 legs flown - when selecting 27-11 in the filter, in **Fleet** section, Leon will show TAH = 104:00 and TAC = 52 | + | |
- | + | ||
- | Because both TAH & TAC values can be __different for different engines__, you can specify exact data for each of four engines. | + | |
- | + | ||
- | Enter each engine' | + | |
- | + | ||
- | When you add a new flight on that particular aircraft, ' | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | **APU** | + | |
- | + | ||
- | You can also add seperate data for ' | + | |
- | + | ||
- | If **APU** Hours input in [[leon: | + | |
- | < | + | |
- | <span style=" | + | |
- | </ | + | |
- | ---- | + | |
- | + | ||
- | ==== Oil Consumption ==== | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | It is possible to monitor **oil consumption** per engine and per APU. You can define how many quarters of oil (in decimal numbers) have been used on a particular flight - a field **Oil uplift** in Journey Log has to be filled in for this purpose. | + | |
- | + | ||
- | Based on manufacturer configuration and oil uplift entered in ' | + | |
- | + | ||
- | * **Oil report period** | + | |
- | + | ||
- | Go to section **Fleet** main screen, edit an aircraft and enter tab **CAM**. Insert engines numbers to make other fields editable and add appropriate data. Do the same with **APU** data. | + | |
- | + | ||
- | In a field **Oil report period** add in full hours **window** which is used to calculate average oil consumption per engine. This value is **specified by engine manufacturer**. The oil field will set the **time window** analysis. | + | |
- | + | ||
- | If, for example, APU is set for **50** it means that for each window time of 50 flight hours an analysis should be done. | + | |
- | + | ||
- | The system also takes into consideration an offset value of **10 %** off the inserted amount of flight hours. So if the value input into the **Oil report period** is 50, Leon will start showing data in the report itself from 45 (10% of 50 = 5). | + | |
- | + | ||
- | <box> IMPORTANT - the number of flight hours you input does NOT mean a series of sequential blocks of hours, it is a sliding window of hours </ | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | * **Journey Log input** | + | |
- | + | ||
- | In [[leon: | + | |
- | + | ||
- | In your Journey Log you will get a new field **Oil uplift** where you can add oil consumption data for engines and APU (see sreenshot). | + | |
- | + | ||
- | Make sure the configuration has been done in **Fleet** section before you enter data to ' | + | |
- | + | ||
- | * **Average oil consumption report** | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | Once data is added to the **Journey Log** and there is enough flights with journey logs filled in (with oil used data), you can view data in the [[leon: | + | |
- | + | ||
- | You can see an example below: for first several flights there is no oil usage data because for this particular aircraft the **Oil report period** is set as **50**. That means, that there has to be a block of flights with at least 45:00 flight hours (as 10% offset off the value 50 hours is taken). | + | |
- | + | ||
- | In the column **Oil uplift** you can see number of quarts inserted for each engine (taken from Journey Log). Then from the flight performed on 12-05-2015 you can see the **average oil consumption** based on the **block of flights** with total flight hours of at least 45. | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | ====Storage requirements reminder service==== | + | |
- | + | ||
- | Storage requirements reminder is a feature that **sends email notifications** shortly before engine parts need storage procedures. | + | |
- | + | ||
- | To start using the feature, you need to **enable** it first. | + | |
- | [{{ : | + | |
- | + | ||
- | Go to [[leon: | + | |
- | Ticking the " | + | |
- | + | ||
- | In " | + | |
- | + | ||
- | In " | + | |
- | + | ||
- | The final step is to go to **CAM** tab of edited aircraft and input number of days in " | + | |
- | + | ||
- | * **EXAMPLE** | + | |
- | + | ||
- | We input value 3 (for 3 days) in " | + | |
- | We input value 5 (for 5 days) for one of parts in " | + | |
- | + | ||
- | If this aircraft has a flight scheduled on day 1, the Storage requirement will fall on day 6 (SR). In this case Storage requirement reminder email will be sent on day 3 as it is 3 days before SR. | + | |
- | + | ||
- | Reminder email **will not be sent** in 2 cases: | + | |
- | * If a flight is scheduled before Storage Requirement day for this particular aircraft, or | + | |
- | * If there is a maintenance scheduled before Storage Requirement day for this particular aircraft. | + | |
+ | * [[leon: | ||
+ | * [[leon: | ||
+ | * [[leon: | ||
+ | * [[leon: | ||
+ | * [[leon: | ||
+ | ---------------- |