Overall Equipment Effectiveness (OEE) for Malaysian Plants
OEE = Availability x Performance x Quality, but the number only helps if it comes from machine signals. How to measure OEE honestly, and what low OEE does to your kWh per unit.

Overall equipment effectiveness (OEE) is the percentage of planned production time your line spends making good product at rated speed. The formula is simple: OEE = Availability × Performance × Quality. The uncomfortable part is what happens when you measure it from machine signals instead of clipboard logs. Most plants measuring OEE honestly for the first time land between 40% and 55%, and because an idle machine still draws power, every point of lost OEE shows up twice: once as missed output, and again as a higher kWh-per-unit on your TNB bill. This guide covers both.
What is overall equipment effectiveness (OEE)?
OEE answers one question: of the time you planned to run, how much actually produced sellable units? It multiplies three factors, each between 0 and 100%:
- Availability = run time ÷ planned production time. Losses: breakdowns and changeovers.
- Performance = (ideal cycle time × total count) ÷ run time. Losses: minor stops and slow cycles.
- Quality = good count ÷ total count. Losses: rejects and rework.
A worked example for one 8-hour shift (480 minutes planned):
- Downtime of 60 minutes leaves 420 run minutes → Availability = 87.5%
- Ideal cycle time is 1 minute per unit, so 420 units were possible; the line made 380 → Performance = 90.5%
- 361 of the 380 units passed inspection → Quality = 95.0%
- OEE = 0.875 × 0.905 × 0.950 = 75.2%
That line lost a quarter of its planned shift, even though "we ran all day" is what the shift report would say. The framework comes from Seiichi Nakajima's Total Productive Maintenance work in 1970s Japan, and it is now a standardised KPI under ISO 22400-2, so the calculation itself is settled. The arguments are always about where the input numbers come from.
Where each of the three numbers really comes from
Each factor has one honest data source, and a familiar dishonest one.
Availability should come from a run/stop signal on the machine: a PLC status bit, a SCADA tag, or a current sensor on the drive. The dishonest source is an operator downtime log, which reliably misses short stops and rounds long ones in the machine's favour.
Performance needs an ideal cycle time. Use the nameplate or engineering-rated cycle, not the "comfortable" rate the line has drifted to over five years. If you benchmark against a degraded rate, performance reads 98% while the machine runs 15% slow.
Quality needs a good count at the end of the line, not a scrap bin estimate. If your reject counting happens at a later QC station, tie those rejects back to the shift and machine that produced them, otherwise quality losses vanish into overhead.
The pattern: every factor is honest when it comes from a sensor or counter, and flattering when it comes from a form.
What's a good OEE score? World-class is 85%, reality is nearer 60%
The benchmark for world-class OEE in discrete manufacturing is 85%, built from Nakajima's component targets of Availability ≥90%, Performance ≥95% and Quality ≥99.9% (multiply them and you get about 85.4%). Note that it applies to discrete manufacturing, not process industries.
Reality is well below that. OEE.com reports that most manufacturers sit closer to 60%, and that they see more companies below 45% than above 85%. Sector ranges vary: automotive plants typically measure 70-80%, food and beverage 55-70%, pharmaceuticals 40-60%. Plants measuring for the first time commonly land in the 40-55% band, and that is normal, not a crisis. A first honest score of 48% is not a failing grade; it is a map of where half of your capacity went.
One warning: a score that jumps ten points in a month without any physical change on the line usually means the measurement got friendlier, not the machine.
The six big losses (and the ones your clipboard never catches)
The Six Big Losses map directly onto the three factors:
- Availability: equipment breakdowns, and setups/changeovers that overrun.
- Performance: minor stops and idling, and reduced-speed running.
- Quality: startup rejects after changeover or warm-up, and production rejects in steady state.
The convention is that a stop under five minutes counts as a minor stop (a performance loss) and anything longer is a breakdown (an availability loss). That five-minute line is exactly where manual logging fails. Nobody writes down a 90-second jam cleared with a broom handle, but thirty of those in a shift is 45 minutes, more than most recorded breakdowns. Reduced speed is worse: a line running 12% slow triggers no event at all, so a paper system literally cannot see it. This is why manually logged OEE routinely reads well above machine-sourced OEE on the same line.
How to instrument a line so the OEE number is honest
Three signals per machine are enough: a run/stop status, a total count, and a good count (or reject count). Practical rules:
1. Pull run/stop from the PLC or SCADA system you already have. Most Malaysian plants have the tags; they are just not historised or trended anywhere useful. An overlay platform reads them without touching control logic, so there is no rip-and-replace and no revalidation of the line.
2. Take counts from the machine counter, not ERP backflush. ERP tells you what was booked, hours later. OEE needs what the sensor counted, this minute.
3. Close the planned-downtime loophole. OEE only counts planned production time, so every hour reclassified as "planned downtime" inflates the score. Fix the definition in writing: scheduled maintenance and no-demand shutdowns are excluded; waiting for material, waiting for QA and unplanned cleaning are not.
4. Sub-meter the line while you are at it. A kWh meter on the incoming feed of each line costs little during the same wiring exercise and turns OEE into money, as the next section shows.
OEE and your electricity bill: kWh per unit produced
A machine that is powered but not producing still burns most of its energy. Research on machining finds that non-cutting activities, idle, standby and auxiliary functions, can account for as much as 80% of a machine tool's energy consumption. So a line at 50% OEE can draw nearly as much kWh as one at 75% OEE, while spreading it over far fewer good units. Your energy cost per unit rises even though the meter reading looks normal.
Two Malaysian specifics sharpen this. Under TNB's RP4 tariff (July 2025 onward), demand is billed on your single highest 30-minute average kW each month, split into Capacity (RM89.27/kW) and Network (RM97.06/kW) charges for medium-voltage general commercial customers; the mechanics are covered in our RP4 demand charge explainer. A stop-start line with poor OEE tends to restart everything at once, and that synchronised restart is a classic demand-peak generator.
Second, the Energy Efficiency and Conservation Act 2024 makes any site consuming 21,600 GJ or more over 12 months (roughly a RM2.4 million annual electricity bill) a regulated consumer, with a Registered Energy Manager, an energy management system and periodic reporting to Suruhanjaya Tenaga. Details in our EECA compliance guide. For a regulated factory, kWh per unit produced is now a compliance KPI, and OEE is the production-side lever that moves it.
Quick wins: what to fix first when OEE is 55%
Work the losses in order of tonnage, not glamour. For a typical 55% line:
- Changeover discipline. Film one changeover, separate what can be done while the machine runs (external work) from what cannot, and move everything possible to external. This SMED-lite exercise cuts changeover time substantially with zero capex. Energy bonus: less time with heaters, hydraulics and air compressors running against a stopped line.
- Minor-stop hunting. Rank stop reasons by total minutes, not by count. Fix the top two feeder jams or sensor misreads. Energy bonus: fewer idle-loaded intervals where the drive draws current for nothing.
- Slow-cycle detection. Compare actual cycle time to ideal per SKU. A worn cam or a nervous speed setting hides here. Energy bonus: kWh per unit falls almost linearly as cycle time recovers.
- Startup scrap. Track rejects in the first 30 minutes after every changeover separately. Every startup reject is full energy and material spend for zero yield.
Verify each fix with before/after data over comparable production weeks, not a single good day. That measurement-and-verification habit is the same one EECA auditors will ask you about.
How a plant monitoring platform captures OEE data automatically
CobiNeural is built for exactly this overlay role. Insights → Equipment reads run/stop and counts from existing PLC and SCADA systems and pairs them with sub-metered kWh, motor efficiency and vibration data, so OEE and energy-per-unit sit on the same screen for the same line. Alerts push a WhatsApp message when a line stops or a cycle-time anomaly appears, which turns minor-stop hunting from a monthly report into a same-shift response. Plan & Verify handles the M&V of each improvement, and Reporting produces the EECA submissions a regulated consumer owes Suruhanjaya Tenaga.
This is running in real Malaysian manufacturing today, at Mosca Malaysia, Kah Hwa Industry and PWO Industries among others, deployed as an overlay on the plants' existing control systems rather than a replacement for them.


