/build/static/layout/Breadcrumb_cap_w.png

Asset Management Best Practice - People Process Technology - When Tools prevent process

AB9BVSUHWWS0AAAAAElFTkSuQmCC

Having worked with ITIL Best Practice guidelines for many years, in the trinity of "People, Process and Technology" it is clearly the people part that becomes the weakest link when trying to implement and Best Practice process such as Asset Management. The point being that you can design process to meet your needs and you can configure technology to do what you want, however when it comes to people you have to be a bit more savvy other wise the old adage is true:


"You can lead a horse to water but you can't make it drink!"


Having technology that makes following a process quick and simple for the Tech to use, is much more likely to guarantee adherence to the process and ultimately better results, in terms of an Asset management process, that means more accurate asset data.


With that in mind, I considered a simple, everyday scenario that techs might come across, namely the allocation of an Asset Tag to a piece of equipment or Asset. The Asset Tag is the unique identifier applied to equipment providing a visual reference for the tech during audits or support visits. For many customers starting a program of Asset management, there is a challenge to register an existing record in KACE with a new Asset Tag, so that every Asset to be managed can be identified both in KACE and physically. This will usually means the application of the Asset Tag label at the user desktop and the update of the record with KACE.


This first video looks at how the KACE Go Mobile app, equipped with Barcode scanning would handle the process.


In the video we see locating the record is simple enough but the ability to add the Asset Tag in the App UI is just not available, creating the type of barrier for the Tech to follow the process in the most efficient manner. This lack of functionality means the Tech would have to record the data and remember to update the record in the main KACE Admin UI when they get back to base. Both of which allow for errors and possibly the record not being updated at all. 


This second video looks at how our BarKode Scanning tool for the KACE SMA Handles the task.


In the video we see that the tech is easily able to locate the asset requiring the Asset Tag update and with the BarKode double scan functionality, they are able to scan the assigned Asset Tag value straight in to the record in KACE.

This means that both the possibility of error and forgotten updates are removed, providing the tech with the simple means to follow the process and facilitate more accurate asset data.

Not only that, but if we go with an estimate that the Go App instance takes 10 minutes longer to record, return to base and update KACE than the simple BarKode Double scan, imagine how long it would take you to add in 500 or 1000 new asset records accurately at the start of your Asset Management project?


That is over 80 hours for 500 and over 150 hours for 1000, multiply that by a nominal hourly rate for your Tech, say $30 and that is a considerable amount of time and money that could be saved?


With that in mind, why wouldn't you choose to use a tool that not only saves you money, time and effort, but also delivers accurate asset data straight into your KACE SMA?


Asset Management - Because small changes make Big Differences

Get in touch with us Here to find out how we can help you with KACE Asset management


www.indigomountain.co.uk     #WeAreQuest


Comments

This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ