Choose the tracked unit
Decide whether the record follows a job, batch, carrier or individual part. Define how the identifier stays associated with the work when containers are reused or items leave a fixture.
Industrial marking and traceability
Work-in-Progress Tracking
Plan work-in-progress tracking around your identifiers, substrates, production events, system interfaces, exceptions and verification records. Discuss a practical data-flow approach with Oxford Traceability.
Speak directly with Oxford Traceability about tracking work through manufacturing stages.
Quick answer
How can we record where work-in-progress is in our production route?
Define the unit to track and the events that move it between operations, queues and holds. Include split batches, rework and transfers outside the normal route. Trial identification at the actual workstations, with rules for missing events and corrections before using the records to report production status.
Application decisions
Track the manufacturing state as well as the item
Knowing that an identifier was read at a workstation is only one observation. A WIP system must establish which operation occurred and what state the work reached.
Name the production events
Separate arrival, operation start, completion, hold and release where relevant. Each event should have a defined meaning so a workstation read is not automatically interpreted as a completed process.
Handle splits and merges
Record parent and child relationships when a batch is divided or components are assembled. Agree how quantities and identities are reconciled without losing the route history.
Keep rework visible
Define the permitted rework route and its return point. Retain the original result and the corrective operation so a repeated visit does not overwrite the explanation of what happened.
Design the capture points
Compare operator scans and automatic reading at the actual workstation. Include missing identifiers, unreadable labels and a part moved outside the normal route in the feasibility review.
Control delayed and corrected events
Define who may correct a record and how delayed information is reconciled. Preserve the difference between the event time and the time it was received where this affects production status.
Applications
Two useful starting points for work-in-progress tracking
The right choice changes with identifier and data rules for tracking work through manufacturing stages, substrate, label or tag behaviour, your line layout and required results.
Practical application guide
Distinguish waiting work from completed operations in the WIP record
A WIP tracking record should explain the unit, location and manufacturing state at the same point in time. Define arrival, start, completion, hold and rework separately, then compare a small known route with the physical work before using the record for production decisions.
Choose what the displayed quantity counts
A job, carrier, batch and individual part are different units. State whether a queue quantity counts containers or their contents and how partial containers are handled. Keep units visible so a display of five carriers is not interpreted as five components.
Define the state transitions at each operation
Decide what confirms arrival, active processing and completed work. A scan on entry may establish location without proving the operation ran. Specify what happens when work is removed before completion and how an interrupted operation is resumed or recorded as abandoned.
Make holds and rework visible
A held item may still be physically at a workstation but unavailable to the next operation. Record the reason, responsible release decision and permitted rework route. Preserve repeat visits so cycle and queue observations do not hide the extra path behind only the latest successful completion.
Reconcile missing and out-of-order events
Test delayed messages and a missed capture point. Determine which status is confirmed and which needs review rather than guessing the missing step. Keep a correction history and the physical observation used to resolve it. Agree which system owns routing, quality release and inventory updates.
A worked planning example
In a hypothetical batch of ten parts, six complete an operation, two are on hold and two have not started. A report showing ten at the station cannot establish ten completed. The acceptance exercise should reconcile those states and then preserve the two held parts’ rework history when they eventually return to the main route.
Acceptance questions to resolve
- Is the tracked unit and quantity basis explicit?
- Can location be distinguished from operation completion?
- Are held and reworked quantities excluded from available completed work?
- Can physical work explain every confirmed and unresolved recorded state?
For the next step, discuss this application using the examples and unresolved decisions above.
Important limits
Know what needs a separate check
- Mark, label, tag and reader performance depends on the real substrate and environment.
- A readable code does not prove that its encoded data is correct or reconciled.
- Retention, privacy and regulatory rules must be defined by the responsible organisation.
Your final solution for tracking work through manufacturing stages must reflect the law, current standards and site-specific risks that apply to your installation.