NivaarExam PrepOfficial exam papers ↗

23-Ind-A4 Production Management · December 2018

Question 1 of 8: 5S and the Five Whys

Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)

Notes on this paper

National Technical Examinations — December 2018 — 17-Ind-A4 Production Management. Three-hour, closed-book exam; Casio or Sharp approved calculators only. Format: eight questions, each worth 20 marks (sub-part weights 10/10 as tabulated on the front-page marking scheme); candidates do two questions from Section A and three from Section B, and only the first five questions appearing in the answer book are marked. All eight are solved below for completeness. The paper asks for point-form answers wherever possible; the solutions below use full working for clarity.

Reference texts: Nahmias & Olsen, Production and Operations Analysis (7th ed., Waveland/McGraw-Hill) — forecasting, inventory (EOQ/EPQ) and aggregate planning; Sipper & Bulfin, Production: Planning, Control, and Integration — production scheduling, JIT/kanban and shop-floor implementation gaps; Hillier & Lieberman, Introduction to Operations Research (11th ed.) — LP formulation and project scheduling (CPM/PERT); Pinedo, Scheduling: Theory, Algorithms, and Systems (5th ed.) — parallel-machine scheduling and days-off workforce scheduling; Hopp & Spearman, Factory Physics (3rd ed.) — variability, buffering, and production scheduling; Liker, The Toyota Way, and Shingo, A Revolution in Manufacturing: The SMED System — 5S, Five Whys, SMED and lean root-cause analysis.

Question 1: 5S and the Five Whys (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) How 5S Improves Production Efficiency

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 efficiency 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 throughput. 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.

(b) “Ask Why Five Times”: Effect and Reason

The technique referred to is the Five Whys, developed within the Toyota Production System under Taiichi Ohno as TPS matured through the 1950s and into the early 1960s. It is a root-cause-analysis method: when a problem or defect occurs, the investigator asks “why did this happen?”, and then asks “why?” again of the answer just given, repeating the question (traditionally five times, though the number is a guideline, not a rule) until the causal chain reaches a true, actionable, process-level root cause rather than stopping at the first, most visible, or most convenient explanation. A representative chain for a stopped machine might run: the machine stopped → why? a fuse blew from an overload → why? the bearing was insufficiently lubricated → why? the lubrication pump was not circulating enough oil → why? the pump's intake was worn → why? there was no strainer fitted to keep metal shavings out of the pump — a root cause (a missing strainer) entirely different from, and far more useful than, the symptom first reported (“the machine stopped”).

The effect is that each successive “why” forces the investigation one causal layer deeper, moving from an equipment symptom toward a process, design, or maintenance-system deficiency that, once corrected, prevents not just this failure but the whole family of failures the same root cause would otherwise keep producing. It works because most problem investigations naturally stop at the first plausible cause, which is usually only a proximate symptom of a deeper systemic issue; fixing that symptom (replacing the blown fuse, in the example) restores production immediately but leaves the true cause untouched, so the same failure recurs. The technique is deliberately cheap and simple — no statistical tooling or specialist training is required — which is precisely why it works as a shop-floor discipline: it can be applied by any operator or engineer, immediately, at the point where the problem actually occurred, which pairs naturally with jidoka (stopping the line the instant an abnormality appears) so the causal evidence is still fresh and directly observable rather than reconstructed later from memory or paperwork.

← Paper overview