WIP Is Moving. Why Is Lead Time Getting Longer?
Activity can hide delay. The useful question is not whether WIP moved, but how long it waited, why it queued and what blocks flow.
The short answer
WIP can move frequently while manufacturing lead time gets longer because movement is not the same as flow. A unit may be scanned into several locations, transferred between queues or partially processed, yet spend most of its elapsed time waiting for material, test capacity, quality disposition, engineering answers or the next batch.
Useful electronics WIP visibility must show age, queue time, hold reason and next constraint—not only current operation or last transaction. When ERP and MES connect these events to the production plan, managers can control flow instead of celebrating activity.
The factory looks busy because everything is moving
Walk through a high-mix electronics plant and the level of activity is impressive. Trolleys move between areas. Operators scan travellers. Boards enter and leave machines. Supervisors expedite urgent lots. Dashboards show thousands of transactions.
At the same time, customer lead time rises.
This apparent contradiction occurs because local activity can increase while end-to-end progress slows. A batch completes SMT quickly, then waits fourteen hours for AOI review. A tested unit moves to a hold rack while engineering decides whether a result is acceptable. A partial kit starts production but stops at the next operation. Each movement creates a status update, yet the order remains unfinished.
Lead time is mostly elapsed time between value-adding steps
Processing time is often a small part of total manufacturing lead time. The rest is queue, transfer, batching, waiting and decision delay.
If management measures only cycle time at each machine, every operation can look efficient while the product spends days between them. The missing measurement is elapsed time from release to completion, decomposed by state.
A useful WIP timeline distinguishes:
- active processing;
- waiting in a normal queue;
- blocked by material;
- held for quality or engineering;
- waiting for batch formation;
- waiting for external processing;
- moving between locations;
- awaiting transaction or reconciliation.
Once time is classified, the dominant causes of lead time become visible.
A location is not a condition
Many systems answer “where is the job?” with an operation or warehouse location. That is necessary but incomplete.
Two lots at the same test station can have completely different conditions. One is next in queue and fully ready. Another lacks a fixture, waits for a repaired unit or requires a customer decision. Both appear as “at test.” Without reason and owner, the planner cannot predict completion.
WIP status should therefore combine location, state, timestamp and next action. “Test queue since 08:10” is better than “Operation 40.” “Quality hold since yesterday, owner Lee, disposition due 15:00” is actionable.
Queue age matters more than queue count
A queue of twenty units may be normal for a high-rate process. A queue of three may be dangerous if one has waited beyond the customer promise.
Measure the age distribution, not only the quantity. Show oldest WIP, median wait, time against expected queue and the reason units exceed threshold. This prevents new work from hiding old work at the back of the queue.
Age also reveals policy problems. If high-priority jobs repeatedly jump ahead, ordinary orders accumulate quietly. The line remains busy, but the factory creates future emergencies.
Batch logic can manufacture delay
Electronics operations sometimes require economic or technical batches. Ovens, coating, environmental tests and external processes may run most efficiently at a certain load. But fixed batch habits can create unnecessary waiting.
The system should make the trade-off visible. How much time will the current units wait for a full batch? What capacity or cost is saved? Does the delay threaten delivery? Could a smaller batch release a constrained customer order?
Batching should be a deliberate decision, not an invisible queue rule.
Holds need clocks and owners
A hold often stops the operational clock in reports even though the customer clock continues. Quality, engineering and customer approvals can become unmeasured queues.
Every hold should record:
- reason and affected units;
- start time;
- responsible owner;
- evidence required for disposition;
- next review time;
- expected effect on schedule;
- final decision and release time.
This converts “waiting for engineering” from a vague explanation into a managed workflow. It also shows whether the underlying problem is slow analysis, unclear authority or missing data.
Do not release more work into a blocked system
When one area falls behind, the intuitive response is often to keep upstream resources busy. That creates more WIP ahead of the constraint and lengthens the queue.
The better question is whether new release will improve customer completion. If test is the current bottleneck, additional SMT output may consume space, increase handling and complicate priority without increasing shipment.
The readiness model in The Schedule Is Green. Why Is the Line Still Waiting? should include downstream capacity. A job can be ready to start and still be the wrong job to release.
Connect WIP events to the customer promise
Shop-floor visibility becomes strategically useful when each unit or lot is connected to the order, delivery commitment and downstream dependency.
A delay of four hours has different consequences for a spare unit, a prototype needed for customer approval and a board feeding final assembly at another site. Priority should reflect that context.
ERP provides order, customer, material and commercial information. MES provides actual movement, processing and hold events. Their integration lets the factory ask not merely “What is late?” but “Which current queue threatens which promise?”
The Mars solution describes real-time WIP monitoring and ERP–MES integration as part of one operational model. That connection is essential if WIP data is to change the plan rather than become another report.
Track the unit through internal and external processes
WIP does not stop being WIP when it leaves the building. Subcontract coating, specialist test or another factory can become the longest and least visible queue.
The article The Board Left for Subcontracting. Did Its History Go Too? explains how shipment, receipt, process evidence and product genealogy should remain connected. For lead-time control, the system should also capture expected and actual external milestones, exceptions and return readiness.
A single “at supplier” status hides whether the product is in transit, queued, processing, held or complete.
Build a flow-oriented dashboard
A useful WIP dashboard should answer five questions quickly:
1. What is the oldest WIP and why is it still open?
2. Where is queue time growing faster than plan?
3. Which holds lack an owner or promised resolution?
4. Which customer commitments are exposed?
5. What release or priority decision would improve completion?
Visualize elapsed time and exception state. Avoid ranking areas primarily by transaction count. A quiet process that releases finished units may contribute more to flow than a busy process that accumulates queues.
Measure flow, not motion
Useful measures include:
- total release-to-completion lead time;
- active processing as a percentage of elapsed time;
- queue age by operation and reason;
- WIP exceeding planned dwell time;
- hold response and disposition time;
- number of priority changes per job;
- throughput at the system constraint;
- jobs started without downstream readiness.
These measures create different behaviour. Teams focus on removing waiting and finishing work rather than maximizing visible activity within their own area.
Turn every delay into a better planning signal
The final step is feedback. If jobs repeatedly wait for the same fixture, inspection step or engineering decision, planning parameters and capacity assumptions should change.
Standard queue time may be unrealistic. A shared tool may need to become a formal resource. A customer checkpoint may require an earlier trigger. A material issue may belong in the readiness gate. The schedule becomes more credible when actual flow continually corrects its assumptions.
This is the difference between tracking WIP and learning from it. Tracking tells the factory where work was. Learning changes what the factory releases next.
Frequently asked questions
Why can WIP movement increase while lead time worsens?
Because transfers and scans may represent handling or queue changes rather than completion. Units can move often and still spend most elapsed time waiting.
What WIP information is most important?
Track identity, location, state, queue age, hold reason, owner, next action and connection to the customer commitment.
Should every operation minimize its local queue?
Not necessarily, but queues should be intentional and visible. The priority is end-to-end flow through the system constraint, not isolated utilization.
How should quality holds be measured?
Measure from hold start to disposition, including owner, reason and customer impact. The customer lead-time clock does not stop during an internal hold.
How does MES reduce manufacturing lead time?
MES supplies timely execution and exception events. When connected to ERP and planning, those events support earlier decisions about release, sequence and recovery.