Alerts and reports

Alerts

Armavio raises an alert when something needs attention.

Type	Appears when
Overspeeding	A vehicle exceeds the limit
Geofence	A vehicle enters or leaves a watched zone
Low fuel	Fuel drops below a threshold
Idle	A vehicle sits still too long
Service due	A service schedule has passed
Document expiring	Registration, roadworthiness, or insurance nears expiry

Each alert carries a severity: information, warning, or danger.

Marking as handled

Alerts that have been acted on are marked handled, which removes them from the active queue while keeping them in the history.

An alert queue that is never cleared gets ignored

If alerts pile into the hundreds, nobody will read them — including the ones that matter.

Clear them daily, and if one type appears constantly without ever needing action, raise its threshold or disable its zone.

Reports

Fuel consumption

A chart of fuel consumption over a chosen period.

Useful for spotting a vehicle whose consumption diverges from others on similar routes — usually a sign it needs service, or of wasteful driving.

Violation summary

A tally of events by type: overspeeding, geofence, low fuel, and idle and others.

Read these as trends, not as a list of offences

A single speeding event means little. A rise in speeding on one route over three weeks means that route's timing is too tight.

Reports used to punish people push drivers to switch the device off, and then you lose the data altogether.

How far back the data goes

Vehicle position history is kept for a limited period

Position traces are pruned periodically to keep storage reasonable.

That means reports built on position traces have a limited reach backwards. If you need to keep trip evidence for a particular purpose, export it before it falls outside that window.

Summaries and aggregates are retained longer than the raw position points.