1. Enable CMDB Health Dashboard: By default, the CMDB Health Dashboard jobs are disabled. Need to enable it manually.

Health indicators such as duplicate CIs, required CI fields, and audits contribute to the calculation of overall health of the CMDB.

2. Utilize OOB CI Classes as much as possible: Utilize CI Classes that are provided as baseline with ServiceNow.  It is also best practice to not extend off of CMDB_CI.

3. CMDB attributes should be placed at the right level: Suppose you want to create Bios Date attributes on the Windows, Linux and UNIX class instead of defining the attributes in the Server class.

Best Practice: You should create Bios Date attributes in the Server class instead of creating three attribute on three different table.

4. Try to use a tree picker wherever it possible: For example you can use tree picker for location attribute. Rather than have the end user type in potentially duplicate or misspelled Locations use a tree picker.

5. Custom CMDB tables begin with “u_cmdb_ci”: While creating new classes (Tables), make sure the table name starts with “u_cmdb_ci”.

6. You should not alter Relationships: Relationships (in the table cmdb_rel_type) should remain baseline or out of box at all times. Changing them can break discovery and cause errors.

7. Avoid customizations: Attributes should leverage the out of the box attributes rather than recreating with custom attributes.

8. Applications should have a Business Owner assigned: Check to see that a Business Owner has been assigned to each Business Application.