A configuration management process and its supporting repository, CMDB or CMS, face the challenge of overlapping and contradicting data from sources across the enterprise.
The configuration management plan must include a way to merge and reconcile CIs to present a single point of reference or single source of truth.
Sex chat in greece - Updating processor
A configuration management tool can improve the organization's change-impact analysis, reducing the outages caused by production changes.
Configuration management combines valid service models, CI interdependency mapping and correlations made between CIs and requests for changes to help restore services faster during an outage.
The configuration management process identifies and tracks the individual CIs, their physical attributes and functional capabilities, and their interdependencies as related to the services they support throughout their operational life.
Such information typically includes the versions and updates that have been applied to installed software packages, and the locations and network addresses of hardware devices.
Configuration management is only aware of this server while it is associated with a given service or services.
If the service is discontinued, asset management will continue to govern the server's financial relevance, while configuration management will no longer have active reference to it.
The correlation between CIs and operational processes -- and how these support business services or affect key performance indicators -- can enable more informed business decisions.
Change management and configuration management are complementary, but not identical processes.
Configuration and asset management govern the items under different lifecycles.
For example, asset management manages a server from procurement through disposal.
Both demonstrate advantages over a static configuration management spreadsheet or text file that requires significant manual upkeep and cannot integrate base workflows and best practices.