Busy people, quiet machines
Walk the shop at any moment and everyone looks busy. Yet when you add up the parts that came off the machines this week, it does not match the hours the machines were staffed. The five axis sat for most of Tuesday morning. Nobody is quite sure why. Someone thinks it was waiting for a first off to be signed. Someone else thinks the material was in the wrong size.
The breakdowns are remembered, because an engineer was called. The dozens of short stops are not.
Why the lost time stays invisible
Most stoppages in a machine shop are not faults. They are waiting: for material, for a tool, for the inspector, for a program edit, for a crane, for someone to finish a setup on the next machine. Each one is short and feels unavoidable, so nobody records it.
- Only breakdowns are logged, in a maintenance book.
- Operators have no quick way to say why they stopped.
- Waiting for first off approval is treated as part of setup.
- Machines left idle over lunch or at shift change are not counted.
- Nobody compares staffed hours with cutting hours.
What the idle time costs
Spindle time is what you sell. Every hour a machine is staffed but not cutting is a cost with nothing to show for it. Without knowing the causes, the usual response is to buy another machine or add overtime, when the real fix might be presetting tools, moving an inspector, or getting material cut a day earlier.
The stoppage logging we build
- Each machine reports whether it is cutting. Newer controls do this through MTConnect or OPC UA. Older ones can use a current sensor on the spindle or a signal from the cycle light.
- When a machine stops for longer than a few minutes, a tablet at the cell asks the operator for a reason from a short list you choose: waiting material, waiting tools, waiting inspection, setup, program, breakdown, no operator, planned.
- One tap records the reason. If the operator is busy, the question waits until they come back.
- Stoppages are recorded with machine, job, shift and duration.
- A daily and weekly report shows cutting time against staffed time for each machine, and the lost time broken down by cause.
- A live screen in the office or on the shop floor shows which machines are cutting, set up or stopped, and why.
| Stoppage reason | Usually fixed by |
|---|---|
| Waiting for material | Cutting stock a day ahead |
| Waiting for tools | Presetting before the machine is free |
| Waiting for first off sign off | Inspector availability or operator sign off rules |
| Program edits | More prove out in CAM or simulation |
| No operator | Shift cover or running one person across two machines |
The list of reasons is yours. We keep it short, because a long list means operators pick whichever is at the top.
What the reports start to show
Within a few weeks you have a picture of where time goes that nobody could give you before. It is usually not what people expected. The fixes that follow are often small and cheap: a tool presetter, a second person trained to sign first offs, a change to when material is cut. The live screen also means the supervisor sees a stopped machine straight away rather than at the next walk round.
This is not the same as predicting breakdowns. It is about the ordinary waiting that makes up most lost time, which is where most shops have the most to gain.
Could your machines be cutting more?
- You cannot say how many hours each machine cut last week.
- Only breakdowns are logged.
- Machines wait for first offs to be inspected.
- Output does not match staffed hours.
- The answer to idle machines has been overtime or another machine.