Production Loss Analysis is a structured review of where available production time, capacity, or good output is being lost.
The objective is to convert a broad performance gap into specific loss categories that can be measured, prioritized, and improved.
Start with the required output
Define:
- planned production time;
- required output;
- actual good output.
The gap between expected and actual performance should be understandable before detailed loss coding begins.
Capacity Planning helps define whether available production time is theoretically sufficient for demand.
Build a clear loss structure
Common production losses include:
- breakdown;
- setup and changeover;
- waiting for material;
- waiting for labor;
- reduced speed;
- minor stops;
- quality defects;
- rework;
- planned downtime.
The categories should be mutually understandable and consistently applied.
Connect to OEE where appropriate
OEE groups equipment loss into Availability, Performance, and Quality.
Production Loss Analysis can be broader.
It may include losses that OEE does not fully explain, such as:
- no schedule;
- material shortage;
- upstream starvation;
- downstream blockage;
- staffing gap.
The analysis should match the decision the team needs to make.
Quantify time and output loss
Losses may be expressed as:
- minutes;
- hours;
- units;
- percentage of planned time;
- percentage of lost output.
A common unit makes comparison easier.
For example, converting a speed loss into equivalent lost units may reveal its true impact relative to downtime.
Use Pareto thinking
Not every loss deserves equal attention.
Pareto Analysis helps identify the few categories that account for most of the capacity or output loss.
The team should then investigate those categories in more detail.
Separate symptom categories from causal analysis
“Breakdown” is a loss category.
It is not the root cause.
“Waiting for material” is also a loss category.
It does not explain why the material was unavailable.
Root Cause Analysis should be used after the loss has been prioritized.
Review losses at the constraint
Losses at the system constraint can have greater effect on throughput than the same amount of loss elsewhere.
Bottleneck Analysis helps identify the resource that currently limits system output.
Protecting capacity at that point can create disproportionate value.
Make data collection practical
Operators should not spend excessive time coding every minute.
Useful systems may combine:
- machine signals;
- simple reason codes;
- production logs;
- supervisor verification.
The coding system should balance detail with usability.
Too many categories create poor data.
Too few hide useful distinctions.
Verify improvement in the loss profile
After action, confirm whether:
- total loss decreased;
- targeted category decreased;
- another category increased;
- system output improved.
A local reduction in downtime may not matter if the process remains constrained somewhere else.
Common mistakes
Using loss categories that overlap, treating loss codes as root causes, measuring only downtime, ignoring speed and quality loss, collecting excessive detail, prioritizing losses away from the true constraint, and celebrating local improvement without checking system output are common mistakes.
Practical sequence
- define planned time and required output.
- define loss categories.
- collect loss data consistently.
- convert losses into comparable units.
- rank the largest losses.
- identify which losses affect the constraint.
- investigate causes.
- implement countermeasures.
- verify the loss profile changed.
- repeat as the constraint and loss pattern evolve.
The practical lesson
Production Loss Analysis turns missing output into visible categories.
Once the loss is visible and prioritized, the team can stop debating where capacity went and start improving the causes that matter most.
Related application
This topic also connects with Loss Tree. Use that method when the improvement requires the related operating or management discipline.