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

Opening: A Problem Hidden in Plain Sight

It is Monday morning at a mid-sized automotive components plant. The production team leader walks the line during the first shift and notices something familiar — machine B7 has stopped again. The operator resets it, production resumes, and the event is logged as a “minor stoppage.” By Friday, the same machine has stopped eleven more times. No alarm was raised, no formal problem was recorded, and no improvement activity was initiated. The loss quietly accumulated. This scenario plays out in plants every day, not because people are careless, but because there is no structured bridge between the daily observations of operators and the formal improvement system. That bridge, in a mature TPM environment, is the connection between Autonomous Maintenance and Kobetsu Kaizen.

Understanding the Role of Autonomous Maintenance as a Problem-Detection Engine

Autonomous Maintenance (AM) is one of the eight pillars of TPM and is fundamentally concerned with restoring and sustaining basic equipment conditions. Its early steps — cleaning, inspecting, and eliminating sources of contamination and forced deterioration — are not simply housekeeping activities. They are, in practice, a systematic method for surface abnormalities that would otherwise remain invisible until they cause a breakdown or quality defect.

During AM Step 1, operators perform an initial cleaning that functions simultaneously as an inspection. This process, often described as “cleaning is inspection,” generates a structured list of abnormalities: oil leaks, loose bolts, worn components, difficult-to-access lubrication points, and sources of dirt or dust. These findings are physically tagged, counted, and recorded. The very act of identifying and categorizing these abnormalities begins to reveal the underlying losses affecting equipment performance.

By AM Step 2, the focus shifts to eliminating contamination sources and improving accessibility. At this stage, operators and TPM coaches start to analyze why abnormalities occur and where recurring problems cluster. This is where the data generated by AM activities begins to directly feed the Kobetsu Kaizen problem list. Abnormalities that cannot be resolved through simple operator action — because they require engineering changes, process redesign, or deeper root cause analysis — become candidates for formal KK projects.

AM Step 3 introduces the development of provisional cleaning and inspection standards. When teams discover that certain standards are impossible to maintain without first resolving an underlying equipment or process issue, those issues are formally escalated as improvement topics. The feedback loop between AM and KK becomes explicit and structured at this stage.

In this way, AM acts as a continuous problem-detection engine. Every cleaning cycle, every inspection round, and every abnormality tag is a potential input to the KK problem list. Without AM, the KK team depends on breakdowns and production reports alone to identify improvement opportunities — a reactive, incomplete, and costly approach.

How AM Data Flows into the Kobetsu Kaizen System

Kobetsu Kaizen, which translates literally as “individual improvement,” is the TPM pillar dedicated to eliminating the 16 major losses that reduce overall plant effectiveness. These losses are grouped into equipment losses, process losses, and resource losses — including breakdown losses, minor stoppages, reduced speed, set-up and changeover losses, and losses in energy, materials, and tools.

The connection between AM activities and KK is both structural and operational. Here is how the data and problem-identification flow works in practice:

1. Abnormality tags generated during AM cleaning and inspection are reviewed in team meetings. Tags that represent recurring or systemic issues are transferred to the KK problem list for prioritization.
2. OEE data and loss analysis — which AM teams begin to understand and contribute to as they advance through the steps — reveal patterns of minor stoppages and reduced speed that are directly linked to the equipment conditions being managed through AM.
3. The 5-Why analysis applied to abnormalities discovered during AM activities often reveals root causes that require structured KK projects, involving cross-functional teams, engineering resources, and formal countermeasure development.
4. One-Point Lessons (OPLs) created during AM activities document both problems and initial countermeasures, providing the KK team with contextual knowledge about the equipment history and the nature of recurring failures.
5. Kaizen boards — maintained visually in the production area — display both AM abnormality status and active KK projects, creating transparency and ensuring that problems identified on the floor are visible to management and improvement teams.

This integration is not accidental. A well-functioning TPM system is designed so that the pillars reinforce each other. AM generates the granular, ground-level observations. KK provides the structured methodology — including cause-and-effect analysis, cost-benefit analysis, and countermeasure validation — to resolve the more complex problems that AM uncovers. Together, they create a closed-loop improvement system rooted in the Gemba, where the work is done and the value is created.

Practical Example: Precision Parts S.p.A.

Precision Parts S.p.A. is a fictitious but realistic manufacturer of machined components supplying the industrial equipment sector. When the plant introduced TPM, the KK team initially relied on breakdown reports and weekly OEE summaries to select improvement projects. Progress was slow, and the team often found themselves addressing symptoms rather than root causes.

When AM was introduced on the machining line, operators began conducting structured cleaning and inspection sessions for the first time. Within three weeks, they had identified 47 abnormality tags across six machines. Among them: a recurring coolant contamination issue on machine M12 that had been causing gradual spindle wear, contributing to reduced cutting speed and intermittent dimensional defects that appeared as waste and rework losses in the OEE data.

The abnormality could not be resolved by the operators alone — it required a modification to the coolant delivery system. It was formally transferred to the KK problem list, prioritized based on its estimated production loss impact, and assigned to a cross-functional team. Using a Problem Solution Story approach — including a structured 5-Why analysis and cause-and-effect diagram — the team identified the root cause as a design weakness in the coolant filtration unit and implemented a permanent countermeasure within four weeks.

The result was a measurable reduction in minor stoppages and rework on that machine, an improvement in MTBF, and — critically — an increase in operator engagement. The AM team could see that their observations directly triggered improvement actions. The KK team had a richer, more operationally grounded problem list. Both pillars became stronger because of their connection.

Key Takeaways

• AM is not just maintenance — it is a structured problem-discovery process. Cleaning, inspection, and abnormality tagging during AM steps generate a continuous flow of improvement inputs that directly feed the KK problem list.
• The 16 losses targeted by Kobetsu Kaizen are often first made visible through AM activities. Minor stoppages, reduced speed, and quality defects are frequently rooted in basic equipment conditions that AM exposes.
• A formal escalation path from AM abnormalities to KK projects is essential. Problems that exceed the operator’s authority or technical scope must be captured, prioritized, and actioned through the KK system without delay.
• Visual management tools — including Kaizen boards and OPLs — connect AM and KK in the Gemba. They ensure transparency, maintain momentum, and make improvement progress visible to the entire team.
• Operator engagement deepens when AM observations lead to visible KK results. The integration of AM and KK creates a virtuous cycle: operators who see their findings acted upon become more motivated to look harder, report more accurately, and contribute to the improvement system.