Paper Travelers vs a Digital Production Logbook
Walk most Indonesian mid-market factories and you will find the same object clipped to every pallet: the paper traveler. It carries the work order, the routing, and a set of boxes someone fills in as the job moves. It has run production for decades, it costs almost nothing to start, and it fails in ways that are predictable enough to list before you visit the floor.
What Paper Travelers Do Well
Credit where due. Paper needs no infrastructure, no training beyond "write here", and no IT sign-off. An operator can read the routing without unlocking anything, a supervisor can grab a traveler and walk to the line, and when the network dies (and it will), paper keeps working. The format is genuinely good at carrying instructions to the point of work. The problem is everything on the other side: getting the record back out.
Where Paper Fails
The failure modes repeat in every plant:
- It arrives late or never. Quantities get filled in at shift end, from memory, or by whoever finds the blank box first. The paper records what the shift remembers, not what happened.
- It is unreadable or wrong. Smudged digits, corrected numbers, a shortage entered as a different figure. Nobody discovers this until a customer complaint forces a recount.
- It cannot be queried. "Which orders ran on machine 3 last Tuesday?" is a day of digging through folders. "Which lots did operator Budi run this month?" is not answerable at all without a data-entry project.
- Nothing is linked. The traveler, the downtime note on the whiteboard, and the inspection sheet are three unrelated artifacts. You cannot walk from a defect back to its cause, or from a material lot forward to the shipments it reached. That link is exactly what traceability and the recall questions described in lot genealogy depend on.
The deeper cost is invisible: someone retypes traveler data into Excel, someone else retypes the Excel into the ERP, and every retyping is a fresh chance for error plus hours of skilled people's time.
What a Digital Production Logbook Changes
A digital logbook keeps the good part of paper (the record lives at the station) and removes the failure modes. Entries happen when the event happens: the operator starts the job at the terminal and the start time is the start time. Quantities are counted in and recorded once, pauses and reasons are tapped, not written, and completion closes the order in the same record. Nothing is transcribed afterward because there is nothing to transcribe.
Because every entry carries order, lot, machine, operator, and timestamp automatically, the record becomes queryable. The questions paper could not answer become a filter: by lot, by order, by operator, by shift. OEE rollups and hourly output fall out of the same data instead of requiring a separate tracking initiative. And when auditors or customers ask for evidence, the record exports as CSV or a month-end zip rather than a photocopy session.
What the Switch Actually Takes
Less than most plants expect, because the workflow barely changes:
- A terminal at the line (a tablet on a stand counts) where the traveler used to hang.
- The operator picks their job from the schedule board and confirms start. No typing of order numbers.
- The record writes itself from there: quantities, pauses, checklist results, completion, each tied to lot and operator.
The honest difficulties are the ones every shop-floor project has: terminals must survive dust and shifts, logins must take seconds, and data entry must be faster than the paper it replaces or operators will quietly keep paper alive in parallel. Run it on one line first, as with any MES adoption, and let the operators who hated double entry become the ones who insist on it.
Voltrus MES works exactly this way: the work order terminal appends every event (start, quantities, pauses, checklist results, completion) to an append-only production log tied to lot and operator. Combined with a schedule board instead of the Excel grid, the paperwork trail becomes a data asset.
Frequently Asked Questions
Should we keep paper at all?
Many plants keep a printed routing or quality checklist at the station as a reference even after going digital. What disappears is paper as the system of record. Reference copy at the line: fine. Data entry onto paper that someone retypes later: that is the part to kill.
What if the network or the terminal goes down?
Plan for it: a terminal that buffers locally while offline and syncs when the network returns, plus a one-page fallback form for true outages, keyed in afterward. The difference from paper-only is that the exception is rare and recorded as an exception, not the daily routine.
Will older operators actually use it?
The friction test is simple: if starting a job takes longer than finding a pen, it fails. Pick-a-job-and-confirm takes seconds, which is why factories that pilot terminals usually report the resistance fades within the first weeks. The operators who write the most paper today have the most to gain.
The Logbook That Writes Itself
Voltrus MES is live: an append-only production log at the line, quantities and times recorded once, exportable when asked for. One line to start.
See Voltrus MES