Model Categories - CI Class

ryanstefani
Kilo Contributor

We are currently resetting our ServiceNow instance, and implementing a lot of our modules along with developing new processes to ensure that we can support these modules properly.

Two of the key items that we are working on implementing are Configuration Mgmt. and Asset Mgmt. While we work on our processes, and implementation we are running into some issues/discussions around model categories and the role they play in this space. Model categories link a model to the appropriate asset class and proper CI Class, and according to ServiceNow you're supposed to create a new model category for every new cmdb_ci class.

If you follow that logic, and use the CI classes out of the box, you would have nearly 700 model categories. Additionally, it would not be clear what CI table you would be using associate the asset/CI to because there are multiple CI classes that have the same name. (example: Load balancer is extend off the base CI, and it also extended from hardware, computer, server, to load balancer). I'm assuming that there is some logic behind this, but I would like some assistance to understand that logic? Are there any definitions/descriptions around the OTB CI Classes? If you have multiple CI classes an asset could fall under, should you utilize multiple model categories?

Thanks for your help in advance

2 REPLIES 2

Simon12
Tera Contributor

Hi Ryan,

Were you able to get any inputs on definitions for OOTB CI class definitions and selection of model categories?

Niklas Peterson
Mega Sage
Mega Sage

Hi,

 

I would say that you only need to create model categories on the level where you want to separtate the models. If you have one model catagory and you are fine with presenting all models of that category on all CI Classes then it's an ok level. If you need to separate models on a sublevel then you need to create more model categories. Like a Server model category and a Workstation category model to differentiate between server and workstation models.

To create 700 model categories just because you have 700 CI classes seems a bit excessive to me.

Regards,
Niklas