A press brake reports thirty cycles. The operator reports a tooling alarm. Inspection holds two brackets. Assembly needs forty. How many parts can assembly actually use?
For a one-bend-per-part operation, the answer is twenty-eight, not thirty. The machine count tells you what ran. The inspection result tells you what passed. The work order tells you what remains. None can stand in for the others.
Record the stop with its cause
Machine data can show the time of a stop and the number of cycles before it. It may not explain whether the cause was tooling, material, a planned changeover or a fault. Record the operator’s reason against the same machine, work order and operation. If the reason is not known yet, leave it open rather than assigning a guessed downtime code.
Tulip’s production-tracking guide separates machine status from the operator’s explanation of why a machine was idle. That distinction matters to the person who must get the station running again.
Record each quantity separately
At the operation, record the planned quantity, machine count, accepted quantity, held quantity, scrap and quantity not yet made. A quality hold is not usable stock, even if the part has passed through the machine. Do not add it back until quality records a disposition.
In the press-brake example: forty planned, thirty cycles, two held, twenty-eight accepted and ten not made. If a part needs several cycles, use the operation’s part-completion event rather than treating each cycle as one part.
Update the next operation before it starts
The shift lead and planner need the accepted count and the reason for the shortfall. They can decide whether assembly can start with a partial kit, another job should run first, or the schedule needs to move. An agent can prepare those options and route the tooling and quality actions. The planner and quality team still make the controlled decisions.
The MES or ERP remains the owner of the approved production record. Publish the corrected quantity there after the supervisor confirms it, so the next shift does not inherit a second, conflicting count.
See shop-floor data collection for the connected station workflow.
Buğra Gündüz
Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.