SystemManufacturing Intelligence

Recurring Loss Analysis

Loss analysis in manufacturing that reads two years of deviations, shift notes, line stops and reject counts as one history, and threads together the events that share a cause.

Follow one repeat from four systems to its owner ↓
Watch with transcript →
The problem

One failure came back for nineteen months under six names, owned by nobody

A packaging line loses an hour to a web break. A shift note says a splice went through unseen. The camera rejects a burst of lids, and a vacuum leak test fails. Each lands in its own system: the stop gets a reason code, the note is read once at handover, the burst is put down to misregister, and the deviation closes as operator splice handling, retrained.

Nobody sees that all of them trace to one supplier's reels, so the loss is never counted once, priced or given an owner. The rule on investigating discrepancies reaches other batches the same failure may have touched, and deviations closed one at a time never get there.

Built forOperational excellence leadsPackaging line managersQA deviation specialistsSupplier quality specialists

The Problem Today

One failure keeps coming back, written a different way in four systems, so nobody counts it once or owns it.

164
FDA citations of the investigations rule in FY2025 published

Four systems that never meet

  • Deviations
  • Shift notes
  • Stop codes
  • Rejects
  • One cause, split across codesA downtime chart splits a repeat written many ways
  • Closed as retrainingEach deviation closes alone, and the cause stays on the line

The Solution

  1. Two years read at onceDeviations, shift notes, line stops and reject counts, read only
  2. One cause, however writtenEvents joined by meaning and material, each kept in its own words
  3. A challenger attacks itEvents with another cause split off, the agents' own sums rechecked
  4. One owner, then every line watchedAn owner and a due date, and each line watched for the cause

Built-in controls

  • Read only on every source system
  • Each ruling signed by two different people
  • An owned loss is frozen; a reopen clears both signatures

What You Get

Plants move from closing each deviation alone to owning the repeats behind them, priced and checked for effect.

  • Caught on the next lineA watched pattern finds the same cause before it is a deviation
  • Repeats an auditor can followEach one linked, challenged, owned and countersigned
  • A line's history, keptNew managers read two years of a line; rulings stay when people leave
Features

Loss analysis in manufacturing features, along one recurring failure

Operational excellence, line managers, QA and supplier quality follow one foil failure on a blister line, from the first read of the records to the owner's actions.

demoEvery plant, supplier, person, record and cost shown is sample data.

  1. 01The loom

    Recurring deviation and line stop history read across four record streams

    • Four systems on one timeline. Deviations from the QMS, shift notes from the e-logbook, stops from the MES and reject counts sit side by side for the first time.
    • Threads through events that share a cause. A web break in the downtime log and a splice not seen in a shift note join one thread, each kept in the words its crew wrote.
    • Threads ranked by cost or recurrence. The weekly loss review starts with the repeat that takes the most from the line instead of the loudest event of the week.
  2. 02Record behind a mark

    Each mark opens its source record, with the material in use at that minute

    • The passage the agents used, highlighted. A QA specialist reads the operator's own sentence instead of a summary, and judges the join from the source.
    • Material consumption beside the note. The reel in use at the event's minute comes from the MES record, so a shared material is shown from the record.
  3. 03The challenge

    Root cause challenged as an inspector, a supplier and plant finance would

    • Events that do not fit, split off. Events that ran on another supplier's reels at a low seal setting become their own thread, so one cause is not padded with another.
    • The agents' own arithmetic rechecked. A reject burst counted again inside a deviation's destroyed packs is caught before anyone prices or signs the loss.
    • Questions only people can answer, sent by name. Reopening a deviation, product impact and a supplier change assessment go to the QA specialist, the QA head and supplier quality.
  4. 04Thread and price

    Recurring loss accepted with its members and its price, line by line

    • Members grouped by their own wording. Each record sits under the words its source used, so the countersigner can open any one of them in a click.
    • A price built from the signed cost basis. Stop hours, scrapped packs, deviation handling and restart checks are each a line of the sum, with no lost margin added.
    • Acceptance with its reason and signature meaning. The excellence lead's signature states what it means, and the thread waits for QA before anyone owns it.
  5. 05QA countersign

    QA countersign only after each sampled deviation and record is opened

    • Every deviation plus members drawn by rule. The countersigner cannot pick the strongest evidence: members are drawn at random, and more can be drawn but not chosen.
    • A record counts once it has been read. Signing stays locked until each sampled record has been open for three seconds, so a countersign means the records were seen.
    • Routed to each plant's QA. The person who accepted a thread cannot give its second signature, and each thread waits for QA at its own plant.
  6. 06Questions for QA

    Product impact of a recurring failure decided by the QA head, by name

    • Product impact sent as a question, with no verdict. Agents state which reels and batches the cause could reach; whether product is affected stays with the QA head who dispositions it.
    • A tightening decision takes effect at once. A deviation raised and a batch held apply as soon as the QA head signs; a decision that loosens waits for a second QA signature.
  7. 07Owner's package

    Supplier corrective action request in fixed fields, open until verified

    • The supplier request drafted in fixed fields. The supplier answers through the supplier portal in fields the case can use, and free text changes nothing until a named person opens it.
    • Corrective action open until it works on the line. The supplier's fix closes only when a tagged splice trips the line's sensor and a second person signs the verification.
    • The client-notice question put to QA. Whether a supplier change needed the client told under the quality agreement goes to the QA head as a question.
  8. 08Owned losses

    Owned recurring losses register across plants, each frozen with an owner

    • Members and price frozen at the countersign. Later runs cannot change an accepted loss, so a client or inspector sees the count QA countersigned.
    • Status from open actions to effectiveness check. Plant heads see which losses wait on a supplier, which are overdue and which are already proving their fix.
  9. 09Watched pattern

    The same cause found on a second line before it becomes a deviation

    • Each accepted loss becomes a watched pattern. Agents look for its signature on every line that runs the same material, leaving the frozen loss as signed.
    • New hits proposed to a person as a thread. The excellence lead rules on the second line's events, so a fix made once reaches each line that shares the cause.

The line manager steers; whoever accepts a thread cannot countersign it

Operational excellence rules on threads, the line steers the agents, QA countersigns and supplier quality owns the fix.

Operational excellence leads

Run the weekly loss review and accept, rename or reject each thread

  • Repeats ranked by cost or recurrence
  • Each thread attacked before the ruling
  • Rulings that become rules after a QA signature
Packaging line managers

Run the lines, steer the agents to them and own line actions

  • Two years of a line's history on one screen
  • Crews' shift notes read again, not filed
  • Steering in plain words, logged
QA deviation specialists

Investigate deviations and countersign thread membership after opening the records

  • Members drawn by rule, never hand-picked
  • Reopen questions sent to them by name
  • Signature meanings kept on record
Supplier quality specialists

Own supplier actions, corrective action requests and change notices

  • Supplier requests answered in fixed fields
  • Corrective actions open until verified on the line
  • Change notices tied to the failures that followed
More screens

The agents, the cost basis, learned rules, the trail and who may change what

Behind each ruling: what the agents did and how sure they were, the rates every thread is priced with, and the rules they learned.

Agents at work, steered in plain wordsSix agent roles side by side, each with its steps, sources, finding and confidence; a line manager can steer them in plain words.
Rates per line, signed by plant financeLine hour, unit cost and restart scrap for every line, proposed by operational excellence and signed by plant finance; owned losses keep the price they were frozen at.
Watched patterns and rules learned from rulingsA rejected thread teaches a rule, such as never joining events by shift alone; it applies only after the excellence lead and then QA have signed it.
People and agents in one audit trailWho did what and when, the reason, what each signature means and the session, downloadable as a CSV or as one loss's evidence file.
Systems read, and duties kept apartEvery source system is read only, the supplier portal reads and sends requests, and a settings change proposed by one person is signed by another.

demoSample data, from the working solution.

Nine agents read, join, price and attack, and none of them names a loss

Each hands its result to the next by name, and every ruling goes to a person.

Stream readers

Four readers, one each for deviations, shift notes, the downtime log and reject counters, mark events that read as a loss and keep the source's own words.

  • Edit no source record
  • Guess no reel lot the MES does not record
Clusterer

Joins marks by meaning and by shared facts, such as the material in use, the equipment and the setting, and proposes threads with a confidence.

  • Joins nothing by shift alone once that rule is signed
  • Names no loss and closes no record
Pricer

Prices each thread with the basis plant finance signed, showing each line of the sum.

  • Uses no unsigned basis
  • Prices no lost margin
  • Rounds nothing before the total
Challenger

Argues each thread as the inspector, the supplier, the client's auditor and plant finance would, and rechecks the agents' own sums.

  • Accepts or rejects no thread
  • Reopens no deviation
  • Sends what it cannot answer to a named person
Watcher

After a loss is owned, watches each line for its signature and keeps the counts on frozen members honest.

  • Adds no event to a frozen loss
  • Proposes new hits to the excellence lead as a thread
Hand-off drafter

Drafts the owner's package: the actions, the structured supplier request and the client-notice question.

  • Sends nothing outside without the owner's click
  • Decides no client notification

The excellence lead rules on each thread; the QA head rules on product

Whether events are one recurring lossThe operational excellence lead rules on each thread with a reason code; QA countersigns once the records are open.
Whether product is affectedThe QA head decides product impact and any hold; the agents name the reels and batches the cause could reach and stop there.
Whether a closed deviation is reopenedThe QA deviation specialist decides whether to reopen a closure and extend it to other batches made with the same material.
Whether a client must be toldQA and supplier quality decide notification under the quality agreement; the drafter only puts the question to them.
What an hour of the line is worthPlant finance signs the cost basis that the excellence lead proposes, and no agent sets a rate of its own.

Questions on loss analysis in manufacturing from plant teams

What is loss analysis in manufacturing?

Loss analysis in manufacturing finds where a plant loses output, material and line time, and why. This solution looks for the losses that return: agents read deviations, shift notes, line stops and reject counts together, thread the events that share a cause, and people accept, countersign and own each one.

How is a recurring loss different from a recurring deviation?

A recurring deviation repeats inside the quality system. A recurring loss may reach the QMS only now and then and live mostly as stop codes, shift notes and reject bursts. Reading all four streams finds a cause that a deviation trend analysis alone would miss.

Does it change anything in the QMS, MES or e-logbook?

No. Each source system is read only, and no agent edits a deviation, a stop code or a shift note. An accepted loss is frozen in the solution's own record, with each step in the audit trail.

Where does the price of a recurring loss come from?

From a cost basis the operational excellence lead proposes and plant finance signs: line hour, unit cost, deviation handling, restart checks and restart scrap. Each line of the sum is shown, and no lost margin is added.

What happens when the same cause turns up on another line?

The watched pattern proposes the new events as a thread for the excellence lead's ruling. The loss already owned stays as signed, and the fix worked out for the first line becomes the starting point for the second.

What are chronic losses?

Chronic losses return on a line again and again, each too small in a single record to call for an investigation of its own. Here they surface as threads across deviations, shift notes, line stops and reject counts, each priced, then frozen with a named owner once QA countersigns.

Bring a failure that
keeps coming back.

Send a year of one line's deviations, stop log, shift notes and reject counts, and we will draw its threads and price the first one.