A defined quantity of material or product produced or received under uniform conditions, managed as a single traceable unit.
In manufacturing, a **lot** commonly refers to a defined quantity of material or product that is:
– Produced or processed under essentially uniform conditions, or
– Received as a single delivery from a supplier,
and is identified and managed as a single traceable unit throughout planning, production, quality control, inventory, and distribution.
Lots are usually identified by a **lot number** (or batch number) that is carried across systems such as ERP, MES, LIMS, and QMS.
A lot usually has these properties:
– **Uniformity of conditions**: Made or received within a defined time window, on a given line or piece of equipment, using the same recipe, specification, or revision.
– **Single identifier**: A unique lot or batch ID used across documents, labels, barcodes, and digital records.
– **Traceability scope**: Acts as the basic unit for backward and forward traceability (from raw materials to finished goods and customers, and vice versa).
– **Quality status**: Shares common quality disposition (e.g., released, on hold, rejected) unless it is later split into sub-lots.
In integrated manufacturing systems, **lot** is used in related but distinct ways:
– **In ERP systems**:
– Represents inventory units for planning, costing, and stock management.
– Lot numbers group quantities of raw materials, intermediates, or finished goods with shared attributes (expiry date, grade, spec).
– Transactions (receipts, issues, transfers) typically occur at the lot level.
– **In MES and shop-floor systems**:
– A lot may represent a production run, a batch on a specific line, or a container of material.
– MES can track detailed consumption (by lot, serial, or unit) and associate it with operations, equipment, operators, and process parameters.
– Lot genealogy is maintained, showing which input lots were used to produce which intermediate or finished lots.
The same physical material may be represented as a single lot in ERP but split into multiple process lots or containers in MES, or vice versa, depending on system design.
Lots are a core construct for **material traceability**:
– **Backward traceability**: From a finished product lot to all contributing raw and intermediate lots.
– **Forward traceability**: From a specific raw material lot to all intermediate and finished product lots that used it.
– **Genealogy records**: Link lots to process steps, work orders, equipment, and quality results.
In regulated industries (e.g., aerospace, life sciences, food), lot traceability is often required to support investigations, containment decisions, and documentation for audits or customer inquiries.
– **Lot vs. batch**:
– Often used interchangeably in many industries.
– *Batch* more strongly implies a discrete, recipe-driven production run (common in batch processing, pharmaceuticals, chemicals).
– *Lot* is slightly broader and can refer to any grouped quantity produced or received under comparable conditions, including continuous or semi-continuous output.
– **Lot vs. serial number**:
– A **lot** groups many units under a single identifier.
– A **serial number** uniquely identifies a single unit, assembly, or component.
– Some environments use both: a serial-numbered unit is also linked to its source material lots.
– **Lot vs. container or pallet ID**:
– A **container/pallet ID** identifies physical packaging or a handling unit.
– A **lot** describes a traceability grouping of material; one lot can span multiple containers, and one container can (in some designs) hold multiple lots.
Within the context of differences between MES and ERP in material tracking (such as in aerospace):
– ERP typically manages **lot-based inventory** for procurement, costing, and availability.
– MES records **lot-level consumption and transformation** at each operation, often alongside unit- or serial-level tracking.
– Reliable traceability requires alignment of lot definitions and identifiers between ERP and MES, so that movements and genealogy records refer to the same logical lots across systems.
When designing integrations, the chosen **lot granularity** (how big a lot is, and how it maps to containers, work orders, and serial numbers) directly affects how traceability and investigations are performed.