What are 3C's in Cmdb?

[Shreya Wani]

Hi @--oooo-- 

Here is what the 3 C's in CMDB mean which are required to monitor the health of the CMDB data - 
1. Completeness - Using the recommended and required metrics, it ensures that the Configuration Items (CIs) are populated with necessary data.

2. Correctness - By checking the duplicates, orphans, and staleness metrics, it measures that the CMDB CIs are up-to-date and accurate with minimal to no duplicates.

3. Compliance - Using the audit metrics, it refers that the CMDB CIs are configured as expected and meeting the desired state expectations.

For further information, check out this product documention - 
https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/co...

Thanks,
Shreya Wani

[Sai Shravan]

Hi @--oooo-- ,

The 3C's in CMDB stand for Completeness, Correctness, and Compliance. Here's a brief explanation of each:

1. Completeness: This refers to the extent to which all relevant configuration items (CIs) and their relationships have been identified and recorded in the CMDB. It's important to ensure that the CMDB contains a comprehensive and accurate representation of the IT environment it's meant to manage.

2. Correctness: This refers to the accuracy and consistency of the data in the CMDB. It's important to ensure that the data is correct and up-to-date so that decisions based on that data are reliable.

3. Compliance: This refers to adherence to established standards, policies, and regulations governing IT service management. It's important to ensure that the CMDB is in compliance with these requirements to minimize risks and ensure accountability.

Reference Doc : https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/co...

Regards,

Shravan

[Suggy]

Completeness is a measure of whether required and recommended data is present.

Correctness is a measure of data quality (duplicate, stale, orphan)

Compliance is a measure of actual values of specified fields against expected values as defined in template audits.

-------------------------------------------------------------------------------------------------------------------------

1. Completeness - Using the recommended and required metrics, it ensures that the Configuration Items (CIs) are populated with necessary data.

2. Correctness - By checking the duplicates, orphans, and staleness metrics, it measures that the CMDB CIs are up-to-date and accurate with minimal to no duplicates.

3. Compliance - Using the audit metrics, it refers that the CMDB CIs are configured as expected and meeting the desired state expectations.

[Harish Bainsla]

Hi @--oooo-- 

• Completeness:

  This refers to whether all the necessary and required data is present for each Configuration Item (CI) in the CMDB. It ensures that critical information is not missing.

  • Example: A server CI should have details like its operating system, hardware specifications, and associated applications. If any of these are missing, the CI is considered incomplete.
• Correctness:

  This focuses on the accuracy and validity of the data within the CMDB. It ensures that the information is up-to-date and free from errors or inconsistencies.

  • Example: A server's IP address in the CMDB should match its actual IP address. If they don't match, the CI is considered incorrect.
• Compliance:

  This refers to whether the CIs in the CMDB adhere to established standards and configurations. It ensures that the CMDB reflects the desired state of the IT environment.

  • Example: If there's a policy that all servers must have a specific security patch installed, the Compliance metric would verify if the CIs representing those servers show that patch as installed. 

  for more details watch below video 

  https://youtu.be/nnWVCqi8pIw?si=Mvd4K-S99NVX2jaf

  if my answer helps you mark helpful and accept solution