5 min read

By the RAAD team

Mixed fleet data management without the silos

PowerTrackWhite-label

Listen to this article

Mixed fleet data management means pulling GPS, fuel, charging, camera and sensor signals from EVs, diesel vehicles, trailers and equipment into one operational picture. Plenty of fleets still run each of those in a separate portal. The fix is not new hardware. It is one console that takes over the trackers and sensors you already own.

Why mixed fleet data management breaks down

A mixed estate rarely fragments on purpose. It fragments one purchase at a time. Electric vans arrive with the manufacturer's portal for state of charge and charging. Trackers come with a vendor login. Cameras report into a third interface. Generators, cold rooms and trailers either get their own dashboard or none at all, and anything that ties the pieces together gets rebuilt by hand in a spreadsheet.

The patchwork has a running cost. Staff spend the first hour of the day collecting numbers instead of acting on them. Simple questions, like what a route cost last week or which vehicles sat idle, need someone to merge exports before anyone can answer them. Trends stay buried until a person has time to dig.

The clearest symptom is this: when a fleet manager spends more time managing systems than managing vehicles, the tooling has fallen behind the fleet.

The data electrification adds

An electric van does not merely burn a different fuel. It produces a different class of data. State of charge, charging windows, kWh drawn per route and battery condition all feed dispatch, maintenance planning and cost modelling in ways diesel never did.

Those numbers usually stay locked in the vehicle maker's own portal while fuel data sits in a separate telematics login. Comparing a diesel route with an electric one means merging two exports and hoping the time windows line up.

This is where the Power module in RAAD earns its place. Every fill is checked against what the tank actually took, a fuel drop while the engine is off opens a case, and kWh and battery swaps post to the same ledger as diesel. The result is one cost per vehicle and per route, whichever way the vehicle is powered.

One console without a hardware swap

Replacing working trackers across a fleet means downtime, capital cost and a migration that never quite ends. The faster route to one picture is a console that adopts the hardware you already run.

That is how RAAD is built. It takes over the trackers, cameras and sensors customers already have installed and brings every signal into one estate, so tracking, power, camera events, site sensors and paperwork answer to one map and one set of roles.

Separate portals versus one estate

The difference shows up in the questions an operations manager asks every week:

Weekly questionSeparate portalsOne estate in RAAD
Where is everything right now?A login per vendor, none of them completeOne live map with trip and stop history for every vehicle and trailer
What did this route cost?Fuel in one system, kWh in another, merged by handFills, kWh and battery swaps on a single ledger
Which alerts need me today?Every system emails someone, and the noise winsAlert triage holds back what needs no person and escalates the rest with a reason and a proposed fix
Was that driver event real?An event reference to look up elsewhereThe clip arrives with time, place and speed attached
Is our paperwork current?Licences and inspections tracked by handDocument expiry and inspection reminders on schedule

What changes day to day

Unified data changes the shape of a working day more than any single report does.

  • One morning check replaces five logins: the map, yesterday's trips, open cases and expiring documents sit on one screen.
  • Rules mean the same thing everywhere: a geofence or an eco-driving score applies to vans, trailers and generators alike, not only to the vehicles one vendor happens to cover.
  • Cost questions stop being projects: with fuel, kWh and battery swaps on one ledger, per-route cost becomes a routine answer rather than an analyst's afternoon.
  • Alerts arrive ready to act on: triage reads every alert, holds back what does not need a person, and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until someone approves it.

The live map, trip and stop history, geofences and scheduled reports come from RAAD's Track module. Assets, Drivers, Documents and Maintenance are included with every account, so the paper trail keeps pace with the telemetry. Fixed-site sensors, such as temperature and door state in a cold store, arrive through Sense and appear on the same map as the vehicles that serve them.

A note for resellers

For partners who resell RAAD, unification is a commercial story as much as a technical one.

A customer with a mixed estate is a customer juggling several vendors and several renewals. Under white label, the partner brings them one console carrying the partner's own brand, logo, domain and invoices. Because the service is billed monthly by the partner, a one-off hardware sale becomes recurring revenue that grows as the customer adds vehicles and sites.

The Platform, Partner and Account hierarchy keeps every tenant walled off, with roles set per screen, so a partner can run many customer estates from one place.

Common questions

Can RAAD use the trackers I already have installed?

Yes. RAAD is built to take over the hardware customers already run rather than replace it, so consolidation does not start with a swap-out project. Working trackers, cameras and sensors keep working inside the same estate.

How do I compare diesel and electricity costs in one fleet?

Through the Power module. Diesel fills, kWh and battery swaps all post to one ledger, so a route's cost reads the same whichever fuel it used. Every fill is checked against what the tank took, and fuel loss with the engine off opens a case.

Who approves an action suggested by an alert?

A person does. Triage reads every alert, holds back what does not need attention and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until someone approves it.

Can a reseller brand the console as their own?

Yes. RAAD is white-label. Partners sell it under their own brand, logo, domain and invoices, and bill their customers directly, turning one-off hardware sales into monthly recurring revenue.

One platform for every connected asset

Tracking, power, cameras, metering and compliance in one console — resold under your own brand and billed by you.

Explore the RAAD platform