Quote:
Originally Posted by horseman
If any fool took your request seriously and started scrapping all the legacy Hub inventory without first ensuring the new Hub vendors had the ramping capacity to supply the shortfall
|
that is what planning is for and you would obviously ensure you had secured enough stock should you decide to embark on such an endeavour. That being said, it obviously how Vm choose to operate because every rollout turns into a fiasco and everyone gets pushed back at least once. You are not telling me that every part or every tech in every area has a problem which requires dates be pushed back by at least 3 months. The planning problems are systemic are lie higher up.
Quote:
Originally Posted by horseman
That's assuming the board accept the CAPEX increase hit on bottom line for the 9 Million Hubs
|
if they are already planning to buy new hubs why oh why are they still buying shub1s when they must be able to get the shub2s for the same price?
Quote:
Originally Posted by horseman
+ replacement for existing 4.9M users)  pmsl.... |
who said anything about replacing every single shub? I said new installs and swaps (i.e. for tech visits). If you are telling me every customer needs a tech visit then something is wrong. It is a progressive approach which you can plan for buy looking at the current call out rate. If you need to do a swap why would you replace a shub1 which is 6 years old with another shub1. Do yourself a favour and replace it with a shub2ac or shub3 and you are reducing potential problems in the future and the customer is happy because they think they are up to date with the latest technology.