Blog · Why losses happen · For operations

When the machine that stopped isn't the machine to fix

The Recurline team · · 4 min read

TL;DR. The machine that stops is where the loss is recorded, not always where it began. In a connected line, starved fillers, blocked packers and air-pressure dips all show up downstream of the cause. Read the minutes before the stop, and put the loss against the machine that started it.

Why does the wrong machine get blamed?

Downtime logs record where a line stopped. That is the easiest fact to capture, so it becomes the working story.

The filler goes down, the filler’s team is asked why, and a plausible answer is written down. The real cause, a feeder that ran short ten minutes earlier, never appears in the filler’s record.

Over months the filler collects a reputation for unreliability. Its team collects extra maintenance. The feeder is left alone.

What does a connected line look like in practice?

Machines are linked by product flow, by shared utilities and by shared people. A stoppage can travel along any of those.

Illustrative example: a fictional dairy line has a pasteuriser, a filler and a case packer. The packer jams and stops. The filler fills the buffer, then stops. The pasteuriser backs up and holds product. Three machines record stops within a few minutes. The cause is a single packer jam.

Without the sequence, the log shows three problems. With it, there is one, and it has an owner.

Which signs suggest a cause upstream?

Several patterns appear again and again.

  • Starvation. The machine stopped waiting for product, packaging or a part that did not arrive.
  • Blockage. The machine stopped because the next machine would not accept product.
  • Shared supply dips. Several machines slowed together when compressed air, steam, chilled water or power sagged.
  • Time clustering. Stops across different machines begin within a minute or two of each other.
  • Speed loss before the stop. The machine ran slowly for a while, then stopped. Slow running often signals a problem it was receiving, not producing.

None of these proves the cause. Each tells you where to look first.

How do you read a stoppage step by step?

Take one stop and work backwards.

  1. Note the time the machine stopped and the reason code given.
  2. Check the same window on the machines before and after it.
  3. Check shared supplies in the same window.
  4. Ask who was on shift and what had changed that day.
  5. Decide whether the stop started here, arrived from elsewhere, or is unclear.

“Unclear” is a valid answer. Writing it down is better than guessing, because it flags where more records are needed.

Who pays for the loss?

This matters more than it sounds. If the loss is booked to the machine that stopped, its owner is accountable for something they did not cause. They will argue, and rightly.

If the loss is booked to the cause, the cost lands where the fix can happen. The stopped machine can still show the loss it suffered, which is useful context, but the owner of the cause carries the number.

What does this change in the Monday meeting?

The question moves from “why did the filler stop?” to “what started this chain?” That is a better question, and it usually has a shorter list of candidate answers.

It also changes who is in the room. If air supply is the cause, utilities need a seat. If a feeder is the cause, so does the team that runs it.

It makes the ranking cleaner too. Instead of three medium losses on three machines, you see one large loss with a single owner. Our post on the Monday loss meeting explains why that helps.

What are the limits?

Not every stop has a clean upstream story. Sometimes two things go wrong at once. Sometimes the records are too coarse to see the order of events.

Be cautious about certainty. A reasonable rule: act on cause when the sequence is clear on several occasions, not on a single event.

Also keep the stopped machine’s own faults on the table. A machine can be both a victim on Tuesday and the cause on Thursday.

What to do on Monday

  • Pick your largest recurring stoppage and pull the three machines either side of it.
  • Check the same minutes for shared supplies such as air, steam or chilled water.
  • Write down whether the loss started here, arrived, or is unclear.
  • If it arrived, move the action to the upstream owner and tell them why.
  • Mark any “unclear” stops as a gap in your records to close.

Questions

How can you tell whether a stoppage started on that machine?

Look at the minutes before it. If other machines slowed or stopped first, or a shared supply dipped, the cause probably started elsewhere.

Should the stopped machine's team still investigate?

Briefly, to rule out their own fault. If the evidence points upstream, the work and the cost belong with the upstream owner.

See this on your lines.

Keep reading