# OEE Program Maturity Assessment > Source: https://netray.co/tools/oee-program-maturity-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions that score your OEE practice from ad hoc to embedded, with next steps for each band. ## Category mes-shop-floor ## Industry Discrete Manufacturing ## Audience - Plant manager - Continuous improvement manager - Operations director ## Tool **Kind:** assessment **Questions:** #### How is OEE defined in your plant? **Options:** ##### Each line or person uses their own method **Score:** 0 ##### A definition exists but is not always followed **Score:** 1 ##### One written definition is used by most lines **Score:** 2 ##### One definition is used by all sites and audited **Score:** 3 #### How is machine state and downtime captured? **Options:** ##### Not captured **Score:** 0 ##### Paper logs filled at end of shift **Score:** 1 ##### Operator entry on a screen at the time of the stop **Score:** 2 ##### Automatic state capture with operator reasons **Score:** 3 #### How are ideal cycle times set? **Options:** ##### We do not have them **Score:** 0 ##### Taken from the routing without checking **Score:** 1 ##### Verified for main products **Score:** 2 ##### Verified by product and reviewed on a schedule **Score:** 3 #### How good is your reason code discipline? **Options:** ##### Most stops are coded Other or not at all **Score:** 0 ##### Many are coded but quality is poor **Score:** 1 ##### Most stops are coded correctly **Score:** 2 ##### Codes are audited and the list is reviewed **Score:** 3 #### Who sees the OEE data? **Options:** ##### Nobody regularly **Score:** 0 ##### Managers in a monthly report **Score:** 1 ##### Supervisors daily **Score:** 2 ##### Operators at the line in near real time, and managers on dashboards **Score:** 3 #### How do you act on the data? **Options:** ##### We do not **Score:** 0 ##### Ad hoc when a problem is loud **Score:** 1 ##### Weekly review of top losses with owners **Score:** 2 ##### Daily routine plus structured projects, verified results **Score:** 3 #### How is OEE aggregated across lines and periods? **Options:** ##### We do not aggregate **Score:** 0 ##### Simple average of percentages **Score:** 1 ##### Weighted by time or volume in a spreadsheet **Score:** 2 ##### Weighted automatically in a governed model **Score:** 3 #### How is OEE linked to ERP data such as orders, scrap and costs? **Options:** ##### Not linked **Score:** 0 ##### Manual re-keying **Score:** 1 ##### Periodic file transfers **Score:** 2 ##### Automated link by work order **Score:** 3 #### How are targets set? **Options:** ##### No targets **Score:** 0 ##### One number for the whole plant **Score:** 1 ##### Set by line from a baseline **Score:** 2 ##### Set by line, tied to a loss reduction plan and costed **Score:** 3 #### How do operators and supervisors view the program? **Options:** ##### As a way to blame people **Score:** 0 ##### As extra paperwork **Score:** 1 ##### As useful for finding problems **Score:** 2 ##### As their own tool, with their ideas driving actions **Score:** 3 **Bands:** #### Ad hoc **Min:** 0 **Max:** 25 **Verdict:** OEE is not yet a dependable number. The first job is agreeing definitions and getting basic data. **Recommendations:** - Write a one-page OEE definition and get it signed off - Pilot on one constraint line with manual capture - Build a short reason code list #### Emerging **Min:** 26 **Max:** 50 **Verdict:** You collect some data but trust and follow-through are patchy. **Recommendations:** - Verify ideal cycle times for the main products - Move from paper to entry at the time of the stop - Start a weekly Pareto review with named owners #### Established **Min:** 51 **Max:** 75 **Verdict:** OEE is used regularly. The next gains are automation, better aggregation and tying results to cost. **Recommendations:** - Automate state and count capture - Move to weighted aggregation in a governed model - Link downtime and scrap to ERP work orders #### Embedded **Min:** 76 **Max:** 100 **Verdict:** OEE is part of daily management and drives improvement. Focus on sustaining gains and spreading practice. **Recommendations:** - Audit definitions and reason codes on a schedule - Share what works between sites - Use loss data to guide capital and maintenance planning ## Content **Intro:** Plants differ less in the OEE number than in how they use it. This ten question assessment scores your practice from ad hoc to embedded and gives a few concrete next steps. **Sections:** #### How to use the assessment **Body:** Answer as the plant is today, not as it should be. It works best if two or three people answer separately, such as a plant manager, a supervisor and a continuous improvement lead, then compare answers. Gaps in answers are a finding in their own right. **Bullets:** - Be honest, nobody sees the result - Compare answers across roles - Re-run every six months #### What is being measured **Body:** The questions cover five themes: definitions, data capture, reporting, action routines and links to ERP and cost. They reflect a simple idea that measurement only pays when the number is trusted, visible and acted on. The score is a guide, and not an audit or a certification. #### Reading your band **Body:** Low bands call for foundations: definitions, one pilot line and credible data. Middle bands call for automation and cadence. High bands call for sustaining gains and linking OEE to cost and capital decisions. Use the recommendations as a list to discuss with your leadership team. #### Common mistakes **Body:** Do not chase a higher band by buying software first. The usual blockers are definitions, reason code discipline and a weekly routine, none of which need new tools. Software helps once those are in place. **Cta:** If you want an outside view of how your OEE data flows from machines to ERP and reports, we can review it with you. **Faq:** #### Is this an official maturity model? **Answer:** No. It is a practical self check based on common patterns in plant performance programs. It is not a standard or a certification, and the bands are a guide to discussion. #### Who should answer? **Answer:** Ask the plant manager, a production supervisor and whoever owns continuous improvement or maintenance. Compare their answers, because differences often show where the program is not reaching the floor. #### What is a good score? **Answer:** There is no pass mark. A pilot plant may reasonably sit in Emerging. What matters is the direction and whether each step is paying back through reduced losses or improved delivery. #### How often should we repeat it? **Answer:** Every six months is enough. Track which answers change and why. If the score rises but losses do not fall, review whether actions are being closed with verified results. ## Search terms oee maturity assessment, oee program assessment, performance management maturity manufacturing, oee self assessment, continuous improvement maturity --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json