<< Click to Display Table of Contents >> Navigation:  Main modules > M.Requirements > Associated procedures > 5-3-4-1 Procedure: Implement a maintenance programme

The implementation of a maintenance programme into AMS should be considered as a critical process, as many functions will rely on this implementation. When defining how a maintenance programme will be implemented, always keep in mind the following rules:

 

- AMS is designed to represent the reality on the field. Do not implement as a MR an intermediary document like a MRB item or a MPD item unless the next rule is satisfied. As an example, if an MPD item is requesting a task X to be performed every 2,000 cycles and another MPD item is requesting the same task X to be performed every 12 months, then there is only one task (one MR) with a repeat interval of 2,000 cycles and 12 months, whichever occurs first.

 

- a MR is a field document: the one which is effectively launched to production or to the repair shop, with all details about the accomplishment instructions (approved maintenance data).

 

 

The implementation of a Maintenance Programme differs from an aircraft manufacturer to the other (and sometimes from an aircraft type to the other, for the same manufacturer). It is not possible to state what document should be the one to set as MR for any aircraft type but, in all cases, this document must be the one ordered to production.

 

Example: The aircraft certification (maintenance analysis) relies on a MSG3 analysis. The results of this analysis is exposed in the MRB documents which defines the thresholds and repeat intervals for each task. This MRB document is approved by the original certifying authority. To help his customers with the implementation of their maintenance programmes, the aircraft manufacturer designed a MPD (Maintenance Planning Document) which uses the information stated in the MRB and also additional information like repetitive ADs, line maintenance operations, etc. This document (MPD) is also approved by the original certifying authority. These MPD tasks are then detailed to provide the accomplishment instructions and TC (Task Cards). In that case, the field documents are the task cards and the implementation of the maintenance programme into AMS should start from the Task Cards. The MPD and MRB items will be recorded as reference document of each MR to build a dynamic cross reference index (refer to MRs by doc.ref.)

 

 

In case of doubt regarding how to implement a particular maintenance programme, do not hesitate to contact us.