The CreatorCon Call for Content is officially open! Get started here.

Defining Model Categories

Steve Gyure
Tera Contributor

We are in the process of migrating to HAM.  As we work on importing asset data from our previous system, the question has come up concerning the definition of Model Categories and getting configuration item records built in the right CMDB class. 

 

Our implementation partner insinuated that we should only use Model Categories that come defined out of the box.  However, that limits us by lumping several pieces of IT-related hardware together in Network Gear, or simply in Hardware within the CMDB.  Some examples would be trunk cables, server racks, and network cabinets, just to name a few.

 

What is the best practice in this case?  Should we simply utilize the Model Categories that exist as out of the box?  Or should we go ahead and define new Model Categories for Cable, Rack, and Cabinet?

 

Thanks for any input,

Steve

1 ACCEPTED SOLUTION

Ashok Sasidhara
Tera Sage
Tera Sage

Use OOB model categories as much as possible. Model record can be used for more granular information about specific types of devices belonging to model categories. Custom model categories should only be created when you don't find any suitable OOB model category and also if there are a lot of devices belonging to such a category which is not available OOB. 'Rack' has an OOB model category which you can use.

Install the latest version of 'Expanded Model and Asset Classes' plugin to get more number of OOB model categories on the instance. 

View solution in original post

2 REPLIES 2

Ashok Sasidhara
Tera Sage
Tera Sage

Use OOB model categories as much as possible. Model record can be used for more granular information about specific types of devices belonging to model categories. Custom model categories should only be created when you don't find any suitable OOB model category and also if there are a lot of devices belonging to such a category which is not available OOB. 'Rack' has an OOB model category which you can use.

Install the latest version of 'Expanded Model and Asset Classes' plugin to get more number of OOB model categories on the instance. 

Thank you for the confirmation, Ashok.  That was my assumption as well, but wanted to have someone outside confirm it for those in my company who did not think we should ever code custom ones.

And yes, my examples of Rack and Cabinet were bad examples as both are actually supplied.  Cable is an example of one that is not currently provided OOB.

Essentially, we are going to go ahead and define categories for CI classes that do not have them, if we specifically need to put something there.  Down the road, if ServiceNow adds those categories, we will deal with them as necessary.