Technical: +47 908 38 730 , Commercial: +47 958 20 005 post@swimeye.no

Part 8 – SwimEye Product Guide

Part 8 – SwimEye On-Duty

Getting the most out of your drowning detection system after the handover.

Adopting Digital Lifeguarding

After the handover, it is important that pool lifeguards use SwimEye as much as possible to become familiar with the functions and performance.

Pool management should champion the process, by implementing new routines or updated procedures that incorporate the SwimEye concept of Digital Lifeguarding.  This one proactive action can be the difference between a successful new Digital Lifeguarding culture or the failure of lifeguards to adopt the drowning detection system into their workplace.

One important actions, is for pool management to identify a “super-user”.  This is often the pool manager or head lifeguard.

The super-user is allocated responsibility to teach other lifeguards how to use SwimEye and check their understanding as they learn.  This includes training other lifeguards in the Digital Lifeguarding activities and implementing changes to the daily routines.

The super-user can become a real instrument for change to the lifeguard culture and also, they can become the contact person for SwimEye after the handover date.

Regular Dialogue with SwimEye

In the first few weeks and months after handover, it is common for SwimEye to fine tune the monitoring zones of each camera and find improvements to the detection performance.  This period can also include small changes to the graphic user interface or adjustments to lifeguard routines, based on operational experience from the pool lifeguards in this time after handover.

SwimEye will promote an active and open dialogue with all clients after handover.

From our experience, this open dialogue can result in shared improvement opportunities and increased safety for pool users.  The dialogue can be simple troubleshooting questions from pool lifeguards or feedback regarding system performance.

Understanding the effect of pool lighting, movable structures and pool cleaning equipment on the computer vision system, can help the SwimEye super-user dramatically reduce the number of preventable false alarms through implementation of Digital Lifeguarding.

SwimEye is always more than happy to speak to pool lifeguards and clients at any time throughout the installation process and after handover.

Quality Customer Service

When you purchase a SwimEye product, we are always there for you, should something unexpected occur.  We consider our quality customer service as a competitive advantage in the market place.

 

Read more here

Regular System Testing by the Lifeguards

Regular system testing is one of the most important activities to help lifeguards learn more about SwimEye following the handover process.  Daily testing helps lifeguards to understand both the system functions, user-interface and detection performance.  It can also highlight any changes to the detection performance as the water quality changes throughout each cleaning cycle or in different lighting conditions, at different times of the day.

SwimEye recommends that at least one random test procedure be undertaken daily, in each pool.  This could be prior to public opening hours each day or at the start of each shift for each lifeguard.

Throughout each week/month, the test positions can be changed to ensure all parts of the pool are tested on a regular basis and at different times of the day.  Testing should also occur with full activity in the pool (i.e. when the pool is in use by swimmers).

SwimEye recommends that the system test is undertaken with full activity in the pool (i.e. when the pool is in use by swimmers).  This will ensure pool lifeguards and management verify and understand the SwimEye detection performance in real operating conditions.

A systematic approach to daily testing should be implemented by the pool manager or super-user, in accordance with the SwimEye user manual.  Record keeping by the pool manager is an important part of the testing process.  Any changes to system performance should be reported back to SwimEye, to ensure improvement opportunities can be implemented. 

Example of a system test of a double drowning scenario (viewed from the graphic user interface).

Example of a random daily system test with the rescue dummy (viewed from the under-water camera).

Example of a system test non-conformance, the rescue dummy must be raised to the surface after each test drop.

Want to learn more about SwimEye?

Pin It on Pinterest