ProGlove Insight provides users with precise information about output expenditure. This includes movement indices that reflect the logging of process steps and the completion of job tasks. Both establish the basis for numerous optimizations and their evaluation. Regardless of whether this concerns a fully assembled car, time critical picking for a click & collect order, or an express delivery.
ProGlove Insight allows users to record the motion effort necessary for completing the shopfloor jobs. To this end, the platform utilizes the numerous sensors of the MARK family of products. By means of IMU sensors (inertial measurement unit) operators can measure all process-relevant motion sequences. This allows organizations to set up a statistical value of the physical effort to be delivered by the shopfloor workers. In other words, it lays the groundwork for an index that summarizes virtually all relevant process movements in logistics and production.
These can be simple steps, for example. But there are also other movements, including those that are necessary to pick up an object. These form the basis for the Insight movement index. Along those lines, these values can establish referential units for jobs such as putting an item into storage or taking it out of a box, typical walking distances, and so on. The objective is to create the right balance. On the one hand, employees should be able to do their job well without having to exhaust themselves on the other.
The relevance of scan time
Moreover, Insight offers other important metrics. For example, the total scan time. This ultimately visualizes the totality of all scanning processes. Starting with the triggering of the scanner to include the barcode capturing up to the transfer of the data to the system. But of course, this also involves documenting failed scan attempts. After all, they provide important evidence about the barcode quality.
In addition, users also receive other critical insights pertaining to the scan engines on site. This information may help to determine whether the scan engine is the right fit for the corresponding application. Above average scan times may indicate potential issues. Maybe the scan engines are not optimized for the required range for instance. A configuration update based on the individual use case may lead to even more speed. But such outliers can certainly also point to a labeling problem. This can very easily lead to subsequent problems which can quickly affect the entire workforce.
Insight provides information on workflows and processes
Needless to stress that the scan time helps to evaluate the overall workflow. For one, this data sheds light on whether the workflow is taking up too much time. But above all, the total scan time narrates how much time the process documentation requires. And with a little extra effort Insight allows operators to break this data down to the level of individual work steps.
Finally, organizations can determine the total scan time required during a given time span by the help of the Insight per-scan view. This data helps to assess the results of optimization initiatives and their resulting ROI. Additionally, it may serve as an important correlation measure to compare processes. And that is precisely what is needed when it comes to identifying best practices.