- \n
- Maintenance and production do not measure the same availability.<\/li>\n
- Changeovers, waiting and micro-stops are left out of maintenance availability.<\/li>\n
- Both indicators can be configured to flatter the line.<\/li>\n
- A single source of time-stamped, typed stops reconciles both views.<\/li>\n<\/ul>\n<\/div>\n
It is a familiar scene. Maintenance presents 98% availability. Production answers with an OEE whose availability rate is much lower. Both are right, and that is exactly the problem: they are not measuring the same thing.<\/p>\n
Two availabilities, two definitions<\/h2>\n
For maintenance, availability measures the equipment’s ability to run. It is calculated from breakdowns: uptime divided by total time, or MTBF divided by the sum of MTBF and MTTR. A changeover, a material shortage or a missing operator are not breakdowns. They are left out of the calculation.<\/p>\n
For production, the OEE availability rate compares run time with planned production time. Any unplanned stop brings it down, whatever the cause: breakdown, adjustment, changeover, missing parts, waiting for a quality check.<\/p>\n
So a machine can be perfectly reliable in the maintenance sense and poorly available for production. The disagreement is not about wrong numbers. It is about a scope nobody ever spelled out.<\/p>\n
Then there are micro-stops. In the most common OEE convention, they count against the performance rate rather than availability. Some plants put them under availability. Both approaches hold up, as long as micro-stops are counted somewhere, which is rarely the case.<\/p>\n
What FreeMaint highlighted on the maintenance side<\/h2>\n
In Maintenance KPIs that lie<\/a> (in French), FreeMaint takes apart three indicators every CMMS displays. Their finding fits in one sentence: “It’s their configuration that lies.”<\/p><\/blockquote>\n
- \n
- Inflated MTBF.<\/strong> When preventive and corrective work are mixed in the failure counter, the more preventive work you do, the better MTBF looks. In their example, the naive MTBF comes out at 159 hours, versus 1,752 hours when only real breakdowns are counted.<\/li>\n
- Underestimated MTTR.<\/strong> It only counts repairing the equipment, not the downstream line waiting or reworking the batch. Their example shows 2 hours of MTTR for around 32 hours of actual downtime.<\/li>\n
- Overstated availability.<\/strong> Short stops cleared without a work order do not show up. FreeMaint estimates that around 60% of line stops last less than 15 minutes. In their example, availability drops from 98.9% to about 97.8% once those stops are added back in.<\/li>\n<\/ul>\n
Their conclusion applies to production too: the indicator is correct, it is the way it is built that misleads.<\/p>\n
![\"Diagram](\"https:\/\/teeptrak.com\/wp-content\/uploads\/2026\/10\/teeptrak-backlink-a2-en.png\")
<\/figure>\nThe same mechanism on the production side<\/h2>\n
OEE has its own ways of flattering a line.<\/p>\n
- \n
- An overly generous ideal cycle time.<\/strong> If the theoretical rate is set below the machine’s real rate, the performance rate is automatically inflated. Slowdowns become invisible.<\/li>\n
- “Planned” stops that are not really planned.<\/strong> Classified as a planned stop, a changeover or a cleaning is removed from planned production time. OEE goes up without the line making a single extra part.<\/li>\n
- Good parts instead of first-pass good parts.<\/strong> Counting a reworked part as good wipes out the quality loss, even though the rework used machine time and labor.<\/li>\n<\/ol>\n
In all three cases, the number still holds up in a meeting. It just no longer tells you where capacity is being lost.<\/p>\n
Getting maintenance and production to agree<\/h2>\n
- “Planned” stops that are not really planned.<\/strong> Classified as a planned stop, a changeover or a cleaning is removed from planned production time. OEE goes up without the line making a single extra part.<\/li>\n
- Underestimated MTTR.<\/strong> It only counts repairing the equipment, not the downstream line waiting or reworking the batch. Their example shows 2 hours of MTTR for around 32 hours of actual downtime.<\/li>\n
- Inflated MTBF.<\/strong> When preventive and corrective work are mixed in the failure counter, the more preventive work you do, the better MTBF looks. In their example, the naive MTBF comes out at 159 hours, versus 1,752 hours when only real breakdowns are counted.<\/li>\n