Configuration Item to Asset Relationship.

[terrymowles]

I am currently reviewing the Configuration Item and Asset relationship in Service Now and I want to find out what is the best way to do the following:

1. Align incremental purchases against a configuration item

2. Determine what is required to assign license to an asset

3. Determine if it you can assign 2 software licenses to a physical asset

4. Determine if there is a way to have an automated process when an employee leaves and the asset is returned that the CI (eg: Visio License) count will increase to show an available license.

I look forward to hearing some of your thoughts.

[Community Alums]

Hi Terry,

Based on your statements, I hope I can clear up a couple things about assets and CIs while I answer you here.

1. Do you mean incremental purchases such as RAM or other types of similar updates? If so, you would track these against the asset, not the CI. The asset is where the financial aspects live. For the RAM example, you would have the RAM available as a consumable which is then "consumed" by the asset. The cost is then associated with the asset through a parent asset-child asset relationship. If you mean something else, can you please clarify?
2. Software licenses are assigned to CIs, not assets (despite the form section name of "Asset Entitlements" on the software license records in Eureka and earlier). CIs are the operational representations where this type of information is assigned and discovered. This is fairly easy to assign in the Software License record. The most difficult part is to determine if there are restrictions you need to apply based on your licensing with the software vendor.
3. You can assign (Entitle) multiple licenses to a single device or user in the Software License record.
4. Absolutely. We do something similar to this in the Asset Management course as part of an Asset Retirement process. This could just as easily be applied as part of the process that returns an item to stock.

I hope this helps.

Ben