Skip to main content

i.safe Mobile Device Preparation

Purpose of this article​

This article guides the partner on how to prepare the i.safe Mobile IS-SW1.1 smartwatch for use with the Dersalis/BioLink solution.

Use this guide before delivering the device to the customer, conducting training, or performing controlled first use.

This article applies to the currently approved device:

  • i.safe Mobile IS-SW1.1 smartwatch.

To validate general connectivity, battery, and operation requirements before preparation, see Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements.

Before you start​

The i.safe Mobile IS-SW1.1 smartwatch is a wearable device with its own screen and connectivity.

Unlike Polar sensors, it doesn't depend on an Android phone as an operational interface. User interaction and connectivity happen directly through the smartwatch itself, according to the model defined for the project.

In practice, the device can handle:

  • wearable use during the shift;
  • interaction with the operator;
  • displaying information;
  • connectivity;
  • data transmission;
  • operational flow defined for the implementation.

Partner responsibility​

In partner-led implementations, the partner must ensure IS-SW1.1 devices are ready before delivering them to the customer or starting training.

This includes:

  • checking the devices received;
  • charging the smartwatches;
  • identifying each device;
  • validating screen functionality;
  • validating connectivity;
  • confirming initial configuration;
  • testing data transmission;
  • guiding the customer on charging, storage, and use;
  • logging pending items before first use.

The customer should not receive devices without minimal functionality testing.

Step 1: check the devices received​

When receiving the smartwatches, check:

  • device model;
  • quantity received;
  • accessories received;
  • chargers;
  • straps;
  • physical condition of devices;
  • screen;
  • buttons, when applicable;
  • visual identification or serial number;
  • signs of damage, wear, poor contact, or apparent failure.

If there's a discrepancy in quantity, model, accessories, or physical condition, log it before proceeding.

Step 2: identify the devices​

Each smartwatch should be easy to identify during implementation and operation.

Identification can be done via:

  • a label;
  • an internal code;
  • a serial number;
  • a name defined for the project;
  • a spreadsheet or control record.

Identification is important to avoid:

  • incorrect swapping between operators;
  • support difficulties;
  • loss of traceability;
  • confusion during training;
  • replacement problems;
  • difficulty linking device, customer, and operation.

Whenever possible, keep a record with:

  • device identification;
  • serial number;
  • customer;
  • unit or operation;
  • device status;
  • responsible party for receipt or use;
  • support notes.

Step 3: charge the smartwatches​

Before any test or delivery, charge the devices.

Best practices:

  • charge the smartwatches before first use;
  • use the appropriate chargers;
  • confirm the device is correctly seated in the charger;
  • avoid delivering partially discharged devices;
  • define a charging routine at the end of each shift;
  • confirm who will be responsible for charging the equipment;
  • confirm where the equipment will be stored.

The charging routine needs to be clear before real operation.

Step 4: validate physical functionality​

Before configuring or delivering the device, validate basic physical functionality.

Check:

  • screen turns on correctly;
  • touch response, when applicable;
  • buttons working, when applicable;
  • strap in good condition;
  • comfortable fit on the wrist;
  • charging working;
  • absence of visible damage;
  • device identification legible.

If there's a physical failure, the device should not be used in training or operation.

Step 5: validate connectivity​

The IS-SW1.1 depends on the connectivity configured for the project.

Before first use, confirm:

  • network configured according to the project;
  • connectivity available at the test location;
  • absence of blocks that prevent transmission;
  • data reaching the platform;
  • appropriate behavior under conditions close to real operation.

When the operation depends on real-time monitoring, connectivity should be tested in the usage environment or under an equivalent condition.

If there's unstable signal, network block, or transmission failure, resolve it before delivery to the customer.

Step 6: confirm initial configuration​

Before releasing the device for use, confirm the project's initial configuration was applied.

Validate:

  • device associated with the correct customer or operation, when applicable;
  • initial parameters configured;
  • usage flow available on the smartwatch;
  • correct language, when applicable;
  • access or authentication configured, when applicable;
  • necessary permissions enabled;
  • communication with the platform working.

If the initial configuration hasn't been applied yet, the device should not be considered ready.

Step 7: test operational flow​

The partner should test the basic flow planned for the project before training.

During the test, confirm:

  • device turns on correctly;
  • operator can interact with the screen;
  • shift-start flow works, when applicable;
  • data is transmitted;
  • information appears on the platform;
  • any alerts or messages appear as expected;
  • pause or end works, when applicable;
  • the focal point can verify usage on the platform.

The goal is to validate the complete path: device in use, data transmission, and viewing on the platform.

Step 8: validate wear on the body​

The smartwatch needs to be worn correctly to avoid compromising data collection and the operator's experience.

Guide that the device should:

  • stay firm on the wrist;
  • remain comfortable;
  • not be loose;
  • not interfere with the use of PPE;
  • not disrupt the operational activity;
  • be kept on during the shift according to project guidance;
  • be removed and stored correctly at the end of use.

If the device causes discomfort, interferes with the routine, or cannot be used with necessary PPE, the partner should log the problem and evaluate it with Dersalis before proceeding.

Step 9: define charging, storage, and delivery routine​

The operation needs a clear routine for the smartwatches.

Define with the customer:

  • where devices will be stored;
  • who delivers devices to operators;
  • who collects them at the end of the shift;
  • who puts them on the charger;
  • who checks charge before the next use;
  • how problem devices will be set aside;
  • how backup devices will be used, if any;
  • who should be notified in case of failure.

Without a charging and storage routine, the operation tends to face recurring problems at the start of the shift.

Step 10: prepare guidance for operators​

Before training, the partner should prepare a simple explanation for operators.

The operator should know:

  • why they'll use the device;
  • how to wear the smartwatch;
  • how to start use, according to the project;
  • how to interact with the screen;
  • what to do when facing messages or alerts;
  • how to pause or end, when applicable;
  • how to care for the device;
  • where to return the device at the end of the shift;
  • who to contact in case of doubt.

Training should be practical and direct.

IS-SW1.1 preparation checklist​

Before considering the smartwatch ready, confirm:

  • devices received and checked;
  • accessories checked;
  • devices identified;
  • devices charged;
  • screen working;
  • strap in good condition;
  • connectivity configured;
  • data transmission tested;
  • initial configuration applied;
  • operational flow tested;
  • data reaching the platform;
  • wearing validated;
  • charging routine defined;
  • storage routine defined;
  • operator guidance prepared;
  • customer's focal point defined;
  • first-level support prepared.

Common preparation problems​

Device doesn't turn on​

Check:

  • smartwatch charge;
  • fit in the charger;
  • charger used;
  • minimum charging time;
  • signs of physical damage.

Device turns on but doesn't transmit data​

Check:

  • connectivity;
  • initial configuration;
  • available network;
  • association with the correct customer or operation;
  • necessary permissions or access;
  • whether data appears after a new test.

Screen doesn't respond correctly​

Check:

  • whether the device is locked;
  • whether there's visible damage;
  • whether touch responds on other screens;
  • whether the device needs to be restarted;
  • whether the problem occurs on more than one device.

Operator can't use the flow​

Check:

  • whether the operator was trained;
  • whether the flow is available on the device;
  • whether the language is appropriate;
  • whether the screen is responding;
  • whether the operation is following the correct procedure.

Data doesn't appear on the platform​

Check:

  • whether the device was used correctly;
  • whether the applicable shift or flow was started;
  • whether there's connectivity;
  • whether the device is correctly associated;
  • whether there's a synchronization delay;
  • whether the platform is showing the correct operation.

If the problem persists after basic diagnosis, contact Dersalis.

What to avoid​

Avoid:

  • delivering a smartwatch without charge;
  • delivering a device without identification;
  • starting training without testing data transmission;
  • considering the device ready just because it turns on;
  • ignoring connectivity failures;
  • not defining who's responsible for charging and storage;
  • not validating whether the device can be used with PPE;
  • letting the customer figure out on their own how to operate the device;
  • escalating a problem to Dersalis without testing charge, connectivity, and initial configuration.

When to involve Dersalis​

Involve Dersalis when:

  • the device doesn't transmit data after basic checks;
  • there's a persistent connectivity failure;
  • there's unexpected behavior in the smartwatch flow;
  • data doesn't reach the platform after a correct test;
  • there's doubt about initial configuration;
  • the device seems unsuitable for the operation;
  • the customer reports incompatibility with PPE or operational routine;
  • the partner cannot validate the flow before first use;
  • there's suspicion of a device defect.

When contacting Dersalis, send:

  • customer;
  • operation;
  • device identification;
  • description of the problem;
  • time of the test;
  • type of connectivity used;
  • screenshots, photos, or videos, if any;
  • steps already tested;
  • impact on implementation.

Expected outcome​

At the end of preparation, the partner should have IS-SW1.1 smartwatches ready for use, with adequate charge, identification, validated connectivity, applied initial configuration, tested operational flow, and data reaching the platform.

The operation should only proceed to training or first use once the device and platform are working together.

Next step​

After preparing i.safe Mobile devices, proceed to Technical Checklist Before Customer Delivery to confirm that all technical and operational items are ready before delivery or first use.

Summary​

The i.safe Mobile IS-SW1.1 smartwatch should be prepared before delivery to the customer.

The partner must check, identify, charge, validate connectivity, confirm initial configuration, test the operational flow, guide correct use, and ensure data reaches the platform before real first use.