This documentation supports the 19.02 version of BMC Atrium Core.

To view the latest version, select the version from the Product version menu.

Relationship classes in the Common Data Model

The following table describes the BMC_BaseRelationship relationship class and its subclasses in the Common Data Model (CDM). Most relationship classes have subclasses that help further define a relationship. These subclasses, which are all categorization classes, can have additional attributes, but most often they further define a relationship only by using different Configuration Item (CI) classes as their members.

 Relationship classes in the Common Data Model




As the superclass for all other relationship classes, BMC_BaseRelationship is key to the design of the CDM. Though you are unlikely to create any instances of this class, you can use its form as a single place to query all relationships. Relationship classes inherit the attributes of these classes. In addition to the attributes such as Name that you populate for all relationships, BMC_BaseRelationship contains the core attributes such as InstanceId, and ClassId that are populated automatically by BMC Atrium CMDB. It even includes several display-only attributes for which values are set temporarily and then discarded.


Used to define composite objects such as a computer system, which is made up of a computer system instance, a disk drive instance, monitors, software, network cards, and so on.


Describes configuration items that are dependent on each other. This relationship can be used to define application dependencies, such as a particular program that is dependent on an application server and database for it to run.


Relates any configuration item to a physical location in your environment.


Used to define groupings of instances in a logical manner. This is used to define network topology, or to define the set of configuration items that make up a business process or service.


Represents impact relationships between any CIs.
Note: BMC_Impact is deprecated. To indicate an impact relationship, instantiate any other relationship class and set the HasImpact attribute to Yes. This strategy reflects the fact that members of any type of relationship can impact each other.


Establishes relationships between a parent virtual machine (VM) and its child VMs. For example, If you have a VM named win2k-vm1 and a clone of that VM named win2k-vm2, the win2k-vm1 VM is the parent and the win2k-vm2 VM is the child.

Was this page helpful? Yes No Submitting... Thank you