Is Discovery Tool supposed to create hardware models or "product models"?

[bjmcdonald]

Is Discovery Tool supposed to create hardware models or "product models" when it discovers a new item that is not set up as a hardware model?

Seems that both our bulk load processes and discovery processes create "product models" - and do not associate the model category and such when it runs and doesn't find a match.   Can someone explain how this SHOULD work - and maybe point me to some recommended governance on models / model management, please?

[cyked]

Hi Jake, any idea what the proper action would be in cases where the information returned from the OS on model and manufacturer is diffent than 1) what is already in asset/CMDB and 2) other machines of the same model?   Example: we have a model for HP Elite 8300 desktops.   We have a small number of machines that report the model as "HP COMPAQ ELIE 8300" and the correct info is "HP Compaq Elite 8300 USDT" (notice the missing T).

Other common excamples are around company/manufacturer name difference.   HP.   Hewlett-Packard.   Hewlett-Packard (HP).   Is this where field normalization comes into play?   I don't see that we have issues with the model category or class (on creation) for Product Models, but the WMI OS info probe (or rather what is set on the computer it self) is causing us problems because we end up with NUMBEROUS models for the same thing.

[jake_mckenna]

for these types of issues i normally turn the Field Normalization to help me manage the models.

Field Normalization - ServiceNow Wiki

[cyked]

Thanks.   It seems though that even doing a coalesce function with normalization on the comany table to the name field that normatlization is more useful for cleanup activities where you have 25 HP companies to coalesce to one rather than a management tool/function.   If you have Dell, Dell Inc. and Dell Computer Incorporated and normalized to Dell, when discovery happens to craete Dell Computer Systems you have to go into normalization add that new item as a alias and run the new job, correct?   I

[jake_mckenna]

With Field normalization you can write Regex expression to match on so incoming data will get caught and converted and stop the need to run this as a manual job.In the past i have setup jobs to find "dell" in the name and convert it to Dell Inc. This would also sometimes need to be expanded out to model names that contain part numbers in the names too.

[bjmcdonald]

Chuck - it's actually a little of both.

Currently, for some reason, our discovery process creates "product models" and it doesn't update / identify the correct model category - so the CI / Assets are not created properly.   I'm trying to figure out if it is a problem with Discovery or if it something we need to update / configure in Model Management somehow.

In our current environment, we are lacking some controls / governance on data - and I'd like to figure out the right way to get this fixed.

Any help you can provide would be excellent.

Thank you,

bj