IT Components subtype

The Subtype is customizable, for our organization, we have, 

-Chandra

Thank you for your quick replay

but in that case, if you have an application supported on LLM you would link direct to the IT Component? 

​@Wiam El Fatihi thank you so much for you complete and professional clarification. 

It makes a lot of sense! 

Could you also provide your feedback regarding the following points: 

1. Imagine that you subscribe a SaaS to a provider X, but that provider has his product in the AWS. 
   • Would make sense to have an IT Component of type SaaS with a Parent that would be an IT Component Service 
   • Example, display name IT Component SaaS:  Amazon Web Services Hosting AWS / XPTO Tableu

We just defined the provider of the hosting service, because there is a need for a legal report on that, otherwise we would just keep the SaaS it Component.

2. Imagine that you have an Hybrid solution (cloud specially reserve for the organization+ on-prem) 
   • Infrastructure (IaaS IT Components):
     • XPTO Cloud of the organization
   • Software (Software IT Components):
     • Database xpto
     • Software B
       • Require Data Center managing B (IT Component service) 
   • Hardware (Hardware IT Components)
     • Servidor A
       • Require Data Center managing B (IT Component service) 
   • Service (Hardware IT Service)
     • Data Center managing B (IT Component service) 
     • Implementação Software B

Thank you in advance for your help and support. 

Hi ​@monicaaugusto 

I'm glad I could provide a helpful explanation!  

1- I would avoid using the Parent/Child Rel in this case for a clean modelling and reusability purposes.  If “XPTO Tableau” is used by business users, plays a clear functional role in business capabilities, and needs to be linked to them, the recommended approach is to: 

• Define XPTO Tableau as a Business Application.
• Define XPTO Tableau SaaS as an IT Component (SaaS).
• Define AWS Hosting Service as an IT Component (Service) and link it to AWS as the provider. If reporting requires clarifying that the service is not directly provided by AWS, you can link it to the Provider X instead.
• Use the "relApplicationToITComponent"  to connect the Application to both IT Components.
• Use the "Requires" and "Required By" relationship between the SaaS IT Component and AWS Hosting Service to clearly indicate that XPTO Tableau SaaS depends on AWS Hosting to function.

If Needed you can also create a custom relationship such as "Hosted By" or "Runs On" instead of using "Requires/Required By". However, keep in mind that this may not work seamlessly across all reports.

2- Quick question regarding the scenario 2, Is the Database XPTO a managed cloud service or is it running in both the private cloud and the on-prem data center? 

Regarding the point 2. The Database XPTO is running in the on-prem data center. 

2. Imagine that you have an Hybrid solution (cloud specially reserve for the organization+ on-prem) 
   Cloud: 
   • Infrastructure (IaaS IT Components):
     • XPTO Cloud of the organization
       On Prem: 
   • Software (Software IT Components):
     • Database xpto
     • Software B
       • Require Data Center managing B (IT Component service) 
   • Hardware (Hardware IT Components)
     • Servidor A
       • Require Data Center managing B (IT Component service) 
   • Service (Hardware IT Service)
     • Data Center managing B (IT Component service) 
     • Implementação Software B

Would you map this way?