How to tie in a LeanIX IT Component

[jaguthrie]

We are trying to implement the CSDM model, and our Enterprise Architects use LeanIX.  We have the integration setup and working to push Business Applications from LeanIX to ServiceNow just fine.  The challenge I am trying to solve for now is they have some items listed in LeanIX as IT Components.  I know that these map to software or hardware models in ServiceNow. 

What I am unable to figure out is, how do I map these models to the Application Service they support in a way that reflects the dependency in both DPM and SOW correctly?  I would like to be able to see that the Application Service is dependent on that IT Component in DPM.  At the same time, if there is an issue with that IT Component, I want to see that the Application Service is being impacted in Service Ops Workspace.

[AJ-TechTrek]

Hi @jaguthrie ,

Great question! This is actually a common challenge when integrating LeanIX IT Components with ServiceNow, especially when you want the dependencies to reflect properly in:

* DPM (Digital Portfolio Management / Application Portfolio Management),
* SOW (Service Operations Workspace / Service Maps).

Here’s a detailed solution and best-practice approach

1. Understand what IT Components are in CSDM context
In LeanIX:
* Business Applications → map to ServiceNow’s Business Application (cmdb_ci_business_app).
* IT Components → typically represent software or technology products, which map to:
* cmdb_ci_product_model (model record)
* Or sometimes cmdb_ci child tables if you discover actual CIs.
In CSDM, the relationship is usually:

* Application Service → depends on → Application or Software Models / Technology

2. How to map IT Components to Application Service in CMDB
Goal:
* Application Service (e.g., Payroll App Service)
* depends on → IT Component (e.g., Oracle Database, Citrix Receiver, etc.)

Best practice:
* IT Components from LeanIX can be imported as:
* cmdb_ci_product_model records
* Or into a CI class like cmdb_ci_appl if they are actual deployable software
 Then use:
* Depends on::Used by relationship (cmdb_rel_ci table)
* Parent = Application Service (cmdb_ci_service)
* Child = IT Component (cmdb_ci_appl or model)
Remember: cmdb_ci_product_model is not a CI; it’s a model. For service dependency and impact to appear in DPM / SOW, you need the dependency on an actual CI (cmdb_ci_*).

3. Steps to implement

Step 1: Map IT Components to actual CIs
* Import LeanIX IT Components to:
* cmdb_ci_appl (for software)
* Or other cmdb_ci_* classes if needed
* Link these to their product models if appropriate

Step 2: Build the dependency
* Create cmdb_rel_ci records:
* Parent: Application Service (cmdb_ci_service)
* Child: IT Component CI (cmdb_ci_appl etc.)
* Type: Depends on::Used by

Step 3: Enable in SOW and DPM
* In DPM: the Application Service now shows dependency on IT Components
* In SOW: if the IT Component CI is impacted, SOW shows impact to Application Service (via the relationship)

4. Why not just use product models?
* Product Models (cmdb_ci_product_model) are templates.
* They don’t appear on service maps or DPM impact analysis.
* You must have actual deployed instances (CIs) to reflect live dependencies.

5. Automation / Integration
* Enhance your LeanIX integration to:
* Import IT Components as CIs (e.g., cmdb_ci_appl)
* Automatically create the Depends on::Used by relationship to Application Service (LeanIX may have metadata for this, or use scripting / IntegrationHub)

6. Validate the model in CSDM
Ensure:
* Application Service → mapped to a Business Application (Business Application maps to Business Capability)
* Application Service depends on CIs (IT Components)
* Follow CSDM "Design & Technical Service" layer best practices

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

[Sam Webb]

Hi,

There's an integration between LeanIX and Enterprise Architecture, in which LeanIX do articulate the data model. I'd use that as a starting point:

https://www.leanix.net/en/download/integrate-ea-and-itsm-with-the-leanix-servicenow-integration

EDIT: I see I didn't consider the question properly, sorry. 

If you have Models coming from LeanIX, you could associate them to CIs (given every CI has a Model ID field).  That functionally starts to bring together all the areas for the "Manage Technical" and "Design" domains and should be a starting point for your adventure!

Hope that helps!

Sam