Configuration Management Database (CMDB) - Revision history

User at 22:56, 7 December 2022

2022-12-07T22:56:11Z

Show changes

User at 22:54, 29 November 2022

2022-11-29T22:54:21Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T14:48:29Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 16:27, 27 January 2021

2021-01-27T16:27:24Z

User at 16:25, 27 January 2021

2021-01-27T16:25:33Z

User at 16:23, 27 January 2021

2021-01-27T16:23:01Z

User at 16:22, 27 January 2021

2021-01-27T16:22:22Z

User at 16:21, 27 January 2021

2021-01-27T16:21:10Z

User at 18:07, 7 September 2019

2019-09-07T18:07:12Z

User at 18:06, 7 September 2019

2019-09-07T18:06:29Z

@@ Line 151: / Line 151: @@
 **Possible hard benefits: Improved assessment of performance to increase effectiveness and decrease expenses
 **Possible soft benefits: Increased user approval rates through quality service of highest quality
-*Contract Management: The CMDB delivers essential [[statistics]] about how to efficiently accomplish an agreement with a service client. Such info comprises of real performance traced against agreed upon [[goals]], bills and expense particulars, contract time period, and extension information. This information is willingly accessible for incident-by-incident contract management as well as overall performance.
+*Contract Management: The CMDB delivers essential statistics about how to efficiently accomplish an agreement with a service client. Such info comprises of real performance traced against agreed upon [[goals]], bills and expense particulars, contract time period, and extension information. This information is willingly accessible for incident-by-incident contract management as well as overall performance.
 **Possible hard benefits: Decreased expenses through more active management
 **Possible soft benefits: Clear & transparent client relationships

@@ Line 128: / Line 128: @@
 source: OpsCentre
-Slicing and dicing these data can then also help not only with IT support and troubleshooting, but also with business intelligence insights into the interactions between IT and the rest of the organisation. These advantages however come at a price. The CMDB system must be acquired, and constantly updated and maintained to ensure that the data mirror exactly the real state of the assets. The change in IT that could give an extra boost to the use of configuration management databases for IT asset management and more is DevOps. Highly automated, DevOps relies on different software modules for integration, testing and deployment of new applications and also relies on the correctness of the application components from one end of the DevOps life cycle to the other. In the same way that a CMDB can be used for auto discovery of IT assets in general, it can also serve to automatically discover new DevOps code at different stages and to check that the version of such code corresponds exactly to official design and deployment specifications. The net effect on CMDB solution usage remains to be seen.
+Slicing and dicing these data can then also help not only with IT support and troubleshooting, but also with business intelligence insights into the interactions between IT and the rest of the organisation. These advantages however come at a price. The CMDB system must be acquired, and constantly updated and maintained to ensure that the data mirror exactly the real state of the assets. The change in IT that could give an extra boost to the use of configuration management databases for IT asset management and more is [[DevOps]]. Highly automated, DevOps relies on different software modules for integration, testing and deployment of new applications and also relies on the correctness of the application components from one end of the DevOps life cycle to the other. In the same way that a CMDB can be used for auto discovery of IT assets in general, it can also serve to automatically discover new DevOps code at different stages and to check that the version of such code corresponds exactly to official design and deployment specifications. The net effect on CMDB solution usage remains to be seen.
 == CMDB Challenges<ref>The Top Five CMDB Challenges [https://www.blazent.com/top-5-configuration-management-database-challenges-2017/ Blazent]</ref> ==
-While not particularly highly visible, a well-managed Configuration Management Database (CMDB) provides organizations with tremendous value. In addition to this value, a CMDB requires an organization to take responsibility for keeping it fit-for-purpose. Hewlett Packard Enterprise (HPE) sponsored a leading analyst firm to poll 100 IT executives on CMDB and discovery tools. The most interesting findings on CMDB challenges are listed below:
+While not particularly highly visible, a well-managed Configuration Management Database (CMDB) provides organizations with tremendous value. In addition to this value, a CMDB requires an [[Organization|organization]] to take responsibility for keeping it fit-for-purpose. Hewlett Packard Enterprise (HPE) sponsored a leading analyst firm to poll 100 IT executives on CMDB and discovery tools. The most interesting findings on CMDB challenges are listed below:
 *Reconciling data between multiple discovery tools or databases: A CMDB is a great place to consolidate information, as multiple business functions, including IT services, operations and asset management use a CMDB. Since most CMDBs are only populated using discovery tools, this data must be verified and augmented using multiple data sources to make it useful to all relevant functions.
 *Achieving accurate discovery in dynamic environments (clouds, containers): Virtual, cloud and containerized systems can exist for short periods of high demand, during which their existence must be extracted from log files. These virtual systems must have their configurations verified for billing, software license use and security vulnerabilities, similar to physical servers.

@@ Line 8: / Line 8: @@
 source: [http://adaptivedynamics.co.za/configuration-management-database-mobi/ Adaptive Dynamics]
-Configuration Management Database (CMDB) is an integral part of IT Service Management (ITSM). It is a repository that stores information about [[Configuration Item (CI)|configuration items (CIs)]] throughout the service lifecycle. It also describes the attributes & relationships between those CIs. As described in ITIL, CMDB is the fundamental component of the [[ITIL (Information Technology Infrastructure Library)|ITIL]] [[Configuration Management (CM)|Configuration Management]] process. Also, it also helps to understand the relationships between the components of a system and track their configurations. The Configuration Management Database (CMDB in ITIL) also coordinates with Incident Management process for receiving updates on replaced components that need to be updated in the database. The minimum number of attributes and data that the CMDB should stores are as follows:
+Configuration Management Database (CMDB) is an integral part of [[IT Service Management (ITSM)]]. It is a repository that stores information about [[Configuration Item (CI)|configuration items (CIs)]] throughout the service lifecycle. It also describes the attributes & relationships between those CIs. As described in ITIL, CMDB is the fundamental component of the [[ITIL (Information Technology Infrastructure Library)|ITIL]] [[Configuration Management (CM)|Configuration Management]] process. Also, it also helps to understand the relationships between the components of a system and track their configurations. The Configuration Management Database (CMDB in ITIL) also coordinates with Incident Management process for receiving updates on replaced components that need to be updated in the database. The minimum number of attributes and data that the CMDB should stores are as follows:
 *CI Unique Identifier or Identification Code
 *CI Name or Label (often, both, long names and short names)

← Older revision		Revision as of 16:23, 27 January 2021
Line 35:		Line 35:

	== Implementing CMDB<ref>Implementing a CMDB in 7 steps [https://www.beyond20.com/blog/draft-how-to-build-a-cmdb-in-7-steps/ Beyond20]</ref> ==		== Implementing CMDB<ref>Implementing a CMDB in 7 steps [https://www.beyond20.com/blog/draft-how-to-build-a-cmdb-in-7-steps/ Beyond20]</ref> ==
−	*Build a Logical [[Data Model]] of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the [[Service Asset and Configuration Management (SACM]] process. The logical model defines the scope of SACM activities. In other words, the logical model explains how deeply the organization would like to trace SACM relationships. For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces). At the other extreme, SACM could trace relationships down to the workstation level.	+	*Build a Logical [[Data Model]] of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the [[Service Asset and Configuration Management (SACM)]] process. The logical model defines the scope of SACM activities. In other words, the logical model explains how deeply the organization would like to trace SACM relationships. For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces). At the other extreme, SACM could trace relationships down to the workstation level.

← Older revision		Revision as of 16:22, 27 January 2021
Line 35:		Line 35:

	== Implementing CMDB<ref>Implementing a CMDB in 7 steps [https://www.beyond20.com/blog/draft-how-to-build-a-cmdb-in-7-steps/ Beyond20]</ref> ==		== Implementing CMDB<ref>Implementing a CMDB in 7 steps [https://www.beyond20.com/blog/draft-how-to-build-a-cmdb-in-7-steps/ Beyond20]</ref> ==
−	*Build a Logical [[Data Model]] of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the [[Service Asset and Configuration Management (SACM]]) process. The logical model defines the scope of SACM activities. In other words, the logical model explains how deeply the organization would like to trace SACM relationships. For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces). At the other extreme, SACM could trace relationships down to the workstation level.	+	*Build a Logical [[Data Model]] of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the [[Service Asset and Configuration Management (SACM]] process. The logical model defines the scope of SACM activities. In other words, the logical model explains how deeply the organization would like to trace SACM relationships. For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces). At the other extreme, SACM could trace relationships down to the workstation level.

@@ Line 1: / Line 1: @@
 == Definition of Configuration Management Database (CMDB) ==
-Configuration Management Database (CMDB) is a centralized repository that stores information on all the significant entities in your IT environment. The entities, termed as Configuration Items (CIs) can be hardware, the installed software applications, documents, business services and also the people that are part of your IT system. Unlike the asset database that comprises of a bunch of assets, the CMDB is designed to support a vast IT structure where the interrelations between the CIs are maintained and supported successfully.<ref>Definition - What is Configuration Management Database (CMDB)? [https://www.manageengine.com/products/asset-explorer/cmdb-configuration-management-database.html Manage Engine]</ref>
+'''Configuration Management Database (CMDB''') is a centralized repository that stores information on all the significant entities in your IT environment. The entities, termed as [[Configuration Item (CI)|Configuration Items (CIs)]] can be [[Hardware|hardware]], the installed [[Software|software]] applications, documents, business services and also the people that are part of your IT system. Unlike the asset database that comprises of a bunch of assets, the CMDB is designed to support a vast IT structure where the interrelations between the CIs are maintained and supported successfully.<ref>Definition - What is Configuration Management Database (CMDB)? [https://www.manageengine.com/products/asset-explorer/cmdb-configuration-management-database.html Manage Engine]</ref>
-A CMDB contains the configuration items (CI) or information system components within an enterprise IT infrastructure. It helps identify the different components of an information system and their configuration and stores this data in the form of metadata. The CI stored by a CMDB can be any IT component from hardware, software, network and/or IS policies and documentations. Typically, a CMDB automatically detects all components/CIs within an IT infrastructure/environment and keeps track of changes as they occur. CMDB provides data about these components in an organized way, making it easier for an organization to review and evaluate the data.<ref>Explaining Configuration Management Database (CMDB) [https://www.techopedia.com/definition/4438/configuration-management-database-cmdb Techopedia]</ref>
+A CMDB contains the configuration items (CI) or [[Information System (IS)|information system]] components within an enterprise [[IT Infrastructure|IT infrastructure]]. It helps identify the different components of an information system and their configuration and stores this [[Data|data]] in the form of [[Metadata|metadata]]. The CI stored by a CMDB can be any IT component from hardware, software, network and/or IS policies and documentations. Typically, a CMDB automatically detects all components/CIs within an IT infrastructure/environment and keeps track of changes as they occur. CMDB provides data about these components in an organized way, making it easier for an organization to review and evaluate the data.<ref>Explaining Configuration Management Database (CMDB) [https://www.techopedia.com/definition/4438/configuration-management-database-cmdb Techopedia]</ref>
@@ Line 23: / Line 22: @@
 *Unify data through automation or federation, identify CI duplication, and correct exceptions.
 *Minimize costs and errors through reduction of manual input.
-*Provide clear views of CI relationships for Change, Incident, and Problem Management.
+*Provide clear views of CI relationships for [[Change Management|Change]], [[Incident Management|Incident]], and [[ITIL Problem Management|Problem Management]].
-*Support Asset Lifecycle Management.
+*Support [[Asset LifeCycle Management (ALM)|Asset Lifecycle Management]].
 *Provide the flexibility to scale in order to support additional CIs.
 *Establish and maintain relationships and application dependency mapping.
@@ Line 36: / Line 35: @@
 == Implementing CMDB<ref>Implementing a CMDB in 7 steps [https://www.beyond20.com/blog/draft-how-to-build-a-cmdb-in-7-steps/ Beyond20]</ref> ==
-*Build a Logical Data Model of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the Service Asset and Configuration Management (SACM) process.  The logical model defines the scope of SACM activities.  In other words, the logical model explains how deeply the organization would like to trace SACM relationships.  For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces).  At the other extreme, SACM could trace relationships down to the workstation level.
+*Build a Logical [[Data Model]] of the Service Asset & Configuration Management Process with Relationships: The first step in the process is to create a logical model of the [[Service Asset and Configuration Management (SACM]]) process.  The logical model defines the scope of SACM activities.  In other words, the logical model explains how deeply the organization would like to trace SACM relationships.  For example, at a basic level, it is possible to draw relationships between key services and the underlying infrastructure (hardware, servers, software, and interfaces).  At the other extreme, SACM could trace relationships down to the workstation level.