Skip to main content

Hello everyone -

I’m new to LeanIX community and I did search to see if there was a similar question asked and didn’t find anything. Let me give some context before I ask the question:

 

I am a business architect in a health insurance company that sells different types of health insurance “Products’. I’m documenting value streams, using Business Context fact sheets, across the organization and then linking Applications, which have their dependencies on the IT components. There are certain value streams that are either specific to a “Product” or multiple Products. Similarly there could be Applications that would be used for a specific Product. I need to create “Product-Specific” views in LeanIX. For example, I need to answer following questions:

  • Which Applications support Product A?
  • Give me a view of Product B value streams and the related Applications and IT Components?

 

Here are my questions:

  1. How can I best associate specific Products against value streams and applications?
  2. Would “Tags” be the optimal mechanism here?
  3. Could I use custom fields? If so, in which facts sheets and how?

 

Thanks

@jsiddiqui I understand that a “Business Product” is one of the standard subtypes of the Business Context factsheet too.

You could follow the modelling guidelines from LeanIX detailed here: Business Context Modeling Guidelines (leanix.net)

Generally they don’t recommend using more than 2 “dimensions” in a fact sheet for modelling, but the Business Product could be related to a Value Stream either in a Parent/Child hierarchy or the Requires/Required by method.

TAGS (great for visual cues in fact sheets) or custom Attributes can be added for additional analysis or filtering options.

I would suggest trying it out (preferably in a Sandbox) and seeing if it works for you to meet your use cases.

@Justin Swift . Thanks for responding.

I would appreciate a bit more information. If I’m understanding correctly, I can mark a business context a specific “Business Product” type. For example, I’ve created a value stream called “Process Claims”. I can mark the “type” as Business Product. That is fine, however, we have multiple products, so how can I mark the value stream to demonstrate that it is applicable to Business Product A and Business Product B, but not Business Product C? OR are you suggesting that I create individual Business Product type fact sheet and then relate them to “Value Stream” type of fact sheets? If I’m thinking wrong, then please use my example to elaborate your point of view.

 

Thanks again!

Hi @jsiddiqui ,

You may consider for all practical purposes that the Business Content subtypes of Business Product and Value Stream to be distinct. They are just grouped into a common Business Context fact sheet type to simplify the meta model. But because they are subtypes of the Business Context fact sheet type, the make use of default defined relations.

Both Value Stream fact sheets and Business product fact sheets may be related to Applications. Something like:

Value Stream « -- » Application « -- » Business Product

And Application may of course be related to IT Components:

Application « -- » IT Component

If you want to be able to indicate that some of Value Stream only applies to specific Business Products, you may extend the meta model to configure a relation between Value Stream and Business Product like that:

Value Stream « -- » Business Product

See https://docs-eam.leanix.net/docs/fact-sheet-relations#self-referencing-relations and https://docs-eam.leanix.net/docs/fact-sheet-relations#creating-a-conditional-relation-between-subtypes-of-the-same-fact-sheet-type for how to do that to constrain the relation to fact sheet subtypes.

Hope this helps.

Reply


Terms & ConditionsCookie settings