A year ago, I wrote about setting up cycle counting for supply items in the Plex ERP tool crib. We covered why counting a little throughout the year works better than doing one large annual count, how to set up counts in Plex, and the basics of ABC classification and assigning ownership.
That post focused on how to count. This one is about what the count results can teach you.
Listen to this post
When the Counts Start Drifting
You set up the cycle types, define the parameters, and get Plex Mobile scanning. Counts happen on schedule—and then the same variances keep appearing.
A few carbide inserts are short. A drill index is over. The differences aren’t huge, but they keep coming back.
The first instinct may be to count more often. But if the same items repeatedly drift in the same direction, counting more frequently probably won’t fix the cause. It may simply confirm the pattern more often.
That’s because a recurring variance is often a process problem, not a counting problem. The count is doing its job: showing you where the process may be breaking down.
Read the Pattern, Not Just the Number
A variance is more than a difference between the physical quantity and the Plex quantity. Look at which way it goes, how often it happens, and where it occurs.
If the crib is short on carbide inserts every month, repeated miscounts are unlikely to be the whole explanation. The inserts may be leaving without an issue transaction, or the reorder point may not reflect actual use.
If counts are regularly over, items may be returned without being recorded, or material may be put away before the receipt is entered.
Occasional differences in both directions are normal. A repeated pattern in one direction is a signal to investigate. The cause is often somewhere upstream of the count.
Check Receiving First
If variances show up around recently received items, take a look at the receiving process before auditing the crib again.
Partial shipments, split boxes, rush orders, or a mismatch between the supplier’s unit of measure and the one used in Plex can all create problems. The effect may not become obvious until someone counts the item weeks later.
Plex can only track what has been entered. If the receipt is inaccurate or incomplete, the inventory record starts out wrong—and the shelf eventually shows the difference.
Look Closely at Issuing
The crib can become a bottleneck when maintenance needs a part quickly. A technician grabs a seal kit to get a machine running, planning to record the issue later. During a busy shift, “later” can become never.
This usually isn’t intentional. People are responding to an urgent need, and the transaction gets missed.
When fast-moving maintenance items are repeatedly short—especially after a maintenance window—check whether issues are being recorded consistently. A recurring shortage may point to a gap in the issuing process, not a need for more frequent counts.
Follow the Parts onto the Floor
Inventory can also go astray after it leaves the crib.
Consumables may build up in a work cell as informal “shadow stock.” Broken tools may not be written off. A container may move to a new location without the location being updated in Plex.
If items in the same zone keep drifting, look at how that area handles, stores, and records material. The count tells you where to look; observing the work can help you find out why.
Turn Count Results into a Diagnostic
To make the results useful, review the variance history in three ways:
- By item: Which items are repeatedly short or over?
- By zone: Are several items in one area drifting together?
- By direction: Do the same items tend to go short or over each cycle?
Items with repeat variances form a practical “leak list.” Zones with multiple variances form a “process list.” Then compare those patterns with what was happening at the time: receiving records, maintenance schedules, shift coverage, or periods when the crib was short-staffed.
Plex dashboards can help you review the results, while the habits from the original setup still matter: assign ownership by zone, use ABC classification to focus attention on important items, and keep a count schedule the team can sustain.
The key is what happens after the count. Don’t just adjust the quantity and move on. Treat a recurring variance like a signal to investigate the process. Find the cause, make a change, and check the next few cycles to see whether the pattern stops.
Keep Counting—and Start Listening
The goal of cycle counting isn’t only to make the quantity on the shelf match the quantity in Plex. That’s the starting point.
Over time, the results can show where your process needs attention: receiving, issuing, storage, or floor discipline. Your tool crib is producing useful information. The cycle counts have been recording it all along.
The next step is to read the patterns—and act on what they reveal.
