Recording why a machine stopped, without adding paperwork

Short answer: recording downtime only works if reporting takes under half a minute and happens at the machine itself. Any system that requires walking to a pc or filling in a form stops being used within two weeks, and then you do not have data, you have an obligation.

Why most logging dies quietly

The operator who sees the stoppage first is also the one who has to clear it. At that moment there is exactly one priority: get the line running again. Reporting comes after, and “after” means at the end of the shift, from memory, or not at all.

So downtime keeps living in the supervisor’s head. They often know remarkably well what is going on, but that knowledge cannot be queried, cannot be handed to the engineer, and leaves with the shift change. And at the next stoppage the engineer starts from zero again: the same questions, the same measurements, the same ruling out.

What makes reporting short enough

Two things together: it has to happen at the machine, and it has to be speaking rather than typing.

Scan a tag on the machine with a phone, then say out loud what is wrong. That is the whole action. What was said gets written out, categorised and recorded against that exact machine. No form, no dropdown with thirty options, no walk to a workstation.

That it is per individual machine rather than per machine type matters more than it sounds. Two identical machines in the same hall have different histories after a year, and it is that history which makes the next stoppage shorter.

What you get once there is history

Once reports are kept, the character of the system changes. It does not only record, it answers back.

• Downtime gets a cause and a duration instead of a gut feeling. The recurring culprit usually surfaces within a month, and it is often not the machine everyone was pointing at.
• A stoppage no longer starts from zero. Whoever is standing there sees what it was the previous times and what helped then, on this specific machine.
• The knowledge stays with the machine, not the person. A holiday or a colleague leaving no longer costs you the history.

A tag and a phone can give even an old machine with no connection an assistant that listens and answers back, without anyone pulling a cable.

What this is not

This is not a maintenance system that takes over your work planning, and it does not replace sensors on a machine that deserves them. It is the least expensive way to start measuring what you currently do not measure, and to find out whether the problem is big enough to justify the next step.

We have written this up as an example scenario in our work. The packages and starting prices are on one page, and otherwise we can work out in a conversation whether this fits your line.