New Hardware asset record model category

ncp · ‎05-19-2017

We import hardware records and automatically create hardware assets from Dell's Advanced shipping notice. They have a Asset category defined as Desktop which I was planning on mapping to a model category of Desktops in ServiceNow. The issue with that is, this model category does not have a defined CI Class that maps to the asset class, so what happens is a CI is not created.

1) I looked to see if I could add a cmdb_ci_computer class to the Desktops category and I cannot

2) I would have to map the desktop to computer which already has that the ci class defined, the issue with that is I wont then be able to identify dekstops from notebooks or thin clients

Any ideas on how we can map and automatically create a CI for the Desktop model category?

The other question is why is the model category a mandatory field when creating an asset - the model already maps to the model category and if you go to the model its a slush bucket where you can pick multiple model categories

Thanks

Chandran

Community Alums · ‎05-22-2017

Hi Chandran,

I agree with the idea that these devices should not require their own classes in the CMDB. It can overcomplicate matters.

My recommendation would be similar to Andrew's with regards to using the Form factor, but I would NOT use the one that is available by default on the CI records. The CI record really is not the place for this type of information. It should instead be on the Product Model record (I would add it to cmdb_product_model; this makes it easy to display the value on the Asset and CI records if you want) and input the choices you want.

With this value set on the Model, you should have just a little work to identify the laptops, desktops, and thin client models. This should be pretty quick and painless to do in groups in the list view, especially if you focus on models in your environment.

Without knowing much about how you have the ASN details coming in, I would have these all point to the Computer as it sounds like they are doing. Then you will get your CIs properly.

A couple points about some of the information shared above:

While you cannot add a CI Class after a Model Category is created, you can add an Asset Class later.
Rather than messing around with the Business Rules and Script Includes that create CIs from Assets, use the Model Categories to support your work. If you do not want a CI created for a particular categorization of device, make sure you have a Model Category that has an Asset class defined but no CI class.
There is often confusion about the Model category on the Model records. If you consider it, it is likely that a Model could be associated with multiple Model categories. For example, that new ProLiant could be a Computer or a Server or a Windows Server or a Linux Server. In fact, in the course of its operational lifecycle, the device might go through several different categories. The Model category just helps when you are creating the asset to limit the Model selections. When the Service Catalog is used, the first Model category on the list is selected as the Model category.

I hope this helps,

Ben

View solution in original post

Ivano B · ‎05-19-2017

Hi Chandran

About the first question.

Unfortunately as per OOB CI class of a model category can be set only at creation time. Same for the asset.

Please refer to the next screen shots.

This means that you need to create a new model category.

About the second question. I suppose the reason of the mandatory field is exactly the slush-bucket.

If you provide just one class against the model than the category it is just one.

On the other hand in some cases you want to use a generic model to cover multiple classes.

In that case you need to specify at the asset level how you want to use it providing a category, this will help to set the CI in the right class.

I hope this will help and if it does please mark it

Cheers

R0b0

ncp · ‎05-19-2017

Thanks for your response R0b0, so my intent is that when I create an asset of model category Desktops, I want it to create a CI also. In this case it wont. Similarly if I create an asset of type Notebooks, I want it to create a CI, which it wont because only the computer model category has a mapping to the cmdb.

Ivano B · ‎05-19-2017

Ok so the question here is. Are you using OOB categories ?

Did you create these categories ? Are the categories already used ?

In case they are not already used maybe you can delete and re-create the model category as requested.

Cheers

R0b0

ncp · ‎05-19-2017

Ok I checked that now and it looks like Desktops and Notebooks categories may have been created by our integration to our older asset system. There are a few assets that are using those, so if I were to delete and recreate them, could I potentially re-associate the assets to the newly created model category? I would assume that model category has to have a cmdb_ci_computer to allow auto creation of the CI correct?