Local types of assets (Assets and Consumables) - managing the Hardware Models

[janglabas1]

Hi All,

I'm facing the following scenario:

we have assets (laptops) and consumables (keyboards) that are ordered based on approved models (multiple models of laptops, keyboards and keyboard+mouse combos).

In most countries we have the same keyboards layout, however some countries (i.e. Germany) have different keyboard layout on both - laptops as well as external keyboards. We have more than 20 laptop models + number of consumable models in place. We don't have hardware model normalization module enabled. 

I need to ensure that:

1. We use/order only approved models (both consumables and hardware assets)

2. The keyboards are matching the local requirements (hardware is ordered globally)

I've tried to search on a web what's the standard way to handle such situation - are we able to break down the model into some sort 'sub-models' or do we need to create a separate model for each country (which would make it unmanageable as we would have hundreds models to manage).. or is there any other solution that would work?

Any suggestions?

Kind regards,

Jan

[Darkl1ght]

Hi Guys,

I have the same predicament. Went through all the posts on this thread, however, we have talked about Ordering and Procurement. That was sorted via creating a Catalog item for each keyboard layout mapped to one Model say, Latitude 5540.

Where I am stuck at is this - the customer do their billing by pulling data from ALM Hardware, i.e Model is referenced from the Product Catalog. 

So before creating the Catalog entries, we chose @Ed Laar Pt 1 route. Now, I have 30 different Product Model entries of Latitude 5540 cluttering the ProdCat. This approach was chosen almost 2 years ago.

Would like to de-clutter the ProdCat.

So, is there a workaround within the ProdCat for this ?