For same Hardware model, can we have multiple Models by location wise

[Shantanu_99]

Hi All.

For one Hardware Model, we have switches in all 4 data centers. Currently only one Model is getting created and all switches associated with it are getting added to one Hardware Model through Discovery

E.g. For Hardware Model "Catalyst 3560x48P", We have switches in US,UK,Japan,Brazil Data centers. We have separate mid servers for each DC for discovery.

Client wants It should create four entries for Hardware Model "Catalyst 3560x48P" by DC and switches should be added to their DC Hardware Model.

How we can achieve this.

Thanks

[Mark Manders]

Why? If the model is the same in all countries, it is still the same model. You could add a country with it, so you have unique ones, but from a device point of view that makes no sense.

Look at it from a mobile phone perspective. If you hand all your country's VPs an iPhone 15, does it make sense to create 4 models of that? What is their use case?

[Shantanu_99]

Hi Mark,

Each DC wants to track their own Hardware Models for procurement purpose.

If I update country "USA" on Hardware model "Catalyst 3560x48P" then same model is used by other country. They will not be able track. This is the use case for them

[Mark Manders]

Procurement information can be tracked on asset level. A model is a model.

[Laveena-Agarwal]

Hi @Shantanu_99 

The Model table is a product reference (e.g., Dell Latitude 5440) and therefore does not have a Location field. Location is tracked at the Asset and CI level, since actual instances are deployed in different places.

With one model, you can still create multiple Assets/CIs across locations, each maintaining its own uniqueness (serial, asset tag, location, etc.).

Creating multiple models per location leads to duplicates, technical debt, and confusion.

Best practice: Keep a single model as the product reference, and manage uniqueness at the Asset/CI level