Skip to main content

How to Choose the Right Device for the Operation

Purpose of this article​

This article guides the partner on how to choose the most suitable device for an operation that will use the Dersalis/BioLink solution.

Use this guide to understand when to use Polar sensors with the Dersalis App on an Android phone and when to use the i.safe Mobile IS-SW1.1 smartwatch.

This article only considers devices currently approved for use with the solution:

  • Polar 360;
  • Polar Verity Sense;
  • i.safe Mobile IS-SW1.1 smartwatch.

Requests for other sensors, watches, or devices should be treated as specific requests and evaluated with Dersalis before any commitment to the customer.

For technical connectivity details and minimum requirements, see Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements.

Why device choice matters​

Dersalis/BioLink depends on suitable devices to collect data during the operational shift and ensure information reaches the platform correctly.

Choosing incorrectly can lead to:

  • connection failures;
  • low operator adoption;
  • difficulty starting a shift;
  • battery problems;
  • incomplete data;
  • implementation delays;
  • need for recurring support;
  • incompatibility with the customer's routine or environment.

That's why device choice should be made before implementation and validated according to the operation's reality.

Main rule​

The device should be chosen based on the operation, technical requirements, and how the user will interact with the system.

First understand the environment, routine, and requirements of the operation. Then choose among the approved devices.

The partner should not offer non-approved devices as a commercial alternative without prior validation from Dersalis.

Currently approved devices​

Dersalis/BioLink is currently approved for use with:

Polar 360​

Wearable sensor without a screen, used for data collection during the shift.

Since it has no screen of its own, it depends on the Dersalis App on an Android phone for the operational interaction and connectivity needed by the flow.

Polar Verity Sense​

Wearable sensor without a screen, used for data collection during the shift.

Like the Polar 360, it depends on the Dersalis App on an Android phone for operational interaction and connectivity needed by the flow.

i.safe Mobile IS-SW1.1 Smartwatch​

Wearable device with its own screen and connectivity.

In this model, user interaction and connectivity happen directly through the smartwatch, without the same dependency on an Android phone as an operational interface.

How to decide between the models​

The choice should mainly consider:

  • the operation's environment;
  • whether the device needs a screen or not;
  • the possibility of using an Android phone;
  • available connectivity;
  • shift duration;
  • ruggedness or certification requirements;
  • charging, storage, and distribution routine;
  • ease of training operators;
  • local support available.

The best choice is the one that allows starting the operation safely, simply, and reliably.

Model 1: Polar sensors with the Dersalis App on an Android phone​

This model applies to use with:

  • Polar 360;
  • Polar Verity Sense.

Here, the sensor collects data during the shift, while the Android phone with the Dersalis App works as the operational interface and connectivity medium.

The Android phone can be used to:

  • start the shift;
  • identify the operator, for example by ID;
  • select the sensor;
  • maintain the Bluetooth connection with the sensor;
  • transmit data;
  • allow pausing or ending the shift, when applicable;
  • display operational messages from the app.

The phone should not be understood as the primary collection device. Collection is done by the Polar sensor.

When to use Polar sensors​

Polar sensors may be suitable when:

  • the operation allows using an Android phone near the sensor;
  • the Bluetooth connection is viable;
  • the operator can start a shift through the Dersalis App;
  • there's a clear routine for charging and storing the sensor;
  • there's a clear routine for making the phone available during the operation;
  • the environment doesn't require an intrinsically safe device;
  • the flow with a screenless sensor is sufficient for the operation.

This model is especially suitable when using the Dersalis App on an Android phone is feasible and doesn't interfere with the operational routine.

Ways to provide the Android phone​

When the project uses Polar sensors, the Android phone can be provided in two main ways.

Android phone in kiosk mode​

In this model, the phone is dedicated to Dersalis's use and configured to run only the Dersalis App.

Typically, this phone is locked via MDM and works as a fixed or controlled point of interaction for shift start, sensor selection, and other necessary actions.

In this case, Dersalis handles the phone requirements according to the model defined for the project.

May be suitable when:

  • the customer doesn't want to depend on individual corporate phones;
  • the operation needs a more standardized flow;
  • the partner or Dersalis needs to reduce the risk of misuse of the device;
  • the phone will remain in a controlled location;
  • the goal is to simplify interaction for the operator.

Points of attention:

  • the phone must be charged;
  • the Dersalis App must be available;
  • MDM must be correctly applied;
  • the usage location must allow connection with the sensors;
  • the team needs to know where the kiosk will be available;
  • there must be a storage and charging routine.

Customer's corporate Android phone​

In this model, the customer provides corporate Android phones for use with the Dersalis App.

In this case, the phones must meet the minimum requirements defined by Dersalis, including Android version, permissions, connectivity, and other applicable technical conditions.

May be suitable when:

  • the customer already has corporate phones available;
  • the devices meet the minimum requirements;
  • internal policy allows installing and using the Dersalis App;
  • necessary permissions can be granted;
  • there's control over updates, charging, and device availability.

Points of attention:

  • Android version;
  • app permissions;
  • Bluetooth active;
  • connectivity;
  • battery;
  • customer's security policy;
  • app installation restrictions;
  • any MDM from the customer itself;
  • responsibility for device support.

The partner should validate these points before confirming that the customer's corporate phone can be used.

Model 2: i.safe Mobile IS-SW1.1 smartwatch​

In this model, the operator uses the i.safe Mobile IS-SW1.1 smartwatch.

The device has its own screen and connectivity, allowing user interaction and data transmission to happen directly through the smartwatch, according to the project configuration.

This model reduces the dependency on an Android phone as an operational interface.

When to use the i.safe Mobile IS-SW1.1 smartwatch​

The IS-SW1.1 smartwatch may be suitable when:

  • the operation needs a wearable device with a screen;
  • interaction should happen directly on the device;
  • using an Android phone isn't desirable or isn't feasible;
  • the operation requires greater ruggedness;
  • there are specific industrial or safety requirements;
  • the environment requires greater attention to equipment certification;
  • the customer needs a more integrated solution on the device itself.

Before offering this model, the partner should confirm whether it's suitable for the environment, local availability, and the customer's requirements.

Criteria for choosing between Polar and IS-SW1.1​

Use the criteria below to guide the decision.

Choose Polar sensors when:​

  • the customer accepts using an Android phone in the flow;
  • use via the Dersalis App is feasible;
  • the Bluetooth connection is adequate;
  • the operation doesn't require an industrial device with its own screen;
  • the environment allows using the sensor + phone combination;
  • the partner can guarantee a charging routine and phone availability.

Choose IS-SW1.1 when:​

  • the operation needs a device with a screen;
  • the flow should reduce dependency on an Android phone;
  • there are stronger industrial requirements;
  • the customer needs a more rugged device;
  • the operation requires greater control on the wearable itself;
  • the smartwatch's own connectivity is more suitable for the project.

Technical and operational evaluation criteria​

Before choosing the device, evaluate the points below.

Type of operation​

Understand where and how the worker operates.

Useful questions:

  • Is the operation industrial, logistics, road transport, port, outdoor, or field-based?
  • Is the worker stationary or moving?
  • Does the operation happen in a vehicle, machine, production area, or open environment?
  • Is there exposure to dust, heat, humidity, vibration, impact, or explosion risk?
  • Is there a restriction on using a phone?
  • Does the equipment need to be more rugged?

User profile​

Assess who will use the device.

Useful questions:

  • Is the user an operator, driver, field worker, or another profile?
  • Can the user interact with the app during the shift?
  • Is using a phone allowed in the routine?
  • Does the user wear gloves, uniform, PPE, or other equipment?
  • Can the sensor be worn correctly in the specified location?
  • Could the device cause discomfort or interfere with the activity?

Shift duration​

Battery life should be compatible with the expected usage time.

Check:

  • average shift duration;
  • existence of long shifts;
  • possibility of charging between shifts;
  • routine for returning and charging equipment;
  • need for continuous use;
  • risk of the device discharging before the end of the shift.

Connectivity​

Connectivity defines how data will be transmitted and monitored.

Assess:

  • whether there will be a phone near the sensor, in the case of Polar sensors;
  • whether the Bluetooth connection is feasible;
  • whether Wi-Fi will be available;
  • whether a mobile network will be used;
  • whether there are areas without signal;
  • whether the operation requires real-time monitoring;
  • whether the chosen device has connectivity compatible with the project.

Operations with low connectivity require more careful evaluation before implementation.

Location and GPS​

Not every use case requires location.

Assess:

  • whether the customer needs to track location;
  • whether location is needed in real time;
  • whether the environment allows a GPS signal;
  • whether there are privacy restrictions or location-use restrictions;
  • whether the chosen device meets the project's requirement.

Safety and certification requirements​

Some operations require specific devices.

Assess:

  • whether the environment is classified;
  • whether an intrinsically safe device is required;
  • whether there are mandatory certifications;
  • whether there are applicable local standards;
  • whether the customer requires internal approval of the equipment;
  • whether there are restrictions on using a phone, battery, or Bluetooth.

When there's a certification requirement, the partner should involve Dersalis before confirming the scope to the customer.

Preparation and support logistics​

Beyond working technically, the device needs to be easy to prepare, deliver, charge, maintain, and replace.

Assess:

  • who will buy or rent the devices;
  • who will receive the equipment;
  • who will install the Dersalis App, when applicable;
  • who will configure MDM, when applicable;
  • who will identify the sensors;
  • who will do the daily charging;
  • who will store the equipment;
  • who will handle replacement in case of failure;
  • who will provide first-level support.

A good device for the project is one that can also be managed in the routine.

What to avoid​

Avoid:

  • offering non-approved devices;
  • choosing a device before understanding the operation;
  • promising future compatibility as if it were current availability;
  • promising a device without validating certifications;
  • assuming connectivity will be sufficient without testing;
  • treating the Android phone as the primary collection device;
  • using the customer's corporate phone without validating minimum requirements;
  • delivering a sensor without a defined charging routine;
  • starting operation without a connection test;
  • choosing a device based only on lowest cost;
  • ignoring operator comfort and adoption;
  • leaving device selection for implementation day.

Checklist for device selection​

Before confirming the choice, check:

  • the operation has been understood;
  • the user profile has been mapped;
  • shift duration has been considered;
  • connectivity has been assessed;
  • the need for GPS has been defined;
  • safety requirements have been checked;
  • an approved device has been chosen;
  • the need for an Android phone has been confirmed or ruled out;
  • the phone model has been defined: Dersalis kiosk or customer's corporate phone;
  • for corporate phones, minimum requirements have been validated;
  • the charging and storage routine has been defined;
  • technical preparation is feasible;
  • the customer knows who will be responsible for the equipment;
  • the partner knows how to provide initial support;
  • non-standard cases have been validated with Dersalis.

When to involve Dersalis​

Involve Dersalis when:

  • there's doubt about the best device;
  • the customer requests a non-approved device;
  • the operation requires certification;
  • there are relevant technical restrictions;
  • connectivity is uncertain;
  • there's a need for integration with other systems;
  • the project involves large scale;
  • the opportunity is linked to a bid/tender;
  • there's doubt about using the customer's corporate phone;
  • the partner isn't confident enough to confirm the technical scope.

Before involving Dersalis, gather information about the operation, environment, number of users, shift, connectivity, safety requirements, and devices under consideration.

Expected outcome​

At the end of the evaluation, the partner should know:

  • which approved device is best suited to start the operation;
  • whether the project will use the Polar 360, Polar Verity Sense, or IS-SW1.1 smartwatch;
  • whether an Android phone will be needed;
  • whether the phone will be provided as a kiosk or as the customer's corporate phone;
  • which technical requirements need to be validated;
  • who will be responsible for acquisition, preparation, and support;
  • how devices will be used in the routine;
  • which risks need to be addressed before implementation;
  • whether the decision needs validation from Dersalis.

Next step​

After choosing or pre-selecting the device, see Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements to validate the minimum technical conditions before proceeding.

Summary​

Device choice should start from the operation's reality and consider only devices currently approved for Dersalis/BioLink.

Today, the approved models are the Polar 360, Polar Verity Sense, and the i.safe Mobile IS-SW1.1 smartwatch.

Polar sensors require using the Dersalis App on an Android phone as the interface and connectivity. The IS-SW1.1 smartwatch has its own screen and connectivity, reducing dependency on an Android phone.

The partner should validate the environment, connectivity, shift, certifications, logistics, and support before confirming the device with the customer.