Cut Stoppage Cost With Four Plant Records for Maintenance Managers

The custo de paragem, or cost of a stoppage, equals lost contribution margin plus restart and recovery costs, and most plants can calculate it today using four records they already hold: production logs, product costing sheets, payroll data and procurement invoices. The immediate step is to open a single event file, one row per stoppage, and pull the output and contribution figures tied to it.

TL;DR:

• Use actual output before the stoppage, not rated speed, and verify current contribution margins because stale costs can understate losses.
• Subtract recovered production from the loss, add restart costs such as scrap, overtime, and rush freight, and report fixed overhead separately.
• Keep each event open for 60 to 90 days after restart, linking invoices, overtime, scrap, and repairs to one identifier so late costs remain traceable.
• Rank assets by annual cost, not failure count: four stoppages at £4,680 each create £18,720 in annual exposure, exceeding ten £500 events at £5,000.

Table of Contents

• 1. The working formula and what each input means
• 2. Where to find and validate the inputs
• 3. A worked example you can copy into a spreadsheet
• 4. Hidden cost categories that most estimates miss
• 5. The metrics that feed the cost calculation
• 6. Operational levers that bring the cost down
• 7. Making the cost visible and keeping it governed
• What finance and maintenance tend to disagree on
• Capturing this data without a parallel spreadsheet
• FAQ
• Sources

1. The working formula and what each input means

The formula at the centre of this method comes from the Siemens white paper on the true cost of downtime, which argues that contribution margin, not gross sales price, is the correct base for lost-production cost. Contribution margin is price minus variable cost, so it strips out the fixed overheads that keep running whether or not the line is down.

The working equation is:

Units lost × contribution per unit × hours lost × (1 − share recovered) + restart/recovery costs

Each term carries its own logic.

• Units lost per hour comes from the rated or actual output speed of the line during the stoppage window.
• Contribution per unit is drawn from the product costing sheet: selling price minus direct material and variable processing cost.
• Share recovered accounts for output clawed back through overtime, speed-up runs or weekend shifts after the event; a figure of 0.3 means 30% of lost units were eventually produced elsewhere in the schedule.
• Restart and recovery costs cover everything spent getting the line back to validated output: changeover labour, scrap from the first runs, quality re-checks and any expedited parts.

Fixed costs stay out of the main calculation and get reported separately, because folding them in inflates the apparent loss without changing what management can actually recover through better maintenance or faster response.

2. Where to find and validate the inputs

Each variable in the formula maps to a specific system of record, and pulling from the wrong one is the most common source of error.

1. Production logs give actual output and the duration of the stoppage; use the shift log or the line’s historian, not the nameplate rated speed, because actual throughput before the stop is usually lower than the rated figure.
2. Product costing sheets from finance or engineering give contribution per unit; confirm the version is current, since material costs drift and an outdated sheet understates the loss.
3. Payroll records supply overtime and contractor hours used for recovery; tag these entries against the event so they are not lost in a general labour account.
4. Procurement invoices capture expedited freight, emergency parts and any premium paid for rush delivery; flag these at the point of purchase order, not months later during month-end close.
5. Quality and logistics records show scrap, rework and any late-shipment penalties tied to the same event window.

The most common pitfall is using rated speed instead of actual pre-stop output, which overstates lost units. A second is omitting fixed costs that the business would have paid anyway, which inflates the number and damages its credibility with finance. A third is failing to flag emergency purchases at the time they happen, which means they get buried in a general ledger line and never reach the event file.

Organise event tagging with a unique identifier for every stoppage, and attach every related work order, invoice, overtime entry and scrap ticket to that identifier so the cost stays traceable from first minute to final invoice.

Pro Tip: Keep the event file open for 60 to 90 days after the line restarts, because late invoices and collateral repairs routinely arrive weeks after the stoppage ends, as the Siemens report and a practical costing guide from Secured Engineers both recommend.

3. A worked example you can copy into a spreadsheet

Say a packaging line normally runs at 600 units per hour, the contribution margin per unit is £2.50, and an unplanned stop lasts 4 hours.

The calculation:

• Units lost: 600 × 4 = 2,400 units
• Units lost after recovery: 2,400 × (1 − 0.25) = 1,800 units
• Lost contribution: 1,800 × £2.50 = £4,500
• Total stoppage cost: £4,500 + £180 = £4,680

This single four-hour stop costs £4,680 once recovery and restart work are accounted for, almost all of it from lost contribution rather than repair labour, a pattern the Siemens white paper describes as typical: the per-hour price of downtime has risen across many sectors even where incident hours have fallen, because lines are more integrated and the value running through them per unit has gone up.

The result is sensitive to the recovery share assumption. Raise restart costs to £500, perhaps because a specialist part had to be flown in, and the total climbs to £6,500. Running both a best-case and worst-case recovery scenario alongside the base case gives management a defensible range rather than a single number that looks more precise than the underlying data supports.

The same spreadsheet scales to several lines or a whole-plant shutdown: sum the lost-contribution lines for every affected line, then add a single shared restart-cost line for shared services such as utilities or a central changeover crew. The Secured Engineers framework notes that splitting a large shutdown into short windows versus running work in parallel changes the recovery-share assumption substantially, so each shutdown option should be priced on this same basis before a decision is made.

4. Hidden cost categories that most estimates miss

A stoppage cost built only from repair labour and spare parts routinely understates the real figure. The Secured Engineers method recommends tracking cost across seven categories and keeping the event file open long enough to catch everything that lands late.

• Lost production, calculated as shown above from units, contribution and recovery share.
• Emergency parts and freight, found in procurement invoices tagged against the event.
• Overtime and contractor labour, pulled from payroll and timesheets for the recovery period.
• Scrap and rework, recorded in quality logs for the startup period after the fix.
• Late shipments and penalties, tracked in logistics or sales order records when a delay reaches a customer.
• Secondary damage, such as a bearing failure caused by the original fault running longer than it should have.
• Deferred planned work, the preventive tasks pushed back to free up technicians for the emergency, which carries its own future risk.

Attribute each category to the event identifier at the point it is recorded, not retrospectively, since the paper trail is far easier to reconstruct while invoices and timesheets are fresh. Some impacts, such as a damaged customer relationship or a missed delivery that cost no immediate penalty, cannot be documented in euros. Treat these as a qualitative risk note attached to the event file rather than forcing a number that cannot be defended.

5. The metrics that feed the cost calculation

Three metrics turn a single event cost into a prioritisation tool. Overall Equipment Effectiveness (OEE) multiplies availability, performance and quality; a drop in availability translates directly into the lost-hours term in the formula above, so tracking OEE by line shows where lost-contribution exposure concentrates. Mean Time To Repair (MTTR) and Mean Time Between Failures (MTBF) together describe how often an asset fails and how long each failure takes to fix, and multiplying average cost per event by failure frequency gives an annual expected loss for that asset.

A data-driven TPM framework recommends ranking assets by this economic exposure rather than by raw failure count, since a rarely failing asset with a high cost per event can outrank a frequently failing but cheap one.

• OEE links availability, performance and quality directly to the lost-hours term in the cost formula.
• MTTR shows how long each event takes to resolve, which drives the hours-lost variable.
• MTBF shows how often failures recur, which multiplies cost per event into an annual figure.
• Cost per event, tracked over several stoppages, validates whether a maintenance investment is actually reducing the number that matters.

Tracking these trends over several quarters, rather than a single incident, is what turns a one-off calculation into evidence that a maintenance investment paid off.

6. Operational levers that bring the cost down

Once assets are ranked by cost per event, the interventions follow a clear order of priority.

1. Prioritise by economic loss, not failure count. An asset with four stoppages a year at £4,680 each (£18,720 annual exposure) outranks one with ten minor stops at £500 each (£5,000 annual exposure), even though the second fails more often.
2. Invest in predictive maintenance where the exposure justifies it. A Portuguese case study at WEG Portugal found that autonomous preventive maintenance on a lathe increased availability by more than 10% and reduced the cost impact of stopped hours by more than 90% for the equipment studied, though the dissertation is explicit that these results are case-specific rather than a guaranteed outcome.
3. Fix the spares strategy for high-exposure assets. Stocking the parts that drive the longest MTTR on your top-ranked assets shortens recovery time without inflating general inventory.
4. Tighten contractor SLAs and production-maintenance coordination. A faster callout clause on the parts that matter most, paired with a shared view between production scheduling and maintenance planning, closes the gap between detection and repair.
5. Apply a structured TPM and condition-monitoring programme on the ranked list, following steps such as those in our guide to preventive maintenance for HVAC and industrial assets and our essential preventive maintenance steps.

An Industry 4.0 decision-support framework combining predictive maintenance, OEE and life-cycle cost analysis can sharpen the timing of these interventions further, but its own authors note that the approach depends on consistent, trustworthy sensor data and an agreed process for acting on alerts, limits that apply just as much to a smaller plant as to a fully instrumented one.

Pro Tip: Microstops under a minute are easy to miss on a manual log; a study on OEE tools in the cork industry recommends combining automatic machine signal thresholds with a simple cause taxonomy confirmed at shift handover.

7. Making the cost visible and keeping it governed

A single calculation proves the method works. A governance routine is what makes it useful month after month.

1. Create one row per event in a shared file, with the unique identifier, the formula inputs and the final total.
2. Keep each event open for 90 days before closing it, so late invoices and secondary repairs get captured rather than written off elsewhere.
3. Assign one owner per event, usually the shift or area maintenance lead, who is responsible for tagging procurement and payroll entries correctly.
4. Build business cases from three-event averages rather than a single incident, since one unusually cheap or expensive stop can skew a one-off number.

Our work order management guide covers the tagging workflows that make this kind of event-level tracking practical without a parallel manual spreadsheet for every line.

What finance and maintenance tend to disagree on

The friction we see most often between maintenance teams and finance is not the formula itself. It is the argument over whether to count fixed overhead in the lost-production figure, and whether an unrecovered unit should be valued at full sales price or at contribution margin. Maintenance teams, under pressure to justify a budget, lean toward the bigger, scarier number; finance, quite reasonably, rejects any figure that double-counts costs the business was paying anyway.

The honest answer favours finance’s instinct, and the Siemens framework backs it: contribution margin is the right base, full stop. A stoppage cost built on gross sales price looks dramatic in a slide deck and falls apart the moment a finance analyst checks it against the P&L, which does lasting damage to the credibility of every downtime figure that follows. The better argument for a bigger maintenance budget is not a bigger number. It is a defensible number, with its assumptions stated, that survives scrutiny and gets reused without a fight the next time a line goes down.

**

Capturing this data without a parallel spreadsheet

We built our platform around the idea that this kind of cost tracking should not depend on someone remembering to update a file. Work orders tagged to an event, technician time registration, inventory movements and automatic reports give the same inputs this method asks for, captured as the work happens rather than reconstructed weeks later.

• Work-order tagging that links labour, parts and time directly to a stoppage event.
• Time registration that feeds the overtime and contractor hours into the same record.
• Inventory tracking that flags emergency stock movements as they happen.
• Automatic reports that turn event data into the cost-per-event trends this method relies on.

If this is the kind of visibility your team has been assembling by hand, our plans overview outlines where a demo or trial might fit your operation.

FAQ

What is the formula for calculating the custo de paragem?

The cost of a stoppage equals units lost multiplied by contribution per unit, multiplied by hours lost, multiplied by one minus the share of output recovered, plus restart and recovery costs. This uses contribution margin rather than sales price as the base, which keeps fixed costs out of the loss figure.

Which costs should be included beyond direct repair?

Beyond lost production, include emergency parts and freight, overtime and contractor labour, scrap and rework, late shipment penalties, secondary equipment damage and any planned maintenance deferred to free up technicians. Each of these shows up in a different system of record, so they need to be actively tagged to the event rather than assumed.

Quanto devo cobrar ao km?

This is a separate question from stoppage costing and depends on vehicle running costs, fuel and the rates common in your sector and region, so it falls outside what this calculation method addresses. A transport or fleet costing guide specific to your vehicle type is the better source for that figure.

Como calcular as ajudas de custo?

Subsistence allowances follow separate payroll and tax rules rather than the contribution-margin method described here, so they are not part of a stoppage cost calculation. Check current guidance from your payroll provider or the relevant tax authority for the applicable rates.

How often should the event file be reviewed?

Keep each stoppage event open for 60 to 90 days after the line restarts so late invoices and secondary repairs are captured before the file is closed. Reviewing three-event averages rather than single incidents gives a more reliable figure for building a business case.

Sources

• The True Cost of Downtime (Siemens white paper)
• Factory shutdown planning: downtime cost (Secured Engineers)

Recommended

• Maintenance Planning Step by Step: Cut Downtime by 30%
• For Maintenance Teams: Condition Based Scheduling, Three Thresholds
• Top 4 Maintenance Tracking Tools for Industrial Teams 2026
• Workflow for Preventive Maintenance: Cut Costs by 30% in 2026