Own output and the loss ledger, and approve the action on each loss
- The loss to fix first, with its record
- Deviations raised from evidence, not memory
- A fix confirmed by batches that held
Yield loss analysis that takes each batch from theoretical yield to the tablets packed, opens the record behind each loss, and ranks the losses that keep coming back.
See one batch's lost tablets traced screen by screen ↓Yield is calculated at each phase because the GMP rules require it: theoretical, actual and percentage of theoretical, verified by a second person. Then it is filed. A batch that lands inside its limits passes review, and its reconciliation sheet attributes most of what it lost to a step.
What nobody sees is that the largest step on that sheet, compression rejects, repeats on batch after batch run with the same punch set. Month-end spreadsheets arrive weeks late without the counter printouts behind them, and when a reconciliation goes over its limit, the pressure is to explain it rather than investigate it.
Built forProduction managersProcess engineersQA batch record reviewersPlant finance controllers
A batch passes its yield limit, and the loss behind it returns on the next batch and the one after, unseen.
Read one batch record at a time
Built-in controls
Yield stops being a filed number and becomes a ledger of fixes that each line and plant works from.
Production managers, process engineers, QA reviewers and plant finance use them to see where tablets went and which losses to fix first. They follow one film-coated tablet batch.
demoSample data throughout: the plant, its client, the people, batches and costs.
Production owns the losses, engineering finds them, QA verifies the yields, finance prices what they cost.
Own output and the loss ledger, and approve the action on each loss
Build waterfalls, trace recurring losses and compile the annual yield section
Verify each yield calculation and sign explanations and rules
Own the cost basis and price each loss and each option
Four things the agents raised on one product's year, each one a filed yield would have hidden.
The counter showed 30,000 rejects, but 1,200 were press-check samples sent through the reject gate; the corrected 28,800 became an approved rule.
One set's 14 batches averaged 2.09% rejects against 0.80% for the other set on the same press: 216,000 tablets.
Five batches were compressed after that set reached its inspection point, with its work order open 37 days; each went to QA.
About 5,500 rejects went uncounted at a login, so the deviation reaches two earlier batches with the same reset.
demoSample data, from the working solution.
Behind the waterfall: each batch's status, each step's record, the limits from the master record, and the losses of other plants.
demoSample data, from the working solution.
Results move by name, from one agent to the next and then to a person.
Builds each batch's waterfall from the batch record, the press counter, the in-process log, the sample list and the reconciliation sheet.
Looks for where unaccounted tablets could have gone, through the counts and the weights.
Groups losses across batches, punch sets, shifts and equipment as percent of theoretical.
Links a recurring loss to tooling, equipment, material or shift through the press log, tooling records, work orders and the historian.
Asks of each explained loss, and of the agents' own draft, which record proves it.
Prices each loss and each option with the signed cost basis, its assumptions shown.
Drafts the yield section of the annual product review and the client's yield summary.
Yield loss analysis finds where a batch's tablets went between theoretical and actual yield, and which of those losses keep recurring. Here agents build each batch's waterfall from its records, rank recurring losses across batches and trace their causes, while people approve actions and verify yields.
Actual yield is compared with theoretical yield at the end of each appropriate phase and recorded as a percentage of theoretical, then verified by a second person, or by one person when validated equipment calculates it. The agents' calculation is treated as such a system, validated before use, and QA verifies each yield.
Batch reconciliation balances the good tablets and each counted loss against theoretical yield; what remains is unaccounted and must sit within the batch record's limit. Here a reconciliation over its limit always becomes a deviation, and the closed sheet stays as it was.
No. They read the batch record, counters and logs without writing to them. They propose leads for unaccounted tablets; a person raises the deviation, the engineer attaches the evidence, and QA accepts it or sends it back.
With the cost basis finance signed: conversion cost plus the value of the active agreed with the client, per tablet. The assumptions behind each option are shown and editable, and no agent invents a cost.
Yes. Losses are counted one way, as percent of theoretical with units and the signed cost basis, so presses, punch sets, shifts and plants compare on equal terms. A fix found on one press can become a check on each press once QA approves it.
When the loss stays down on the corrected setup. Each recurring loss on the ledger has an owner, a next action and a due date; the owner acts, and a second person confirms the fix only after three batches on the corrected setup show it held.
Slow leaks found across four record streams, priced and owned before they become a major deviation.
1-min demoOEE & Downtime AnalysisLost line time gets a cause and an owner by the next morning, and the operator's note becomes the record of why.
1-min demoProduction Bottleneck AnalysisPlants find the step that really limits them, rehearse the fix, and take on more client volume.
1-min demoSend one closed batch record with its counter printouts and reconciliation sheet, and we will build its waterfall and rank what repeats.