Batch genealogy is the linked record of everything that went into making a given batch: which raw-material lots were charged, which intermediate batches were consumed, and which equipment was used. It is the family tree of a product, and it exists so a plant can trace materials in both directions. Forward tracing answers where a suspect lot ended up; backward tracing answers what went into a batch under investigation. This bidirectional traceability is what makes recalls containable and quality investigations tractable, and it ties batch control directly to the broader theme of traceability.
batch genealogy in one line: Batch genealogy is the linked record of which raw-material lots, intermediate batches, and equipment went into a given finished batch. It enables forward tracing, following a material lot to every batch that used it, and backward tracing, listing everything consumed by a batch. This bidirectional traceability is essential for recalls and quality investigations.
Genealogy is valuable because it works in two directions. Backward tracing starts from a finished batch and asks what went into it: every raw-material lot charged, every intermediate consumed, and the equipment used. If a finished batch fails a quality test, backward tracing lets investigators list every input that could be responsible and check whether any of them is implicated in other failures too.
Forward tracing runs the other way. It starts from a raw-material lot, or an intermediate, and asks where it went: every batch that consumed it, and every downstream batch made from those. When a supplier reports a contaminated raw-material lot, forward tracing identifies exactly which finished batches contain it, so a recall can be scoped precisely rather than pulling far more product than necessary.
The power of having both directions is that an investigation can pivot. Start backward from a bad finished batch to find a suspect ingredient lot, then pivot forward from that lot to find every other batch it touched. A complete genealogy makes this two-step reasoning possible, turning what would be a plant-wide guess into a bounded, defensible list of affected batches.
Genealogy is built up phase by phase as a batch runs. When a charge phase adds a material, the batch engine records not just the quantity but the specific lot number of what was charged, linking that lot to this batch. When a phase consumes an intermediate produced by an earlier batch, it records the identity of that source batch, creating a parent-child link in the genealogy tree. Equipment used is captured too, so a batch knows which vessels and lines touched it.
This produces two complementary records: the materials consumed by the batch and the materials produced by it. A batch that makes an intermediate is a producer, and that intermediate becomes an input consumed by a later batch. Chaining these consumed-and-produced links across many batches builds the full multi-level tree, from purchased raw materials through every intermediate up to finished product.
Capturing genealogy as the batch runs, rather than reconstructing it afterward, is what makes it trustworthy. Because the lot charged is recorded at the moment of charging by the phase that charged it, there is no ambiguity later about which lot went into which batch. The genealogy is a natural byproduct of executing the recipe with lot tracking switched on, not a separate documentation exercise bolted on at the end.
Genealogy and the batch report are related but distinct. A batch report documents what happened within one batch: its parameters, timings, exceptions, and sign-offs. Genealogy documents the relationships between batches and materials: the network of lots and parent batches that connect one batch to others. The report is inward-looking, focused on a single batch; genealogy is outward-looking, connecting a batch to its inputs and outputs across the whole production history.
The two serve different questions. A batch report answers did this batch run correctly, while genealogy answers where did this material come from and where did it go. A quality reviewer reads the batch report; a recall coordinator queries the genealogy. Because they answer different questions, most systems maintain both, with the batch report giving the single-batch detail and genealogy giving the cross-batch traceability.
For a cloud SCADA platform overseeing distributed or multi-site operations, centralized genealogy is a strong traceability asset. When lot consumption and production are captured at each site and streamed to the cloud, forward and backward traces can span facilities, following a raw-material lot from the site that received it through the sites that processed it. That cross-site view turns genealogy from a per-plant record into an enterprise-wide traceability capability, which is exactly what a fast, precisely scoped recall requires.
Backward tracing starts from a finished batch and lists everything that went into it, every raw-material lot, intermediate, and piece of equipment. Forward tracing starts from a material lot and lists every batch that consumed it and every downstream product made from it. Backward tracing supports quality investigations; forward tracing supports scoping a recall precisely.
A batch report documents what happened inside one batch, such as its parameters, timings, and exceptions. Batch genealogy documents the relationships between batches and materials, the network of lots and parent batches that connect a batch to its inputs and outputs. The report is inward-looking for one batch; genealogy is outward-looking across the whole production history.
It captures genealogy as the batch runs, phase by phase. When a charge phase adds a material it records the specific lot number, and when a phase consumes an intermediate it records the source batch, creating parent-child links. Recording lots at the moment of charging, rather than reconstructing later, is what makes the genealogy trustworthy and complete.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.