Differences

This shows you the differences between two versions of the page.

--- leon:mx-fleet [2020/02/06 12:47]
bartek [MX Fleet]
+++ leon:mx-fleet [2023/02/09 17:36] (current)
rafal [Documents]
@@ Line 1: / Line 1: @@
 ====== MX Fleet =======
+[{{ :leon:mx-fleet:mx_fleet_new.png?200|MX > Fleet - the general view on aircraft}}]
-In this panel Leon shows all aircraft along with their **general details**, such as: Type, Registration, Default flight number, MTOW, Capacity, Status and Base. There are also displayed **TAH** & **TAC** for airframe and engines (hidden under the wheel icon).
+In this panel Leon shows all aircraft along with their **general details**, such as: Type, Registration, Default flight number, MTOW, Capacity, Status and Base. There are also displayed **TAH** & **TAC** for airframe and engines.
-The filter allows you to view flights with/without Journey Log inserted, or only with Journey Log. It is also possible to see TAH value in **decimal**.
+The filter is located at the top of the view and allows to select the following:
-[{{ :leon:mx-fleet:tah_decimal_off.png?200|TAH in minutes }}]
+  * Aircraft type
-[{{ :leon:mx-fleet:tah_decimal_on.png?200|TAH in decimal }}]
+  * Status
+  * ACMI
+  * TAH/TAC Date
+  * TAH/TAC Source Flights
+[{{ :leon:mx-fleet:mx_fleet_camo_decimals.png?200|TAH in minutes }}]
 Leon converts values into decimal with a **pattern**:
@@ Line 29: / Line 35: @@
 ===== Documents =====
+[{{ :leon:mx-fleet:edit-docs.png?200|'Documents' section}}]
-[{{ :leon:mx-fleet:general-view.png?200|MX > Fleet - the general view on aircraft}}]
 Here you can see **Fleet documents** assigned to the particular registration. You can add documents **details** (number, date of issue, expiry date, notes) as well as add **scan** of the document (pdf max. of 12MB).
@@ Line 39: / Line 44: @@
 ===== CAM =====
-<box>It is possible to integrate Leon with **CAMP**. Leon exports aircraft **TAH & TAC** (Total Aircraft Hours & Cycles) as well as **APU** hours (if updated in Journey Log in Leon). CAMP integration works one way only. It means that data updated in Leon updates data in CAMP, but data updated at CAMP's end does not update data in Leon. </box>
 Here you can define such values for aircraft airframe and engines, as:
@@ Line 74: / Line 78: @@
 **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:fw-jl|Journey Log]] are lower than the value from the previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning:
 <html>
 <span style="color:red;font-size:100%;">APU hours too low. APU has been entered on dd-mm-yyyy as hh:mm</span>
 </html>.
+------------------------
+==== Next maintenance due ====
+[{{ :leon:mx-fleet:nmd_-_limits.png?300|Next maintenance due limits}}]
+In the **Limits** subsection, it is possible to insert the limits for the next maintenance.
+This subsection contains 3 fields:
+  * **TAH** - TAH limit of the next required maintenance
+  * **TAC** - TAC limit of the next required maintenance
+  * **Date** - date of the next required maintenance
+Based on the values inserted in the abovementioned fields, Leon will check planned and performed flights against the limits, as per below:
+  * if all fields are empty, the limits aren't changed
+  * if the 'Date' field is empty, Leon will assume January 2032 as the due date
+  * if the 'TAH' or/and 'TAC' fields are filled in, the limits are included in the next maintenance due check for CAMO Limits in OPS (regardless of the date being selected or left empty):
+In addition, the 'Next maintenance due' limits will overwrite 'Schedule Maintenance' limits for the aircraft in the CAMO Limits in OPS if the 'Next maintenance due' limits are lower than the limits inserted in 'Scheduled Maintenance'.
+[{{ :leon:mx-fleet:nmd_-_scheduled_mx_limits.png?300|Limits in Scheduled MX}}]
+__**EXAMPLE**__
+Based on the first screen, the date of the limits is set to 01-12-2022 with the TAH value set to 4835:00 and the TAC value set to 2343.
+The scheduled maintenance is planned for 29-11-2022 with the higher limits of TAH value set to 4850:00 and TAC value set to 2350.
+Calculated TAH/TAC limits on 24-11-2022 are as per below:
+{{:leon:mx-fleet:nmd_-_tah-tac_limits.png?nolink|}}
+When adding the flight on 24-11-2022 and considering the dates and limits set in the Fleet and Scheduled Maintenance, Leon will generate the CAMO warning, **in this case, based on the limits from the CAM tab in the MX > Fleet section**:
+{{:leon:mx-fleet:nmd_-_warning_in_ops.png?nolink|}}
+The calculations are based on more restrictive limits from 29-11-2022, as per below:
+  * **TAH** - 4875:27 - 40:27 = 4835:00
+  * **TAC** - 2346 - 3 = 2343
 -------------------------
@@ Line 103: / Line 146: @@
   * **Journey Log input**
-In [[leon:operator-settings|Settings]] > **Flight Editing** mark a checkbox **Oil used** in section 'Show in Journey Log'.
+In [[leon:flight-editing|Flight editing]] section mark a checkbox **Oil used** in section 'Show in Journey Log'.
 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).

Leonsoftware Wiki

User Tools

Site Tools

Differences

Page Tools