Skip to content


The trace is the surrounding bracket that holds the tour, the device fleet, the profile and the the notification together. This trace then determines if and which alarms will result in a notification, who is notified and if there are also escalations. exist.

Create different traces for different monitoring or alerting scenarios. traces. Each trace can be activated or deactivated; several traces can be active at the same time. traces are active at the same time, and the different traces may contain the same or an overlapping same or an overlapping set of your devices are monitored.

To create a new trace, you have to select in the menu in Expert mode the item Trace in the Expert mode menu and then create a new trace there with the “+” symbol. Existing traces can also be changed at any time via the Dashboard.


In the overview all current traces are displayed as tiles. In this it is possible to read multiple information from one tile:


  1. the markers for monitoring and escalation are flashing red, if this trace is active is active and generates alerts and escalations. The number next to the globe shows how many devices are currently monitored in the trace. are currently monitored.
  2. in the detail area you can see which alarms are activated and who will be notified in case of an escalation. notified in case of an escalation.


Each trace must have a name and can also have an optional description. can be added. Use this when you create different traces to recognize later why you created the trace. recognize why you have created the trace.

In the upper area of the trace you can specify the data for monitoring:


Select the fleet to be monitored from the list. 2. Select from the list the tour which should be linked to the monitoring. In the list exists a fixed entry The whole world which can be used if no special zones are defined. This tour corresponds to a world where there are only Safezone’s. 3. 3. in the profile list a profile must be selected, which contains the alarm functions. alarm functions. 4. tracking type 1. in the standard case the devices are monitored by the specified tour. In the monitoring view it is possible to define an Ad-Hoc security zone, but most of the time this is not needed, because the zones are often are fixed and already coded in the tour. 2. 2. if a Floating Fence is selected, you still have to select a device and a radius for a perimeter. This device then spans a safety zone. Use Use this feature to be alerted by a ship if the dinghies are too far away. move too far away.


While the supported alarm functions are defined in the profile, the trace serves to is used to associate such alarms with notifications. To do this, create a notification matrix and select the appropriate nodes:


The alarms are activated with the switch Activate Alarms. Only when the alarm is switched on, the trace is active. Alarms are then sent to the corresponding channels. sent. If alarms are to be sent repeatedly, then this repetition can be can be specified, including a waiting time between the repetitions.

The alerting matrix consists of one row for each notification and dynamic columns that can be added with the “+” symbol. Each column represents an alarm that can be generated with the profile. If in the profile the alarm is deactivated in the profile, it will be crossed out in the matrix.

It is always possible to configure several columns for one and the same alarm. configure. The “i” icon is clickable and there details for the alarm can be can be defined:

Alarm details

  1. define if this alarm should also cause an ON/OFF feedback on the device.
  2. you can set a time limit for the notification. So it is possible to configure in the columns in the alarm matrix, which e.g. send alarms only at certain times (e.g. when the (e.g. if the recipients only work at certain times).

If details have been adjusted here, the “i” symbol will appear in blue.

In the matrix itself, by setting a check mark in the first (red) column, a notification can be notification can be forced when the alarm is generated. A check mark in the second (green) column means that also a notification will be sent when the alarm is is stopped again.

Operation on the device

Depending on the terminal device, alarms can be terminated by various actions on the device:

  • If the device has an SOS CANCEL key or action, you can use it to end all alarms. end. If you have set the MUTE function in the profile, then no automated alarms are no more automated alarms will be triggered for the defined time.
  • If the device has START/STOP keys, you can stop almost all alarms with the STOP action. alarms with the STOP action; only the manually triggered SOS alarms must still be terminated with CANCEL. Please note that this will also put you into Pause mode i.e. no new alarms will be activated until you press START again. again.
  • If the device has the possibility to start a PAUSE, almost all alarms will also be (except SOS). In contrast to STOP e.g. the Alive still sends tracking data to our system, so the our system, so that the pause mode can be terminated automatically by leaving a pause zone. pause zone (this is not mandatory for STOP). given).
  • If the device also sends POWER-ON/OFF events, you can also simply switch off the device to stop all alarms (incl. SOS).

Please note your settings in the profile for the PAUSE function. If there that the device automatically switches to the pause mode if it does not move for a certain time, this can cause an unintentional termination of the alarms. cause.


SmartSafety supports a two-stage alerting model. The first stage of alarming occurs when one of the alarm functions hits in the profile. This alarm can then be assigned to a notification via the alerting matrix.

An alarm remains open until the reason for the alarm is no longer present. Thus an SOS is valid until the device sends a CANCEL. With automatic alarms, the server must stop them. For example, in the case of a ZONE alarm, the device must device must transmit a new position for this alarm to be terminated.

If an alarm remains open, however, the second stage of the alarming can take place. called EScalation.


The configuration of the escalation distinguishes between Instant and Delayed escalations. The alarms configured in the Instant escalation field will immediately trigger an escalation processing. escalation processing as soon as this alarm occurs.

In contrast, Delayed escalations are delayed; the delay time is specified in the Idle time list. is defined in the Idle time list. Only when a Delayed alarm has been active for this time period is active for this period of time, this alarm will be escalated.

Each escalation has a Cooldown time, i.e. if an escalation is finished, no new escalation is executed during this time period. no new escalation will be started during this time period. A user can be escalated by a CANCEL event to end an escalation; such an event is therefore a signal to a rescue unit that a rescue unit that everything is OK. However, since alarms may remain open directly (e.g. a ZONE alarm will always remain open or reopened as long as the position does not position does not change). A cooldown thus makes it possible that an escalation is terminated although the alarm is still not closed.


If the alarm situation is not changed fundamentally, the escalation will be reopened after the cooldown time. escalation will be reopened.

Finally the escalation contains additional information as free text and the notification channel to be used. notification channel to be used. The list also contains an entry for Focuspoint International, but this can lead to an error message:


In such a case you have to unlock your devices for Focuspoint rescue. Please contact please contact with us.