This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
leon:mx-fleet [2017/10/31 07:57] bartek [CAM] |
leon:mx-fleet [2019/04/17 13:03] bartek [Oil Consumption] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== MX Fleet ====== | + | ====== MX Fleet ======= |
Line 47: | Line 47: | ||
- | [{{ :leon:mx-fleet:cam main screen.png?150|CAM data main screen}}] | + | [{{ :leon:mx-fleet:CAM3.png?150|CAM data main screen}}] |
Section '**Airframe**' defines data for total TAH & TAC of the aircraft (without splitting on engines). That data is also displayed in main Fleet screen, column 'Airframe'. | Section '**Airframe**' defines data for total TAH & TAC of the aircraft (without splitting on engines). That data is also displayed in main Fleet screen, column 'Airframe'. | ||
Line 61: | Line 61: | ||
When you add a new flight on that particular aircraft, 'Airframe' TAH & TAC will change as well as TAH & TAC for each separate engine. To view it, hover the mouse over the icon {{:leon:icons:silnik.png?20|}} in Settings > Fleet section, and you will see exact information in the pop-up window (see example below). | When you add a new flight on that particular aircraft, 'Airframe' TAH & TAC will change as well as TAH & TAC for each separate engine. To view it, hover the mouse over the icon {{:leon:icons:silnik.png?20|}} in Settings > Fleet section, and you will see exact information in the pop-up window (see example below). | ||
+ | **Warnings** will help to trigger CAM warnings in Edit Flight or when adding the Flight depending on the values inserted in **Flight hours** and **Flight cycles** fields. | ||
**APU** | **APU** | ||
- | You can also add seperate data for '**APU**' (Aircraft Power Unit), however, APU hours and cycles **do not** get automatically increased from the journey log entries (like engines). Here you can input initial APU value and the date when the system should start counting it from. This is a cummulative value, not hours per single flight. With APU, Leon just **stores** the latest value you provide here, which should be updated every time you have the new one. | + | You can also add separate data for '**APU**' (Aircraft Power Unit), however, APU hours and cycles **do not** get automatically increased from the journey log entries (like engines). Here you can input initial APU value and the date when the system should start counting it from. This is a cumulative value, not hours per single flight. With APU, Leon just **stores** the latest value you provide here, which should be updated every time you have the new one. |
- | **Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be summary value (start APU + sector one). | + | **Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be the summary value (start APU + sector one). |
If **APU** Hours input in [[leon:journey-log|Journey Log]] are lower than the value from previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: | If **APU** Hours input in [[leon:journey-log|Journey Log]] are lower than the value from previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: | ||
Line 75: | Line 75: | ||
</html>. | </html>. | ||
+ | ------------------------- | ||
===== Oil Consumption ===== | ===== Oil Consumption ===== | ||
- | [{{ :leon:mx-fleet:CAM - Oil Consumption.png?200|CAM - fleet oil consumption }}] | + | [{{ :leon:mx-fleet:CAM3.png?200|CAM - fleet 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. | 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. | ||
Line 96: | Line 96: | ||
<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 </box> | <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 </box> | ||
- | [{{ :leon:mx-fleet:Oil in JL.png?200|Oil consumption input to Journey Log}}] | ||
* **Journey Log input** | * **Journey Log input** | ||
Line 116: | Line 115: | ||
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. | 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. | + | |
- | [{{ :leon:mx-fleet:storage.png?360|Reminder Service Activation Screen}}] | + | |
- | + | ||
- | To activate the functionality you need to go to [[leon:flight-editing|Flight editing]] section. At the bottom of the screen you will see Storage Requirements Reminder Service section. | + | |
- | Ticking the "Enable checkbox" will activate the facility as well as activate "Reminder" boxes in CAM tab of an edited aircraft. | + | |
- | + | ||
- | In "Remainder period (days from SR event)" you define how many days before Storage Requirement you want to receive a notification email. You can input a number of days after commas. | + | |
- | + | ||
- | In "Remainder e-mail recipients" you input emails of people who should receive reminders. It is possible to input number of emails separated by commas. | + | |
- | + | ||
- | The final step is to go to **CAM** tab of edited aircraft and input number of days in "Reminder" box in the part you require storage for. | + | |
- | + | ||
- | * **EXAMPLE** | + | |
- | + | ||
- | We input value 3 (for 3 days) in "Remainder period (days from SR event)" in Admin > Operator settings. | + | |
- | We input value 5 (for 5 days) for one of parts in "Reminder" in CAM section of Fleet for 1 particular aircraft. | + | |
- | + | ||
- | 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. | + | |