Stock rooms vs locations

[Robert _ysakows]

All,

We've just implemented HAM Pro and moved from legacy ServiceNow instance which did not have HAM module but just ITSM. HAM concept is new to everyone.

We're implementing process flows, for requesting a hardware we want to put it into a stockroom in 'in stock' state, before it can be installed. We are facing resistance from users who think that 'stockrooms' are unnecessary added complexity and they just want to use a 'location'. I am aware, that 'in stock' state requires a 'stockroom' to be populated so this would need to be adjusted in several places. Are the other considerations?

What are the pros and cons of using stockrooms? Is it even possible to use HAM features without stockrooms being properly utilized?

thanks,

Rob

[ericward · Accepted solution]

Hello! Change is always hard with end users, but this is a scenario where change is required. Stockrooms are essential within the realm of HAM and should be used. At the end of the day a stockroom just references a location. Whether that is a physical warehouse, a closet in a building, or a virtual storeroom. Within asset the location is auto populated based off of the assigned to or the stockroom selections. Set up stockrooms to match the locations where you actually house stock, and then train the users to use these stockrooms rather than the location fields. In the long run this is necessary and will save a lot of headaches. 

[AmolJ]

Hi Eric, could you please elaborate on "Within asset the location is auto populated based off of the assigned to or the stockroom selections." Are you saying if there is no "assigned_to" for an asset then it will automatically look for a stockroom association for that asset and then assign that location?