Best way to implement a sublocation of a Stockroom.

[PeterC90]

Hello Everyone

I am new to ServiceNow and our Business is moving from Spreadsheets to ServiceNow Assets and Requests. ( YAY!)

We ship Assets to some Smart Lockers ( lockers that can be accessed by a Code to access a door that has the asset within)

I have set these lockers up as a Local/ Onsite Stockroom so we can see which stock is in each locker.

The lockers have 15 draws that each has its own coded lock on the doors.

I need to have some kind of sub Stockroom location to track the draw in which the stock is placed, so I would be able to see which stock is in which locker and which Bay/draw.

it's important we know which stock is in which Draw so we can give them the pin to the correct user who needs that specific Model.

I'm sure people go pretty granular when dealing with Stockrooms, Like Bay, Isle, Row and Shelf ( similar to Ikea for example)

What would be the best way to achieve this? Ideally, I want to look up the asset or configuration Item of that asset and see where its located.

I can see people create fields and then transform Map these fields to other tables but as I said I'm very new to ServiceNow and cannot code/ script anything to save my life.

Kind regards

Thank you

[Hitoshi Ozawa]

There isn't any OOTB detailed location on assets.

It's possible to use location and create a hierarchical structure (by specifying "parent") to support bay, isle, row, and shelf. The downside of this approach is it may be difficult to find the exact location because there's only one location field related to an asset so it may be difficult to distinguish between "shelf A" in row 1 and "shelf A" in row 2.

Another option is to add a field of type "select box" with options such as bay, isle, row, and shelf to the location table. Then add fields bay, isle, row, and shelf in asset table that references the location field with a reference qualifier to only show the appropriate type.

[PeterC90]

Cheers

We have gone and just made a stock Room for each Draw for now which works fine but just makes allot of records in the stockroom table and makes the dropdown list on the asset huge. but gets me out of a bind

[Ken Neikirk1]

A solution that might be worth a look:

https://www.prnewswire.com/news-releases/velocity-smart-technology---smart-collect-is-servicenow-built-on-now-certified-301195898.html

[Arthur Schulcz1]

To me the key here is to have a proper hierarchy and well thought out and clearly defined naming convention in your Locations table.  You may have to work with platform admins on creating this.  There is a ‘Full Name’ field that contains the full hierarchy for each record, but most references and lookups from other tables are tied to the ‘Name’ field. 

As an example, the name for the location of a Drawer should be Drawer 1 Stockroom A Building 100 City XYZ (etc).  Each location node in the name being a child of the tier above.  Stockroom is the parent of Drawer. Building is the parent of Stockroom.  See the example below.  These somewhat verbose titles help make functional sense of the data and help it be more usable within the platform. 

The 'Stockroom' would be at the level of storage locker.  When the ‘State’ of an Asset is “In Stock”, ‘Stockroom’ becomes a mandatory field.  There is a client script that populates ‘Location’ from the ‘Stockroom’ record.  However, you can manually update ‘Location’ after selecting ‘Stockroom’.  In my example, select a “Drawer” location that is a child of the stockroom’s location.  The benefit here is you maintain reporting integrity for both locations and stockrooms and can utilize stock rules to help manage inventory.