InnerWeb
Skip to main content

Group training at the workstation: implementation notes for the integrator

A group of a dozen people scans codes before the safety film at a workstation where nobody stands. An integrator deploying such a workstation has several pitfalls to defuse before go-live: the lifetime of the group on the server side, the size limit, a latecomer's scan and a film interrupted halfway.

34 min
lifetime of the group trained on the server side
Source: documentation of the registration workstation function

Workstation architecture in three sentences

The registration workstation is an unattended screen where a USB HID scanner is the only input device: no keyboard, no login and no field for typing a code. A scan of the QR code gives one of three responses: a welcome for a person with valid training, the introductory briefing for a person without it, or a record of exit after a break longer than the scan window.

For the integrator the conclusion is simple: the device has no input that could fix a wrong situation. All exceptions must be resolved in the logic, not by user intervention.

Stage 1: the group state on the server side

The introductory training can be replayed for the whole group at once, and the group completion records the entry for all participants with one click. The training group is kept on the server side and expires after 34 minutes. The screen shows only its view, so a person not counted in the group will not be credited.

A pitfall for the integrator: the 34 minutes refers to the lifetime of the group, not the length of the film. If the film runs for a dozen or so minutes and the participants gather for longer than the remaining minutes, the group will expire before anyone clicks completion. Plan a message for the supervisor about the time window.

Group window versus film (example)

Group window versus film (example)Horizontal bar chart: 34 minutes of window, 15 minutes of film and 19 minutes of margin010203040minGroup lifetime windowGroup lifetime window: 34 min34Safety film (assumption)Safety film (assumption): 15 min15Margin for gathering the groupMargin for gathering the group: 19 min19
Source: Sample calculation: film of 15 minutes, group window of 34 minutes

Stage 2: the group size limit

The group size limit at the workstation is checked before the request is sent. A scan of a person without training during a running session, a welcome or a closing does not add them to the group. For the integrator this means the limit must be defined with the client, taking into account the largest realistic group, for example a class of students.

A pitfall: a limit that is too low for a large group creates queues for a second round, while a limit that is too high lengthens the time the supervisor must stay at the screen. Set it based on a measurement of the first group, not on assumptions.

Stage 3: the latecomer and the re-scan window

The re-scan window is sliding and set in seconds (minimum 1). A person who scans again every few seconds is welcomed again and stays on the attendance list, and the exit is recorded only after a real break. For an unattended workstation this is an important safeguard against impatient participants who scan the code a third time.

A latecomer who scans after the film has started does not join the group. The integrator should prepare a text on the screen or an instruction for the supervisor that the latecomer waits for the next session, because without it the situation looks like a failure.

Stage 4: interrupting the training

Interrupting the training, for example through a material loading error, clears the group on the server, so that an abandoned group is not credited at the next session. This behaviour is deliberate and safe, but the integrator should know that after a loading error the whole group starts again.

Test this behaviour before go-live: disconnect the network during the film, check that the group is cleared, and record the result in the acceptance protocol.

Stage 5: the evacuation list and integrations

A person who scanned at the training workstation appears on the evacuation list from the moment of the scan, with the status 'training in progress', also when they are missing something other than the training. The integrator is responsible for making sure security knows about this status and does not treat it as an error.

Reception events can be routed to the team channel in a messaging app with one setting and a webhook address. Check the client's IT policy on outgoing traffic to the messaging app before you promise this feature.

Video

Frequently asked questions

Does the workstation have a keyboard for typing a code?

No. The USB HID scanner is the only input device, with no keyboard and no login.

What happens to the group if the film does not load?

Interrupting the training clears the group on the server, so an abandoned group is not credited at the next session.

Will a latecomer join a group already in progress?

No. A scan during a running training, welcome or closing does not add the person to the group.

Are you deploying a registration workstation?

We will send the integrator a list of pitfalls and test scenarios for the acceptance protocol. Book a technical talk.

Let's talk