How to Improve OEE with ERP Data in Your Factory

Why OEE matters and where the data already lives

A 2 % rise in Overall Equipment Effectiveness can add the same margin as a 10 % sales increase, yet most plants measure OEE on paper or not at all. The data needed—shift start times, cycle counts, defect logs—already exists in the ERP system; it is simply not pulled together in one place.

OEE is the product of three ratios: availability (time the machine ran divided by planned time), performance (actual output divided by theoretical maximum at running speed) and quality (good pieces divided by total pieces). Each ratio can be read from standard ERP documents: shift rosters, batch cards and quality inspection sheets. Facteno, for example, records every machine stop against a reason code and every defect against a 4-point score, so the data is already structured for OEE.

Map OEE terms to ERP fields

Start by listing the ERP fields that correspond to each OEE component.

• Availability needs planned shift duration, actual start and stop times, and unplanned downtime reasons.
• Performance needs theoretical cycle time per piece, actual pieces produced, and any speed losses recorded.
• Quality needs total pieces inspected, defect counts and rework quantities.

In Facteno these fields are already present on the production module shift log and batch card. If your current ERP lacks a machine journal, add a custom field to the shift log called “Machine ID” and another called “Stop Reason” with a drop-down list: breakdown, material shortage, changeover, operator absent, power cut, maintenance.

Set up the data capture routine

Decide who records what and when.

• Shift supervisors log actual start and stop times on the shift card, not on a separate sheet.
• Operators record every stop longer than two minutes on the batch card, selecting a reason from the drop-down.
• Quality inspectors enter defect counts directly into the quality module as they inspect each batch.
• Production planners enter theoretical cycle times once per product family and update them when the standard changes.

Train the team to use the ERP screens instead of paper. If operators forget to log a stop, the shift supervisor reconciles the batch card at shift end and corrects the ERP record before closing the shift. This keeps the data clean and ties it to the production ledger.

Calculate OEE with a worked example

Illustration: a single-shift weaving loom

Planned shift: 8 hours (480 minutes).
Actual start: 08:05, actual stop: 16:55, so planned production time = 530 minutes.
Recorded stops: material shortage 20 min, breakdown 15 min, power cut 10 min, total unplanned downtime = 45 minutes.
Running time = 530 – 45 = 485 minutes.
Availability = 485 ÷ 480 = 101 % (capped at 100 % for OEE).

Theoretical cycle time: 1.2 minutes per metre.
Actual output: 380 metres.
Theoretical maximum = 485 ÷ 1.2 = 404 metres.
Performance = 380 ÷ 404 = 94 %.

Total pieces inspected: 380.
Defects: 8 (2 major, 6 minor).
Good pieces = 380 – 8 = 372.
Quality = 372 ÷ 380 = 98 %.

OEE = 100 % × 94 % × 98 % = 92 %.

Build a daily OEE report that reconciles with finance

Create a report that shows OEE per machine, per shift and per product family. The report must tie to the production ledger and the costing module so the numbers are auditable.

Add a summary row that shows total planned minutes, total running minutes, total output and weighted-average OEE. This summary must match the shift log totals in the production module and the output quantities in the finance ledger. If it does not, the reconciliation process begins: check batch cards, shift logs and inspection sheets until the numbers agree.

Identify the largest loss category

Group the unplanned downtime reasons into three buckets: availability losses (breakdowns, power cuts, operator absent), performance losses (speed drops, small stops) and quality losses (defects, rework).

In the example above, availability losses totalled 45 minutes, performance losses 24 minutes (404 – 380) and quality losses 8 pieces. The largest bucket is availability, so the improvement effort starts there. Drill into the breakdowns: if the 15-minute stop was caused by a bearing failure, schedule preventive maintenance; if it was a material shortage, check the inventory module for stock-outs.

Close the loop with corrective actions

Once the largest loss category is identified, assign corrective actions to specific roles.

• Maintenance manager schedules preventive maintenance for the bearing failure on Loom-3.
• Production planner reviews the material shortage and adjusts the reorder point in the inventory module.
• Quality manager investigates the two major defects and updates the inspection checklist.

Record each action in the ERP task list with a due date and owner. Facteno links tasks to the original shift log or batch card, so the follow-up is visible to the whole team. After the action is completed, the next OEE report will show whether the loss has been reduced.

What to do next week

Pick one bottleneck machine and run the process for four weeks.

1. Map the three OEE components to existing ERP fields.
2. Train the shift team to log stops and defects directly into the ERP screens.
3. Calculate OEE for the machine every shift and post the number on the shop floor.
4. Identify the largest loss category and assign one corrective action.
5. Review the OEE trend after four weeks and decide whether to expand to the next machine.

If the ERP system does not capture machine stops, start with a paper batch card that lists the stop reasons. After two weeks, move the data into the ERP so the numbers are visible to planners and accountants.