Skip to main content

Dear LeanIX’ers,

I would like to get some feedbacks from the community regarding the “best usage” of the sub-type Deployment of an application.

We are a large watchmaker group in Switzerland, made from many organizations, and the goal is to modelize the application landscape of the entire group with LeanIX.

We are not using the virtual workspaces, so that all the compagnies can see the complete application list already existing in the group.

When an application is used by several compagnies, we modelize it as “Parent - Children” Application / Deployment, so that each deployment have it’s onw business owner, business criticality, technical fits, etc… This makes particular sense when the application is running for each company it’s own instance on a virtual server.

But when we take cloud applications, I always hesitate to create a Deployment for each company, as it’s the same application, but can have different business owners (by brands), and therefore different levels of criticality, depending on the brands.

For instance : Microsoft Dynamics 365 could have different values and different results for each of my companies.
 

So … How to you deal in such cases in your (large) company ?

Thanks in advance for your comments and testimonial,

Best regards,
Michael

Hi Michael,

the LeanIX best practice is to only use deployments to represent multiple technical instances of an application in different environments, such as testing, staging, sandbox, quality assurance, and standby fallback environments. Have a look at our application and deployment modeling guidelines. We strongly recommend automating the creation and management of deployment fact sheets using Configuration Management Databases (CMDBs) and not to model them manually.

It sounds like in your situation, you don’t always have different technical instances. For those applications like SaaS, where the same instance is in use by multiple legal entities you could model them with just one application and visualize the different usages through relations to the organization fact sheet (formerly user group) or if you want to have it more explizit, create a dedicated application fact sheet for each.

The latter is something we do ourselves for the use case of application harmonization while we integrate into SAP. We leverage suffixes to the fact sheet name for identification (e.g., “ApplicationX LeanIX instance”, “ApplicationX Signavio instance”, “ApplicationX SAP instance”).

Reply


Terms & ConditionsCookie settings