A relationship map helps you to visualize relationships between a base CI and other (related) CIs. This allows you to figure out the dependencies between the CIs and analyze the impact of Changes on the CIs. Using the map you can view the number of pending requests, changes, etc raised for different modules such as Assets, Business, IT Services, etc. This alerts you to initiate appropriate actions to progressively reduce the recurring issues faced by your organization.
This document walks you through the below topics:
A sample Relationship Map depicting different CIs and their relationships
In general, a Relationship Map is composed of nodes and their connections. The nodes are represented using a parent-child structure. In our context, the nodes are referred to as CIs and the connections are referred to as CI relationships. The relationship map also depicts cardinality (relationships in terms of numbers).
See the sample screenshot for more clarity.
Here`s a glossary of different terminologies used to interpret and understand a relationship map.
| Sl No: | Term | Description | Reference in the sample screenshot |
|---|---|---|---|
|
1. |
Base CI |
The CI from which the map begins and for which the relationships are defined. |
John |
| 2. |
Related CIs
|
All CI(s) extending from the base CI. The related CIs are depicted using a parent-child structure. |
Cisco_WebX_Service,Vulcan_Cluster, |
| 3. | Direct CI Relationship |
The relationship between a parent CI and a child CI. |
Cisco_WebX_Service “Includes” Cisco_WebX_Service is “Managed By” John |
| 4. | Inverse CI Relationship |
The relationship between a child CI and a parent CI. Note: The inverse relationship can be seen from the relationship map view of the child CI. |
Vulcan_Cluster is a “Member of” Cisco_WebX_Service. John “Manages” Cisco_WebX_Service. |
| Sl No: | Icon | Function |
|---|---|---|
| 1. | ![]() |
Click to zoom in and zoom out the map, respectively. |
| 2. | ![]() |
Mouse over the CI to view this icon. Click to view the child CIs. Click this again to hide the child CIs. |
| 3. |
Mouse over the CI to view this icon. Click to add more relationships. |
|
| 4. |
Click on any CI to view the CI details and associations. |
|
| 5. | ![]() |
Click to see the horizontal view of the relationship map. |
| 6. | ![]() |
Click to see the vertical view of the relationship map. |
| 7. | ![]() |
Click to see the force view of the relationship map. |
Once you reach the relationship map view, you will have three ways to view the relationship map; horizontal, vertical, and force. In all the 3 views the base CI and different related CIs are arranged in a parent-child pattern with relationships defined between them.
The three views of relationship maps are explained using the example CI John of People CI type.
The map has a left-to-right tree structure starting with the base CI.

The map is shown in a top-to-bottom tree structure with the base CI at the top.

This is the only map view that is customizable and you can reposition the CI nodes as needed.

To view relationships between any 2 CIs you should define them first. The relationships can be either direct or inverse.
Consider the relationship map of the CI John whose related CIs are Cisco_WebX_Service and Google_Azure_Service. Now, let's see how to interpret the direct and inverse CI relationships between the CIs John and Cisco_WebX_Service in the map.
In the below screenshot, John Manages Cisco_WebX_Service is a direct relationship.

In the below screenshot, Cisco_WebX_Service Managed by John is an inverse relationship:

You can perform the following actions from the map view:
You can add more CI relationships in addition to the existing ones.
You can view the pending requests and changes raised for the CI.