Lesson 1: KK and Autonomous Maintenance: How AM Activities Generate and Feed KK Problem Lists

Opening: A Signal from the Shop Floor

It is 6:45 in the morning at a packaging line in a mid-sized consumer goods plant. During the daily autonomous maintenance routine, an operator on Step 2 notices that the conveyor belt guide rail shows unusual wear marks — not a breakdown, not yet, but a clear abnormality. He tags it, records it in the AM defect log, and moves on. By the end of the week, three similar observations have been logged across two shifts. A team leader reviews the data and realizes this is not a random occurrence: it is a recurring loss pattern hiding behind normal operations. This is exactly the moment when Autonomous Maintenance (AM) and Kobetsu Kaizen (KK) connect — and when individual improvement begins to generate real, measurable value.

Understanding the Relationship Between AM and Kobetsu Kaizen

Kobetsu Kaizen — literally meaning individual improvement — is one of the eight pillars of TPM (Total Productive Maintenance). Its purpose is to systematically eliminate losses across the production system. As established in the TPM framework, these losses are organized into the 16 Loss Model, which includes eight major equipment losses (such as breakdowns, setup losses, minor stoppages, and reduced speed), five process losses, and additional losses in energy, tools, and materials.

Autonomous Maintenance, on the other hand, is the pillar focused on developing operator ownership of equipment. Through a structured step-by-step progression, AM trains operators to clean, inspect, lubricate, and detect abnormalities before they become failures. What is critical to understand is that these two pillars are not independent activities — they are deeply interdependent.

AM activities, particularly in Steps 1 through 3, generate a continuous stream of observations from the shop floor: cleaning reveals contamination sources, inspection uncovers hidden defects, and standardization exposes deviations from optimal equipment conditions. Each of these observations is a potential input for a Kobetsu Kaizen project. In practical terms, AM creates the problem list that KK teams use to prioritize and launch improvement activities.

The connection works in both directions. While AM feeds KK with problems and abnormality data, KK countermeasures — once implemented — improve the stability of equipment and reduce the burden on AM teams. When a KK team eliminates a contamination source identified by an operator during cleaning, that operator’s future cleaning time is reduced. This is a direct synergy: AM sustains the conditions, KK improves them.

How AM Activities Generate and Prioritize KK Problem Lists

The process of translating AM observations into structured KK projects follows a logical and data-driven path. Understanding each step helps plant managers and team leaders establish a reliable pipeline of improvement activities.

Step 1 — Abnormality Detection and Tagging

During initial cleaning activities in AM Step 1, operators are trained to systematically note abnormalities. These are recorded using tags or defect cards attached directly to the equipment. Common categories include oil leaks, loose fasteners, unusual vibrations, abnormal heat, and contamination sources. This is not casual observation — it is a structured and auditable process that produces documented data on equipment condition.

Step 2 — Contamination Analysis and Loss Classification

In AM Step 2, the focus shifts to understanding where abnormalities come from. Contamination analysis asks why dirt, dust, or fluid accumulates in specific areas. This deeper investigation often reveals systemic causes — a seal design flaw, an inadequate guard, or a process parameter out of range. At this stage, the data collected begins to align with the KK loss categories: Is this a breakdown precursor? A source of minor stoppages? A driver of quality defects? The classification of each abnormality into the 16 Loss framework is what transforms an operator observation into a quantifiable KK opportunity.

Step 3 — Problem Solution Story and Root Cause Analysis

By AM Step 3, teams are applying structured problem-solving methodologies such as the 5-Why analysis and Cause-and-Effect (Ishikawa) diagrams to address the root causes of recurring abnormalities. These tools are foundational to the KK methodology. A problem identified through AM that cannot be resolved at the operator level — because it requires engineering intervention, budget approval, or cross-functional coordination — is formally escalated to a Kobetsu Kaizen project. This escalation ensures that no observation is lost and that every confirmed loss has a responsible improvement track.

Feeding the KK Board with AM Data

Visual management plays a critical role in making this connection visible and actionable. AM teams maintain display boards that show the status of tagged abnormalities, and KK teams maintain their own Kaizen boards showing active improvement projects. A well-designed visual management system links these two boards: abnormalities that have been escalated to KK status are reflected on both, giving the entire team transparency on what is being worked on, who owns it, and what the expected outcome is in terms of loss reduction.

Practical Example: Flemington Consumer Products

At Flemington Consumer Products, a manufacturer of household cleaning solutions, the line team responsible for the bottle-filling area had been struggling with an OEE score stuck at 61% for two consecutive quarters. The maintenance department attributed the low performance primarily to minor stoppages and increased rework, but the root causes remained unclear.

When the plant launched AM Step 2 on the filling line, operators began recording abnormalities during their weekly cleaning sessions. Within three weeks, 34 tags had been raised. Of these, 12 related to nozzle wear patterns, 8 to inconsistent fill-level readings, and 7 to a recurring film of product residue building up on the sensor housing. These observations were classified against the 16 Loss framework: nozzle wear was linked to tool change losses and quality defects, while sensor contamination was connected to minor stoppages and measurement and adjustment losses.

The team leader escalated two clusters of observations to formal KK projects. The first project used a 5-Why analysis to trace nozzle degradation back to an abrasive cleaning agent used upstream, leading to a material substitution that extended nozzle life by 60%. The second project addressed the sensor contamination source, resulting in a simple guard redesign that eliminated the residue build-up entirely. Within eight weeks, minor stoppages on that line dropped by 38%, and the OEE moved to 74%. The AM defect log had become the most valuable source of improvement data the team had.

Key Takeaways

• AM is the primary source of KK problem lists: Systematic abnormality detection during cleaning and inspection activities creates a structured, documented pipeline of improvement opportunities that directly feed Kobetsu Kaizen prioritization.
• Classification against the 16 Losses is the bridge: Translating AM observations into the KK loss framework transforms shop floor data into quantifiable improvement projects with measurable impact on OEE and cost.
• Root cause tools are shared between AM and KK: The 5-Why analysis and Cause-and-Effect diagrams are used in both pillars, creating a common problem-solving language that strengthens cross-functional collaboration.
• Visual management connects the two pillars: Linked AM defect boards and KK Kaizen boards make the improvement pipeline visible, accountable, and aligned to production targets.
• The synergy is bidirectional: KK countermeasures reduce the workload of AM teams, while AM activities continuously surface new opportunities for KK — creating a self-reinforcing cycle of sustainable improvement.