Best Practice for Hardware Models with Multiple Model Numbers

Maurice Murphy
Tera Guru

My organization is in the process of trying to get our existing hardware models to be in line with the hardware models we get from SCCM, and I as I have been reviewing through the hardware models we get from SCCM, I've noticed that certain hardware models will have multiple model numbers. Does ServiceNow have any best practices for hardware models that have multiple hardware models?

My immediate assumption is to create multiple hardware models which are differentiated by their model numbers, but I wanted to make sure we were approaching this in the right way.

1 ACCEPTED SOLUTION

Scott Halverso1
Mega Guru
Mega Guru

If you have HAM Pro you get three additional fields to help with the potential clean up/deduplication effort.  The below example is a model created by the SG-SCCM integration.

Normalized ManufactureHewlett-Packard
Normalized ProductEliteBook x360
Model1030 G3

The normalization engine plucks the information from the below fields. 

ManufactureHewlett-Packard
NameHP EliteBook X360 1030 G3
Model 

If you don't have HAMP, you often have to deduplicate the Manufacture, and then break a part the value in the name and put some of that into the model field.  The Normalization engine can take a 'basket of words' from any and all fields and get a pretty good hit.

I'm looking forward to the day when the Service Graph integrations and Discovery bounce first up against the Model content library, rather than normalizating in arrears and clean up yourself.  (MakeandModelJS API 2.0)

 

 

View solution in original post

2 REPLIES 2

Scott Halverso1
Mega Guru
Mega Guru

If you have HAM Pro you get three additional fields to help with the potential clean up/deduplication effort.  The below example is a model created by the SG-SCCM integration.

Normalized ManufactureHewlett-Packard
Normalized ProductEliteBook x360
Model1030 G3

The normalization engine plucks the information from the below fields. 

ManufactureHewlett-Packard
NameHP EliteBook X360 1030 G3
Model 

If you don't have HAMP, you often have to deduplicate the Manufacture, and then break a part the value in the name and put some of that into the model field.  The Normalization engine can take a 'basket of words' from any and all fields and get a pretty good hit.

I'm looking forward to the day when the Service Graph integrations and Discovery bounce first up against the Model content library, rather than normalizating in arrears and clean up yourself.  (MakeandModelJS API 2.0)

 

 

Community Alums
Not applicable

Hi Maurice,

Given that specific model numbers may have different lifecycles/pricing/region-specific info associated, it is best to have a separate hardware model for each model number. As Scott mentioned, it isn't always perfectly automated, so there may be some manual intervention to ensure that the model numbers are being pulled into the hardware model records correctly, and it's not just the model name field that is being populated with the Name and Model #.

All the best,

Stephanie