Yesterday, we built our "Master Inventory" (Assets). But a list of laptops sitting in a database isn't useful unless you know who is holding them when things go wrong.
The Scenario:
An Elf runs up to Santa: "My hammer broke!" Santa asks, "Which hammer?" The Elf holds up a generic hammer. Santa needs to know exactly which specific tool it was so he can record the breakage and issue a replacement. If he has to dig through a logbook to find the Serial Number, toys don't get built.
The HR Reality:
Offboarding is the scariest time for asset management. An employee resigns. Do you know exactly what they need to return? If you don't have a clear link between the person and the device, thatβs a $2,000 laptop walking out the door forever.
The JSM Solution:
Linking Assets to Tickets.
When you view an employee's profile in Assets, you can see he currently holds: MacBook Pro no.1234, iPhone 14 no.5678, and Badge no.99.
You can also see a panel showing "Linked issues".
When the "Offboarding" ticket is created, you can select employee in Assets field and this request will be automatically presented in the employee's profile, so you will know that "Retrieve MacBook no.1234" must be on the offboarding checklist.
π Tip of the Day:
This closes the loop. HR manages the person, IT manages the device, and JSM Assets connects the two so nothing gets lost during the holiday shuffle.
βοΈ Letβs chat: Have you ever had a "Phantom Laptop" situation where an employee left, and weeks later, you realized nobody asked for their computer back? π»
Kate Pawlak _Appsvio_
Chief Product Officer & Co-founder
Appsvio
Wroclaw, PL
87 accepted answers
0 comments