good morning good afternoon and good evening everyone my name is Victor predis Colonia I'm part of our asset management business unit and today we have another one of our servicenow Live Events this time focused around sap and the software license compliance equation thank you everybody for joining if you haven't already joined some of these events in the past we put a lot of these events on covering different areas of our product different areas of the platform and our particular group focuses around software Asset Management Hardware asset management and Cloud insights we're going to throw a link in the chat here where you can register for other future events and before we do get started a quick couple of announcements uh first and foremost the information we may provide here is privileged and confidential as well as some of the information that we answer on the Q a session or display in product um maybe before we're looking in nature so just keep that in mind as you work with us through today's session all right so a big welcome to everybody again this is our commitment to all of our customers to help Drive adoption and Achieve value faster with your Investments and servicenow we're going to focus today's session on understanding the software license equation and we're going to use sap as our case study and to do that I brought on my team to join me you have probably heard about me and you probably have heard about Michael we lead these events for the outbound team here at the asset management business unit but you may or may not have heard of akash akash is our PM who leads our sap product feature set and he has all the wealth of knowledge around our publisher pack for sap so Kosh thanks for making the time I appreciate you being with us today thanks for having me Victor so here's what we're going to cover today we're going to cover three areas we're going to talk about the software license equation we're going to set it up what is it to be in compliance with your software Asset Management program but then we're going to look at sap looking at the product overview what do we cover from a license metric standpoint how do you configure that within us within Sam and then some nuances around licensing and at the end of this Akash is going to walk us through different ways to optimize our sap configuration so that we're not wasting any of our software consumption spent as always put your questions and comments in the chat and we have a q a form that we're going to read off all the questions at the end of the session a couple other quick takeaways for those of us in the audience let's stay laser focused on the topic of the day if you have comments to share again use the chat feature if you have questions use the Q a form we're going to have a quick survey at the end of the session where we do want your feedback so that we can keep putting on these events and if you have anything to contribute again use the common feature we'll we'll read those off during the course of the event here and we might reference some of those during the Q a all right so without further Ado let's get started we have a big event today here let's start with the software license compliance equation so Akash when I think of this I'm really thinking about licenses and software consumption can you help us understand what is the goal uh behind the software license compliance equation and why is it an equation I guess it's a better question sure uh just like you know all of our other uh software publisher packs all the other you know kind of software uh that you're going to be tracking from an uh Asset Management perspective you want to identify what you've purchased versus what you're using within the organization um on the sap side it's no different we're going to take a look at what we've purchased from sap on the entitlements and then what is our software consumption as far as named user licenses um and the engine measurement licenses things like that that's going to be our our software consumption and then we're going to be able to see on an ongoing basis where we are uh from a licensed position perspective um are we do we are we over um licensed are we under license uh are we doing fairly well and be able to have those insights um on an ongoing basis versus uh once a year when you're doing your true up and and your Audits and so on and so forth yeah so this is It's almost like that point in time snapshot right of what you own versus what you're using uh and and are you over under like like you mentioned so the end result being that effective license position there's a couple of different scenarios um where you make that comparison and you might have different outcomes could you talk a little bit about those I see that you have their true up buy more and optimize what's the differentiation yeah uh no no different than anything else that we do you know once we're uh once we know where we are from uh a licensed position you know with sap it's a little different where you're gonna need to send that information uh to sap um but they're going to identify you know the true up value you know what what are you using and do you do you need to to you know buy uh more or you know stay current with your current license position uh or are you going to need to purchase additional named user licenses or you know engine measurement licenses and and things like that um and then from an optimization standpoint again if we're able to see these insights on an ongoing basis you know do we have uh any sort of uh named users that are are assigned to uh inactive users do we have any locked out users and things like that something that can help us optimize and get us ready for when we do have to do that at that overall audit yeah yeah I guess the best way to to kind of summarize what you said there is you could either be over licensed where you have more entitlements than software installations or under licensed where you have less entitlements than software installations the former being over licensed is not a it's not a bad place to be right it gives you ability to optimize like you said or grow your business uh using using the entitlements that you already own yeah and again on the sap side we're not really looking necessarily around uh installations but you know from a software Asset Management perspective yeah in typical software is exactly right uh you know the um on the you know the buy more you know when you need to buy more obviously you're going to be under um uh you have less uh rights available and so you know yeah when you do that true up or when you have to you know go purchase more just to make sure you're you're within compliance um but if you're over licensed that's not a great thing in the sense of we're just spending too much money on that particular software so you know where can we where can we reduce uh that overall spend yeah nice so you can take actions on both end of the of the spectrum if you will for sure so let's look at how that how this kind of translates into sound so this is this is how Sam works right maybe we can jump through some of these and overlay where entitlements and and software consumption goes and and effective license position but for those of us that haven't seen this slide in the past Akash uh how does Sam work how would you explain this to somebody yeah so uh what just Sam Pro on on the uh on the servicenow platform you know basically we have our software assets our our entitlements um so those are going to be the purchases that you've made and then we're going to bump that against the the inventory that we're getting from our different Discovery sources um or Integrations in the case of sap so that's your software consumption and so that is going to go through the content service it's going to normalize a lot all of you know a lot of that data for us um and then we're going to get to a point where we have the ability to reconcile and see where we are from a compliance standpoint where we are from you know the what we've bought versus what we're using um you know on you know whether whatever software we're looking at in the case of sap what are we using that we've integrated uh through the uh the ABAC program and bringing into servicenow we can see what we're using on the sap side so that's where we're going to identify some of that compliance um in our licensed positions um and from there you know you're hoping to be able to take some sort of action so we have optimization dashboards and so on and so forth that will allow us to identify you know what are some low-hanging fruit that we can go and we can help optimize um and then where are we from a named user license perspective are there any optimizations from a role-based optimization or transaction based optimization and that would be your within your action awesome awesome no no thanks for for clarifying that and bringing in that equation into how the engine here works I appreciate that all right let's get to the meat of everything sap walk us through kind of an overview what do we support today um what are some license metrics and how can we think about sap Within servicenow sure um so as far as what we support uh our main uh areas that we we are uh we support today uh from engine measurement uh so Gathering those different engine uh measurements uh from your multiple systems that you have those clients Gathering that data as well as your named user types so uh named user licensing we do uh get a lot of that data directly from a Content perspective directly from sap as far as the measurement IDs as well as uh all the different name user types uh and things like that so all of that data is gathered through the sap from a Content perspective and then we capture that data um via our ABAC program deployed in sap for your individual instances for your individual sap deployments we bring that in through any integration and then that's where we would be able to do uh create those entitlements uh identify any licensed position and optimization so um we do role-based optimization transaction based optimizations today um and then we identify um different what we consider low hanging fruit inactive users um users without named user assignment locked out users things like that awesome and I saw there that you also support s4hana and self-declaration any comments around that yeah so uh as far as uh ds4hana we support like the ECC uh applications as well as uh S4 Hana um the self-declared you know that kind of goes back to our engine measurement um but we you know not just the the measured data that we get from sap we also uh allow you to uh to enter in those self-declared uh measurements as well self-declared um uh usage as well okay yes it gives it gives you a little bit more flexibility when it turned when it comes to mapping out all your license consumptions all right so you mentioned the ABAC program uh let's talk a little bit about that because there is a there's some nuances around configuring configuring sap within Sam so maybe we can spend a little bit of time there sure um so uh with our with our abat uh program you're going to download that from the servicenow store um and deploy that within um on the sap side we do have and I think uh you have it here as well um we do have a installation guide uh for that where you're going to create um that user and Associate roles and and so on and so forth for the servicenow system to be able our servicenow uh user to be able to gather that information from your multiple systems uh and then we store it into um a now uh table namespace on the uh sap side once you've deployed that we can go and create the sap connection on the servicenow side So within servicenow there's an sap connection table um you'll go ahead and create that profile um identify a mid server if you're going to use a mid-server and then from there we can go ahead and run the test and then you can do your initial uh refresh of data from the multiple systems and then pull that into uh servers now so there's a couple links there that allow you to do that once we've brought in that data that's when you want to start utilizing the software models that were created and utilize that those models to create the software entitlement so um it's similar to you know kind of our SAS uh software models that get created if we're we're doing some sort of SAS integration where you want to utilize the software models that are uh being created through that integration and not necessarily create them ahead of time which is what we recommend doing um with other type of Publishers and and entitlements and so on and so forth so this one goes against the grain a little bit yeah that's a really that's a really key distinction there right so just as a general term um on-prem licensing we normally say create your entitlements using a publisher part number that's going to automatically create the software model and then that'll get linked to the software installation or product from from a SAS perspective we kind of say the opposite we say set up your API integration to pull in data Sam will create the software model automatically and then you associate the entitlement so on one hand you're going from left to right on the other hand you're going from right to left what you're saying here is sap follows that right to left format set up the ABAC program bring in the data Sam will automatically create the software models and then you create the entitlements I think that's a very very key takeaway when it comes to sap configuration that's correct and and the reason for that is we we look up that named user license uh in their content generate that model correctly we look up the the license metric that we're getting uh from sap and generate those models correctly and so you just you're guaranteed that those models have been created correctly and you're going to be able to reconcile against them uh going forward yeah that makes sense so you're using some sort of unique identifier to harvest the right information out of the Content Library to create the software model that's correct great and then step four right is uh reconciling and then uh and you know taking a look at any of the optimization items um that you will see in um in the optimization dashboard so um we also identify any possible indirect uh access which we'll talk about later things like that there's a there's some different data points that you can take a look once you're uh you've uh run reconciliation against uh the sap data yeah okay great so when you do have it set up and configured it should look something like this diagram that we're going to show right where you have the ABAC module it's bringing in the data it may go through a mid-server and then it gets kicked over into servicedown anything else you you think you should comment here Akash that makes sense for our audience yeah not I mean to be honest like what we're doing here is we're deploying that in your uh solution manager or Central system um and then it's going to go query all the different systems we are bringing in um based off of your RFC connections uh we are bringing in um uh different uh whether it's development production test we are bringing in all of those systems um but then as we see you know going forward when we reconcile that for engines we're really just looking at uh production and then for uh your named user licensing um we're looking at Dev and production uh mostly so okay a quick question here that I didn't ask on the previous slide is the configuration that you mentioned is that the same configuration that's applicable for for the different license metrics that we support in in Sam so in other words you set it up once kind of thing say that again so like uh so we have we have engine measurement we have named user will I get both of those data sets and that data through the a through that one time where you set up that ABAC um program yeah it's a it's a single setup and then you just like uh our SAS just like any other Integrations really nothing you have to do there unless you see that um you're not getting data for a particular uh system or something like that then you may have to go back and take a look if there's any errors um but yeah it's for both named user and engine uh the only difference is for self-declared you will create those in service now directly um it won't come in through uh this integration so self-declared is is the only one that there is some some additional work uh on the servicenow side okay yeah that makes sense all right let's jump into uh sap licensing because I know we talked about engines and we talked about name users I'm going to set up a scenario Akash if you will and then I'd like you to maybe speak to it and if we get a chance to I'd like to jump into the the product so it's very common when I meet with customers and they're working on sap I come across a Sam admin who you know wants to reconcile their compliance for named users right so they they approach me and they say hey Victor our business outcome is that we have to be compliant with our sap named user licenses so that when audit comes around you know we're reconciled and we're in a good spot so from from their perspective they essentially need to calculate active sap users across systems and compare that to um their license count effectively what they're asking me is how do I create an effective license position where I can optimize or take action right so what would you say to an individual in that scenario looking at named user licenses yeah so uh on the sap side you're absolutely right you've got to be able to consolidate that across systems uh so you're going to run a usmm uh on the sap side um and that's going to get you you know all of the different data elements from each individual system um and we kind of do the same thing on the on the servicenow side where we're going within that particular system we're capturing um the users and and their user type and and so on and so forth bringing that into uh the central system and then pulling that data into servicenow so when you see um the reconciliation when you do that license position it's going to look across those systems and then identify the highest value um across those systems for that particular user from a named user license uh perspective so uh it'll select the the highest named user type and then that is what gets applied to that license position so a lot of the things that they they're going to have to do on the sap side as far as um you know pulling that in uh and into a law report and so on and so forth they still have to do that this allows them to see that on an ongoing basis uh within servicenow so there's no kind of uh surprises at the end kind of thing yeah yeah what does this look like in the product sure so uh let me still share here real quick yeah and I'll show you this so um so when we're looking at at uh from a Reconciliation standpoint again uh within the workspace um you're just you're gonna go to uh the sap um the publisher pack uh within that named user this is you know similar to just about anything else that we have where we're identifying software models and and so on so forth this groups it by named users and then you'll have all your different named user uh licenses um from a licensed metric perspective uh identified here so let's see if we can get that to pull up here um so what you'll see is you'll have uh the named user um uh identified here so sap application professional how many do we own from a entitlement perspective so if we take a look at our entitlements we have 90 rights and then you know what are we using um within that we've captured data wise uh from all those individual systems and then what you'll see is even though we have 139 sap users we are consolidating that we're identifying what's been uh who's been licensed and not licensed and so on and so forth but you can see those 139 users you can see those across systems here um and then what they you know who they are and so on and so forth so you'll be able to kind of see that data in servicenow as well um so that's you know from a a licensed position perspective that is the from unnamed users that is the type of data that we'll be pulling in um into servicenow uh on top of that we also have uh we go to our analytics um we do have four named users we do have different optimizations and I think we're going to get into this later but um this is also where a lot of that data is utilized as well is within the optimizations themselves that's awesome and and again just to play it back the um the named user piece you say that if a user has a different role or type in different systems we're counting the highest most roller type so that so that they're licensed by the highest uh rule so it's kind of like a watermark if you will exactly highest watermark okay great so if you have any questions on named users feel free to throw those in the chat we'll get to those let's jump into engine licenses there's a little bit more information here that we should cover uh so Akash again I'll set up the stage here customer comes to us and says hey my business outcome is I want to be compliant with my engines again to mitigate any any risk exposure that I have to audits so to do that I need to calculate the number of sap engines that I have and compare that to my license count and ultimately I need an effective license position I need a point in time perspective letting me know if I'm over or under so I can take action what can you say to that yeah kind of the same thing again we're we're that ABAC code is going uh across systems it's pulling that data into servicenow um we're able to see uh the uh the engine usage by system in servicenow as well uh and so we'll consolidate that data and then uh you're basically from a licensed position report you're going to go against what you've defined as your entitlement of usage for the engine data and then it's going to calculate uh in the sap engine usage table calculate all those records and then be able to show you the license position um uh and and where you are we also have a couple of um uh indicators one uh where you're if you're 90 within the the range of 90 or higher on an engine usage it'll uh call those out specifically and then any unused engine so let's say you have entitlements that have been created um for specific engine measurements uh software models when if we find no usage uh for that we'll identify those unused engines now doesn't mean that they're truly unused but they may you may have an issue with the data that's being pulled uh from that particular RFC connection some for some reason something might have gotten turned off or whatever for us to be able to pull that data or you're truly not using uh that particular and so that that gives you just something maybe you can utilize it to for a trade-in or something you know when you're negotiating with sap it's difficult to take it off completely but you know if you're gonna not use it anymore maybe there's something else that you can you can purchase yeah at least you said it at least what you're saying here is it makes you aware that something may not be used or may not be used at full capacity or you know the highest utilization that you're measuring so you may want to take some action around that you made a comment earlier about production clients I just want to kind of resurface that here for this slide what was that comment around production clients yeah so we'll we'll put uh we'll pull all of your your different clients to some clients into servicenow uh but when we do the reconciliation for engine licensing we're doing that only against production systems um so we will identify those uh engine records uh specifically for production and then that's what you're going to end up seeing on the servicenow side and I can actually kind of just quickly share as well so let's take this back so if we go back to our uh license usage under sap um let's see I probably should have figured out which one I wanted to utilize first but uh let's see if we have any records in here so like if we'll see like we have certain engine measurements uh identified this license required here um this is where you're going to see across systems um how much we're we are uh using uh for those particular licenses so um in the case of uh like this one here uh we've got this engine this is these are engine um uh usage records so we can drill down into this um and that is going to show us our engine usage record from what system um the software model that's associated and then the engine usage of that particular uh for that client so that's that's really what we're looking at you know similar to um like if you're drilling down into something that's software installations and you click on the licenses required it's going to show you all the different software installations and who's using it and so on so forth this acts the same way except it's just going to show you engine usage records or in the case of named users it's going to show you those uh those users uh that we gathered from sap so um same Concepts uh that we we utilize within this license required link uh as far as uh engines that have reached you know 90 or above again this is just an indicator uh you can drill down into that and then you can take a look at some of that data uh as well here uh to see from which system which measurements themselves and so on and so forth um we are reaching that that threshold you can change this as well if you want to be you know at a lower Mark or whatever you can update this uh it's an indicator uh for this particular widget uh and then lastly if we take go back to our uh analytics uh we also identify any unused engines also um we'll also probably just take a second here and just go through the um a software model uh for let's say a self-declared uh engine so if I uh just quickly I'm already on this particular software model uh but if we take a look at this one's uh the license metric for small plants um so you know anything defined as 500 or less uh employees at a particular plant consider a small plant um and then you just identify you know what's my software entitlement you know how many of those am I allowed and then from a usage perspective this is where you would click off of that software model you would identify that here um I'll just put in the name I'd say you know November uh 2022 and then what is my you know what is my count of that uh so I might have you know five of those uh whatever so I'll go ahead and submit that and that's your engine that's your self-declared engine usage uh for that particular um uh for that self-declared engine measurement got it and then that that's there for um reconciliation purposes or is it just there for your visibility purposes no it is uh therefore reconciliation in fact I think I ran this yesterday um for you know what we had previously so it does get reconciled um and it so I just added another five so that we popped into here if we run reconciliation now um but this will actually pull in those uh what it is uh pulling for those reconciliations this is that record um in my case I created a second one for five here but this is showing me the one that I created yesterday oh awesome okay so then you have it in one place as well where you can look at all of your sap named users engines and self-declarations in the same spot yep fantastic so let's look at this next slide here it's a it's a engine flow engine measurement flow and I just want to walk through this is there anything that that you mentioned that we didn't cover that we should point out uh when it comes to measuring engines yeah I think we're uh I think we've kind of hit on All Points uh we're we're going to um you know have the the ABAC program gather those those engine measurements uh uh it's going to create the software models on our side um and then uh obviously we will continue to kind of track that um it it pulls it on a weekly basis uh uh it's going to gather uh different measurements on a weekly basis um and then pull that into servicenow automatically and then we'll be able to kind of see where we are over time from an engine measurement perspective so really it's it's you know generating those entitlements knowing what we should be at um being able to see the data coming in on a periodic basis being able to monitor that data uh and then and then reporting off of it going forward okay all right now what about um because I get this question sometimes about indirect access is that something that's um particular to sap and what could you comment around that yeah so when we're looking at indirect access really um we're looking at uh systems users that uh are are logging in from third-party tools uh things like that um that may be querying um sap May write some data sap uh and and so on and so forth maybe there's multiple concurrent users um you know that are utilizing uh that connection um so those are the kind of things that that sap is looking for from an indirect uh access perspective which can get expensive so um either you need to apply a named user type Associated to it or you need to pay for digital access uh and again all of these things that they're just creeping up on you um that could be expensive and it's difficult to kind of see that on the sap side um so what we're able what we're doing is through PA Spotlight we do have the ability to we have criteria that we've set automatically out of box um customers can go and update that criteria they can you know change thresholds and things like that um but uh basically what we're looking uh to doing is identifying that indirect access and I think there was a couple of uh widgets where we do uh show on the reconciliation dashboards uh for potential indirect access from user activity and then potential indirect access uh from a transaction activity perspective I see and so if I had this displayed on my side what would I do with this information so this is definitely something that you want to work with your sap teams you know and and I will say just across the board our sap integration is pulling data from sap we do not write data back to sap um and again mainly for uh this type of indirect access and and uh taking up licenses and so on and so forth um so we don't write anything back so this is definitely something that um you can drill down into these you can get these records um and show the um the usage so show what clients it's coming from what's the system name um or the the username and so on and so forth um that is is uh that have these user activities or these transactions uh and then report that back to the sap and and figure out what you want to do um and kind of dig into that a little but it gives you some insight which is kind of the main main issue the place to start if you will yep awesome all right so we've we talked about sap from an overview perspective we talked about how to configure it we looked at licensing we looked at the product now let's talk about optimization uh so this is not just being compliant right once you're done and you're compliant now it's about how do you save additional cost for the business so you can walk us through optimization um just at a high level and then let's focus a little bit on on sap yeah so you know servicenow just in general right like we with all the different publisher packs that we have um customers are asking for and we're we're trying to provide as much uh from a optimization perspective that we can so whether it's Microsoft Oracle IBM things like that we do have some optimization either dashboards indicators or uh in certain cases um you know guided guided uh playbooks uh for those optimizations and we're continuously uh coming out with more uh specifically around sap is no different we do have um optimization uh set up for um the named user licenses you know based off of roles and transactions we've got um optimizations or indicators to identify any inactive users or locked out users um uh anybody that that has a named user uh or as a dialogue user that that is missing a named user assignment uh and then engines that like we talked about on unused engines or engines that are reaching 90 um of the entitlement and so on and so forth we identified those as well so these are just these are things to be able to some of these are low hanging fruit things um some of these are hey we need to be able to monitor similar to those indirect access kind of things we we need to be able to to consolidate and monitor that data um so we can make uh any recommendations back to the sap team yeah and and I guess the other thing to note here is as part of our uh you know newest U UI workspace that we've released back in San Diego there's a central place where customers can navigate and identify all of their optimization opportunities yep so I think within Tokyo like if you go to these the software asset analytics um page and then on the tab for optimizations and savings we do have three specific Publishers that we we have um where we have these specific uh publisher optimizations um sap Microsoft and I don't remember the last one but um but sap is one of them and uh you're gonna go ahead and drill down into the sap one this is where you will see uh specific widgets that are that apply only to in this case sap yep so let's walk through some of those um those optimization opportunities right so I think I've identified seven yep uh so inactive users just like it says uh so we use 90 days um customers can update those indicators if they want to reduce that number of days or increase those number of days but um or if they have certain additional filters that they need to apply based off of those users uh they can do that as well but basically we're looking at inactive users that have a named user assignment um and we want to make sure that either if they're not using it that they you know those those uh those roles are removed from that that particular user um as well um here we've got sap users without a named user assignment so through transactions we've seen um uh activity um and but they're not actually uh there's not a named user assignment Associated to them these we want to make sure that we're calculating correctly because this could result in utilizing the default named user assignment um on the price list and that is typically the most expensive one locked out users again from a an sap perspective these are users that have been locked out of all the systems um uh that they have Associated they're Associated to um that we're seeing a lock that a locked out user and they are consuming a license as well uh some sort of uh dialogue user that is consuming a license so we just want to make sure that if they're not using it um that you know if they're locked out that they you know get unlocked or remove that that access um non-dialogue users with a named user assignment so these are um you know system users or something like that where we don't have a A or we do have a named user assignment which we we shouldn't in that case so we just want to be able to to clear that up and make sure that we're not consuming an additional license that we don't need to right how about number five here yeah and then this is uh for uh role-based optimization there is a little bit of setup that that is required um you do need to identify we typically tell customers to kind of go with their most expensive ones first but you do need to do some mapping between the rules and the named user types um and based off of that we can we can take a look across uh the multiple systems what roles have been assigned to your user and see if they're uh if they have the uh if there's a cheaper named user assignment that could be utilized for that particular user some over six and seven tell me about it yeah transaction based ones these are uh again from a setup perspective um there is a uh Reclamation rule that needs to get created identify you know what transactions uh minimum transactions you're looking for uh for that user and if they fit that uh criteria um then we would identify a possible transaction based optimization uh for that particular user fantastic and their last one there like you said unused engines uh if there's any that you need to make activity on or action on talk to sap uh regarding those yeah whether that's you know something that you know we're truly not using anymore we can we can uh add that to our negotiation uh discussion or um if it's something that we have an issue with uh we may want to talk to our sap team to see you know if that RFC connection got inactivated for some reason fantastic great well so this is what it looks like in the dashboard again right you can click into those I would imagine you can click and teach those tiles and it would give you the unique records for all of those inactive users or licensed non-dialock users ready to list those um details out great great great great all right so Akash big thanks for handling that for us I want to see if there's any questions out in the Q a form uh Michael's going to help us with uh facilitating those questions yeah gentlemen great job another great conversation and really thorough we have a good amount of people on for today so thanks everyone for joining we have I'll read this first question here um from Tom um but keep the questions coming so Thomas and I was the ABAC part of the is the ABAC part of the Tokyo release or that a purchase add-on for Sam Pro yeah so when you purchase sampro you get um you get all the publisher packs um that are associated to it um and then the ABAC program is uh downloadable from the servicenow store and that is included with your with your Sam Pro purchase it is not an additional purchase awesome somebody messaged me while we were talking Akash and the question was once I have this the data coming in through the ABAC program do I start with named user or do I start with engines is there an order of operations is there a recommended approach I guess if we were to expound on that what is the best method yeah that's a I mean that's a good question I I don't know if there's a tried and true like simple you know hey you should always start with this and and so on and so forth um I I think engines are probably um easier in the sense of uh because we're creating those engine measurement records uh and you're generating a software entitlement for it and your reconciliation just kind of happens at that point named users because we have optimizations and and so on and so forth um that may take a little more setup um on the named user if we want to utilize like role-based optimization or transaction based optimization you're probably going to spend a little more time on the named user side I guess another another way to look at this is can customers set up multiple ABAC programs let's say they have different systems across their environment is that possible and if that is possible then maybe to answer the other person's question maybe you start with the smallest system right just so that the data set is a little bit more manageable maybe that's another way to look at it and then expand into your larger footprint just a suggestion I don't know if you can validate it makes sense you know uh if they do have multiple systems you know across organizations or whatever definitely start with one um maybe get your feet wet you know we we talk about it with uh with Sam Pro and just in general you know crawl walk run you know try and just get that process down you know understand the data that's coming in uh and then you know utilize that to repeat that process across uh across your uh sap instances okay cool let's see any other questions out there Michael yeah we have one from Philip I was multitasking in the chat you didn't you didn't address this one yet did you Victor no um no I don't think so okay let me read it out then so uh Philip wants to know what about different license types for a single publisher how is optimization represented for various licensed product models different license types for a single publisher I'm not sure I understand the question specifically but um if we do have let's say for different models um if we do have different license metrics per model so we still on the entitlement you can have the same software model but across those different software models we might have different um uh and not necessarily on on in the case of sap but let's say Microsoft or something like that something maybe per user something maybe per device uh type license metrics um you can do that across models and we do reconcile those differently so we will look at that entitlement we'll create two separate license metrics uh license metric results for the same model and then uh reconcile that um based off of how you've defined it so hopefully that is what um the question was about sure and it's not um the individual can reach out to us feel free after the after the session we can clarify anything yeah I do see a good question here uh can you do this type of training for other Publishers like Adobe Microsoft Oracle especially Oracle uh the answer is yes um it is part of our our roadmap if you will uh when it comes to these Live Events uh we're picking and choosing different Publishers we did do one from Microsoft not too long ago so if you are looking for the Microsoft recording we actually do have that on the community but we will be expanding into other Publishers to do something very similar thanks for the question all right um sorry I sent the incorrect PDF in the chat I'll be sending sap related PDF shortly Paul wants to know is there any cost on the fap side for this integration and do you find your other customers that the benefits of enabling this outweigh the cost to license we also have success factor licenses and cpea licenses can I capture anything from them as well yeah so um as far as the integration itself there is no even on the sap side there's there's no uh licensing costs specific licensing costs there um so what we're what we're looking at is because we're not we're also not writing anything back to sap um we're just reporting um and bringing that into servicenow so there should be no uh indirect access type of or digital access type of costs associated to it um so at least that I've heard from from customers uh specifically um and based off of multiple contracts that you know they they might have across those different customers so um as far as success factors and so uh I know today we are we are looking at an integration for Success factors to be able to to to gather that information and license that I don't believe that is supported as of today um and then CPE Fury I that is also I don't believe that is uh currently uh supported either got it there's one more question here in the Q a form um does the ABAC interface require a named user license and what type here uh no uh so again from a uh sap perspective I don't believe so it is some um uh uh I have not heard that our ABAC program integration requires an sap named user license okay I've I've in in the ones that we've we've dealt with uh going forward like all the different customers and and so on and so forth uh when we've gone to set this up uh that's never been brought up yeah I've experienced the same um when working with customers that hasn't that hasn't shown up [Music] okay all right well thanks gentlemen those are good questions we this recording as I said in the chat will be posted on the event page in a couple of days and we're now going to review some trainings and resources available to you on the Community page and be sending out some links so thanks for the great questions yep thanks for that appreciate that all right so if you want more information about what we discussed today we also recommend that you take some related trainings right these are fundamental to understanding Sam not just for sap but for everything related to Sam so starting first with the fundamentals training staff fundamentals a lot of you have probably already taken that it's a good place to start in fact we highly recommend that you start there but if you want to add more um expertise around certain areas like entitlements normalization Discovery and Reconciliation troubleshooting there's a couple of other free they're they're no long they're not nothing longer than like 10 15 minutes each module but these are really good concrete trainings to help support what you already know in Sam fundamentals adding to that there are some white papers and guides so some of the things that Akash talked about today are covered in two areas we have a white paper called managing sap named user licenses and then we have another one that is um a KB article but we've also provided the PDF in the chat here to sap integration with servicenow software Asset Management so again talking about engines talking about how to configure everything those two documentations will help you with that and then the import entitlement guide is just another document that helps you bring in entitlements or teaches you how to bring it bring in entitlements into Sam after you've set up your sap configuration all right and the last but not least we mentioned it but the item Community is a great place to get a lot of this information recordings from other live events that we had our getting started guide which has a lot of links to other resources and areas where you can set up on how to be successful with Sam um and then again a list of those trainings that I mentioned earlier so I want to thank everybody for their time for joining us today Akash thanks again as always appreciate you being here for us and to the audience thanks for the questions we hope you had a good successful presentation with us and we'll catch you in 2023 thanks everybody thanks all