Most workshops have one folder that holds everything together. Inside are the job sheets: which order, what quantity, which operation, who did what and when. The folder has worked for years. It has only two weaknesses. It is always in exactly one place, and it never knows how far along anything is until somebody opens it.
The paper is not the problem, the transcription is
Almost every workshop already records its data. It just records it twice: once on paper while the work happens, and once on a computer when somebody has time in the evening. All the trouble lives between those two entries. Numbers get mistyped, sheets go missing, and the status in the system is always a few hours out of date.
The obvious answer is to give everyone a computer. That fails because nobody wants to use a keyboard with oily hands. The workable answer is shorter: the job gets a code, and the code gets scanned.
A scan that knows what it means
What matters is that a scan does not just return a number but is recognised. A barcode can stand for a part, a production order, a storage location, a tool or a staff badge. When the system tells those identifiers apart, scanning becomes an interface: badge, then order, then operation, done. The operation is booked on without anyone filling in a form.
At the end of the operation the same path in reverse, with the quantity and what was actually consumed. The material movement lands in stock at the moment it really happens rather than at the end of the month.
What becomes measurable for the first time
The real gain is not the saved typing, it is the visibility. Once operations are booked on and off, you know three things that used to be estimates: where an order currently stands, how long an operation actually takes, and which machine work is piling up in front of.
The third number is usually the most uncomfortable and the most useful. Bottlenecks rarely sit where people assume, and they move with the order mix. Without recording you notice them in tense conversations about delivery dates. With recording you notice them in a list.
Why this is not an IT project
Getting started needs neither a new building nor a year of preparation. It needs three things: labels with codes, a device that scans, and a decision about which operations to record at all. The third is the only one that takes real thought, and it is regularly answered too ambitiously.
Start with the bottleneck everyone already knows about. One operation recorded properly is worth more than fifteen recorded half-heartedly. Once that one runs, the next follows on its own, because somebody will ask why the neighbouring step does not have the same number.
In many cases a phone is device enough. Where work happens permanently in one spot, a fixed terminal is sturdier: no battery, nothing to look for, and it is always where the operation happens.
Frequently asked questions
What happens when the network in the workshop drops?
Recording has to continue on the device and sync afterwards. In a workshop that is the normal case, not the exception.
Do we have to relabel every part?
Only the ones you want to record. The order itself carries the most important code, and that one is created fresh anyway.
Is this a way of monitoring staff performance?
What is recorded is order progress, not the person. What gets evaluated from it is a management decision that belongs made and communicated openly beforehand, not a technical side effect.
Our production solution shows how this fits together on the shop floor. The matching hardware is under scanners and terminals.