Parent - child Dependency in Connection Relationship
Being able to define an asset is connected to another asset in SDP is useful when you try to establish the impact of an incident or a change to other assets.
However, in the current feature of defining connections, it is hard to establish how assets are connected in a perspective of dependency
For example, we have desktops which is connected to Edge Switch 1. We can define the assets Desktop1, Desktop 2, etc... connected to Switch 1. Switch 1 is connected to Distribution Switch 2. If we look at the Assets Section of Relationship Tab for Asset Page of Edge Switch 1, we can see Desktop 1, Desktop 2, and Distribution Switch 2. It is hard to recognize the parent - child relationship between connections of the asset.
If we can classify a connection further as parent or child, we can easily establish a dependency of the asset to another asset.
Assuming this is a feature is available:
We can see define that Desktop 1 and Desktop 2 are child connections of Edge Switch 1. But Edge Switch 1 has parent connection to Distribution Switch 3.
Not only does it make easier to recognize the connections but also how assets not defined as connected to the asset may be affected by other assets.
In the example above, you cannot see the connection of Desktop 1 and Desktop 2 to Distribution Switch 2 because their Asset Relationship only displays they are connected to Edge Switch 1 but in reality, these desktops may be affected when there is an issue with the Service of Distribution Switch 2.
This feature requirement actually spans across the whole Service Life Cycle or across different ITIL Modules.
However, in the current feature of defining connections, it is hard to establish how assets are connected in a perspective of dependency
For example, we have desktops which is connected to Edge Switch 1. We can define the assets Desktop1, Desktop 2, etc... connected to Switch 1. Switch 1 is connected to Distribution Switch 2. If we look at the Assets Section of Relationship Tab for Asset Page of Edge Switch 1, we can see Desktop 1, Desktop 2, and Distribution Switch 2. It is hard to recognize the parent - child relationship between connections of the asset.
If we can classify a connection further as parent or child, we can easily establish a dependency of the asset to another asset.
Assuming this is a feature is available:
We can see define that Desktop 1 and Desktop 2 are child connections of Edge Switch 1. But Edge Switch 1 has parent connection to Distribution Switch 3.
Not only does it make easier to recognize the connections but also how assets not defined as connected to the asset may be affected by other assets.
In the example above, you cannot see the connection of Desktop 1 and Desktop 2 to Distribution Switch 2 because their Asset Relationship only displays they are connected to Edge Switch 1 but in reality, these desktops may be affected when there is an issue with the Service of Distribution Switch 2.
This feature requirement actually spans across the whole Service Life Cycle or across different ITIL Modules.