Engineers Clinic
BeginnerEngineering trackFP-ME-08

OEE and downtime analysis on a six-machine CNC cell, with a kaizen plan

Turn four weeks of machine logs into OEE by machine and shift, find the biggest losses, and write a kaizen plan that lifts the cell from about 55% to 70% OEE.

Core EngineeringMechanical Engineering
6 Guided Steps32h Internship TierSubmit: Synthetic machine and quality log + OEE script with results by machine and shift + loss Pareto + root-cause sheets + kaizen plan with SMED study + short reportVerified CertificateAI Rubric Graded
Program Overview

Industry project · for Brenner Precision Components, a German machining supplier with plants in Schweinfurt and Spartanburg, South Carolina, making hydraulic valve bodies

Brenner's valve-body cell has six horizontal machining centres. Each part takes an ideal 4.2 minutes, and the cell runs two shifts of 7.5 hours, five days a week. A tractor maker has offered a contract for 18% more parts from next quarter. The plant manager would rather find the capacity in the existing cell than buy a seventh machine at €420,000.

Nobody knows the real OEE. The shift reports say the cell is "busy", but the monthly output suggests it is closer to 55%. The machines log state changes (running, idle, alarm, changeover, waiting for material, planned maintenance) and the quality station logs scrap and rework. Nobody has ever put the two together.

The Spartanburg plant runs an identical cell and wants to use whatever method you build.

Your job is to: - generate a realistic four-week machine and quality log from the distributions in task 1, since real plant data is confidential; - calculate availability, performance, quality and OEE per machine and per shift; - build a Pareto of losses using the six big losses; - run a root-cause analysis on the top two; - write a kaizen plan, including a changeover reduction study, with a target and an owner for every action.

You do not need a factory. The work is done in Python with pandas, or in a spreadsheet if you prefer. Done looks like an OEE calculation that one command re-runs on new data, a Pareto that the shift leaders agree with, root causes for the top two losses, and a kaizen plan showing how the cell reaches 70% OEE and whether that covers the 18% extra demand.

OEE calculationSix big lossesPareto analysisRoot-cause analysis (5 Whys, fishbone)SMED changeover reductionKaizen planningpandas data analysis
What you submit

Synthetic machine and quality log + OEE script with results by machine and shift + loss Pareto + root-cause sheets + kaizen plan with SMED study + short report

Stack: Python, pandas, Matplotlib, Spreadsheet (alternative), A3 or kaizen template

How it is graded
  • Correct OEE30

    Availability, performance and quality are calculated from the logs with the right time bases, per machine and per shift, and the cell OEE matches the factors.

  • Losses classified20

    Every lost minute is assigned to one of the six big losses and the Pareto adds up to total lost time.

  • Root causes20

    The top two losses have 5 Whys and a fishbone that reach a cause someone could act on.

  • Kaizen plan and capacity30

    Each action has a target, owner and date, the SMED study is quantified, and the plan shows whether 70% OEE covers the 18% extra demand.

Pass 60% · Merit 75% · Distinction 90%

Learning Outcomes
Calculate OEE correctly from machine logs
classify losses into the six big losses
find root causes with 5 Whys and a fishbone
plan a changeover reduction
link an OEE target to capacity
Target Audience

Engineering Students

Diploma, B.Tech, B.E., BCA, MCA, or M.Tech students seeking practical experience.

Aspiring Developers

Developers who want to build proof-of-work capstone projects for tech resumes.

Job Seekers

Graduates looking for AI-evaluated code review & verified industry credentials.