Query on Asset Management for a CMDB project implementation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2023 10:34 PM
Hey All,
We have a customer who is new to ServiceNow. They have a requirement to implement CMDB to track all thier CIs.
They dont want to do Asset Management for now.
So for this CMDB project, what is the best/right approach wrt creation of Assets via CI?
I mean, since its a CMDB project, should I turn off Asset creation via Model categories?
or
Should I just dont bother about Assets, let it get created, let customer use it when they want?
- Labels:
-
Data Foundations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2023 11:56 PM
Anyone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 07:30 AM
You can consider any of the following approaches after discussion with customer:
1. Turn off asset creation completely: Disable the 'Create asset on insert' business rule. This business rule is responsible for creation of assets when new CIs are created.
2. Based on model categories: Enable 'Enforce CI verification' flag on required model categories to prevent automatic creation of assets for those model categories.
3. For managing at the 'Product Models' level, you can use the 'Asset tracking strategy' field. But for the requirement which you mentioned, any of the options 1 & 2 will be better suited as solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:25 AM
My only concern with your customer request: Are they a completely virtual environment?
Because CIs that are all virtual are not barcoded or appear as items in a G/L needing accounting for or depreciation on.
If they don't want to worry about Assets now, will they ever? How are assets being tracked from an audit and governance perspective? Are all CIs discoverable and populated with a model number?
Having assets created in SN for tangible assets in the environment doesn't cause harm to your instance. Try running discovery in the Dev instance and see how it looks to you and your client. Then make a decision. That's my recommendation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2023 04:00 AM
I would let the Asset get created so the data is still available via dot walking. Eventually the customer is going to want some attributes that already exist on the Asset tables and when that happens, customizations to the CMDB tables will start. Avoiding that is worth having data that they currently don't want.
