Back to the blog
Scenario Traceability Production

7:45 a.m., a customer reports a defect on a lot. Where do you start?

A customer reports a defect on a delivered lot: two hours of binders for an approximate answer, or seven minutes when the batch record is written during manufacturing.

2 min read

7:45 a.m. A customer reports a defect on a lot delivered last week. They expect an answer within the day.

Before calling the customer back

To give a serious answer, the production manager has to establish three facts:

  • Which components was this lot made with? Materials, supplier lots, intermediate production runs.
  • Which inspections were performed, by whom, and with what result? Verification, quality control, release.
  • Are other lots affected? In stock, in progress, already shipped.

Into the filing cabinet

  • 07:45 — Customer calls, defect reported
  • 07:55 — Search for the right production binder
  • 08:20 — Three sheets bear the same lot number
  • 08:50 — Three operators, three ways of filling them in
  • 09:20 — Components cross-checked by hand, one empty box
  • 09:45 — An answer, an approximate one

Two hours for a "probably". And lot 2611-B, made with the same component, was missed.

Nobody did a bad job. The record was simply filled in after the fact, and that is where information gets lost.

The same call, with Arianis

  • 07:45 — Customer calls, defect reported
  • 07:46 — Search for lot 2609-A
  • 07:47 — Components and supplier lots displayed
  • 07:48 — Verification, inspection, release: who, when
  • 07:50 — The same component found in lot 2611-B
  • 07:52 — The customer is called back, lot 2611-B set aside

Seven minutes, and an exact, confident answer.

The record is written during manufacturing

In Arianis, operators do not fill in a sheet after the fact: they record the production run as they carry it out.

  • Every component consumed, with its lot number
  • Every verification and every inspection, in the name of the person who performed it
  • No production run closed with missing information or an uninspected component

Omissions show up at the workstation, not in an audit six months later.

The answer, in two clicks

A first search on the delivered lot, LOT-2609-A, shows its production run, verified, and its components, including the component in question, CMP-2208.

Arianis Traceability module: searching for lot LOT-2609-A expands its production run PRD-000412, verified, and its components, including the component in question, CMP-2208

A second search on that component lists every lot that consumed it: LOT-2609-A, already shipped, and LOT-2611-B, still in stock.

Arianis Traceability module: searching for component CMP-2208, Stock tab, finds LOT-2609-A shipped and LOT-2611-B still in stock

One search on the lot, one on the component: the 7:45 call has its answer.

And how long would it take you?

Think about your last customer complaint. Would you have traced it in a few minutes, without the slightest doubt?

If you are not sure, let's replay this scenario together, in Arianis: cerebellis.com/en/arianis.

Doubt costs you time. Arianis gives it back.

See the original post on LinkedIn (in French)
Contact

A business need to scope, a project to integrate?