Mergers, acquisitions and the CMDB

The link between merger activity and the Configuration Management Database

Industry analysis by Beth Schultz, plus the latest news headlines.

The topic for this column combines two gorilla-level subjects demanding my attention: mergers and acquisitions on the one hand, and implementations of the IT Infrastructure Library’s Configuration Management Database (CMDB) on the other.

The former have occupied my attention because, well, they just “keep on keeping on” and because they’re certainly changing the enterprise management landscape. The latter is occupying my attention because Enterprise Management Associates is finishing up the second in a series of reports on the CMDB, looking at vendor and IT implementations.

The CMDB would be a common trusted repository of information involving configuration, topology and service relationships in support of a whole host of management disciplines and applications. Like mergers and acquisitions, industry CMDB initiatives are also beginning to change the enterprise landscape in some significant ways.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

The topic for this column combines two gorilla-level subjects demanding my attention: mergers and acquisitions on the one hand, and implementations of the IT Infrastructure Library’s Configuration Management Database (CMDB) on the other.

The former have occupied my attention because, well, they just “keep on keeping on” and because they’re certainly changing the enterprise management landscape. The latter is occupying my attention because Enterprise Management Associates is finishing up the second in a series of reports on the CMDB, looking at vendor and IT implementations.

The CMDB would be a common trusted repository of information involving configuration, topology and service relationships in support of a whole host of management disciplines and applications. Like mergers and acquisitions, industry CMDB initiatives are also beginning to change the enterprise landscape in some significant ways.

These initiatives are bringing together very distinctive communities of vendors, ranging from platforms and frameworks that, yes, will compete to be the center of the CMDB universe, to vendors focused on application service discovery, such as Collation, nLayers and Tideway; to service catalog vendors such as Centrata; to business service management vendors such as Managed Objects; to network and systems change and configuration vendors, such as BladeLogic, Opsware, Configuresoft and Ecora; and AlterPoint, Intelliden and Voyence. The initiatives will also touch help desk vendors, asset management vendors and lifecycle application development and planning vendors.

In the best of all possible worlds (don’t hold your breath for at least 10 years on all of this being real) - it will enable a modular, federated approach to integrating different types of data stores in a single, cohesive, trusted system for understanding the health and state of critical business services. And it will do this across changes in configuration, topological dependencies, asset and contractual information, customer information, policies (business, operational, security, compliance), and the health and availability of all service components.

This federated system should, moreover, be dynamically current, administratively light and support virtually all management disciplines and applications with consistent, current and accurate information. And it will allow for multi-brand choice in a modular way.

I did say in the “best of all possible worlds,” right?

Well, needless to say, a truly workable approach to the CMDB in the near term would require narrowing the focus to make “doable” chunks. It also would require collaboration among vendors (witness Collation working with Compuware, nLayers with Managed Objects, Peregrine with Mercury, etc.).

Most vendors supporting the CMDB direction are designing for multi-brand integration from the start, sensing that one of the best ways to lose the CMDB wars is to announce, “We can do it all!” This can be an affront to buyers (many of whom, nevertheless, do want to start with a single core brand) - as well as an R&D nightmare.

Schultz is a longtime IT journalist. You can email her or find her here.