Checklist

OEE Measurement & Data Validation Checklist

An interactive, repeatable checklist teams can use to validate OEE data, capture discrepancies, assign owners, and track weekly data-governance actions so OEE becomes trusted and actionable.

Interactive Tool

OEE Measurement & Data Validation Checklist

Use this checklist when launching or auditing an OEE dashboard. Answer each item, record evidence or discrepancies, and assign owners so data problems are found and fixed quickly. Save a copy for each equipment-area and review it in your weekly validation huddle.

Identify the exact equipment IDs, line names, or cell boundaries this checklist covers.
Optional: add location context for reporting or aggregation.
Select all shifts that operate this equipment.
Optional details about split shifts, partial coverage, or special schedules.
Confirm that PLC/SCADA tags, MES events, and dashboard timestamps match expected timezones and clock sync.
Record specific mismatches, sample timestamps, and proposed fixes.
Ensure teams share the same definition of 'running', 'planned stops', and the ideal cycle time per SKU/operation.
Enter the ideal cycle time (in seconds per part or specify units in the notes).
Include SKU-specific values, changeover considerations, or mode-dependent cycles.
Check how planned stops, micro-stops, and unplanned stops are classified in the OEE calculation.
List missing rules, ambiguous events, or mapping problems between event codes and dashboard categories.
Confirm the formula used (e.g., Produced Count / (Planned Run Time / Ideal Cycle Time)).
Note any thresholds used to flag speed loss (e.g., <90% of ideal) and where they are configured.
Ensure rejects, rework, and scrap sources are correctly attributed to process steps or defect codes in the data.
Include examples where rejects were not captured or were misattributed between lines or SKUs.
A one-week spot-check compares dashboard OEE against manual observations or independent logs for a representative week.
Use YYYY-MM-DD to record the dates used for the spot-check.
Record notable mismatches, percent differences, and suspected causes.
Owners should include an operations lead and an engineer or data steward responsible for fixes.
Name, role, and preferred contact method (email/phone).
A standing short review to surface new data issues and verify fixes.
Choose the cadence for data validation meetings.
Rate how much teams can rely on the current OEE figures for decision-making.
1.0 10.0
List practical next steps (e.g., sync clocks, correct tag mapping, update event code table) with owner and target date.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
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.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.