OEE Quick Diagnosis Workbook

Interactive workbook to measure OEE reliably, map top losses by category, run prioritized experiments, and capture sustainment handovers. Collects run data, guides correct OEE calculations, records loss-detail entries, tracks up to three rapid experiments, and stores a short sustainment checklist and handover notes.

Interactive Tool

OEE Quick Diagnosis Workbook

Welcome

This workbook helps teams capture reliable OEE inputs, map the top availability/performance/quality losses, run prioritized experiments, and record sustainment handover steps. Use this interactive form during a short improvement huddle or while validating data on the shop floor.

Quick example (filled)

Run: Line 2, Day shift. Planned production time = 480 min. Downtime = 60 min → Availability = (480-60)/480 = 0.875 (87.5%). Total pieces = 9,600, Ideal cycle = 3 sec = 0.05 min → Performance = (0.05*9,600)/(420) = 1.14 → capped at 1.0 (100%). Good pieces = 9,360 → Quality = 9,360/9,600 = 0.975 (97.5%). OEE ≈ 0.875 * 1.00 * 0.975 = 0.85 (85%).

This form stores your entries so you can compare before/after runs, prioritize losses, and track experiments. If you want automatic calculations and dashboards later, see the CapabilityEnhancementNotes below.

Give this entry a short name you will recognize later, e.g. 'Line2_2026-08-01_Day'.
Which production line, cell or machine is this run on?
Select the shift for this entry.
Name of the operator or CI owner for follow-up.
Total scheduled production time for the period being measured (minutes).
Minutes the line was stopped for any reason during the planned production time.
Run Time = Planned production time - Downtime. Enter value or leave blank to compute externally.
All parts produced (including scrap and rework).
Parts that meet quality criteria without rework.
The theoretical fastest consistent cycle time for this product/line (seconds).
Formula: Availability = Run Time / Planned Production Time. Enter as percentage (0–100). If you calculated it elsewhere, paste the value. Example: 87.5
Formula: Performance = (Ideal Cycle Time * Total Pieces) / Run Time (in same time units). Convert to percentage (cap at 100%). Enter as percent (0–100).
Formula: Quality = Good Pieces / Total Pieces. Enter as percent (0–100).
OEE = Availability * Performance * Quality (as decimals). Enter OEE as percent (0–100).
Categorize losses as Availability (stops and speed losses that cause downtime), Performance (reduced speed, micro-stops), or Quality (scrap, rework). Record minutes lost and a short description. Prioritize by total minutes and root cause potential.
Describe the loss (e.g. 'Changeover delay', 'Sensor fault causing stop', 'Product jam').
Which OEE component does this loss primarily affect?
Total minutes lost to this cause in the measured period.
How many times the loss occurred in the period.
Use this to capture your team's initial priority. See scoring rubric below.
1.0 10.0
1.0 10.0
1.0 10.0
List the top three losses you will address and why these were prioritized.
Priority scale guidance: 5 = >60 minutes or safety/stop risk or high customer impact; 4 = 30–60 minutes or likely repeat; 3 = 10–30 minutes; 2 = <10 min and low repeat; 1 = negligible. Combine minutes, frequency and ease-of-fix when prioritizing.
Clear hypothesis: what you will change and expected measurable outcome (e.g. 'Reducing changeover checklist items will save 10 minutes per changeover').
What you will measure (minutes saved, scrap%, uptime), and the baseline value.
Select yes if the experiment result should become standard work and be handed over.
Check items required to sustain a change.
Include who will own the new standard, where documentation is stored, and who to contact if problems recur.
Capture any other immediate actions, risks, or requests for support.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.

Discussion

Comments and conversation will live here.