Skip to main content

Hi All,

Two key risks we would like to use LeanIX to address here in our organisation is out of date software and / or operating systems.  Were early in our LeanIX journey so we have no plans for mass population of IT components yet but instead are focussing on value  add and these two key things are a historical challenge here adding risks to our application portfolio.

Were finding the aggregated obsolescence capability in LeanIX a really powerful tool for tracking this software support lifecycles and surfacing it up.  To do this we create an IT component for the application with the software version / vendor lifecycle in it and it all works correctly.

For operating systems we have observed there is a dedicated field in the IT component fact sheet for server operating system.  However this value does not seem to be used in calculating aggregated risks and seems to be treated  as a separate element of an IT component and it has no concept of lifecycle with it.

Do people use the server operating system field in the IT component fact sheet?  I have thought about creating an OS IT Component of type software of  for example “Windows Server xxxx”, adding the lifecycle in and then associating it with all relevant applications.  This would then be applied to the aggregated obsolescence view.

Is there a reason not to do this and effectively not use / disregard the dedicated field within LeanIX?

Has anyone else solved the above use case with LeanIX?

Thanks,

Neil

Do people use the server operating system field in the IT component fact sheet?  I have thought about creating an OS IT Component of type software of  for example “Windows Server xxxx”, adding the lifecycle in and then associating it with all relevant applications.  This would then be applied to the aggregated obsolescence view.

This is exactly what we do. We have our applications mapped to servers in our ServiceNow CMDB and we use automation to make sure we have corresponding OS IT components and to map those OS IT components to the application fact sheets. As OSes get upgraded and/or new servers are added, the mappings in LeanIX are updated automatically. We do this for more than OS as well. The aggregatedObsolescenceRisk value takes on the most severe obsolescence risk of all the mapped IT components.

Hi ​@neilcook, a very similar feature to the one that ​@KevinR developed in their organization is also available as part of our standard product LeanIX Automation Platform. We process the dependency tree in ServiceNow, automatically link the IT Components in LeanIX via a configurable mapping (operating systems, database products etc.), and also create a back-reference from LeanIX to ServiceNow so that you can see where the automatic link came from.

In short: Yes, your suggestion is a standard procedure. Most companies I know are using the ITComponents fact sheet type for operating systems.

Reply


Terms & ConditionsCookie settings