CMDB is not a given: Why CMDB is a Bad Idea for 95% of Organizations
Rob England explains that CMDB is not a given.
CMDB has actually been inflated and over-sold to hide its complexities and justify its huge costs. CMDB automates impact analysis by storing the service configuration in advance of when we might need it, so that when we do need it the information is quickly to hand. However this benefit may well be outweighed by some significant costs. He doesn't believe the vendors who say they can automate discovering the link between a true service entity and its components. The total cost of ownership of a CMDB is immense. A tool will not eliminate all the delays and errors in the impact analysis process. A CMDB will only reduce them not eliminate them.
It may introduce new potential for errors and even delays. And the moment staff lose confidence in its data, its improvements will fall near to zero. He estimates that about 5% of IT organisations truly need a CMDB. This makes CMDB into an obscure niche technology of interest to a few, not a core foundation of IT operations. So, he repeats, think twice, CMDB is not a given.
Want to learn about a totally new approach to configuration and change management?
Learn how Evolven redefines configuration and change management with its Change Monitoring solution. Take our tour or sign up for a free trial and see for yourself how Evolven eliminates outages. Really.