Blog · Board and management reporting · Manufacturing
Build OEE dashboards from exported production logs with availability, performance, and first-pass quality by shift. Use spreadsheet formulas, a worked example, and a time reconciliation to check the result.
OEE dashboards show how planned production time becomes first-pass good output, separating availability, performance, and quality losses by equipment and shift. Start with exported production logs, calculate each factor from its underlying rows, and keep a reconciliation in minutes beside the headline percentage. The method below uses one product with the same ideal cycle time across both shifts.
Use planned production time as the minutes when the equipment was scheduled to produce. Within that window, recorded stops reduce run time. Good units must pass the process the first time; units needing rework are quality losses for this calculation.
The Vorne OEE calculation guide defines the factors and the equivalent good-count formula:
Availability = Run time / Planned production time
Performance = Ideal cycle time × Total units / Run time
Quality = First-pass good units / Total units
OEE = Availability × Performance × Quality
Keep cycle time in minutes per unit when time columns contain minutes. Use the fastest achievable cycle time under ideal conditions for that product and equipment, rather than a planning allowance that already includes losses. The broader production dashboards guide covers output against scheduled targets, which is a separate comparison.
For an illustrative US component manufacturer, use these columns on a worksheet named Logs. The records cover October 21, 2026. The line produces the same component all day; inspection results are complete.
| Worksheet row | A: Date | B: Shift | C: Planned minutes | D: Stop minutes | E: Total units | F: First-pass good | G: Ideal minutes/unit |
|---|---|---|---|---|---|---|---|
| 2 | October 21, 2026 | Day | 450 | 60 | 720 | 684 | 0.5 |
| 3 | October 21, 2026 | Night | 450 | 90 | 630 | 600 | 0.5 |
Store dates as real spreadsheet dates. Preserve equipment and run identifiers in your full file even though the example covers one line. If stop events are in another export, total them to the run identifier before combining them with production counts.
Add H for run minutes, I for availability, J for performance, K for quality, and L for OEE. Enter these formulas in row 2 and fill down:
H2 = C2-D2
I2 = IF(C2=0,NA(),H2/C2)
J2 = IF(H2=0,NA(),G2*E2/H2)
K2 = IF(E2=0,NA(),F2/E2)
L2 = IF(C2=0,NA(),G2*F2/C2)
The label before each equals sign identifies the cell; enter the expression beginning with =. Keep a no-production period visible as a status requiring interpretation. A shift with planned time and no output has zero OEE under the direct formula, even when performance or quality cannot be calculated separately.
| Shift | Run minutes | Availability | Performance | Quality | OEE |
|---|---|---|---|---|---|
| Day | 450 − 60 = 390 | 86.7% | 92.3% | 95.0% | 76.0% |
| Night | 450 − 90 = 360 | 80.0% | 87.5% | 95.2% | 66.7% |
| Combined | 750 | 83.3% | 90.0% | 95.1% | 71.3% |
All percentages are rounded to one decimal place for display. Day performance is 0.5 × 720 / 390; day OEE is 0.5 × 684 / 450. Multiply unrounded factors if you use the three-factor route.
Combined planned time is 450 + 450 = 900 minutes. Stops total 60 + 90 = 150 minutes, total production is 720 + 630 = 1350 units, and first-pass good production is 684 + 600 = 1284 units. The combined calculations are:
Availability = SUM(H2:H3)/SUM(C2:C3)
Performance = SUMPRODUCT(G2:G3,E2:E3)/SUM(H2:H3)
Quality = SUM(F2:F3)/SUM(E2:E3)
OEE = SUMPRODUCT(G2:G3,F2:F3)/SUM(C2:C3)
The summary labels identify measures rather than cell names. These factor totals reconcile because the example has one shared ideal cycle time. For mixed cycle times, preserve each run's ideal production minutes and use time-weighted quality when reconciling the factors to the direct OEE formula.
For a selected date in B1 on a separate summary sheet, planned minutes can be filtered with:
=SUMIFS(Logs!C2:C3,Logs!A2:A3,B1)
Microsoft documents SUMIFS as summing values that meet criteria. Apply the same date and equipment filters to every numerator and denominator. Expand all ranges together when adding records. Covirage is not affiliated with Microsoft.
Convert the losses to the same time basis. Slow-running loss is run minutes minus ideal minutes for all units. Quality loss is the ideal minutes represented by units that failed first pass.
| Time component | Calculation from the combined rows | Minutes |
|---|---|---|
| Stop loss | 60 + 90 | 150 |
| Speed loss | 750 − 0.5 × 1350 | 75 |
| Quality loss | 0.5 × (1350 − 1284) | 33 |
| Fully productive time | 0.5 × 1284 | 642 |
| Check against planned time | 150 + 75 + 33 + 642 | 900 |
The direct check is 642 / 900 = 71.3%. Maintenance and operations can now inspect stop reasons first, while quality reviews the first-pass rejects. The counts still need to agree with the source records; the identity does not prove their accuracy.
Use the production dashboard template for a broader workbook layout and a quality assurance dashboard for defect and rework investigation. An operational dashboard places these findings in the wider operating review.
Upload a sample of your own production log with planned time, stops, counts, and ideal cycle times: Covirage maps the columns, and its tools compute and check the figures. The external AI model explains the losses with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your file.
See Covirage for industrial manufacturers for the manufacturing context.
For each comparable production run, collect planned production time, stop time, total units, first-pass good units, and the ideal cycle time for the product and equipment. Keep the shift, equipment, product, and run identifiers so you can check the source records and compare the same scope.
OEE quality uses units that pass the process the first time. A unit requiring rework is a first-pass quality loss even if it later becomes saleable. Keep its later disposition separately so the production and quality teams can reconcile accepted output without erasing the original loss.
A result above 100 percent signals a definition or data problem. Check whether ideal cycle time is too long, seconds and minutes were mixed, run time is missing, or counts were duplicated. Correct the cause instead of hiding the result by capping the percentage.
Recompute the result from the underlying production times and counts. With one ideal cycle time, divide summed good units times that cycle time by summed planned production minutes. Mixed products require run-level ideal times; a simple average of displayed percentages loses the relevant weights.