Skip to main content

Is it time to ask your vendors these 21 tough questions?

If you want to simplify support and get better performance from your infrastructure at lower cost, these are the tough questions you should ask your vendors about their support plans.
  1. Can you support a multi-vendor environment?
  2. Can you support multiple technologies?
  3. Do you offer a single contract to cover all assets?
  4. Is diagnosis time included in your SLA?
  5. Can you provide support in numerous local languages?
  6. Do you apply patches and configure replacement equipment for us?
  7. Do you stay on site until service is restored?
  8. Do you invoice in all our local currencies?
  9. Can you offer a single management portal giving me visibility of my whole estate?
  10. Can I vary the level of service on certain assets if they’re mission critical?
  11. Do you keep an archive of all our configurations settings to speed up restoration?
  12. Do you use automation tools to perform MACDs faster and more accurately?
  13. Do you proactively find the root cause of problems to avoid future incidents?
  14. Will you keep configuration items up to date with version updates and patches?
  15. Will you co-ordinate with any third parties on our behalf?
  16. Will you provide a senior engineer who knows our environment to act as an escalation point?
  17. Will you do proactive polling to avert availability and capacity issues?
  18. Do you provide a Service Delivery Executive to handle operational and commercial issues?
  19. Do you offer automated asset tracking and analytics to improve configuration management and patching?
  20. Can you integrate your service management system with ours and all the other vendors in our estate for automated ticket exchange?
  21. Can you give us a roadmap for service evolution as we move towards a totally programmable hybrid IT environment?
Read the blog post over at Dimension Data here.



Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi