ProGlove Documentation

All teams follow certain processes, and some can even have more than one process type in place (i.e. picking, packing, sorting, etc.).

By setting custom process identifiers, you can easily identify processes that were executed on your shop floor and attribute each scan to a specific process, or process type. This allows you to perform process mining and analyze your data based on different types of processes.

Process type ID helps you attribute scans to a specific process type, while a Process trace ID connects to a specific process. Each identifier will have an associated timestamp so you can quickly understand when one process ended and a new one started.

Both process identifiers can be added using Android Intent calls. You set your own, custom values, which will be enriched with a new field containing the timestamp for each scan: customer_process_type_started and customer_process_trace_started.

Once values are set, you can overwrite them by simply setting new ones. Both Process type ID, Process trace ID, and the associated timestamps are visible in the INSIGHT Mobile (Android) app. They can also be pulled in your generated reports and extracted in a .csv file.

Set your process identifiers

To define the desired values and start applying them to your processes for an in-depth analysis, use the code below:

Intent().also { intent ->
    intent.setAction("com.proglove.api.SET_EVENT_TAG")
    intent.putExtra("com.proglove.api.EVENT_TAG_KEY", "<tag_name>")
    intent.putExtra("com.proglove.api.EVENT_TAG_VALUE", "<value>")
    sendBroadcast(intent)
}

Note

Values are in a string format and can contain from 1 to 257 characters.

Once the values are in place and you've generated your reports, you will see the defined values and their corresponding timestamps, as shown below:

For more details on how to export data and generate reports in INSIGHT webportal, see here.