LeanIX VSM

Overview and benefits

The integration with LeanIX VSM offers an automatic way to integrate data about self-built software discovered from your LeanIX Value Stream Management (VSM) workspace into your LeanIX Enterprise Architecture Management (EAM) workspace.

Benefits of the integration
Using this integration will allow you to:

1. Use aggregated information on your self-built software to drive decision making within EAM
2. Provide a seamless end-to-end view in EAM on your IT Landscape to support your business transformation use cases
3. Populate the Product Catalog in VSM with your self-built applications

How to activate VSM integration

Key steps to activate the VSM integration:

1. Go to the Administration area
2. Select Integrations in the left-hand panel. Here you have the possibility to configure and activate the VSM integration for your LeanIX EAM workspace.
3. Click on Configure to do so.

Configure the integration

Let's have a look on the configuration page: It is structured in several sections, the Basic Configuration, the Product Synchronization, the Open Source Software Risk Discovery and the Interface Discovery. Let us go through them one by one.

1. Setup the Basic Configuration

In this section, you can set the integration to active or inactive.

Also, you need to choose the VSM workspace you want to discover data from. The list will include all VSM workspaces from your account that your user has access to.

Finally, you may choose a VSM Tag that will be applied to any Fact Sheet that the integration will create in your EAM workspace. Make sure that the Tag you choose is applicable to all types potentially being created by the integration (e.g. Interfaces and IT Components).

2. Product Synchronisation

Next, you can configure which of your Applications of your EAM Workspace will be send to your VSM Mapping Inbox so that you can map them to the corresponding VSM Product.

First, you can choose any tag that is applicable to Applications. The integration will import any Application carrying this tag into your VSM Mapping Inbox. There, you can map it to a corresponding product. If you leave it empty, all Applications will be imported.
Secondly, you can also choose whether this specific synchronization is active or inactive.

As soon as an Application is mapped to a VSM Product, a field with the Number of Services, that are linked to this Product in VSM, will be updated on the Application Fact Sheet.

📘

Extension to your Application Fact Sheet Type

The integration will automatically create a number field for the Number of Services on the Application Fact Sheet Type in your EAM workspace.

3. Open Source Software Risk Discovery

As soon as you have some EAM Applications mapped to the corresponding VSM Products, you can use the integration to sync back the aggregated Open Source Software Risk for the Product in VSM into the EAM Application.

📘

Extension to your Application Fact Sheet Type

For this to work, the integration will make sure automatically that you have the required fields defined on the Application Fact Sheet Type in your EAM workspace.

Open Source Software Risk Extension

4. Interface Discovery

The integration can also help you to identify high-level dependencies between you self-built Applications. For that it analyses the Services & APIs that you gathered for their corresponding Products within VSM. Based on that, it will create up to two Interface Fact Sheets between any two of your self-built Applications that reflect whether at least one of the Services of the one Product consumes an API that is provided by a Service of the other Product, and potentially in addition also the other way around. If configured, the integration will apply the VSM tag to the Interface Fact Sheets.

5. Tech Stack Discovery

The integration allows you to discover the Tech Stack of your self-built Applications using the Tech Stack Catalog in VSM. For each of the Tech Stack items that support your corresponding Product in VSM, it will create an IT Component and link it to your Application Fact Sheet in EAM. If configured, the integration will apply the VSM tag to the IT Component Fact Sheets.

6. Saving & running the integration

After saving the integration, it will immediately start a synchronization of the workspaces. In general, such a synchronization runs at least once per hour. Additionally, the integration will react to changes on the involved workspaces to update the synchronized data right away.

As for the other integrations, the progress and the results (including warnings and errors) of the synchronizations of this integration will be tracked in the Sync Logging.

Resources

• Our VSM product & its documentation