Hello,

personally I also have an extra subtype for the modules, e.g. SAP HR, SAP MM etc.

About the pricing:

Microservice fact sheets do not count for pricing.

Deployment fact sheets do not count for pricing, but they must not have direct relations to business capability or business context fact sheets.

Different instances usually = Different applications especially if a different instance refers to a different organization etc.

Environments = probably depending on your needs, do you want to capture IT or Development processes? Do you help possible integrations this way e.g. ServiceNow? Otherwise you can just add an environment field in the application fact sheet indicating any extra environments, so its values would be something like TEST,QA,DEV,STAGING etc., Do you want to monitor risk on non prod environments? 

So no clear answer here, I have seen several approaches

Versions = This is usually captured from the IT Components.

Hope this helped.

Hi ​@abhinavrajput, 

The Deployment, and Microservices subtypes would not count toward the total number of applications under your current LeanIX licensing model, since pricing is typically based only on the number of business applications. However, you still need to respect the fair use policy when using these subtypes, meaning you should avoid linking them to business contexts or business capabilities, to ensure they are not interpreted as business-relevant applications.

Regarding your second question: yes, by using these subtypes, you can still comprehensively map the relationships of these applications across the entire IT landscape. That includes linking to IT Components, Data Objects, Interfaces, and Technology Categories. The subtypes inherit the same relational possibilities as their parent Application Fact Sheet type, allowing you to capture a full and connected architectural view.