Every alert rule starts from a template. The template decides what the rule watches, which fields you fill in, its default severity and firing policy, and how often it checks. This page lists all 97 templates in their ten families.
¶ How to read this page
In the rule form, the Template list groups templates by family, sorted by name. Type part of a name to filter it. The families are Apps, Connectivity, Counters, Fleet, Geo, Patterns, Routes, Seals (JT-701), System and Telemetry.
The tables below use these columns:
| Column | Meaning |
|---|---|
| Template | The name in the Template list. |
| Fires when | What the template watches. |
| Fields and defaults | What you fill in under Condition, with the default value. "None" means it fires on the event itself. |
| Checks | How often it checks, as the rule form shows it. See the list below the table. |
| Severity | The default severity. You can change it. |
The values in the Checks column:
- per message: on every message the device sends.
- from intervals: after the app works out a trip, stop or visit, up to 2 minutes later.
- every 30 s from aggregates: from daily or weekly totals.
- every 30 s across the fleet: across all the units the rule watches.
- timer: when a set time passes without the expected data.
- per message, as a sequence: on every message, against earlier events.
- every minute, from records: every minute, from stored records such as maintenance reminders.
- every 15 min from the SIM registry: every 15 minutes, from the SIM cards and recharges in SIM management.
Only templates that check per message, or per message as a sequence, can use Test on history.
A few templates show greyed, with the reason after a dash; you cannot choose them.
¶ Telemetry
Templates that read what the device reports: ignition, speed, driving events, fuel, power and sensors.
¶ Ignition and engine
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Ignition on | The ignition switches on. | None | per message | info |
| Ignition off | The ignition switches off. | None | per message | info |
| Ignition without driver | The ignition is on with no driver on the unit, for 1 minute. | None | per message | warning |
| Idling longer than | The engine idles longer than the set time. | Duration: 15 min | from intervals | warning |
| Engine running without movement | The engine runs without the unit moving for longer than the set time. | Duration: 10 min | from intervals | warning |
| RPM out of range | Engine RPM leaves the range for 30 seconds. | Minimum: 0 rpm; Maximum: 4000 rpm; Sensor parameter: rpm | per message | warning |
| A/C on with engine off | Air conditioning runs with the engine off. | Duration: 5 min | — | warning |
The list greys out A/C on with engine off; you cannot choose it.
¶ Speed and driving behaviour
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Speeding | The speed stays above the limit for 10 seconds. Clears after 30 seconds at or under it. | Speed limit: 90 km/h (1 to 400) | per message | warning |
| Over-speed flag | The device's own over-speed flag switches on. | None | per message | warning |
| Harsh braking | The device reports a harsh braking event. | None | per message | warning |
| Harsh acceleration | The device reports a harsh acceleration event. | None | per message | warning |
| Harsh turn | The device reports a harsh cornering event. | None | per message | warning |
| Repeated harsh driving | Several harsh driving events happen within ten minutes. Repeats every 10 minutes while true. | Number of events: 3 (2 to 50) | per message | warning |
| Seat belt unfastened | The driver unfastens the seat belt. | None | per message | warning |
| SOS | Someone presses the SOS button. Repeats every minute while held. | None | per message | critical |
For speed inside geofences, see Speeding in geofence in the Geofences family.
¶ Fuel
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Low fuel | The fuel level drops to or below the set level. | Fuel level: 10 l | per message | warning |
| Fuel theft | The fuel detector confirms a theft with at least the minimum confidence. | Minimum confidence: 60 %; Alert as soon as suspected (before confirmation): off | per message | critical |
| Fuel refill | The fuel detector confirms a refill with at least the minimum confidence. | Minimum confidence: 60 %; Alert as soon as suspected (before confirmation): off | per message | info |
With Alert as soon as suspected (before confirmation) on, the incident opens at the first sign. The confirmation then notifies again on the same incident. If the detector retracts the detection, the incident is withdrawn. The incident shows the confidence and its reasons; see Incident details.
¶ Power and battery
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Power disconnected | The device loses external power. | None | per message | critical |
| External voltage out of range | The external power voltage leaves the band for 30 seconds. | Minimum voltage: 11.5 V; Maximum voltage: 14.8 V | per message | warning |
| Low battery | The device's battery level drops to or below the limit. | Battery level: 10 % (10, 5 or 2) | per message | warning |
¶ Sensors and inputs
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Temperature out of range | A temperature sensor leaves the range for 1 minute. | Minimum: 2 °C; Maximum: 8 °C; Sensor parameter: temperature; Sensor: empty | per message | warning |
| Parameter threshold | A sensor parameter goes above, below or equal to a value. | Comparison: Gt (also Lt, Eq); Sensor parameter; Value; Sensor: empty | per message | warning |
| Parameter range | A sensor parameter moves outside, or inside, a range. | Fire when: Outside (or Inside); Minimum; Maximum; Sensor parameter; Sensor: empty | per message | warning |
| Parameter change | A parameter changes by at least the set amount between two messages. | Minimum change: 1; Sensor parameter; Sensor: empty | per message | info |
| Digital input on | The digital input switches on. | Digital input: digital_v; Sensor: empty | per message | info |
| Digital input off | The digital input switches off. | Digital input: digital_v; Sensor: empty | per message | info |
| Digital input on longer than | A digital input stays on longer than the set time. | Digital input; Sensor: empty; Duration: 30 min | from intervals | warning |
| Threshold violation duration | A configured threshold, such as over-temperature, stays violated longer than the set time. | Threshold; Duration: 5 min | from intervals | warning |
Sensor parameter is the raw value from the device, such as io239. Sensor picks a named sensor instead; left empty, the rule uses the unit's first sensor of that kind. Threshold violation duration offers only thresholds set up for your installation.
See Alert rule form.
¶ Trips, parking and towing
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Trip longer than | A trip lasts longer than the set time. | Duration: 240 min | from intervals | warning |
| Trip distance over | A trip is longer than the set distance. | Distance: 500 km | from intervals | warning |
| Parked longer than | The unit stays parked longer than the set time. | Duration: 120 min (up to 20160) | from intervals | warning |
| Stopped longer than | The unit stays stopped longer than the set time. | Duration: 2 min | from intervals | warning |
| Towing | The unit moves while the ignition is off, for 1 minute. | Minimum speed: 5 km/h | per message | critical |
¶ Geofences
Templates that watch geofences, places and other units. They need the geofences to exist first. See Geofences and routes.
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Geofence entry | The unit enters one of the selected geofences. | Geofences | per message | info |
| Geofence exit | The unit leaves one of the selected geofences. | Geofences | per message | info |
| Inside geofence for | The unit stays inside a selected geofence longer than the set time. | Geofences; Duration: 30 min | per message | warning |
| Outside geofence for | The unit stays outside the selected geofences longer than the set time. | Geofences; Duration: 30 min | per message | warning |
| Geofence visit longer than | A visit to a selected geofence lasts longer than the set time. | Geofences; Duration: 60 min | from intervals | warning |
| Expected arrival missed | The unit is not inside the geofence by the set time. | Geofences; Arrive by: 09:00 | timer | warning |
| Speeding in geofence | The speed exceeds the zone's own limit, or the rule's, inside the selected geofences, for 10 seconds. | Geofences; Speed limit: 90 km/h | per message | warning |
| Units close together | The unit comes within the set distance of another unit for 30 seconds. | Radius: 200 m (10 to 50000); Other unit | per message | info |
| Left allowed cities | The unit's address resolves to a city outside the list. | Cities | per message | info |
Geofence entry and Geofence exit open one incident per geofence.
¶ Routes
Templates that follow route schedules and rides. Leave Route schedules empty to watch every schedule. All check per message and use Unit scope.
| Template | Fires when | Fields and defaults | Severity |
|---|---|---|---|
| Checkpoint reached | The unit arrives at a route checkpoint. | Route schedules: all | info |
| Checkpoint left | The unit leaves a route checkpoint. | Route schedules: all | info |
| Checkpoint missed | The unit misses a route checkpoint. | Route schedules: all | warning |
| Ride activated | A scheduled ride becomes active. | Route schedules: all | info |
| Ride started | A scheduled ride starts. | Route schedules: all | info |
| Ride finished | A scheduled ride finishes. | Route schedules: all | info |
| Route deviation | The unit strays from its route by more than the set distance. | Route schedules; Distance from route: 300 m | warning |
The list greys out Route deviation; you cannot choose it. Route templates cannot send device commands.
¶ Connectivity
Templates that watch whether devices report, and how well.
¶ Offline and silent devices
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Offline for | No message arrives from the device for the selected period. Clears on the next message. | Duration: 30 min (8, 30, 60, 240, 480 or 1440) | timer | warning |
| Message flood | The device sends more messages per minute than the limit. | Messages per minute: 60 (5 to 600) | per message | info |
¶ GPS quality
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| GPS signal lost | The device reports no satellites or no position for a minute. | None | per message | warning |
| Low satellite count | Fewer satellites than the minimum, for a minute. | Minimum satellites: 4 (1 to 20) | per message | info |
| No GPS for | No valid position for the set time. | Duration: 30 min | timer | warning |
| GPS jump | The position jumps faster than a vehicle can move. | Maximum jump speed: 70 m/s | per message | info |
¶ Units that have not moved or started
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Not moved for days | The unit has not moved for the set number of days. | Days: 7 | timer | warning |
| No ignition for days | The ignition has not switched on for the set number of days. | Days: 7 | timer | warning |
¶ SIM cards
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| SIM card changed | The device reports a different SIM card (ICCID) than it last reported in the same slot. One incident per new ICCID. | ICCID parameters: active_sim_ccid_ext, iccid, gsminfo_simicc, param8; SIM slot parameters: currently_used_sim_card_slot_ext | per message | warning |
| Unregistered SIM card | The device reports a SIM card (ICCID) that is not registered to it in SIM management. Clears when it reports a registered one. | ICCID parameters: as above | per message | warning |
| SIM plan expiring | A SIM fitted to the unit reaches its recharge expiry date. Reminds before the date and once it has passed. | Remind days before expiry: 7, 3 (up to 5 values, 0 to 365); Stop reminding after days expired: 30 (0 to 365) | every 15 min from the SIM registry | warning |
ICCID parameters and SIM slot parameters name the device parameters that carry the SIM's ICCID and slot; the defaults cover the common device types. The first time a device reports an ICCID is not a change. Unregistered SIM card never fires for a device with no ICCID registered in SIM management. SIM plan expiring reads each SIM's latest recharge expiry date and notifies once per reminder stage. A SIM that is not fitted to a unit cannot raise it. These templates use Unit scope for expiry and Device scope for the others.
¶ Counters and usage
Templates that watch totals and counters. The list names this family Counters.
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Daily mileage over | The day's mileage exceeds the limit. | Distance: 500 km | every 30 s from aggregates | warning |
| Daily idling over | The day's idling time exceeds the limit. | Duration: 60 min | every 30 s from aggregates | warning |
| Daily fuel use over | The fuel used in the day exceeds the limit. | Fuel used: 100 l | every 30 s from aggregates | warning |
| Weekly utilisation below | The week's utilisation falls below the set percentage. | Percentage: 20 % | every 30 s from aggregates | warning |
| Fuel consumption anomaly | Fuel consumption differs from the 30-day average by more than the set percentage. | Percentage: 25 % | every 30 s from aggregates | warning |
| Mileage counter reached | The odometer reaches the set value, or passes every multiple of the interval. | Value: 10000 km; Repeat every: empty | per message | warning |
| Engine hours reached | Engine hours reach the set value, or pass every multiple of the interval. | Value: 250 h; Repeat every: empty | per message | warning |
| Service reminder | A maintenance reminder for the unit becomes due. | Notify from: First reminder (also Second reminder, When due, When overdue) | every minute, from records | info |
Service reminder turns your maintenance reminders into alerts. Each minute it checks the reminders of the units it watches. When a reminder reaches the stage in Notify from, or a later one, the rule opens an incident. It opens one per reminder, per stage, per service cycle. It cannot send device commands. Maintenance can open this template for you, with the unit filled in.
¶ Fleet
Templates that look at many units together. They check every 30 seconds across the fleet, use Unit scope, and cannot send commands or change groups.
| Template | Fires when | Fields and defaults | Severity |
|---|---|---|---|
| Fleet offline ratio | The share of offline units in a group reaches the set percentage. | Offline share: 20 %; Duration: 30 min | warning |
| Group incident burst | A group produces many incidents within the set time. | Incidents: 10; Within: 15 min | warning |
| Units in zone | The number of units inside a zone reaches the set count. | Geofences; Minimum units: 5 | warning |
¶ Patterns
Templates that look for a pattern of events over time, checked per message as a sequence.
| Template | Fires when | Fields and defaults | Severity |
|---|---|---|---|
| Dwell after event | The unit is still inside one of the zones the set time after an event. Clears when it leaves or the ignition comes back on. | After event: Ignition off (or Ignition on, Geofence entry, Trip ended); Geofences; Within: 30 min | warning |
| Event sequence | One event happens, then another within the set time. | First event; Then; Without: optional; Within: 30 min | warning |
| Repeated incident | Another rule fires several times within the set time. | Rule; Number of events: 3; Within: 60 min | warning |
In this version, the First event, Then and Without lists of Event sequence offer no events, so you cannot complete a rule from this template.
¶ System and custom rules
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| Command failed | A command sent to the device fails. | None | per message | warning |
| Command succeeded | The device accepts a command, or the command goes to a device that does not confirm commands. | None | per message | info |
| Command reply | The device replies to a command. | Commands (codes; empty = all): empty; Reply contains: empty (up to 200 characters); Reply matches (regular expression): empty (up to 200 characters) | per message | info |
| Driver assigned | Someone assigns a driver to the unit. | None | per message | info |
| Driver unassigned | Someone removes the unit's driver. | None | per message | info |
| Custom rule | A condition you write as a free expression comes true. | Condition expression; Clear condition: optional | per message | warning |
Custom rule shows "Custom expressions are not enabled for this account" and you cannot choose it unless your account has custom expressions turned on. The driver and command templates cannot send device commands.
¶ Apps
| Template | Fires when | Fields and defaults | Checks | Severity |
|---|---|---|---|---|
| App event | An installed app reports an event on a unit, optionally only when one of its fields passes a value. | App event; Event field: Any occurrence (no field condition); Comparison: at least (also at most, equal to); Value: 0; Field text: empty | per message | warning |
App event notifies on every event the app reports; it uses Unit scope. The App event list offers the events of the apps installed in your account. If you uninstall the app, Polygon switches its rules off and the rules list says "Switched off: its app was uninstalled".
See Alert rule form.
¶ Electronic seals
The list names this family Seals (JT-701). Its templates are for JoinTech JT-701 and JT-701D electronic seals. None has fields. All check per message, use Device scope and fire even for alarms the seal sends late, after a gap in coverage. The seal must be set to send each alarm over GPRS (its P40 setting); an alarm sent only by SMS never reaches the app.
| Template | Fires when | Severity |
|---|---|---|
| Seal opened by command | The seal opens with a remote static or dynamic password, from the platform or by SMS. | warning |
| Seal opened by card | The seal opens with an authorised RFID or vehicle-ID card. The incident shows the card number. | warning |
| Seal: unauthorised card | Someone presents a card the seal does not accept. The incident shows the card number. | critical |
| Seal opened over Bluetooth | The seal opens from the Bluetooth app. | warning |
| Seal locked | The seal locks itself after the rope goes in. | info |
| Seal: rope cut | The steel rope of a locked seal is cut. | critical |
| Seal: back cover opened | The back cover of the seal is opened. | critical |
| Seal left unlocked | A JT-701D stays unlocked longer than its P38 limit, or a JT-701 is unlocked without authorisation. | warning |
| Seal: wrong passwords | Five wrong unlock passwords in a row. | critical |
| Seal: unregistered card alarm | The seal's alarm status reports an unregistered card, without the card number. | critical |
| Seal: low battery | The battery stays below its P61 threshold for 10 minutes. | warning |
| Seal: lock motor fault | The lock motor is stuck. | critical |
| Seal: vibration | The seal reports vibration above its P36 threshold. | warning |
| Seal: entered device geofence | The seal enters a geofence set up on the seal itself. | info |
| Seal: left device geofence | The seal leaves a geofence set up on the seal itself. | info |