Customer Requirements for StrataCom’s Mobile JSM Asset Solution with Bar-code Scanning

We’ve seen our customers use our Bar Code Scanning solution for JSM (Jira Service Management) Assets to solve a number of business problems.  We typically do workshops with them to configure the solution as well as train their admins on how to build their own use cases.  Because of this, we don’t often get to see a large list of requirements, as we’re normally pulling those out during the workshops as our customers realize how our solution can help them.  Below is a list of requirements we received from a new customer who transitions around 25,000 assets a year in their organization.  They purchase the StrataCom Bar code scanning solution for JSM (Jira Service Management) Assets to save their technicians hundreds of hours a year in assigning, moving and retiring physical assets.  Below is a list of requirements and question (Yes, our solution handled all of these use-cases!) that our Consultant/Trainer helped the customer implement.  All of these requirements were implemented in less than 2 hours!

• Right now when we scan a serial # – it automatically looks for the serial # and if found, it instantly displays the match.
• For example in the screenshot  below – under “inventory management” if we wanted to bulk scan 5 serial # ‘s and change the status to “EOL” – how can we do this?

• This will be a feature that IT will use 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”

• change the current   (key: TH-92918) “active inventory  to  “(key: TH-92919)  –  “Pre-Deployment Staging IT prep”.
  • The reason being for this change I recently learned that workstations are often “imaged” for days in advance before deployment, so we need 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 we are in the process of adding.  However for deployment purposes we need it configured so the end user can see /select seats for their respective campus.

• 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 vs what is received serial # wise. Any discrepancies in serial # numbers can then be investigated and validated at time of receiving.

• location #1  –  – perhaps under “inventory management” –  need an 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
  • operating system
• location #2 –  under “reclaim” add a function to add a serial # not found upon scanning …. but restrict so can ONLY add serial # itself – no other attribute fields.
  • Reason being –  at times we receive workstations several months after someone leaves the org- this limited add feature will allow our facilities team to add assets that are not part of the go live data set.

• ie. if any blanks – prevent IT from being able to save /change the asset lifecycle status to anything else until all 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

• This would only be used by IT when moving assets assigned to one seat to another on the production floor
• LifeCycle impact – just change the current assigned seat location to the new seat location. (new seat location would be selected via a drop down menu)
  • Reason being – I was informed in some of our locations, our assets are frequently moved around on site based on client needs and seating plan changes. (ie.  move from one floor to another, etc).

• One possible idea i had – create a new button on main menu (or a sub menu) and call it “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.