Maintenance & Reliability worked example
Spare Parts Reorder Point with reorder trigger quantity of 70 units: a worked example
This worked example runs the spare parts reorder point numbers for a tougher week than the baseline: reorder trigger quantity of 70 units instead of the typical 140 units. Translate lead-time demand, daily usage, and a safety multiplier into protected reorder coverage for a critical spare.
The inputs for this scenario
- Reorder trigger quantity: 70 units (the input this scenario stresses; the baseline uses 140)
- Average daily spare demand: 4 units / day (held at the documented default)
- Reorder safety multiplier: 1.1 x (held at the documented default)
Working through the calculation
- The calculation starts from the formula this tool documents: Base lead-time coverage = reorder trigger quantity รท average daily spare demand.
- Protected Reorder Coverage works out to 15.91 days at these inputs, and this is the headline figure for the scenario.
- Base Lead-Time Coverage works out to 17.5 days at these inputs.
- Reorder Trigger Quantity works out to 70 units at these inputs.
- Average Daily Demand works out to 4 units / day at these inputs.
How this compares with the baseline
- Against the tool's baseline example, where reorder trigger quantity sits at 140 units and the headline result is 31.82 days, this scenario comes in 50% below the baseline at 15.91 days.
- Use it when validating a CMMS min/max setting or asset BOM reorder point against the actual replenishment lead time for that spare. A result at this level usually justifies acting on the stressed input before touching anything else, because every other figure in the table is downstream of it.
Results at a glance
- Protected Reorder Coverage: 15.91 days (headline result)
- Base Lead-Time Coverage: 17.5 days
- Reorder Trigger Quantity: 70 units
- Average Daily Demand: 4 units / day
Run it with your numbers
- To rerun this with your own numbers, open the live Spare Parts Reorder Point calculator, set reorder trigger quantity to your actual value, and adjust the remaining inputs to match your operation.
Last reviewed 2026-05-12.