14th January 2009

Why Do You Want a CMDB? (Part 2 of 3 Part Series)

Why Do You Want a CMDB?
Part 2 of a 3-part Series about Configuration Management Database

We previously discussed what a CMDB is a repository of information related to all of the components of an information system.  After providing an overview of the CMDB, we now explore why an enterprise needs this analysis tool.  A CMDB serves as a single source of data, which is one of its greatest strengths.  Without a central repository for configuration information, IT organizations continue to work in silos and fail to align activities with business objectives.

Without the ability to manage and improve IT services, enterprises are adversely impacted in the areas of operations and service delivery.  Specifically, the capability to optimize IT services is needed by management to maintain cost effectiveness, enterprise control and flexibility and the maximization of business performance.As with any organization, the need for intra-company communication or with outside stakeholders is paramount.  Technological innovations in technology render yesterday’s solutions obsolete; an enterprise must effectively maintain the ability  to respond to customer preferences and changes in the legal and regulatory environment without disrupting operations.

The implementation of configuration management and its accompanying CMDB are vital for responding to the challenges of day-to-day operations. Companies need continuity and the seamless flow of activity on a daily basis.  CMDBs allow operational effectivness, cost efficiencies and a high overall quality of service.  Further, best practices and IT compliance mandate the need for CMDB, thereby ensuring compliance with multiple regulatory agencies, as well as legislation stemming from the Sarbanes-Oxley Act of 2002.  Both business practices and IT practices require a repository that will effectively handle and mitigate the challenges of operating in a global, highly complex workplace.  The CMDB positions and strengthens your company, making it one that is proactive to change, not reactive.

This entry was posted on Wednesday, January 14th, 2009 at 11:10 am and is filed under Asset Management, Change Management, Service Management. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.