The Fleet OS
Anyone can buy electric vehicles.Keeping them earning is the hard part.
Bluwheelz runs a single control layer across every vehicle, driver, route and charge cycle. It is the reason we can sign an SLA on an asset class most operators still treat as experimental.
Control layer
15-min cycle
Illustration: trucks running three routes out of a charging hub, and an exception on one route raised to city operations and worked the same shift.
- See
- Decide
- Act
Abstracted · no client or registration data
The problem
Four systems that disagree with each other.
Each one is right about its own slice and wrong about the fleet. Watch the four readouts below: none of them is counting the same shift.
GPS in one tool
Tracking that tells you where a vehicle is, but not whether it should be there.
Pings every 30s
Drivers in a spreadsheet
Rosters, attendance and payroll disconnected from the routes they cover.
Updated daily
Maintenance in a logbook
Servicing driven by the calendar rather than by how the vehicle is actually being used.
Written weekly
Clients on email
SLA performance reconstructed monthly, by hand, from four sources.
Reconciled monthly
The unified layer
One record per vehicle, per driver, per trip.
- Four systems. One record.
- Nothing to reconcile at month end.
- Your SLA number is our SLA number.
GPS telemetry
Position,Speed,Stop
Workforce
Shift,Attendance,Pay
Maintenance
Fault,Service,Wear
Client master
SLA,Window,Rate
Bluwheelz Fleet OS · Control tower
One live picture. One version of every number.
Illustration of the control tower: fleet-pulse gauges, the operating cities on a map of India, the fleet’s status mix, and alerts that are raised and then cleared.
Alert engine
Exceptions surface in fifteen minutes, not at month end.
- 01T+0
Threshold crossed
A vehicle sits idle past its window, a charge cycle is missed, a route runs late.
- 02T+15 min
Exception raised
The engine raises it to the city team with the vehicle, the route and the client it affects.
- 03Same shift
Worked
Spare capacity dispatched, or the client notified before they notice.
- 04Monthly
Reviewed
Every exception feeds the operations review, so recurring causes get fixed rather than re-handled.
What we measure
Six numbers that decide whether an EV fleet works.
Six instruments, read every shift. The values themselves are client data, so what you see here is the shape of each measure rather than a figure.
- 01 / 06
Utilisation
Share of available vehicle-hours actually earning. The number that decides whether a fleet is profitable.
% of vehicle-hours - 02 / 06
km per battery-%
Kilometres travelled per percentage point of battery consumed. The cleanest single measure of whether a vehicle, a driver and a route are well matched.
km / battery-% - 03 / 06
On-time rate
Against the client's window, not ours.
% inside the window - 04 / 06
Charging efficiency
Energy delivered versus energy billed, per hub and per session.
kWh in / kWh billed - 05 / 06
Vehicle health
Battery degradation, fault codes and service adherence, per vehicle.
faults · degradation - 06 / 06
Cost per delivery
Fully loaded: energy, driver, maintenance, compliance and hub overhead.
₹ per drop
What clients get
Access, not screenshots.
SLA reporting
Performance against the agreed window, with the as-of date on every figure.
Monthly operations review
A working session on exceptions, causes and what changes next month.
API access
Trip, status and proof-of-delivery events into your own systems.
Interface fragments shown across this site are abstracted. We do not publish screenshots containing client names or vehicle registration numbers, on this site or in a sales deck.