Top Loss Diagnostic Workbook

Top Loss Diagnostic Workbook

Purpose: Rapidly identify the handful of loss types that, if reduced, will deliver the largest realistic improvement in OEE. This workbook captures loss events, maps them to a simple taxonomy, supports quick containment, and helps teams design short experiments with owners and measurable expected savings.

How to use this workbook

1. Capture losses in the Loss Capture sheet as they occur for a short discovery window (e.g., 1–2 weeks).
2. Map each captured loss to a loss taxonomy category (Availability / Performance / Quality) and a more specific cause code.
3. Aggregate by frequency, duration, and impact to find top losses by lost minutes/hours per period.
4. Run quick containment where safety or immediate customer impact exists.
5. Create a focused experiment for 3–8 highest-impact, tractable losses. Record hypothesis, test, measurement plan, owner, and timeline.
6. Measure results, update the Owner Tracker, and roll successful countermeasures into standard work.

Sheet: Loss Capture

Purpose: fast, low-friction logging of loss events. Keep entries short and factual. Capture a sample entry for context (shift, product, machine).

Sheet: Loss Taxonomy Mapping

Purpose: normalize free-text captures to consistent cause codes so aggregation identifies real top opportunities. Use one row per LossID.

Sheet: Aggregated Time-Series & Top Loss Summary

Purpose: convert events into ranked lost minutes/hours by loss category and cause. Example aggregation columns:

• Cause Code
• Total Events (period)
• Total Lost Minutes (period)
• Average Duration (mins)
• Estimated % OEE Impact (relative to planned production minutes)
• Tractability (High / Medium / Low)

Rank by Total Lost Minutes adjusted by Tractability to choose the few losses to address first.

Sheet: Containment Actions

Purpose: for safety or customer-impact losses, capture short-term containment so production can continue while root cause analysis and experiments are organized.

Sheet: Proposed Experiments

Purpose: convert hypotheses into short, measurable experiments. Keep experiments time‑boxed (1–4 weeks) and focused on a single changeable variable.

Sheet: Owner Tracker & Experiment Results

Purpose: maintain accountability and collect measured outcomes so successful countermeasures are standardized.

Sheet: Expected Savings Calculator

Purpose: estimate the likely impact of a successful countermeasure so teams can prioritize by expected value. Use conservative inputs and document assumptions.

Key inputs:

• Planned production minutes per period (e.g., shift/day/week)
• Average lost minutes per event
• Current events per period
• Estimated % reduction if experiment succeeds (conservative)
• Unit contribution per minute (if available) or approximate cost of lost capacity

Simple formula (per period):

Estimated Saved Minutes = Current Events × Avg Duration × Estimated % Reduction

Estimated Savings ($) = Estimated Saved Minutes × Unit Contribution per Minute

Worked example:

• Planned minutes / week = 20,160 (2 shifts × 8 hrs × 5 days × 60)
• Loss L-001: Avg duration = 33 mins; Current events = 3/week → Lost minutes = 99 /week
• Conservative reduction estimate = 70% → Saved minutes = 69.3 /week
• If unit contribution per minute = $5 (capacity value), Estimated Savings ≈ $346 /week

Notes: use shift‑level or line‑level contribution values if possible. If contribution-per-minute is unknown, use saved minutes and percent OEE improvement to argue prioritization instead of dollar figures.

Prioritization checklist

Use this short decision rubric to pick the top experiments:

• Impact: Does this loss represent one of the top three lost-minute sources?
• Tractability: Can a team reasonably test a countermeasure within 1–4 weeks without major capital expense?
• Safety/Quality Risk: Does delaying action create unacceptable risk? If yes, contain immediately.
• Confidence: Do we have a plausible hypothesis linked to operator-observed causes?
• Scalability: If successful, can the countermeasure be applied to other lines or shifts?

Common mistakes and how to avoid them

• Chasing low-impact noise: aggregate before acting.
• Fixing symptoms only: pair containment with a testable root-hypothesis experiment.
• Measuring the wrong thing: pick a direct metric (trips/week, scrap rate, cycle time) not proxy vanity metrics.
• No owner: every experiment needs a single accountable owner and a deadline.
• One-off fixes: design to standardize and scale successful countermeasures into standard work / maintenance plans.

Next steps after a successful experiment

1. Document the change and update work instructions / maintenance procedures.
2. Train operators and maintenance on the new standard.
3. Schedule preventive tasks or design changes to remove the root cause permanently if needed.
4. Monitor the metric for a sustainment window (e.g., 8–12 weeks) to ensure the improvement holds.

Template files / copies

Suggested format: keep each sheet as a table so teams can copy the workbook into a spreadsheet or into an interactive form. If your site uses MES / historian data, consider linking aggregated event timestamps to automatically populate the Loss Capture sheet.

Image search phrase: oee loss diagnostic