AHU-07 tripped on overload in the night, the shift reset it, and it has run since. That is the whole log entry, and none of it is a cause.
Five whys gets past it. Worked through on that trip:
- State the event with time and data. At 02:14 the drive tripped on motor overload at full speed, and room pressures were lost for 11 minutes.
- Ask why, and attach evidence to each answer. The fan was at full speed because the airflow loop was chasing its setpoint against rising resistance (speed trend, three weeks). Resistance rose because the final filters were loaded (differential pressure log). They were not changed because the high-DP alarm was set up as an event that notifies nobody, and the plan changes filters by calendar.
- Stop at a cause the site can change. "Filters were dirty" only buys new filters; the alarm class and the maintenance trigger change the system.
- Assign each action to an owner with a date: the alarm routed to maintenance, the filter task triggered by differential pressure.
- Check later that it worked: at the next loading cycle, see whether the filters were changed on the alarm before the fan reached its limit.
ICH Q10 says a structured approach to the investigation should be used, with the objective of determining the root cause. Five whys follows one branch; where two causes had to coincide, a fault tree, described in ICH Q9(R1), serves better.




