The Herman inventory system provides a convenient interface for inventory management via slack commands and messages.
Your responsibility as a DevOps team member
The Herman inventory system relies on the Meteor DevOps team to facilitate the organization and reliability of Meteor inventory so that all of the talented Meteor workers can have easy access to well-maintained technology, quickly.
Inventory management channel / notifications
All notifications regarding new inventory requests are sent to the inventory-management slack channel so make sure that you are in this channel and be sure to set your notifications to all messages.
Approving or denying check out requests
When a team member makes a check out request it is sent to the shared inventory-management channel so that any DevOps team member may fulfill the request the next time that they are in office. When a new request comes in there will be information regarding the request along with a dropdown to select an assigned device and a button for confirm and a button for deny. It is your job as a DevOps team member to first validate the request project/reason to ensure that the device will be used in an acceptable manner. If the device request should be denied, press deny and provide the requester with the reason why. If the request reason is valid, locate a device in inventory that matches the request and select the item from the dropdown (see Identifying Devices for help). Once you have located and selected a suitable device for the requester, you may press the approve button. Approving a request marks you as the team member responsible for placing it out and thus you should immediately receive a direct message from the Herman bot asking you to place the item in the designated pickup location (currently this is just the back left desk at the Stauffer lab however a location at MIX will be added soon). Place the device in the check out location, click the button in the message from Herman, and scan the QR code on the device. The requesting team member will then be notified that their device is ready
Checking in items
when a team member wishes to check in an item that they have been using, they will place the item in the same place which they picked it up from and then complete the check in item form. This will send a message to the inventory-management channel where a DevOps team member should place put the device away and then press confirm to move the item back in inventory so it can be checked out by others.
Identifying Devices
All devices in Meteor studio inventory should have QR code stickers on the device and box/container to uniquely identify the device. The sticker should also contain some text with the device UPC on it. This UPC consists of the device type code ex. Q2 for Quest 2 followed by a unique ID for the device and then the device's primary serial number. The easiest way to identify the device is to look for the unique ID for example the unique ID for a device with the UPC Q2-21-1WMHHB6CXN2183 would be 21. The unique IDs are unique for all devices even of different device types.