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

Community Alums · ‎12-15-2017

Chad,

Can you please describe the situation a little more. I'm not sure I understand the situation.

Thanks,

Ben

Chad Wilhelm1 · ‎12-15-2017

We have a integration with Ariba which automatically creates assets and they want to create ci's when any asset is created that has a model category of audio. Anything else they do not want a ci to be created from this integration. So I was asking in order to keep other ci's from being created is there any configuration that can be done.

Thanks,

Chad

ncp · ‎12-15-2017

Chad, Its the model categories that determines if an asset will create a ci or vice versa. if you go to model categories you will see a ci class and an asset class, those model categories which have a ci class and associated asset class, they will create/update a ci or asset depending on what is crated/updated. If you dont want to create a corresponding ci when an asset is created dont associate that with a model category that has an existing mapping. Not sure if I made sense, but ben sweester has explained the linkage in other posts how model category and asset/ci classes tie together.

Models vs. Model Categories: Model Management, Part 2