InnerWeb
Skip to main content

RCP pilot with a tester list: implementation notes

The working time module is switched off by default and the administrator turns it on. Before doing so, they can limit its visibility to a tester list, but an empty list means all employees. This single rule decides whether the pilot covers ten people or the whole plant.

0 people
an empty tester list means visibility for everyone
Source: working time module documentation

Starting state: module off, visibility limited by a list

The working time module is switched off by default. The administrator turns it on, and before doing so can limit its visibility to a tester list. This is the pilot mechanism: a selected group of employees sees the module and generates data, while the rest of the plant notices no change.

Remember the status of the feature. The module has been piloted on one installation, and we do not describe it as widely deployed. It also does not settle pay: it provides records and an export of hour quantities, not payroll. The rota screens, the HR tabs and the export to ERP are at the preview stage with demonstration data, and we treat them as a development option.

The most dangerous trap: an empty tester list

An empty tester list means all employees, not nobody. An administrator who turns the module on before entering the first person launches it for the whole plant. The effects are immediate: hundreds of people get access to the module, and supervisors get exception queues built from data that nobody has configured yet.

The order of operations must therefore be reversed compared with intuition: first the tester list, then turning the module on. It is worth adding this to the implementation instructions as the first control point and requiring a second person when switching it on.

Module reach: tester list vs empty list (example plant of 500 people)

Module reach: tester list vs empty list (example plant of 500 people)Comparison: with 20 testers the module is seen by 20 people; with an empty list, by all 500 employees of the example plant.0100200300400500osobyList with 20 testers: Sees the module: 20 osoby20 osobyList with 20 testersEmpty list: Sees the module: 500 osoby500 osobyEmpty list
Source: Example calculation: plant of 500 people, pilot of 20 testers; empty list rule from the module documentation

Pilot stages from preparation to extension

The following order is an implementation recommendation, not a system requirement.

Stage 1: data preparation

Before you turn the module on, check the organisational tree and the assignment of supervisors, because they decide what each person sees. The supervisor sees their sub-tree, HR sees the employees of its own company, and the employee sees themselves.

Stage 2: choosing testers

Choose a representative group: different shifts, an internal employee and an employee of an external company, a supervisor and a person from HR. A group made up only of enthusiasts will not detect the problems that appear on the night shift.

Stage 3: switching on and observation

After turning the module on, watch the gate scans, because they create the records. QR scans at the gate, also used for the evacuation list, feed the working time module. Check the exception queues and the reminder call every day.

Stage 4: closing the trial period

Close the settlement period for the test group. Closing and reopening is performed only by the HR or administrator role, so check that these roles are correctly assigned.

Stage 5: extension

Add further groups to the tester list in small batches. Only when the pilot no longer requires configuration corrections can the list be emptied, which means a scope covering all employees.

What to check before switching on

The IT administrator should go through the checklist before each switch.

  • The tester list is filled in and is not empty.
  • The organisational tree and the supervisors are assigned correctly.
  • Gate scans reach the module on a tester's account.
  • The tolerance, reminder call and uncertainty thresholds are set and agreed with HR.
  • The HR and administrator roles are held by the right people.
  • The testers have been informed about the purpose of the pilot.

What the pilot will not check

A pilot on a test group will not show the full scale of records at the gate at peak time, or the exception queues with a full workforce. Plan a separate load test at the extension stage.

The pilot will also not check the integration with the access control system. The card swipe webhook does not record the direction, entry or exit, or the event identifier, so card swipes from access control do not yet feed the working time records. The source of records remains the QR scans; the card integration requires an extension on the InnerWeb side and is a separate project.

After the pilot, prepare a short summary for management: how many testers took part, how many exceptions appeared in the queues, how many came from the threshold settings, and how many from actual gaps in the records. Such a summary is the basis for the decision to extend and evidence for an audit that the module was switched on deliberately, in a controlled group, and not by accident for the whole plant.

Video

Frequently asked questions

What does an empty tester list mean?

All employees. If the administrator turns the module on without a filled-in list, visibility covers the whole plant.

Does the module settle pay?

No. It provides working time records and an export of hour quantities; payroll remains in the client's system.

Will the pilot include card swipes from access control?

Not today. The source of records is the QR scans at the gate; card swipes require an extension of the webhook with direction and event identifier.

Sources

Plan a pilot without risk to the whole plant

We will help you choose the tester group and the order of switching the module on. Book a call with the InnerWeb team.

Let's talk