Excel Template To Your Track OEE, OOE And TEEP Daily
Baseline first, then scale
The math is simple: planned minutes minus unplanned downtime gives operating time; ideal cycle time and good parts translate that time into performance and quality. OOE and TEEP widen the lens to scheduled and calendar time, so you see both execution and capacity. With one sheet and a 7-day dashboard you get a credible baseline, a common language across crews, and a way to prove where the real losses sit. It is the shortest path from feelings to facts and a solid stepping stone to real-time monitoring when you are ready.
Turn minutes and counts into money
Downtime minutes, cycle seconds, and scrap counts are just numbers until you wire them together. This calculator does exactly that. OEE exposes losses during planned production, OOE adds the penalty of planned stops, and TEEP shows how much calendar capacity you are leaving on the table. One consistent structure across shifts unlocks trendlines by machine and product, so supervisors can address the right constraint and managers can quantify the cost of inaction. The result is a trusted baseline for budgeting, staffing, and capital planning, built with tools every plant already has.
A single source of truth for the shop floor
Spreadsheets often fail because they try to do too much. This one does just enough. Operators record a handful of fields per shift; formulas handle the rest and clamp bad math where it matters. The workbook rolls OEE, OOE, and TEEP into clean tiles and averages for the last week, making it easy to compare lines, crews, and SKUs. The point is discipline and repeatability: a lightweight log that creates a single source of truth your teams can rally around while you scope an IIoT rollout.
Separate execution from scheduling and capacity
Plants mix three problems by accident: how well we ran, how we scheduled, and how much of the calendar we used. This template splits them cleanly. OEE grades execution during planned production. OOE folds in planned stops like meetings, changeovers, and cleaning. TEEP answers the capacity question against 24x7. Backed by transparent formulas and a shift-level log, the three numbers remove guesswork from debates and make it obvious whether you need better setups, better staffing, or more hours on the constraint machine.
Fast feedback loop for CI
Continuous improvement dies when feedback is late. This Excel build makes it daily. Each shift feeds a small table; the dashboard highlights Availability, Performance, and Quality patterns, plus OOE and TEEP to expose scheduling and utilization. Because the math is visible, operators trust it. Because the view is consistent, managers stop arguing definitions and start fixing losses. You get a repeatable rhythm that connects shop-floor actions to measurable movement in a week, not after month-end
How to use the values to drive results
No definitions here - just decisions.
Download and start tracking
MDCplus team got your covered with a template, which you can take as a reliable start, and can be used further, improving and helping until you decide to move on with a digital system.
Already started, have some values which you can't relate or act upon? That is what the rest of the article tells you.
If OEE drops but OOE stays close to target
Problem is inside planned production time - Availability, Performance, or Quality.
Triage rule
- If Availability is the lowest of the three → run a downtime huddle. Kill the top 2 unplanned causes for the next 5 shifts.
- If Performance is lowest → run a 30 min SMED review on yesterday’s longest changeover and lock one externalization change.
- If Quality is lowest → do a first-piece checklist audit and one-point lesson on the top defect.
If both OEE and OOE are poor, TEEP is ok
Planned stops are the hidden tax.
- Trim meeting and cleaning time or move it off the line.
- Stage tools and materials externally.
- Lock a shorter break cadence if that is eating ScheduledHours.
If TEEP is far below OOE
You are under-scheduling the asset vs market demand.
- Add a weekend shift or extend runs on the constraint machine.
- If demand is seasonal, build a capacity plan so sales does not overpromise during peak weeks.
If TEEP, OOE look fine but OEE is volatile shift to shift
This is execution discipline
- Daily 10 minute standup around the Dashboard for yesterday.
- Assign one owner per loss bucket with a 1 week target and simple countermeasure.
Targets - keep it simple
-
Start with OEE 0.85, OOE 0.80, TEEP 0.55. They are in Dashboard as editable cells. Tune for your plant after 2 weeks of data.
Daily operating routine
-
Operators log a shift
- In ShiftLog, fill Date, Shift, Machine, CalendarHours, ScheduledHours, PlannedStopHours, UnplannedDowntimeMin, IdealCycleTimeSec, TotalCount, GoodCount.
- Columns K to T calculate automatically.
-
Supervisor review - 10 minutes max
- Open Dashboard. Look at the last 7 days OEE, OOE, TEEP.
- Check Availability vs Performance vs Quality averages. Whichever is lowest sets today’s focus.
- Pick one fix. Write it on the whiteboard. Done.
-
Weekly CI review
- Sort ShiftLog by Machine then Date.
- For the worst machine, scan Availability, Performance, Quality columns. Choose the bottleneck.
- Pull one example shift and fix the root cause with the team within 7 days.
About MDCplus
Our key features are real-time machine monitoring for swift issue resolution, power consumption tracking to promote sustainability, computerized maintenance management to reduce downtime, and vibration diagnostics for predictive maintenance. MDCplus's solutions are tailored for diverse industries, including aerospace, automotive, precision machining, and heavy industry. By delivering actionable insights and fostering seamless integration, we empower manufacturers to boost Overall Equipment Effectiveness (OEE), reduce operational costs, and achieve sustainable growth along with future planning.
Ready to increase your OEE, get clearer vision of your shop floor, and predict sustainably?
Other articles
OEE, OOE, and TEEP answer different parts of that problem. Pick the right metric when capacity is your constraint