routine maintenance technical log - apsys

ROUTINE MAINTENANCE TECHNICAL LOG

USER’S MANUAL


User’s Manual: AMASIS R9.30

MAO-CRM Release: 2.0 Date: 3rd September 2014

/35

- Contents -

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

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

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

Introduction: Technical Log ............................................................................................... 4

Process: TL .......................................................................................................................... 6

Main access: TL ................................................................................................................... 6

Prerequisite: TL ................................................................................................................... 6

TL settings ........................................................................................................................... 7

Services involved ................................................................................................................ 7

Description of screens and screen parts ........................................................................... 8

MAO-CRM-P1 Create TL .....................................................................................................17

MAO-CRM-P2 Add flight to TL ...........................................................................................19

MAO-CRM-P3 Display TL ...................................................................................................20

MAO-CRM-P4 Add manhours on TL .................................................................................22

MAO-CRM-P5 Work with fuel .............................................................................................23

MAO-CRM-P6 Work delays and incidents ........................................................................25

MAO-CRM-P7 Work with TL, add engine oil and hydraulic liquid ...................................26

MAO-CRM-P8 Change next TL No on A/C sheet ..............................................................27

MAO-CRM-P9 Delete TL .....................................................................................................28

MAO-CRM-P10 Create adjustment TL ...............................................................................29

MAO-CRM-P11 Generate WO linked to TL ........................................................................30

MAO-CRM-P12 Display or change PIREPS linked to TL ..................................................31

MAO-CRM-P13 Display or change specific data linked to TL..........................................32

MAO-CRM-P13-1 Prerequisite: TL specific data ...............................................................32

MAO-CRM-P13-2 TL specific data update following TL number modification ...............34

MAO-CRM-P14 Reports ......................................................................................................35




/35

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 12/08/2014 Application of document

R2.0 03/09/2014 Document update following integration of EVO969 – Addition of § MAO-CRM-P13 specific data on AMASIS Technical Log

Tracking

WRITTEN BY VALIDATED BY AUTHORIZED BY

Service Service Service




/35

Introduction: Technical Log This procedure presents the full process to be followed with AMASIS for managing the introduction of A/C activity and reliability. Every flight, performed or cancelled must be introduced in AMASIS using a Tech Log. The Technical Log is the only document that enables recording of activity of each aircraft (flight hours, cycles, engine hours; APU hours and other special follow-ups). It also records fleet reliability: delays, flight cancellations and incidents occurred during each flight. It must be either introduced manually, or automatically from Flight logs (KEOPS software), even from another interfaced software (AIRMAN AIRBUS for instance). It is important to note that it is the introduction of TL that makes each aircraft and on-wing equipment age. TL introduction is a determining factor in aircraft and equipment ageing and maintenance schedules (WO, SB, AD, checks, equipment potentials). Remark:

By default each aircraft is followed in flight hours (FH and cycles CY). Other types of follow-up can be defined and linked to effectivity and aircraft. It is important to also define the type of follow-ups specific to each Part Number, using the reference card, and the related intervals on each Kardex position.

When a crew complaint / or Log book sequence (PIREPS) is issued, it is represented by a Work Order: this one can be generated directly from TL or manually created from WO menu.




/35

GENERAL DIAGRAM OF TECHNICAL MODULE




/35

Process: TL The runway personnel creates the TL, declares the flight, performed job and possible anomalies and/or maintenance.

Main access: TL Routine Maintenance module � TL menu

There are other ways of accessing a TL, depending on the screen you are using. This access is

always represented by the following icon:

Prerequisite: TL

- The user must be allowed to access Routine maintenance management (refer to Work with menu, Work with roles and Work with users )




/35

TL settings Various general settings pre-defined by the Administrator have an impact on the introduction of some data of a TL.

To access these settings in display mode, select icon on TL management screen or from the main menu of Routine Maintenance settings.

Services involved Depending on company organization, the involved services by the creation/change of TLs are:

� The line � The stations � The Planning




/35

Description of screens and screen parts This chapter describes TL functions. For the general description of the product, refer to Navigation and ergonomics documentation.

TL icons for not interfaced A/C

From left to right:

• Change (F2) or Display (F2) • Create (F9) • Create adjustment TL • Delete • Work with manhours • Display aircraft sheet • Print/Report options • Tracking • TL management settings Deletion is only permitted on the last TL and if no WO is linked to it.

Description of TL list columns

Date TL date A/C A/C registration Number TL number

Text indicates the presence of a comment

Adjustment TL indicates that it is an adjustment TL, either a normal TL




/35

Last TL this is the last TL of aircraft Effectivity Effectivity of aircraft Administrator Administrator of aircraft WO/TFU Number of WO/TFU linked to TL AB hours Total flight time of aircraft Cycle Number of total cycles of aircraft BB hours Total Block/Block time of aircraft Nonstandard 1 to 20 Total quantity of nonstandard ageing of aircraft Code 1 to 20 Description of nonstandard ageing of aircraft

Selection / sort settings

- Select Routine Maintenance menu � TL

- Click icon on the left top.




/35

- Select the selection setting The use of this function is described in Navigation and ergonomics documentation.

TL header

The key data included in a TL are highlighted in a blue-grey and background and in bold.

A/C Registration of A/C for which technical log is introduced. It

corresponds to usual aircraft registration defined in aircraft file. Mandatory field , selection possible with F4. Date Flight date which can be different from TL date of entry in AMASIS.

Mandatory field . No Tech Log number. This one should be the same as the number

mentioned on the original paper Tech Log filled in by the crew. The very first Tech Log number initialization is done in aircraft information sheet. AMASIS automatically adds one after each flight. When a new physical Tech Log is used, the next Tech Log number will have to be modified in aircraft information sheet (see §MAO-CRM-P8). It must be noticed that, in case of mistake in A/C activity data entry, only the very last Tech Log can be modified. If a past error is reported, an adjustment TL can be created (see §MAO-CRM-P10); hours, cycles and non-standard values can be added or deducted to/from A/C. CPT Crew member codes (Captain) F/O-F/E Crew member codes (First Officer, Fist Engineer) Number of linked PIREPS Number of WOs/TFUs linked to TL

TL tabs Display mode Change mode




/35

« Detail » tab

in display mode

Part 1 Summary table of TL flights You can see the details of the selected flight in part 3 of the screen Summary table of total ageing (native or nonstandard of the aircraft further to TL.

Part 2 Summary table of WOs/TFUs linked to TL

Part 3: « Flight »tab




/35

Field description

Departure Code of airport of takeoff. When a new TL is created, code of airport of departure is

automatically filled in with the code of the last airport of previous TL. Arrival Code of airport of landing Flight No Flight number Flight type Type of flight (revenue flight, ferry, training…). These types must be

defined (see Effectivities and A/C §INFO-AC-P13 doc). By default, the flight is considered as a revenue flight.

Only delays and incidents related to revenue flights will be taken into account for the fleet and system reliability calculation.

ETOPS ETOPS type flight Touch & Go Number of Touch & Go made during flight. By default, one Touch &

Go corresponds to one aircraft cycle. B/B and A/B departure Flight block (brakes-off) and airborne (take-off) hours on departure.

Depending on the settings, these data may not been introduced (see §TL settings )

B/B and A/B arrival Flight block (back to parking) and airborne (landing) hours on arrival.

Depending on the settings, these data may not been introduced. (see §TL settings )

A/B and B/B duration Flight airborne (flight time) and block (time between brakes-off and

return to parking after landing) durations. Flight airborne duration cannot exceed flight maximum duration

(aircraft sheet) nor flight block/block duration.

Part 3: « Delay(s) and Incident(s) » tab




/35

Field description

Delays

Two levels of delay are possible for a flight: primary delay and secondary delay.

1st level Code of delay 1 and associated length in minutes. When the delay or cancellation is directly related to a system or

equipment malfunction. 2nd level Code of delay 2 and associated length in minutes When the delay or cancellation is due to a primary delay within the

previous 24 hours These codes must previously be defined (see Background data doc). Cancellation Flight cancellation can be of primary or secondary type:

Primary level cancellation: cancellation not related to a previous flight. Secondary level cancellation: cancellation due to a previous flight

Caution: In the reliability report, when a delay and a flight cancellation are declared, flight cancellation only is taken into account. The code used for the delays indicates the cancellation reason. WO/TFU Technical delays or flight cancellations are related to a Work Order /

Technical Follow-up which must be of Tech Log type. This field can only be introduced if at least one technical delay or a flight cancellation occurred. WO/TFU must be of TL type and linked to this TL.

The entry of Work Order can be changed in two different ways: - Direct entry of responsible WO/TFU number for associated flight leg. AMASIS then

automatically changes reliability status of WO/TFU to ‘R’ (responsible) with associated leg number.

- Postponed data entry. WO status reliability has then to be changed to ‘R’ (responsible). AMASIS will then automatically update Tech Log.

Incidents Incidents 1, 2 and 3 Incident codes, and associated quantity, which occurred during flight. These codes must be defined (see Background data doc)




/35

Part 3: « WO/TFU » tab

Detail of selected WO in the table of part 2 of the screen.

Part 3: « Fuel» tab

Field description

Stations Code of the airport where aircraft is replenished. Fuel type Type of delivered or replenished fuel




/35

Quantity Quantity of delivered or replenished fuel Density Fuel density (modifiable) Sheet No Information on fuel sheet No Chargeable to flight Check box. In case of replenishment in flight Total fuel delivered Total quantity of delivered and replenished fuel Total fuel burnt Total quantity of consumed fuel (calculated or introduced) Total fuel on departure Total quantity of fuel before the flight Total fuel on arrival Total remaining quantity of fuel on arrival Total fuel next flight Total quantity of fuel for next flight (calculated or introduced)

Part 3: « Oil(s) and Fluid(s) » tab

Field description Departure & Arrival Various replenishments, indicated in number of tins before and after

the flight. The number of engines, APUs and fluids by aircraft is defined in A/C sheet (see Background data doc).

Engine Engine oil replenishment indicated in number of tins or other

packaging units defined by the company.

APU APU oil replenishment indicated in number of tins or other packaging units defined by the company.

Fluid Fluid replenishment indicated in number of tins or other packaging

units defined by the company.




/35

« Text » tab

« Text » tab is used to track all the important data related to TL.

« Logbook » tab

« Logbook » tab includes:

- the list of Kardex positions of aircraft designated for special monitoring (with Kardex position, Kardex position description, P/N and eventually S/N). To display these Kardex positions on TL, Logbook box must have been checked on Kardex position.

The Kardex positions displayed in this tab will be present in the A/C Technical situation report which can be accessed from A/C information sheet.

- one table which corresponds to the remaining potential of selected position if equipment is installed on this Kardex position

- one table which shows again aircraft ageing data.

With this tab, you can:

- View Kardex position of equipment using , or equipment with ,

- Generate WOs related to these equipment with .




/35

MAO-CRM-P1 Create TL To create a new TL:

- Select Routine maintenance menu � TL

- Click icon or press F9 key

- Introduce A/C registration (F4 on A/C field) and TL date. The other data is not mandatory, but

we recommend you to fill in as many fields as possible. For the description of the various data, refer to §Description of TL header

- Validate a first time with (or press Enter) After this first validation, a message is displayed:




/35

At the same time, TL number is automatically fed by expected number.

- Validate a second time with (or Enter), the TL has been created. - Introduce airport of arrival (departure airport corresponds to airport of arrival of previous flight).

- Fill in flight activity fields, and validate with (or Enter).

Remarks:

- Once introduced data is validated with (or Enter), AMASIS automatically calculates aircraft ageing after flight and copies out additional ageing on equipment cards via Kardex position.

- Flight type (revenue flight, ferry, training…). These types must be defined (see Effectivities

and A/C §INFO-AC-P13 doc). By default, the flight is considered as a revenue flight. Only delays and incidents related to revenue flight are taken into account for fleet and system reliability calculation.




/35

MAO-CRM-P2 Add flight to TL To add a flight to TL, from main menu:


- Select the A/C and related TL in the list, and click (or F2)

- In « Detail » tab, click Flight tab

- Click on the right part of the flight window. - Enter the airport of arrival (the airport of departure corresponds to the airport of arrival of the

previous flight).

- Enter the flight activity values, and validate with (or Enter). Remarks:

- Once the introduction is validated with (or enter), AMASIS automatically calculates the post flight ageing and copies out the additional ageing on equipment cards via their Kardex position.

- Flight type (revenue flight, ferry, training…). These types must be defined. By default, the

flight is considered as a revenue flight. Only delays and incidents related to revenue flight are taken into account for the fleet and system reliability calculation.

- Repeat these operations as many times as necessary.

You can:

- quit flight introduction and no information will be recorded

- delete the last flight, after selecting it.




/35

MAO-CRM-P3 Display TL To display a TL, from main menu:

- Select Routine maintenance menu � TL - Select the A/C. The date and TL number are optional. The last introduced TL is shown on list

bottom in bold red characters.

« Detail » tab includes:

- data related to flight - A/C total ageing indicated in all the follow-up codes - the list of WOs linked to TL - data related to delays/incidents/oils - data related to fuel

« Text » tab is used to track important information related to TL. « Logbook » tab proposes a synthesis of the most important remaining potentials of selected range of equipment (refer to Work with Kardex process) and the total ageing of aircraft.




/35




/35

MAO-CRM-P4 Add manhours on TL To add manhours to a TL, from main menu:

- Select Routine maintenance menu � TL - Select the A/C and related TL number in the list.

- Click manhours management icon on the right top of the screen

- Click on the right top of the screen

- Enter performer id, spent time (in one way or another) and date (if date is not introduced, TL date is taken by default).

- Click (or Enter) to validate. - Repeat these steps for each performer.

- Once manhour introduction is completed, click to leave this screen

- To go back to TL, click on the left top.

or




/35

MAO-CRM-P5 Work with fuel To add fuel to a flight of a TL, from main menu:


- Select the A/C and related TL number in the list, and click (or F2).

- In « Detail » tab, click Fuel tab

- In the summary table, select the flight onto which fuel data require to be introduced - Check Total fuel on departure (total fuel next flight is carried forward from previous TL)

- Note Total fuel on arrival (automatic calculation of Total fuel burnt )

- Click on fuel part of the screen to add fuel replenishment or uplift. Enter location, fuel type, quantity (+/-), fuel sheet No. Check fuel density (or update it if necessary).

- In case of replenishment in flight, check Chargeable to flight box. The delivered quantity will




/35

change the Total fuel burnt but not the Total fuel next flight ).

- Validate with (or Enter).

- Repeat these steps as many times as necessary and leave fuel introduction screen with .

- Check Total fuel delivered (automatic sum of delivered quantities)

Total fuel burnt and Total fuel next flight quantit ies , calculated by system, are modifiable. However, modified quantities appear in blue (and not in red) and the user who validated modifications can be displayed with tracking icon.

To delete a fuel delivery:

- Switch to change mode (or F2 key)

- Click button




/35

MAO-CRM-P6 Work delays and incidents To add delay or incidents on TL, from main menu:


- Select the A/C and related TL number in the list, and click (or F2).

- In « Detail » tab, click Flight tab

- In the flight summary table, select the flight onto which delay data require to be introduced. - Enter the delay and cancellation codes, eventually the number of the WO linked to delay, the

type of incident and the number of incidents. For more information on these data, refer to §Delays and Incidents .

- Validate with (or Enter). - Repeat this operation for the other flights if necessary.

Note that only delay and incident data linked to revenue flights is taken into account in fleet and system reliability calculations.




/35

MAO-CRM-P7 Work with TL, add engine oil and hydraulic liquid To add oil to a flight of a TL, from main menu:

- Select Routine maintenance menu � TL.

- Select the A/C and related TL, then click button (or F2).

- In « Detail » tab, click Oil(s) and Fluid(s) tab

- In the summary table, select the flight onto which oil and hydraulic liquid data require to be introduced.

- Fill in the fields concerning added quantities before and after the flight (unit used is the tin).

- Validate with (or Enter).




/35

MAO-CRM-P8 Change next TL No on A/C sheet To change the next number of a TL, from main menu:


- Select A/C and click to display A/C sheet.

- Click (or F2)

- Enter the new number of next TL

- End the process with (or Enter)

- Close the window with to go back to TL screen.




/35

MAO-CRM-P9 Delete TL In case of entry error, you can delete last TL only , if no WO is linked to this TL. To delete last TL of an A/C, from main menu:

- Select Routine maintenance menu � TL and select the A/C.

- Select the last concerned TL and click . - Answer Yes to the question, the TL is deleted.




/35

MAO-CRM-P10 Create adjustment TL In case of entry error, the last TL only can be deleted. If the error concerns another TL, it is necessary to use an adjustment TL. To create an adjustment TL, from main menu:

- Select Routine maintenance menu � TL and select the A/C.

- Click button. The following window is displayed:

- Enter the date and click (or Enter) - Enter the corrected values using the ageing codes (native and nonstandard).

- End the process with (or Enter)

It is not possible to carry out several adjustment TLs on the same day. In addition, we recommend you to make this at the end of day in order to facilitate value adjustment on the first TL of the following day.




/35

MAO-CRM-P11 Generate WO linked to TL Crew or line maintenance complaints are directly linked to TL via WOs of TechLog type. To generate a WO linked to a TL, from main menu:

- Select Routine maintenance menu � TL and select the A/C and TL.

- Click (or F2), a WO/TFU tab appears on TL.

- Select this tab, button is on the right of the screen.

WO creation button can go along with display button , if a WO linked to TL already exists.

- Click to create a new WO. For more information on required data to be entered, refer to Work Order documentation.

Once this data is introduced and validated, click to go back to TL screen.




/35

MAO-CRM-P12 Display or change PIREPS linked to TL To display or change WOs linked to a TL, from main menu:

- Select Routine maintenance menu � TL, the A/C and related TL in display mode.

In change mode, button can be used in WO/TFU tab and process is the same as the one in display mode.

- Click « Detail » tab and « WO/TFU » tab - Select the WO/TFU in WO list. A display of this WO is already shown in WO/TFU tab.

- Click to display WO/TFU details

- Once you have viewed or changed WO/TFU (see Work Order documentation), go back to TL

screen with . In case of WO closing, refresh TL to view the new date of the WO related to the table of linked WOs.




/35

MAO-CRM-P13 Display or change specific data linked to TL MAO-CRM-P13-1 Prerequisite: TL specific data

- The user must be allowed to access Routine maintenance management (refer to Work with menu, Work with roles and Work with users and rights )

- In addition, in order to be able to create new fields for specific data, the user must be allowed to access Background data management (refer to Work with menu, Work with roles and Work with users and rights )




/35

To display specific data related to a TL, from main menu:


- Click on the right top of the screen - Switch between tabs to display the fields related to each topic.

Field description

Technical log Details about the TL linked to specific data: A/C registration, TL date

and TL number Topic titles Customizable. This title can be created by using the menu:

Background data – Miscellaneous – Text topics Specific fields Customizable and modifiable. This field and its related format can be

created by using the menu Background data – Miscellaneous – Specific field settings

To modify specific data related to a TL, from main menu:


- Click on the right top of the screen - Switch between tabs to display the fields related to each topic

- To modify the specific fields data, click on the right top

- Validate the modification by using icon




/35

MAO-CRM-P13-2 TL specific data update following TL number modification

- It is possible for the user to change the TL number previously defined by double-clicking on the TL menu.

- On the following screen, use the dedicated menu to change TL number.

In case of TL number change, the related specific data will be also updated accordingly.




/35

MAO-CRM-P14 Reports To access reports linked to TLs, from main menu:

- Select Routine maintenance menu � TL, then the A/C and related TL.

- Click on the right top of the screen - Select the report in the menu

If you want to cancel the print-out request or if you made an error, click again to leave report menu.

routine maintenance technical log - apsys

Documents