Why OEE definitions drift across plants

OEE sounds like a standard measure until the first cross-plant review. One plant may count planned micro-stops as availability loss, another may push them into performance, and a third may exclude them because the line is still technically staffed. None of those decisions are irrational. The problem is that the label stays the same while the rule behind it changes.

The easiest way to find drift is to ask for examples, not definitions. Pull five stops, five slow cycles and five quality holds from each plant. Then ask each operations team how those events enter the OEE calculation. The differences become visible quickly, and the conversation stays tied to production reality rather than spreadsheet doctrine.

ForgePulse Digital recommends a versioned KPI dictionary before the first dashboard launch. It should name the event, the source system, the transformation rule and the owner who can approve changes. That dictionary does not need to be long. It needs to be current and linked from the place where people read the KPI.