Jump to text
On this page
Copy and source
Original source · lines 97–111
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

MNT-FLEET — Learn from maintenance history

  • Situation: One pump group has fewer recorded failures, a proposed monitoring service promises improvement, and an upcoming task already lacks an applicable spare.
  • Question: Which programme, task or support change does the available evidence warrant?
  • First useful result or blocker: A comparable fleet account and supported retain or change decision, or the event, exposure or applicability discrepancy that prevents the relevant conclusion.
  • Start with: MNT.13 - Coordinate the Maintenance Programme and Fleet Learning, using MNT.3 and MNT.12 only where the failure or history basis needs work.
  • Stop or return: Retain an adequate current policy or fix a known support deficiency on its existing basis. Further inquiry is selected only for a worthwhile attainable answer.
  1. Make the comparison mean the same thing. In the 48-pump case, twenty pumps have four relevant failures over 20,000 operating hours; 28 have six over 56,000 hours. The crude rates are 0.20 and approximately 0.107 events per 1,000 hours. Counts favor the first group, rates the second. MNT.3 establishes what counts as a failure, and MNT.12 attaches events and exposure to the components and intervals to which they belong.
  2. Propagate a corrected history before changing the policy. If two of the second group’s six records are preventive removals, correct that event classification and the affected rate. Duty, component histories and selection into the groups still limit any causal policy comparison.
  3. Keep a policy decision separate from a support decision. Use MNT.2 - Select and Reopen the Maintenance Policy to decide whether to retain the current task. You can retain it where the failure-and-response basis remains adequate. The weak comparative data do not establish that adequacy. With MNT.13 you can separately decide to correct the known shortage, using MNT.5 to establish readiness for the upcoming task. A broader redesign of recurring support returns to the relevant enabling-arrangement practice; it need not wait for a causal fleet study.
  4. Compare the proposed method at the response it can improve. Use MNT.14 - Compare Maintenance Methods for Retention or Change to compare the online predictor with current periodic interpretation at the same maintenance use. In its case, existing provider information shows no improvement in feasible response: the same specialist and part constraints dominate, while integration and interpretation add work. Retain the present method for that use and address support. For another family, rapidly changing condition and an available response may warrant reopening the comparison.

The policy alternatives also depend on the function. An obvious, low-consequence indicator failure may justify deliberate run-to-failure; a hidden protective-function failure needs an applicable means of finding it.