Guide
Making OEE mean the same thing everywhere
Definitions, loss coding and the shared model that ends the cross-plant argument.
8 min read
The argument is about denominators
Most cross-plant OEE disputes are not about data quality. They are about which hours count as available time, whether planned maintenance is a loss, and how changeovers are treated.
Fix the definitions first and publish them next to the number. Data work before definition work is wasted work.
Loss codes must be short and mutually exclusive
A code list that operators cannot hold in their head produces garbage. Ten to fifteen top-level reasons with optional sub-reasons beats a hundred flat codes, every time.
Show the calculation with the result
Every published OEE figure should expose its inputs, its window and its rule. When the calculation is visible, disputes resolve in the tool instead of in the meeting.
Read next
Explainer
The real decision cadence of a plant — daily, weekly, monthly, quarterly
Most plant decisions are not made in a system. They are made in a meeting, from a spreadsheet someone rebuilt the night before.
9 min read
Explainer
Spreadsheet debt: the hidden operating system of manufacturing
The models that actually run scheduling, costing and planning are undocumented, unversioned and owned by one person.
8 min read
Start here
Ask one question. Get one answer. Today.
Start on the free tier with a single connection, or bring a real question to a working session and we will build the first answer with you.
Free tier · No credit card · Cloud or self-hosted