Loading…
Loading…
How to turn Job Cards, workstations and downtime reasons into a real Overall Equipment Effectiveness number — and use it to find the hours you're losing.
Most plants know they're losing time on the shop floor — they just can't say where, how much, or why in a way anyone can act on. Overall Equipment Effectiveness (OEE) is the discipline that answers those questions, and it only works when it's built on real, captured data rather than end-of-shift memory. This paper is a practical, honest look at how ERPNext records the raw shop-floor signals — operation-level time logs on Job Cards, machine downtime with reasons, and produced-versus-rejected quantities — and how you turn those signals into a defensible OEE number. It is deliberately clear about what ERPNext captures out of the box and what you configure with a report or dashboard, so you go in with the right expectations.
The complete paper — every section, in a clean branded PDF you can share with your team. Free, no email required.
ERPNext captures every input OEE needs — Job Card time logs, Downtime Entries with reasons, planned-vs-actual operation times and produced-vs-loss quantities — but core does not ship a single pre-built OEE gauge. The Availability, Performance and Quality roll-up is configured with a Query Report, Report Builder view or dashboard on top of data ERPNext already stores.
Through the Downtime Entry doctype. Each entry logs the workstation, a from/to time (so the duration is known), the operator, free-text remarks and a structured Stop Reason. Because the reason is a defined field rather than a note, you can total downtime by reason across a month and see exactly where your hours are going.
Yes. The standard Stop Reason list (set-up time, unplanned maintenance, machine malfunction, operator errors, electricity down, and so on) is a starting point. Using Customize Form you can replace it with your own loss vocabulary — for example "awaiting QC", "no material", "tool change" or "power cut / DG switchover" — so the categories match how your team describes lost time. That's configuration, not custom code.
Often yes, because the biggest capacity gains for smaller plants come from small, frequent stops that nobody currently logs — waiting on material, changeovers, an ageing machine that trips. ERPNext lets you start with a single bottleneck machine, capture clean data there, and prove where the hours go before scaling. You reclaim capacity you already own rather than buying new equipment. Acube can help scope a right-sized rollout.
Get a clear plan, an honest timeline, and a fixed scope. Talk to a real expert today — whether or not you work with us.
Kochi (Kadavanthra & Infopark) · Thiruvananthapuram · across India & overseas · In business since 2011