Jidoka

Thinking Tools6.1 Designing and Testing the SolutionAlso known as Autonomation

From the self-stopping loom of Sakichi Toyoda (1896), made a pillar of Toyota's production system by Taiichi Ohno (1978).

Builds a process to stop itself the moment something abnormal appears, so each defect is fixed at its source before it flows downstream.

A filler drifts at minute 3: stop the line at once, or keep it running

At minute 3 one filler nozzle starts underfilling three bottles in ten. When the line stops, the cause takes two minutes to fix, then the line restarts. Set how long the line runs before it stops, from zero (the filler stops itself at the first short bottle) to twenty-five minutes, as when someone has to notice, and watch where the bad bottles go. Illustrative.

Select a loop to trace it, or a box to read it.B1, Stop and fix. A short bottle stops the line, the stop gets the cause fixed, and the fix ends the short bottles. The delay on the stop arrow is the minutes the line runs first. One negative (−) link: an odd count, so the loop balances.Nozzle drifts. A worn seal: from minute 3, three bottles in ten come out short.Short bottles. Each short bottle is caught by a fill-level sensor, if anyone listens to it.Packed bad. Short bottles that were capped, labeled, and cased: each one must be found and reworked later.Cause fixed. Two minutes to change the seal, whenever the stop comes.Line stops. With jidoka the sensor stops the filler at the first short bottle; without it the line runs until someone notices.
25

Short bottles packed

0: 0: 02: 0: 04: 30: 606: 90: 1208: 150: 18010: 210: 24012: 270: 30014: 330: 36016: 390: 42018: 450: 48020: 510: 54022: 570: 60024: 630: 66026: 690: 72028: 750: 75030: 75002004006008000246810121416182022242628300: 0: 02: 0: 04: 30: 606: 90: 1208: 150: 18010: 210: 24012: 270: 30014: 330: 36016: 390: 42018: 450: 48020: 510: 54022: 570: 60024: 630: 66026: 690: 72028: 750: 75030: 7500200400600800024681012141618202224262830

Good bottles made

0: 0: 1002: 200: 3004: 370: 4406: 510: 5808: 650: 72010: 790: 86012: 930: 1,00014: 1,070: 1,14016: 1,210: 1,28018: 1,350: 1,42020: 1,490: 1,56022: 1,630: 1,70024: 1,770: 1,84026: 1,910: 1,98028: 2,050: 2,05030: 2,05001,0002,0003,0000246810121416182022242628300: 0: 1002: 200: 3004: 370: 4406: 510: 5808: 650: 72010: 790: 86012: 930: 1,00014: 1,070: 1,14016: 1,210: 1,28018: 1,350: 1,42020: 1,490: 1,56022: 1,630: 1,70024: 1,770: 1,84026: 1,910: 1,98028: 2,050: 2,05030: 2,05001,0002,0003,000024681012141618202224262830

Minute 30 of 30

Short bottles packed
750
Good bottles made
2,050

B1, Stop and fix
A short bottle stops the line, the stop gets the cause fixed, and the fix ends the short bottles. The delay on the stop arrow is the minutes the line runs first. One negative (−) link: an odd count, so the loop balances.
Nozzle drifts
A worn seal: from minute 3, three bottles in ten come out short.
Short bottles
Each short bottle is caught by a fill-level sensor, if anyone listens to it.
Packed bad
Short bottles that were capped, labeled, and cased: each one must be found and reworked later.
Cause fixed
Two minutes to change the seal, whenever the stop comes.
Line stops
With jidoka the sensor stops the filler at the first short bottle; without it the line runs until someone notices.

An example

A juice bottler checked fill levels at the end of the line, where an inspector pulled a sample every hour. One Thursday a worn nozzle seal began underfilling three bottles in ten on a filler running a hundred a minute. By the time the hourly sample caught it, about 1,700 short bottles had been capped, labeled, and cased. Finding them meant opening pallets in the warehouse for two days.

The plant manager moved the check to the filler. A fill-level sensor now stops that filler at the first short bottle and lights a lamp over it; the operator fixes the cause before restarting, and writes it on a board. In the first month the line stopped fourteen times, and the operators grumbled about the lost minutes. The board showed why: nine of the stops came from the same two seals, which maintenance began replacing on a schedule. By the third month the line stopped twice a month, total downtime from stops was under one percent, and no short bottle had reached the warehouse since the sensor went in.

Why it works

A defect is cheapest to fix at the moment it happens, at the place it happens, while the cause is still visible. Every station it passes adds work to the bad unit and hides the evidence of what went wrong. End-of-line inspection finds defects after the line has made hundreds more of them.

Stopping looks expensive because the lost minutes are visible and the bad bottles downstream are not. The arithmetic runs the other way: the fix takes the same two minutes whenever the stop comes, and every minute of delay only adds bad units. The stop also makes each abnormal condition impossible to ignore, so the same cause gets found and fixed for good, which is how a line that stops often at first ends up stopping rarely.

The thinking behind it

Sakichi Toyoda Sakichi Toyoda, the inventor who founded the Toyota group, built power looms that stopped themselves when a thread broke or ran out, beginning with his Toyoda Power Loom of 1896 (Toyota's own history dates its completion to 1897). A loom that halts at the first broken thread weaves no more bad cloth, and that habit is the origin of building quality in by stopping at the first defect.

Taiichi Ohno Taiichi Ohno, the Toyota executive regarded as the father of the Toyota Production System, made autonomation, or jidoka, one of the system's two pillars beside just-in-time production, and set it out in Toyota Production System: Beyond Large-Scale Production (1978; English edition 1988). In his account, machines and workers stop the moment something is abnormal, so each problem is seen and fixed where it starts.

How to run it

  1. List the abnormal conditions. Write down every condition that should halt the work, such as a short fill, a missing part, or a failed test.
  2. Detect each one where it happens. Put a sensor, a check, or an automated test at the station that creates the defect, not at the end.
  3. Stop the process on detection. Make the stop automatic where possible, and give every operator the right to stop the line.
  4. Make the stop visible. Light a lamp or raise an alert at the station, so help arrives and the cause is seen.
  5. Fix the cause before restarting. Restart only after the cause is fixed or contained, and write it on a board.
  6. Count stops by cause. Review the board weekly and remove the most common cause for good.
  7. Reward the stop. Thank the operator who stopped the line, and never count a stop against the shift.

Where it goes wrong

Stops are counted as failures. If a shift is judged on minutes running, operators learn to let bad units through, and the sensor gets taped over. Measure defects that escape, and treat each stop as a problem found early.

The line restarts without a fix. Clearing the jam and pressing go brings the same stop back in an hour. Insist the cause is fixed or contained, and recorded, before restart.

Too many conditions stop the line. A sensor set too tight halts the line for variation that does no harm, and people stop trusting it. Set each threshold at what the next station or the customer cannot accept, and tune it from the board.

When to use something else

  • Poka-Yoke. When the defect can be made impossible by the design of the part or the fixture, so no stop is needed.
  • Control Chart. When the process drifts slowly and the need is to see the trend before it produces defects.
  • Five Whys. When a stop has happened and its cause needs tracing past the obvious first answer.

Where it sits in SOLVE eX

Go to the source

  • Self-stopping automatic loom, 1896
  • Toyota Production System: Beyond Large-Scale Production, Japanese original 1978; English edition 1988, 1978
  • The Toyota Way, 2004

Back to the catalog