cycle count

Core meaning

A **cycle count** is a recurring, sample-based physical inventory check in which a subset of stock (items, locations, or both) is counted and reconciled against the recorded inventory in a system such as ERP, WMS, or MES.

Unlike a full physical inventory, which attempts to count all stock at once, cycle counting spreads counting activities over time according to a defined schedule or sampling strategy.

How cycle counts are used in manufacturing

In industrial and regulated manufacturing environments, cycle counts commonly:

– Focus on specific **locations** (e.g., high-velocity racks, quarantine areas, kitting zones)
– Focus on specific **materials** (e.g., high-value APIs, controlled components, serialized parts)
– Are triggered by **time**, **transaction volume**, or **risk category** (e.g., ABC classification)
– Are executed via **scanners, mobile terminals, or MES/WMS terminals** on the shop floor
– Result in **reconciliations**: adjusting system records, investigating discrepancies, and documenting reasons (e.g., scrap not recorded, mis-picks, unit-of-measure errors)

Cycle counts can be planned (on a defined schedule), event-driven (triggered by anomalies), or both.

Relationship to MES and inventory accuracy

In the context of MES- and ERP-integrated operations, cycle counts:

– Provide the **ground truth** used to measure inventory accuracy KPIs
– Are often initiated or recorded in MES or WMS, then reconciled back to **ERP/MRP** stock records
– Help validate that **transaction logic, scanning workflows, and master data** correctly represent real movements and consumption on the shop floor
– Are used as a **statistical sampling method** to assess whether an MES inventory-accuracy pilot is producing stable and auditable improvements

A well-defined cycle count program typically specifies scope (materials, locations), frequency, counting method (blind vs. guided), and rules for investigating and documenting discrepancies.

Boundaries and exclusions

A cycle count **includes**:

– Physical verification of quantities (and sometimes status or condition) of selected inventory
– Comparison of the physical result with the system on-hand balance
– Documentation and processing of necessary adjustments or investigations

A cycle count **does not necessarily include**:

– Counting all inventory across the entire site in one event (that is a full physical inventory)
– Valuation or costing calculations beyond updating quantities
– Broader process-improvement activities, although findings may later be used for root-cause analysis

Common variants and methods

Common cycle counting approaches include:

– **ABC cycle counting**: higher-frequency counts for A-class (high-value/critical) items; lower frequency for B/C items
– **Location-based cycle counting**: rotating through storage locations (bins, racks, zones) on a schedule
– **Event-based cycle counting**: triggered by stockouts, negative inventory, or system exceptions
– **Blind counting**: counters do not see the system quantity before counting, to reduce bias

These methods can be combined and configured based on risk, regulatory requirements, and operational constraints.

Common confusion and misuse

Cycle count is often confused with:

– **Full physical inventory**: a one-time, comprehensive count of all stock, often requiring production shutdown or system freeze. Cycle counts are ongoing and partial.
– **Inventory audit**: a formal, often external assessment that may use cycle counts as evidence but has a broader assurance objective.

In manufacturing IT/OT contexts, “cycle count” refers specifically to the **inventory counting activity**, not to:

– Production machine cycles
– Maintenance cycles
– Process control loop cycles

Site-context application

Within MES- and ERP-integrated manufacturing systems, cycle counts are a key mechanism for:

– Verifying that **system-recorded inventory** reflects physical reality at selected points
– Providing **statistically sound stock checks** for pilots and ongoing operations
– Supplying data to measure whether changes to MES workflows genuinely improve **inventory accuracy** and stay stable under day-to-day operating conditions.