faktry

operations

How to Calculate OEE for Batch Processing (With Chemical Factory Numbers)

OEE formula, worked example with Gujarat chemical factory data, common calculation mistakes. A practical guide for MSMEs tracking Overall Equipment Effectiveness.

Team Faktry · ·7 min read

OEE = Availability × Performance × Quality. For batch processing, measure Availability as run-time over scheduled time, Performance as theoretical-cycle × batches over run-time, and Quality as first-pass-QC batches over total batches. World-class OEE is 85%; most Indian chemical MSMEs land between 40% and 65% when they start measuring.

OEE — Overall Equipment Effectiveness — is the most widely cited metric in manufacturing. It’s also the most widely miscalculated. This guide walks through the formula with real numbers from a Gujarat dye unit, calls out the common mistakes, and shows how batch-processing OEE differs from discrete manufacturing.

What is the OEE formula?

OEE = Availability × Performance × Quality

All three as percentages (0 to 1, or 0 to 100%). OEE world-class benchmark is 85%. Most Indian chemical MSMEs that measure it land between 40% and 65% initially.

Availability

Fraction of scheduled time the equipment actually ran.

Availability = (Planned Production Time − Downtime) / Planned Production Time

Downtime includes: breakdowns, changeovers, cleaning (CIP), raw material wait, operator wait, power outages.

Performance

When running, how close to theoretical speed you actually ran at.

Performance = (Ideal Cycle Time × Units Produced) / Run Time

For batch processing, adapt this to: (Theoretical batch cycle) × (batches produced) / run time.

Quality

Fraction of output that passes QC first time.

Quality = Good Units / Total Units Produced

In batch processing: good batches / total batches. Reworked batches count as losses even if eventually released.

How does OEE calculation work on a real batch reactor?

Reactor RX-02 in a Vatva dye unit. Month: March 2026.

  • Scheduled hours for the month: 30 days × 22 hrs/day (2 hrs planned cleaning) = 660 hrs

  • Unplanned downtime (breakdown, power outages, long waits): 92 hrs

  • Available hours: 568

  • Theoretical batch cycle (Reactive Blue 19, 500 kg target): 7 hours

  • Batches actually completed: 62

  • Theoretical time: 62 × 7 = 434 hrs

  • Performance: 434 / 568 = 76.4%

  • Availability: 568 / 660 = 86.1%

  • Total batches: 62

  • First-pass QC passes: 52

  • Failed or reworked: 10

  • Quality: 52 / 62 = 83.9%

OEE = 0.861 × 0.764 × 0.839 = 0.552 → 55.2%

World-class is 85%. This reactor has significant headroom.

OEE component summary for RX-02 (March 2026)

ComponentInputValue
Availability568 run hours / 660 scheduled hours86.1%
Performance434 theoretical hours / 568 run hours76.4%
Quality52 first-pass batches / 62 total batches83.9%
OEE0.861 × 0.764 × 0.83955.2%
World-class benchmark85%

Where are the OEE losses hiding?

Look at each component:

  • Availability 86%: 92 hours of unplanned downtime across the month. Likely root causes: raw material wait (H-acid delivery delays), operator unavailability during shift handoffs, minor breakdown on stirrer motor. Each hour of avoidable downtime recovered = roughly 1 extra batch.
  • Performance 76%: Even when running, the reactor takes longer than theoretical. Usually: batches running longer for yield reasons, slow charging, coupling taking 20% longer than spec. This is the softest number to improve but also where process discipline pays off.
  • Quality 84%: 10 out of 62 batches failed first-pass QC. Costly — every failed batch is raw material waste, rework time, or dispose. Drilling into the failures (are they all the same product? same shift? same raw material lot?) usually reveals a single systemic cause.

A reactor improving from 55% to 65% OEE on the same shift count adds roughly 18% more finished output. For a typical dye reactor, that’s ₹8–15 lakh more monthly revenue at no additional fixed cost.

What are the most common OEE calculation mistakes?

Mistake 1: Confusing availability with utilisation

Utilisation = hours run / total calendar hours (includes planned shutdowns). Availability = hours run / scheduled production time. Many MSMEs calculate utilisation and call it OEE. Utilisation drops OEE to near-meaningless; it counts Sundays and holidays as “losses.”

Mistake 2: Ignoring changeovers

Changeover time between products is often classified as “planned downtime” and excluded from Availability. This hides a real efficiency lever. Include changeovers in downtime — then you’ll actually measure whether you’re reducing them.

Mistake 3: Counting reworked batches as passes

If a batch fails QC, gets reworked, and eventually passes — it’s a Quality loss, not a pass. Rework consumes real time and material. Counting reworked batches as “good” flatters the number and hides the problem.

Mistake 4: Using theoretical cycle for equipment that’s never hit theoretical

Some units set ideal cycle time equal to their best-ever batch. If your best batch was 6 hours but your design capability is 5 hours, you’re anchoring Performance to an achievable number, not a stretched one. Use the equipment manufacturer’s spec, not your history.

Mistake 5: Not collecting data at source

The biggest practical failure: OEE calculation depends on downtime logs, batch completion timestamps, and QC results being captured accurately at the source. If your shop floor writes all this on paper and someone re-enters it into Excel once a week, your OEE number has ±15% error bars. At that point, trends are illegible.

How to actually start tracking OEE

For an MSME running on paper today, OEE tracking has a minimum data requirement:

  1. Every batch start and end timestamp captured at source (not reconstructed)
  2. Downtime events logged with duration and reason category (breakdown, material wait, operator wait, changeover, other)
  3. QC outcomes — pass / fail / rework for every batch
  4. Ideal cycle time per product (calculated once, reviewed quarterly)

This is what Faktry’s Machine & OEE module captures automatically. Every batch logs start, end, downtime, QC result against the product’s ideal cycle — OEE per reactor, per shift, per product becomes a standing dashboard rather than a month-end Excel exercise.

Without the source data, OEE is a vanity number. With it, OEE becomes the metric that drives the highest-leverage improvements in any batch factory — because it points you directly at where the losses are.

The simplest starting point

If you’re not measuring OEE today:

  1. Pick one reactor or machine
  2. For two weeks, log batch start/end, every downtime event with cause, and QC outcome
  3. Compute OEE for that two-week window
  4. Drill into the biggest loss (availability, performance, or quality)
  5. Fix that one thing

You’ll almost certainly find a 5–10% OEE improvement within the first month. Scale the approach to your other equipment from there.

Faktry offers this data capture as part of the Machine & OEE add-on module on top of the ₹8,999 base plan. If you want to see how it works on your factory’s numbers, book a 30-day pilot — no credit card required.