Maintenance tracks each vehicle's mileage, engine hours and elapsed days against your service intervals, and tells you what is coming due before it is overdue. It does not hold a second copy of anything: intervals are stored as Wialon service intervals on the unit itself, so what you create here appears in Wialon and what you created in Wialon appears here. On top of that it keeps the part of a service that never fits in a telematics platform — parts, labour, cost and the invoice.
The intervals list with its four summary cards — what is due, and how much is left on each axis.
Screenshot pending
Creating an interval across several units, with a warning window per axis.
Screenshot pending
A service record with parts, labour and the invoice attached to it.
Why this exists
Every claim below is published by the platform vendors themselves. Follow the links.
Wialon tells you it is overdue, not that it is due
A Wialon service interval has a frequency but no warning window, so the state you get is before or after the threshold. Intervals created in Wialon therefore arrive here with a default warning window — 500 km, 20 engine hours, 14 days — until you set your own. A window is the difference between scheduling a workshop slot and discovering the van should have been in it last week.
Wialon already does maintenance, and this does not replace it
The former Fleetrun application is now integrated into Wialon and included with the platform — scheduling by time, mileage or engine hours, service logging, and maintenance reports. This is not a competing store for that data. It reads and writes the same Wialon service intervals, which is why nothing has to be migrated and nothing diverges.
Fleet and workshop managers who are already tracking service in Wialon and want to see what is approaching rather than what has already slipped.
Wialon partners who need a maintenance surface to put in front of their own customers, under their own brand, without standing up a separate maintenance database.
What you get
Three axes, one status
Intervals run by mileage, engine hours, days, or any combination. When more than one axis is tracked, the worst one decides the status — fine on kilometres and past the calendar rule still reads Overdue.
A warning window you set
Warn before due in kilometres, hours and days independently. Anything inside the window is flagged Due, which is the state worth acting on.
Stored in Wialon, not beside it
Intervals are Wialon service intervals on the unit. Create one here and it exists in Wialon; create one in Wialon and it appears here. There is no second database to keep in step.
Batch across the fleet
Apply an interval to many units in one action. Units already at Wialon's per-unit interval limit are reported as skipped rather than failing the batch silently.
Service log with the money in it
Parts with quantity and cost, labour with hours and rate, a running total, location and comments. Linking a service to an interval moves that interval's baseline and advances the next due date.
Attachments that export
Invoices and photos attach to the service record, up to 10 MB each. A single-service PDF embeds image attachments and copies the pages of PDF ones into the same document.
The data itself
Intervals
Unit, interval, frequency, last-service baseline, and what is left on each axis with its sign — +9,684 km / −12 d reads as nine thousand kilometres to run but twelve days past the calendar rule.
Statuses
OK, Due and Overdue, recalculated against the unit's live odometer and engine hours on every page load rather than cached.
Services
Date, unit, service name, odometer and engine-hour readings, total cost and attached files — filterable by vehicle, service name and date range.
How it connects
1
Step 1: Connect a Wialon account
Authenticate against Wialon. Existing service intervals on your units appear immediately — there is nothing to import.
2
Step 2: Set the warning windows
Intervals that came from Wialon start on a default window of 500 km, 20 engine hours and 14 days. Edit them once to match how far ahead your workshop actually needs to know.
3
Step 3: Add what is missing
Create intervals across a group of units in one action, with frequencies on any combination of mileage, engine hours and days.
4
Step 4: Register work as it happens
Log the service against the interval with readings, parts, labour and the invoice. The baseline moves and the next due date advances on its own.
What you point at it
Platform
Wialon Hosting
Wialon Local
Self-hosted Wialon instances
Export
Excel
CSV
PDF
Per-service PDF with attachments
Tracked by
Mileage
Engine hours
Calendar days
White-label
Maintenance ships white-label, and it also exists as a section inside FleetTAB — partners take whichever shape fits what they already sell.
Standalone under your brand and domain, or as part of FleetTAB if you resell that.
Because intervals live in the customer's own Wialon account, a partner is adding a surface rather than a dependency — the data survives the relationship.
You hold the commercial relationship and the billing; we stay behind it.
Product work and Wialon API changes are handled on our side.
Security and access
Authenticates against Wialon; no separate account and no Wialon password stored here.
Intervals are written to the customer's own Wialon account, so the maintenance schedule is theirs and stays after any change of supplier.
Service attachments are capped at 10 MB per file.
Deleting a service removes its attachments and the underlying Wialon maintenance event — stated plainly because it cannot be undone.
How is this different from the maintenance already in Wialon?
It works on the same data rather than replacing it — Wialon's own maintenance functionality, formerly Fleetrun, is included with the platform and this reads and writes the same service intervals. What it adds is a working surface: a warning window, which the Wialon interval has no field for, so you see what is approaching rather than only what has passed; creating an interval across many units in one action; and a service record that carries parts, labour, a running cost total and file attachments together.
Do we have to migrate anything?
No. Intervals already configured in Wialon appear as soon as you connect, and anything created here is written back to Wialon. There is no import step and no second source of truth to reconcile.
What happens to intervals created in Wialon's own interface?
They appear here with a default warning window of 500 km, 20 engine hours and 14 days, because Wialon has no field to carry one. Edit the interval once and your own window replaces the default.
How is status decided when an interval tracks more than one axis?
The worst axis wins. An interval fine on mileage but past its calendar rule reads Overdue, not OK. Status is recalculated against the unit's live odometer and engine hours every time the page loads rather than served from a cached value.
Can we attach invoices?
Yes — files up to 10 MB each attach to the service record. The single-service PDF export embeds image attachments and copies the pages of PDF attachments into the same document, so one file can go to finance or to an auditor.
Can we sell it under our own brand?
Yes. It runs standalone under your brand and domain, or as a section inside FleetTAB. Because the intervals live in the customer's Wialon account, you are adding a working surface rather than a dependency.
Does it work with Wialon Local?
Yes, alongside Hosting and self-hosted instances. The service intervals it reads and writes are the same objects in every case.