Key takeaways
Short answer: Downtime reason codes are the categories operators select when logging a stop. The taxonomy design is where most plants ruin their OEE analytics — too many codes, too vague, too overlapping. A useful taxonomy has 10-20 codes per line, mutually exclusive, easily recognized by operators. Designed for analysis, not completeness. The 90 minutes spent designing this set right are worth years of cleaner analytics. See also PLC Fault Code Design.
Five properties:
1. Too many codes. 50+ codes per line. Operators cannot scan the list; they pick the first plausible one. Analytics noisy.
2. Too few codes. 3-5 generic codes. Pareto is meaningless; everything is "equipment fault" or "material."
3. Overlapping codes. "Mechanical failure" and "Mechanical breakdown" exist as separate codes. Operators pick randomly between them.
4. Codes that mix root cause with symptom. "Sensor fault" and "Wrong product" might both be triggered by the same root cause. Confusing.
5. Codes for the planner's needs, not the operator's. "PM Type 3.4.b" means nothing to a technician at 3am.
Availability losses:
Performance signals:
Quality signals:
~18 codes. Each operator-recognizable. Each maps to a specific action.
"Other" is the smell. If it is more than 5% of stops, the taxonomy is missing categories. Add codes for what is actually happening.
Audit: pull a week of "Other" entries with their free-text comments. Cluster them. Promote frequent clusters to dedicated codes.
Some platforms support two-level reason codes (category → subcategory). This can help operators (pick category fast, drill subcategory) but only if the second level is genuinely useful. If second-level is rarely used, simplify to one level.
1. Letting each line define its own taxonomy. Cross-line comparison becomes impossible.
2. Never reviewing. Taxonomy decays as equipment and processes change.
3. Codes that mix structured and free-form. "Other - see notes" defeats the structured-data purpose.
4. Punishing operators for honest reason codes. "Safety stop" should be welcomed, not buried.
A modern OEE platform supports configurable reason code taxonomies, surfaces "Other" rate and Pareto distribution, and lets the data steward refine the taxonomy without losing historical comparability.
Fabrico's OEE module supports tiered reason codes, surfaces taxonomy quality metrics ("Other" rate, distribution skew), and allows refinement with versioned history.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
10-20 per line is typical. More than 30 makes operator selection unreliable.
Categories yes; subcategories tailored to the line. The high-level structure should be consistent.
Under 5%. Higher means the taxonomy is missing categories.
Increasingly. ML on PLC signatures plus operator-entered context can suggest codes. Human confirmation usually preserved.
Monthly for "Other" rate, annually for full taxonomy review.
Login
Blog
