Skip to main content

Hello everyone,

we are currently in the process of categorizing our IT components using the LeanIX Tech Category Catalog. However, we often encounter difficulties in finding the right categories for certain technologies due to the predefined hierarchy based on the TBM Solutions Layer. For instance, we created a custom tech category called "Operating Systems" with subcategories "Mobile OS", "Server OS", and "Workstation OS" to better fit our needs. Additionally, we developed a separate category for "Languages and Frameworks".

Since this approach diverges from the intended use of the catalog, I am curious about how others in the community handle these challenges. Do you adhere strictly to the catalog, adapt it to meet your specific needs, or create entirely new categories?

I appreciate any insights and experiences you are willing to share!

Best regards,

Julian

 Sorry, i wish I had an answer for you to share.  We are just adopting LeanIX now and I’m trying to import TBM Tech categories and getting errors that we exceeded hierarchy quota.  Glad you got the TBM imported, but we even do that fully?  strange

 

Hi @Keith Vargas ,

That error is due to the fact that the import is attempting to create a hierarchy deeper that the max defined in the Meta Model. You will need to increase the max level for the Fact Sheet type:

 

@JulianS: We have not extended the TBM Tech Categories that we started with. Yet. We may need to, but I’m hopping that the whole Tech Category will get some TLC by LeanIX in a not too distance future. This also has some impact in ServiceNow integration in case we decide to sync Tech Categories… Which one should be the source of true? We will have to look at the whole area soon, but we haven’t got to it yet.

Cheers.

 

Hello ​@JulianS 

We're just starting out with LeanIX and have the same question. I was actually looking for a category for operating systems. Could you tell me how you resolved this?

Hello ​@Javier Guajardo,

we decided to adjust the reference catalog to better fit our needs and internal technology landscape. We also chose to limit ourselves to two hierarchy levels, since the number of technologies we manage doesn’t require a deeper breakdown at this stage.

For example, we created our own category for Operating Systems under the parent category Infrastructure.

Here’s a quick look at our current tech categories:

  • Corporate

    • Corporate / Business

    • Corporate / Shared

    • Corporate / Workplace

  • Delivery

    • Delivery / Database

    • Delivery / DevOps Technology

    • Delivery / Languages & Frameworks

    • Delivery / Middleware & Integration

    • Delivery / Security & Compliance

    • Delivery / Server Technology

  • Infrastructure

    • Infrastructure / Data Center

    • Infrastructure / Network

    • Infrastructure / Operating System

    • Infrastructure / Storage

    • Infrastructure / Virtual Compute & Container

If a category becomes overloaded or too broad, we consider splitting it further. But for now, this setup gives us a good balance between structure and flexibility.

Hope that helps, feel free to reach out if you have more questions!

Hello ​@JulianS Thanks for your insight, it's been helpful.We've imported the TBM, but we're going to trim it down and surface it as needed. We're going to put the operating system in infrastructure like you, but I'm not sure if the database should also be in infrastructure under a "Software Base" category in infrastructure or something similar.…Or in Platform.Thank you very much.

Reply


Terms & ConditionsCookie settings