How to establish a CMDB
The creation of a CMDB across an organization’s enterprise has been highly scrutinized within the industry. Clearly the term CMDB is on the radar screen of many organizations that desire an end state that will satisfy compliance and continuity planning requirements. A significant percentage of the time this desire is fueled by the catalyst of political pressure which requires a CMDB to be developed in an illogical fashion which either provides segmented views into the enterprise or risks data integrity. Keeping that in mind, this repeatable model has been derived with the assumption that these pressures are trumped by logic and that the iterative approach ensures a more comprehensive CMDB.
The following working model is to logically establish a method to develop a CMDB.
The intent of this approach is first to focus on laying the proper foundation in order to ensure a comprehensive logical data structure. Then focusing on the linkage between the individual items that comprise a CMDB.
10 steps to creating a CMDB
- Document current state
- Develop a product portfolio
- Formulate Future State
- Formulate a Roadmap
- Position for Organizational Change
- Establish a Comprehensive Foundation
- Establish Data Integrity
- Integrate with the Enterprise
- Establish Linkage
- Perform Audits
Clearly, creating a CMDB offers unquestionable value to an organization. It is my opinion that the CMDB is not an end state but rather the inception of something greater. Any thoughts? Any opinions? Any interest for additional information on this subject? I hope so because I am in the final throws of developing a white paper on this topic which should be out shortly.
—–