The CMDB is a popular topic these days. Everyone needs it. Few can explain it. Fewer can justify it. Software vendors developed products to support the ITIL process for Configuration Management. Analysts use terms like "federation" and "reconciliation" to help explain the gaps and benefits. Despite this awareness, the adoption of a CMDB has not kept pace with the market. Here are some frequently asked questions and my answers about a CMDB. If you need more help, reach out to me here.
A Configuration Management Database (CMDB) tracks all physical and virtual assets and maintains them in one place. The elements of people, process, and technology integrate with the entire IT infrastructure. This ultimately provides one complete view of IT configurations that are easy to understand, track, and manage.
Think of the CMDB as a pyramid where you have your common data on the bottom that feeds up into your services and the business utilizing people, process, and technology - your customers. See a snapshot to the right.
A business service is the work that supports the distribution of the services of a business, whether it's physical or virtual. In terms of a CMDB, this is ranked as a middle tier. Underneath that, you have your common data and how that relates to your services.
Let's take HR business services for an example. When HR onboards someone, they may need to set the associate up with an email address, Salesforce, Workday, a workstation - essentially four different application services the user may consume. Once that user is set up, they are tied to those individual services, which is when we can see the universe of people that consume each of those services, from the business service layer on down.
Having multiple sources is fine – you don't want to put all your eggs in one basket. The idea of the CMDB is to aggregate data from multiple sources to have one single source of truth. If you're having trouble with this, please reach out to us so we can explore this further for your organization.
In order to migrate to ServiceNow, we need to take a look at your current tool, what fields and data we need to migrate, and makes sure that information holds value. Then evaluate that data as part of the ServiceNow system. Reach out to our team today for an evaluation.
In general terms, for any size organization, you'll want to know, at minimum, who is supporting each part of the CMDB. For larger organizations, it could be broken down into different regions or groups. For small organizations, it may be more about addressing those bare minimums and figuring out who is supporting each part of the CMDB. Depending on the organization and their maturity level, we can address this during implementation.
Successful ServiceNow implementations start with a comprehensive plan and follow the ServiceNow Implementation Methodology (SIM). The CAI approach begins with a strategy tailored to your business needs, focused on process improvement and organizational enablement. We have the expertise to maximize your ServiceNow investment and deliver your projects on time and on budget.
Depending on the state of your organization, we may recommend a reorganization. Realistically, we cannot reorganize your entire corporation overnight – it may take months. Our goal is to move as fast as we can without really impacting the business. When CAI goes into implementation, we encourage our customers to take the crawl-walk-run approach.
Contact CAI, a ServiceNow Elite Partner, and we can further evaluate the need for reorganization in your company in order to implement a CMDB.
CAI offers CMDB Healthcheck Services to help our customers achieve significant improvement.
Bottom line: You "don't know what you don't know" until you know. Let us review your current state and we'll let you know what's going on. Contact CAI, and we can fill in the blanks.
If your CMDB is healthy and ongoing, take a look at your services. How do those services relate to your common data?
You have the common data of the CSDM built, but now you need to build some barriers – that's your application layer. We can then look at your business capabilities and how to best conceptualize everything under one roof.
CAI follows ServiceNow's best practices implementation methodology. We provide a project team consisting of an Engagement Manager and Senior Technical Subject Matter Expert, among others. We conduct a formal workshop to define requirements and address any challenges or roadblocks upfront. We then build implementation plans. Our normal project timeline is around a 2–3 month approach. Of course, this all depends on your organization's adoption of the CMDB.
Last year a financial services company refined their ServiceNow environment by implementing ServiceNow's Discovery and ServiceMapping modules. This company's IT environment includes 100,000 devices and 5 core enterprise applications. They needed an updated CMDB in order to monitor all of their assets. The client worked with CAI to retire their outdated tools and implement ServiceNow's ITOM tool, allowing them to map application relationships and improve visibility into application-level relationship data. Check out the solution and benefits here.