SIM Card in CMDB

cruz1
Kilo Contributor

Hi all,

Our customer wants to track the SIM cards in the CMDB associated to the mobile phones.

Is there any OOTB way to store this information?

How is this normally handled in other customers?

We are working with Geneva version.

Thank you for you responses.

1 ACCEPTED SOLUTION

antoniovegue
ServiceNow Employee
ServiceNow Employee

Hi Cruz!



It depends of how important for the customer is that information and also if they would treat that as an Attribute of Mobile phone or as a Configuration Item with it's own entity and attributes.



In the first case, maybe just a string to store the number would be enough.



In the second case, your customer may want to store data of the SIM Card like PUK number, Serial Number, Telephone number, owner, support groups and so on. In that case, you should extend cmdb_ci table to create your own class of CIs. This is a natural operation when implementing CMDB. Here you have more information: Create CI class



I hope this helps!



Regards!


View solution in original post

7 REPLIES 7

in cmdb_ci_sim_card class, we do not have ICCID number, whereas in cmdb_ci_handheld_computing class we have many relevant attributes to store SIM details. Which one is ideal to use for storing the SIM details?

 

Thanks. This was helpful. Just curious to know if there is a direct way to see the list view of SIM Cards through application navigator apart from CMDB CI table. 

You cant view the data in navigation, the only option is via table. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************