Leonsoftware Wiki

User Tools

Site Tools

You are here: start » leon » mx-fleet
leon:mx-fleet

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
leon:mx-fleet [2017/10/31 07:57]
bartek [CAM] 		leon:mx-fleet [2020/02/06 12:47]
bartek [MX Fleet]
Line 1: Line 1:
-===== MX Fleet ======+====== MX Fleet =======
  
  
-[{{ :leon:mx-fleet:general-view.png?200|MX > Fleet - the general view on aircraft}}] 
  
-The difference between this view and the one available from [[leon:fleet|Settings]] is that here you can see all your aircraft (including not used or deleted, if you change status), but you can't add a new aircraft, which can only be done in section Settings > [[leon:fleet|Fleet]]+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).
  
-**Aircraft status** - to change, it go to Settings > Fleet and open drop-down box **Status** at the bottom of the screen.+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**.
  
-By clicking on any tail you have access to **2** tabs.+[{{ :leon:mx-fleet:tah_decimal_off.png?200|TAH in minutes }}] 
 +[{{ :leon:mx-fleet:tah_decimal_on.png?200|TAH in decimal }}] 
 + 
 +Leon converts values into decimal with a **pattern**: 
 +  * 00-03:59 min = 0.0 
 +  * 04-09:59 min = 0.1 
 +  * 10-15:59 min = 0.2 
 +  * 16-21:59 min = 0.3 
 +  * 22-27:59 min = 0.4 
 +  * 28-33:59 min = 0.5 
 +  * 34-39:59 min = 0.6 
 +  * 40-45:59 min = 0.7 
 +  * 46-51:59 min = 0.8 
 +  * 52-57:59 min = 0.9 
 +  * 58-59:59 min = 1.0 
 + 
 + 
 +By clicking on a particular tail Leon shows a new page with **2** tabs described below.
  
  
 ===== Documents ===== ===== Documents =====
  
-Here you can see **all documents** assigned only 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). 
  
-The list of documents can be defined in a section [[leon:fleet-documents-setup|Fleet Documents Setup]].+[{{ :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).
 +
 +The list of documents can be defined in a section [[leon:fleet-documents-setup|Fleet Documents Setup]].
  
 +----
 ===== CAM ===== ===== 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> <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 each aircraft, as: +Here you can define such values for aircraft airframe and engines, as: 
  
   * **Start date** - the date of the first flight.   * **Start date** - the date of the first flight.
Line 28: Line 47:
   * **Start TAC** - total number of accumulated cycles.   * **Start TAC** - total number of accumulated cycles.
  
-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**. 
-[{{ :leon:mx-fleet:tah_decimal_off.png?200|TAH in minutes }}] 
-[{{ :leon:mx-fleet:tah_decimal_on.png?200|TAH in decimal }}] 
  
-Leon converts values into decimal with a pattern: 
-  * 00-03:59 min = 0.0 
-  * 04-09:59 min = 0.1 
-  * 10-15:59 min = 0.2 
-  * 16-21:59 min = 0.3 
-  * 22-27:59 min = 0.4 
-  * 28-33:59 min = 0.5 
-  * 34-39:59 min = 0.6 
-  * 40-45:59 min = 0.7 
-  * 46-51:59 min = 0.8 
-  * 52-57:59 min = 0.9 
-  * 58-59:59 min = 1.0 
  
  
  
-[{{ :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 65:
 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 79:
 </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 100:
 <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 119:
 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.+
  
  
  
leon/mx-fleet.txt · Last modified: 2023/02/09 17:36 by rafal

Page Tools

© 2021 LEON SOFTWARE ALL RIGHTS RESERVED | Leon Software