Skip to main content

MDM Configuration, When Applicable

Purpose of this article​

This article guides the partner on when MDM configuration applies in projects with the Dersalis/BioLink solution.

Use this guide to understand the role of MDM, when it should be used, what precautions are needed, and how to validate that the Dersalis App is working correctly after configuration.

Dersalis currently uses Hexnode as the MDM solution for Android phones configured as kiosks or devices dedicated to Dersalis's use.

To understand when an Android phone is needed, see Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements.

What is MDM​

MDM stands for Mobile Device Management.

In practice, MDM allows configuring, restricting, and controlling phones used in an operation, ensuring they work in a standardized way with lower risk of misuse.

In Dersalis projects, MDM can be used to turn an Android phone into a device dedicated to the Dersalis App, for example in kiosk format.

When MDM applies​

MDM applies when the project uses Polar sensors with the Dersalis App on an Android phone and there's a need to standardize or restrict device usage.

This can happen when:

  • the phone will be used as a kiosk;
  • the phone will be dedicated to the Dersalis project;
  • the device should run only the Dersalis App;
  • the customer doesn't want to allow free use of the phone;
  • it's necessary to reduce the risk of configuration changes;
  • it's necessary to guarantee a standardized experience for operators;
  • the phone will be available in a shared location;
  • the partner or customer needs to control app installation, permissions, and usage.

MDM isn't necessary in every project. It should be used when it makes sense for the defined operational model.

When MDM doesn't apply​

MDM may not be necessary when:

  • the project uses the i.safe Mobile IS-SW smartwatch;
  • the Dersalis App won't be used on an Android phone;
  • the customer already has internally managed corporate phones;
  • the customer will use their own devices with an already defined IT policy;
  • the operational model doesn't require a dedicated or locked phone.

When the customer uses their own corporate Android phone, there may be the customer's own MDM. In that case, it's necessary to validate that the customer's internal rules don't block the Dersalis App from working.

Difference between kiosk phone and corporate phone​

Android phone in kiosk mode​

In kiosk mode, the phone is dedicated to the Dersalis project and configured to run only the Dersalis App.

In this scenario:

  • the phone is prepared for controlled use;
  • the Dersalis App is available as the main application;
  • other device functions may be restricted;
  • the operator uses the phone only for the necessary flow;
  • Dersalis handles the phone requirements according to the model defined for the project;
  • the MDM used by Dersalis is Hexnode.

This model is recommended when the project needs a standardized and controlled flow.

Customer's corporate Android phone​

In the case of the customer's corporate phone, the device belongs to or is managed by the customer.

In this scenario:

  • the phone must meet Dersalis's minimum requirements;
  • the Android version must be compatible;
  • the Dersalis App must be installable;
  • necessary permissions must be granted;
  • Bluetooth, connectivity, and battery must work;
  • the customer's IT policies or MDM cannot block the app;
  • device support may depend on the customer.

If the customer's corporate MDM blocks permissions, connections, or background operation, the device may not be suitable for use in the project.

Hexnode's role​

Hexnode is the MDM solution used by Dersalis to manage Android phones dedicated to the project.

It can be used to:

  • restrict phone usage to the Dersalis App;
  • reduce access to unnecessary apps;
  • standardize settings;
  • control permissions;
  • facilitate kiosk mode usage;
  • reduce the risk of user changes;
  • simplify the operator's experience.

The partner should not change Hexnode settings without guidance from Dersalis.

Where to find the configuration step-by-step​

This article explains when MDM applies and what should be validated before operational use.

To configure an Android phone in kiosk mode with Hexnode, follow the How to Configure an Android Phone in Kiosk Mode with Hexnode article.

The partner should not improvise MDM configuration or change Hexnode policies without guidance from Dersalis.

Partner responsibility​

When there's a kiosk phone or MDM involved, the partner must ensure the device is ready for use before delivery or first use.

This includes validating:

  • phone charged;
  • Dersalis App available;
  • MDM applied;
  • phone locked according to the planned flow;
  • Bluetooth active;
  • connection with Polar sensor working;
  • connectivity available;
  • necessary permissions granted;
  • charging routine defined;
  • usage location defined;
  • focal point informed about how the kiosk works.

The partner doesn't need to change advanced MDM policies, but needs to confirm the operational flow works.

What to validate after applying MDM​

Once the phone is configured with MDM, validate real use of the Dersalis App.

Confirm:

  • the phone turns on correctly;
  • the Dersalis App opens without blocks;
  • the user can start a shift;
  • the user can enter an ID or identifier, when applicable;
  • the Polar sensor appears for selection;
  • Bluetooth works;
  • the sensor connects;
  • the shift starts correctly;
  • data reaches the platform;
  • pause or end works, when applicable;
  • the operator cannot exit the planned flow, if kiosk mode is configured;
  • the phone remains operational after restarting.

Don't consider the device ready just because MDM was installed. The complete flow needs to be tested.

Permissions that should not be blocked​

Necessary permissions may vary depending on the Dersalis App version and the project model, but the partner should pay attention so MDM doesn't block essential resources.

In general, the Dersalis App may depend on:

  • Bluetooth;
  • internet access;
  • location, when needed for connection or use case;
  • notifications, when applicable;
  • background operation, when applicable;
  • access to resources required by the project's flow.

If any essential permission is blocked, the app may show connection failure, difficulty finding the sensor, data interruption, or unexpected behavior.

Precautions with customer's MDM​

When the customer uses their own corporate phone, they may have their own MDM or security policy.

In that case, the partner should validate with the customer whether the device allows:

  • installing the Dersalis App;
  • enabling Bluetooth;
  • keeping Bluetooth working during use;
  • granting necessary permissions;
  • accessing the internet;
  • keeping the app active as needed;
  • using location, if applicable;
  • displaying notifications, if applicable;
  • avoiding battery-saver blocks that interrupt the app.

If the customer's MDM prevents correct operation, the partner should log the problem and involve Dersalis before proceeding.

What to avoid​

Avoid:

  • delivering a kiosk phone without testing the Dersalis App;
  • treating a configured MDM as synonymous with a validated operation;
  • changing Hexnode policies without guidance from Dersalis;
  • using the customer's corporate phone without validating requirements;
  • ignoring Bluetooth, internet, or permission blocks;
  • starting training with a phone that hasn't been tested;
  • leaving the customer without knowing where to charge or store the phone;
  • allowing the operator to change critical device settings;
  • escalating a problem to Dersalis without testing the app, Bluetooth, sensor, and connectivity.

Dersalis App doesn't open​

Check:

  • whether the app was installed correctly;
  • whether MDM allows the app to open;
  • whether the device is in the correct mode;
  • whether there's a policy block;
  • whether the phone was restarted after configuration.

Sensor doesn't appear in the app​

Check:

  • whether Bluetooth is active;
  • whether MDM doesn't block Bluetooth;
  • whether the app has necessary permissions;
  • whether the sensor is turned on and nearby;
  • whether the sensor is charged.

App opens, but the shift doesn't start​

Check:

  • internet connection;
  • ID or identifier entered;
  • app permissions;
  • customer/operation configuration;
  • whether the app is in the correct environment;
  • whether there's a network or corporate policy block.

Phone exits kiosk mode​

Check:

  • whether the Hexnode profile is applied;
  • whether there was a restart or manual change;
  • whether the device is associated with the correct profile;
  • whether the lockdown policy is active.

App loses functionality after screen lock​

Check:

  • battery saver;
  • background operation permissions;
  • MDM policy;
  • Android settings;
  • connection stability.

MDM validation checklist​

Before considering the phone ready, confirm:

  • usage model defined: kiosk or corporate phone;
  • Hexnode applied when it's a Dersalis kiosk;
  • Dersalis App installed;
  • Dersalis App opens correctly;
  • Bluetooth active;
  • permissions granted;
  • connection with sensor tested;
  • shift started successfully;
  • data reaching the platform;
  • kiosk mode working, when applicable;
  • device remains functional after restart;
  • charging routine defined;
  • usage location defined;
  • customer's focal point briefed.

When to involve Dersalis​

Involve Dersalis when:

  • there's doubt about Hexnode configuration;
  • the kiosk phone isn't working after configuration;
  • the Dersalis App is blocked by a policy;
  • Bluetooth is blocked;
  • essential permissions cannot be granted;
  • the customer's corporate phone doesn't meet requirements;
  • there's a conflict with the customer's MDM;
  • the app works before MDM but fails afterward;
  • the partner cannot validate the complete flow.

When contacting Dersalis, send:

  • customer;
  • operation;
  • phone model;
  • whether it's kiosk or corporate;
  • Android version;
  • whether it uses Hexnode or the customer's MDM;
  • description of the problem;
  • screenshots or photos, if any;
  • steps already tested;
  • impact on implementation.

Expected outcome​

At the end of validation, the Android phone should be ready for use with the Dersalis App, without blocks that harm Bluetooth, connectivity, permissions, or operational flow.

If the phone is in kiosk mode, Hexnode should be correctly applied and the device should allow controlled use of the Dersalis App according to the project.

Next step​

After validating the MDM configuration, proceed to Technical Checklist Before Customer Delivery to confirm that all technical and operational items are ready before delivery or first use.

Summary​

MDM is used when the project needs to control Android phones dedicated to the Dersalis App, especially in the kiosk model.

Dersalis uses Hexnode for this purpose. The partner must validate that the Dersalis App works correctly after configuration, that Bluetooth, connectivity, and permissions are enabled, and that the phone is ready for operational use.

When the customer uses their own corporate phone, the partner should check whether the customer's MDM or internal policies don't prevent the Dersalis App from working.