Skip to main content

Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements

Purpose of this article​

This article helps the partner validate whether the minimum technical requirements are met before the first use of Dersalis/BioLink.

Use this guide after the project's device has already been defined.

To choose between the Polar 360, Polar Verity Sense, and IS-SW1.1 smartwatch, see How to Choose the Right Device for the Operation.

When to use this article​

Use this article before:

  • preparing devices;
  • training operators;
  • performing controlled first use;
  • considering the implementation ready.

The goal is to prevent basic functional failures, such as an incompatible phone, disabled Bluetooth, a discharged sensor, blocked permissions, or insufficient connectivity.

Main rule​

No project should proceed to first use without minimal validation of phone, sensor, connectivity, permissions, and battery.

Android phone validation​

This step applies only to projects with Polar sensors.

Polar sensors don't have their own screen and depend on the Dersalis App on an Android phone for operational interaction and connectivity.

When the phone is provided as a kiosk​

When the Android phone is provided as a dedicated kiosk, locked by MDM to run only the Dersalis App, Dersalis handles the phone requirements according to the model defined for the project.

Even so, before first use, the partner should confirm:

  • phone charged;
  • Dersalis App available;
  • MDM correctly applied;
  • Bluetooth active;
  • connection with the sensor tested;
  • phone positioned in the correct usage location;
  • team briefed on where and how to use the kiosk;
  • storage and charging routine defined.

When the phone is the customer's corporate device​

When the customer provides a corporate Android phone, the device must meet the minimum requirements defined by Dersalis.

Before confirming use, validate:

  • compatible Android version;
  • ability to install the Dersalis App;
  • permissions required by the app;
  • Bluetooth active and functional;
  • available connectivity;
  • battery compatible with the routine;
  • absence of corporate blocks that prevent operation;
  • customer's MDM or security rules;
  • responsibility for device support.

If the corporate phone doesn't meet the minimum requirements, the project should not proceed with that device.

Polar sensor validation​

This step applies to projects with the Polar 360 or Polar Verity Sense.

Before first use, validate:

  • sensor charged;
  • sensor identified;
  • sensor in good physical condition;
  • sensor turns on correctly;
  • sensor connects to the Dersalis App;
  • sensor stays close to the phone during the necessary flow;
  • the operator knows how to select the correct sensor;
  • post-shift charging routine defined;
  • storage location defined.

During the test, confirm the sensor can start a shift and transmit data to the platform.

For complete preparation, see Polar Device Preparation.

IS-SW1.1 smartwatch validation​

This step applies to projects with the i.safe Mobile IS-SW1.1 smartwatch.

Before first use, validate:

  • smartwatch charged;
  • device identified;
  • screen working;
  • connectivity configured;
  • user interaction working on the device itself;
  • initial configuration applied;
  • data reaching the platform;
  • charging routine defined;
  • storage location defined;
  • local support briefed.

For complete preparation, see i.safe Mobile Device Preparation.

Bluetooth validation​

This step is especially important in projects with Polar sensors.

Before first use, confirm:

  • Bluetooth enabled on the Android phone;
  • sensor turned on;
  • sensor close to the phone;
  • Dersalis App with necessary permissions;
  • sensor selection working in the app;
  • connection tested before real operation.

Best practices:

  • run the test with the sensor close to the phone;
  • wait a few seconds and try again if there's an initial failure;
  • check sensor and phone battery;
  • restart the sensor if the connection fails repeatedly;
  • don't start training without first testing the connection.

Wi-Fi or mobile network validation​

Before first use, confirm whether available connectivity matches the project's model.

Validate:

  • Wi-Fi available, when applicable;
  • mobile network available, when applicable;
  • absence of network blocks that prevent the Dersalis App from working;
  • functioning at the real location or under conditions close to the operation;
  • data reaching the platform;
  • behavior in areas with weak signal, if any.

If connectivity is unstable, involve Dersalis before releasing the operation.

GPS validation​

Not every project requires GPS.

Before treating GPS as a requirement, confirm whether location is part of the use case.

When GPS is necessary, validate:

  • whether the chosen device supports the intended use;
  • whether the location allows adequate signal;
  • whether location appears as expected;
  • whether there are privacy restrictions or internal policy;
  • whether the customer understands how location will be used.

If GPS is essential and there's technical doubt, involve Dersalis.

Dersalis App permission validation​

This step applies to projects with the Dersalis App on an Android phone.

Confirm whether the app has the necessary permissions for the project to function, such as:

  • Bluetooth;
  • location, when necessary;
  • internet access;
  • notifications, when applicable;
  • background operation, when applicable.

Also confirm that IT policies, corporate MDM, or device restrictions don't block these permissions.

Battery and charging routine validation​

Before first use, define:

  • who charges the sensors;
  • who charges the phones, when applicable;
  • who charges the smartwatches;
  • where equipment will be charged;
  • when charging will happen;
  • who checks battery before the shift;
  • what to do if a device is discharged;
  • whether there will be backup equipment.

The charging routine needs to be defined before real operation.

Minimum technical checklist​

Before proceeding to first use, confirm:

  • approved device defined;
  • Android phone validated, when applicable;
  • Dersalis App installed and tested, when applicable;
  • sensor or smartwatch charged;
  • Bluetooth tested, when applicable;
  • Wi-Fi or mobile network validated;
  • GPS validated, when it's part of the use case;
  • permissions granted;
  • devices identified;
  • charging routine defined;
  • data reaching the platform;
  • technical focal point defined;
  • first-level support prepared.

When to involve Dersalis​

Involve Dersalis when:

  • there's doubt about technical requirements;
  • the customer wants to use a non-approved device;
  • the corporate phone doesn't meet the requirements;
  • there are IT or MDM blocks from the customer;
  • connectivity is unstable;
  • GPS is essential and there's technical uncertainty;
  • there's a persistent failure after basic diagnosis;
  • the partner isn't confident enough to release first use.

When contacting Dersalis, send:

  • customer;
  • operation;
  • chosen device;
  • phone model, when applicable;
  • Android version, when applicable;
  • connection type;
  • description of the problem or doubt;
  • tests already performed;
  • screenshots, photos, or evidence, if any.

Expected outcome​

At the end of this validation, the partner should know whether the minimum technical requirements are met to proceed with preparation, training, and first use.

Implementation should only proceed once the device, phone, connectivity, permissions, battery, and operational routine have been validated.

Next step​

After validating technical requirements, proceed to Polar Device Preparation or i.safe Mobile Device Preparation, depending on the device chosen for the project.

Summary​

This article should be used as a technical checklist before first use.

It doesn't serve to choose the device, but to confirm that the defined model is ready to operate. The partner must validate phone, sensor, Bluetooth, connectivity, GPS when applicable, permissions, battery, and charging routine before releasing the operation.