Consumption poorly explained
The fuel cost is read in the final balance, without context on the route, vehicle and use.
CAN bus, the electronic network that every vehicle uses to communicate with itself, tells how much fuel a vehicle really consumes, how it is driven and when something is about to break. Zenit reads these signals and transforms them into operational priorities, without promising unverified savings percentages.

Fuel, idle time, driving style and anomalies can affect management, but clear readings linked to the real work of the fleet are needed.
Consumption poorly explained
The fuel cost is read in the final balance, without context on the route, vehicle and use.
Idle time not visible
Engine running times and operational stops may be left out of the decision reports.
Disconnected driving style
Accelerations, braking and use do not always feed coaching or in-house policies.
Late anomalies
Technical signals and recurring behaviours are detected when they already have an impact.
Responsive maintenance
Interventions and checks do not communicate sufficiently with km, engine use and vehicle data.
Non-operational analyses
A lot of data is not enough if it does not become KPIs, priorities and shared actions.
Consumption, stops and anomalies sorted by vehicle and route, with the context necessary to understand where to intervene.

Fleet
Each vehicle with its use and its status.
The screenshots show the Zenit demonstration environment: no connection to the customer operating platform and no guaranteed savings.
CAN bus and vehicle data become useful when linked to routes, drivers, consumption, maintenance and reports.
Isolated data
Technical readings
The vehicle data remains available, but difficult to use for daily decisions.
Final costs
Fuel and maintenance are analyzed when the expense has already occurred.
Non-contextual anomalies
A technical signal without route, use and means risks being ignored.
Data in the Zenit system
Readable signals
Consumption, km, idle time and anomalies are sorted by priority.
Operational analysis
The data is read together with the route, driving style and use of the vehicle.
Informed maintenance
Interventions and checks can be planned with more context.
Data availability depends on vehicles, devices and configuration. The demo clarifies which signals are applicable to your fleet.
Vehicle data
CAN bus readings and technical signals available based on vehicle and configuration.
Fuel and consumption
Analysis of consumption, trends, anomalies and context of trafficking.
Driving style
Useful signals for coaching, policy and more conscious use of the vehicle.
Engine use
Reading of engine running, operating load and conditions of use.
kilometres
Mileage and usage linked to maintenance, costs and reports.
Idle time
Stops with engine running and unproductive times to be read in the operational context.
Maintenance
Signals and deadlines to support scheduled checks and interventions.
Anomalies
Events and trends to check before they become recurring problems.
Operational analysis
KPIs and reports to link vehicle data to fleet decisions.
The difference between knowing where a vehicle is and knowing how it is working comes from here. It's worth understanding this before evaluating any solution, including this one.
CAN stands for Controller Area Network. It is the bus that connects the vehicle's electronic control units to each other and on which they continuously exchange messages: engine rpm, fuel level and consumption, kilometres, operating status, anomalies. It is the network on which the vehicle describes itself, and it remains the same whether the vehicle is stationary or moving.
A tracker that reads only the satellite signal knows where the vehicle is and how fast it is moving. It cannot tell whether the engine is running while stationary, how much fuel is being used on that route or whether a control unit has already reported a fault. That information is available only through the vehicle network.
When a control unit detects an anomaly, it generates a diagnostic code. Once interpreted, that code becomes actionable information before the dashboard warning is noticed at the end of the day—and before the anomaly causes a breakdown. This is the basis of maintenance planned around actual use rather than the calendar.
Not all vehicles expose the same signals or expose them in the same way: availability varies by make, year, equipment and installation configuration. That is why this page describes vehicle data as “available according to vehicle and configuration” rather than presenting a fixed list. Promising a signal that a vehicle does not provide would produce an empty report.
Zenit avoids unverified percentages: first it makes the operational causes legible, then the company decides which actions to take.
Explainable consumption
Connect fuel, route, vehicle, driver and operating conditions.
Use of the lightest vehicle
kilometres, idle time and engine usage become readable indicators.
Informed maintenance
Signals and anomalies can support controls and planning.
Report by management
Technical data become useful summaries of costs and priorities.
Measure
Vehicle data, consumption, km and idle time.
Compare
Routes, vehicles, behaviours and anomalies.
Intervene
With policies, maintenance and operational actions.
Which signals a vehicle displays on the on-board network changes with the brand, year and setup: it occurs on the real fleet before installation, because a report built on a signal that that vehicle does not display is born empty. No savings percentage appears on this page — a savings without data, period, context and calculation method is not a given, it is a promise.
Consumption is read on the working unit of the vehicle, and it is not always per kilometre.
Transport and logistics
On long routes, consumption depends on load, route and driving style together: separating them requires vehicle data.
Construction and construction sites
On a construction vehicle the fuel is used up with the engine running and the car stopped. Sometimes it's work, sometimes it's idle: only the engine hours say so.
waste collection
Short distances, many restarts, a lot of time with the engine running: here the consumption is read by the lap, not by the kilometre.
Fleet rental
Consumption is produced by those who have the vehicle in use, and when returning it you need to know how much and in what conditions.
The same deviation, four different consequences.
Fleet Manager
«This vehicle consumes more than its twin: is it the vehicle or is it the person driving it?»
Maintenance Manager
«Do the real engine hours tell me when to intervene before something breaks?»
CFO
«Can the fuel item I see on the balance sheet be explained by the work that was done?»
Entrepreneur / CEO
“How much of the fuel I pay becomes work?”
Responses oriented to available data, conservative results and connection with maintenance and policy.
No. Zenit helps to read fuel, consumption, idle time, use and anomalies, but does not guarantee savings percentages. Results depend on fleet, processes, policies and actions taken.
Fuel, kilometres travelled, engine use, idle time, driving style, anomalies and signals useful for maintenance. However, which of this data is actually available depends on three factors: the vehicles in the fleet, the device installed on board and the chosen configuration. The demo checks which ones are readable on your fleet.
Yes, vehicle data can support checks, anomalies and intervention planning when available and interpreted within a maintenance process.
Zenit can make useful signals for coaching and company policies legible. The use of data must be consistent with responsibility, in-house communication, privacy and purposes defined by the company.
Zenit can help you understand what vehicle data is available, how to read it and how to link it to costs, maintenance and driving behaviour.
We use technical cookies, necessary to make the site work and to remember this choice. We would also like to use analytical cookies, to understand which pages are useful: you can refuse them and the site works in exactly the same way. Cookie policy · Privacy policy