Today
Every deviation needs an investigation with root cause, impact assessment and CAPA, often under time pressure because batches are on hold. Whether the same failure happened before and whether the CAPA back then worked sits in old reports, maintenance logs and e-mails. Recurring deviations surface late, sometimes only during an inspection.
An example
At Rhenalis, the hardness of film-coated tablet FT-500 in batch 26-0412 on tablet press T3 is below the IPC limit. The agent finds two similar deviations on the same press from the previous year, both shortly after a punch change, and a CAPA from then without an effectiveness check. It lists three more batches that ran on T3 since the last punch change and drafts the deviation report. QA classifies the deviation as major and decides on the four batches.
Your data, wherever it lives
Today deviations and CAPAs sit in the QMS, process data in the MES, test results in the LIMS, maintenance in the maintenance system and older investigation reports as scans in the DMS. demi reads, understands and links them per equipment, product and batch, with your rights. The AI finds similar cases in seconds instead of after a long search, and QA decides on classification, root cause and CAPA.
Where the data lives today
- QM system
- MES
- Databases
- Machines & sensors
- DMS & archive
- Scans & paper
- E-mails
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the QMS, MES, LIMS, maintenance and DMS. demi replaces nothing and links every deviation to product, batch, equipment, process step, maintenance, earlier deviations and their CAPAs. demi only writes back after approval, for example the draft report into the QMS.
- 2 · PermitPermission Layer
QA sets classification, root cause and CAPA. Production sees the deviations of its area, a client's data only those who work for that client, and every step is in the audit trail.
- 3 · ActIntelligence Layer
The agent searches for similar deviations by equipment, product, process step and failure pattern, even when they are worded differently. It lists every batch that ran under the same conditions, checks whether earlier CAPAs are closed and checked for effectiveness, and drafts the report to your template.
How it runs
- 1
Record the deviation in the QMS as before
- 2
Find similar past cases with root cause and CAPA
- 3
Narrow down affected batches and equipment
- 4
Draft the report and impact assessment
- 5
QA classifies, sets the CAPA and decides on the batches
What changes
Recurring deviations caught early
Investigations closed sooner
Every impact assessment backed by sources
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+300 hfreed per year
Assumptions and calculation
demi finds past cases, affected batches and CAPAs and drafts the report; QA classifies.
4 h → 3 h per case
How we calculate
25 deviations × 4 h × 25% × 1.0 (manual) × 12 months = 300 h
Value per year, before demi costs
Freed per year+300 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$19,500
gained per year
300 h ÷ 1,760 h per role = 0.2 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
How does demi know about earlier deviations?
From your QMS and the reports in the DMS, including scanned old reports. The agent reads failure pattern, root cause and CAPA and assigns them to equipment, product and process step. No system is replaced.
Does demi classify the deviation itself?
No. The agent proposes a classification with its reasons, for example because a similar case was rated major. Whether the deviation is minor, major or critical is decided by QA, with the reason in the record.
Can demi tell whether a CAPA worked?
demi shows whether a CAPA is closed and checked for effectiveness, and whether the same failure pattern came back afterwards. Whether the action was effective is assessed by QA.
What happens to the affected batches?
The agent lists them with their status, such as quarantine, released or shipped. Hold, release and a possible recall remain decisions of QA and the Qualified Person.
