Root Cause Analysis Methods demo
A fishbone whose every bone is proved or ruled out by a cited record, challenged as an inspector would, before the investigator signs the root cause. 1:30
What the demo shows
Root cause analysis for GMP investigators: 5-Why, Is/Is-Not and fishbone proved by records.
A method chooser suggests the method that fits the event, such as Is/Is-Not for a sudden change on one asset, a fault tree when a protective layer failed or FMEA for a process-wide weakness, and says why. One agent per fishbone bone proves or rules out each candidate cause from the batch record, historian, maintenance and change records, and a ruled-out cause stays visible, struck through, beside the record that cleared it. A challenger plays the inspector against the agents' own draft, a cause test checks that the surviving causes explain every fact, and a 5-Why carries each proved cause to a system cause. The investigator signs, and QA opens every record before approving.
Transcript
- Root Cause Analysis Methods helps GMP investigators rule causes in or out with records.
- Investigations are FDA's second most cited drug finding; six agents read the bones.
- The binder is ruled out: the same lot ran clean twice.
- The challenger plays inspector: why did no alarm stop the batch at 340?
- Its own draft missed it; change control CC-25-0219 proves a second cause.
- A 5-Why reaches each system cause; the cause test checks every fact.
- Nerys signs with her own ID, password and reason.
- Amara, the QA approver, opens each record herself, and approval stays locked until she has read every one.
- Then she approves with her own ID, password and reason; every step lands in the audit trail.
- New investigators reason like veterans; the fix reaches every granulator.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.