Implementing a CMDB without knowing why is like putting your life savings into the hands of an entrepreneur before they’ve told you their business plan. Defining and implementing a CMDB can be a long and expensive process & embarking on this journey without knowing “why?” will most certainly lead to failure. This article will outline the fundamentals of why a CMDB is important to your organisation but will more specifically determine the critical importance of having a resource that can understand your Why, or help you to articulate it.
Why is the CMDB Important?
The configuration management database, if implemented correctly can provide one database that gathers, manages and links information critical to every other major IT process. At the same time, a configuration item (CI) can be any IT component including software, hardware, documentation and personnel, there are millions of potential CI’s that could be included in the CMDB. It is therefore extremely important to understand why the business needs a CMDB in order to ensure that it is populated with good quality data that the business can rely on to improve processes.
CMDB Empowered Incident Management
If the focus of your CMDB is to empower your incident management process the business needs to ask itself a number of questions in order to avoid having an overpopulated CMDB that will inevitably increase incident times. CMDB’s often contain millions of CI’s that are not relevant to the critical needs of the business. The organisation, therefore, needs to establish what configuration items are critical to the business and why. This will enable you to build a CMDB that helps the team to respond to incidents in record time.
CMDB Empowered Change Management
The CMDB is very capable of empowering the change management process just as easily as it can cause unnecessary disruption to the business. The reason for this isn’t necessarily having good data vs bad data within the CMDB. Knowing the businesses wants it’s CMDB to focus on the change management process is a great start. This enables the business to understand that it needs to be able to grasp the properties and relationships between CI’s. The next questions that need to be asked are around what major changes occur in the business and which relationships should be mapped and why.
CMDB Empowered Risk Management
When considering how the CMDB could empower the risk management process the first thing that came to mind was: how do you decide what to put in the CMDB, surely everything is classed as a risk!? This confirmed two things to me; 1 – the CMDB should be very important in underpinning the risk management process and 2 – it is extremely important for the business to understand which processes are the most important and risk-averse in order to determine the data most needed to be discovered.
The Why Question
Many businesses will embark on implementing the CMDB because best practice says that they should. Suddenly you realise every department wants all kinds of data in for their own purposes. Sometimes the design process takes so long that the CMDB is out of date by the time it is implemented!
How do you solve this problem to ensure that you do not fall foul of these issues? Employ a specialist CMDB Implementation Consultant who can help the business to discover why they are implementing a CMDB and which business processes they are trying to empower. Can the CMDB truly underpin the entire enterprise? Yes, it can, but it is critical to understand what is most important to the business and why or you will undoubtedly end up with a CMDB that is overpopulated with bad quality data that hinders multiple processes instead of empowering them.
Momentum Consultancy Group understands the complex and important journey involved with implementing a CMDB. We also understand that employing the right resources are pivotal to the success of the project. If you are embarking on this journey and want to talk about employing a CMDB Consultant please contact us via LinkedIn, Email: firstname.lastname@example.org or call: 07880496714