Build a Configuration Management Database (CMDB)
Create a design that fits your needs.
Bigger isn't always better. Many organizations recognize the benefits of a CMDB, but assume that only a complex, expensive system will deliver measurable value. Most organizations struggle to design an effective CMDB that can be created and maintained for a reasonable cost.
Your Challenge
Wasted time and resources, running and maintain an overly complex system:
- Scope is too wide
- Too many levels
- Too many attributes
Value/Benefits of the CMDB are not realized, due to poor design:
- Relationships are non-existent
- Relationships are too simplistic
- Relationships are too complex
Cost of implementing a CMDB is prohibitive, due to:
- Poor design
- Poor management
- Inappropriate tool choice
Our Solution
- Make the case for designing a CMDB.
- Choose an appropriate CMDB design type.
- Identify Business requirements.
- Define the scope and depth of the CMDB and identify the relationships between configuration items.
- Obtain approval for your CMDB
Talk to our analyst about this research
This research isn't live yet, but if you would like to speak to someone about this topic early, we're happy to connect you with an analyst.
Book an Analyst CallIf you are a media professional who would like to cover this research upon its release, please contact pr@infotech.com.
