# P-F Interval Inspection Frequency Calculator

> Source: https://netray.co/tools/condition-monitoring-p-f-interval-inspection-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Work out how often to inspect so you catch a potential failure before it becomes a functional failure, and what each inspection interval costs.

## Category

maintenance

## Industry

Manufacturing

## Audience

- Reliability engineer
- Maintenance manager
- Condition monitoring analyst

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### P-F interval

**Key:** pf

**Type:** number

**Default:** 60

**Min:** 1

**Step:** 1

**Unit:** days

**Help:** Typical time from the first detectable sign of failure to functional failure.

#### Time needed to react

**Key:** lead

**Type:** number

**Default:** 14

**Min:** 0

**Step:** 1

**Unit:** days

**Help:** Parts, planning, scheduling and a downtime window to fix it properly.

#### Inspection interval

**Key:** insp

**Type:** number

**Default:** 30

**Min:** 1

**Step:** 1

**Unit:** days

#### Detection probability per inspection

**Key:** d

**Type:** slider

**Default:** 85

**Min:** 10

**Max:** 100

**Step:** 1

**Unit:** %

**Help:** Chance that an inspection finds the defect if it is present.

#### Developing failures per year

**Key:** events

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 1

#### Cost when caught early

**Key:** c_plan

**Type:** number

**Default:** 2500

**Min:** 0

**Step:** 100

**Unit:** $

#### Cost when missed (functional failure)

**Key:** c_fail

**Type:** number

**Default:** 12000

**Min:** 0

**Step:** 100

**Unit:** $

#### Cost per inspection

**Key:** c_insp

**Type:** number

**Default:** 80

**Min:** 0

**Step:** 5

**Unit:** $

**Outputs:**

#### Usable detection window

**Key:** window

**Expr:** max(pf - lead, 0)

**Format:** days

**Description:** P-F interval minus the time you need to react.

#### Inspections inside the window

**Key:** n

**Expr:** window / insp

**Format:** decimal

#### Probability the defect is missed

**Key:** p_miss

**Expr:** pow(1 - d / 100, floor(n)) * (1 - (n - floor(n)) * d / 100)

**Format:** decimal

#### Probability caught in time

**Key:** p_catch

**Expr:** (1 - p_miss) * 100

**Format:** percent

**Primary:** true

#### Rule-of-thumb interval

**Key:** rec

**Expr:** window / 2

**Format:** days

**Description:** Half the usable window, a common starting point.

#### Annual inspection cost

**Key:** insp_cost

**Expr:** c_insp * 365 / insp

**Format:** currency

#### Expected annual failure and repair cost

**Key:** fail_cost

**Expr:** events * ((1 - p_miss) * c_plan + p_miss * c_fail)

**Format:** currency

#### Total annual cost

**Key:** total

**Expr:** insp_cost + fail_cost

**Format:** currency

**Primary:** true

**Chart:**

#### Annual cost vs inspection interval

**Type:** line

**X:** insp

**From:** 5

**To:** 90

**Steps:** 30

**Series:**

- total

**Disclaimer:** Assumes the inspection falls at a random point relative to the onset of the defect and that detection chances are independent between inspections.

## Content

**Intro:** The P-F interval is the time between the first detectable sign of a failure and the failure itself. Inspect more often than that window allows you to react, and you are only watching it happen. This calculator shows the odds of catching a defect in time and what each interval costs.

**Sections:**

#### How to use it

**Body:** Enter the P-F interval for the failure mode, the days you need to react (parts, planning, a downtime window), your inspection interval, and the detection probability of the method. Then add costs for an early catch, a missed failure and a single inspection. The tool reports the chance of catching the defect in time and the total annual cost, and the chart shows where cost bottoms out as you change the interval.

**Bullets:**

- P-F differs by technique: vibration, oil analysis and thermography all see defects at different stages.
- Detection probability below 100 percent is realistic, especially for walk-around checks.
- Be honest about the reaction time, it is the most overlooked input.

#### The logic

**Body:** A defect is only useful to find if you can still act. The usable window is P-F minus reaction time. Inspections inside that window are window divided by interval. With detection probability d and n whole inspections inside the window, the miss chance is (1 - d)^n, with an adjustment for the fractional inspection that may or may not land in the window. Reliability-centered maintenance guidance commonly suggests an interval of about half the P-F interval, and this tool adds the reaction time to that idea.

#### Reading the result

**Body:** If the catch probability is low even at short intervals, the technique is the problem, not the frequency, so look for a method with a longer P-F or better detection. The cost chart usually shows a shallow minimum. Going much shorter than the minimum adds inspection cost without gaining much protection, and going much longer raises failure cost steeply.

#### Common mistakes

**Body:** Using the interval from the vendor manual without checking P-F for your operating conditions, forgetting that planning and parts lead time shrink the window, and treating continuous monitoring as perfect are the main errors. In an ERP or CMMS, condition triggers should create notifications or work orders automatically, otherwise a detected defect still waits in someone's notebook.

**Cta:** Netray can help connect sensor or inspection results to work order creation in your ERP so a finding turns into a planned job. The calculator is complete on its own.

**Faq:**

#### How do I find the P-F interval?

**Answer:** Use failure history where the first detectable sign and the failure date are both recorded, or ask experienced technicians and vendors. Test the sensitivity by sweeping the chart, because small errors in P-F move the optimum.

#### Why is half the P-F interval a rule of thumb?

**Answer:** If you inspect at half the interval, you are guaranteed at least one inspection inside the window, and usually two if you subtract reaction time carefully. It trades some extra inspections for protection against a missed reading.

#### What if reaction time exceeds the P-F interval?

**Answer:** Then the window is zero and inspection cannot prevent the failure. Shorten the reaction time with kitted spares and standby planning, or switch to a method with a longer P-F.

#### Does this replace RCM?

**Answer:** No. It supports the interval decision inside a reliability-centered maintenance study, after you have decided that condition monitoring is the right task for the failure mode.

## Search terms

p-f interval calculator, inspection frequency calculator, condition monitoring interval, potential failure to functional failure interval, vibration analysis frequency, condition based maintenance interval, how often to inspect equipment, rcm p-f interval

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json