Almost every OEE journey starts in Excel. It is free, familiar and good enough to prove the concept, and there is nothing wrong with that. If you want to calculate OEE in a spreadsheet, this guide shows you exactly how, the structure, the formulas and a worked example. It also covers the part most templates leave out: the point at which a spreadsheet quietly starts costing you more than it saves.
An Excel template is a great place to start measuring OEE — and a frustrating place to stay.
OEE is the product of three factors:
OEE = Availability × Performance × Quality
Availability = Run Time ÷ Planned Production Time (how much of the planned time the machine was actually running).
Performance = (Ideal Cycle Time × Total Count) ÷ Run Time (how fast it ran versus its ideal speed).
Quality = Good Count ÷ Total Count (how many units were good first time).
Inputs. Create cells for: planned production time, downtime (and therefore run time), ideal cycle time, total count and good count.
Availability. Run Time = Planned Time − Downtime; then Availability = Run Time / Planned Time.
Performance. Performance = (Ideal Cycle Time × Total Count) / Run Time.
Quality. Quality = Good Count / Total Count.
OEE. Multiply the three, and format as a percentage.
Planned time 480 min, downtime 60 min → Availability = 420/480 = 87.5%. Ideal cycle time 1.0 min/unit, total count 380 in 420 min → Performance = 380/420 = 90.5%. Good count 360 of 380 → Quality = 94.7%. OEE = 0.875 × 0.905 × 0.947 ≈ 75%.
Manual data entry is slow, late and error-prone, and operators resent it. Numbers entered after the shift are estimates, not facts.
No real time. A spreadsheet tells you yesterday's OEE; it cannot alert you to a problem happening now.
It does not scale across many machines, shifts or sites without becoming a fragile mess of tabs.
No root cause. A number without categorised downtime reasons tells you OEE is low, not why.
It becomes a silo. The data sits in a file, disconnected from maintenance and everything else, classic dark data.
The spreadsheet has done its job once you have proven OEE is worth tracking and you hit any of these: more than a machine or two, a need for real-time response, or frustration that the numbers arrive too late to act on. At that point automated capture pays for itself quickly. The wider trade-off is the same one in our guide to CMMS vs spreadsheets, and the capture options are covered in OEE data collection methods.
Fabrico captures availability, performance and quality automatically from the machines, in real time, with downtime reasons attached, so you get live OEE and the why behind it without anyone keying numbers into a sheet. It scales across machines, shifts and sites, and connects OEE to maintenance in one platform, everything the Excel template was quietly failing to do.
Yes. Using the formula OEE = Availability × Performance × Quality, you can build a simple template with inputs for planned time, downtime, ideal cycle time, total count and good count.
Manual entry, no real-time visibility, poor scaling, no root-cause detail, and isolation from other systems. It is great to start, frustrating to rely on long term.
When you have more than a machine or two, need real-time response, or find the manual numbers arrive too late to act on.
Outgrowing your OEE spreadsheet? See how Fabrico captures availability, performance and quality automatically, in real time. Book a demo today.
Login
Blog
