Question 1 of 7: Little's Law, 5S, and the Seven Zeros

Question 1: Little's Law, 5S, and the Seven Zeros (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

(a) Using Little's Law to Calculate and Control WIP

Little's law states that, for any production system operating in steady state, the average amount of work-in-process $L$ equals the average throughput rate $\lambda$ (units completed per unit time) multiplied by the average flow time $W$ (the time a single unit spends in the system from release to completion): $L=\lambda W$. To calculate WIP on a real production line, an engineer measures any two of the three quantities directly on the shop floor — throughput $\lambda$ is read off shipping/completion records over a period, and flow time $W$ is measured by time-stamping a sample of units at release and at completion — and solves for the third: $L=\lambda W$ gives WIP directly, or if WIP is counted by a physical inventory sweep and throughput is known, $W=L/\lambda$ gives the average flow time instead. Because the relation holds for essentially any arrival pattern, service-time distribution, or dispatching rule as long as the system is stable, it applies at any scope — one workstation, a whole line, or an entire plant — without needing a full queueing or simulation model.

Controlling WIP matters because $L$, $\lambda$, and $W$ are locked together: for a fixed throughput $\lambda$ (set by market demand), the only way to shorten flow time $W$ — and hence lead time, a major driver of responsiveness and customer satisfaction — is to reduce the amount of work-in-process $L$ sitting in the system. Excess WIP ties up capital and floor space, hides quality problems inside large queues (a defect introduced early is not discovered until it reaches the end of a long queue, by which time many more units have been built on top of the same error), and lengthens the time a demand change takes to reach the shop floor. Too little WIP has the opposite failure mode: a station starves whenever its input buffer empties, wasting available capacity and reducing achievable throughput below what the line could otherwise sustain. This is the theoretical basis for WIP-capping systems such as kanban and CONWIP: by directly limiting $L$ to a deliberately chosen level, a plant forces $W$ down to the corresponding minimum without touching capacity, instead of letting WIP grow unmanaged and drag flow time out with it.

(b) 5S and Why It Improves Production

5S (Sort – Seiri, Set in order – Seiton, Shine – Seiso, Standardize – Seiketsu, Sustain – Shitsuke) is a structured workplace-organization method, originating in the Toyota Production System, that removes clutter, assigns every tool and part a labelled, visually obvious home, and maintains that standard through periodic audit and habit-building rather than a one-time clean-up.

It improves production because a disorganized workstation hides problems — a missing tool, a leaking machine, an out-of-spec part — inside visual noise, and searching for a misplaced item is pure non-value-added time that adds to every job's flow time without adding to $\lambda$. By making abnormalities visually obvious (a shadow board with an empty tool outline, a marked floor zone that is not empty), 5S is usually the first step of any lean or TPM rollout: it builds workforce discipline and creates the visual baseline that later tools (kanban boards, andon signals, standardized work) depend on. Plants that genuinely sustain 5S typically see fewer minor stoppages and safety incidents, simply because hazards and defects that used to hide in clutter become visible immediately, and operators spend measurably less of their shift searching rather than producing.

(c) Why the Seven Zeros Work

The "seven zeros" is a just-in-time production framework (associated with R.W. Hall's Zero Inventories) that states the goal of a lean production system in seven simultaneous, idealized targets: zero defects, zero (excess) lot size, zero setups, zero breakdowns, zero handling, zero lead time, and zero surging (a level, uniform release rate rather than lumpy batches).

They work because each of the seven targets attacks one specific root cause of waste or variability, and driving all seven toward zero together — rather than trading one off against another — is what lets a line run with minimal buffers while still meeting demand: zero defects removes rework and scrap (a quality-driven variability source that otherwise forces extra WIP and inspection buffers); zero setups (via SMED-style quick-changeover techniques) is what makes zero lot size economically viable, since a large batch only exists in the first place to amortize a slow changeover, and small batches directly shorten flow time; zero breakdowns (through TPM-style preventive and autonomous maintenance) removes machine-availability variability; zero handling minimizes non-value-added motion and damage risk between operations; zero lead time is the cumulative result of the other six being achieved; and zero surging (heijunka, levelling the production schedule) prevents the plant from absorbing demand shocks as sudden capacity spikes. By Little's law, flow time $W$ and WIP $L$ are locked together at a given throughput $\lambda$ — every one of the seven zeros is, in effect, another way of shrinking $W$ (or the variability that forces a buffer around $W$), so pursuing all seven together compounds rather than conflicts, which is why the framework treats them as one integrated target rather than seven separate initiatives.