Add new event to the organization – Help Centre

You can create custom events for your organization:

Click Manage.
Under Config Admin, click Libraries.
Click on the Event Library tab.
Click on the Add event icon,
Enter the Event description, e.g. panic alert triggered.
Enter the Event ID or leave the field blank for the system to allocate the next available ID automatically.
Complete the rest of the fields.

Please read Setting up events - important guidelines if you are new to creating events in MiX Fleet Manager.

Conditions

A condition is the combination of a parameter, an operator and a trigger value. A combination of one or more conditions is used to define when an event is recognized by the unit. For example, the default Over Speeding event occurs when the Road Speed parameter is greater than 120 km/h or 75 mph.
You could enhance the Over Speeding event to take a Siren On parameter into account. This would be useful in emergency vehicles. In this case, you would define the Over Speeding event to occur when road speed is greater than 120 km/h or 75 mph AND Siren On is False. In other words, over speeding would not be recorded in an emergency situation, if the siren were on.
Operators are used in the definition of an event, to relate a parameter to a trigger or threshold value. Valid operators are Greater Than (>), Less Than (<), Greater Than Or Equal To (>=), Less Than Or Equal To (<=), and Equal To (=).
A trigger value is a threshold value, or a Boolean state (true/false) that determines when a condition is true.
Select the value of the parameter which should be recorded - Minimum, Maximum, Average.
Click on the condition after which you would like to add a new condition and click the '+'. You can duplicate conditions, remove conditions and move them up or down. Clicking the star makes a condition required and clicking it again (when it is gray) makes it an optional condition. See below for an example of conditions for a cold chain, cooling unit off while driving event:

Check the box if you want the event to be recorded.
The recording delay is the time that the event must be true before the unit will record the occurrence of the event. If this is disabled then the event will not be recorded by the unit, but can still be used to sound the buzzer or enable the relay.
Choose between one of the following recording types:
- Detailed - Each start and end of the event will be recorded. This means that duration can be shown for each individual occurrence of the event.
- Summarized - The number of occurrences and the total duration (the total amount of time that the event was true) will be recorded with each sub-trip.
- Notification - Each start of the event will be recorded. The end of the event is not recorded; hence the unit will record no duration.
Record Actions - choose the following by checking the relevant boxes: record the start and/or end odometer, the start and/or end position, video, the pulse count (for fuel, etc).

Defines what action must be taken when the event occurs and contains the following properties:

Check the box if you want the buzzer to sound when a condition has been true for a delay of a certain time. This means an alarm will warn the driver of an event that has triggered. You can also indicate how long the buzzer must sound, e.g. for 1 second or continuously while the condition is true, etc.
Enable relay drive - indicates whether the relay must be switched on and if so after how long. This will not be available if a GPS or other device is using the relay for power control.
Allow override - is only available if either the buzzer or relay delays are enabled. If checked, the alarm and relay will not activate during a trip if a system override plug was inserted between identifying the driver and starting the trip.
Display warning message - this allows a critical warning to be enabled that will be displayed for certain events on the FM Terminal after the configured delay.

Check the box to enable the sending of active messages - this defines additional, communication actions that must be taken when the event occurs and contains the following properties:
Queue Message - indicates whether the vehicle is to send an SMS text message notifying that the event has occurred. You are able to specify the delay (time that the event must be true) before a message is sent, the priority for the message and whether the message should include GPS position information. Note that this delay is independent of the recording delay and the delay period begins immediately the event becomes true.
- Message priority - Urgent will cause a message to be sent immediately (after the delay); Normal will cause the event message to be queued to be sent in an SMS message when the message is full or before that if another event with urgent priority occurs; Critical will be sent immediately using any available transport, including satellite. Mobile device will surface if required.
Enable Active Tracking - check this box if you want the vehicle to be actively tracked (position information sent at regular intervals) when the event occurs. If this option is turned on, the time for which active tracking should be turned on can be chosen as well as the interval at which the active tracking messages are to be sent.

Notes: At least one of the delays (recording, buzzer or relay) must be enabled for the event to be saved.