Bottleneck Quotes
-
The new orders have changed the balance. We took more orders, which by themselves didn’t turn any resource into a new bottleneck, but they did drastically reduce the amount of spare capacity on the non-bottlenecks, and we didn’t compensate with increased inventory in front of the bottleneck.
-
There is a global shortage and that's a bottleneck for us.
-
Bottlenecks are usually at the tops of bottles.
-
What we had been doing many times was turning a nonbottleneck into a temporary bottleneck. This was forcing other work centers downstream from it to be idle, which reflected poorly on efficiencies. Now, even though we’ve recognized that non-bottlenecks have to be idle periodically, there is actually less idle time than before. Since we cut batch sizes, work is flowing through the plant more smoothly than ever. And it’s weird, but the idle time we do have is less noticeable. It’s spread out in shorter segments. Instead of people hanging around with nothing to do for a couple of hours, now they’ll have maybe a few tento twenty-minute waits through the day for the same volume of work. From everybody’s standpoint, that’s much better.
-
I say an hour lost at a bottleneck is an hour out of the entire system. I say an hour saved at a non-bottleneck is worthless. Bottlenecks govern both throughput and inventory.
-
The entire bottleneck concept is not geared to decrease operating expense, it’s focused on increasing throughput.
-
The key is in the hands of production. These techniques to manage the buffers should not be used just to track missing parts while there is still time, they should be used mainly to focus our local improvement efforts. We must guarantee that the improvements on the CCRs will always be sufficient to prevent them from becoming bottlenecks.
-
PHP is rarely the bottleneck.
