Fleet Vehicle Over-Speed Alarm

Who it’s for

Fleet operators, telematics providers, and rental-equipment managers asking “is this truck pushing past the speed limit?”, “is a courier under deadline pressure driving recklessly?”, “is a rental vehicle being pushed beyond contract, or has a van just been stolen?” — when over-speed should trigger an early warning before it stays well over the limit long enough to escalate.

What it does

Reads the device’s speed telemetry and raises a Major alarm when speed goes over the limit, escalating to Critical when it stays well over for several seconds. The alarm auto-clears once speed drops back to a normal level.

How to set up

The rule has default values for every threshold, so it works as soon as it is installed. Install on a device or asset profile so the alarm covers every entity of that type at once and automatically picks up any new entity added later. Single-device or single-asset installs are also supported.

How to customize

• To monitor a different telemetry — change the Time series key on the metric argument (e.g. speed → gpsSpeed for trackers that publish under a different name).
• To use different threshold attribute names — change the Attribute key on the threshold arguments to match what your vehicles already use (e.g. speedWarningThreshold → speedLimit).
• To change the warning, danger, and clear thresholds used when no per-entity attribute is set — change the Default value on the warningThreshold, criticalThreshold, and clearThreshold arguments.
• To change how long speed must stay above the danger threshold before Critical fires — change the Default value on the holdSeconds argument.
• To tune thresholds and hold duration at runtime without editing the rule — set the value on the entity as a regular server-side attribute. It can be edited directly from a dashboard using Update Multiple Attributes input widget:
  • Per vehicle — set the attribute (e.g. speedWarningThreshold, speedHoldSeconds) on the vehicle itself. The per-entity value overrides the Default value.
  • Per customer (in deployments that use customers) — change Entity type on the relevant argument to Current owner, then set the attribute on the customer. Every vehicle that customer owns picks up that value.
  • Tenant-wide — change Entity type to Current tenant, then set the attribute on the tenant. The value applies across every vehicle.
• To make the alarm manual-clear-only — remove the Clear condition. The alarm then stays active until an operator clears it.
• To restrict firing to specific hours or days — in the Trigger condition’s Schedule, choose Active at a specific time range (or Custom schedule for different intervals per day) — e.g. delivery hours only, or school-zone times. For per-entity schedules — vehicles with different routes or shift patterns — switch to Dynamic mode and source the schedule JSON from an attribute on the entity.
• To control where the alarm shows up — toggle the propagation flags under Advanced settings.