Asset and CI Creations for Assets without proper model category

[Saurav]

There are a lot of devices/assets which are do not have a Model category example UCSC Devices , Netapp Storage Servers but need to have CI created in correct classes what is the best option around this

1. We have option to create custom Model Category 

2. Create via a different/any Model Category and remap/classify the CI to correct class ( which does not have a associated record in Model Category )- Need to understand if this will break the CI to Asset sync.

Thanks !!!

[Iraj Shaikh]

Hi @Saurav 

The best approach to handle devices or assets that do not have a corresponding Model category in ServiceNow is to create a custom Model category that accurately represents these items. Here's a breakdown of the options you've presented:

1. Create a custom Model Category:
- This is the recommended approach when you have devices or assets that do not fit into any existing Model categories.
- By creating a custom Model category, you ensure that the Configuration Items (CIs) are classified correctly from the start.
- This approach maintains the integrity of the CMDB and allows for better reporting and tracking of these assets.
- It also ensures that any workflows or automation that depend on the Model category will function correctly.

2. Create via a different/any Model Category and remap/classify the CI to the correct class:
- This approach is less ideal because it involves initially misclassifying the CI, which can lead to confusion and data integrity issues.
- Remapping or reclassifying the CI to the correct class after creation can be a manual and error-prone process.
- It is important to understand that remapping a CI to a different class should not inherently break the CI to Asset sync, as long as the relationships and field mappings are correctly configured. However, it introduces an additional layer of complexity and potential for errors.
- If you choose this route, you must ensure that the remapping process is well-documented and that any scripts or automation that handle the remapping are thoroughly tested.

In summary, the best option is to create a custom Model category for these devices or assets. This ensures that the CIs are classified correctly from the outset and maintains the integrity of the CMDB. It also avoids the potential complications that can arise from initially misclassifying CIs and then having to remap them to the correct class later on.

Please mark this response as correct or helpful if it assisted you with your question.