Skip to main content
Question

Reference standards (Business and Solution)

  • June 11, 2026
  • 1 reply
  • 15 views
L

Hi all,

 

I’m trying to document the Reference Standard for Business Capability and Technical capability in LeanIX.

By Reference Standards, I mean ‘Prescribed or preferred technology, design, data, and process elements that conform to architectural principles, and that can be used to build the Solution Design’

For example, I have 4 different solutions in my landscape for Identity Management, each catering to different needs but they are the standards/preferred for that capability. As a solution architect, one should be able to look at this repository to build the Identity Architecture for the solution.

I have the same question for Business Capability as well. One way can be to add a new tag but it’s going to be a lot of maintenance, same with enabling Leading and Supporting capabilities.

Appreciate if any one can share best practices used for this use-case.

 

Thanks,

Shanthi

 

    1 reply

    GiannisAnt
    Forum|alt.badge.img+2
    • GiannisAnt
    • Everlasting Love
    • June 12, 2026

    Hello Shanthi,

    Multiple tags can indeed cause noise in the workspace, and maintenance might be hard.

    You can think about using a custom Fact Sheet type, or utilizing an existing type like Tech Categories or Platforms (by adding a new subtype to them).

    Then you can create a Fact Sheet named “Approved Technology Stack” or be more specific and create things like “Approved Database Stack”.  
    Same goes for Business Capabilities with a Fact Sheet named “Reference … or X Capability/Domain”.

    By connecting those Fact Sheets with your desired IT Components, Applications, etc., you can create reports showing which items are included and compliant with your references. Optionally depending on your modeling you can use a custom relation for this to keep things neat.

    This also results in interesting matrix reports where you can see how close your current landscape already is to your reference items and pinpoint interesting cases for changes.

    Architecture Decisions also work nicely with these, because your references are actual Fact Sheets.

    Finally, a calculation that reads those relations and populates a hidden field can be used in another field that will, for example, calculate a percentage of how many reference entities something is using, and more.

    Hope this gives you some food for thought.

    Terms & ConditionsAccessibility statement