LemursEye
Insight Engine · The brain between positions and actions

Rules you set. Alerts you trust.

Every position is evaluated against what you defined as normal, working hours, home zones, speed policy, and the engine speaks only when reality deviates.

Alerts · yesterday
1 critical
  • Truck 5 moved after hours, 11:40 pm, 43 min, 18 km23:41
  • Van 7 speeding, 132 km/h on the regional ring road14:05
  • Van 3 idling over 2 hours at the site09:52
  • All devices reporting, digest sent07:00

Insight Engine

The Insight Engine is the streaming logic that turns a firehose of positions into a handful of things worth your attention. It segments trips by real movement, evaluates geofences with hysteresis so borders do not flap, runs your rules per vehicle or group, and deduplicates with a cooldown so one event is one alert. It is exception-based by design: silence means all normal.

Building blocks of the engine

  1. 1

    Position event

    events.domain

    The enriched position, vehicle, tenant, status, telemetry, is the input to every block below.

  2. 2

    Trip segmentation

    trips · displacement-based

    A trip continues while the vehicle actually moves and ends when it dwells; time gaps are bridged. Idle is counted only with the engine on.

  3. 3

    Geofences

    geofence.entered · geofence.exited

    Circles and polygons you draw; a two-fix hysteresis and dwell time so a vehicle parked on a border does not generate a storm.

  4. 4

    Rules

    speeding · idle · after_hours · geofence · low_battery · sos

    Per tenant, per vehicle or group, with thresholds and active time windows. Changes are live within a minute, no redeploy.

  5. 5

    Cooldown

    valkey · dedupe

    The same condition on the same vehicle raises one alert, not one per position. SOS is never suppressed for long.

  6. 6

    Outputs

    alerts.outbound

    In-app alert centre and email today; the digest consumes the same stream; webhooks and WhatsApp follow.

The engine in action

Movement after hours

Truck 5 moved at 11:40 pm for 43 minutes, an alert in the moment and a line in tomorrow's digest.

Idling on site

Two hours engine-on and stationary is a rule, an alert, and 95 EGP the Money Engine can put a number on.

SOS from the cab

A panic button on the tracker or the driver's phone becomes a critical alert, independent of any rule configuration.

Who uses it

Operations managers

Define normal once; get exceptions.

Safety officers

Speeding and behaviour, with history.

Site supervisors

Geofences around every site and depot.

TSPs

Rules per client tenant, isolated.

Questions

Insight Engine

The brain between positions and actions