Eco-Driving turns the violations your Wialon account already records into a 0–100 score per vehicle and per driver — and keeps every individual event visible behind it, on a table and on a map. It does not invent its own rules: the criteria, thresholds and penalty weights are the ones configured on your units, so a score can always be traced back to what actually happened.
The same view by driver rather than by vehicle, because the two rankings rarely agree.
Violations clustered as pie charts by criterion, with the heatmap tracing full event paths.
The events behind a score, filterable down to one driver, one criterion or a minimum severity.
Every claim below is published by the platform vendors themselves. Follow the links.
Driver scoring fails at the conversation, not at the calculation. If a driver disputes a number and the answer is a black box, the ranking stops being used. Every score here decomposes into weighted violations, and every violation into a start point, an end point, a duration and a maximum speed.
docs.fleettab.app — eco-drivingRanking on raw violation counts penalises whoever drives most. Normalising by distance fixes that for long-haul and breaks it for city work and machines, where distance understates exposure. The metric is a setting — per kilometre or per unit of driving time — rather than an assumption baked into the model.
docs.fleettab.app — how the score worksHarsh acceleration, harsh braking, sharp turns, speeding, sensor violations, harsh driving and excessive idling are read from the unit's own Wialon configuration, under your names and in your language. Rename a criterion in Wialon and the column here renames itself. A unit with no criteria configured produces no score rather than a misleading one.
wialon.com — driver behaviour monitoringFleet and safety managers who need a driver ranking that survives being questioned — where a low score can be opened up into the specific events, on the specific roads, that produced it.
Wialon partners and integrators who want driver scoring to offer without building the scoring model, the map layer and the export pipeline themselves.
Weighted violations divided by exposure, expressed out of 100. Colour-banded into Excellent, Good, Average and Poor on thresholds you set.
The same report grouped either way, so a unit ranking and a driver ranking stay consistent with each other instead of coming from two models.
Clusters drawn as pie charts split by criterion, a heatmap that traces the full start-to-end path of each event, and per-event focus with A and B markers.
Metric, penalty multiplier and score bands are settings. If every vehicle lands in one band, the model is adjusted rather than abandoned.
The violations table is virtualised, so fleet-wide events over a full month scroll without slowing down.
Excel, CSV and PDF, respecting the active filters, unit selection and date range — including start and end coordinates in the Excel output.
One row per vehicle: trips, distance, duration, a column per criterion, and the score as a badge. Each criterion cell shows count, raw amount and the weighted value applied.
The same report grouped by driver, using the driver bound to the unit at the time of the event rather than at the time of the report.
Every event with start, end, unit, driver, criterion, duration, maximum speed, distance and weight — filterable by driver, type and minimum value.
Authenticate on Wialon's own login page, or paste an API token. There is no separate account to create and no credentials stored here.
Choose individual units or groups and a date range. With nothing selected, every unit is included.
Average score with a first-half against second-half trend, a donut of which criteria cost the most points, and a daily bar of points lost per criterion.
Switch to Violations to see the individual events as a table or on the map, filtered down to the driver, criterion or severity in question.
Eco-Driving ships white-label, and it also exists as a section inside FleetTAB — partners take whichever shape fits what they already sell.
From your Wialon units. Eco-Driving reads the criteria already configured there — including thresholds and penalty weights — rather than defining its own. That is deliberate: it means the report reflects the policy your organisation already agreed, and renaming a criterion in Wialon renames the column in the report.
Each violation is multiplied by the penalty weight of its criterion, the weighted violations are summed, and the total is divided by how much the unit drove — so covering more ground is not itself a penalty. The result is expressed out of 100, where 100 means no weighted violations. You choose whether exposure is measured by distance or by driving time.
Usually it means the Wialon penalty weights are large relative to your fleet, which compresses the range. Lower the penalty multiplier in the settings — ×0.1 or ×0.01 — and the scores spread out. The ranking between vehicles does not change; only the scale does.
A unit with no criteria configured produces no violations and no score, and is skipped rather than shown as a perfect 100. Units with no distance or driving time in the period are sorted to the bottom rather than scored.
Some Wialon accounts do not include positions in eco-driving data. The map shows a count of how many events could not be placed, and says so explicitly rather than rendering an empty map. The table and the scores are unaffected.
Yes. It runs standalone under your brand and domain, or as a section inside FleetTAB if that is what you already resell. Either way the commercial relationship is yours.
Eco-Driving is available both as a standalone application and as a section within FleetTAB. If you need driver behaviour alone, take it on its own; if you also want trips, maintenance and dashboards in the same place, FleetTAB carries it.
How FleetSQL began: a passion for telematics reports, years of customer feedback, and the path from one Python script to a full backend service.
Read moreAudit Wialon unit properties, sensors, hardware parameters, and eco-driving settings in Google Sheets with the open-source Wialon Auditor Apps Script.
Read moreA fleet organization moved from static report exports to SQL analytics with governed metrics and daily data quality checks.
Read moreHow a last-mile operator deployed a unified KPI dashboard to cut dispatch response time by 34% and improve route adherence by 18%.
Read moreHow a regional distributor stabilized Wialon to ERP sync and eliminated manual reconciliation for delivery operations.
Read moreHelping businesses to make their fleets safer, teams more productive and processes more efficient.