I talked in an earlier post about the need to collect supply chain metrics and record your activities on a very detailed level. Reason being that you will need it in order to support you in turning performance indication into preventive actions. Now to part two and the importance of measuring what doesn’t happen!
…to get the low hanging fruits? After having rambled on about the risks with big bang automation projects, I found a soul mate in Cliff Holste at Supply Chain Digest. He builds a solid case for automating pieces of your warehouse processes rather than the entire operation. Why?
Hello again, and welcome to the second and last part of this blog post about software modifications, which we also plainly call mods.
You read in the previous Part One post that mods significantly drive implementation cost. Let’s look at the math again, further explore the mod drawbacks and then see what can be done…
Last time I started to warn for the pitfalls of (fully) automated warehouse operations. What I meant is that if you by design see it as a single black box system I sense a risk of déjà-vu of the inflexible AS/RS silos of the 70’s. Here you might say: No chance! With the flexibility of today’s equipment and integrated warehouse control system (WCS) we can adjust and tune that system both up and down to meet variations in demand.
│
