Concurrent users measurement
The pricing of the Yard Operating App depends on the number of concurrent app users (see Sales Pitch). For this reason we need a definition and a metric to monitor if customer’s app usage is in line with their purchased licenses.
Definition of concurrent users
Concurrent users are defined by the maximum of distinct operators that finished a task (using the app) in the same hour over a given period in time (e.g. six months).
Metric
Every 15 minutes, the application reports the number of concurrent connected users (CCU). We define the number of concurrent connected users as following: all users that match one of below conditions
a user had any activity in the last 30 minutes (log-on action or finish a task)
the user is not logged off
By evaluating the trend, one can derive the concurrent users of the customer. In general, the concurrent connected users will be the “maximum” value that is reported. However, shift changes might impact these maxima in an incorrect way.
Example
Timing | 06:00 | 06:15 | 06:30 | 60:45 | 07:00 | 07:15 |
|---|---|---|---|---|---|---|
A user that logs off will immediately stop counting | Tom finishes a task | Tom finishes a task | Tom logs off |
|
|
|
A user that forgets to log off, will continue to count for 30 minutes | John finishes a task | Count: 1 |
|
|
|
|
A user that logs on and does nothing, will count for 30 minutes | Ann logs on | Count: 1 | Count: 0 | Count: 0 | Count: 0 | Count: 0 |
Concurrent users measured: | Total: 3 | Total: 3 | Total: 0 | Total: 0 | Total: 0 | Total: 0 |
Shift changes
There is a chance that shift changes incorrectly affect the definition of concurrent usage. This is illustrated by next example:
Timing | 12:50 | 13:00 | 13:05 | 13:15 | 13:20 | 13:30 |
|---|---|---|---|---|---|---|
Early shift operator forgets to log off | Tom finishes a task |
| Tom finishes a task |
| (Tom’s session is marked inactive) |
|
Late shift operator logs on | Ann logs on | Count: 1 | Count: 1 | |||
Concurrent users measured: | Total: 1 | Total: 2 | Total: 1 |
If Operator_1 forgets to log off, the system will report on 13:15 a concurrent use of 2 operators:
Operator_1 finished a task in the last 30 minutes (and is still “connected”)
Operator_2 logged on at 13:05
It is best practice for customers to instruct the operators to log off when they quit their activity/shift. However, some interpretation will be required when analyzing the CCU-trend: if certain spikes are observed around the time of shift changes, they can be ignored (even though technically spoken, the users are concurrent…).
Concurrent usage metric
Concurrent usage of the Yard Operator App (YOP) will be monitored in Amplitude (a platform to keep track of usage metrics) on the Customer Succes Manager’s Dashboard:
