I don’t want to mess up my CMDB – again!


If you are struggling with all the available data source options and feeling overwhelmed, you’re not alone. Many business leaders are wondering how they can prevent rework and data remediation.

There are many data sources to choose from, so narrowing this down is a key step in getting to compliance with your CMDB. Additionally, the risk associated with improper initial design and deployment can result in major remediation activities.

Regardless of a platform’s capabilities, having a partner that understands your end goals will ensure successful CMDB implementation. Cask can help you define success for your business.

A common issue we find with CMDB deployments occurs when business leaders do not define a strict foundation for requirements you can actually support when the platform of choice is live.

When I work with clients, we will clearly define trusted data sources, and how they will reconcile to enrich or create Configuration Items. Likewise, it’s critical that you as the client understand your options, and the gates that should be opened only when you can support the expansion of data. Supporting initial GoLive capabilities is not an end state, but they ensure a trusted baseline is in place. ITSM, ITOM, and SecOps all build upon this foundation.

To ensure continued success, scope only what your process can support. Define a parent data source (gold source) and secondary enrichment sources. Finally, sell your success by keeping a trusted CMDB.

Defining scope based on what you can support ensures the organization will actually use and trust the CMDB. Click To Tweet This state of CMDB data integrity typically leads to new opportunities for the enrichment of data in ongoing phases, leading to exponential benefits for teams involved in the process.

Menu