Learn
Platform docs7
SPC & Process Control8
RCA & 8D11
Electrochemical10
DOE & Predictive8
Materials Development9
Integration8
Voice & Wearables2
RCA & 8D · 8D workflow

Interim containment

Screen out the bad parts now, before the cause is even known.

In short

Containment (8D discipline D3) stops bad parts reaching the customer before the cause is even known: stop the affected line, screen, quarantine, rework. It buys the investigation time; it fixes nothing, and forgetting that is how a two-week bridge becomes a permanent tax.

Interim containment8D workflow
Containment screening out the bad parts now, while the defect source is still live upstream. This stops escapes; it does not stop the defect.

What it measures

D3 sits between “we have a problem” and “we know the cause,” and it has its own engineering content:

  • Scope: every place suspect material can be: the line, WIP, finished goods, in transit, at the customer, and on sister lines running the same process. Containment scoped only to the line that complained is containment with holes.
  • Stopping the source: the line producing the defect stops, and only the lines verified clean keep running. Production continues on the healthy lines while the affected one stays down until the investigation clears it, so the plant is not manufacturing more containment work while it looks for the cause.
  • Action set: 100% screening with a check that actually detects the defect, quarantine of suspect lots, rework where rework is validated, and certified (“clean-point”) stock so good material is positively identified, not assumed.
  • Effectiveness check: a containment screen has an escape rate like any inspection. Verify the screen catches seeded or known-bad parts before trusting it with the customer.
  • Exit criteria: defined up front: containment ends when the permanent corrective action (D5-D6) is verified effective, not when everyone gets tired of the inspection cost.

How to read the output

Track containment like a process of its own: parts screened, fallout rate, escapes. The fallout trend is live evidence for the investigation, if quarantine-and-screen fallout suddenly drops to zero while the suspected cause is still untouched, the defect was intermittent upstream and the containment boundary may be drawn around the wrong window. And watch the calendar: containment cost is roughly linear in time, so a D3 that has run for months without a D5 behind it is the signature of an investigation that stalled, the bridge became the building.

A real use case

A customer flags intermittent low open-circuit voltage in delivered cells, a self-discharge signature that takes days to manifest. Containment lands within hours, scoped by genealogy: the implicated assembly line is stopped while the two lines testing clean keep shipping, the affected production window is quarantined across finished goods and in-transit stock, sister-line cells from the same electrode lots are pulled in, and a 100% OCV-retest screen with a tightened delta-V limit goes up at outgoing inspection. The screen is validated against the customer-returned cells first, it catches them, and a clean point is declared at the last lot that passes extended retest. Fallout clusters in two electrode lots, which quietly hands the D4 investigation its first real clue while the customer ships nothing else suspect.

Common mistakes

  • Letting containment become the fix. If 100% inspection still runs a quarter later, the 8D stalled at D3 and the defect is now a permanent cost center.
  • Screening with a check that does not detect the defect, unvalidated containment is theater, and the escapes continue with a paper trail saying they cannot.
  • Scoping to one line. The same process on a sister line, the same material in another product, and stock already in transit are all part of D3.
  • No exit criteria, containment without a defined end either ends too early (escapes) or never (cost).
  • Discarding the containment data. Screening fallout by lot, shift, and date is free evidence for the root-cause work happening in parallel.
How Niobia runs it

D3 with the data wired in

Inside Niobia’s guided 8D workflow, D3 produces a structured containment record: scope, actions, validation status, exit criteria, and owners, kept in the audit trail that formal investigations (ISO 9001, IATF 16949, FDA 21 CFR Part 820) require, and feeding the 8D report it generates when the customer demands that format. The screening data itself goes to work: spec-compliance checks run the screen results pass/fail by lot and by limit, and the fallout clustering across lots and dates becomes evidence the cause-analysis disciplines pick up directly. It will not let a containment quietly stand in for a root cause, a confirmed cause requires cited evidence, and D3 is explicitly not that.

Frequently asked

What is the difference between containment (D3) and correction (D4-D6)?

Containment protects the customer from parts already at risk, screen, quarantine, rework, while the cause is unknown. Correction eliminates the verified cause so new parts are made right. D3 changes nothing upstream; that is its definition, not its weakness.

How do I know the containment screen actually works?

Validate it against known-bad parts, customer returns, seeded defects, before relying on it. Every inspection has an escape rate; an unvalidated 100% screen is an assumption wearing a checkpoint's uniform.

When does containment end?

When the permanent corrective action is implemented and verified effective, defect rate down and staying down, plus a defined clean point so certified stock is unambiguous. Define those exit criteria when containment starts, not when the inspection bill arrives.

Used in these applications

Where this method shows up in practice

This method page is live before the application cross-links are fully expanded. Start with the wider Applications index to explore where Niobia uses it today.