TABLE OF CONTENTS Once a full-scale cycle counting program is in place, it should be expected that all items will be touched at some time, at least once, during the year by a cycle counter.
Ten consecutive days of 100 percent accuracy measured in the control group is a good sign that your process, at least for the control group, is now in control.
Let s look at an example of a cycle count schedule: There is a 1000- part-number overall database. The ABC stratification in this sample company (see Table 9-2) resulted in the following quantities per level:
| 1000 total items |
| 150 A items |
| 150 B items |
| 700 C items |
| Item Stratification | Counts per Year | Quantity of Items | Total Counts Required |
|---|---|---|---|
| A | 4 | 150 | 600 |
| B | 2 | 150 | 300 |
| C | 1 | 700 | 700 |
| Total counts for year | 1600 |
Here, A items might get counted once a quarter. This means cycle counters would have to count 150 items four times or 600 counts of A items in a year s time period. This would amount to 2.4 counts for A items per workday using 250 workdays as a base. Continuing with the math, a chart could be developed to schedule and understand capacity issues associated with the cycle counting process.
With 1600 counts required per year, the amount per day (1600 divided by 250) is 6.4 counts per day. This can now be scheduled and become part of...
