How to model different Functional Fit values per region when the same application + capability combination exists?

Hi ​@syed.aun,

Thanks for the post!  First, a question - to confirm, are you currently modeling the “Regions” you refer to in your original post as Organization fact sheets, categorized by the “Region” subtype we offer?  See screenshot below for context:

If you are not already doing so, our best practice would be to capture your Regions (i.e. NA, APAC) as Organizations fact sheets of the Region subtype.

Modeling in this way will allow for you to relate multiple regions to 1 given App, if you’d like (really the relation is many:many).

On the relation between Applications and Organizations also exists a functional fit field, which would get you what you’re looking for.  The functional fit on the relation between Apps and Orgs will showcase the App’s functional fit in (this case) a specific region.  See screenshot of the functional fit field on the App to Org relation from my demo environment:

Ultimately, App1 can be related to a given Business Capability (BC1 per the table in your post) - this would be independent of the Organizations relations.  App1 would then also be related to Org1 (NA) and Org2 (APAC), each with a different functional fit captured on their respective relations.

I can confirm that you will be able to report on the functional fit field that exists on the relation between Apps and Orgs.

In case it is also helpful, I am providing the email address to reach our SAP LeanIX Customer Success team: leanix_customer_success@sap.com This is where you can reach out if you are ever interested in chatting through modeling questions, best practice, and/or product-related questions directly with our CS team.

Let me know if this helps and/or if you have additional questions.

Best,

Danielle

Hi ​@danielle.moccia ,
Thanks for your support.

Yes, I am using the Organization Fact Sheet to represent regions.
My challenge is that while mapping a Business Capability inside the Application Fact Sheet (as shown in the image), once I save the capability relation, the "Relation Valid For" (Organization/Region) field gets applied.

Now, I need to map the same Business Capability again for a different region within the same Application Fact Sheet, each with its own Functional Fit value, but LeanIX does not allow selecting the same capability multiple times.

Hi ​@syed.aun,

I am not sure I am understanding fully.  The screenshot you provided indicates that the feature called “constraining relations” captured in the “relation valid for” column displays All Organizations, which means that the Business Capability you are relating to the given App is valid for any/all Org fact sheets that are also related to said Application.  If this is your goal, you should not be selecting a specific Organization here - you should be leaving the “All Organizations” set in the “relation valid for” column - leaving this as-is would mitigate the extra effort you note you are taking to set the same Business Capability for different regions, as this would capture the same Business Capability for all regions already.

I think the confusion could lie in that you need to be looking at the relation between the Application and Organization - in the screenshots you’ve provided, you are showcasing the relation between the App and Business Capability.  You should be relating Apps to Business Capabilities and also Apps to Orgs.  Can you try scrolling down further on your fact sheet to the separate/independent Application to Organization relation?  This shouldn’t have anything to do with the Business Capabilities you are highlighting - it is separate.  I’m providing a screenshot of what this relation looks like from my demo environment:

To sum up - you should be relating:

• Applications to Business Capabilities (per the screenshots you provided)
• Applications to Organizations (per my screenshot here)

Each of these separate relations allows for you to indicate a functional fit specific to that relation.  So, the functional fit field on the App to BC relation you highlighted would tell us the functional fit of the Application specific to that given Business Capability, where the functional fit field on the App to Org relation tells us the functional fit of the App specific to a given Organization (Region) fact sheet.  Your initial post leads me to believe that you are interested in capturing the functional fit between the Application and Organization (depicted in my screenshot) - this is modeled separate from / not considering the Business Capability. 

By default, when the constraining relation (“relation valid for” column) is set to “All Organizations” as shown in your screenshot, this will capture any/all Organizations you relate to the Application - you don’t need to select specific Orgs here unless you want that level of granularity with regard to the BC to App relation.

If my understanding of the ask is incorrect - apologies here.  My suggestion would be to reach out to leanix_customer_success@sap.com to chat with the customer success team further on the topic, as the CS Team specializes in modeling best practice topics like this here.

Best,
Danielle

We are facing an issue in the Application → Business Capability relation.
Some applications have different organization/region combinations for the same capability.

Example:

LeanIX currently allows the capability to be selected only once, so we cannot create multiple entries of the same capability with different regions and different functional fit values.

Required traceability of Functional Fit at the App–Business Capability–Region level, not just at the application level- business capability level.

Hi ​@syed.aun,

Thanks for clarifying - the way that we handle this is to have functional fit on the App to BC relation and on the App to Org relation, it won’t be possible to have the functional fit for App-BC-Org in one view as you are expecting, as we handle functional fit on the App-BC separately from the functional fit on the App-Org.  If you desire to see functional fit for App-BC-Org all encompassing, please submit this as an idea on our public-facing product roadmap.

To discuss additional potential workarounds, I would suggest reaching out to the CS team at leanix_customer_success@sap.com on the topic.

Best,

Danielle