Bulk
Product/Quality Management

Every defect, numbered and owned.

Scattered defect notes, sticky labels and one-off A3 sheets become one numbered, owned, traceable queue — every quality event tied back to the job, part or supplier that caused it, with a built-in root-cause toolkit where the investigation happens.

First Pass Yield & Defect PPM Root-cause analysis built in A trail from defect to closure
In plain terms

What is Bulk Quality Management?

Bulk Quality Management turns scattered defect notes, sticky labels and one-off A3 sheets into one numbered, owned, traceable queue. Every quality event is tied back to the job, part or supplier that caused it, with a built-in root-cause toolkit where the investigation happens and live First Pass Yield and defect PPM across the plant.

The escalation path

One defect, five ways up.

A problem found on the line starts as an Issue and escalates only as far as it needs to — into an NCR, a physical Hold, a CAPA or a full 8D. Scroll the path and each stage opens in turn, carrying context forward with no re-keying.

01
ISS-0142Burr on bore edgeMajor
Job J-4805 · OP 40 · CNC-204 · 6 pcs affected
Severity
MinorMajorCritical
Evidence
+
Disposition
ScrapReworkUse-as-isReturn
02
NCR-0086Non-conforming lot 7741At MRB
Draft
Review
3MRB
4Disposition
5Closed
Material Review Board · today 14:00
AOJMRK3 signatures required
Use-as-is + concessionReworkScrap
03
HOLD · H-012Quarantine bay 3 · tag applied 08:42
Severity ladder
Quarantinesuspect stock isolated
Production holdline stops consuming
Stop-shipnothing leaves the dock
240 pcs held£42,000 value at risk
04
CAPA-0031Eliminate burr at sourceImplementing
Action items → linked tasks
Re-cut chamfer tool pathLN
Update op-40 work instructionAO
Train night shift on new WIJM
Effectiveness check
EffectivePartiallyNot effective
05
8D-0009Coupling field failureD4 · root cause
D0D1D2 D3D4D5 D6D7D8
Auto-saved · effectiveness checks at 30 / 60 / 90 days
Root-cause analysis

Five investigators, built in.

Every analysis tool lives inside the record where the investigation happens — drop one into an 8D discipline, a task, or a safety incident, with the same code. Up to five analyses per record, each auto-saving as you work.

01Fishbone · Ishikawa

Sort every cause by category.

Categorised cause analysis off a single effect statement, with a primary-cause flag and multi-diagram tabs. Categories snapshot at creation, so the history stays intact.

DEFECT MACHINE METHOD MATERIAL MANPOWER MEASURE ENVIRON
025-Why

Drill from symptom to cause.

A one-to-five answer chain rendered as a drill-down from the problem statement — the fastest path from a symptom to a cause actually worth fixing.

Coupling failed in service
Why 1A fatigue crack started in the bore.
Why 2The bore carried a sharp machining step.
Why 3The stress-relief radius was never cut.
Why 4The operation sheet didn't call for it.
Why 5 · rootThe spec template omitted the stress-relief step.Root cause
03Fault tree

Map every failing path.

A top-event graph with intermediate and basic events joined by AND / OR gates, drag-positioned — for failures with more than one contributing path.

TOP EVENT · Coupling leaks
OR
Seal degraded
basic event
Over-pressure
basic event
04Is / Is-Not

Pin down where it isn't.

A structured comparison table — dimension, is, is-not, distinction — that pins down exactly where a problem lives, and just as importantly, where it doesn't.

DimensionIsIs-not
WhatBore Ø over tolSurface finish
WhereLine 3 · op 40Lines 1–2
WhenAfter tool changeShift start
Extent1 in 12 partsWhole batch
055W2H

Frame it before you fix it.

The structured-description form — what, where, when, who, how, how many, why-significant — that frames a problem completely before anyone reaches for a fix.

WhatCoupling bore oversize
WhereLine 3 · operation 40
WhenDay shift, post tool-change
WhoCaught by QC inspector 2
HowCMM, 0.04 mm over limit
How many6 of 72 in the lot
Why significantFails fit at assembly — a stop-ship risk on the export order.
And one gate on top

Nothing closes until it's signed.

A polymorphic acknowledgement layer wraps any record or revision: name the people who must sign, and they see a blocking dialog with a drawn signature until they do — every request, view and signature on an immutable trail.

Sign-off required · 8D rev 4
A. OkaforQuality Lead
A. OkaforSigned
J. MensahPlant Manager
Sign herePending
This revision stays locked until every party signs.
The deep dive

Nine disciplines, D0 to D8.

The richest record in the module. Each discipline is its own card with guidance, requirements and an auto-save indicator; two of them embed the full root-cause suite. Complete a discipline to advance the report — undo to step back.

D0Plan
D0

Plan

Gate the investigation: confirm the problem deserves a full 8D, and stand up emergency response actions while you decide.

Go / no-go gatewayEmergency response actions live
D1Team
D1

Team

Champion, leader and cross-functional members — named on the report, so ownership is never vague.

Champion & leader namedCross-functional members on record
D2Problem
D2RCA

Problem

Frame it completely with 5W2H and Is/Is-Not — the root-cause suite embeds right inside this discipline.

5W2H description writtenIs / Is-Not boundary drawn
D3Contain
D3

Contain

Interim containment protects the customer while the cause is still unknown — verified, not assumed.

Containment action in placeVerified on the line
D4Root cause
D4RCA

Root cause

Fishbone, 5-Why and fault tree drive to a cause worth fixing — and the result syncs back to every linked issue.

Fishbone · 5-Why · fault treeCause syncs to linked issues
D5Correct
D5

Correct

Choose the permanent corrective action — and validate it on paper before anything rolls out.

Permanent action chosenValidated before rollout
D6Implement
D6

Implement

Put the fix on the line, verify it holds under real production, and retire the interim containment.

Fix live & verified in productionInterim containment retired
D7Prevent
D7

Prevent

Change the system — specs, templates, training — so the same failure can't come back somewhere else.

Specs, templates & training updated
D8Close
D8

Close

Verify effectiveness at 30 / 60 / 90 days, recognise the team, and close the report for good.

30 / 60 / 90-day checks passTeam recognised
Why teams switch

All in one place.

One place for defects
Every problem,
owned
From a quick issue to a full investigation — each one gets a number, an owner and a clear next step.
Find the real cause
5 proven
tools, built in
Trusted methods like Fishbone and 5-Why live right inside the record — so the fix actually sticks.
Guided investigations
The full 8D,
step by step
The full 8D process, broken into clear stages so nothing gets skipped and the report writes itself.
Always know where you stand
Live quality,
at a glance
Yield and defect rates update in real time across the whole plant — no spreadsheets, no waiting.
Wired in

Quality doesn't sit in a silo.

Defects arrive from the floor, corrective actions become real tasks, and the same root-cause tools serve safety — quality is connected to everywhere a problem can start or end.

Production

Issues link to jobs, steps and assets — a scrap tap on the floor opens a lifecycle record here.

Tasks

NCRs, CAPAs and 8Ds create linked tasks tagged with the source and discipline — corrective action, tracked.

Safety

The same RCA suite powers incident investigation, and risk-assessment revisions use the sign-off engine.

Suppliers

Issues, NCRs, holds and 8Ds reference suppliers — return-to-supplier and RMA flow through.

Settings

Quality categories and a shared root-cause catalogue feed every classifier and picker.

Dashboards

FPY, Pareto, open 8D and corrective-action counts feed the cross-module team and quality boards.

Straight answers

Questions, answered.

01

What is Bulk Quality Management?

It replaces scattered defect notes and one-off A3 sheets with one numbered, owned, traceable queue — every quality event tied back to the job, part or supplier that caused it, investigated in the same record.

02

How does a defect get owned and tracked?

From a quick issue to a full investigation, each defect gets a number, an owner and a clear next step — so nothing sits in someone’s notebook and every event has a trail from defect to closure.

03

What root-cause tools are built in?

Five proven methods, including Fishbone and 5-Why, live right inside the record — so the investigation happens where the defect is logged and the fix actually sticks.

04

Does it support the 8D process?

Yes. The full 8D process is broken into clear, guided stages so nothing gets skipped and the report writes itself as you work through the investigation.

05

What quality metrics can I see live?

First Pass Yield and defect PPM update in real time across the whole plant, so you always know where you stand — no spreadsheets and no waiting.

06

Can a quality event be traced to its source?

Every quality event is tied back to the job, part or supplier that caused it, giving you a trail from the defect through the investigation to closure.

Stop chasing defects across three systems.

We'll take one real non-conformance from your floor and walk it the whole way — Issue to 8D to closed — so you can see the trail it leaves.