Inventory Management - How do you do it in D42?
Our company having recently acquired Device42, I'm looking at ways of recording our inventory numbers in a bid to move away from spreadsheets. Items would include SFP of various models, Cables of different colours, lengths and categories, server parts etc. all of which are kept in storage cabinet in different buildings.
The aim being to better manage new and used parts & report when stocks are low.
Have you tried to do this and can offer any feedback?
Presently I can only come up with creating 'Parts' for each inventory model type, and each cable, e.g. Part for Blue Cat6 6ft and then using count for the quantity. I have tried tags but the entry is prone to spelling or typing differences between regions.
Each storage cabinet would be logged as a 'Device'. I've found using a cabinet as storage affects the available RU count for each locality.
With each part being assigned to the 'storage' (device) in the relevant building.
Unfortunately this method is quite cumbersome for larger projects having to manually edit and update the number for each cable type, SFP, component used.
I may need to create a custom spreadsheet where we can perhaps import to update counts but this is open to creating errors.
If you have any alterative methods please do let me know I'm very keen to learn more about this application.
My checklist is as follows:
So, I need to determine if there is a way to exclude racks from the RU count.
A quick way to update Part counts en-mass (export/import or otherwise)
A method of categorizing/identifying similar parts.
A custom report to list stock per locale.
This is something I've been thinking about tackling as well at my org. But I've come to the conclusion that if isn't grocery-shopping easy, no one is going to follow through. No one likes to update a spreadsheet every time they take out a part. The ideal experience is like going to Home Depot, doing the self-checkout, and then walking out. The system does what it needs to do and adds/deducts as needed depending on the intended experience.
I'm thinking bar code readers (dumb or smart) and a custom Python script. I might be overthinking this but it would be a sure fire way that always works.0
I've found the current methods available are not used, as you've pointed out, because they are not streamlined enough to use. We'll have to stay with a spreadsheet for the time being.\
Appreciate the reply.0
Please sign in to leave a comment.