Product Model with option(s) in HAM

[Ed Laar]

Hi HAM people,

Some manufacturers are delivering equipment of a certain product model with a different selection of options but: with the same Product Model.

Example: A laptop with the same specs without a camera has the same manufacturer product model as the same laptop with a camera.

An other example regarding the memory size or disk capacity: Same manufacturer product models but in fact different equipment.

What is the best way to deal with this? Compatible models or Substitute models? Simply ignore such options (in my opinion a bad solution) or create 'custom' product models to defer the models with their options? Create a customization to be able to register the options separate from the manufacturer product model?

How does Product Model Normalization deal with this?

Looking forward to your reactions,

Cheers,

Ed

[Saiganeshraja]

• Use Configuration Management Database (CMDB) attributes: Store options (RAM, camera, etc.) as attributes on the Configuration Item (CI) representing the specific product instance, not as separate product models.
• Maintain a base Product Model: Keep a single Product Model representing the general type.
• Leverage Option Choices: If applicable, use ServiceNow's option choice features to standardize attribute values.
• Prioritize CMDB normalization: Ensure attributes are consistent and accurate.

Essentially, use attributes to differentiate configurations within a single base Product Model, aligning with ServiceNow's CMDB-centric approach.


Mark correct and helpful.If it helps.

[JolieG]

i'm not sure if your examples work like ours, but when we've seen this, they have different model numbers. we've included the model number in the model display name to help us differentiate them.