Closed work orders, open RCAs. The Copilot drafts the first-pass 5-Whys from the work order context. A fishbone aggregates every cause across the asset class. Repeat failures stop being invisible.
Problem statement
Hydraulic Pump A-2 lost pressure during batch 1442
Why did pressure drop?
Internal seal was leaking past its spec.
Why was the seal leaking?
Shaft was running 0.03mm above tolerance.
Why was the shaft out of tolerance?
Bearing preload was incorrect after the last swap.
Why was preload incorrect?
SOP was using old torque spec.
Copilot draft
Suggesting why #5: Why was the SOP still using old torque?
The 5-Whys form will not save if any entry is missing the question or the answer. That alone stops 80 percent of the lazy 'operator error' RCAs that linger in most systems.
Sequential drill-down with question AND answer per entry. Corrective + preventive actions required before save.
Auto-aggregates causes across the asset class. Confidence levels, frequency counts, linked WOs per cause node.
Every closed RCA produces corrective and preventive actions with assignees, due dates, and verification sign-off.
Draft, diagram, track, prevent. Every closed work order feeds the next fix.
Copilot
Drafted from WO #1247 context
Why 1
Pressure dropped because the seal was leaking.
Why 2
Seal wore past tolerance.
Why 3
Bearing preload wrong.
WO context in, 5-Whys draft out. Engineer refines in place and saves.
Causes grouped by category. Tap a node to see confidence, frequency, and linked WOs.
Open CAPAs · 12
Update SOP 117 torque spec
Retrain shaft-bearing swap
Verify on next PM
Audit torque tools
Every closed RCA produces CAPAs with assignees, due dates, and verification gates.
Repeat offenders · 90d
Pump A-2
Seal wear
Chiller C-1
Refrig leak
Conveyor 3
Belt slip
Gearbox GX-8
Alignment
Assets with the same root cause twice in 90 days land here for priority intervention.
Not a form-filling exercise. A structured investigation with Copilot help, live aggregation, and a CAPA gate at the end.
Every entry requires both a question and an answer. Incomplete investigations cannot save. No more 'operator error' at why number 2.
The Copilot reads the work order, the asset, the issue, and drafts a first-pass 5-Whys. Engineer refines, not writes from scratch.
Auto-rolls RCAs into an Ishikawa with confidence levels, frequency counts, and linked work orders per cause node.
Corrective action (immediate fix) AND preventive measure (systemic prevention) are both required before save. No half-solutions.
Every closed RCA produces CAPAs with assignees, due dates, and verification sign-off. Nothing closes without proof.
Assets with the same root cause twice in 90 days surface for priority intervention. The dominant failure mode reveals itself.
RCA becomes read-only once the parent WO is closed. Audit trail tracks createdBy, updatedBy, and every field change.
High / Medium / Low confidence on every saved RCA based on fix history and repeat success. Fishbone nodes colour-code accordingly.
A closed unplanned downtime event prompts a RCA from the production module. No manual handoff.
We had the same seal failure on four different pumps. The fishbone showed it was a torque-spec issue in the SOP, not the seal. One SOP update killed four recurring failures.
Reliability Engineer · Pulp & Paper Mill
-50%
Repeat failures
Dominant cause reveals itself once the fishbone has a quarter of data in it.
3 min
First-draft RCA
Copilot drafts from WO context so the engineer refines, not writes from scratch.
100%
CAPAs verified
Verification gate refuses close until every action is signed off.
Every closed WO is the starting point of an RCA, with Copilot drafting the first pass.
Learn moreEvery NC feeds the RCA tracker. Corrective actions roll up to the fishbone.
Learn moreClosed unplanned downtime auto-prompts an RCA before the shift ends.
Learn moreRCA findings feed the PM optimization board so the next interval is informed by real causes.
Learn moreTurn on the fishbone, let the Copilot draft the first pass, and watch the dominant cause reveal itself within a month.