What the Platform Actually Does.

Four capabilities covered in the depth an operations manager needs — including the failure modes most vendors leave out, because knowing why a feature goes wrong is what makes it work.

Capabilities, Explained Honestly

The four modules that carry most of the commercial case for a telematics deployment. Each page covers how it works, how it fails, and what to decide before you buy hardware.

⚙️

Fuel Monitoring

  • Sudden drops while stationary
  • Drops during movement, which are harder
  • Refuels smaller than the receipt
Fuel Monitoring guide
⚙️

Geofencing

  • Circles for simple sites
  • Polygons for real boundaries
  • Route corridors for fixed journeys
Geofencing guide
⚙️

CAN Bus Monitoring

  • Real odometer, not GPS-derived distance
  • Engine hours for plant and billing
  • Fuel consumed by the engine
CAN Bus Monitoring guide
⚙️

Driver Behaviour

  • iButton or RFID at shift start
  • Events attach to a person, not a vehicle
  • Shared vehicles stop corrupting the data
Driver Behaviour guide

Which One Pays for the Project

A telematics deployment is justified by one number, not by a feature list. Find yours here.

Matching the capability to the business case
If your problem is…Start withHardware it needs
Fuel disappearing between refuelsFuel monitoringCapacitive probe, or CAN on FMS trucks
Disputed site times and delivery claimsGeofencingAny tracker — no extra hardware
Plant billed on hours you cannot proveCAN bus monitoringCAN-capable tracker or adapter
Accident rate and insurance premiumsDriver behaviourDriver ID reader; camera if disputes are common
Vehicles used outside working hoursGeofencing with time windowsAny tracker — no extra hardware
Service done on calendar, not usageCAN bus monitoringCAN-capable tracker or adapter

Why these pages describe failure modes

Most feature pages in this industry list what a capability does. That is not the information a buyer is missing — every platform does geofencing, every platform detects harsh braking. What buyers actually need is the part nobody publishes: why the feature gets switched off three months after go-live.

Geofencing gets muted because boundary drift floods a dispatcher with alerts. Fuel monitoring gets disbelieved because nobody calibrated the tanks. Driver scoring gets abandoned because it ranked the busiest drivers as the worst. None of these are software defects and all of them are predictable, which is why each page above spends as much space on the failure as on the feature.

The 49 modules, and why only four have pages

The platform includes 49 modules covering tracking, fuel, garage and service, inspections, HR and payroll, billing, dispatch, cargo security and reporting. Writing a page for each would produce forty-five pages nobody searches for and four that matter. These four carry the commercial case in almost every deployment we see; the platform page lists the rest.

Capability is in the platform; feeding it is hardware

Worth stating plainly before anyone buys trackers: every feature here is included in the platform, but not every tracker can supply the data it needs. Fuel monitoring needs a probe or a CAN connection. Driver scoring needs an identification reader. Video review needs a camera. The device guides cover what each manufacturer can actually feed, which is the question that decides your hardware order.

Tell us the number that justifies the project and we will show you the shortest path to it. Book a demo on your own fleet or message us on WhatsApp — fleet size, vehicle types and the problem you are trying to solve is enough to start.

Common Questions

Are these features charged as separate modules?

No. The platform ships with 49 modules and the features described here are part of it rather than paid add-ons. What varies with price is device count and hosting shape, not which capabilities you can switch on.

Which feature should a new deployment start with?

Whichever one has a number attached to it. If fuel loss is costing you, start with fuel monitoring and a probe. If you are billing plant by the hour, start with CAN engine hours. Starting with everything at once is how deployments stall — pick the capability that pays for the project and add the rest once it has.

Do all features work on every tracker?

No, and this is worth checking before you buy hardware. Fuel monitoring needs a probe or CAN, driver scoring needs driver identification hardware, video features need a camera. The capability is in the platform; whether your device can feed it is a hardware question. The device guides cover this per manufacturer.

Can I see these working before committing?

Yes, and on your own fleet rather than a sample dataset. A demo built against your vehicle types, your sites and your reporting requirements tells you considerably more than a generic walkthrough.

How many modules does the platform actually include?

49, covering tracking, fuel, garage and service, HR and payroll, billing, dispatch and reporting. The pages here cover the four asked about most; the full list is on the platform page.

See It Running on Your Fleet.

Bring your vehicle types and your reporting requirements. A demo built on those is worth more than any feature list.

Book a Live Demo