Classifying Mobile Devices - use the Hardware asset class or create a new asset class?

[Bella4]

I am wondering how others approach Mobile Device management, and if they are classified under the Hardware asset class (default option) or if a new asset class would be recommended for Mobile devices? We currently have a Mobile Device model category under the Hardware asset class. Is there any benefit (or risk) of creating a Mobile asset class and moving them?

[Amarjeet Pal]

Hello @Bella4 ,
It is common to classify mobile devices under the Hardware asset class as a separate model category. You can also add custom fields to the Hardware asset table to capture additional information about mobile devices. Alternatively, you could create a new asset class for mobile devices if your organization requires more detailed tracking or reporting for these assets. The decision to move mobile devices to a new asset class should be based on your organization's specific needs and requirements, taking into account any potential benefits or risks associated with this change. It is recommended that any changes be thoroughly tested before they are implemented to avoid unintended consequences.

Just take care of the integration like intune their field mappings , rest I feel there is no risk.

Hope you find this helpful

Thanks 

Amarjeet Pal

[Ashok Sasidhara · Accepted solution]

The recommended method is to use alm_hardware table and the OOB model category named 'Mobile Device'. Important data from an asset perspective like cost, warranty, depreciation, contracts etc. are already available in alm_hardware. So it is better to avoid creation of a new class except if you require a lot of new attributes to be tracked that are relevant for assets (i.e. anything financial or contractual or warranty related).

If you are looking at tracking of technical & operational attributes which needs to be done in the CMDB, it is better to create a new model category for mobile devices (As OOB model category mobile device does not have a CI class associated with it) with Asset class=alm_hardware and CI class=cmdb_ci_handheld_computing so that the operational & technical data will be tracked in the corresponding CI record.

You can also use the OOB model category named 'Communication Device' instead which is mapped to CI class Communication Device [cmdb_ci_comm]. But this is not recommended if you are using or planning to use Service Graph Connectors to populate CMDB (As cmdb_ci_handheld_computing is the recommended CI class for mobile devices in that scenario).

[Bella4]

Thank you, that was helpful and informative

[Ashok Sasidhara]

I would like to add one more important point here which will be applicable only if you are using HAM pro. If you use the OOB 'Mobile Device' model category with HAM pro activated, there will be an additional tab named 'Mobile' in the form view of hardware assets. This tab contains attributes like IMEI, Carrier, Phone number, Service contract number, MAC address etc. which are important for mobile devices. So the best practice is definitely to leverage the OOB 'Mobile Device' model category for all mobile devices that will be managed as Assets (especially if you are using HAM pro or planning to use HAM pro in future)