|
March 1998 Volume 8 Number 3 Back to Basics: Cycle Counting Basics Revisited Initially, it was my intent this month to talk about problem-solving and the various terms associated with this process. However, this task will be delayed for one more month. The reason is due to an article that I recently received from Donald N. Frank, a consultant. At the 1997 APICS Conference I had a chance to talk with Frank, and one of the topics that we discussed involved that of cycle counting and ABC analysis (the topic of a past "Back to Basics" column). During this discussion, Frank introduced me to several issues not examined in our articles on this topic. I invited him to write an article on these issues. The following is the resulting column. It is being published because it introduces some very important concepts in a simple and straightforward manner. As for the articles on problem-solving, we will wait until next month. Now, for another view on ABC analysis and cycle counting. Steve Melnyk
By Donald N. Frank, CFPIM, CIRM
I am constantly being brought up short by people going through APICS basic training and then not looking beyond the knowledge transferred to analyze and question the business implications of decisions based on what was learned. Thus, I will address a number of basic questions.
Why do we cycle count? Cycle counting is the proven, accepted method of achieving high levels of inventory accuracy. Both the accounting folk who have to keep track of company assets and the material managers who have to plan product deliveries have a compelling need for truly accurate data.
What should we cycle count? Here the answers in the literature are somewhat murky. I suggest that purchased parts is a category that lends itself most to cycle counting. The balance of what follows is specific to purchased parts unless otherwise indicated. Whether subassemblies and finished goods should be cycle counted will be addressed later.
How do we differentiate between different classes of parts for cycle counting? The traditional method is to use ABC analysis and I agree with that. However, there are two caveats here:
1. ABC runs should not commingle purchased parts with subassemblies and finished goods because this will force all purchased parts down toward the "C" class, defeating the purpose of the analysis.
2. "A," "B" and "C" may not be the only classes used. You may want to include and establish tolerances for such classes as inactive parts, floor stock, samples and prototype parts, parts at suppliers, consignment parts, etc.
What tolerance levels should we apply? Here are some "typical" numbers. Are these numbers definitive? No. The only category where there is consistency in the literature is the "C" parts at 5.0 percent. The "A" numbers start at �0.0 percent and run to �1.0 percent. The "B" parts run from �1.0 percent to �3.0 percent. The key factor is not the actual percentages, but an understanding of what the numbers mean. For "C" parts, for example, if the tolerance is �5.0 percent, then the planning process must allow for the numbers to be off by 5 percent. Here is a good place for applying safety stock to cover the deviation. Perhaps a 3 percent safety stock on "C" parts, given that they represent from 5 to 10 percent of the total cost of inventory, is a small investment in ensuring a minimum of stockouts due to the "planned" discrepancy.
How often should we count? Here is a representative set of numbers gleaned from the literature:
This works very well with items with long dwell time in the manufacturing process. These times can be adjusted up or down depending on the individual business process. However, it is important to remember that the statistical rules which guide cycle counting assume that any realistic sample will be representative of the entire part population.
What should we do with a count discrepancy? First, all counts out of tolerance should be recounted, the source of the discrepancy determined and, if warranted, the records adjusted. However, what to do with counts in tolerance? Consider this case: A part is machined to �0.005 inch tolerance in its diameter. A part is inspected and is found to be -0.002 inch from the design center dimension. Would you spend any time in reworking (or rejecting) this part? Of course not.
Now, extend this logic to cycle counting discrepancies. A "C" part with �5 percent tolerance is counted and a 2 percent difference between the "book" value and the actual count is found. Would you (a) fix the record, (b) recount and then fix the record, or (c) accept the fact that the count is within tolerance and do nothing. The gut reaction, given my informal benchmarks, is to adjust the record. However, one should consider these critical points before accepting this:
Here are some other simple rules to help increase inventory accuracy:
At the beginning of this discussion, I indicated that one should separate purchased parts from the balance of the inventory population in doing ABC runs to establish both count tolerances and frequencies. I find it difficult to look at ABC tolerances for finished goods. These are the parts that have all the value added of labor and overhead, and therefore are all relatively expensive items when compared to purchased parts.
Rather than consider cycle counting these finished goods items, I would rather institute policies and procedures that ensure that all movements of finished goods into and out of the stockroom are really precise in counts. At a minimum, the tolerances for "A" parts should apply to all finished goods. The subassemblies should be separated into high-ticket items which carry the same rules as finished goods, and the balance should use "B" tolerance rules. The measure of successful management of finished goods and high-ticket subassemblies is that any spot check of inventory status should show these strict tolerances are being adhered to and therefore cycle counting need not be applied here.
In conclusion, cycle counting with good business practice has a real place in bringing purchased part inventory accuracy up to snuff. For finished goods and high-ticket subassemblies, higher discipline in managing "in" and "out" transactions should be the rule of the day.
|