Calculator overview
Inputs and outputs
This summary comes from the calculator's published input and output contract.
Inputs
- Daily Production Data
-
Default 7 rows
About this input
One row per day, seven columns: the day label, shift minutes, planned stops, unplanned downtime, ideal cycle time in seconds per piece, total count and REJECTS. The last column is rejects, not good pieces: good count is derived as total minus rejects, so entering good pieces there inverts the quality factor. Planned production time is likewise derived, as shift minutes minus planned stops, rather than entered. Availability, performance and quality are aggregated over every row.
Column Range or allowed values Day Not declared Shift minutes 0 to 1440 Planned stops At least 0 Unplanned downtime At least 0 Ideal cycle sec At least 0 Total count At least 0 Rejects At least 0
Outputs
- Quality Loss
-
Unit minutes
About this output
The time spent producing pieces that were not good, in minutes, expressed as equivalent lost run time.
- Run Time
-
Unit minutes
About this output
The time the equipment was actually running, in minutes: planned production time minus unplanned downtime.
- Planned Production Time
-
Unit minutes
About this output
The time the equipment was scheduled to run over the period, in minutes, after planned stops such as no orders are removed. It is the base OEE measures against.
- Quality
-
Unit %
About this output
The share of pieces that were good, in percent: good count divided by total count. It captures defect and rework losses.
- Speed Loss
-
Unit minutes
About this output
The time lost to running slower than the ideal rate, in minutes, expressed as equivalent lost run time.
- Units Lost To Downtime
-
Unit units
About this output
The good pieces that could have been made in the downtime, in units, valued at the ideal rate.
- Units Lost To Speed Loss
-
Unit units
About this output
The good pieces forgone by running below the ideal rate, in units.
- Total Count
-
Unit units
About this output
All pieces produced over the period, in units, good and bad together.
- Total Effective Equipment Performance
-
Unit %
About this output
Total effective equipment performance: fully productive time against the full 10,080-minute seven-day week, the calendar this template models (Data!C6). For a period other than a whole week, read OEE and the loss breakdown instead; TEEP's denominator does not follow the number of rows you fill.
- Performance Uncapped
-
Unit %
About this output
The raw performance figure before it is capped at 100 percent, in percent. A value above 100 signals a cycle time or count error to investigate.
- Downtime Loss
-
Unit minutes
About this output
The production time lost to unplanned stops, in minutes: planned production time minus run time.
- Fully Productive Time
-
Unit minutes
About this output
The time that produced only good pieces at the ideal rate, in minutes. It is planned production time times OEE.
- Availability
-
Unit %
About this output
The share of planned time the equipment was running, in percent: run time divided by planned production time. It captures downtime losses.
- Calendar Utilisation
-
Unit %
About this output
The share of all calendar time that was scheduled as planned production time, in percent.
- Gap To The World Class Benchmark
-
Unit points
About this output
How far the OEE sits below the commonly cited world-class level of 85 percent, in percentage points. A positive gap is room to improve.
- Overall Equipment Effectiveness
-
Unit %
About this output
The single figure for equipment effectiveness, in percent: availability times performance times quality. It is the product of the three, so a low factor drags the whole result down.
- Performance
-
Unit %
About this output
How close the running speed was to the ideal rate, in percent: actual output against what the run time could have produced at the ideal cycle time. It captures speed losses and is capped at 100 percent.
- Good Count
-
Unit units
About this output
The pieces that passed first time, in units, excluding rejects and rework.
- Model Status
-
No unit declared
About this output
The overall check on your entries, shown above the results. It reads OK when the inputs are usable, NOT VALID with a reason when an entry makes the model meaningless, or CHECK with a reason when a result is valid but worth a second look. Read it before you trust the numbers below.
What it is
The OEE Calculator computes Overall Equipment Effectiveness from a week of production data. You enter one row per day, and it returns availability, performance and quality, their product as OEE, and the losses behind them expressed both in minutes and in units of lost output.
It also reports Total Effective Equipment Performance, which measures the same fully productive time against the whole calendar rather than against scheduled time.
Read the input grid carefully before entering anything. The last column is rejects, not good pieces. Good count is derived by subtracting rejects from the total count. Entering good pieces there will produce a quality figure that is wrong by a very large margin.
Methodology
Purpose and model boundary
This model calculates overall equipment effectiveness (OEE) from up to seven production-day rows. It separates planned production time into availability, speed, quality, and fully productive time; reports the aggregate OEE and total effective equipment performance (TEEP); and charts daily availability, performance, quality, and OEE.
It is a descriptive loss model. It does not diagnose root cause, establish the correct ideal cycle time, collect machine data, or define whether a stop is planned or unplanned for a particular operation.
Inputs and units
Each row in Daily_Production_Data contains:
| Column | Meaning and unit |
|---|---|
| Day | Editable row label. |
Shift minutes, S_i |
Total scheduled shift length, 0 through 1,440 minutes. |
Planned stops, PStop_i |
Minutes intentionally excluded from planned production. |
Unplanned downtime, D_i |
Minutes lost during planned production time. |
Ideal cycle, c_i |
Seconds per piece at the ideal rate. |
Total count, T_i |
All pieces produced. |
Rejects, R_i |
Rejected pieces, not good pieces. |
Blank rows are allowed. The grid has a fixed seven-row capacity, and calculations aggregate every populated or zero row.
Governing relationships
For each row, the workbook calculates:
Planned production time_i = max(0, S_i - PStop_i)
Run time_i = max(0, Planned production time_i - D_i)
Ideal production time_i = T_i × c_i / 60
Good count_i = max(0, T_i - R_i)
Aggregate values are the sums across all seven rows. Using aggregate planned production P, run time Run, ideal production time Ideal, total count Total, and good count Good:
Availability = Run / P
Performance_uncapped = Ideal / Run
Performance = min(1, Performance_uncapped)
Quality = Good / Total
OEE = Availability × Performance × Quality
The workbook expresses the aggregate losses as:
- downtime loss:
P - Run; - speed loss:
max(0, Run - Ideal); - quality loss:
Ideal × (Total - Good) / Total; - fully productive time:
P - downtime loss - speed loss - quality loss.
TEEP uses the fixed full-week basis stored in the workbook:
TEEP = fully productive time / 10,080 minutes
Calendar utilisation = P / 10,080 minutes
The benchmark gap is 0.85 - OEE. Estimated units lost to downtime and speed use the aggregate actual production rate (Total / Run) multiplied by the corresponding loss minutes.
Calculation sequence
- Validate each row's stop, downtime, and reject relationships.
- Convert each row to planned time, run time, ideal production time, and good count.
- Sum those quantities before calculating the aggregate factors. This produces weighted aggregate results rather than a simple average of daily percentages.
- Cap performance at 100% for OEE while preserving the uncapped value as a diagnostic output.
- Reconcile downtime, speed, quality, and fully productive minutes to planned production time.
- Calculate OEE, TEEP, calendar utilisation, benchmark gap, and lost-unit estimates.
- Evaluate
Model_Statusin the precedence below.
Outputs and interpretation
Overall_Equipment_Effectiveness is the primary product of availability, capped performance, and quality. A low factor pulls down the entire product. Performance_Uncapped is retained so data that imply performance above 100% are visible rather than silently hidden. TEEP has a different denominator from OEE and is meaningful only against the workbook's fixed seven-day, 168-hour calendar basis.
Validation and status logic
| Condition | Returned status |
|---|---|
| Any row has planned stops greater than shift minutes, unplanned downtime greater than shift minutes minus planned stops, or rejects greater than total count | NOT VALID: a production row is internally impossible (stops, downtime or rejects exceed their limits) |
| Aggregate planned production time is less than or equal to zero | NOT VALID: planned production time is zero |
| Aggregate total count is less than or equal to zero | NOT VALID: total count is zero |
| Uncapped performance is greater than 1.0001 | CHECK: performance exceeds 100%, so the ideal cycle time is too slow; OEE uses the capped value |
| OEE is less than 40% | CHECK: OEE below 40% suggests a data problem or a major loss |
| None of the preceding conditions applies | OK |
An impossible row takes precedence over aggregate zero checks. The performance warning takes precedence over the low-OEE warning.
Assumptions and limitations
- Planned and unplanned stop classifications, counts, rejects, and ideal cycle times must be supplied consistently; the workbook cannot verify their source.
- Performance above 100% usually indicates an incorrect ideal cycle or count basis. The cap prevents that value from inflating OEE but does not correct the input.
- Aggregation is weighted through summed time and count quantities, not an unweighted average of the daily chart values.
- TEEP and calendar utilisation always use 10,080 minutes. If the grid represents less than a full week, use OEE and the loss breakdown rather than interpreting TEEP as a period-normalized figure.
- Multiple products, changing ideal rates, planned shutdown policy, rework, micro-stops, and changeovers must be represented deliberately in the supplied rows; the model does not create a product-mix standard.
- The 85% world-class figure is a comparison constant, not a universal operational target.
Restrictions and non-computing states
The grid has seven fixed data rows and cannot be extended on this page. Its numeric columns reject negative entries; shift minutes are additionally constrained to 0 through 1,440. The workbook rejects a row when planned stops exceed shift minutes, unplanned downtime exceeds the remaining planned-production time, or rejects exceed total count. It also refuses an aggregate with zero planned-production time or zero total count. Blank and zero rows may remain in the grid and contribute zero to the sums.
Errors and warnings
Grid shape or cell-bound violations can be rejected by the page before the calculation runs. Workbook NOT VALID indicates internally impossible production data or an empty aggregate basis. Workbook CHECK preserves the calculated metrics while flagging a cycle-time inconsistency or very low OEE. A connection failure is not an equipment-performance finding.
References
The workbook states its own method rather than citing sources for it. Overall Equipment Effectiveness is a widely used industry measure, and the sources below describe the definition the workbook implements.
- Nakajima, Seiichi. Introduction to TPM: Total Productive Maintenance. Productivity Press, 1988. (the origin of Overall Equipment Effectiveness and the six big losses)
- Wikipedia. Overall equipment effectiveness. https://en.wikipedia.org/wiki/Overall_equipment_effectiveness
- Wikipedia. Total productive maintenance. https://en.wikipedia.org/wiki/Total_productive_maintenance
The 85 percent world class benchmark used on this page is a commonly quoted figure for discrete manufacturing rather than a published standard, and the workbook treats it as an editable constant.
Additional source notes migrated from Methodology
The model uses the standard OEE relationship Availability × Performance × Quality and the common TEEP calendar-time extension. The delivered reviewer packet cites OEE.com's calculation guide and its canonical single-shift example for independent arithmetic comparison.
Frequently asked questions
The last grid column is rejects, not good pieces. What happens if I get that wrong?
Why is my OEE so much lower than each of the three factors?
My performance came out above 100 percent. Is the machine beating its rated speed?
Should planned maintenance count as downtime?
Why are calendar utilisation and TEEP so low?
Is 85 percent a target I should be aiming at?
Found a problem, or have an idea?
Tell us if a result looks wrong, a label is unclear, or something is missing. We read every message.
LogicCommons is in beta. If a result, label, or reference looks wrong, tell us here; we read every message.