Currently we have all types of apps classified in ServiceNow APM module and only Business apps type are sync'ed from ServiceNow to LeanIX overnight.
We are planning to move out of ServiceNow APM module and bring all apps into LeanIX.
What are the types of issues or concerns, I need to take into account, so we have successfully moved out of ServiceNow APM module? - Which are the tables associated to APM module? - What will be the impact to other related tables? (ex.: Mapped Application Services) - What will be upstream/downstream (IT components, etc.) effect on this? - We also have Business Capabilities definied in ServiceNow, would like to use LeanIX Business Capabilities, how this will be impacted?
Basically, we do not see ServiceNow and LeanIX as complimentary – they are redundant. Putting 2 systems in place will likely lead to slower outcomes, higher cost, more configuration, additional manual data entry, and a poorer user experience.
Thoughts and experiences on this subject please?
Thanks, Satish
Page 1 / 1
You would be basically closing down the APM in Service Now. However, the APM in ServiceNow is in the Design domain when looking at it from the CSDM perspective. Choosing not to use it should not have much effect on the operational side of the house for Service Now (Technical Domain and Consumer domains). The mapping from the APM will need to be cleaned up - you do not want orphan data from the APM perspective sitting around in the system. Mapped Applications likely won’t be affected aside from the previous comment. The Business Applications are mapped to Business Capabilities, but the Tech Domain objects (Tech Services, Tech Service Offerings) are not, so you should be okay. You will need to manually map the applications to the LeanIX business apps once you do your import. If you develop a mapping between the SN Biz Caps and the LeanIX biz caps, you should be able to take care of the change over in Excel. I assume you have not established the LeanIX - ServiceNow integration otherwise you would be doing the work there.
I would disagree with your assessment that LeanIX and ServiceNow are redundant, unless you were speaking from the perspective of ServiceNow APM only. LeanIX is a strategic tool for supporting critical decision-making working towards transformation and future modernization. ServiceNow, aside from APM, is an operational tool concerned solely with what it currently in place, managing incidents, problems, events, and change control. None of these operational processes are found in LeanIX. We have adopted a peering perspective between LeanIX - ServiceNow - Financial system. Each of the three pillars has a critical and unique role to play. However, integration in a collaborative manner is leveraged to allow the various systems to maintain a common language of sorts when addressing application and service management.
This is for Xanadu, but it should be mostly applicable as long as you are not multiple versions behind. Incidentally, you can see in Xanadu that they have renamed the Application Portfolio Management to be “Enterprise Architecture” which supports their stated initiative to move into the EA Management System (EAMS) space competing directly with LeanIX.
Hi Satish,
First of all, thank you for choosing SAP LeanIX!
Our out of the box integration can support you to bring existing “Business Capability” as well as “Business Application” in our Meta model. In order to understand how this is mapped in our standard configuration, please review our Default mapping diagram.
Thank you @PaulHinsberg for your insights.
There exists SNOW and LeanIX integration today for only Biz apps, capabilities and user-group, but not for all types of apps (IT, OT, etc.)
Also, the way these are currently classified in SNOW, I see there is an opportunity to rationalize the classifications, so that would help on the licensing.
You are correct, my assessment is specifically focusing on APM capabilities. I agree, want to leverage LeanIX strategic, road-mapping, modeling capabilities, we have already built TIME/6R in LeanIX for rationalization and modernization.
As an FYI, we are currently upgrading from Vancouver to Xanadu, as well.
Thanks again.
There exists SNOW and LeanIX integration today for only Biz apps, capabilities and user-group, but not for all types of apps (IT, OT, etc.)
@satishbyali our current SAP LeanIX integration is highly customisable, so we you can import any record from any ServiceNow table.
Can anyone share where there LeanIX and ServiceNow model is working well? We have been leveraging ServiceNow for a long time and are just going through a transformation for Hardware and Software asset management. We are working to stand up LeanIX for Business Capabilities and Business Applications. When teams need to add technology to ServiceNow for IT service management we don’t want to create duplication or conflicting data.
What’s your integration model?
How do you govern your application portfolio and CMDB? Any considerations on process, role or responsibilities?
Any tips or lessons learned on getting buy-in from leadership and/or adoption from Product Managers and Solution Architects?
Hi @Widget08
please take a look at this general overview below. For further details feel free to contact me directly.
Happy to discuss this further!
Hi @Carlos ,
That is a great… integration relationship model you have there, I have sent you personal msg asking for additional information on it.
Going back to basic Q, if I need flip the coin (i.e. move all apps from SNOW to LeanIX), what should I really be concerned?
Does this integration model suffice, or I need to looker deeper, to ensure there is no residual left on SNOW side?