SmartSafety¶
Call for help … even if you can no longer do it yourself! Automatic monitoring & emergency call system for early detection of critical situations. Reduces rescue response times by up to 90%. With companion rescue navigation.
Why SmartSafety?¶
Every year, more than 20,000 people are involved in outdoor accidents. It usually only becomes critical when friends and helpers do not become aware early enough. Or do not know your exact position. Or no emergency call is possible at all because only 10% of the world is covered by mobile phone networks. We deliver the missing 90% by satellite. And draw attention to you at an early stage. With your exact position.
SOS : What happens if…?¶
Different notification chains with a 2-step escalation can be created for each scenario (e.g. manual SOS or automatic crash/standstill alarm). Example: SmartSafety first reports your position by SMS/email to friends and the team for the purpose of rescuing comrades. At their request or after a timeout without a response, professional rescue organisations such as the mountain rescue service or coastguard (via 112/FocusPoint) are then activated, which may communicate further with you or your stored emergency contacts.
How do I configure my SmartSafety?¶
Go to protegear.io to SmartSafety. A default setting is already available!
- Profiles: set the monitoring scenarios for your activity
- Tours: set the geofences (SAFE, DANGER and REST zones)
- Notifications: store your alarm recipients (SMS, email, Telegram, …)
- Trace: compile who is alerted, when and for which event
- Contacts: enter the emergency contacts that can be contacted by a rescue coordination centre such as FocusPoint in the event of an SOS or escalation!
Overview of alarm detections¶
Note on initial setup: All automatic alarms should be tested before actual use to familiarise yourself with them. For this reason, ESCALATION to the rescue coordination centre is initially deactivated in the default setting, so that alarms only go to your own emergency contacts.
All alarm types can also be combined with each other, so that with POSITION6D + MOTIONLESS, for example, motionlessness only triggers an alarm if the device (and its wearer) are horizontal. Furthermore, this can also be combined with ZONES (geofences) so that different parameters automatically apply depending on the location.
| Alarm Type | Features | Important to note | available for device types |
|---|---|---|---|
| MOTIONLESS | motionlessness (complete resting position) for x minutes | to be worn on the body; is independent of the GPS; may be cancelled by the device going to sleep after 15 minutes (NOT-MOVING) if NOT-MOVING is activated as a pause | only A*LIVE |
| HALT | movement less than x metres in y minutes | good GPS required | all |
| CRASH | impact and/or free fall with and subsequent standstill within y metres for at least z minutes | good GPS required if subsequent movement is to be detected | only A*LIVE and P99; P88 |
| ZONE | Within DANGER zone (red zone in TOURS/ZONES) | differentiates between REST (no alarm triggering except SOS); SAFE (no ZONE alarm); DANGER (position in DANGER zone triggers ZONE alarm) | all |
| Floating geofence: You can also define a dynamic security zone around a “master” device to keep team devices within range | |||
| PROXIMITY | proximity alarm when 2 or more devices are less than x metres apart, optionally in 3D with altitude information | good GPS required | all |
| DEADMAN | |||
| Active dead man’s switch: | absence of a defined manual action on the device (e.g. preset message) for x sec | ||
| passive dead man’s switch: | A) “Outdoor only”: Poor GPS reception triggers an alarm after x seconds | all | |
| B) “Indoor + Outdoor”: Signal interruption for x seconds triggers an alarm | all | ||
| This is the final alarm detection; if your device is “offline” for whatever reason (destroyed; battery empty; no connection; etc.) | |||
| Timeout must be set so large that any latencies caused by poor network coverage do not trigger a false alarm | |||
| POSITION6D | position of the device in X/Y/Z axis | to be worn on the body; independent of GPS | only A*LIVE |
| HEIGHT | x metres above ground level (AGL) exceeded / below / within | all | |
| ALTITUDE | x metres above sea level (AMSL) exceeded / below / within | all | |
| SPEED / VSPEED | Horizontal or vertical speed exceeded or undershot | VSPEED only A*LIVE | |
| PAUSE | not an alarm; but a pause in monitoring | PAUSE mode can be triggered by… | |
| Switch off (POWER-OFF) | |||
| Tracking STOP | |||
| PAUSE (2x TRACK button on ALIVE or PRESET message PAUSE on InReach) | |||
| Start-Charge (if activated in the profile) | |||
| Not-Moving (if activated in the profile) - device remains motionless for at least 10 or 15 min | |||
| PAUSE mode is ended by | |||
| Switch on | |||
| Tracking START | |||
| Movement outside the PAUSE radius |
IMPORTANT for certain device types:¶
GARMIN INREACH / MONTANA / GPSMAP: It is essential to trigger TRACKING Start at the beginning of the monitoring and Tracking STOP at the end of the monitoring and to give the device at least 10 minutes in the open air to send this signal, otherwise false alarms (especially DEADMAN) may occur.
A*LIVE: Regular switch-off ends the monitoring, make sure that the switch-off does not take place on an activated charging pad, as this triggers a RESET.