What is the issue? Let’s just take a (classic) VSM picture of a fictional example. These are hospitality and event applications in a municipality. The made VSM looks like this:<\/p>\n In this picture, the bottom right corner says: waiting time = 17.5 days. And I think that is incorrect.<\/p>\n That 17.5 days should represent the waiting time of one new product: from the time push production starts until the trip to the customer takes place. In terms of processing time, it is then the total waiting time plus the processing time of 68 minutes. How does this calculation come about? The total wait time is the addition of the indicated wait times. The different waiting times are calculated by multiplying the stock before a process step by the cycle time. To represent everything in days, we divide this time by 60×8. For example, the wait time before the “Check Request” step is:<\/p>\n P.S. For simplicity, things like changeover times and quality loss are excluded.<\/p>\n This calculation of total waiting time is incorrect because it does not take into account the bottleneck that exists in this process. The bottleneck is the process step with the longest cycle time and that is the “review request” process step with a cycle time of 20 minutes. By itself, it is true that the waiting time before purely the “check request” step is 2.6 days but because of the bottleneck, the stock for bottleneck accumulates. And all the stocks that still have to pass through the bottleneck only get through there in the frequency of every 20 minutes. So the total waiting time for a product coming in at the front end is the inventory times the cycle time of the bottleneck:<\/p>\n So better to calculate the wait times corresponding to the indicated inventories with the cycle time of the bottleneck. So e.g. the waiting time before the “Check Request” step is:<\/p>\n This then leads to the following picture:<\/p>\n And so this total waiting time of 25 days is substantially longer for a new product to be produced than the 17.5 suggested in the earlier picture.<\/p>\n One final comment. So far, we have not considered the client’s branch time. If we do, we see that the branch time is lower than the cycle time of the bottleneck. So the customer wants to receive the products at a higher rate than the process can deliver. So the customer is not satisfied. And no inventory is created at the back end of the process either. In the case where the branch time exceeds the cycle time of the bottleneck, the situation becomes different. The customer then wants to receive products at a slower rate than the process can deliver. In that case, one must count with the customer’s branch time to calculate the correct waiting time. The customer then becomes, in purely process terms, of course, the bottleneck.<\/p>\n<\/p>\n<\/div>\n<\/div>\n Want to learn more about Value Stream Mapping or our other services? Then contact us, using the form below or call us at 053 – 20 30 240<\/p>\n<\/div>\n [\/et_pb_text][et_pb_code module_id=”contactformulier” _builder_version=”4.4.7″]\n <\/p> ![\"\"](\"https:\/\/www.symbol.nl\/wp-content\/uploads\/2020\/07\/Thom_Luijben-2-277x300.jpg\")
Let me just start by reaching out to myself: for years I, too, made incorrect wait and lead time calculations and worse, trained others incorrectly in them. I adopted something I had been trained in by others, saw it in all kinds of Lean books and thought that was right but something gnawed at me.<\/strong><\/p>\n![\"Value](\"https:\/\/www.symbol.nl\/wp-content\/uploads\/2021\/02\/210209-VSM-Thom.png\")
<\/div>\n<\/div>\n
<\/div>\n
<\/div>\n
![\"Value](\"https:\/\/www.symbol.nl\/wp-content\/uploads\/2021\/02\/210209-VSM-Thom-1.png\")
<\/div>\nWant to know more?<\/strong><\/h3>\n
<\/ul><\/div>\n