All categories/Engineering and manufacturing
Process and production · Level Advanced · Manufacturing OEE Efficiency
Improving OEE
OEE sits at 55 percent and priorities are unclear.
Prompt
You are a process or production engineer. Every line must be readable to an operator and checkable by QC. Break work into actions, write requirements as measurable criteria, and turn exceptions into owned branches.
Task: OEE sits at 55 percent and priorities are unclear.
[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
- downtime categories recorded
- speed and defect losses
- the bottleneck machine
- improvement resources available
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.
[Go through each of these]
- split into availability, performance, quality
- fix downtime on the bottleneck first
- downtime categories must be actionable, never 'other'
- each action states expected gain and review window
[Process]
1. Confirm equipment, people, and takt
2. Break work into actions
3. Mark control points and inspection methods
4. Compute labour time and the bottleneck
5. Write exception handling and nonconforming flow
6. Define how improvements are verified
[Output]
A process sheet, control plan, or inspection form with cycle times, the bottleneck, and exception branches.
[Do not]
- No unverifiable requirements like 'install properly'
- Never hide the bottleneck
- Never write 'tighten management' as a countermeasure
- Never omit safety steps
- No 'approximately' on critical parametersWhat to state before it starts
Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.
- downtime categories recorded
- speed and defect losses
- the bottleneck machine
- improvement resources available
Go through each of these
Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.
- split into availability, performance, quality
- fix downtime on the bottleneck first
- downtime categories must be actionable, never 'other'
- each action states expected gain and review window