servicenows and professional normalization basics the outcome we're trying to achieve is to get normalized enriched discovery data into the instance for this example we'll use an excel sheet that's mainly uploaded to replicate what a discovery source would be or even a third party discovery source as well so in the excel file you see that there's three records three being the same product of microsoft project professional 2016 on three unique computers if we go to load the data we'll create a new table and we'll label it normalization test we'll select our file and we'll upload we'll select create transform map we'll label it norm transform the target table of software installations you can either put the table name or you can search it itself and then we'll do auto map matching matching fields installed on is installed on version version everything's matching up correctly so now we hit transform select transform again and then if you go to the software installation table you'll see that the values were just uploaded see how we just uploaded three unique records into the software installation table each one of these records though is the same product microsoft project professional 2016. again this is the base table of cmdb sam sw install if i go to discovery models you'll see one record that's because it's just that same product of microsoft project professional 2016. if i select the record you can see that the three records that we were previously talking about in the software installation table are referenced here this is because they all roll up to the singular product that we're able to put normalization rules around and enrichment rules around as well so you see here on the right-hand side is discovered publisher discover product and discovered version those are the raw data that's discovered from the third-party data source servicenow discovery or even the excel file that we previously uploaded so for this one we have microsoft in the left hand side we actually have the normalized values so it goes microsoft to microsoft that's one to one that's good in the discovered product field you have microsoft project professional 2016 enus so it repeats the publisher value that could be a problem later on we're trying to roll up you know what's included in our compliance positions what's including our software model so we want to normalize that value to just include project it even repeats even when it says the addition value in here so we want to make it a new field so we actually split that out and we put professional under its own addition value and then the version as well gets its own field here and then discovered version also gets the full version value there as well so that's the normalized data we also add enrichment data as well so is the product licensable is it free is it not licensable is it a child of a sweet product again all that would be included in the product type field and we also include life cycle data as well in the software model