Static discussion and calculation aid · Maintenance Data Pro
Use this with a maintenance or reliability practitioner, operations, finance and the accountable site manager. It holds the assumptions behind a claim so people can check and accept them. Copy the Markdown version into your working document, replace the fictional values and complete the blank prompts with your team. Calculate each result and check it independently; the HTML is a static reading/printing view. The completed example is entirely fictional. Technical acceptance and the improvement decision belong to the accountable team.
1. Define the comparison before filling in a benefit
| Field | Completed fictional example | Your proposal |
|---|---|---|
| Decision and owner | Whether to introduce the proposed change to pump repair arrangements. Nina, site manager, owns the decision with the accountable team. Technical acceptance is required separately. | |
| Baseline records | 2026 intervention records, issued parts, contractor invoices, employee hours, production-loss log and unavailable intervals. | |
| Counterfactual | Existing arrangement continues from 1 January to 31 December 2027. Same duty, prices and workload as 2026. | |
| Proposed period | 1 January to 31 December 2027. Full operation of the change from day 1; £4,000 setup charged within the same period. No ramp-up assumed. | |
| Currency and price basis | GBP (£), constant fictional prices, excluding VAT. No exchange conversion, tax, financing or discounting. | |
| Boundary | Pump package and incremental line output. No plant-wide improvement inferred. Avoided charges and additional programme costs are separate. | |
| Lost-output treatment | Extra output assumed saleable, capacity elsewhere sufficient, no later catch-up of baseline lost output. | |
| Other scope | No safety/environmental/life-extension valuation. Fixed salary bill unchanged. No cancellation fees or additional implementation outage assumed; check before use. |
2. Put a record and an owner beside each input
The records below are stipulated fictional observations, not actual source exports. “Assumption” means the example has no observed result supporting that value. For your case, attach approved record references, dates, evidence quality and an input owner's acceptance. Store actual sensitive records in approved company storage, outside this review package.
| Input | Fictional value and status | Check and input owner |
|---|---|---|
| Repeat interventions | 6 in baseline 2026, stipulated observation | Leah, reliability engineer: work-order/event identity, completeness, scope and repeat-failure classification |
| Issued parts per intervention | £2,000, stipulated observation | Finance: issues versus purchases and inventory timing; would payments fall in the comparison year? |
| Variable contractor repair support per intervention | £1,000, stipulated observation | Finance: invoice basis; no employee salary or fixed retainer included; no cancellation fee assumed |
| Employee hours per intervention | 12, stipulated observation | Planner and Leah: actual time scope, retained staff, no overlap with contractor hours |
| Employee allocation rate | £50/hour, supplied rate for illustration | Finance: allocation only; no salary payment avoided in this case |
| Package-unavailable hours | 48, stipulated observation | Operations: repair/outage boundaries, not yet a line-loss measure |
| Standby-protected intervals | 12 hours, stipulated observation | Operations: full duty maintained; intervals separate from shutdown hours |
| Intervals inside planned shutdown | 12 hours, stipulated observation | Operations: no extra line loss; no restart benefit assumed |
| Net line loss | 48 − 12 − 12 = 24 hours | Operations: reconcile intervals and competing events; each line-loss hour counted once |
| Avoided interventions | 3 in central case, assumption | Leah: technical mechanism, evidence of effectiveness, timing, side effects and plausibility |
| Recovered line hours | 12 in central case, separate assumption | Operations with Leah: which events/hours affected, production constraints, no catch-up, no double counting |
| Saleable output rate | 10 units per recovered line hour, assumption | Operations/commercial: actual incremental output and demand |
| Unit sales price | £130, assumption | Commercial/finance: correct product, period and price basis |
| Additional variable cost | £30 per unit, assumption | Finance/operations: extra materials, energy and other costs to make those units; no duplicated support cost |
| Added annual support | £6,000 in comparison year, assumption | Programme owner and finance: scope, invoices, no overlap with avoided repair support |
| Setup | £4,000 in comparison year, assumption | Programme owner and finance: full additional first-year payments, introduction timing |
3. Keep spending, output and capacity separate
| Calculation | Fictional working | Result and meaning |
|---|---|---|
| Baseline variable repair spend | 6 × (£2,000 + £1,000) | £18,000 |
| Baseline employee capacity | 6 × 12 hours; 72 × £50 | 72 hours; £3,600 allocated labour value. Retained salary is not avoided spend. |
| Unchecked sales estimate | 48 hours × 10 units/hour × £130/unit | £62,400. Uses asset hours as if all were lost saleable production. Do not use as accepted benefit. |
| Unchecked headline | £18,000 + £3,600 + £62,400 | £84,000. Assumes all events prevented, adds fixed employee value and gross sales, omits programme cost. |
| Avoided payments | 3 × (£2,000 + £1,000) | £9,000 conditional avoided spend |
| Released employee capacity | 3 × 12 hours | 36 hours, held outside the monetary benefit. £1,800 at allocation rate is not added. |
| Added programme payments | £6,000 + £4,000 | £10,000 |
| Repair and programme payment change, proposal minus baseline | £10,000 − £9,000 | £1,000 increase in these payments, before the extra production costs below. |
| Additional saleable output | 12 hours × 10 units/hour | 120 units |
| Additional sales | 120 units × £130/unit | £15,600 |
| Additional variable production cost | 120 units × £30/unit | £3,600 |
| Modelled contribution | 12 hours × 10 units/hour × (£130 − £30) per unit | £12,000. Use this once, not sales plus contribution. |
| First-year net modelled benefit | £9,000 + £12,000 − £6,000 − £4,000 | £11,000 conditional on the accepted inputs |
| Total expenditure change in this comparison | £10,000 − £9,000 + £3,600 | £4,600 increase including extra variable production cost |
| Cross-check using sales and total expenditure | £15,600 − £4,600 | £11,000. Same benefit; production cost deducted once. |
General formulas for a simple one-period comparison:
- Avoided expenditure = avoided interventions × variable payment per intervention.
- Released employee hours = avoided interventions × retained employee hours per intervention. Keep outside cash savings unless a specific payment change is accepted and reconciled.
- Modelled contribution = recovered net line hours × additional saleable units per hour × (unit sales price − additional variable cost per unit).
- Repair and programme payment change = added programme payments − avoided repair payments. A positive result here means these payments increase.
- Total expenditure change in this comparison = repair and programme payment change + additional variable production cost. Net modelled benefit can also be checked as additional sales − this total expenditure change.
- Net modelled benefit = avoided expenditure + modelled contribution − added programme payments.
Don't subtract a fixed cost twice or add a released-hours valuation on top of an accepted payroll reduction for those same hours. The formulas do not establish whether an intervention can safely be removed, a failure will be prevented or output can be sold.
4. Show uncertainty without pretending to know its probability
These are paired editorial scenarios. There is no probability estimate. Avoided interventions and recovered line hours require separate evidence; proportional values here are an illustration, not a physical rule.
| Scenario | Avoided interventions | Recovered line hours | Avoided repair payments | Contribution | Added programme payments | First-year net modelled benefit |
|---|---|---|---|---|---|---|
| Less effective | 1 | 4 | £3,000 | £4,000 | £10,000 | −£3,000 |
| Central | 3 | 12 | £9,000 | £12,000 | £10,000 | £11,000 |
| More effective | 4 | 16 | £12,000 | £16,000 | £10,000 | £18,000 |
For your case, test a later start, fewer recovered saleable hours, higher introduction/support costs and different prices. Keep periods and cost boundaries consistent. A zero-benefit result can be a useful check. Record exclusions rather than assuming excluded effects have no value or no risk.
| Uncertain assumption | Evidence needed | Input owner | Alternative value / scenario | Does it change the decision? |
|---|---|---|---|---|
5. Accept the assumptions and plan the check
| Acceptance / follow-through | Person and date | Record or action |
|---|---|---|
| Baseline and event identities accepted | ||
| Avoidable payments and added cost scope accepted by finance | ||
| Net line hours, incremental output and demand accepted | ||
| Technical acceptability and site requirements accepted | ||
| Double counting checked against other projects and events | ||
| Main assumptions and alternatives accepted by accountable team | ||
| Improvement decision and basis accepted by accountable manager | Proceed / revise / gather evidence / do not proceed, with reason | |
| Baseline or counterfactual adjusted for duty/price/workload changes | ||
| Actual invoices, events, net losses and use of released hours reviewed | Name owner, review date and comparison method |
Nina's role in the fictional example shows where decision accountability belongs. These blank fields do not record an actual approval. Compare actual results with an agreed counterfactual and explain changed conditions; a lower bill or fewer failures alone doesn't prove the proposed change caused it.