Configuration Management
A couple weeks ago I wrote about the challenges of implementing a CMDB. As luck would have it, I’ve now been asked to help scope a CMDB implementation project. This project is being initiated for the purpose of supporting an upcoming data center move. This data center move is a large project that will impact many mission critical business systems.

In preparation for the project I’ve done some research on CMDB planning. I came across this article on ZDNet that I felt did a good job of summarizing the requirements of a CMDB:

What Do You Need From a Configuration Management Database?

The article focuses on technical requirements for a CMDB and is aligned with ITIL.

Of course, technical requirements and technology solutions are only half the battle. The real challenge will be defining processes that ensure the CMDB data is accurately maintained and easily accessible to those who need it. This will require coordinated efforts on the part of everyone involved in the following processes at a minimum:

• Service Management
• Incident Management
• Change Management
• Release Management
• Service Level Management

And will also cover specific technology departments including:

• Mainframe
• Midrange
• Database
• Network
• Servers
• Applications Development
• Facilities

Fortunately, the initial scope is limited to the CIs in the data center, but the long-term goal is for this to establish the foundation for an organization wide CMDB. Should be fun. I?ll keep you posted on the progress.

—–