CI Relationship Attributes

Community Alums
Not applicable

I'm looking to create relationship between CMDB CIs Business Process and Business Capabilities, which is relatively simple to do, however, in our business architecture concepts, a Business Capability may have more or less relevance to a business process. I'd like to capture that relevance (or impact) in addition to the fact that a Business Process may depend on a Business Capability, but I haven't yet found a way to capture additional attribute data to define those relationships. Is it poor practice to extend the cmdb_rel_ci table to capture specific attributes between CIs, to add additional attribute fields to the table, or to just create my own M2M reference table (which I'm concerned I'd lose seemingly import functionality of the CMDB)?

 

Use case is strongly associated with analytics of business processes, capability and applications.

1 REPLY 1

Niklas Peterson
Mega Sage
Mega Sage

Hi,

I would not recommend changing the cmdb_rel_ci table since it is such a foundational part of the CMDB.

Instead go with a new M2M table to manage the relationship between the two tables. Besides the two reference columns you can add one more column for your "relevance" value. Adding more than one extra column to the M2M will make it count towards your custom tables and that may affect your licensing. With just one extra column it is still exempted.

 

Regards,
Niklas