alm_asset or alm_hardware ?

[mathieu_brule]

Hi !

I'm actually working on a new project conception, on which we have to manage construction machines (like forklifts, ...) in a CSM environment. These machines come from another referential, we also have to import them regularly.

I can see that the related list "asset covered", on contrat form, points to alm_asset table.

I'm wondering where can we store these construction machines : alm_asset or alm_hardware, in term of best practices ?

In my mind, we should not use high level table (as alm_asset), for the benefit of lower tables as alm_hardware.

(I know that alm_hardware assets will be displayed in asset covered related list, my question is really in term of good practices).

Thanks for your points of vue.

Regards

[Saurav11 · Accepted solution]

Hello

alm_hardware is the way to go. Currently in our project we also use alm_hardware to save all asset details. Similar to how we use different ci classes in cmdb rather than using the parent table we should follow the same principle for assets as well.

Thanks

[mathieu_brule]

Thanks for your confirmation, Saurav !

Regards