Speed rules per zone, time, and weather
Mine sites, plant yards, residential zones — each has its own speed rule, and the platform only knows about a violation after it happened. Sites increasingly demand active in-vehicle enforcement before they let a contractor's fleet in.
How the logic runs
Geofences (circular or polygonal) are stored on the device with per-zone speed limits.
The algorithm continuously checks position against the zones and speed against that zone's limit.
Over the limit → immediate in-cab alert (buzzer output in the standard template; audio files also possible).
Conditional rules stack: the official example runs 90 km/h in daytime, 60 km/h between 22:00–08:00 or when rain is detected via sensor.
The zone map and the rules ride with the vehicle. A contractor entering a mine site enforces the site's limits with no coverage and no integration project with the site's systems.
- Monitoring compliance with the speed limit in a set geofence
- Speed limits control depending on time and weather
- Checking location within a circular geofence
- Checking location within a polygonal geofence
Proven templates from the Easy Logic library — we commission and adapt them to your fleet.
Straight answers
How complex can the rules get?
The library's example combines time windows and a weather sensor: 90 km/h by day, 60 km/h at night or in rain. Rules are blocks you chain, not custom firmware.
Circular or polygon zones?
Both — separate templates exist for circular and polygonal geofence checks.
What warns the driver?
A buzzer on an output in the standard template; the audio-file templates can play voice alerts instead.
Want this running on your fleet?
Describe the operation — we quote the hardware and commission the algorithm with you. Stock in Johannesburg, no MOQ.