Hi @Ramel
- Parent-Child Relationship: This is the most straightforward hierarchical relationship, where the parent CI hosts or contains the child CI. This is typical for hardware and software components (e.g., server (parent) and its databases (children)), network systems, and application architectures.
- If your CMDB or ITSM tool provides predefined relationship types, use them whenever appropriate. Common types include “HostedOn”, “RunsOn”, “Contains”, etc., which can often fit the parent-child model.
- For example, a server (parent) may “Host” a virtual machine (child), or an application (parent) “Contains” its modules (children).
- The chosen relationship should clearly indicate how the parent and child CIs affect each other, especially for critical ITSM processes.
- For instance, knowing that an application (child) is “HostedOn” a particular server (parent) helps in quickly identifying the impact of a server outage.
Automate Where Possible: Use discovery and service mapping tools to automate the identification and mapping of relationships where feasible. This saves time and reduces errors.
- Review Relationships Regularly: IT environments are dynamic, with frequent changes. Regular reviews of CI relationships are necessary to keep the CMDB accurate and useful.
Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning
Thanks & Regards
Deepak Sharma
