Manufacturing › Make
Batch Records
The recipe, and the executed record that makes a batch evidence rather than data.
In Manufacturing → Make · 8 screens
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Master Recipes | List | The process industry’s counterpart of a BOM plus a routing: its steps carry parameters with specifications, and its quantities scale with batch size. | 11 | 17 | 2 |
| Recipe Phases | List | The instruction as it is read on the floor. Held as text rather than as a reference because the executed copy has to be the one that was approved. | 10 | 15 | 0 |
| Recipe Parameters | List | What has to be measured, and what it has to be. Fixed here, BEFORE the batch — which is the property that makes an in-spec judgement a fact rather than a later opinion. | 10 | 13 | 0 |
| Batch Records | Read-only list | What a batch DID, in the order it happened, with every controlled parameter against the specification it was supposed to meet. Review by exception: the counts say whether it can be released without reading two hundred pages. | 13 | 0 | 5 |
| Batch Steps | Read-only list | The executed phases, in sequence. A step is executed through its own route and signed; it is never edited on a grid. | 12 | 0 | 3 |
| Parameter Captures | Read-only list | Every captured value against the specification that was fixed before the batch started. A correction does not overwrite — it points at the original, because an audit trail that can be edited is not one. | 13 | 0 | 0 |
| Batch Deviations | List | Raised at the moment it happens, by the person or the machine that saw it. A deviation opened at review time is a much weaker animal. | 12 | 0 | 1 |
| Batch Signatures | Read-only list | Who signed what, and what the signature MEANT. The signed content is hashed, so a later edit would not match — and there is no update path, because that is what a signature is. | 9 | 0 | 0 |