Skip to main content

Our organization has experienced significant growth through acquisitions, leading to a diverse IT landscape. We have multiple sites within the same country using different applications for the same business capabilities. To better manage and streamline our IT environment, we need to capture detailed information about these applications. Specifically, we are looking to gather the following details:

  1. Application Ownership: We need to identify who is responsible for each application. This includes understanding who pays the bills, who makes key decisions regarding the application, and who has overall ownership.
  2. Application Maintenance: It is crucial to know who is in charge of maintaining each application. This includes not only vendor-provided applications but also the internal administration tasks such as user management, permissions, and monitoring.
  3. Application Usage: We want to understand who the end-users of each application are. This will help us in mapping the application usage across different sites and business units.

We are seeking insights, best practices, and any tools or methodologies that can help us effectively capture and manage this information within LeanIX. Your expertise and experiences would be greatly appreciated.

I would highly suggest you review our meta-model-4 as I believe the new Organization subtypes can help you in this situation. Particularly the attribute Owner/user on the application → organization unit subtype.

The organization subtype comes with these subtypes, which you can setup using a hierarchy similar to how you would business capabilities or anything else.

  • businessUnit
  • customer
  • region
  • legalEntity
  • team

With these, they also have a location field where you can denote the locations if you please. I would reach out to your customer success manager as this is a rather simple solved use case using out of the box features. 

 

You can setup region hierarchy using the various countries applicable. Relate business units / teams to that said country factsheet as children so you can understand where they are located. Then associate the applications to applicable areas of usage and ownership using the OOTB attributes. For understanding who owns and manages the infrastructure this can be done via a multitude ways such as attributes on relations, tags and direct attributes depending on your organizations needs for views in reporting etc. 

Reply


Terms & ConditionsCookie settings