Service Catalog Software/Access Best Practice

[jeff_eigenraam]

We are currently in the process of converting our 800+ item catalog into Servicenow.   We don't want to have 800+ items and are trying to consolidate and slim it down to what is actually needed.   My question is around the best practice for software that requires physical/pushed installation and also requires access or restricted access to use.   Our current catalog has these as separate items and are in different locations, which is very confusing to the end user.   Would it be better to make it one item with all of the options for install and access in one form?   Or is is better to keep them separate but use an order guide to build the item?   Or is there another way that is better?

Thanks

Jeff

[SanjivMeher]

I would recommend creating a category for Software and add everything there. Like in Amazon.

We had everything in an order guide, but then it is difficult to manage and search as well. Everytime there is a addition or deletion, we also had to update order guide.

[akash_mehta]

Jeff:   I would keep this as simple as possible which would be keeping the software installation request/access request as a single item.   I would use some field (new configured field on the software model table) to help identify if you need to send to a group for "access"...So this way in the workflow you can look at the data to determine if you need to add a task for access request.

-Akash

[sachin_namjoshi]

Hi Jeff,

Below posts will provide you best practices for implementing service catalog.

Application Guide: Service Catalog Best Practices

13 Service Catalog Best Practices

Regards,

Sachin

[Chimenem]

Hello Jeff, did you ever find a solution for this question. I'm in the same pickle and would appreciate any insights on how to go about it. Thank you!