Relationships are key to impact analysis, as relationships link CIs together. If you have associated CIs with people, then by using the Impact window in the CI Structure component, you can notify all of the affected people when a CI changes.
You need to create the relationship types that are relevant to your company. We recommend the following:
Is part of – When a CI (item A) is part of another CI (item B).
For example, a hard disk drive and a monitor can both be parts of a PC. A simple change to a CI will not affect a CI with a part of relationship. A complex change will affect related CIs. For example, changing the screen resolution of the monitor does not impact the PC – the PC is always available (a simple change). Changing the hard drive, however, cannot be done without making the PC unavailable (a complex change).
Arrows go in the direction of impact.
Is used by – CIs can be used by other CIs.
For example, a printer can be used by a PC that is not directly connected to it, but which has access to the printer using printer sharing.
Dependently linked to – A change to a CI impacts all of its children that are connected to it by a dependent connection.
For example, a printer with a dependent connection to a PC is impacted when the PC requires a change such as a new disk drive, because it cannot be used to print.
A change to a child CI does not impact the parent CI. Using the same example, removing the toner cartridge from the printer does not stop the PC from being used.
Independently linked to – A change to a CI does not impact all of its children that are connected by an independent connection.
For example, a segment of a network that is connected to the main LAN backbone can continue to work when the LAN backbone is unavailable. In the same way, changes to a child CI do not impact the parent.
Creating custom relationship types
Creating a configuration item structure view
Was this article useful?
The topic was:
Not what I expected