OEE Lab / Templates / Machine Downtime Report Template

Machine Downtime Report Template

Enter the stops for a period: machine, reason, minutes. You get a finished downtime report with totals, downtime percent and a ranked Pareto list, ready to print or paste into an email. Nothing is sent anywhere.

Your stops

One row per stop, or one row per reason if you already have totals. Leave out breaks and time with no orders.

min
Left empty, it counts the machine names below. If some machines had no stops, enter the real number, or the percent reads too high.
Downtime percent
-%
Stop minutes ÷ planned production time
Total downtime
-
Stops
-
Average stop
-
Availability
-
Planned time, all machines
-
Top reason share
-

Want help with your downtime numbers?

Leave your work email if you would like the OEE Lab team to get in touch. To keep the report, use Print or Copy above.

Thanks, we have your email.

No newsletter, no spam.

A report is only as good as the stops that reach it.

Short stops and waits are the first to drop off a paper log. Fabrico, a light MES for OEE, takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line. Where cameras are fitted, video of any stop can be streamed on request next to its machine data.

See where your line loses this time: book a demo with a Fabrico consultant.

Request a demo Contact us
Our tools stay free either way.

What this downtime report does

A downtime report turns a list of stops into one page someone can act on. It answers three questions: how much time was lost, where, and what comes first.

This template is for the end of the period, when you hand the numbers on. To record each stop as it happens, with start and end times, use the downtime log template and bring the minutes here.

The downtime report format

1
Header
Line, period and who prepared it.
2
Headline figures
Total downtime, downtime percent, number of stops, average stop and availability.
3
Pareto by reason
Reasons from largest to smallest, with share and running share.
4
By machine
Minutes and downtime percent for each machine.
5
Action
What happens next on the top reason, who owns it and by when.
The report above follows this order, so the reader gets the verdict before the detail.

How the percentages are worked out

Downtime % = stop minutes ÷ (planned minutes per machine × machines)

Availability = 100% - downtime %

Share of a reason = its minutes ÷ total stop minutes

Planned production time leaves out breaks and time with no orders. Changeovers stay in, so they count as downtime here, the same way they lower availability in OEE, as the guide on counting changeovers in OEE explains.

The machine count comes from the machine names you enter. Check the spelling, since "Filler" and "Filler 1" count as two machines.

A machine with no stops has no row, so it would not be counted. Enter the real number in Machines in this report, or the percent reads too high.

A downtime report example: one bottling line

Example: a bottling line with a Filler, a Capper and a Labeller, each planned for 2,250 minutes in the week. Ten stops add up to 297 minutes.

Planned time is 2,250 × 3 = 6,750 minutes, so downtime is 297 ÷ 6,750 = 4.4% and availability is 95.6%. The average stop is 29.7 minutes.

Bearing failure105 min, 35.4%
Changeover80 min, 26.9%
Waiting for material52 min, 17.5%
Jam or misfeed42 min, 14.1%
Sensor fault18 min, 6.1%
Bar length is share of the 297 stop minutes. The top three reasons make up 79.8%.

By machine, the Filler lost the most at 148 minutes, 6.6% of its planned time. But the top reason, bearing failure, sits entirely on the Capper, at 105 of its 117 minutes.

That is why the report shows both lists. The machine with the most downtime is not always where the biggest single fix is.

How to read the report

  • One reason far ahead of the rest: a single fix can pay off. Give it an owner and run a root cause analysis.
  • A flat list: many small causes. Your reason list may be too vague, so check it against these downtime reason codes.
  • Many short stops: a low average stop with a high count points at jams and misfeeds, not repairs.
  • Few long stops: a high average points at repairs and waiting for people or parts. Track MTTR on those machines.

To turn the minutes into money for the reader, run them through the downtime cost calculator. If the report goes to someone who also wants OEE, pair it with the OEE report template.

What makes a downtime report useless

  • Free text reasons. "Jam", "jammed" and "infeed jam" split one problem into three short bars. Use one fixed list.
  • Counting breaks as downtime. It lifts the percent on lines that log them and makes lines impossible to compare.
  • A big "Other". If it sits near the top, the report is telling you about your logging, not your machines.
  • No action line. A report with no owner and no date gets filed and forgotten.
  • Comparing against someone else's percent. Compare a machine with its own past periods, measured the same way, as the guide to downtime percentage advises.

Downtime report questions

What should a machine downtime report include?

The line and period, total downtime, downtime percent, number of stops, a ranked list of reasons and the minutes per machine. Add one action on the top reason, with an owner and a date.

How do you calculate downtime percent for several machines?

Add the stop minutes of all machines, then divide by the planned minutes per machine times the number of machines. Three machines planned for 2,250 minutes each with 297 stop minutes give 4.4%.

Should planned downtime go in the report?

Leave out breaks and time with no orders, since they sit outside planned production time. Keep changeovers in, because they are time the machine was meant to run, as planned vs unplanned downtime explains.

How often should I make a downtime report?

Weekly is a good default, since a week holds enough stops to rank and is short enough to act on. A monthly roll-up works better for management, as long as both use the same reason list.

Can I use this downtime report template in Excel?

Use Copy as text to paste the report into an email or a sheet, or print it to PDF. To log stops in a workbook with a Pareto chart, download the downtime log template.

← All OEE Lab tools · All templates