How are you all managing consumables that are deployed with assets?

[Anwer]

We have a service catalog with our standard hardware (laptops, desktops etc) tied to asset models. We also have peripherals and accessories that are tied to consumable models.

I would like to associate certain consumables with assets so that users don't have to select multiple items from the catalog. For example, if a user requests a Dell Precision Laptop, the request should also automatically include the power adapter consumable.

I know there are bundling capabilities, but I haven't been able to figure it out fully. We created a bundle and tried to add the model components but when we get to the sourcing task it doesnt show the components.

We then tried to use the catalog items "includes" function to also include the consumable items but then each item is created as a separate RITM within the REQ, which is overkill for what we are trying to do.

How do you all manage this use case?

[Ashok Sasidhara]

Bundles would be the appropriate solution for this use case. Have you looked into the information in the following URLs? If yes, can you elaborate the issues which you are facing?

https://docs.servicenow.com/bundle/washingtondc-it-asset-management/page/product/hardware-asset-mana...

https://docs.servicenow.com/bundle/washingtondc-it-asset-management/page/product/product-catalog/con...

[Anwer]

Yes, we followed that documentation because it fits our use case. We got stuck when it asked us to add assets to the bundle. It seems like we are being required to add asset numbers for all the assets that we want to use as part of the bundle, but we were hoping it would just select any in-stock available asset that matched the model being requested.

Everytime we purchase a set of laptops, do we need to create the asset record and then add those assets to the asset bundle? Is that how others are using this functionality?

[DavidWallace1]

I thought the same as you, that a bundle was just defining a 'set' of items, that you could then order. It actually needs you to go into the stock room, physically bundle some stuff together and then define it as a bundle so it's basically a 'new asset' that can then be shipped out as one thing instead of several.

Personally I don't quite understand why you'd need to do that, so don't use this functionality.

My answer to the original question would probably be to modify the flow, do a check for specific model on the request (probably best done with a decision table) and create a task to get the power supply and consume it just before your shipping/deploy task. I have a similar requirement on my backlog waiting for me to implement it.