Part counting methods and which one fits your machine

The counting method that fits your machine depends on where one part becomes visible. Count machine cycles and multiply by the parts each cycle makes on a CNC, a press or a molder. Count beam breaks where finished units pass one point in single file, as on a packaging line or a bagger. Read the controller’s counter when the machine already reports one, and keep a hand tally to prove the others.

This guide is for manufacturing engineers choosing how to count across a mixed floor. It covers how each signal becomes a count, a machine-by-machine table, the errors each method makes and one validation worked two ways. How a sensor tells running from stopped is a separate question, answered in how a sensor knows a machine is running.

What are the four ways to count parts?#

There are four sources of a part count: the machine’s own cycle, a beam break at a fixed point, the controller’s counter and a person with a tally. Each counts a different event, so each answers a slightly different question.

The event decides what the number means. A cycle count says what the machine did, including scrap and setup pieces. A beam after the last reject station says what the line shipped. The rest of this guide takes each method in turn.

How does a machine cycle become a part count?#

A machine cycle becomes a part count when a rule decides where one cycle ends, counts those ends, and multiplies the total by the parts each cycle yields. The rule has to match the shape of the machine’s signal.

The glossary entry for detection algorithm uses the same meaning. Three signal shapes cover most machines, and each takes a different rule.

One burst per cycle#

A CNC mill vibrates while it cuts and falls back to idle while the operator unloads and reloads. Count one cycle each time the trace falls back to idle and stays there.

Merge short dips back into the burst they interrupt. A tool change or a probe move drops the trace for a few seconds without finishing the part, so a rule that counts every dip splits one part into two. Counting bursts also beats dividing run time by an average cycle when the job mix changes, as the CNC part-count guide works through.

One impact per part#

A stamping press makes one part per stroke, and each stroke is a sharp impact. At 10 to 120 strokes a minute, a rule that merges nearby events merges real parts, so count every impact on its own.

The exception is a heavy press whose ram rebounds and rings twice per stroke. That press counts close to double under an every-impact rule. Move it to the merging rule, or count at the exit chute with a beam instead.

A trace that never drops#

An injection molder at temperature cycles without resting: clamp, inject, hold, cool, eject. The trace stays up through every shot, dipping for a second or two at mold open, so there is no fall to idle to count.

Divide running time by the measured cycle time instead.

Here the cycle time is the divisor, so its accuracy is the count’s accuracy. For example, a molder that really runs a 22-second shot but is entered at 21 seconds reports 3,600 ÷ 21 = 171 shots an hour instead of 3,600 ÷ 22 = 164, about 4.8% high. Time 10 to 20 consecutive shots on a good day, and see setting the ideal cycle time for why the number needs an owner.

Parts per cycle#

Every cycle count needs one multiplier: the parts one cycle makes. A four-cavity mold makes 4 parts per shot, a two-out die 2 parts per stroke and a four-station vise fixture 4 parts per cycle.

Keep the cycle time per cycle and put the multiple in the quantity per cycle setting. Halving the cycle time instead gets the part count right on a division rule and every rate, goal and gauge wrong.

When does a beam break count better?#

A beam break counts better than a machine cycle when finished units travel a fixed path in one direction and the number you report is what left the line. A laser or light beam across the path registers one count each time a unit interrupts it.

That makes the beam the right method for packaging lines, baggers, case packers and conveyors carrying output from several machines. On a filling line, no single machine’s cycle is the line’s output, and a filler, a capper and a case packer each run their own rhythm.

The count point decides what the number means. Put the beam after the last reject or divert station, so the count is good output rather than attempts. Four rules pick the exact spot:

• Single file. A beam across a conveyor two units wide counts neither lane reliably.
• Off accumulation. A unit that backs up and drifts forward crosses the beam twice.
• A gap between units. Two cartons touching end to end break the beam once for two.
• An opaque feature. Clear glass and film may pass without breaking the beam, so aim at the cap or the label band.

One break is whatever the beam sees. Aimed at single bottles, one break is 1 bottle. Aimed at cases leaving a packer, one break is a case, so a 24-count case carries a multiplier of 24. The packaging line guide covers count points in detail.

A beam also counts parts leaving a press, at the exit chute. Choose it there when the press misfeeds or rings more than once per stroke, because the exit count includes only parts that cleared the die.

When should you read the controller’s counter?#

Read the controller’s counter when the machine already reports one, IT has approved the connection, and you need what only the control knows: which program ran, which job it belonged to and how many parts it marked good or bad. A connection to the control is a security concern for many plants, and IT usually reviews it first.

Check first whether the counter counts cycles or parts, because the standards keep them apart. MTConnect defines a cycle count as the “accumulation of the number of times a cyclic function has attempted to, or is planned to attempt to execute”,^[1] and a part count as an “aggregate count of parts”.^[2]

Packaging machines that follow PackML split the count by quality instead. The standard’s example of its processed count is “the number of products that were made, including all good and defective products”, and the processed count minus the defective count is the non-defective output.^[3]

Molding machines on the OPC UA plastics model report JobCycleCounter, “the number of finished cycles in the job”, beside separate counters for good, bad and test sample parts.^[4] The mold’s cavity count is NumCavities, an optional property, so confirm your machine fills it in before you trust a part count built on it.^[5]

Choose the controller counter when you need program or job names on every count. Default to a sensor where the fleet mixes builders and decades, or where some machines have no network port at all. The sensor versus PLC comparison sets out what each approach sees, with its sources.

Where do manual counts still fit?#

Manual counts still fit in two places: as the reference that proves every automatic count, and as the record where no machine signal separates the parts. Everywhere else, a hand count is slower and less frequent than the machine.

People count in three ways. A tally sheet marks parts as they come off. A count at packout multiplies full totes or cases by their standard quantity. A count by weight divides a bin’s net weight by the weight of one part, measured over 50 parts.

A hand count carries no timestamps, so it cannot show an hourly rate or when the machine stopped. A count written at the end of a shift is also a count from memory. Log it hourly when it is the record, for example at a hand-assembly bench where no machine cycle exists.

Which method fits each machine type?#

The method that fits each machine follows from its signal: count bursts on a CNC, every impact on a press, run time divided by the cycle on a molder, and beam breaks on a packaging line or a bagger.

A molder with an operator loading inserts by hand waits between shots, so it counts like a CNC. A bar-fed lathe running one job unattended never rests, so it counts like a molder. The signal decides, not the machine’s name.

You don’t need two methods on one machine whose count already validates. A second counter is a second thing to calibrate and a second number to argue about.

What makes a part count wrong?#

A part count goes wrong in one of three places: the signal, the rule that finds cycles in it, or the multiplier that turns cycles into parts. The shape of the error tells you which.

Merged cycles happen when two fast parts land inside one burst, for example a press at 90 strokes a minute on a rule that merges dips. Double counts happen when one part rings twice on an every-impact rule, or a unit crosses the beam twice on an accumulation table.

Multi-cavity molds fail in two ways. A four-cavity mold left at 1 reports a quarter of its output. A four-cavity mold running with one cavity blocked makes 3 parts a shot, so a setting of 4 overcounts by one part in three, as the molding guide shows.

Check parts per cycle before you touch the rule. An exact multiple is almost never the detector, and no rule change fixes a multiplier. The part-count troubleshooting guide works each symptom through to a fix.

Count parts automatically with IoTFlows#

IoTFlows counts parts from each machine’s own signal, with no PLC connection. A magnetic SenseAi reads the machine’s vibration and sound and takes one of three detection algorithms: Discrete Analysis counts one burst per cycle and merges short dips, Discrete w/o Merge counts every impact, and Continuous Analysis divides running time by the cycle time.

A BeamTracker, an IP67 laser counter that bolts on in 10 to 20 minutes, runs Counter: each beam break is one cycle, with ±2% count accuracy.

Every operation carries a quantity per cycle, so cavities, multi-out dies and case counts multiply correctly. The algorithm comparison sets all four side by side.

The visibility into operator performance was eye-opening. We could immediately see which team members needed additional training to reach target speeds. Within weeks of targeted coaching based on the IoTFlows data, our newer operators were hitting 30 bags per minute. The downtime tracking also revealed setup procedures we could streamline. This platform has transformed how we manage our bagging operations.

How do you validate a count by hand?#

You validate a count by comparing it with a hand tally over the same window, twice: once in parts and once in cycles. The parts ratio tells you whether the count is right. The cycles ratio tells you whether the detector or the multiplier is wrong.

1. Pick a window and a reference

   Run the machine normally for 20 minutes to two hours on one operation. Use a hand tally of parts, and the machine’s own stroke or shot counter if it has one.

2. Read both counts for the same window

   Note the system’s part count, its cycle count and the hand tally for the same start and end times. Most disagreements are two people reading two windows.

3. Divide parts by parts

   Divide the system’s parts by the hand tally. At 95 to 105%, leave the setup alone.

4. Divide cycles by cycles

   Divide the system’s cycles by the machine’s real cycles. A cycles ratio of 1 with a parts ratio off is the multiplier; both off by the same ratio is the detector.

Had the die been set to 4 parts per cycle with a clean detector, the system would read 2,400 parts from 600 cycles. The parts ratio would be exactly 2.00 and the cycles ratio exactly 1.00, which points at the setting, not the sensor.

Validate with ten parts first, then with a longer window, as the first-count quickstart describes. A count that matches part for part is right. A shift total that lands near the truth can hide two errors that cancel, and stamping lines get their own walkthrough in how to monitor stamping presses.