Why one curve runs your whole PdM program

Most machine failures don't happen – they develop. A bearing doesn't explode out of nowhere: a defect initiates, then announces itself in ultrasound, then in vibration spectra, then in oil debris, then in heat, then in noise – and finally the machine stops. The P-F curve is simply that story drawn as a graph, and it answers the two questions every predictive maintenance (PdM) program lives or dies by: which technology can see the failure coming, and how often must we look?

The curve appeared in Nowlan & Heap's 1978 RCM report and was popularized by John Moubray in RCM II. Doug Plucknette – creator of RCM Blitz® and one of the most under-rated authors in the field – then spent two decades pointing out what the classic curve hides: by the time you're watching for "P", most of the die is already cast. His D-I-P-F curve (2006) completes the picture.

Reading the P-F curve

The vertical axis is the asset's condition (its resistance to failure); the horizontal axis is time. Two points matter: P, where a developing failure first becomes detectable, and F, where the asset can no longer do its job.

CONDITION / RESISTANCE TO FAILURE → TIME → Defect initiates (invisible) P — failure becomes detectable F — functional failure Ultrasound Vibration analysis Oil analysis / wear debris Thermography Audible noise Hot to touch P-F interval — your window to plan the repair
Fig. 1 — The classic P-F curve, redrawn by Rob Reliability after Nowlan & Heap (1978) and Moubray (1997). The earlier on the slope a technology detects the defect, the longer your warning window. Technology order is typical for rolling-element bearings; it varies by failure mode.

Three things follow directly from the picture:

  • Each technology has its own P. Ultrasound and vibration see a bearing defect months before heat or noise do. "We do thermography monthly" is not a strategy until you know what failure modes thermography can actually catch, and how late on the curve it sits.
  • The P-F interval is failure-mode specific – not asset specific. The same pump has a months-long P-F interval for bearing wear and a seconds-long one for a coupling shear. That's why task lists must be built per failure mode (the RCM discipline – see our RCM II summary).
  • Detection buys planning time, not life. Finding the defect at P doesn't make the machine last longer – it converts a 2 a.m. breakdown into a planned, kitted, scheduled repair. The value is the difference between those two costs.

Sizing inspection intervals from the P-F interval

The rule is mechanical: to be confident of catching the failure between P and F, your inspection interval must be comfortably shorter than the P-F interval – the common rule of thumb is half the P-F interval or less. It's the same logic as medical screening: if a condition takes years to go from detectable to dangerous, an annual check-up will catch it in time. Your inspection just has to come around faster than the failure can develop.

P F ← P-F interval → Inspect once per P-F interval defect initiates just after a visit… inspection 1 — all clear inspection 2 — too late ✗ can miss the whole window Inspect every ½ P-F interval same bad luck, same defect… caught inside the window — repair planned ✓ always one look inside P–F same machine, same defect, same technology — only the inspection interval changed
Fig. — Why "half the P-F interval" is the rule of thumb, drawn by Rob Reliability. With an interval equal to the P-F interval, a defect that initiates just after a visit develops and fails before the next one. At half the interval, at least one inspection always lands inside the detection window.
TechniqueTypical warning it gives*Sensible route interval*
Ultrasound (bearing/lube defects)monthsmonthly
Vibration analysisweeks – months2 weeks – monthly
Oil / wear-debris analysisweeks – monthsmonthly – quarterly
Thermography (electrical, mechanical)days – weeksweekly – monthly
Operator senses (noise, heat, leaks)hours – daysevery shift
Continuous online sensors (IIoT)whatever the physics allowscontinuous

*Indicative orders of magnitude for common rotating-equipment failure modes – your machines, speeds and duty will differ. The logic, not the numbers, is the takeaway.

This is also where Plucknette's field criticism lands hardest. In The Introduction of the I-P Interval, he describes PdM programs set up as generic technology routes – monthly vibration on everything, quarterly thermography on everything – without a single inspection naming the failure mode it was looking for. The assets kept failing. A PdM task that doesn't know its failure mode and its P-F interval is a ritual, not a strategy.

And continuous monitoring changes the economics, not the logic: an IIoT sensor is just an inspection whose interval has gone to zero. It widens the usable warning window for fast-developing failures – it does nothing about defects that haven't initiated yet. For that, read on.

What Plucknette added: the D-I-P-F curve

In 2006, after readers pushed back on his article "Expanding the Curve", Plucknette drew the version he'd been teaching in RCM Blitz® training: add D (Design) and I (Installation) to the left of the P-F curve. The result – the D-I-P-F curve, also called the asset lifecycle curve – shows the whole life of the asset, not just its death.

PROACTIVE DOMAIN — build reliability in MANAGE THE FAILURE ASSET LIFE → D Design inherent reliability is set here I Installation precision or defects from day one P F I-P interval — extended by precision work, lost to defects P-F interval
Fig. 2 — The D-I-P-F (asset lifecycle) curve, redrawn by Rob Reliability after Doug Plucknette, "Completing the Curve" (Reliabilityweb / Uptime Magazine; first drawn 2006). Design sets the ceiling; installation decides whether you start at it or below it; the defect-free run from I to P is where life is won or lost.

The proactive domain (D to P) is where Plucknette says the real return on investment lives, and what belongs there reads like a checklist for a capital project done right: RCM analysis from the design phase, FMEA, reliability block diagrams, design standards, equipment hierarchy and criticality analysis, supplier agreements, precision installation and commissioning – then the maintenance plan that the analysis produced, executed with on-condition monitoring, PM and operator care.

The I-P interval: where the money actually is

The classic P-F curve invites you to invest in detection. The D-I-P-F curve asks a better question first: why did the defect initiate at all?

The distance between I (installation) and P (first detectable defect) is not fixed by fate. It is stretched or shredded by things fully under your control:

  • Precision installation – laser alignment, balancing to grade, correct torque, proper base/grout. A misaligned coupling can cut bearing life by an order of magnitude before the machine has run a week.
  • Lubrication discipline – right lubricant, right quantity, right interval, kept clean and dry. Lubrication issues are consistently among the top contributors to premature bearing failure (see our SKF summary).
  • Operating within design envelope – cavitation, dead-heading, overloads and frequent starts all consume the I-P interval silently.
  • Defect elimination culture – treating every early detection as a question ("what put this defect in?") instead of a victory lap for the vibration analyst.

The uncomfortable truth

A site that detects every failure at P but installs sloppily will spend its life doing well-planned repairs at an impressive rate. A site that extends I-P doesn't need most of those repairs at all. Condition monitoring is your insurance policy; precision work and defect elimination are your pension fund. Most plants over-buy the first and barely fund the second – and that mistake is invisible in the classic P-F picture.

What this means for your program

A practical reading of both curves, condensed.

  1. Map PdM tasks to failure modes. Every inspection on every route should name the failure mode it targets and the technology's position on that mode's P-F curve. Delete the ones that can't answer.
  2. Size intervals from the P-F interval – at most half of it. If the P-F interval is shorter than any practical route, that's a case for an online sensor or a redesign, not for more frequent clipboards.
  3. Put IIoT where the curve justifies it. Continuous monitoring earns its cost on critical assets with fast-developing or high-consequence failure modes – not as confetti over the whole plant.
  4. Fund the left of the curve. Precision standards for every rebuild and installation, lubrication excellence, commissioning acceptance criteria (vibration signatures at handover, alignment records). This is reliability you don't have to monitor for.
  5. Close the loop with defect elimination. Every P-detection feeds a "why did it initiate?" review. The goal is fewer detections next year, not more.

References & further reading

This summary is original explanatory writing. All concepts belong to their authors – go to the sources.

  1. Plucknette, D. "Completing the Curve." Uptime Magazine / Reliabilityweb.com. Read on Reliabilityweb (free)
  2. Plucknette, D. "The Introduction of the I-P Interval." Reliabilityweb.com. Read on Reliabilityweb (free)
  3. Plucknette, D. Reliability Centered Maintenance Using RCM Blitz™. Reliabilityweb.com Press, 2009. ISBN 978-0-9820517-7-1.
  4. Plucknette, D. "Expanding the Curve." Uptime Magazine, June/July 2006 – the article that started the debate.
  5. Nowlan, F.S. & Heap, H.F. Reliability-Centered Maintenance. United Airlines / DoD, 1978 – origin of the P-F curve. DTIC record (free)
  6. Moubray, J. RCM II, 1997 – the P-F interval and on-condition task logic. Our summary

Disclaimer. This page is an independent educational summary written entirely in Rob Reliability's own words. It is not affiliated with, sponsored by or endorsed by Doug Plucknette, Allied Reliability or any related publisher. No text from the original articles is reproduced; the P-F and D-I-P-F curves shown here are our own original drawings of concepts that are part of the public technical literature. Trade names and trademarks remain the property of their respective owners, used solely to identify the work being discussed. If you are a rights holder and have any concern about this page, contact us at hello@robreliability.com and we will address it promptly.

Done for you

Want this applied to your site?

P-F thinking is exactly how we re-derive PM intervals from your data - useless tasks killed, gaps covered, savings quantified.

Maintenance Strategy Optimization