Have you been asked to implement a CMDB? Here are a few pointers for doing it successfully.
- Find the “low hanging fruit” where you will obtain the most benefit for the least cost. Implement that.
- Configuration Management should be focused on improving processes, not implementing a database. A database is the presumed tool, but you need to look at how your processes will be improved.
- The leading candidates for improvement include: Request Fulfillment, Incident Management, Change Management, Problem Management, Availability Management, and Capacity Management (not necessarily in that order).
- Configuration Management is not about building a database. Your CMDB can be a spreadsheet, if that provides the most benefit for the lowest cost. If necessary you can generate a more robust database later. However, see the next caveat.
- Maintaining the CMDB will be costly. This leads to two points: 1) make sure you understand what data you need and why, and 2) automate data collection as much as possible.
- Implement your CMDB in phases, in conjunction with Continuous Service Improvement.
Don’t expect your CMDB to include everything that it could conceivably contain according to ITIL. That would be too costly for the value provided to most organizations.