Skip to main content
Question

Clarifying License Cost Modeling: TCO Extension vs IT Component–Application Link

  • November 5, 2025
  • 2 replies
  • 63 views

Hi everyone,

I'm working on cost modeling in LeanIX and I have a question regarding how to best represent license costs—especially in cases where a shared technology platform (e.g., SAP) supports multiple business applications.

Context:

  • SAP licenses are purchased centrally, but used across several applications (e.g., Finance, Procurement, HR).
  • In LeanIX, I’ve already entered these costs on the IT Component–Application relation, since the licenses are tied to the SAP component.
  • The Application TCO extension also allows me to enter license costs directly on the Application fact sheet, but this creates a duplication of cost data (TCO doesn’t use IT Component-Application relation costs)

Questions:

  1. Should shared technical costs like licenses be entered in the TCO extension at the application level, or is it more appropriate to model them on the IT Component–Application link when the licenses are centrally managed and technically scoped?
  2. I know the TCO extension supports reporting costs per organization, and ideally I’d like to model both costs per organization and costs per provider. Is there a recommended way to do this without duplicating data?

I’d like to avoid double-counting while staying aligned with TCO and TBM principles. Any best practices or guidance on how LeanIX recommends handling this kind of scenario would be greatly appreciated.

Thanks in advance!

2 replies

Jim Harry
  • Sophomore
  • 5 replies
  • November 6, 2025

We haven’t started this yet, but I’m interested in this as well.  I’d love to apply costs at the licensed component level and be able to apply a % based on usage or something similar. 


GiannisAnt
Forum|alt.badge.img+1
  • Veteran
  • 92 replies
  • November 6, 2025

I heard from a colleague that went to Hague that there are some changes coming regarding cost modeling.

So maybe hold your horses a bit.