Pretty common scenario for us as well. We split the metadata across 2 perspectives: We use ‘as a service’ classifications as IT component sub-type fact sheets. For those business applications that are serviced based and clearly part of the application portfolio, we simply add those in as application fact sheets and build logical interfaces to capture data flow.

We are pretty early in our LeanIX tenure, so others may have better approaches.

Cheers,

CJ

This is a very common scenaraio.  We track them by creating an Application Fact Sheet (subtype = Interface Group ...which is a custom subtype) that represents all of the interfaces to/from a particular vendor.  Details regarding indivual interfaces can be included and/or attached to that fact sheet.  Pros:  Allows you relate the interface provider/consumer with the interface group (an “Application”), Cons:  Increases your application count and makes metrics reporting a little more complex.

Regards, Jeff

Our answer is pretty similar to folks' above: for the external partners, we create application fact sheets with a custom subtype. The conditions on this app subtype limit number of attributes - i.e., we do not care about their IT Components, tech or functional fit. To save some $, we also bundle some of the similar function partners together differentiating the integrations by creating multiple interfaces. It is a bit of a penny pinching but with multiple POS streams from sale channels it adds up.

We created an ‘Integration Endpoint’ Application Fact Sheet Subtype to represent external integrations.