Our clients have successfully leveraged our Barcode Scanning solution for Jira Service Management (JSM) Assets to address a variety of business challenges. Implementation of our solution begins with workshop sessions to configure the solution and train administrators to build out their own use cases going forward. As a result, we often uncover requirements organically during these sessions rather than receiving a predefined list.
Recently a new customer, managing the transition of approximately 25,000 assets annually, implemented the StrataCom Barcode Scanning solution for JSM Assets to streamline asset assignment, movement, and retirement—saving their technicians hundreds of hours each year. Implementation was completed in only 2 hours! Below are sample requirements and questions we addressed during this implementation which often come up with other clients as well.
Requirement 1: How do we bulk scan serial numbers?
- When we scan a serial # it automatically looks for the serial # and, if found, it instantly displays the match.
- Example in the screenshot below: under “inventory management” to bulk scan 5 serial # ‘s and change the status to “EOL”…how woudl this be accomplished?
Solution: Using our ‘Scan to Action’ automation, the user simply scans the 1st barcode, changes the status to “EOL…” and hits OK to apply the change. 1. The scanner will pop up, 2. User simply scans the next asset and hits OK to save. You can scan an unlimited number of assets, changing each one as soon as it’s scanned!
Requirement 2: Create a new main menu button called ” IT PREP / IMAGING”
- This is a feature that IT commonly uses when pulling workstations from inventory to image them BEFORE deployment.
- The asset lifecycle impact is:
- pull from (key: TH-92918) – active inventory (on site) ”
- change status to (key: TH-92919) – “Pre-Deployment Staging IT prep”
Solution: Simply adding a button to the home page that Scans to an Action and is called “IT Prep/Imaging”. The action automatically sets the status of the asset to “Pre-Deployment Staging IT prep” as soon as it’s scanned. The scanner then pops up immediately after save, ready to set the next asset’s status.
Requirement 3: We have 3 Current Deployment Options: “DEPLOY (WFH)”, DEPLOY (ONSITE/MOBILE”, “DEPLOY PRODUCTION FLOOR.” We need to make the following changes:
- Change the current (key: TH-92918) “active inventory to “(key: TH-92919) – “Pre-Deployment Staging IT prep”.
- Workstations are often “imaged” days in advance before deployment, so the customer required another “inventory /life cycle bucket” to account for this for inventory tracking and reporting.
- Add the new attribute field “PROGRAM” to each.
- This will be a selectable drop down menu from all our client programs that we will mass upload into Jira Assets.
- Under “DEPLOY PRODUCTION FLOOR” only – add the asset attribute selectable field “Seat location“.
- This will be a new attribute field in Jira Assets for all campuses. For deployment purposes it must be configured to allow the end user to view and choose seats for their respective campus.
Solution: As StrataCom’s app already offered 3 automation buttons for deployment, we simply added the field changes into each button’s action.
Requirement 4: Create a new main menu button called “RECEIVE INVENTORY”
- All new purchases will now be mass uploaded to the lifecycle status “In-Transit” (key TH-143518) at time of purchase.
- Lifecycle impact: IT will scan serial numbers of assets received and change the status to “active inventory” from “in transit”.
- This extra step will help ensure data accuracy of what a vendor ships versus what is received serial # wise. Any discrepancies in serial # numbers can then be investigated and validated at time of receiving.
Solution: We added a home screen button called “Receive Inventory” that is tied to a scan action that simply changes the status from “active inventory” from “in transit”. The user can scan as many assets as they need with this action. Updates take around 1 second or so to complete, so they can scan dozens of assets per minute.
Requirement 5: Add the ability to add a serial number …. but are 2 different methods and locations possible?
- Location #1 requires the ability for IT to add a serial number and enter all the applicable existing workstation attribute fields in Jira Assets below via drop down menus.
- Campus (if not defaulted based on user profile location)
- Hardware type
- Asset Lifecycle status (is there an option to default to ‘active inventory’ – but option to override if needed?)
- Brand / Manufacturer
- Model Number
- Form Factor
- RAM size
- Chip / processor
- Pperating system
- Location #2 – under “reclaim” add a function to add a serial # not found upon scanning …. but create a restriction to ONLY allow the addition of the serial # itself, no other attribute field changes.
- Use case: at times the client receives workstations several months after someone leaves the organization. This this limited add feature will allow our facilities team to add assets that are not part of the go-live data set.
Solution: We added both “scan to actions:” the 1st with all the fields listed as inputs and the 2nd ONLY allows them to add the serial number.
Requirement 6: Under the “Inventory Management” button: Change the display to show 9 attribute fields (detailed below) for workstations and require technicians to update those fields if they are blank.
- If there are any blanks: prevent IT from being able to save or change the asset lifecycle status until all fields are completed.
- The 9 attribute fields are:
- Campus (if not defaulted based on user profile location)
- Hardware type
- Asset Lifecycle status
- Brand / Manufacturer
- Model Number
- Form Factor
- RAM size
- chip / processor
- operating system
Solution: StrataCom added the 9 desired attributes and configured them mandatory. We have a logic builder for mandatory that can include the value of other fields. For example: if the Brand is Dell, we can make operating system required, but if the Brand is Motorola, we would set the flag to not required.
Requirement 7: Add new button to main menu “ON SITE SEAT SWAP”
- This requested functionality would only be used by IT technicians when moving assets assigned to one seat to another on the production floor
- LifeCycle impact: change the current assigned seat location to the new seat location by selecting from a drop down menu
- Use Case: In some of our locations, assets are frequently moved around on site based on client needs and seating plan changes. (ie. move from one floor to another, etc).
Solution: StrataCom added a new button with a scan to action of “On site seat swap” that prompts the user to enter a new seat location. The seat locations are stored in assets, so our type-ahead list picker allows the user to easily find it.
Requirement 8: Is there a way to add an “inventory cycle count” update functionality wise?
- The client requested a new button on main menu (or a sub menu) and to be titled “INVENTORY CYCLE COUNT”
- Goal: for each campus IT to mass scan each type of asset in inventory and default save to “Active Inventory” so that all assets in inventory are recorded as being scanned/counted on a weekly basis and the asset’s corresponding log history is date stamped with this info.
Solution: StrataCom added a button to the main menu that is tied to a “Scan to Action” called “Inventory Cycle Count”. This actions set the status to “Active Inventory”.
For more information about our mobile solution, visit our landing page HERE
If you’d like a demonstration of our JSM Mobile Barcoding App or would like to request a price quote, please reach out to Laura Walker: lwalker@stratacominc.com.