# OEE Rollout Readiness Checklist > Source: https://netray.co/tools/oee-rollout-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist covering definitions, data capture, people and routines to complete before and during an OEE rollout. ## Category mes-shop-floor ## Industry Discrete Manufacturing ## Audience - Plant manager - Continuous improvement manager - Operations manager ## Tool **Kind:** checklist **Groups:** #### Definitions and scope **Items:** **Text:** Pilot lines or machines chosen, with a clear reason for each **Critical:** true **Text:** Planned production time rules written down **Critical:** true **Text:** Ideal cycle time source agreed for each product **Critical:** true Minimum stop length for logging agreed Rework treated as not good in first pass quality Changeovers classed as downtime and recorded One-page definitions sheet approved by operations and quality #### Data capture **Items:** **Text:** Machine state captured automatically or by a defined manual process **Critical:** true **Text:** Total and good counts captured by shift or by job **Critical:** true Downtime reason code list built and trimmed for the pilot Clocks across machines and systems are synchronised Work order or part number linked to each run Scrap and rework reported against the same line and shift Data entry fallback defined for when sensors fail #### People and ownership **Items:** **Text:** Executive sponsor named **Critical:** true Owner named for each pilot line **Text:** Operators briefed on why the data is collected, and what it will not be used for **Critical:** true Supervisors trained on the reason codes Maintenance and quality included in the review meetings Union or works council informed where relevant Time set aside for operators to log stops #### Reporting and baseline **Items:** **Text:** Baseline period of at least four weeks recorded before targets are set **Critical:** true Daily line board or screen visible at the cell Weekly Pareto of downtime by reason produced Availability, performance and quality shown separately, not only OEE Weighted aggregation used across lines and periods Data quality check for OEE above 100 percent added Targets set by line, not copied from a benchmark #### Improvement routines **Items:** **Text:** Daily short stand-up held at the line **Critical:** true Top three losses assigned to named owners with dates Action tracker visible to the team SMED, autonomous maintenance or poka-yoke projects chosen from the Pareto Monthly review with plant leadership scheduled Gains verified in the data before the action is closed Plan to extend to further lines after the pilot review **Scoring Note:** Aim to tick every critical item before go-live. Missing critical items are the usual reason pilots lose credibility with operators. ## Content **Intro:** Most OEE programs stall on definitions, data trust or lack of follow-through, not on maths. Use this checklist to close those gaps before the first dashboard goes on the wall. **Sections:** #### How to use the checklist **Body:** Work through the five groups with the plant manager, a maintenance lead, a quality lead and one operator from the pilot line. Tick what is done, note owners for what is not and re-run the checklist before go-live. Export it to PDF for the project file or to Excel for tracking. **Bullets:** - Do the critical items first - Keep the pilot to one or two lines - Review progress weekly #### Why these areas **Body:** Definitions make the number mean the same thing everywhere. Data capture decides whether the number can be trusted. People decide whether anyone acts on it. Reporting turns data into a visible baseline. Routines convert that baseline into improvement. A gap in any one of the five will cause the program to fade. #### Reading your result **Body:** If more than a few critical items are open, delay go-live and fix them, because early distrust of the numbers is very hard to undo. If critical items are done and others are open, go live and treat the open items as the first improvement tasks. #### Common mistakes **Body:** Common failures are starting with every line at once, setting targets from a benchmark before measuring a baseline, using OEE to rank operators, and building a dashboard before the reason codes are usable. Start small and show results first. **Cta:** If you want help linking OEE data to ERP orders and maintenance records, we can review your data flow before you scale. **Faq:** #### How long should the pilot run? **Answer:** Run it for at least four to eight weeks. That gives a stable baseline, enough stops to build a Pareto and time for operators to get used to the reason codes. Shorter pilots often reflect a single unusual week. #### Should we measure every machine? **Answer:** Start with the constraint or the machines with the largest cost of lost time. Measuring everything at once dilutes attention. Add lines as the routine proves it is working. #### Is automatic capture required? **Answer:** No. Manual capture with a good reason code list can start the process. Automatic state and count capture improves accuracy and removes burden, so plan it for the second phase. #### How do we avoid misuse of the number? **Answer:** State clearly that OEE measures equipment losses, not people. Use it to find and remove obstacles. Avoid league tables between operators, and share improvements and wins at the same pace as problems. ## Search terms oee implementation checklist, oee rollout plan, how to implement oee, oee readiness checklist, oee program checklist, start oee measurement --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json