Time series data model
The analytics is done using the time series data where all data is stored with a specific point in time to which the data correlates to.
E.g. every scan of a connected device creates a datum at the time of the scan. The data persisted at this point in time is all the information retrieved about the scan: E.g. information about the devices used, scan-related metadata such as the decoded symbology, but also inferred information such as an estimation of the worker effort preceding such as step counts or missed scanning attempts.
The data model provides efficient access to the data persisted for a specific interval of time (e.g. a day, hour, etc.) Additionally, other attributes (e.g. scan symbology, device serial number, etc.) can be used to further filter or group the data.
Conceptionally, you can consider the data model a big table where the data is indexed by timestamps with additional columns:
Time | Attribute: Symbology | Attribute: Device Serial | Attribute: Scan Duration |
|---|---|---|---|
2021.01.23 06:02:12 | QR Code | M2MD010101234 | 2.03 s |
2021.01.23 06:03:14 | DataMatrix | M2MB010105678 | 9.23 s |
2021.01.23 11:17:45 | QR Code | M2MD010101234 | 0.54 s |
2021.01.23 14:18:03 | QR Code | M2MD010101234 | 5.54 s |
Each of these columns is either a simple attribute or a measure.
A measure has a varying value of a specific type that is meaningful to observe. This can be a simple count like the number of steps taken or a continous measure such as the duration of triggering the scanner to perform a barcode scan.
An attribute is any kind of label that further identifies a measure. Examples include the device’s metadata such as the serial number or the firmware version, process details (like the level or sublevel of a connectivity device), or just the symbology of the decoded barcode. Below, you can find the current list of potential attributes attached to measure.
Recorder measures
Measure | SQL Data Type | Description |
|---|---|---|
| DOUBLE | The percentage of the battery’s charge levels |
| VARCHAR | The scanned barcode value |
| DOUBLE | The trigger time in seconds needed to scan the barcode |
| DOUBLE | The approximate number of steps since the last scan |
| DOUBLE | The sum of trigger times for unsuccessful scans |
| DOUBLE | The number of trigger presses for unsuccessful scans |
| DOUBLE | The barcode scanning effort measure in miliseconds |
| DOUBLE | The scanning effort measured as a number of trigger button presses. |
| DOUBLE | The time effort between the current scan and the previous successful scan made by the same device, measured in milliseconds (max. 5 min). |
Recorded attributes
Each measurement can be identified by a set of metadata attributes:
Attribute | Description |
|---|---|
| Worker scanner device model |
| Worker scanner device manufacturer |
| Worker scanner device serial number |
| Worker scanner device firmware revision |
| Connectivity device model |
| Connectivity device manufacturer |
| Connectivity device ID |
| Connectivity device deploymen type |
| Connectivity device software revision |
| Type of event: scan or telemetry |
| Unique event ID |
| The decoded barcode symbology |
| Connectivity device name |
| Name of the first associated level in the connectivity device organization |
| Name of the second associated level in the connectivity device organization |
| Name of the third associated level in the connectivity device organization |
| Name of the forth associated level in the connectivity device organization |
| ID of the first associated level in the connectivity device organization |
| ID of the second associated level in the connectivity device organization |
| ID of the third associated level in the connectivity device organization |
| ID of the forth associated level in the connectivity device organization |