InnerWeb
Skip to main content

Watch fleet in MDM: kiosk mode and lock

A watch issued to a worker should do one thing: run the system app. Every other app, game or setting is a risk to the battery, the data and security. Good practices describe the configuration of a watch fleet in MDM, kiosk mode, remote lock of a lost device and a checklist for the IT administrator.

1
app available in kiosk mode
approx. PLN 400
per month for renting 4 watches with SIM and MDM, net

Why MDM for watches

LTE watches are managed as a fleet through MDM: configuration, kiosk mode (only the system app), remote lock and data protection on the device. Without MDM, each watch is configured by hand, and after several dozen units the manual settings drift apart. MDM is one place from which the administrator pushes settings to the whole fleet and sees which devices did not accept them.

Good configuration practices

Below is a breakdown by case, in the order in which they most often appear in real rollouts.

Reference profile

Build one reference profile and clone it for groups. The profile contains the app settings, permissions, disabled stores and network settings. A change in the profile reaches all devices.

Kiosk mode

Set kiosk mode so that only the system app starts. The worker should have no access to settings, the store or other apps. This removes accidental closing of the app and extends battery life.

Button remapping

The watch button works for SOS through the companion app after remapping in the management system (Knox). The watch face itself does not read the button. The remapping goes into the reference profile so it is not done by hand.

Remote lock

Define a procedure for a lost device: who starts it, within what time and how it is confirmed. Remote lock protects the data on the device and prevents the watch being used by an unauthorised person.

Updates

Roll out updates in stages: first a few test devices, then a pilot group, and only at the end the whole fleet. An update that changes the behaviour of the button can switch off SOS.

Stages of rolling out the profile to the fleet (example)

Stages of rolling out the profile to the fleet (example)Chart of the staged rollout of the profile: test devices, group, whole fleet.020406080100% of fleetTest devicesTest devices: 5 % of fleet5Pilot groupPilot group: 20 % of fleet20Whole fleetWhole fleet: 100 % of fleet100
Source: Example calculation: staged update rollout

The role of the IT administrator and OHS

The IT administrator is responsible for the profile and security, but OHS defines the requirements for the alarm. Agree together what must always work: SOS, stillness detection, position reporting. After every profile change, run a test alarm on a test device. The LiveWorker app runs on watches with Wear OS, scans BLE beacons and detects stillness and falls, so the test should check each of these elements.

Document the profile version and the date of deployment. When after a month some watches stop reporting their position, the change history will show what changed.

Lost and damaged devices

Define what a worker does after losing a watch: reports it at reception or to the supervisor, and the administrator locks the device in MDM. After it is found, the device needs reconfiguration or unlocking according to the procedure. A reserve of devices allows a replacement watch to be issued without interrupting work.

For LTE watches, the rental cost of four watches with SIM and MDM is approximately PLN 400 net per month (ranges from 2025-2026 deployments, individual quotation). It is worth adding the administrator's time to the fleet cost.

What to record in the fleet documentation

Fleet documentation is one page per device or group: number, assignment, profile version, date of the last update and status. For the IT audit, attach the lock policy and the list of people with MDM permissions. For OHS, attach the results of test alarms after each profile change. This set shortens the answer to the auditor's question of who changed the settings, and when, that decide whether a worker can call for help.

Verification after rollout

Every week during the first month, check the fleet's compliance with the reference profile, the list of devices without connectivity and the battery state. Watches that have not reported for several hours need diagnosis: is it a flat battery, no coverage, or a setting? The device log sent to the server will help.

After a month, run a review: which settings blocked work and which devices failed. Make changes in the reference profile, not in individual watches.

Checklist

Video

Frequently asked questions

Is MDM necessary for a few watches?

For a few, settings can be made by hand, but with several dozen the manual settings drift apart. MDM becomes a necessity.

What does kiosk mode give?

The watch starts only the system app, and the worker has no access to settings or other apps.

Does remote lock delete the data?

The lock protects the data and prevents use of the device. The scope depends on the MDM policy set by the administrator.

Can an update switch off SOS?

Yes, if it changes the behaviour of the button. That is why updates are tested in stages.

Let's talk about devices at your plant

We will show how to match devices to roles and how the system connects them on one map. Book a conversation with the InnerWeb team.

Let's talk