Quality-control module (QC, NCR/CAPA)
Quality control by the standard, not by eye: an ISO 2859-1 sampling plan for the lot size, process stability monitoring, lot dispositions — accept, reject, rework. The verdict is computed from the plan and actual measurements, so a borderline lot does not pass because someone was in a hurry. Defects group by cause and supplier — the supplier conversation starts from numbers. For manufacturing and anyone running incoming inspection.
/quality/qcThey read the same documents as your team, prepare the next action, surface exceptions and keep the decision trail inside the process.
You set the authority. External messages, money and irreversible actions remain approval-gated until verified evidence earns a wider mode.
Choose an industry preset and start with realistic demo data; the team sees the target flow before migration.
Import or connect source data. Digital employees observe, draft and expose gaps while people confirm decisions.
For a typical 50-person company, the target is four weeks. Source quality, integrations and legal requirements can change it.
A module is more than screens. Digital employees work behind them: they prepare the decision and bring it to you instead of waiting for you to type everything in. Below — who exactly, what they do, and where their authority stops.
Computes the sampling plan and derives the verdict from measurements
A borderline lot is always a human call
Every capability below is tied to an implemented product route. A reviewed product screenshot is shown when it exists in this language; otherwise the route is explained as a transparent work loop, never as invented UI.
The AQL sampling plan is computed to the standard: give the lot size, AQL level and inspection level, and the system returns the sample size and the accept/reject thresholds. The lot decision is recorded together with its grounds.
/quality/qcAccept, reject, rework — the verdict is computed from the sampling plan and actual measurements. A borderline lot does not pass because someone was in a hurry.
/quality/qcA period view of inspections: where defects repeat, which supplier brings them, what rework yielded. The supplier conversation starts from numbers.
/quality/dashboardControl limits and Western Electric rules: feed in a series of measurements and the system says whether the process is stable or already drifting. Alongside it, the quality dashboard: scrap share, recurring defects and the suppliers behind them.
/quality/dashboardYes. Start with one workflow and the data it needs. Add adjacent modules only when the operating process calls for them.
Digital employees watch product records, prepare the next action, surface exceptions and keep the decision trail. Their exact actions and authority gates are shown on this page.
Your team sets the authority. External messages, money and irreversible actions stay approval-gated until you deliberately expand the operating mode.
You can review the target flow with realistic demo data on day one and connect real evidence during the first week. For a typical company of up to 50 people, four weeks is the target for moving one operating loop; source quality, integrations and legal requirements can change it.