Performance Analysis
Note
The Performance Analysis section is a one of ProGlove's customizable analytics features. To enable it in your INSIGHT, activate the INSIGHT Analytics plan, or apply for a 30-day Free trial.
Get valuable insights into your process and devices, as well as key statistics, relative to any level you select from your Process Layout hierarchy.
To display the data crucial to your work processes, click the desired Process Layout level and select a time frame. Default selection includes all levels with today's data.
The Performance and Effort sections show Scan, Movement, and Scan Time metrics with the following components:
Graph visualization - Displays the respective measurement over the selected time frame and the selected Process Layout level. Each color in the graph is assigned to one sublevel of the selected Process Layout level, and its size represents how much it contributed to the overall number. Clicking on different colors in the graph hides or highlights different sublevels. To help you visualize the statistics, you can select to display the data in form of a bar graph or a heatmap.
Overall number - The number next to the graph is the accumulated value for the selected time frame and the selected Process Layout level.
Trend - The green, red, or grey arrow indicate a positive, negative, or neutral trend in comparison to the selected time frame.
Performance
The Performance section displays the number of Scans made under the selected Process Layout level for the selected time frame.
Effort
The Effort section displays the Movement and Scan Time metrics.
The Movement chart helps you visualize the total movement of your workforce under the selected Process Layout level and within the selected time frame. The Movement effort includes the total number of steps (distance walked) by your workforce, as well as any additional effort needed for the process-related movements (e.g. picking and packing).
The Scan Time chart displays the overall time of all scanning-related efforts under the selected Process Layout level within the selected time frame. This includes the time from pressing the scanning button to the decoding of the barcode in case of successful scans, as well as the time spent on all unsuccessful scanning attempts of the same barcode (e.g. in case of damaged barcodes).
Use the toggle at the top of the Effort section to display the Movement and Scan Time statistics for the Total workforce or Per Scan for the selected time frame.
Export data
You can export the data of the current selection Process Layout level and time frame in a .csv file.
In the Process Layout, select a hierarchy level.
At the top of the page, click on the date picker to select the desired time frame.
Note
The exported
.csvfile can contain up to 30 days of data.In the top right, click the download icon.
The Download Event History modal window displays.
Select DOWNLOAD.
A
.csvfile downloads with the data for the selected parameters.
Note
The export is a semicolon delimited .csv file where the events are displayed in rows while the features are displayed in columns.
Exported data-points
There are four types of events which are used to collect raw data:
Scan events - contain all scanning-related data and metadata
Telemetry events - contain all metadata collected between scans
Display events - contain all metadata collected when scanner receives a display message from connected host
Worker Feedback events - contain all metadata collected when scanner receives an LED feedback from connected host
Introduction events - contain data sent from your Gateway devices every time a connection is established with INSIGHT
Metrics available in the .csv file export
Metric name | Event in which data is collected | Metric data type | Description of metric |
|---|---|---|---|
| Telemetry event | STRING | Scanner's charging state at the time of ingestion. |
| Telemetry event | ARRAY | A series of events recorded during a specific period of time, while the scanner is charging. |
| Scan and telemetry event | INTEGER | Unix timestamp. |
| Scan and telemetry event | VARCHAR | Human-readable time stamp. |
| Scan and telemetry event | STRING | Custom Connectivity device identifier set by the user and used to annotate events. |
| Scan and telemetry event | STRING | Unique ID of the currently performed execution within a process (see: "customer_process_type_id"). If this execution is finished and the user starts a new execution within the process or starts a new execution of a different process type, this ID will change. |
| Scan and telemetry event | INTEGER | Timestamp when the trace (see: "customer_process_trace_id") started. This value is set by the Connectivity device based on customer input. |
| Scan and telemetry event | STRING | Unique ID of the process the user is working on, i.e. picking or packing. If the user performs the same process consecutively several times, this ID stays the same. To identify individual instances of this process, see: "customer_process_trace_id". |
| Scan and telemetry event | INTEGER | Timestamp of when a specific process was started. |
| Scan and telemetry event | DOUBLE | Scanner’s battery level (in %). |
| Scan and telemetry event | VARCHAR | Scanner’s firmware version. |
| Scan and telemetry event | VARCHAR | Scanner's serial number. |
| Display event | STRING | The header text of field 01. |
| Display event | STRING | The content text of field 01. |
| Display event | STRING | The header text of field 02. |
| Display event | STRING | The content text of field 02. |
| Display event | STRING | The header text of field 03. |
| Display event | STRING | The content text of field 03. |
| Display event | STRING | The display refresh strategy. |
| Display event | STRING | The ID of the used template. |
| Scan and telemetry event | STRING | ID of the predefined feedback action that was signaled. |
| Scan and telemetry event | VARCHAR | Connectivity device's firmware version. |
| Telemetry event | STRING | The Connectivity device's software installation ID (if applicable). |
| Scan and telemetry event | VARCHAR | Name of the Connectivity device, as defined by the user. |
| Scan and telemetry event | STRING | Operating system (OS) version of the Connectivity device. |
| Telemetry event | STRING | The serial number of the Connectivity device. |
| Scan and telemetry event | VARCHAR | Thing name of the collecting Connectivity device. Used instead of the |
| Scan and telemetry event | STRING | The IP v4 address of the Wi-Fi access point (if applicable). |
| Scan and telemetry event | ARRAY | The IP v6 address of the Wi-Fi access point (if applicable). |
| Scan and telemetry event | STRING | The BSSID of the Wi-Fi connection used by the Connectivity device. |
| Scan and telemetry event | STRING | The local IP v4 address of the Wi-Fi connection (if applicable). |
| Scan and telemetry event | ARRAY | The local IP v6 address of the Wi-Fi connection (if applicable). |
| Scan and telemetry event | INTEGER | The signal strength of the Wi-Fi connection (in dBm). |
| Scan and telemetry event | STRING | The SSID of the Wi-Fi connection used by the Connectivity device. |
| Scan and telemetry event | VARCHAR | Unique ID of the event. |
| Telemetry event | DOUBLE | Sum of trigger time in milliseconds for unsuccessful scans. |
| Telemetry event | DOUBLE | Number of unsuccessful scanning/trigger actions. |
| Scan event | DOUBLE | Movement effort of all steps, as well as additional movement, measured by the scanner (e.g. picking, packing efforts). |
| Scan and telemetry event | ARRAY | Full list of names, defined by the user, of the parent levels for the collecting Connectivity device at the time of ingestion. |
| Scan and telemetry event | VARCHAR | Full path of the collecting Connectivity device, with IDs of the parent levels concatenated with a ‘#’ character at the time of ingestion. |
| Scan event | VARCHAR | Scanned barcode. |
| Scan event | VARCHAR | Symbology of the scanned barcode. |
| Scan event | DOUBLE | Trigger time in seconds. |
| Scan and telemetry event | STRING | ID of the currently active session between the Connectivity device and the scanner. With each new connection this value will change. However, it will remain stable across reconnections between cloud/customer integrations. |
| Scan and telemetry event | INTEGER | Message counter within the current session (see: session_id). The Connectivity device will assign a new, subsequent number, starting from the "0" value, to each new message. With each new session this counter will restart. If the counter reaches the maximum of "int32" the customer is responsible for closing that session and starting a new one. |
| Scan and telemetry event | VARCHAR | Type of event. |
Scan performance optimization
Since the below parameters have an influence on the overall scan performance and Scan Time displayed in the Effort section, we advise to check the following and ensure optimal conditions:
Configuration
Check if the scanner settings set in the ProGlove.proconfig file are best suited for the barcodes you are currently scanning. Use Fuzzy 1D processing on 1D, damaged, or low-quality barcodes. For mobile displays, electronic screens, or similarly reflective surfaces, use the Display Mode. In areas of multiple closely-placed barcodes where you want to decode only barcodes below the aiming crosshair (dot) use the Picklist Mode.
Symbology configuration
If your Daily Insights indicates that you are not using a certain symbology, consider turning it off in your configuration file to speed up the decoding. Having fewer symbologies enabled takes less time to scan and decode the desired barcodes.
Physical barcode condition
You scanning performance is greatly affected in cases of dirty, damaged, or even reflective barcodes. Check the state of your barcodes to identify possible improvements to the scan reliability and speed, and either preserve the physical barcode quality or try enabling the Fuzzy 1D processing in your configuration's Scanner settings. If you find the barcode surface too reflective (e.g. scanned from a display), or the barcode too large or small to scan, consider adjusting the scanning distance or the light conditions or enabling the Display Mode in the Scanner settings of your configuration.
Worker handling
The way in which workers scan using ProGlove scanners can also have an influence on the scan time. Make sure to provide your workers with enough time and training with the devices.
Dirty scanner camera lens
Your scanning performance can be affected by a dirty camera lens on your scanner. If your scanners are used in industrial environments with heightened dust conditions, make sure to clean the scanners regularly as demonstrated here.
Symbology usage
The table below presents the list of most used symbologies and how fast they are decoded (Scan Time) as compared to the ProGlove benchmark (established by processing data from multiple customers' use cases).
Symbology | Average decode time (in seconds) |
|---|---|
CODE 39 | 0.23 |
ITF | 0.25 |
CODE 128 | 0.25 |
EAN-8 | 0.27 |
UPCA | 0.32 |
EAN-13 | 0.32 |
GS1-128 | 0.34 |
QR CODE | 0.35 |
DATA MATRIX | 0.37 |
CODE 11 | 0.45 |
IATA | 0.50 |
D25 | 0.50 |