Our hardware support contracts are expensive, and getting replacements has sometimes taken a lot of effort. How do you decide what coverage to keep and where spare equipment might be a better deal?
Are hardware support contracts still worth the cost?
Answers
Treat it as a risk decision, not just a count of support calls. Compare the contract cost with replacement parts, staff time and the cost of an outage. For critical infrastructure, a cheap spare is only useful if you can configure it and get services back within the time the business can tolerate.
Try a recovery test before dropping coverage. Check that the spare is compatible, the configuration is available and someone knows how to deploy it. A contract doesn't guarantee a smooth recovery either, so test the process even when you keep one.
Reply to this answer
Don't look at Cisco coverage as hardware replacement alone. Depending on the product and contract, software updates and help with upgrades can be part of what you're paying for. Check the specific entitlements before cancelling, especially for systems that are difficult to rebuild if an upgrade fails.
Reply to this answer
For a large workstation fleet, buying a few ready-to-deploy spares can make more sense than extended coverage on every machine. Run the numbers using the contract term, expected failures, replacement cost and help desk time, rather than comparing the warranty total with a single year's failures.
The catch is a bad model or batch. A handful of spares won't go far if lots of machines develop the same fault, so keep that risk in the calculation.
Reply to this answer
Support quality seems to vary quite a bit by vendor, coverage level and location. Look at your own case history: time spent troubleshooting, time to get approval and time until the correct part arrived. Those are more useful for renewal decisions than the service level printed on a quote.
c.591~torkiva:
Breaking out approval time from delivery time sounds useful. A fast shipment doesn't help much if getting the replacement approved takes weeks.
Reply to this answer
Add your answer
Answers are reviewed before publication.
v.813+ferrisocket:
Also check the actual replacement terms and local delivery performance. A promised response time and a working service restored are not necessarily the same thing.