Net Equipment Effectiveness (NEE) vs OEE and TEEP

Net Equipment Effectiveness (NEE) is a production performance metric that multiplies Availability, Performance, and Quality just like OEE, but it measures the Availability portion against loaded (scheduled) time including the planned downtime that lands inside that loading window. In plain terms, NEE asks how effectively a machine ran during every minute it was supposed to be producing, without excusing planned stops such as changeovers, setups, or scheduled maintenance. That makes NEE a stricter, bottleneck-focused view of a single constraint asset, sitting between the shop-floor lens of OEE and the total-capacity lens of TEEP.

What NEE actually measures

Classic Overall Equipment Effectiveness (OEE) deliberately removes planned downtime before it calculates Availability. It starts from Planned Production Time, so a scheduled changeover or a planned maintenance window does not count against the score. That is useful for measuring how well operators and equipment perform during the time management already committed to running.

NEE takes a different stance. It keeps planned stoppages that occur inside the loaded time in the denominator, so the metric reflects the real throughput a constraint delivered against the time it was loaded. If your bottleneck sits idle for a two-hour planned setup, NEE feels that loss. This is why NEE is often applied to the single asset that governs plant output rather than to every machine on the floor.

The NEE formula

NEE uses the same three factors as OEE, but with a wider Availability base:

• Availability = Operating Time divided by Loaded Time (loaded time includes planned downtime that falls within it).
• Performance = (Ideal Cycle Time multiplied by Total Count) divided by Operating Time.
• Quality = Good Count divided by Total Count.

Then NEE = Availability multiplied by Performance multiplied by Quality. The Performance and Quality factors are calculated identically to OEE. The only structural difference is that NEE's Availability denominator is loaded time, so planned stops inside that window pull the number down instead of being subtracted out first.

NEE vs OEE vs TEEP

These three metrics differ only in the time base they measure Availability against. Understanding the ladder makes the whole family click:

1. TEEP (Total Effective Equipment Performance) uses all calendar time (24 hours a day, 7 days a week) as its base. It shows how much of your theoretical maximum capacity you are converting into good product. See TEEP for the full breakdown.
2. NEE uses loaded time including any planned downtime that falls inside it. Stricter than OEE, looser than TEEP.
3. OEE uses planned production time, which already excludes planned downtime. It is the fairest measure of execution during committed run time.

Because they share the Performance and Quality factors, the score always falls in the order TEEP is less than or equal to NEE, which is less than or equal to OEE. If your OEE looks healthy but NEE is much lower, planned downtime is quietly eating your constraint. If you also want the utilization angle, pair NEE with capacity utilization to see how much of your available hours you actually load.

A worked numeric example

Take one shift on a bottleneck line:

• Shift length: 480 minutes (8 hours).
• Planned downtime inside the shift: 30 minutes (a scheduled changeover) plus 20 minutes (planned cleaning) = 50 minutes.
• Unplanned downtime: 40 minutes (a breakdown and a jam).
• Ideal cycle time: 1.0 minute per unit.
• Total units produced: 360, of which 342 were good.

For NEE, loaded time is the full 480 minutes. Operating Time = 480 minus 50 planned minus 40 unplanned = 390 minutes.

• Availability = 390 / 480 = 0.8125 (81.3 percent).
• Performance = (1.0 multiplied by 360) / 390 = 0.923 (92.3 percent).
• Quality = 342 / 360 = 0.950 (95.0 percent).
• NEE = 0.8125 multiplied by 0.923 multiplied by 0.950 = 0.712, or 71.2 percent.

For OEE on the same shift, planned production time removes the 50 planned minutes first: 480 minus 50 = 430 minutes. Availability = 390 / 430 = 0.907. Then OEE = 0.907 multiplied by 0.923 multiplied by 0.950 = 0.795, or 79.5 percent. The 8.3 point gap between OEE (79.5) and NEE (71.2) is exactly the cost of that planned downtime on your constraint, a loss OEE hides but NEE exposes.

When to use NEE

NEE shines when you are managing a true bottleneck under the Theory of Constraints. Every minute lost on the constraint, planned or not, is a minute of lost plant throughput, so a metric that refuses to forgive planned stops keeps attention where it matters. Use NEE to:

• Justify changeover reduction and setup improvement (SMED) projects, since NEE rewards shorter planned stops directly.
• Track the payoff of moving maintenance from reactive to proactive maintenance, which shrinks both planned and unplanned loss.
• Distinguish planned from unplanned downtime on the constraint so improvement effort targets the bigger bucket.

Where Fabrico fits

Any effectiveness metric is only as trustworthy as the time data underneath it, and manual stop logging is where most numbers fall apart. Fabrico provides real-time OEE and production monitoring that automatically timestamps every run, stop, and micro-stop, then classifies planned versus unplanned downtime so you can compute NEE, OEE, and TEEP from one clean dataset. Its camera and computer-vision monitoring captures cycle counts and stoppages even on older machines that have no PLC, which is exactly where bottlenecks often hide. Fabrico is EU-built with EU data residency. Note that NEE itself is a calculation methodology, not a Fabrico feature: what Fabrico supplies is the accurate, timestamped foundation the metric needs. Downtime causes then flow into the CMMS as work orders, closing the loop between measurement and action.

Frequently Asked Questions

Is NEE always lower than OEE?

Yes, whenever any planned downtime falls inside the loaded time. NEE keeps that planned downtime in its Availability denominator while OEE removes it first, so NEE's Availability factor is equal to or smaller than OEE's, making NEE equal to or lower than OEE. They only match when there is zero planned downtime in the window.

Does Fabrico calculate NEE automatically?

Fabrico delivers real-time OEE and production monitoring with automatically captured, timestamped downtime data separated into planned and unplanned categories. That is the exact input NEE requires, so the metric is straightforward to derive from Fabrico's numbers. NEE is an industry calculation method rather than a named product feature, and Fabrico's role is the reliable data foundation.

Should I replace OEE with NEE?

No, use them together. OEE is the right lens for judging execution during committed run time across many machines, while NEE is the right lens for a single constraint where planned stops still cost throughput. Watching the gap between them tells you how much planned downtime is holding back your bottleneck, and pairing both with TEEP shows total capacity headroom.

Ready to build every effectiveness metric on data you can trust? Book a Fabrico demo to see automatic, real-time downtime tracking on your lines, including machines with no PLC, and turn OEE, NEE, and TEEP into decisions your team can act on.