CMDB Systems: Some Key (and Surprising) Findings from Deployments
May 01, 2015

Dennis Drogseth
EMA

Share this

In writing CMDB Systems: Making Change Work in the Age of Cloud and Agile, we gained a lot by talking to deployments. In the spirit of our own recommendations for how to manage and optimize a CMDB-related initiative, our goal was to learn from reality more than just preach a series of best practices. What I’ve chosen to write about here are just a few highlights, following four key areas of interest:

■ Dialog, Communication and Stakeholder Planning

■ Architecture

■ Cloud

■ Agile

Start with: CMDB Systems in the Age of Cloud and Agile - Why We Wrote the Book

Dialog, Communication and Stakeholder Planning

Taking the time to engage stakeholders effectively is one of the bigger challenges in any strategic IT initiative, and one of the biggest single catalysts for CMDB success. One of the problems, of course, is time and energy to engage in something new, no matter how valuable, when most IT professionals are already overworked and trapped within their own treadmills.

The Hamster Scenario
“Cultural challenges were a big factor — in getting the silos to think about new ways of working together. Something like what I call the “Hamster Scenario” running around its wheel. You’ve got some processes in place and you’re used to those processes. When do you step back and change those processes? In other words when does the hamster get off its wheel and think it might move in other directions?” (a transportation/travel company from Chapter Eight)

Next is a comment in both the challenge and resolution category about dealing with a very different concern — too much enthusiasm, and with it, too many expectations:

Challenge/resolution: Trying to please everyone
“When we discussed the CMDB with different groups in our organization, each team got very excited about what they wanted to get out of our CMDB. But very quickly we could see that many of their priorities were at least a couple of years away from implementation. So everybody’s understanding of the scope was different. For instance, we had desktop people saying 'can I inventory my mouse? Can I inventory my keyboard and my monitor?' They all wanted to see those as CIs.

“But managing this wasn’t too difficult. I asked everyone two questions; first, ‘What is this equipment that you’re prepared to manage from day one through its entire lifecycle as a CI?’ And second, ‘Do you have the resources to manage these items as CIs once they get into our CMDB?’ If there were no costs associated with CI inclusion, then everyone would want everything included in the CMDB right at the start. But as soon as they begin to understand the costs, including update and data access costs, they viewed it differently.” (a manufacturer from Chapter Four)

Architecture

We spend a lot of time in the book looking at architectural challenges, including a very progressive technology landscape as it’s evolving to support more dynamic and complex service interdependencies. Below are just two perspectives, the first on service modeling, and the second on assimilating multiple data sets.

Service models vs. data models
“Our Service Model is based on ITIL’s definition, and it’s all about the processes, functions, services and technologies that we deliver to our customers. So therefore it’s a separate idea that can be applied to the data model. Our Global Finance team defines our business strategies company-wide. And these are of course not about a data model or technology. But that’s where we started, so we can trace everything we do back to those business services.” (manufacturer from Chapter Four)

Assimilating and reconciling many multiple sources
“Each discovery tool has its own idiosyncracies in terms of what it captures and how it works. This impacts both our ability to manage it and our ability to optimize our hardware and software asset investments in terms of utilization and licensing. With our integrated data analytics, we’re leveraging 35 different discovery tools in order to get a more cohesive 'golden record' for the CMS ... This includes desktop security, network management and administration, application dependency mapping, systems management and administration, asset management solutions, and BSM performance management, just to mention a few categories.” (a financial services company Chapter Nine)

Cloud and Agile

Since our book does its best to focus on the very current landscape of cloud and agile, I thought it fitting to end with two excerpts — one on each point. I think both are a bit surprising as well as insightful, but I’ll let you decide which might raise more eyebrows.

Cloud
“... the general idea is to leverage ADDM visibility for consistency across the cloud and hybrid cloud environments — so that you can identify servers that are not registered in your configuration management tools. Another example of the value of this type of visibility is keeping track of the Amazon Machine Images (AMIs), which can potentially lead to malware and other problems. There are over 30,000 community AMIs and not all of them are patched correctly, so if a developer decides to use one that’s not authorized it may cause problems. When that happens, ADDM can help to identify and remediate the problem.” (a software manufacturer from Chapter Fifteen)

Agile/ DevOps
“Before investing in the CMDB we were very fragmented in how we saved information. Some of it was in Visio, for instance. Some were in OneNote or in Excel. We also had a lot of Word documents — so it was difficult-to-impossible to get insight into impacts when we were about to make a change …

“At that time, development was a little bit ahead of operations in terms of maturity. Our operations organization was fairly siloed and hadn’t yet invested in best practices. We often had no clear idea what would happen if, for instance, we unplugged a server. Most of our change records there resided inside someone’s head … If somebody was sick at the wrong time, it could be very disruptive …

“But we did have some [scrum] best practices that had evolved in development for source control. So when we saw what a CMDB could do, we felt we had a chance to transform our way of working when it came to managing change.” (a mid-tier financial planning company from Chapter Fifteen)

All right, I’ll be candid. Probably the biggest single “revelation from the trenches” for me was this last — a development team purchasing a CMDB to support an agile environment using scrum and pushing it into operations.

The point being in these and other insights is that each deployment shares common challenges with other deployments, on the one hand; but is also distinctive on the other hand. The goal is, invariably, to find the best path for you — while learning from the many other voices of wisdom and experience available. And this was, perhaps, the single most pervasive "guiding light" in seeking out optimal content for our book.

Dennis Drogseth is VP at Enterprise Management Associates (EMA)
Share this

The Latest

November 15, 2018

We all know artificial intelligence (AI) is a hot topic — but beyond the buzzword, have you ever wondered how IT departments are actually adopting AI technologies to improve on their operations? ...

November 14, 2018

How can IT teams focus on the critical events that can impact their business instead of wading through false positives? The emerging discipline of AIOps is a much-needed panacea for detecting patterns, identifying anomalies, and making sense of alerts across hybrid infrastructure ...

November 09, 2018

In a recent webinar AIOps and IT Analytics at the Crossroads, I was asked several times about the borderline between AIOps and monitoring tools — most particularly application performance monitoring (APM) capabilities. The general direction of the questions was — how are they different? Do you need AIOps if you have APM already? Why should I invest in both? ...

November 08, 2018

There's no place like the web and smartphones for the holidays. With the biggest shopping season of the year quickly approaching, retailers are gearing up to experience the most traffic their online platforms (web, mobile, IoT) have ever seen. To avoid missing out on millions this holiday season, below are the top five ways developers can keep their apps and websites up and running without a hitch ...

November 07, 2018

Usage data is multifaceted, with many diverse benefits. Harvesting usage-driven insights effectively requires both good foundational technology and a nimbleness of mind to unify insights across IT's many silos of domains and disciplines. Because of this, leveraging usage-driven insights can in itself become a catalyst for helping IT as a whole transform toward improved efficiencies and enhanced levels of business alignment ...

November 06, 2018

The requirements to maintain the complete availability and superior performance of your mission-critical workloads is a dynamic process that has never been more challenging. Here are five ways IT teams can measure and guarantee performance-based SLAs in order to increase the value of the infrastructure to the business, and ensure optimal digital performance levels ...

November 05, 2018

APMdigest asked experts from across the IT industry for their opinions on what IT departments should be monitoring to ensure digital performance. Part 5, the final installment, offers some recommendations you may not have thought about ...

November 02, 2018

APMdigest asked experts from across the IT industry for their opinions on what IT departments should be monitoring to ensure digital performance. Part 4 covers the infrastructure, including the cloud and the network ...

November 01, 2018

APMdigest asked experts from across the IT industry for their opinions on what IT departments should be monitoring to ensure digital performance. Part 3 covers the development side ...

October 30, 2018

APMdigest asked experts from across the IT industry for their opinions on what IT departments should be monitoring to ensure digital performance. Part 2 covers key performance metrics like availability and response time ...