Paper Container Machine Downtime Root Cause Analysis FAQ

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 addressing 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)

Data: ISO 9001 quality management requires corrective action that addresses the cause of a nonconformity and verification that the action was effective so the 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 found but never fixed is analysis without result.

Source: ISO - ISO 9001 Quality Management Systems (2023)

Data: TAPPI's converting operations resources describe the operating and maintenance variables on paper converting lines, the machine-side reference for which inputs 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.

Source: TAPPI - Converting Equipment and Operations Resources (2024)

What is the difference between a symptom and a root cause in machine downtime?

A symptom is the visible event, such as a jam or a seized bearing, while the root cause is the condition behind it, such as a skipped lubrication point or a wrong clearance. Fixing the symptom clears the stop for now, but the same stop returns because the cause is still there. Root cause analysis keeps asking why until it reaches the condition that, if fixed, prevents the symptom from recurring.

How do I use the 5-why method on a paper container machine stop?

Start with the stop as the first statement, then ask why it happened and repeat for each answer until you reach a cause you can control. Each why should be backed by evidence from the machine or the record, not an opinion. Five whys is a guideline, not a hard count; stop when the next answer is an action you can take, such as adding a lubrication point to the schedule.

Which downtime data should a container plant record for root cause analysis?

Record the time and duration of each stop, the station and fault code, the material roll and tooling set in use, and the action that restarted the line. This data lets a Pareto chart show which stops are the biggest and whether they repeat, and it links each stop to its inputs so a cause can be traced. Without this record, root cause analysis is guesswork.

Why do recurring stops return after they are cleared?

A recurring stop returns because the crew cleared the symptom, not the cause. Clearing a jam restarts the line, but the worn cam follower or skipped lubrication point behind the jam is still there, so the same stop reappears. The fix is to keep asking why, with evidence, until the answer becomes an action that removes the cause, then verify the stop does not return on the next run.

How should a plant choose which downtime problem to attack first?

Rank the stops with a Pareto chart by frequency and total duration, and attack the top causes first. A plant that fixes its top two stops by frequency and duration usually recovers more output than one that fixes whatever broke last. The long tail of rare stops can wait, because the biggest few causes are where most of the lost output actually sits.

How can a buyer verify a downtime analysis capability before accepting a machine?

Confirm the machine or the supplier's program records time, duration, station, and fault code for each stop, links each stop to its roll and tooling set, and supports a Pareto ranking and a 5-why discipline. Require corrective actions that are assigned and verified against recurrence, plus a weekly review. The capability proves itself in the stop log and the closed investigations, not in a slide about uptime.