[Music] all right good morning good afternoon and good evening everybody my name is victor paredes colonia i'm part of our itam business unit and here i'm very excited to present with you and few others our next live event if you've been joining us in the past we've had a couple of these different live events doing deep dives into different aspects of the product and the discipline around sam and today we are going to be talking about entitlements software models and the discovery models and before we jump into that just a few little announcements the first and foremost some of some of the information here is privileged and confidential so please bear that in mind in addition in addition to that uh we are going to have some forward-looking statements we might respond to questions uh with a forward-looking statement or you might have things displayed on the in the product that has some forward-looking statements as well so bear that in mind as things are subject to change but without further ado i want to welcome everybody this is another one of our servicenow events you know our commitment to you is to help all of our customers deploy adopt and achieve value with their investments in it asset management more specifically with software asset management and today we're going to be looking around getting a better understanding of the inner workings within sam so again entitlements discovery models software models and we're also bringing on shankar who is going to be part of our business unit to discuss a little bit more about that so again my name is victor i've been co-hosting this with patrick lounge for some time now and we're really excited to have you all here with us today and we're especially excited to have shankar shankar is joining us from the product team and shankar's specialization is around software asset management as well as sas and shankar has a lot of different demonstrations he's going to show us today in product as well as answer a lot of questions around entitlements and the different software models and discovery models so sean carr thank you for making the time i know it's a little late where you are but we appreciate it no problem thank you i'm glad to be on this call looking forward to this movie for sure and for everybody out there we're going to focus on two topics again entitlements and looking at what are some leading practices around that we always get questions around what should i be doing with entitlements what order should i be uh you know importing them how should i import them what's important what's required what's not required so we'll try to address all those and summarize those at the end of that segment and at the same time we'll jump into software models and discovery models we'll peel back the onion look at what are the inner workings between them what's the difference between them as well as how are they interrelated as with everything please please use the chat please include your questions in the in the q a form and let's stay laser focused on the topic of the day so those are the two topics we're going to talk about entitlements and the different software models and discovery models so questions and comments keep them to those and if you have any experience using the product with those topics in mind share those with share those with all of us right i mean we want to we want to engage with you we want to hear uh your comments and there's other folks out here that probably want to learn from you as well so use the chat okay let's get started so shankar one of the things that comes to my mind with entitlements like anything else really with mining data and loading data into sam there's always a challenge there's an initial barrier to entry if you will so what's the challenge uh with entitlements how would you define that yeah so uh typically any any sam product we find that entitlement creation itself is an issue and part of the reason is because of the multiple sources that you would have within an organization especially when they are moving to sam for the first time that they would find that there is a lot of information that spread across the organization that could be entitlements purchased using the legacy procurement systems and those pos and your alliance will be sitting there then there are contracts which could be sitting in a totally different system and you could also have contracts that are in pdf files or maybe even printed documents so those are also lying around the organization so you need to collate all this information and and then be able to create the entitlements of the system and with the advent of sas anybody can purchase a software just a credit card so you would see that individual teams or maybe even individuals go and they would be you know purchasing software on the internet and they would be charging it through expenses in the system which may be completely undetected by the i.t department so you would see that all these are also lying around the organization so to collate all this information across all these various sources and be able to create the entitlement in sam is itself a big challenge and that's what most of our customers uh face and as part of that uh you know sam as out of the box provides a lot of tools that enables uh creation of the attachment tries to make the life of uh assam admin much easier so you you could set up entitlements in the system using the guided setup where specifically for those people who are new to sam and new servicenow they may find it easier because it takes the user through a guided set of steps it could also be useful for setting up certain entitlements where you're not sure where to start from so the playbook would actually help you go through those steps and create their title and when you are migrating from another system or from a legacy system to to sam or if you are renewing your entitlements uh every year where you need to update a lot and create new entitlements in bulk then the bulk import facility that we provide using a spreadsheet actually becomes very useful the same feature is also extended to be able to import your microsoft licensing mls statements and sam automakes a process for you you can also set up your integrations to your procurement systems and import the po and po lines into service now so that you automate the process of creation of entitlements within cern we could also build custom integrations to other systems and download the information and finally if nothing no other automation helps you you could just create an entitlement using a form so there are various ways in which you could do it and today we could we'll probably look at two or three ways in which you can we can create entitlements inside yeah yeah let's do that and while you're bringing that up you know i'm just going to summarize what i heard you say so the biggest challenge in entitlements is gathering the the information right it's sometimes it's a very decentralized um world out there with entitlements things floating all over the place uh but we've developed different ways that you once you've collected all that information how you can upload them so i'd like to double click on that shankar do you have anything to show us yeah sure so let me uh share my screen here [Applause] and can you see my subtracted overview page i do i see it alright so this is the landing page when you log in to sam and if you are on the software asset management workspace so you get this landing page where you have this great entitlement ui action available you can also go to the operations license operations module where you can see the entitlements list view and you can create a new entire comment using the new application there so today for this demo we will do it from the software asset overview page so when you click on this ui action sam pops up a window that provides you with three options uh the first one is your guidance step-by-step blog or what we call as entitlement playbook the second one is importing entitlements in bulk using the spreadsheet and the last one is what we call as the simple standard form which allows you to enter an entitlement field by field so we'll first start with the guided step-by-step walkthrough you select that option and you click on next so sam then takes you to a page that renders with a few stages each stage specifically about how you create the entitlements the first stage it collects information about the software product for which you want to create an entitlement form the second would be the actual entitlement details in terms of the rights purchased third you will provide additional details that you may use that would be helpful for your reporting purposes and then you would review and submit so the first stage when you get in the first question that uh sam is asking you is whether you're going to set this up for on-premise or sas so you could set it up for on-premise um and the playbook could take you through the steps that would that would require you to do one promise if you choose sas then the first question that it's going to ask you is whether you've already set up the integration profile so that sam can download the data from the sas product windows portal and be able to guide you through the remaining process so for this demo we'll go with the on premise and we will complete this step the next question that sam is asking you is the publisher part number this is a very important aspect of license management in servicenow software's advancement because there's some content that we publish we tie a lot of information around what we call as a publisher part number this is this queue that your publisher will provide to you when you purchase software licenses from the publisher and i am insisting on the word publisher here because you could get publish you could get part numbers from your resellers as well software resellers also issue a part number but that is not the part number that we use in sam we go with the publisher part number that the publisher issues and if you are buying your purchase licenses from your resellers then please insist on getting the publisher part number that those softwares are associated with yeah so i'm just gonna i'm just gonna highlight that piece because that's that's really important right i mean i've dealt with customers that say hey i can't find this part number i can't find this publisher partner and bring your content and oftentimes we ask okay what's the part number and it ends up being the resellers part number for that that product not not the direct publisher part number from the actual vendor so that's important right our content is tied to the software vendors part number not the resellers part number and then you said another thing that was important to sean carr you said the publisher part number is important because it generates the software model which we'll get to later but it generates a lot of automation in the back end so i would say maybe anytime you do entitlements having the publisher part number is is is extremely important it's probably one of the preferred methods of creating an entitlement would that be correct that is correct it is the suggested way of creating entitlements in sam because as you said when you use the publisher part number sam knows all the content that is surrounding that that particular software it is able to create the software model it is able to create the downgrade uh items it is able to specify the lifecycle events so all all that information is is published in the sam content portal and the ppn is that uh you know tool that you use to pull all the data out and create your entitlements and software models so it automates the entire process you don't have to do much after you use a ppm if you don't use a ppn then you'll have to set up most of the things yourself you'll have to ensure that you use the right d map and and a lot more things happen when when you don't use the people [Applause] so we'll complete this step and move to the next one which is specifying the actual publisher part number [Applause] you will see that on this card there are two fields one is the publisher part number is a software model both are required fields but we will specify the publisher part number and as i said earlier this is the number that sam uses to identify the software so when i specify the ppm sam looks for the nearest matching software model for this particular ppm if the software model doesn't exist then sam automatically creates a software model and populates it here so in that case you had the publisher part number and because we have it in the content it's able to identify the software models associated to that partner that is right if the publisher part number does not exist then we suggest that you create a support request with the sam content team and get it added so that you can use the vpn to create the entitlement that's that's the preferred route that we recommend to our customers so once we have identified the software product for which we want to manage licenses we now specify the entitlement details using the information that is provided some of the values are populated here and choose the remaining information here the reason why license type was not properly populated is because some customers buy visual studio this is a visual studio uh vpn so they buy it as a subscription uh some customers buy it as perpetual from microsoft so since both are available we do not repopulate it here otherwise you will see that license type and license metric also are populated based on the vpn that is provided [Applause] so once you have specified the license metric the next is to specify the number of writes that you have purchased and complete this step now these two steps are sufficient for you to create an entitlement however we also have another stage where you specify other details you could specify the company location and department uh for which this entitlement is uh associated with so if you want to restrict the entitlement to be used by a specific department or for a specific location there are certain instances that we have seen where you have some legal restrictions on using certain licenses outside a country so you could specify the country as a location and restrict the entitlement usage there and you could also have multiple companies defined within the organization so you may want to restrict the usage of the entitlement to a specific company so you could you could restrict the usage based on these and these are all not required please if you want to use the entitlement for these you could and once you have specified these you could complete this stage and go to the next task which is to specify who is the owner of this license this is typically somebody who is actually owning the budget [Applause] and then you also specify the finance aspects from whom did you purchase what invoice was used to pay this pay for this license uh you can also specify the gl account or the cost center so these are various fields that are provided on the entitlement that allows you to define where the entitlement is being used so all this can be used when you generate your reports you can see how your entitlements are being consumed by various cost centers and by various locations or country etc so you could use these for your various reports and then finally we have the contract details that can be entered as well we will skip this as well and now that we have specified all the information required to create the entitlement we are actually good to go but we would first review what we had entered in the review stage and if you want to make any changes you could do that here and once you're done you click on finish so the entitlement was created in real estate and you are redirected to the entitlement from the playbook that guided setup is really designed for someone that is maybe fresh to importing entitlements or wants a little extra guidance around how to go through the proper steps but you're saying once they've once they've done it they can actually access the entitlement record itself which is what you're showing now and i'm guessing they can review it one last time before they actually publish is that is that what happens next uh more than review there are also other um edits that you could do so you may want to do your user allocations here which ensures that this entitlement rights are consumed only by specified uses or at least preferences given to these users you can also review the expense lines which are interfaced with your gl you can verify your downgrade rights that are populated here if you have longer text defined and and then once you're fine you can see the state is built which means this is still not consumed by your reconciliation process so once you're comfortable with all that is here on this entitlement you can choose to publish this so when you publish this entitlement state changes from build to in use so now exactly yeah so now it's active in sam yeah it is active inside so it now it gets consumed by your cancellation process so the new state uh also there are some conditions so if it is a perpetual license then it becomes in use automatically if it is a sas subscription with a start date that is in the future then this becomes on order and it automatically changes to in use on the date when it is active so so all those aspects are handled as part of the entitlement form but you created this using the playbook so you can see that in the activity stream as well entitlement created using guided workflow so you can use this information later on if you want to do an audit on any issues that you may have with your attachments so this is with how you create using the guided setup now let us go back and see how we can import entitlements for the sake of a demo i am taking a taking a spreadsheet with only two rows but typically we have seen that your species may have thousands of rows as well if you are importing for the first time there are two types of input that you could do the standard import document is to import any kind of entitlement but if you are specifically looking for your microsoft mls statements then you could import that as full and sam automates the process of creating the entitlements and even the contracts behind those for you so the entire process of importing your microsoft licenses can be automated using the mls for this demo we'll go with the standard import document you can download the template for this from the ui action here populate the template with the entertainment details so i have two roles in this entitlement as i said earlier so it's uploading it now so again uh there's a difference between what we had till paris and maybe till rome and and in san diego and beyond where we changed the import uh functionality from a synchronous process to asynchronous so you don't have to necessarily wait to upload the entire uh set of rows in the entitlement and get them processed you could click on import and it submits a background job and you could you could come back and check for the status of that on the software asset audio so i will click on import here now and it has been submitted and you can actually go back to your software set overview and if you refresh this page you will see that there is a new new alert and a new notification for the spreadsheet import job that was completed the reason why there is a new alert is because there are actually two errors and this is the completion notification which says the end port was completed but with errors so let us now go into the import errors to see what import errors were identified by the import process so there are two here and we will take a look at one of these so if you see the [Applause] error here you see that the publisher part number is incorrect and sam automatically says that if you if you do not have the right publisher part number you might want to probably create a custom vpn and still upload this entitlement otherwise you could just delete this and choose to import without the publisher part number now what sam does is it tries to identify the closest software model and then creates the entitlement and associates it with that software model so this is the entire element that was created let's now go back to the import record here you will see that one entitlement has been created there is one more error which you can still go and review and import that as well we will now open this and see that this is doesn't have a publisher part number but it has identified that this is a software model that matches the entitlement record to the maximum action so you could actually look at publisher product printer and edition to match this so that's the other way in which you could uh create entitlements by importing them in bulk using the spreadsheet and the last option is your form standard form we have already seen this when we saw those entitlements but when we go here we could see that it has all the fields that are needed you could specify the ppn here and it would automatically populate some of the fields as you can see the metric group changed from common to microsoft this changed from perpetual to none because of the reason i already mentioned earlier and then we could continue creating the entitlement like we did before so that's that's what i had as part of the demo for these three different ways of creating the attachments yeah yeah three different three different methods right so the guided setup gives you the play-by-play so to speak the the the bulk file import you know gives you the ability to include a lot of different records um you might incorp you might uh might have some issues or errors from time to time so you'll be able to troubleshoot those but that's part of the practice of uploading entitlements and then individual entry that's great thank you for sharing that sean carr um now you know you've been you've been in entitlement in titans for quite some time here with the with the product development and things like that so if you were to summarize leading practices around entitlements um what would you say are what we call our eight leading practices so uh essentially what we have seen is uh customers who try to structure their import in patches or in phases uh they are far more successful so you could split the you know when you're doing it for the first time you may have uh hundreds of thousands of entitlements so if you split them into batches say publisher like that so you may have one patch for microsoft entitlements you may have another for oracle so if you split your entitlements into different patches and do it one at a time that actually helps because some of the issues that you face when you import for the same publisher would be very similar so it would be easier to successfully uh you may also want to gain a you know experience and uh in a variety of important things so you could uh import it in uh you know split the entitlements import it and then you could also have other import methods like importing from your purchasing systems getting the data in so it's essentially get the data into sam so that the rest of the automation process is handled by some and once you have identified the entitlements to import please have a very good plan to ensure that you are you're having a structured way of loading the information and after you load the information into sun you have a way to verify that all the entitlements that were created the software models that are created they are all accurate because the data that is that is that is entered in the entire elements on the software models these are used by your reconciliation process it would impact your license consumption it could also impact your compliance position so it's very important that you ensure that the data entered is accurate leverage the ppn as much as possible we've already spoken about this all the sam content data is structured around the ppm the dmap the downgrade rights the life cycles everything is structured around this so it's it's best to use the vpn because it automates the maximum extent possible again when you are importing entitlements for your on-premise applications you would create the entitlement and using the vpn wherever possible it automates separation of the software model and then you can start discovering your software installs to ensure that your reconciliation process can match the software installs discovered with their title on the other hand the sas works in the reverse order you first configure your integration profiles you download the data from your sas vendors portal and using that information sam creates the software model and you define that entitlement for that software model so it's it's kind of a reverse process and we have we have seen that this actually makes it a little more accurate because the data that you get from your sas vendors portal is far more accurate than what you get from the license uh documents that you have the purchase orders and other documents uh contracts this works better yeah so let me let me double click on that so i in on-premise world if i have software i'm going to load my entitlements first and then it's going to generate the software model and then i'll worry about linking those to the to the um installed software if you will if it's sas it's the other way around i'm going to link up my sas integration first pull in all the subscription data and it's through that ingestion of data that my software model has created and then i can associate entitlements to that software model is that what you said yeah okay okay okay great uh we we did see about uh user allocations uh i mentioned that user allocations helps you prioritize who consumes the rights first similarly you can also do your device allocations for those entitlements where you use per device or per server license metrics so you ensure that those devices can consume the rights first before other devices can see them install condition this comes into use specifically for software that you want to control on where it is being used and how the lights are consumed one example that i have is microsoft visual studio which provides you access to some 400 500 different microsoft products but with the condition that you can use those products you can install them and use them only in a development or test environment if you use them in a production environment then you are not compliant it is not just a production environment but even if it is on a pm or a server with two vms where one vm has a production instance running and another vm if you install the software using visual studio it is still a violation of microsoft's terms and conditions so you would you would have to be very careful where it is consumed so use install conditions to specify exactly those software models uh those are those devices which are either development or test test environments and you do not consume those rights for any other environment yeah this is great i think we probably should just uh just jump right into some questions that are about things we just talked about and a few questions from earlier it might even be better to answer some of these questions by pulling up uh just a a blank software entitlement form so if you wouldn't mind shane carr go ahead and take the screen share back and i'll ask you some of these questions i'm seeing come through um but yeah just pull up a basic uh you know kind of a manual entry uh and we'll go into some of these questions so um so i i think i'm gonna take these in a few different orders here so sean asked a good question what we just said was hey it's better to get entitlement data in there before you start pulling in those uh on-premise installs so his question is kind of the opposite he says well if we're already discovering on-prem software um but we haven't loaded entitlements should we delete the install records or or something else what what's our recommendation if you're already having installs created but haven't done entitlements yet yeah you wouldn't need to delete them um they would still be there and you'll have to ensure that the sam background jobs run so that the discovery models are created uh using the information on the install records so you can't stop but you don't have to delete them and rediscover them that is not required but it is just that when you are doing it for the first time the processes you define the entitlements the software model then you discover and then it works yep okay and so this is uh brings me to the next question is we talked a little bit about using tpn a really good question came through a little bit ago from teresa she says you know some smaller companies don't have uh publisher part numbers and so what would be our recommendation here if you know uh you know should we create a manual or custom uh a custom software entitlement or custom part number so can you maybe speak to what if we don't have a ppn do we need to provide anything to content team to help them create that if you do not have a ppm then you cannot use it but you'll have to ensure that at least the software model that you'll be creating you are using a d map that is published by the sam content team so if you do not find a d map that matches the product that you purchased then you would probably want to raise a support request with the sam content team get the dmap added and then use that to create your software and sometimes if if the very specific part of the software you know if it's not listed anywhere publicly uh just be prepared the content team might ask for verification like for example uh you know a purchase record or something that that where the you know the vendor you bought from is showing or describing the software that's kind of proof that this product really does exist so just be prepared for that too but let's on this demo here can you just briefly touch on um there's some questions around you know what does software look like entitlements like with maintenance um so can you maybe just pull down those examples again on on the license detail for perpetual or maintenance maybe talk about that for a minute yeah so you could create the entitlements for maintenance type as well so the license type you have perpetual plus maintenance where you buy the perpetual licenses ibm typically provides this where when you buy perpetual licenses you also buy the maintenance and the maintenance is for a period of one year for the first time so uh that's that's the purpose of plus maintenance and then when you renew your maintenance because the perpetual license was still with you then you would use only the maintenance type yeah so you could use these two to define your maintenance okay and you know that kind of brings us to a question um someone was asking here the the what's the license type you choose if the entitlement uh is for a subscription-based software but with maintenance and software assurance keeping in mind that when you say when you say subscription that there's a purchase method and there's a software delivery method if the if the software delivery method is installed but they're selling it to you through like a subscription payment method which for example adobe great example it's actually an on-premise software product they can say cloud all day long but as long as it is installed and deployed with an install that's a great example but i think with with microsoft you're also alluding to that question about software assurance so most pure sas products there's no such thing as software assurance as long as you own an active license they're going to push updates all the time and you're entitled to those updates unless it's a whole new product so maybe sean carpe just touched to the the question of what if i've got like office 365 or i've got an install that that still has maintenance yeah you could define the agreement type here uh this is not populating here because of the data here but you would see the software assurance pop-up here as agreement type you so you could choose that and then you could choose to define your license type as perpetual or subscription based on the type of licensing that you have you can choose microsoft here and you would choose uh when you choose perpetual you'll get various uh per user per device etcetera that's right and you choose subscription you are restricted to only uh i think yeah it's that's the friction here it's kind of some different details there yeah yeah and i will i will say you know peter asked a question about you know what is the guided setup look like for a subscription product we're just gonna point you to uh you know to actually you know make that integration happen first in guided setup so that's the biggest change is we're pointing you away to do some work before you pull in the entitlement which is fine um so i think yeah you you touched on that but if you just if you instead of on premise you have subscription you'll see kind of the experience kind of change and uh and shankar is pulling up right here um so yeah that's just a good example again we're trying to guide you through the best way to set this up so if you said it was a sas product you'll notice that the the steps will change to kind of focus on you know pulling in that data from the api integration which you can see right here if it's been set up then great but if it's not we'll probably move you towards setting that up um that is right so if you choose no then it would ask you to first set it up before you proceed with the creation of their pattern if you say yes then it will ask you to choose which type of integration that you have set up directors sso and based on that you choose the integration profile when you choose the integration profile then it will provide you with the software model that is associated with this entitlement that's right that's right and one other question that just came up was um what if you don't have a ppn and you're trying to find the software model this is probably i'm guessing this is back to that page we were just looking at uh shenkar like just the blank software entitlement form um and someone was asking how did you pull up the software model if you don't have the entitlement do you just search for it there or how do you get to it yes uh you you can go here and search for the software model if it has already been created if you do not have the vpn then there's quite likely that the software model is also not created so if that is the case then you have to go to the license operations module create a new software model and then come to the attachment form to select the software you could just pop this up and if it's already existing you could choose a software module that's excellent cool excellent great so good um oh i do see one other uh question here we'll try to get to is there any way to connect the retired entitlements to the current entitlement especially within the current comment record what do you think shane carr i don't think you can add them but if you have created a new maintenance entitlement from an expired maintenance entitlement or if you have upgraded then the related entitlements are automatically added to the new entitlement similarly if you create a reserve entitlement for office 365 the reserve entitlement will have the original attachment as a related attachment so those are automatically added by sam but you cannot explicitly add that feature that doesn't exist here yeah and and lisa you're asking a good follow-up i'll go ahead and put this in on the adobe question there are customers some customers that still have adobe installs that they're paying for and they're tracking maintenance and upgrades on them so if you still are you know you have some of those licenses kind of legacy licenses that you're you're tracking those would be on-prem and perpetual but um most of the customers have been kind of you know pushed over to the subscription model and in that case again you're not you're not tracking the maintenance costs on it because generally speaking again you you're you have that um you know all apps are single apps license which entitles you to any any of those versions down below so again it's different if you're primarily on the subscription model with with adobe that that would be a specific example we can go offline more on that if you want but that's the short answer and uh yeah and we're going to go back and kind of a lot of great questions but let's get into this next phase if you um shankara i'll steal the share back and we'll talk about what's the difference between software models um and discover nd maps we keep talking about d maps or uh uh you know these discovery models and that's basically a dmap is the same thing as a discovery model so victor i'll hand it back over to you yeah thanks patrick so shankar let's let's go into kind of the the data schema behind sam and interchangeably a lot of folks talk about software models discovery models d maps there are differences between them i just want to learn from you directly how would you define a software model what is it and what's what are some important attributes associated to software models let's start there first yeah software model is that entity in sam that represents the product the software product that you are trying to manage its licenses so when you when you define a software model you're identifying it as you know the publisher is adobe the product is creative cloud the product type is licensable uh and version is uh because it's a sas product it's anything if it is office 365 uh it will again be anything if it is microsoft office you would say versus 2016 so you would specify exactly all those attributes of the software as part of this software model so define the product essentially in addition to identifying what the software product is the software model also includes other information like your if it is a suite for example it would have all the sweet components obviously 65 would have all the other office products including your access database and depending on the plan if you are an e5 plan you get access to a lot of other microsoft products as part of obvious 360 by subscription so those will be added as sweet components similarly visual studio will have 400 plus suite components so those are also specified on the software model the software model also specifies what are the downgrade rights applicable what are the life cycles that have been defined by the publisher and all that information is also populated as part of the software model that is all this information is used by your reconciliation engine when it tries to reconcile the software installs and consume the rights based on how the software model is defined so if you have an attachment defined for office sql server 2016 and there are downgrade rights covers for 2013 and then the reconciliation reconciliation engine would know that it can cover the rights for the downgrade rights assessment so that information is all available as part of the software model so the software model contains all of the attributes associated to that particular product title title and edition it's coming from content if you will is it something that you would you would have customers create on their own or is there is it is there a way to say you know use the one that comes out of content first and then if you need to change anything to software models then you can do that is that that kind of the way to do it yeah it is it is recommended that you use what comes from the same content so if you use the ppn then the software model is automatically created using the vpn data and you use that software model if you do not have a vpn then you will have to define the software model using a d map the d map is again published by the sam carter team if you use a dmap then all the information that i just spoke about they're all auto populated if it's available if you want to create a software model from scratch without using a d map then you have to define every single component and that is more likely to lead to errors and your complex position could be errors got it got it let's transition then to discovery models and can you define that for us and help us understand what's that all about yeah so the entitlement of the software model or on the or one end of the spectrum of your software license management sam the other end of the spectrum is on the discovery side where when you discover install records using various tools it could be discovery it could be accm it could be jamf so when you discover all that information as mdp is populated the install records are then processed by sam to create what we call as discovery models as the name suggests these are this is a model that is based on the discovered records so what you see on the right hand side on the screenshot are the values that sam discovers from the installed record so that's why it's a discovered publisher discovered product based on the publisher they have different ways of signing an install record so the information is populated based on that but then for us to be able to map this to a software model because we need to end of the day consume rights from the entitlement that's on the software model really normalizes data that so the normalization rules are published by the sam contact team again that normalizes the discovered value to what has been defined in the software library so you can see here that oracle is normalizing itself to oracle but the database server enterprise is actually normalizing to tv product for the db server as a product and enterprise is actually the edition so it actually splits the data into two different fields similarly 12.1.0 is the discovered version that is normalized to 12c so this normalization rules are all published by the sam content team and that helps the sam to normalize the values that is discovered and once this once the discovery model is normalized then it is able to identify the d map that is associated with this discovery with the with these values of publisher product version edition language etc and associated itself with the software model so once that link is established then the entitlement the software model the team app with the discovery model the uh install records they're all linked and the linking factor between these two extensor extremes of the spectrum is a demand got it got it yeah we actually had a live event last week i believe it was where we talked about normalization and how that works so i appreciate you doing a quick summary of how that's discovered and what's used in terms of normalization this next slide that we have talks about that spectrum that you that you uh you spoke about so on one hand on the left hand side you have the entitlements and on the right hand side you have the software installations and in between you have the software model the discovery model and the discovery map so it looks like that connective tissue is the discovery map and the two data points coming in from the left-hand side you have entitlement records which you showed us today and on the right-hand side you have software installation data that goes through its normalization process and eventually they connect and so that's how they're interconnected right could you show us in the product how that how they're interconnected [Applause] can you see your screen yes okay so this is an entitlement that has been defined for windows server 2008 r2 standard so when i open this entitlement you will find that you know this is actually defined for a software model which is for windows server 2008 r2 let me open this software model so from the entitlement i can navigate to the software model you can see that this has a lot of attributes defined i think this is part of a cis instance so this does the parent as well let me go to more and you can see that there is a matching discovery model for this software model so when i click on this the related list opens and i can see the matching display models typically if you have many install records across various versions uh you will see many discovery models here so i click open the discovery model now and you can see that this is the discovery model which had these values so you can see the discovered publisher was actually microsoft corporation now this gets normalized to microsoft which is the value that we have in our libraries similarly the discovered product is this it gets split across this windows server as a product version is 2 000 r2 additional standard so this this is how the normalization happens and once it is normalized then all the install records that were used to create this discovery model now these are associated with the software model so when the entitlement when the reconciliation runs the entire human rights are consumed against these devices for these installations so this is how you you can see that all these entities which are seemingly you know on their own but they are linked because of that dmap that is used to link all these entities that's great so the publisher part number creates the software model and the installation records create the discovery model and the dmap and that finds the software model and it marries those two entities together so that when you're running reconciliation you are correctly assigning the right entitlements to the right installations [Applause] that's fantastic i see a lot of questions coming through um let's take a look at some of those okay let's jump right in with uh this this kind of basic question from sharon about um who uh well her question is what but i think the other part of that is who sets the normalization rules between discovery model and the software models uh so shankar do you want to speak to that yeah it is a spam content team so what we have is a way for customers to opt in for the sam content service so when you create a new when you bring in your discover your install records and the discovery models are created these get normalized by the out of the box normalization rules that are available sometimes some of the values that are discovered they wouldn't get normalized because we wouldn't have encountered those earlier so when those discovery models are identified they could be in partially normalized status or they could be in manually normalized status when when you when these discovery models are identified if you had opted in for the sam content service the information about the discovery model and the values that have been normalized and not normalized these are sent back to the sam content team and they review it and when they realize that there are some normalization rules that are missing they create these normalization rules and they republish them back and when the when the next content download happens in your instance the new normalization rules are downloaded and you are partially normalized or manually normalized storage models become fully normalized so that's that's how uh sam content team discovers new uh normalization rules based on customer usage that's great um okay and and yes i think um the when you say software asset management content you know the content service every customer that software asset management professional and enterprise that's the product we're talking about today those customers uh automatically get content from that team so even if you don't opt into content um you you like don't opt in to share uh your content you just want to receive the out of box matching and models you'd be able to interact with that content team out of the box that that would turn on we talked about this in activation plug-ins in a previous live event so yeah the opting in just means that you're sharing some more information with them and you're you're willing to uh to basically let them look at your data um and and be able to improve the content service based on the specific data that you want to provide to it so um to share and you can find out some more by looking at our previous live event on that topic i want to go to this next question uh from princess here she says i know we can create custom d maps how do custom d maps affect software entitlements and how is the information uh in the software model updated with that custom dmapp so when you create a custom dmapp sam uses the information that you have provided on the custom demand to create the software model for you and but unfortunately that software model that gets created would not have all the other details that typically happens when the sam content team publishes them the downgrade rights and those may not be populated so you'll have to still create the software model edit them add all that information that is that is required for the software model and then you create an entire event use this software model as a reference on that entitlement and create it so then you should be able to start using that okay so the only difference is how the software mode is created otherwise the process is still the same okay excellent and then i see one final question here which might be a question a little bit more for the strategic portfolio management business unit um because it's for in relation to their products for business applications um so her question is what makes an application a business application should all service models be part of the business application table so that's just a if you want to speak through that shin car you can or else we can um you know point point uh over to that other uh team to answer that yeah this is an apm uh functionality so you can use sdm to define the business application but i don't know the details of how the service models are part of the business yeah yeah so we we bring in the software uh model uh uh in particular the life cycle dates that really make tpm very helpful and valuable so hopefully that something you can follow up with your account team and get more information on um so great i just see a new a question coming in uh from alicia we have a few more minutes here any final questions get those in here so the question here is is the content library um more usable for different industries do you want to speak to that of shankar um not really the content the same content is actually industry agnostic it is essentially it covers software applications that are used across various industries and it doesn't really make one industry the content being more useful for one industry versus another it's the same for all it depends on the type of applications that are being used uh manufacturing industries that may use more of engineering apps applications they would see they would see that the content still contains all information that they would need to manage their engineering applications so it is it is diagnostic of industry and as your follow-up question kind of indicates alicia we do have a lot of very large uh healthcare systems that are using our software today um and have have seen lots of again their healthcare software covered the bigger issue we find is when you have companies that you work for that create a lot of their own software their custom software or they use a lot of open source software so it's a combination of open source and custom that's where you run into more of those issues so hopefully that gives you a little bit more color it's not necessarily industry verticals it's more about how custom is it and is it is it not even in the market which is it's it's valid to track that just not something we're gonna have out of box obviously um so hopefully that is uh that's enlightening there i see your responses that's great um yeah i think i'll go here to uh let's see here um luis last question we'll answer which model which application service software hardware uh is there a script called and there's a specific script called the product model assignment uh which is set to true can automatically create the model based on business applications so there's some very technical questions luis you should probably go ahead and bring up with your account team um we'll probably get a little bit too detailed here for that um and um last i guess this is the last one princess will give it to you the ppn is not entered will the downgrade rights and life cycle data still be able to populate i think in shankar the answer is no would you confirm that yes you it would but if you have to use the right d map if you can pick the right team app then you will be able to create the software model and and the data will get auto populated the bpm helps in identifying the right demand so that's where you are recommended to use the people yeah yep that's excellent well great and yes we talked a little bit about the um um james as well just being able to to automate this process by pulling in software entitlements uh you know through procurement systems we see a lot of customers doing that as well so i think with that victor i want to hand it back to you what resources do we have to make this easier for customers um after this uh this live event for them to go and maybe learn more yeah well we have a lot some of those are just highlighted here for everybody we spoke to some of these or we've gathered information from some of these so if you want to go more in depth from a user guide perspective a white paper perspective we have the import entitlement user guide that is really going to summarize everything that that shankar demonstrated today and talked about with some some key uh examples in there as well there's a couple other white papers i would just highlight one about keeping asset data accurate by tracking your software entitlements that's just a nice story if you will around that but then there's also a lot of customers migrating off of flexera into servicenow and so how do you do that and we have a lot of best practices around that as well as some step-by-step instructions on how to do that and then shankar did highlight more specifically around microsoft visual studio how to do license management for that with respect to an emphasis on managing the software models and the entitlements so that is something that we're also going to be posting when we post this recording uh in the community and then it goes without saying but training is always very very crucial and one of the best trainings that we have out there right now is import basics for software asset management which is free of charge it shouldn't take more than about 20 25 minutes max and there's also some embedded content in there that allows you to download some cheat sheets along the way and last but not least the item community that is our central hub where you're going to find all of our content all of our information we have our getting started guide which i i tell people is our central compass or central focal point to start there you're going to have a summary of all the information on how to set up for success but then we also have a library of documentation and links to trainings that we've we've shared in the past so that's a good place to segue and start when you're going to start your journey so with that said i think it's now a good time to just say goodbye i want to thank everybody for joining us shankar really appreciate your time again i know you're on the other side of the world so we really appreciate you helping us with this patrick kudos to you thanks for helping me with all of this as well and to everybody that's out there great questions we really appreciate the feedback and we'll put on more of these hitting on different topics so we hope to see you more in the future thanks everybody everyone have a great week [Music] foreign [Music] you