Direct Answer
Downtime root cause analysis on a paper container machine means separating the symptom from the cause and keeping a record that lets the biggest, recurring stops be traced to a controllable condition. A jam or a seized bearing is the symptom; the skipped lubrication point or wrong clearance behind it is the root cause. The 5-why method keeps asking why, with evidence, until the answer becomes an action you can take. Record the time, duration, station, fault code, material roll, tooling set, and restart action for every stop, then use a Pareto chart to rank the stops and attack the largest. Fixing the symptom clears the stop for now; fixing the cause prevents it from returning.
Opening Hook
A container line lost a day to the same forming jam three times in a month, and each time the crew cleared the jam and restarted — the symptom, not the cause. When someone finally asked why five times, the answer was a worn cam follower that had never been on the lubrication schedule, and the fix was ten minutes of greasing, not another day of clearing jams. The lesson is that a stop that keeps coming back is a cause that has not been found. At yoco-group, we build container machines and the data discipline to find the cause — here is the method.
Symptom vs. Root Cause — Ask Until It's Controllable
The analysis works only if it keeps going past the visible event to the condition you can fix.
| Level | Example | Question |
|---|---|---|
| Symptom | Forming jam | What happened? |
| Direct cause | Cam follower seized | Why did it seize? |
| Contributing cause | No lubrication on schedule | Why was it not lubricated? |
| Root cause | Point missing from the map | Why was it missing? |
| Corrective action | Add point to schedule | What prevents recurrence? |
Each step must be backed by evidence from the machine or the record, not by opinion. The analysis stops when the next answer is an action you can take and verify, not when someone runs out of patience.
Data: The Lean Enterprise Institute's A3 problem-solving resources describe structured root cause analysis that moves from the observed problem through repeated why questions to a countermeasure that addresses the cause, not the symptom.
Judgment: Write the stop, the why chain, and the countermeasure on one page, because a recurring stop that is only cleared and not traced will return on schedule, and each return is a day of output lost twice.
Source: Lean Enterprise Institute — A3 Problem Solving and Root Cause Analysis Resources (2024)
The 5-Why Method, Step by Step
The 5-why is a chain of evidence, not five guesses, and it ends in an action.
| Step | Do | Avoid |
|---|---|---|
| State the stop | One clear event statement | Vague or multiple events |
| Ask why | With evidence | Opinions or blame |
| Repeat | Until a controllable cause | Stopping at the symptom |
| Verify | Check the cause against data | Assuming without proof |
| Act | Assign and complete a fix | A fix that is not verified |
The method is a guideline, not a hard count of five. Sometimes the cause appears in three whys, sometimes in six; the test is whether the next answer is an action you can take, such as adding a point to the lubrication map or resetting a clearance.
Data: ISO 9001 quality management requires corrective action that addresses the cause of a nonconformity and verification that the action was effective, so the same problem does not recur.
Judgment: Close a downtime investigation only when a corrective action is assigned, completed, and verified against a later run, because a cause that is found but never fixed is analysis without result.
Source: ISO — ISO 9001 Quality Management Systems (2023)
Data, Pareto, and Where to Attack First
Not all downtime is equal, so rank the stops and attack the largest and most frequent first.
| Data to Record | What It Reveals |
|---|---|
| Stop time and duration | Total loss and trend |
| Station and fault code | Where and what fails |
| Material roll and tooling | Input that triggered it |
| Restart action | What was done each time |
| Repeat count | Whether it is recurring |
A Pareto chart ranks the stops so the few largest causes are addressed before the long tail of rare ones. A plant that attacks its top two stops by frequency and duration usually recovers more output than one that fixes whatever broke last.
Data: TAPPI's converting operations resources describe the operating and maintenance variables on paper converting lines, providing the machine-side reference for which inputs — roll, tooling, and station settings — to record against each stop.
Judgment: Record the roll, tooling set, and station with every stop, because a stop that cannot be linked to its inputs cannot be traced to a cause, and the record is what turns downtime into a solvable problem.
Source: TAPPI — Converting Equipment and Operations Resources (2024)
A Downtime Analysis Routine
A weekly routine keeps the analysis moving instead of letting stops pile up as anecdotes.
| Step | Action | Output |
|---|---|---|
| Collect | Pull the stop log | One list of stops |
| Rank | Pareto by frequency and time | Top causes |
| Analyse | 5-why the top stops | Cause chain |
| Act | Assign and complete fixes | Corrective actions |
| Verify | Confirm no recurrence | Closed investigation |
The routine is cheap, and the payoff is the end of the same jam, the same seized bearing, the same forming stop returning month after month. Root cause analysis is how a container line stops losing the same day twice.
A Buyer's Downtime Analysis Checklist
Confirm these items before accepting a paper container machine.
- A stop log that records time, duration, station, and fault code.
- Roll and tooling set recorded against every stop.
- A Pareto routine that ranks stops by frequency and duration.
- A 5-why discipline that traces stops to a controllable cause.
- Corrective actions assigned and verified against recurrence.
- A weekly review that keeps the analysis moving.
Adjacent decisions follow the same logic. Our paper machinery maintenance guide covers the program that prevents many stops, and our paper cup defects troubleshooting guide explains how to trace the defects behind the stops.
The Bottom Line
Paper container machine downtime root cause analysis separates the symptom from the cause and attacks the biggest, recurring stops with evidence. Record the time, duration, station, fault code, roll, tooling set, and restart action for every stop, rank them with a Pareto chart, and run a 5-why chain on the top causes until the answer becomes a controllable action. Assign, complete, and verify each fix. A stop that keeps coming back is a cause that has not been found, and the record is what finds it.
At yoco-group, we build container machines with the data discipline to trace a stop to its cause, so the same day is not lost twice.