Triggers

You can trigger actions based on rules you define. This is done in a IFTTT (If This Than That) way. You can name the rule and assign it to asset groups.

Example: If RPM > 3000, Send Fleet Management Notification.

Trigger

Name

Name your trigger.

Type / Priority

Event or episode where a episode has a begin and end. In contrast to a event that does not have a duration.

The priority determines how the notification will be labeled.

Minimum duration

Use this to disregard (too) short episodes. Below this threshold the episode will be ignored.

Asset groups

Select one or more asset groups the trigger applies to.

Enabled

When selected, the trigger will be running after creation. If not selected, the trigger will be created but won’t run until manually enabled afterwards.

Rules

To start you have to define rules. You can pick from a list of rules, each of them having different parameters to update the rule as per your requirements.

• Avg Deviation

Can be used to detect anomalies. The system will compute a running average and if the new sensor value deviates from this average by the given threshold it will trigger. Use a negative % to detect drops, use positive % to detect increase.

You can use it to detect loading/unloading events when using a weight sensor. Or to detect a sudden change in temperature.

• Event
  

You can select a device event to look for. For instance a Cornering or Harsh acelleration event. These events are triggered by the device and are often not very long so work best when in event mode. They require the device configuration to be updated to trigger the chosen event as well.

• Geofences
  

You can select the trigger to be send when the vehicle(tracker) goes outside or inside the selected geofence(s). You then can select any geofence, one or more geofence groups, or one or more specific geofences.

• IO Logical
  

You can also select the logical ‘mapped’ meaning regardless on which physical input it’s connected. You can select the logical ports for the device. For instance ‘Ignition on’ or ‘Airconditioning on’. This will look for the mapping of the specific device

• IO Port (Input / Output)
  

You can select physical IO ports that have to be enabled to trigger this rule. You can select the hardware ports for the device here. So for instance IO input 1 and condition ‘On’ or ‘Off’.

• No sensor data

If no data is received for the selected sensor, the trigger will be fired.

• Schedule

You can define a schedule in the settings menu. Then you can add this rule and determine if the trigger should fire when in or outside this schedule.

• Speed (relative to road)

Every location will be checked with our road speed database to make sure you are within the right speed limits. You can select at what deviation % relative to the road speed limit the trigger will be fire.

• Tracker sensors value

You can select different sensors (rpm, speed, temperature, etc.) and fire the trigger whenever it is above(>) or below(<) the given value.

• Tracker sensors outside specs

You can set sensor thresholds on devices. For instance you can create a frozen spec (< 0 degrees). When the sensors go outside this spec or have no value while a value is expected this sensor will be triggered.

• Tracker status

You can select a tracker state (e.g., Is idling) and condition (true or false). It will compared the state and condition with the calculated device state from our backend and fire the trigger if the rule matches. You can check for the following tracker statuses:

• Has Ignition
• Has External Power
• Is Idling
• Is Communicating
• Has gps fix

• Virtual sensor

You can select different virtual sensors and fire the trigger whenever the condition is true or false.

Actions

Now that we’ve set the conditions for the trigger to fire, we are ready to define actions. Actions can be:

• Store event in database as episode
• Notification message by email
• Webhook

Message

• Send Message

The message that will be sent when the trigger is fired can be fully customized. You can change the body and subject of the message and include {{variables}}.

Depending on the selected contact group the notification will be sent via email or sms.

• FleetManagement app notification

A notification popup will show within the FleetManagement web application

• Mobile app push notification

A push notification will show in the mobile app.

Webhooks

Tip: you can test the output of a trigger by using the ‘Test’ button. You will receive a message as if all the conditions of the rules were met.

Examples

Seatbelt off while driving

– Speed > 20kmh for more than 30 seconds
– Logical Input ‘Seatbelt violation’ is True

Using the asset outside working hours

– DeviceState = Ignition On
– Schedule ‘weekend’ active

Using the asset outside allowed areas

– DeviceState = Igntion On
– Outside geofence groups ‘X, Y, Z’

Rerun

You can view all your created triggers in the over trigger menu. To select a trigger click the details button. After clicking on the details tab, you will find the rerun button in the bottom right.

The rerun button will calculate all moments that the trigger was fired in the selected date range and create episodes of it which you can find under the episodes tab.

You can select an episode by clicking on it and see all moments when the triggers were fired during that episode. When you hover over the bullets in the chart, you will see the location of the vehicle on the map when the trigger was fired.