Key takeaways
Short answer: Safety incident rate (TRIR or similar) measures injury frequency. OEE measures equipment effectiveness. In poorly-run operations, pushing for OEE can lead to shortcuts that cause incidents — the metric and safety appear to trade. In well-run operations, both improve together because the practices that drive OEE (standard work, 5S, autonomous maintenance) also drive safety. Trading safety for OEE is always a sign the OEE program is wrong. See also Run Rate vs Design Rate.
The most common safety metric in manufacturing is TRIR (Total Recordable Incident Rate), calculated as:
TRIR = (Number of recordable incidents x 200,000) / Total hours worked
Recordable incidents per 200,000 hours worked (roughly 100 full-time workers for one year). Industry benchmarks vary; manufacturing is typically 2-5.
Variants: LTIR (Lost Time Incident Rate), DART (Days Away, Restricted, Transferred). All measure injury frequency normalized to hours worked.
Three patterns where chasing OEE produces safety incidents:
Plants with poorly-designed OEE programs often see incident rate rise as OEE rises. The cause is not OEE measurement; it is the incentive structure around it.
The practices that drive OEE in mature operations are also safety practices:
In mature plants, the correlation between OEE and safety is positive: better organized = both safer and more effective.
Both incident rate and OEE are lagging indicators — they report what already happened. The leading indicators that drive both:
Plants that track leading indicators move both OEE and safety in the right direction.
1. Reporting OEE without safety context. Hides whether OEE gains came from shortcuts.
2. Treating safety as a constraint on OEE. They are not in tension when the operating system is right.
3. Rewarding only the lagging numbers. Drives short-term gaming; misses the leading practices that matter.
4. Investigating incidents without OEE context. Production pressure that caused the incident is invisible if OEE is not part of the post-incident review.
A modern platform allows safety-related downtime to be tagged with specific reason codes, reports OEE alongside safety incidents in the same dashboard, and surfaces near-miss reports as leading indicators alongside OEE losses.
Fabrico's OEE module supports safety-tagged downtime reason codes, integrates with safety incident systems for combined dashboards, and exposes near-miss data as leading indicators for both effectiveness and safety.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
Industry varies. Manufacturing world-class is around 1.0 or below; industry average is 2-5.
Yes. Reporting them separately allows shortcuts to be hidden.
Yes, when poorly designed. Safety must be veto in the metric system.
Near-miss reports, autonomous maintenance compliance, 5S audit scores.
Yes, in Availability loss with safety reason code. Track them so they are not hidden, but never penalize stopping for safety.
Login
Blog