Wrong image provided by ServiceNow? How to read the relationships of CSDM tables?

[Suggy]

How to read the relationships of CSDM tables from the image?

(case i) Left CI class + ::rel type on right + right CI Class.

or

(case ii) left CI class + ::rel type on left + right CI Class.

If I consider the 1st case (rel type on right)

Business capability - PROVIDED BY - Business application >>>>>>>>>which is CORRECT

Application - RUNS ON - Infrastructure CIs >>>>>>>>>which is INCORRECT

If I consider the 2nd  case (rel type on left)

Business capability - PROVIDES - Business application >>>>>>>>>which is INCORRECT

Application - RUNS - Infrastructure CIs >>>>>>>>>which is INCORRECT

PS - I can go to CI class manager and see but I cannot do it for classes. To save time, I relied on the official image but

its **bleep** confusing!!!

Is that image wrong or what?

[Suggy]

Anyone 🙂

[Jonathan Schnei]

What CI's are you trying to relate together that are not being populated automatically by discovery, the relationship is not explicitly prescribed by the CSDM, or the relationship is not suggested by ServiceNow?

ServiceNow has done most of the legwork for this, but there could be specific use cases that are missed. Luckily, the framework is designed in a way that you can adapt it as needed. We can help advise on specific use cases you may have, but if you are adapting or creating relationships between CI's that are not automated, prescribed, or suggested by SN, that is also OK. Of course, be sure you document internally and apply consistently. For any of the relationships that are not automated/prescribed/suggested, there are no OOB workflows so the only risk to using the relationships framework in your own logical way to help describe your environment is the technical debt you may incur if that custom use case does not align with CSDM.

[Suggy]

Hi @Jonathan Schnei  I am not talking about the relationships populated by Discovery. 

I am talking about the relationships where logical CI's/conceptual CI's are involved.

[Jonathan Schnei]

@Suggy Of those that you are looking at, what CI's are you relating where the relationship is not explicitly prescribed by SN, nor suggested in the CI mapping?

As above, there is no 1 size fits all response here. If you are relating CI classes that SN has not prescribed OOB, then you can use whatever relationship best fits. Of course, document the use case, the reasoning, and be consistent; else, you can relate with whichever relationship you want and the system is designed to allow that.

[Suggy]

Anyone?