Batch Size
How does batch size differ from lot size?
Batch size is the operational quantity processed together in one run or movement, while lot size is the traceability or procurement unit tied to a specific lot number. They may be equal in practice but are not always identical, since a lot can be split across batches or multiple lots can be consolidated into one batch.
Why does batch size matter for OEE and throughput?
Batch size directly affects setup frequency, queue length, and waiting time. Larger batches generally improve run-time efficiency by reducing changeovers but can lower responsiveness and increase inventory days on hand, while smaller batches add setup interruptions that reduce overall equipment effectiveness if not carefully planned.
How is batch size enforced in ERP or MES systems?
Systems enforce minimum, maximum, and step batch rules, or select work definitions by quantity range. The planned order must conform to those limits before release or sequencing is accepted; otherwise the system may choose the wrong routing, split the order, or defer production.
Batch size is the quantity of units, lots, or parts processed together as one production, picking, receiving, or planning block before the next block starts. In manufacturing, it is the number of items produced consecutively without interruption, often constrained by minimum, maximum, and step-size rules. It determines grouping for production runs, material transfers, and warehouse waves, balancing setup efficiency against inventory exposure.
On the shop floor, batch size determines how many units are grouped into a production run before changeover, directly balancing setup time against work-in-process and finished-goods exposure. Large runs reduce changeovers but delay defect discovery, while smaller runs improve responsiveness and lot-level traceability at the cost of more frequent setups and scans. In process manufacturing, the released quantity must fall between defined minimum and maximum batch values so the correct routing or recipe version is selected. In warehousing, the same logic governs receiving, putaway, replenishment, and picking waves: one batch becomes a single operational unit, reducing labor fragmentation but increasing the impact of any count or inspection discrepancy. In material tracking, batch size sets traceability granularity, because smaller batches isolate shortages, mispicks, or scrap faster, while larger batches reduce transactions. The core planning tradeoff is setup cost versus inventory cost, minimized under equipment, demand, and lead-time constraints.
Oversized batches create hidden stock and delayed problem detection: Running extremely large batches masks defects and wrong component usage until many units are finished, amplifying scrap, rework, and traceability cleanup while inflating work-in-process inventory.
Undersized batches overload changeovers and receiving throughput: Very small batch sizes force excessive setups, sanitation, scans, and administrative movements, creating bottlenecks at machines, docks, or warehouse stations and raising labor cost per unit.
Mismatch between batch rules and actual demand causes scheduling failure: When planned order quantities fall below minimums or exceed maximums, the system picks the wrong work definition, splits orders unexpectedly, or defers production, triggering shortages and unstable line sequencing.