Aftermarket, Field Service & Service Parts worked example
Parts Availability Risk Score with customer downtime impact of 23 1-10: a worked example
This scenario runs the parts availability risk score calculation on the strong side: customer downtime impact of 23 1-10, with every other input held at its documented default. a spare parts planner needs to rank parts that could disrupt field service or customer uptime
The inputs for this scenario
- Customer downtime impact: 23 1-10 (raised for this scenario; the documented default is 9)
- Stockout likelihood: 7 1-10 (unchanged)
- Recovery difficulty: 6 1-10 (unchanged)
Working through the calculation
- Applying the documented formula (Parts availability risk score = service impact severity × stockout likelihood × detection or recovery difficulty) to the inputs above produces each figure below.
- At this operating point the engine returns 13.15 score for parts availability risk score, the number this scenario is built around.
- At this operating point the engine returns 23 1-10 for customer downtime impact.
- At this operating point the engine returns 7 1-10 for stockout likelihood.
- At this operating point the engine returns 6 1-10 for recovery difficulty.
How this compares with the baseline
- Against the tool's baseline example, where customer downtime impact sits at 9 1-10 and the headline result is 7.55 score, this scenario comes in 74.17% above the baseline at 13.15 score.
- Use it during service-parts planning reviews to rank SKUs for stocking, sourcing, or escalation decisions before customers experience downtime. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Parts availability risk score: 13.15 score (headline result)
- Customer downtime impact: 23 1-10
- Stockout likelihood: 7 1-10
- Recovery difficulty: 6 1-10
Run it with your numbers
- Every input above is editable in the live Parts Availability Risk Score calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.