2009/07/30

CMDB Relationships

We have been using different types of relationships inside the CMDB to link Configuration Items to one another. There is no limit to the types and number of these relationships and they can be fully customized to fit the client needs. The objective is to indicate which configuration items are related. For example, PC1 "is connected to" Printer3. Or License number XXX “is assigned to” SoftwareX.
These relationships will allow the user to know which items or services will be affected when a device presents a malfunction or any kind of problem. We think that the more information we have on the relationships field, the more accurate and precise the solution will be.
What do you think about creating these relationships?
Can you think of any crucial one that can not be let out?
Any ideas will be greatly appreciated.
Thanks!