ROUTINE MAINTENANCE RELIABILITY - Apsyswebapp.ifrskeyes.com/amasis/doc/EN/Reliability.pdf ·...

ROUTINE MAINTENANCE RELIABILITY

User’s Manual: AMASIS R9.30

MAO-FI Release: 1.0 Date: 4th April 2014

/57


USER’S MANUAL




/57

- Contents -

Involved AMASIS releases .................................................................................................. 3

Table of modifications ........................................................................................................ 3

Tracking ............................................................................................................................... 3

Introduction: Reliability ...................................................................................................... 4

Process: Reliability ............................................................................................................. 5

Main access: Reliability ...................................................................................................... 6

Prerequisite: Reliability ....................................................................................................... 7

Involved services ................................................................................................................ 8

Data gathering / « Introduction » ........................................................................................ 9

Introduction of operation data - TL .................................................................................... 9

Data introduction on WO ...................................................................................................11

Data introduction on OF ....................................................................................................12

Reliability settings ..............................................................................................................14

Equipment reliability settings ............................................................................................15

Fleet reliability management .............................................................................................16

Calculation formula ............................................................................................................19

System reliability management .........................................................................................20

P/N or Equipment reliability management ........................................................................23

Line stop reliability management ......................................................................................28

Reliability chart management ............................................................................................30

P/N reliability charts ...........................................................................................................53




/57

Involved AMASIS releases This document applies from the following A.M.A.S.I.S release:

� A.M.A.S.I.S R9.30

Table of modifications

RELEASE DATE DESCRIPTION

R1.0 04/04/2014 Application of document

Tracking

WRITTEN BY VALIDATED BY AUTHORIZED BY

Service Service Service




/57

Introduction: Reliability The reliability management function offers to users the environment tools which provide the following reports:

FLEET RELIABILIITY SYSTEM RELIABILITY EQUIPMENT RELIABILITY LINE STOP RELIABILITY

These reports, which produce technical availability and reliability, use data taken from Technical Logs, Work Orders, Order Forms. This data can also be displayed using control screens. Fleet reliability produces the general activity of Airline fleet, from 'technical' punctuality of each aircraft and global rates of failures occurred during flight operation and maintenance. System reliability repeats the majority of aircraft data, with a presentation by ATA chapter. Equipment reliability produces MTBF, MCBF, MTBUR, MCBUR, delays and cancellations occurred during A/C operation. Line stop reliability produces reliability data depending on the line stops introduced on the TLs.

Fleet reliability

- by effectivity - by A/C

System reliability

- by ATA

P/N reliability

- by P/N - by equipment

Line stop reliability

- by issuing centre

Graphics reliability

Crystal report print-outs




/57

Process: Reliability Reliability module relies on the principle of analysis of data integrated into AMASIS.

1) Data gathering / « Introduction » a. TL b. WO c. OF

2) Launching of calculation of the various reliabilities

3) Analysis of reliability results in the form of reports � Graphics reliability

At least 12 months of operation are necessary to obtain reliability with significant results, especially for Equipment reliability.




/57

Main access: Reliability Module Routine Maintenance module � Reliability menu




/57

Prerequisite: Reliability

- The user must have the authorizations to reliability management (see Work with menu, then Work with roles menu and Work with users menu).

- The manufacturer references must have been defined with « Reliability follow-up » option in order to obtain the reliability. By default, all the S/Ns linked to this reference will also have a reliability follow-up. But the system offers the possibility not to include a particular S/N in the reliability.




/57

Involved services � Engineering service




/57

Data gathering / « Introduction » For consistent reliability results, it is important to introduce data on the various AMASIS documents:

- TLs: Delays, Incidents, Cancelled flights

- WO

- OF FS

Introduction of operation data - TL The TL includes a zone dedicated to reliability. Data introduced in this zone will be exploited for Fleet reliability. During creation or change of a TL, introduction of this data is possible.

Field description Flight

Flight type Indicates flight type (Tests, Instruction, Delivery …) made on this TL leg.

Must be defined in the Background data � Flights If no flight is introduced in the TL, the flight is considered as a

commercial flight and then included in reliability statistics. ETOPS Check box that indicates if it is an ETOPS flight Delays 1st level IATA delay code. Indicates the code of delay linked to involved flight

leg. Configurable in the Background data � Flights

WO responsible for delay




/57

IATA codes 4x are considered as technical delays, thus included in reliability calculations.

Min Delay duration in minutes 2nd level Same codification as 1st level. But this delay is the consequence of

another flight or aircraft. It is possible to accumulate the two levels of delay Min Delay duration in minutes Cancel flight 1st lev Check box used to cancel the flight. Cancellation not due to a previous

flight or aircraft. Cancel flight 2nd lev Check box used to cancel the flight. Cancellation is due to a previous

flight or aircraft. WO/TFU Field used to link the anomaly to the WO/TFU dealing with the failure.

It must be of Techlog type and be responsible of the failure (code R in Reliability field).

It is possible to introduce a WO linked to an A/C not same as TL one. Incidents Incidents 1 to 3 Indicates the type of incident encountered during flight

Must be defined in the Background data � Flights 3 fields for different 3 incidents on the same flight: QRF, QRP,

Rerouting… Number Occurrences occurred for an incident of same type

In reliability report, a delay and a cancellation will not be accounted for a same leg. The cancellation only will be accounted in this case. At present, the delays and the cancellation of 2nd level are to taken into account in reliability statistics.




/57

Data introduction on WO The calculation of System reliability (by ATA) is made from the data included on the WOs/TFUs.

Fields exclusively used for reliability follow-up Reliability Yes, Not processed in reliability or R responsible for delay

If the WO is responsible for the delay of a flight, then you can introduce the impacted TL directly from the WO.

The reliability field is filled in by default for some types and/or subtypes of WOs. Refer to Documents §IP-DOC-TOE doc. In this case, the default code of the involved WO must be changed into ‘R’ if it is responsible for flight delay or cancellation.




/57

Data introduction on OF The data introduced on the operation forms will be used afterwards for equipment reliability calculation (calculation of MTBF, MTBR, MTBUR…)

During creation of removal due to failure, the OF is pending for confirmation. The user will have to indicate if failure is confirmed or not, or if it remains with no reply. The maintenance type and removal reason fields will be automatically filled in fields according to subreason of OF at the origin of removal (refer to Documents doc §IP-DOC-SBO) - The type of maintenance takes « not scheduled » value for removals due to failure and

« scheduled » in the other cases. The user will be able to change the value of this field.

- The removal reason will take one of the following values according to subreason. The user will always be able to change the reason if necessary.

An OF linked to a FS will be updated during OF closing, reliability data being filled in.




/57




/57

Reliability settings




/57

Equipment reliability settings

Alternates taken into account in the family It is possible to define which alternates will be taken into account in the family for a given P/N. Failure confirmed on OF These settings are only used to determine which types of OF (Operation Forms) are taken into account for MXBF calculation (X = T for Time, C for Cycle, 1,2,3 for nonstandard 1, 2 or 3 and BF = Between Failure). Considered in reliability calculation: this type of removal will be accounted in MXBF calculation. Not introduced: If box is checked, the removal type is taken into account for MTBF calculation if no data is introduced by a user on the OF. Once the settings « Considered in reliability calculation » and « Not introduced » are validated with at least « Considered in reliability calculation » selected, it is necessary to indicate for each type of removal which answers are taken into account or not for failure confirmation: E: answer pending (default value during creation of a removal form) O: Confirmed failure S: No answer




/57

Fleet reliability management

1. Fleet reliability calculation Accessible from Routine Maintenance module �� Reliability �� Fleet reliability

• If « Detail by A/C» option is at Yes, the calculation by A/C will be automatically launched. Otherwise, launch A/C reliability calculation.

• If « Override eventual manual data » is at Yes, the calculation will override the previously

manually introduced data for fleet reliability.




/57

2. Fleet reliability management

It enables access to basic data used in reliability report. Part 1: List of monthly introduced data. You can select to display the data for an effectivity or an A/C Part 2: Detail of data over a month selected in part � spread out on the various tabs and in the form of charts. « Incidents » tab shows the statistical data on the incidents occurred to the fleet.

On the left list, you can see all the incidents occurred over the selected period and its occurrences. « Rate » tab shows the calculated data which represent fleet reliability (punctuality, Pireps/Mareps rate…)

��

��




/57




/57

Calculation formula Operation Scheduled flights = OPS flights + Cancelled flights Average leg (in hours hundredths) =

flights scheduled NbFH total Month

Daily use (in hours hundredths) =

month of days nb A/CNbFH total Month

×

Technical punctuality Cancellation rate (Technical availability) = 100

flights scheduled Totalflights cancelled Not ×

Delay rate (Technical punctuality) = 100

flights scheduled Totaldelay no withFlights ×

Delay rate > 5min = 100

flights scheduled Total5mindelay no withFlights ×>


fights scheduled Total15mindelay no withFlights ×>


flights scheduled Total45mindelay no withFlights ×>

Average delay =

delays of number Totalduration totalDelay

Punctuality =

flights Nbduration totalDelay

PIREPS rate for 100FH = 100

FH total MonthPIREPS Nb ×

PIREPS rate for 100CY = 100

CY total MonthPIREPS Nb ×

MAREPS rate for 100FH = 100

FH total MonthMAREPS Nb ×

MAREPS rate for 100CY = 100

CY total MonthMAREPS Nb ×

MAREPS/PIRES rate = 100

PIREPS NbMAREPS Nb ×

Removal rate for 100FH = 100

FH total Monthremovals scheduled of Nb ×

Removal rate for 100CY = 100

CY total Monthremovals scheduled of Nb ×

Incidents Incident rate for 1000FH

= 1000FH total Month

incidents of Nb ×

Incident rate for 1000CY = 1000

CY total Monthincidents of Nb ×




/57

System reliability management

1. System reliability calculation Accessible from Routine Maintenance module �� Reliability � System reliability

• If « Detail by A/C» option is at Yes, the calculation by A/C will be automatically launched. Otherwise, launch system reliability calculation.


manually introduced data for system reliability.

2. System reliability management It enables to access basic data used in reliability report. Part 1: List of monthly introduced data. You can select to display the data for an effectivity or an A/C and by ATA. Part 2: Detail of data over a month selected in part � spread out on the various tabs and in the form of charts.




/57

« Incidents » tab shows the statistical data on the incidents occurred to the fleet. Refer to Calculation formula page above. « Rate » tab shows the calculated data which represents system reliability (punctuality, Pireps/Mareps rate…). Refer to Calculation formula page above.

ATAs ?? correspond to TLs with no WO responsible for a delay but for which a « technical » delay has been declared (IATA 4x delay code). AMASIS calculates the sum of delays, pireps, mareps… of sub-ATAs at main ATA level.

��

��




/57

Example: For a pireps for ATA 3510 and ATA 3520 during the same period, there will be 2 pireps for ATA 35.

3. Threshold management Manufacturer or company reference thresholds can be introduced and will be used as comparison criterion in reliability reports. A reference threshold is defined for an effectivity, a period (month/year) and an ATA (or subATA).

When the thresholds are defined, you can see on reliability screen if rates are higher or lower than thresholds.




/57

P/N or Equipment reliability management For calculating MTBxx, we recommend you to always launch in order P/N reliability calculation, the, once this operation is complete, MTBxx calculation during the same period.

1. P/N reliability calculation Accessible from Routine Maintenance module �� Reliability � P/N reliability It is possible to launch the calculation by S/N with « Calculate reliability / Equipment » function from the main menu.

• If « Override eventual manual data » is at Yes, the calculation will override the previously manually introduced data for P/N reliability.

2. P/N or Equipment reliability management It enables access to basic data used in reliability report. Part 1: List of P/Ns or Equipment taken into account in the reliability. Part 2: List of data introduced for a selected P/N or Equipment. You can select to display the data for an effectivity, an A/C or the Fleet.




/57

Part 3: Detail of data during a month selected in part � spread out on the various tabs and in the form of charts.

��

��

��




/57

3. Calculation of MTBxx by P/N

Accessible from Main menu � Routine Maintenance �� Reliability �� Work with MTBBxx

• If « Override eventual manual data » is at Yes, the calculation will override previously manually introduced data for MTBxx management.

• If « Calculate equipment » option is at Yes, the calculation by S/N will then be automatically

launched. Otherwise, launch « Calculate MTBxx/ Equipment » option.

4. Work with MTBxx by P/N or Equipment It enables to access basic data used in reliability report. Part 1: List of P/Ns or Equipment taken into account in reliability. Part 2: List of data introduced for a selected P/N or Equipment. You can select to display the data for an effectivity, an A/C or the Fleet. You can also request the calculation of MTBxx over rolling 12-months or from the total life of part.

The MxBF, MxBUR and MxBR are indicated in hours, cycles or nonstandard. Example for flight hours: MTBF (Mean Time Between Failure) = mean time between to consecutive failures =




/57

failures confirmed of Numberhours Flight

MTBUR (Mean Time Between Unscheduled Removals) = mean time between two unscheduled removals =

removals dunschedule onf Numberhours Flight

MTBR (Mean Time Between Removals) = mean time between two consecutive removals =

removals of Numberhours Flight

Part 3: Detail of data during a month selected in part � spread out on the various tabs and in the form of charts.

��

��

��




/57

5. Threshold management Manufacturer or company reference thresholds can be introduced and will be used as comparison criterion in reliability reports.




/57

Line stop reliability management

1. Line stop reliability calculation Accessible from Routine Maintenance module �� Reliability � Line stop reliability

• If « Detail by A/C» option is at Yes, the calculation by A/C will be automatically launched. Otherwise, launch line stop reliability calculation / AC.


manually introduced data for line stop reliability.




/57

2. Line stop reliability management

It enables to access basic data used in reliability report. Part 1: List of monthly introduced data. You can select to display the data for an effectivity, an A/C or a Line Stop. Part 2: Detail of data over a month selected in part � spread out on the various tabs and in the form of charts. Data is retrieved from one part from the TLs (line stops) and the other part from the WOs/TFUs (location). « Delay codes » supplies statistical data on delays (type and duration) occurred during a stop line. Refer to Calculation formula page below. « Rate » tab shows the calculated data representing the line stop reliability (punctuality, Pireps/Mareps rate…). Refer to Calculation formula above

��

��




/57

Reliability chart management The reliability chart is a report that provides a graphics representation (charts, histograms…) of reliability data introduced in AMASIS system.

1. Reliability chart by period, ATA or line stop

By period




/57

By ATA

By line stop




/57

Field description

Sorted by Selection of report of reliability chart by period, ATA or line stop Mandatory check box For Selection of report of reliability for an effectivity, A/C or fleet Effectivity Aircraft effectivity code If it is a report for an effectivity, this field is displayed and mandatory A/C Aircraft registration If is a report for an A/C, this field is displayed and mandatory

From ATA To ATA Start and end ATA to be taken into account for the report Line stop Airport code Comparison period Period, indicated in month/year, used to compare reliability data Mandatory field Analysis period Reliability period, indicated in month/year Mandatory field Detailed report Detail of the data used for the chart report Mandatory field Fleet breakdown Selection of the report of fleet breakdown Mandatory field Optional parameters Report of the following charts:

- Daily use for studied effectivity or aircraft - Flight average duration for studies effectivity or aircraft - Number of in service aircraft during the period for the

effectivitity or aircraft Available for a report by period PIREPS rate / Flight hours and cycles Report of the following charts:

- PIREPS rate / X flight hours - PIREPS rate / X cycles

X is the ratio defined in reliability settings Available for a report by period or ATA MAREPS rate / Flight hours and cycles Report of the following charts:

- MAREPS rate / X flight hours - MAREPS rate / X cycles

X is the ratio defined in reliability settings Available for a report by period or ATA




/57

Incident rate Report of the chart of incident rate Available for a report by period or ATA Rate of on-time flights Report of the chart of rate of on-time flights Available for a report by period Average delay Report of the chart of average delay times Delayed or canceled flight rate Report of the chart of the rate of delayed or cancelled flights Available for a report by ATA Delay rate / Flight hours Report of the chart of the rate of delay / flight hours Available for a report by line stop

2. Description of charts

a) By period Optional parameters • This chart shows the daily use of an A/C for the studied effectivity or A/C during analysis period.




/57

FIHBFIHA

useDaily =

FIHA = total FH for the fleet during the period FINB = number of present aircraft of this type with at least one TL, one WO/TFU or OF during this period • This chart shows the flight average duration for the studied effectivity or A/C during analysis period

FIEXPFIHAEXP

duration average Flight =

FIHAEXP = total FH for operational flights FIEXP = number of operational flights




/57

• This chart shows the numbers of in service aircraft during the period for an effectivity during analysis period

PIREPS and MAREPS rate by flight hour and cycle • This chart shows the comparison between analysis period PIREPS or MAREPS rate and the

number of PIREPS or MAREPS




/57

• This chart shows the number of PIREPS or MAREPS rate for X hours and Y cycles during

analysis period

X×=FIHA

FIPIREPS rate PIREPS (for hours)

Y×=FIHA

FIPIREPS rate PIREPS (for cycles)

X = ratio indicated in FH, value in reliability settings (refer to § Reliability settings) Y = ratio indicated in CY, value defined reliability settings (refer to § Reliability settings) FIHA = total FH for the fleet during the period FIPIREPS = number of PIREPS following in reliability

X×=FIHA

FIMAREPS rate MAREPS (for hours)

Y×=FIHA

FIMAREPS rate MAREPS (for cycles)

FIMAREPS = number of MAREPS followed in reliability




/57

Incident rate • This chart shows the comparison between the comparison period and analysis period of incident

rate by X flight hours and the number of incidents

• This chart shows the incident rate by X flight hours during analysis period

X×=FIHA

FINBINC rate Incident




/57

X = ratio indicated in FH, value defined in reliability settings (refer to § Reliability settings) FIHA = total FH for the fleet during the period FINBINC = number of incidents of all types Rate of on-time flights • This chart shows the comparison between comparison period and analysis period of the rate of

on-time flights and the total on-time flights




/57

• This chart shows the number of on-time flights during analysis period.

( )Y

FIVOL×

+++= FIANN2FIANN1FIRTD22 FIRTD12 - FIVOL flights time-on of Rate

Y = ratio indicated in CY, value defined in reliability settings (refer to § Reliability settings) FIVOL = number of flights FIRTD12 = number of flights which first level delay is > than 2nd parameter of delay (15min by default) FIRTD22 = number of flights which second level delay is > au 2nd parameter of delay (15min by default) FIANN1 = number of first level cancellations FIANN2 = number of second level cancellations




/57

Average delay times • This chart shows the comparison between comparison period and analysis period of average

delay times

• This chart shows the average delay times during analysis period




/57

( )( )FIRTD2FIRTD1

FIRTDTPS2 FIRTDTPS1 timesdelay Average

++=

FIRTD1 = number of delayed flights of first level FIRTD2 = number of delayed flights of second level FIRTDTPS1 = total delay times of first level indicated in min FIRTDTPS2 = total delay times of second level indicated in min

By ATA PIREPS and MAREPS rate by flight hour and cycle • This chart shows the comparison between comparison period and analysis period of the 20

highest rates (descending order on the rate of the analysis period) of PIREPS or MAREPS for X hours and Y cycles for each ATA




/57

• This chart shows the 20 highest rates (descending order) of PIREPS or MAREPS for X hours and Y cycles for each ATA during analysis period

X×=FIHA


Y×=FIHA


X = ratio indicated in FH, value defined in reliability settings (refer to § Reliability settings) Y = ratio indicated in CY, value defined in reliability settings (refer to § Reliability settings) FIHA = total FH for fleet during period FIPIREPS = number of PIREPS followed in reliability

X×=FIHA


Y×=FIHA


FIMAREPS = number of MAREPS followed in reliability




/57

Incident rates • This chart shows the comparison between comparison period and analysis period of the 20

highest rates (descending order on the rate of analysis period) of incidents by X flights hours and the number of incidents for each ATA




/57

• This chart shows the 20 highest rates (descending order) of incidents by X flight hours for each ATA during analysis period.

X×=FIHA


X = ratio indicated in FH, value defined in reliability settings (refer to § Reliability settings) FIHA = total FH for the fleet during the period FINBINC = number of incidents of all types




/57

Rate of delayed or cancelled flights • This chart shows the comparison between comparison period and analysis period of the 20

highest (descending order on the rate of analysis period) rates and the numbers of delays and cancelled flights for each ATA




/57

• This chart shows the 20 highest (descending order) rates and numbers of delayed or cancelled flights for each ATA during analysis period.

( )Y×+++=

FIVOLFIANN2 FIRTD2 FIANN1 FIRTD1

flights cancelled or delayed of Rate

Y = ratio indicated in CY, value defined in reliability settings (refer to § Reliability settings) FIVOL = number of flights FIRTD1 = number of delayed flights of first level FIRTD2 = number of delayed flights of second level FIANN1 = numbers of cancellations of first level FIANN2 = number of cancellations of second level




/57

Average delay times • This chart shows the comparison between comparison period and analysis period of the 20

highest (descending order) average delay times for each ATA

• This chart shows the 20 highest (descending order) average delay times for each ATA during

analysis period.




/57

( )( )D2FIRTD1

FIRTDTPS2 FIRTDTPS1 timesdelay Average

FIT++=

FIRTD1 = number of delayed flights of first level FIRTD2 = number of delayed flights of second level FIRTDTPS1 = Delay total time of first level indicated in min FIRTDTPS2 = Delay total time of second level indicated in min

By line stop PIREPS and MAREPS rate by flight hour and cycle • This chart shows the 20 highest rates (descending order) of PIREPS or MAREPS for X hours and

Y cycles for each line stop during analysis period

• This chart shows the 20 highest rates (descending order) of PIREPS or MAREPS for X hours and

cycles for each line stop during analysis period

X×=FIHA





/57

Y×=FIHA


X = ratio indicated in FH, value defined in reliability settings (refer to § Reliability settings) Y = ratio indicated in CY, value defined in reliability settings (refer to § Reliability settings) FIHA = total FH for the fleet during the period FIPIREPS = number of PIREPS followed in reliability

X×=FIHA


Y×=FIHA


FIMAREPS = number of MAREPS followed in reliability • This chart shows the 20 highest numbers (descending order) of PIREPS or MAREPS for each line

station during analysis period




/57

Incident rate • This chart shows the comparison between comparison period and analysis period of the 20

highest rates (descending order on analysis period) of incidents by X flight hours and the number of incidents for each line stop

• This chart shows the 20 highest rates (descending order) of incidents by X flight hours for each

line stop during analysis period




/57

X×=FIHA


X = ratio indicated in FH, value defined in the reliability settings (refer to § Reliability settings) FIHA = total FH for the fleet during the period FINBINC = number of incidents of all types Delay rate by flight hour • This chart shows the comparison between comparison period and analysis period of the 20

highest delay rates (descending order on the rate of analysis period) for X hours for each stop line




/57

• This chart shows the 20 highest delay rates (descending order) for X hours for each line stop during analysis period

( )X×+=

FIVOLFIRTD2 FIRTD1

rateDelay

Y = ratio indicated in CY, value defined in reliability settings (refer to § Reliability settings) FIVOL = number of flights FIRTD1 = number of delayed flights of first level FIRTD2 = number of delayed flights of second level




/57

P/N reliability charts

1. General

Field description

P/N Selection of the report of dispatch reliability by P/N Check box Family Selection of the dispatch reliability by family (P/N + inter) Check box From P/N To P/N Start and end P/N to be taken into account for the report. Must be

defined in the manufacturer references (refer to Reference card doc) Manufacturer code Code of manufacturer indicated on reference card Pool code Code of supplier pool indicated on P/N sheet. Must be defined in the

Background data (refer to Thirds, suppliers, clients doc § INFO-TFC-P4 Pool)

A/C A/C registration. Must be defined in the Background data (refer to

Effectivities and A/C doc) In case of report for A/C, displayed field and mandatory




/57

Effectivity A/C effectivity code. Must be defined in the Background data (refer to Effectivities and A/C doc)

In case of report for A/C, displayed field and mandatory Fleet All the A/C, all effectivities taken together, active in AMASIS From ATA To ATA Start and end ATA to be taken into account for the report From date To date Reliability period, indicated in month/year Mandatory field Detailed report Detail of the data use for the dispatch reliability Mandatory field Report of the n first records Selection of he number of P/Ns to be studies Mandatory field Ageing codes P/N ageing code. Adds the dispatch reliability charts of MTBF,

MTBUR, MTBR for each ageing code. Up to 5 ageing codes can be used. Must be defined in the Background data

2. Description of charts MxBxx for effectivity and A/C • This chart shows the most critical P/Ns, which percentage of threshold is the lowest, i.e. the

MTBF, MTBUR or MTBR the nearest or lowest to defined threshold (manufacturer or airline) for this P/N by company and effectivity. Ascending order by % of the threshold and MTBF, MTBUR or MTBR




/57

thresholdMxBxx MxBxx

threshold of % =

MTBF, MTBUR and MTBR are indicated in hours, cycles or non-standard ageing. MTBF (Mean Time Between Failure) = average duration between two consecutive failures MTBUR (Mean Time Between Unscheduled Removals) = average duration between two unscheduled removal MTBR (Mean Time Between Removal) = average time between two consecutive removals




/57

MxBxx for fleet • This chart shows the most critical P/Ns, which MTBF, MTBUR or MTBR are the lowest




/57

NFFR (No Fault Found Ratio) • This chart shows the not confirmed failure rate sorted by descending order by P/N

( )FIBO

FIBOCF - FIBONP NFFR =

FIBO = number of removals during the 12 last months FIBOCF = number of not confirmed removals during the 12 last months FIBONP = number of not scheduled removals during the 12 last months (removals which reason is failure of type 1 on installation/removal documents and removal type code different from « P ») NUR = number of not scheduled removals NCF = number of not confirmed failures

ROUTINE MAINTENANCE RELIABILITY - Apsyswebapp.ifrskeyes.com/amasis/doc/EN/Reliability.pdf ·...

Documents

Transcript of ROUTINE MAINTENANCE RELIABILITY - Apsyswebapp.ifrskeyes.com/amasis/doc/EN/Reliability.pdf ·...