TMM-0060 Machine Stoppage — Practical Problem Solving Report

▸ Historical Context — Toyota Problem Solving Development, circa 1960

Toyota in 1960 — Two Parallel Disciplines

This report depicts events at Honsha Plant circa 1960, a period when Toyota was developing two distinct but complementary disciplines that would shape the company for decades.

Organizational: Hoshin Kanri and PDCA — Eiji Toyoda, Masao Nemoto, Mikio Sugiura, and others
The broader organizational discipline of PDCA-based management and policy deployment — what became known as Hoshin Kanri — was developed across Toyota in the 1960s and 1970s under the leadership of Eiji Toyoda and senior executives including Masao Nemoto and Mikio Sugiura. This effort, associated with Toyota's Kan-Pro (Kanri Promotion) program, embedded structured problem solving and annual policy objectives throughout the management system — from executive strategy down to departmental targets. It was influenced by Deming's quality thinking and adapted into a distinctly Toyota form of management. Machining operations at plants like Honsha were expected to carry Hoshin objectives — annual improvement targets with structured review cycles — in areas like equipment reliability, quality, and productivity.

Shop Floor: TPS and the 5-Why — Taiichi Ohno
On the shop floor, it was Taiichi Ohno who drove the discipline of direct observation and root cause investigation. Ohno coined the 5-Why method and insisted that group leaders and foremen ask why five times — not accept the first answer — before responding to a problem. This was floor-level discipline, applied at the machine, at the point of occurrence. It was Ohno's insistence that made the investigation of a stopped machine a structured inquiry rather than a maintenance call.

What distinguishes Toyota is not that they learned from failure — every organization does that eventually. NASA reorganized after Apollo 13, and again after Challenger, each time driven by catastrophic public failure. Toyota built these disciplines across ordinary production problems, every day, at every level — not as an emergency response but as normal operating practice. The MBR, the 5-Why, the lateral deployment, the standards codification: these were not special programs. They were the expected rhythm of an organization that had decided systematic learning was a competitive requirement.

Major Breakdown Reports (MBR) were one small part of this broader Hoshin-driven movement. The MBR system defined a threshold — four continuous hours of downtime — above which a machine failure became a formal production event requiring structured investigation, documented findings, and management review before restart. It was not a repair log. It was a problem solving trigger. MBR-1960-031 is one such event. This report reconstructs the investigation that followed, based on Ohno's published account and what is known of Honsha Plant operations in this period.

Step 01

Clarify the Background

Engine Block Machining — Honsha Plant

TMM-0060

Machine Type

Horizontal Milling Machine — Face Mill, Engine Block Top Deck

Location

Honsha Plant · Engine Block Line No. 3 · Operation 30

Report Trigger

Major Breakdown Report — Downtime exceeded 4-hour threshold

Plant

Toyota Honsha (Main Plant), Toyota City

Shop

Engine Block Machining, Building 3

Product

4-Cylinder Engine Block (Cast Iron)

Shift Goal

300 Blocks

Actual Output

125 Blocks

Incident Date

Circa April 1960

Reported By

T. Harada, Manufacturing Engineering
w/ Group Leader K. Tanaka, Shift 1

Engine Block Line No. 3 — Process Flow to Final Assembly (Op-10 through Op-300)

TMM-0060 — Horizontal Milling Machine Schematic (circa 1960, open design)

▸ Organizational Context — Toyota's Quality and Problem-Solving Movement in the 1960s

A Company-Wide Commitment to Quality Improvement

This machine failure occurred during a period when Toyota was building one of the most systematic quality improvement efforts in industrial history. Understanding the organizational context makes clear that the 5-Why investigation below was not one clever manager's technique — it was one expression of a company-wide movement.

In the late 1950s and throughout the 1960s, Toyota implemented several interlocking management disciplines across the company. Hoshin Kanri (policy deployment) established annual improvement objectives that cascaded from executive strategy down through every department and plant — including targets for equipment reliability, quality, and productivity in operations like machining. QC Circles engaged frontline workers in structured group problem solving on the shop floor, building capability and ownership at the team level. PDCA (Plan-Do-Check-Act) became the fundamental cycle underlying all improvement activity — from executive hoshin reviews to individual problem investigations like this one.

The emphasis was on improving quality systematically across design, engineering, and operations — not just reacting to defects after the fact. Toyota invested in statistical quality control methods, trained engineers in design of experiments, and built organizational routines for learning from every failure. The Deming Prize, which Toyota won in 1965, recognized exactly this kind of sustained, company-wide quality management capability.

Where the 5-Why Fits
Within this broader movement, Taiichi Ohno drove a specific discipline on the shop floor: direct observation and relentless root cause investigation at the point of occurrence. The 5-Why method — asking why five times before accepting any answer about a failure — was Ohno's tool for ensuring that group leaders and foremen did not stop at the first convenient explanation. It required no statistics, no special equipment — only disciplined thinking at the machine. The investigation of TMM-0060 is one example of this shop floor discipline in action.

This emphasis on structured problem solving at every level — from hoshin objectives to QC circle activities to Ohno's 5-Why at the machine — continued through the 1960s and remains central to Toyota's management system today. The machine failure described in this report is ordinary. The organizational response to it is what made Toyota different.

Step 02

Define the Problem

Machine Stopped — Production Line Starved

Standard

Zero unplanned stoppages
> 4 hrs per month per machine

Gap

6h 20m

Actual

TMM-0060 stopped April 14
Shift 1 production short of goal

Downtime Duration — TMM-0060, April 14, 1960

TMM-0060 DOWN — 6 hours 20 minutes

4h Threshold
MBR Triggered

0h1h2h3h4h5h6h6h20

Problem Statement: At 07:42 on April 14, 1960, TMM-0060 (horizontal milling machine, Engine Block Line No. 3, Op-30) stopped due to a blown overload fuse. The machine remained down for 6 hours and 20 minutes — exceeding the 4-hour MBR threshold. Shift 1 production fell well short of the 300-block goal. Buffer stock between Op-30 and engine final assembly was depleted, starving the assembly line for approximately 80 minutes.

Point of Occurrence

Op-30, TMM-0060 — face milling of engine block top deck surface. The machine stopped when the spindle motor overload fuse blew at 07:42. Machine locked out. Cause of the overload was not immediately apparent and required investigation.

Production Impact

Shift 1 production fell significantly short of the 300-block goal. Assembly line starved for approximately 80 minutes as buffer stock between Op-30 and engine final assembly was depleted.

▸ Organizational Context — Standards as the Baseline for Improvement

Without a Standard There Is No Baseline for Improvement

Defining a problem at Toyota means identifying the gap between a standard and the actual condition. This requires that standards exist — and in the 1960s Toyota was systematically building them across the entire organization.

Standards at Toyota operated at multiple levels. Production area performance standards established targets for productivity, quality, and equipment availability at the department and line level. Machine standards defined expected uptime, cycle time, and tooling life for each class of equipment. Process standards specified cutting conditions, feeds and speeds, machine static accuracy, and other parameters required to hold quality and throughput at each operation.

Beyond these operational standards, Toyota developed a set of proprietary company-wide standards that codified manufacturing knowledge into institutional architecture:

TMS — Toyota Manufacturing Standards: Facility-level and item-level standards common to all equipment — covering requirements that applied regardless of machine type.

MTS — Machine Tool Standards: Standards specific to machine tools — design specifications, performance criteria, and maintenance requirements for each class of equipment Toyota purchased and operated.

TMR — Toyota Manufacturing Regulations: The governance framework — how to determine process capability requirements, how to plan for machine purchases, how to investigate machine breakdowns, and how to feed data back to Production Engineering and equipment vendors so that lessons from operations improved future equipment design.

This is the architecture the problem statement above relies on. The "zero unplanned stoppages greater than four hours" standard was not an arbitrary target — it was part of a systematic framework that defined what normal looked like so that abnormal could be identified, investigated, and eliminated. Toyota was not just solving individual problems. It was building the system and architecture of company-wide improvement — and standards were the foundation.

Step 03

Set a Goal

Production · Reliability · Standards

Goal 1 — Production

300 engine blocks per shift at TMM-0060 with no unplanned downtime. Machine repaired and returned to Op-30 by end of Shift 2, April 14. Full production volume restored Shift 1, April 15.

Goal 2 — Reliability

Zero MBR events on TMM-0060 and all other milling machines in the machining department. No recurrence of lubrication-related bearing failure exceeding the 4-hour MBR threshold.

Goal 3 — Standards

Findings codified into TMS, MTS, and TMR. Initial standards revision within 30 days of MBR closure per TMR requirement. Full codification complete by Q3 1960.

▸ Organizational Context — Goal Setting and the Connection to Hoshin Kanri

Goals in Problem Solving Reflect Goals in the Organization

Setting a goal in a problem-solving report may look like a simple step — restore production, prevent recurrence, update standards. But at Toyota this step connects directly to Hoshin Kanri and the broader management system.

Starting in the 1960s, goals at Toyota became increasingly specific and visible at every operating level. Annual hoshin objectives cascaded from executive strategy through plant management to department and line targets — covering quality, delivery, cost, equipment uptime, and safety. A machining department did not set its own goals in isolation. Its targets for machine reliability, scrap reduction, and defect prevention reflected higher-level organizational objectives that had been deployed through the hoshin process.

This means the three goals in the report above are not just local problem-solving targets. The production goal connects to delivery commitments. The reliability goal — zero MBR events across the department — connects to plant-level uptime objectives and the broader push to eliminate unplanned stoppages as a class of waste. The standards goal connects to Toyota's institutional commitment to codifying learning so that improvements hold and transfer.

This alignment is what gives problem solving at Toyota its organizational weight. A group leader investigating a machine failure is not just fixing a local problem. The goals in the report reflect and contribute to improvement objectives that run all the way up through the management system. When those goals are met, they are reported upward through the same hoshin review cycle that set them. Problem solving and organizational management are connected — not separate activities.

Step 04

Identify Root Causes

5-Why Analysis — TMM-0060

The Problem

TMM-0060 stopped. Overload fuse blew. Machine locked out.

Observed by operator at 07:42. Immediate action: lockout/tagout applied, maintenance notified. Fuse confirmed blown on inspection.

Why 1 — Why did the fuse blow?

The spindle motor was overloaded — drawing more current than the fuse rating allowed.

Fuse rating: 15A. Draw at trip estimated >22A. Overload confirmed by electrician. Mechanical resistance in the spindle drive identified as the source.

Why 2 — Why was the motor overloaded?

The spindle bearing had failed — insufficient lubrication caused the bearing surface to degrade, creating resistance that overloaded the motor.

Bearing disassembly: dry, scored bearing surface. Lubrication had failed progressively before final seizure. Bearing replaced during repair.

Why 3 — Why was the bearing insufficiently lubricated?

The lubrication pump was not delivering sufficient oil to the bearing.

Pump output measured at 0.4 L/min against specification of 1.2 L/min. The pump was running but could not maintain adequate output or pressure.

Why 4 — Why was the lubrication pump output insufficient?

The pump shaft was worn — metal chips that had entered the lubrication system had abraded the shaft, reducing pump efficiency over time.

Pump disassembly: shaft showed wear marks consistent with abrasion by fine metallic particles. Output had degraded gradually, not suddenly. The worn shaft could no longer maintain rated pressure and flow.

Why 5 — Root Cause — Why were metal chips inside the lubrication pump?

No strainer was fitted on the lubrication pump intake. Chips and metallic fines from the machining operation entered the lubrication system through the unprotected intake and progressively abraded the pump shaft until output fell below the minimum required to protect the bearing.

Verification — lateral investigation across Line No. 3: lubrication pumps on other milling machines inspected — all showed internal wear consistent with chip contamination. No machine had an intake strainer. Lubrication tank lids on multiple machines found warped or improperly seated, providing a direct entry path for airborne chips and metallic fines. The condition was systemic. TMM-0060 failed first — its pump showed the most advanced wear and its tank lid the worst fit.

Root Cause: No strainer on the lubrication pump intake. Metal chips from machining entered the unprotected pump, abraded the shaft, and reduced output below the minimum required to lubricate the spindle bearing. The bearing failed progressively, then seized, overloading the motor and blowing the fuse. The condition existed on every similar machine on the line — TMM-0060 happened to be first to cross the failure threshold.

▸ Organizational Context — Root Cause Findings Are Not Local

From One Machine to the Organization

In most organizations, a root cause finding fixes one machine and the investigation ends. At Toyota the root cause finding was the beginning of a broader organizational response — not the end of one.

The scope of action expanded in concentric rings:

1. The affected machine: TMM-0060 was repaired — strainer installed, pump shaft replaced, tank lid resealed, system flushed. The immediate problem was solved.

2. Similar machines in the same facility: Every milling machine on Line No. 3 and in the machining department was inspected. The same condition — no strainer, worn pump shafts, poorly seated tank lids — was found across the line. The countermeasure was deployed laterally to all affected machines before they failed. Toyota calls this Yokoten — lateral deployment.

3. Similar machines in other facilities: The finding was communicated to other Toyota plants operating the same class of equipment. Those plants investigated their own machines and applied the same countermeasures where the condition existed.

4. Feedback to Production Engineering: The root cause was reported back to Production Engineering — the group responsible for writing equipment specifications and purchasing machines. The finding that no strainer was specified on the lubrication pump intake was not just an operations problem. It was a gap in the equipment specification. Production Engineering updated TMS and MTS standards so that future purchase specifications would require intake strainers, proper tank lid sealing, and lubrication system design criteria that prevented this class of failure.

5. Feedback to the equipment vendor: The root cause and updated requirements were shared with the machine tool builder. Toyota did not simply buy better machines next time — they told the vendor what to change and why, with the expectation that the design improvement would be incorporated into future equipment. This closed the loop between shop floor failure and equipment design.

This is the organizational architecture that most accounts of the 5-Why example leave out. The 5-Why identified the root cause. What happened next — the lateral deployment, the standards update, the feedback to engineering and vendors — is what prevented the problem from recurring across the company. Root cause analysis without organizational deployment is just local troubleshooting.

Step 05

Develop Countermeasures

Four Levels — Immediate Through Systemic

Level 1

Immediate Fix

Day 1 — April 14

Strainer + Tank Lid Sealing on TMM-0060 — Return to Production

Replace seized spindle bearing and worn pump shaft — repair work required to restore TMM-0060 to running condition. Install fine-mesh strainer on lubrication pump intake. Replace warped lubrication tank lid and reseal to prevent chip ingress. Flush lubrication system completely. Op-30 returned to production before start of next shift. Strainer inspection and lid check added to PM checklist.

Prevention — Blocks chips from entering lubrication system

Level 2

Short-Term

Weeks 1–3

Lateral Deployment (Yokoten) — All Milling Machines, Engine Block Line No. 3

The TMM-0060 investigation confirmed the same condition existed across all other milling machines on the line. Lateral investigation is not optional — if the root cause is systemic, so is the countermeasure. Install lubrication pump intake strainers on all machines during scheduled downtime windows. Inspect every lubrication tank lid — replace warped or damaged covers, reseal all units. Inspect pump shafts for wear — replace any showing chip abrasion damage. Strainer and lid inspection added to weekly PM route for all machines.

Yokoten — Same fix deployed to every affected machine

Level 3

Medium-Term

Months 1–3

Reduce Chip Scatter — Guard Extensions + Chip-Breaking Insert Geometry

Address the machining environment that makes chip ingress possible. Fabricate and install sheet metal chip deflector guards on both sides of the milling zone — the 1950s open machine design had no lateral containment. Specify chip-breaking insert geometry appropriate for gray cast iron, producing shorter, more controllable chips. Redirect coolant nozzle angles to flush chips toward the collection tray rather than the machine interior. These changes reduce the contamination load reaching the lubrication system and extend strainer service intervals.

Elimination — Reduces chip contamination at source

Level 4

Systemic

Months 3–6

Update TMS, MTS, and TMR — Embed Learning into All Future Milling Machine Purchases

The investigation produced specific, verifiable knowledge about what machine design permits this failure. That knowledge belongs in the equipment specification — not the maintenance manual. TMS (common to all machines): enclosed lubrication system with gasketed lid, integral pump intake strainer. MTS (machine tool specific): lateral chip guarding, chip-breaking insert geometry for ferrous machining, chip collection tray standard. TMR (regulatory): standards revision required within 30 days of MBR closure; incoming machine inspection against TMS and MTS before production qualification; change point management sign-off at installation. Every milling machine purchased after this update arrives already solving the problem that stopped TMM-0060. This is mizen boshi — prevention before occurrence.

Mizen boshi — Future machines cannot develop this condition

▸ Organizational Context — Countermeasure Types and Strength

The Countermeasure Must Match the Strength of the Cause

Most organizations that experience a machine failure like TMM-0060 respond by cleaning the machine, reminding operators to be more careful, and adding a checklist. None of that changes the physical condition that caused the failure. Within months, the same failure recurs — and the organization wonders why their problem solving didn't hold.

Toyota taught countermeasure development in terms of three types, arranged by strength:

Administrative countermeasures depend on human behavior and discipline. There is a critical distinction between good and bad administrative responses. Bad administrative — generic instructions, awareness memos, verbal reminders — provides the illusion of a countermeasure without changing anything structural. Good administrative — scheduled PM with specific inspection criteria, documented routes, assigned ownership with audit — is slower to degrade because it is structured. But even the best PM schedule depends on sustained human attention and cannot catch a failure that develops between inspection intervals.

Detection countermeasures use engineered devices to signal an abnormal condition before failure occurs. A low lubrication flow warning or an abnormal motor current monitor converts a surprise catastrophic stoppage into a managed condition. Detection is substantially stronger than administrative because the machine signals its own condition — it does not depend on a technician catching the problem on a scheduled visit.

Prevention countermeasures change the physical or design condition so that the failure mode cannot develop. The intake strainer physically blocks chip entry. Chip-breaking insert geometry reduces airborne contamination. Coolant flow redesign and internal guarding contain chip scatter. Prevention does not depend on human attention after implementation.

The four levels of countermeasure above reflect this hierarchy. Level 1 installs a strainer — prevention on one machine. Level 2 deploys it laterally. Level 3 reduces the contamination source. Level 4 embeds the learning into equipment standards so that the failure mode is designed out of every future machine before it arrives on the floor.

The pattern most organizations miss: They identify the root cause correctly. Then they apply only administrative countermeasures. The failure recurs. The discipline Toyota developed is that a structural root cause requires structural countermeasures. The strainer held not because operators became more careful. It held because the chips could no longer get in.

Step 06

Implement Countermeasures

April 1960 — October 1960

April 14, 1960 — Day 1

TMM-0060 Repaired and Returned to Production

Strainer installed on lubrication pump intake. Lubrication tank lid inspected — warped cover replaced and resealed. Pump shaft replaced. Lubrication system flushed. Spindle bearing replaced. Machine returned to Op-30 by 16:20. Shift 2 production resumed on schedule. MBR investigation report filed by Group Leader Tanaka.

April 15–28, 1960 — Week 1–2

Lateral Deployment (Yokoten) — Strainer + Lid Sealing, All Milling Machines, Line No. 3

Maintenance team installed lubrication pump intake strainers on all other milling machines during scheduled downtime windows. Every lubrication tank lid inspected — warped or ill-fitting covers replaced and resealed. Pump shafts inspected on each machine — several showed abrasion wear and were replaced. Strainer and lid inspection added to weekly PM route. The same condition that stopped TMM-0060 was confirmed present to varying degrees on every machine on the line.

April 28 – May 15, 1960 — Weeks 3–5

Chip Deflector Guards Fabricated and Installed

Tooling shop fabricated extended chip deflectors for Line No. 3 milling machines. Installed on all machines in sequence with production. Trial run confirmed chip scatter into sump reduced by approximately 70% on test machine.

May – July 1960 — Months 2–3

Insert Geometry and Coolant Direction Changes

Manufacturing engineering trialed chip-breaking insert geometry on TMM-0060. Coolant nozzle angles redirected. Chip accumulation rate in sump reduced. Changes applied to full line after trial confirmation. Strainer cleaning interval extended from weekly to bi-weekly based on reduced accumulation.

May 1960 — Within 30 Days

TMS, MTS, and TMR Updated — Standards Codified

Manufacturing engineering submitted revised specifications to the Toyota Manufacturing Standards group within 30 days of MBR closure. TMS updated for lubrication system requirements (enclosed tank, gasketed lid, pump intake strainer) — applicable across all machine types at Honsha. MTS updated for machine tool chip management (guarding, insert geometry, coolant direction) — applicable to engine plant machine shops. TMR updated to require incoming machine inspection against current TMS and MTS before production qualification. Standards distributed to procurement and filed for application to the Kamigo Engine Plant planned for 1965 launch.

▸ Organizational Context — Every Problem Feeds Back to Standards

The Strainer Is a Local Fix — The Standards Update Is the Organizational Fix

Installing a strainer on TMM-0060 solved the problem on one machine. Deploying strainers across the line solved it for existing equipment. But left alone, both are local countermeasures. The next milling machine Toyota purchases arrives without a strainer — and the problem repeats.

This is why every problem at Toyota was captured and related back to the standards that allowed the problem to happen in the first place. The investigation of TMM-0060 did not just ask "why did this machine fail?" It asked "why did our standards permit a machine to be purchased and installed without a strainer on the lubrication pump intake?"

The answer was that TMS, MTS, and TMR — Toyota's manufacturing standards — did not require it. The standards gap was as much the root cause as the missing strainer. Fixing the machine without fixing the standards leaves the organization exposed to the same failure on every future machine purchase.

TMS (Toyota Manufacturing Standards) was updated to require enclosed lubrication systems with gasketed lids and integral pump intake strainers — applicable across all machine types.

MTS (Machine Tool Standards) was updated for chip management requirements specific to machine tools — guarding, insert geometry, coolant direction.

TMR (Toyota Manufacturing Regulations) was updated to require incoming machine inspection against current TMS and MTS before production qualification — and to require that MBR investigation findings be fed back to Production Engineering and equipment vendors within 30 days of closure.

This feedback loop — from shop floor failure, through investigation, to standards revision, to Production Engineering specifications, to equipment vendor requirements — is the mechanism that converted a single machine breakdown into permanent organizational improvement. The standards ensured that every future machine arrived already solving the problem. The vendor feedback ensured that the machine builder understood what to change and why.

Without this loop, problem solving is local and temporary. With it, every problem makes the organization permanently better. This is the architecture of company-wide improvement — and it runs on standards.

Step 07

Check Results

Zero Recurrence — 60 Days Post-Repair

MBR events on TMM-0060
in 60 days following repair

All

Milling machines in machining dept.
with strainers installed

Lubrication failure bearing events
across all machining dept. mills, 60 days

MBR Events — TMM-0060 Post-Repair Trend (60-Day Verification Window)

Period	MBR Events	Note
April 14, 1960	1	The event — 6h 20m downtime, MBR triggered
April 15 – April 30, 1960	0	TMM-0060 back in production April 15; strainer + lid sealing installed; lateral deployment to machining dept. mills begins
May 1960	0	All machining dept. milling machines strainered and lid-sealed; weekly PM inspection confirmed on schedule
June 1960	0	60-day verification complete — zero recurrence on TMM-0060 and across machining dept.; target confirmed met

Result Verification

TMM-0060 met the 300-block production goal on April 15, Shift 1 — the day after the failure. The machine ran without MBR-level downtime through the 60-day verification window. Weekly strainer and lid inspections confirmed chips were being intercepted before entering the lubrication system. Strainer service time: approximately 8 minutes per machine per week — a known, planned activity replacing an unknown, catastrophic failure mode.

No milling machine in the machining department triggered an MBR for lubrication-related bearing failure during the 60-day verification period following lateral deployment. Prior to this investigation, periodic bearing failures had occurred across the department but had not been connected to a common root cause.

Step 08

Standardize & Share Learnings

From One Machine to Every Future Machine

Standards Updated — Three Levels

TMS — Toyota Manufacturing Standard

Lubrication Systems — All Machine Types

Lubrication tank: enclosed design with gasketed, properly fitted lid — open or warped covers not approved for any machine type
Fine-mesh strainer required on lubrication pump intake — cleanable without tools, accessible during scheduled downtime
Strainer and lid condition: verified at weekly PM interval, documented on PM route card
Applicable to all machine types — machining, welding, painting, casting — across all Toyota manufacturing facilities

MTS — Machine Tool Standard

Milling Machines — Engine and Transmission Plants

Lateral chip guarding: both sides of milling zone, minimum 300mm height — required at procurement
Coolant nozzle direction: specified to direct flow toward chip collection tray, not into machine interior
Insert specification: chip-breaking geometry required for ferrous (cast iron) machining operations
Chip collection tray or conveyor: standard equipment, not optional add-on
Applicable: Honsha Plant machining operations; Kamigo Engine Plant (planned 1965 launch) — standards in place at procurement

TMR — Toyota Manufacturing Regulations

Equipment Reliability — Governance Requirements

MBR required for any equipment stoppage exceeding 4 continuous hours — investigation mandatory before restart
Hard failures (bearing, lubrication, drive) require preventive maintenance schedule and periodic audit after MBR closure
Standards revision required: TMS and MTS to be updated within 30 days when MBR investigation identifies a design gap
Incoming machine inspection: new equipment verified against current TMS and MTS before production qualification
Change point management: new machine installation requires manufacturing engineering sign-off confirming standard compliance

▸ Organizational Context — The Complete Learning Sequence

What Most People Miss About This Example

The world teaches this case as a lesson in root cause analysis — the 5-Why chain in Step 4. But the 5-Why is only one step in an eight-step process, and root cause analysis is only one part of what made Toyota's approach to problem solving different. What happened in Steps 5 through 8 is the part that made the organization better — and it follows a specific sequence that should not be collapsed or skipped.

Stage 1 — Fix the Affected Machine. TMM-0060 failed. The investigation determined why. The machine was repaired — strainer installed, pump shaft replaced, tank lid resealed, system flushed. This is reactive. The problem already occurred. Most organizations stop here.

Stage 2 — Yokonarabi-Tenkai (横並び展開) — Lateral Deployment. The investigation confirmed the same condition existed on every similar machine on the line. Deploying the countermeasure to machines that had not yet failed — before they failed — is what Toyota calls Yokonarabi-Tenkai, lateral deployment. This is where problem solving crosses from fixing one machine to preventing the same failure across existing equipment. Many organizations never take this step. They fix the broken machine and move on, leaving identical machines running with the same vulnerability.

Stage 3 — Standards Codification. The learning was codified into TMS, MTS, and TMR — the standards that govern how Toyota specifies, purchases, installs, and maintains equipment. This is the critical step most accounts leave out. The strainer is a local countermeasure. The standards update is the organizational countermeasure. Without it, the next milling machine Toyota purchases arrives without a strainer, and the problem repeats. Every problem was traced back to the standards that permitted it — and those standards were updated so that the gap could not recur. TMS, MTS, and TMR are proprietary Toyota documents with volumes of detail. They are not published, but their role is central to how Toyota converted individual failures into permanent organizational improvement.

Stage 4 — Mizen Boshi (未然防止) — Prevention Before Occurrence. On new equipment programs, design reviews consider known failure modes — including ones like this — and engineer them out before the first machine is built. The lubrication tank is enclosed by design. The strainer is integral to the pump. The chip guarding is part of the machine envelope. The problem cannot develop because the design never permits the conditions that cause it. This is mizen boshi in its full sense: prevention before occurrence, at the design stage. The requirements flow from Production Engineering to the equipment vendor — Toyota does not simply hope for better machines, it specifies what must change and why.

The Full Arc. A fuse blew on a milling machine in 1960. The investigation identified a missing strainer. The countermeasure was deployed laterally across the facility and to other plants. The finding was fed back to Production Engineering and the equipment vendor. The standards were updated. Future machines were designed so the failure could not occur. This is the architecture of company-wide improvement — Hoshin Kanri providing the objectives, structured problem solving providing the method, and standards providing the mechanism that converts local learning into permanent organizational capability. The 5-Why identified the cause. Everything that followed is what made Toyota better.

Location / Application	Countermeasure Shared	Method	Status
Engine Block Line No. 3 — all milling machines	Strainer installation, lid resealing, pump shaft inspection + PM route update	Direct implementation by maintenance during scheduled downtime windows	Complete — April 28
Honsha Plant — all other machining lines (milling machines and similar machine tools)	Strainer installation, guarding, lid inspection; PM route updated plant-wide	Plant maintenance deployment; manufacturing engineering oversight	Complete — May 1960
TMS / MTS / TMR — standards update	Lubrication system requirements, chip management specifications, incoming inspection and MBR governance codified	Manufacturing engineering → Toyota Manufacturing Standards group; 30-day revision per TMR requirement	Complete — October 1960
Equipment procurement — all future milling machine purchases	TMR: incoming machine inspection against current TMS + MTS required before production qualification	Manufacturing engineering sign-off at installation; non-conformances require resolution before machine acceptance	Active from October 1960
Kamigo Engine Plant — machining shop (planned 1965 launch)	MTS strainer, guarding, and lubrication system specifications embedded in equipment procurement standard — designed in before machine purchase	Manufacturing engineering: spec compliance required at machine acceptance; no retrofit needed	Planned — standards in place for launch

Beyond the Report — The Third Layer

The 5-Why gets taught as a technique. The eight-step process gets taught as a method. But there is a third layer that almost never appears in the literature — and without it, the organization does not get better over time.

This report shows one problem on one machine. But the machine that generated the famous 5-Why example was not special. Hundreds of similar problems were being investigated across Toyota's plants in the same period — bearing failures, tooling wear, coolant contamination, process variation, equipment design gaps. Each investigation produced local countermeasures. What made Toyota different was the organizational discipline to accumulate that learning systematically — to feed findings back into standards, into equipment specifications, into vendor requirements, into design reviews for future programs.

Over time, this accumulation produced improvements that no single problem could have generated on its own. Tooling geometry studies improved chip control across machining operations. Lubrication system design evolved toward enclosed sumps and integrated strainers. Coolant flush systems became more reliable. Equipment guarding standards addressed chip containment at the design stage. These advances did not come from one 5-Why or one 8-step report. They came from thousands of investigations, each contributing a small piece of learning to the standards and specifications that governed how Toyota designed, purchased, and operated equipment.

This third layer — the organizational architecture that captures, codifies, and deploys learning from ordinary problems — is invisible. It does not appear in the 5-Why. It is not a step in the eight-step process. But it is the mechanism that converted Toyota's problem-solving discipline into permanent organizational capability. Without it, each problem is solved locally and forgotten. With it, each problem makes every future machine, process, and standard permanently better. The 5-Why made this example famous. The third layer is what made Toyota better.

Machine Stoppage —Engine Block MachiningTMM-0060

Machine Stoppage —
Engine Block Machining
TMM-0060