Create or edit a CMDB health orphan rule

Create an orphan rule to determine the percentage of orphan CIs in the CMDB. This sum is then aggregated into the correctness CMDB Health KPI, and weighed into the overall CMDB health report. Orphan rules are defined per class, and only a single orphan rule can be defined per class.

Before you begin

Role required: itil_admin (on top of itil)

About this task

In order for a CI to be considered an orphan CI, specify attributes that a CI must have, relationships that a CI should not have, or both. In the relationship conditions, you can either specify that the CI has no relationships, or a set of specific relationships that he CI does not have. An orphan rule can for example define that if a CI doesn’t have an owner or an asset, then it is considered an orphan CI.


  1. Navigate to Configuration > CI Class Manager.
  2. Select a class from the Class Hierarchy.
  3. On the right-hand side navigation pane, check Advanced, expand the Correctness strip, and click Orphan Rule.
  4. If an orphan rule exists for the selected class, double-click it to edit, or click New.
  5. Complete or edit the form.
    Table 1. CMDB Health Orphan Rule form
    Field Description
    Class The class for which the orphan rule applies.
    Attributes Attribute conditions that a CI must satisfy to be considered an orphan CI. For example, the filter conditions in which both the Assigned to and the Owned by fields are empty, will identify the matching CIs as orphans.
    Condition And/Or operation between the Attributes conditions and the Relationship conditions.
    Relationship The relationship conditions that a CI must fail in order to be considered an orphan CI.

    To specify that a CI must have no relationships, choose Any Relation and Any Class respectively.

  6. Click Submit or Update to save the rule.