Operator maintenance programs
Aircraft operators define operator maintenance programs (OMPs) and associated maintenance checks for each type of aircraft type in their fleet. When the maintenance program is approved by the aviation authority, the OMP is activated and becomes the controlling document for maintenance of that aircraft.
In the Maintenance Task Library (MTL) application, MRO operators can import copies of OMPs that control the maintenance of aircraft that they are servicing for customers. The imported OMPs can be viewed and managed in the OMP application.
Aircraft operators can define and revise OMPs in the OMP application before submission to aviation authorities for approval.
An OMP record is associated with at least one model and is effective, by default, for all aircraft or equipment that are associated with the specified model or models. Maintenance changes to the effective aircraft and equipment are validated against the models to ensure continuing compliance. When an OMP is in draft status, you can remove selected aircraft from the effectivity list.
An OMP typically contains many hundreds of OMP tasks that have associated master task cards. The list of OMP tasks can be compiled from one or more of the following sources:
- Maintenance Task Library (MTL) records that contain task information from maintenance planning documents (MPDs) or other sources
- Master task card records that are maintained in the Master Task Cards application
In an OMP, you can create and manage a sampling program of maintenance tasks for an aircraft fleet. To create a sample group, you indicate an aircraft in your fleet as a sample aircraft. The sample group is approximately 20 percent of the aircraft in the fleet. The sample group contains the oldest aircraft and the newest aircraft in your fleet.
You determine which aircraft in the fleet are the oldest and the newest based on the manufacture date and manually select the aircraft that are in the sampling program. After you indicate that an aircraft is part of the sampling program, you define the sample interval and sample threshold of the maintenance tasks in the Master Task Card application.
In OMPs, maintenance checks group related tasks that occur at the same intervals. In Maximo® for Aviation, a check is a type of master task card that you configure in the OMP application. On the Checks tab, when you add a check, you add OMP tasks to the check content. Because the check is a master task card, when the OMP tasks are due, work orders are automatically generated and warnings are issued when work is about to become due.
The checks in an OMP are typically organized in a hierarchy, where the first level of checks are the lowest and the fourth level of checks are the highest. You can use a naming convention to distinguish the check hierarchy, for example, A checks are the lowest, then B and C, and D checks are highest. Lower checks are, typically, frequent light checks that can be completed at a line maintenance location. Higher checks are often heavy maintenance tasks that occur less often and require the aircraft to be in a hangar for a number of weeks.
To configure the hierarchy of checks for an OMP, on the Checks tab, you configure higher and lower relationships with other checks on the OMP record. For example, if you relate checks A and B, because A is the lower check, when check A runs, check B does not run. When check B runs, check A also runs.
After you define the higher and lower checks, you can create a check loop that breaks down the series of maintenance task requirements into a sequence of related checks. You associate higher and lower checks with the check loop and specify the order of the checks in the sequence. You also specify the frequency at which the maintenance tasks occur in the check loop. When a check loop is completed, it repeats.
Example check configuration
The following table shows example checks:
Check ID | Frequency in flight hours | Number of master task cards |
---|---|---|
A1 | 600 | 70 |
A2 | 1200 | 28 |
A3 | 1800 | 21 |
A4 | 2400 | 18 |
The following table shows an example of check loop frequency:
Interval flight hours | Cumulative flight hours | Higher checks | Check content (lower checks) | Number of master task cards |
---|---|---|---|---|
600 | 600 | A1 | A1 | 70 |
600 | 1200 | A2 | A1, A2 | 98 |
600 | 1800 | A3 | A1, A3 | 91 |
600 | 2400 | A4 | A1, A2, A4 | 116 |
600 | 3000 | A5 | A1, A3 | 91 |
600 | 3600 | A6 | A1, A2, A3 | 119 |
600 | 4200 | A7 | A1 | 70 |
600 | 4800 | A8 | A1, A2, A4 | 116 |
600 | 5400 | A9 | A1, A3 | 91 |
600 | 6000 | A10 | A1, A2 | 98 |
600 | 6600 | A11 | A1 | 70 |
600 | 7200 | A12 (Sequence repeats from A01) | A1, A2, A3, A4 | 137 |