Geofences and rules engine

Most operations do not need someone watching the map: they need the system to speak up when something departs from plan. The Vortex rules engine combines geography, time and telemetry to decide what deserves attention.

What it includes

A rule is made of chained conditions and actions. You can require several at once, scope them to a schedule or a group of assets, and chain escalations if nobody attends the event.

Polygon, circle and route-corridor geofences
Entry, exit and dwell with configurable tolerance
Conditions on speed, ignition, temperature, fuel or inputs
Time windows and calendars by day of week
Actions: alert, email, SMS, webhook, device command
Automatic escalation when an event goes unattended
Bulk geofence import from file
Rules per asset group, customer or branch

How it works

Route corridors

Beyond zones, you can define the corridor a vehicle must follow, with a tolerated width. If it strays further than allowed, Vortex catches it even though no traditional geofence was crossed. It is the practical way to control deviations in freight transport.

Compound rules

Conditions combine with AND / OR logic. “Outside the customer zone AND with the engine running AND between 22:00 and 05:00” is a single rule, not three loose alerts someone has to correlate by hand.

Less noise, more signal

Every rule has a quiet period and a repetition threshold. That stops a device oscillating on a geofence edge from firing forty alerts in ten minutes and training the operator to ignore them.