The OEE Number Nobody Acts On
In the first conversation, a plant manager describes the problem plainly. Line 3 is the bottleneck. Changeovers eat the first hour of most shifts. They run three shifts, with a fifteen-minute break in each and a planned maintenance window every Friday. And the monthly OEE report, the one number everyone is supposed to manage by, arrives in the second week of the following month.
When the first OEE dashboard shows up, it reports a single plant-wide percentage. It doesn't mention Line 3, it can't separate changeovers from breakdowns, and it counts the Friday maintenance window as lost time. The plant manager looks at it and asks the same questions again, because the number answers none of them.
Why OEE Arrives Late and Wrong
Overall Equipment Effectiveness is a simple idea: Availability times Performance times Quality. Availability is run time as a share of planned production time. Performance compares actual output to what the machine could do at its ideal cycle time. Quality is good units as a share of total units. The arithmetic is easy. Agreeing on what goes into it is not.
- Planned production time is a business decision. Whether breaks, planned maintenance and changeovers count against the denominator changes the result. Someone has to decide, and it's usually decided in conversation, not in a spreadsheet.
- Ideal cycle time is rarely written down. Without an agreed figure, Performance becomes whatever the person building the report assumes it is.
- Stops get coded after the fact. Reason codes entered at the end of a shift, from memory, blur changeovers, jams and waiting for material into one bucket.
- A monthly average hides the line. By the time a plant-wide figure is reported, the shift and the machine that caused the loss are long gone.
What Changes When the Same Agent Builds It
In an Agent Relay, OEE isn't assembled from a report template. It's built by the agent that was in the first conversation, so the definitions the plant manager gave aloud become the definitions in the model: the shift pattern, the breaks, the Friday window, and the fact that Line 3 is where to look first.
It follows the same thread as the retail forecast and the delivery team: whatever the customer said about their business becomes an input, not a note that gets lost between meetings.
What This Actually Looks Like
- The shift calendar defines planned production time. Breaks and the maintenance window are excluded the way the plant manager said they should be, so Availability measures what the plant actually controls.
- Losses are separated, not blended. Changeover time shows up as an Availability loss on its own, so the first-hour problem on Line 3 is visible instead of averaged away.
- The view is by line and shift, in near real time. A supervisor sees today's number during the shift, not next month's average after it.
- Definitions are written down once. Ideal cycle time, what counts as a good unit, and what counts as planned downtime are recorded in one place, so everyone is arguing about the plant and not about the formula.
Why This Matters Beyond Speed
An OEE figure people don't trust gets ignored, and then it stops being managed. The usual cause isn't bad math. It's that nobody can explain what's in the number. When the definitions come straight from the people who run the plant, and anyone can see how a loss was classified, the number becomes something a shift lead can act on while there's still time to change the outcome.
That matters because OEE is only useful at the speed of the floor. A loss that is visible during the shift can be fixed during the shift. The same loss, reported a month later, can only be explained.
Next In the Relay
This is the sixth post in the Agent Relay series, one continuous AI carrying context across the whole customer journey instead of resetting at every handoff. To see how we approach this industry, read about AI and BI for manufacturing. Next up: customer support, and why the agent that answers a ticket should already know the deal behind it.
If your OEE report arrives after the shifts it describes, that's not a reporting problem. That's a relay with a broken leg.