Entity relationships

• Workspace tree: The hierarchical tree in the Workspace tab is used to organize entities into groups and sub-groups for ease of administration. The tree is built using parent-child relationships. For details about how hierarchies are used, see Hierarchies.
• Derived systems: A derived system can be used to represent calculated metric values from other systems. For example, a logical cluster (active/active or active/passive) can be defined as a derived system that is parent of the two cluster nodes. In this example, the CPU utilization of the derived cluster system is automatically calculated based on the CPU utilization of the nodes. For information about creating a derived entity, see Creating-and-viewing-entities.
• Reporting and data extraction: A report, view, or external data client can use relationships to extract related entities from BMC Helix Continuous Optimization. For example, a client can extract all of the systems that support a service. 

Relationships can be made between any two entities in BMC Helix Continuous Optimization, subject to these rules:

• A domain can be a parent of a system, or of a business driver, or of another domain.
• A system can be a parent of another system.
• A business driver can be a parent of another business driver.

The Workspace navigation tree shows all of the visible relationships that are currently valid. If an entity is a child of two different entities, then the child is shown twice in the tree, once under each of its parents. The Hierarchy tab of a particular entity lists all parents and all children (if any) for each hierarchy in which the entity is involved. The available relationship types are CONTAINS and USES. 

The parents entities are represented by CONTAINS relationship and child entities are represented by USES relationship.

For example, the relationship between a business service, service pool, and server at service pool level is represented as:

• Business service contains service pool
• Service pool uses server