Convert your fleet into a real-time data network. Authenticate drivers at the ignition. Meter fuel at the tank. Decode engine telematics at the CAN. Act on anomalies before they cost you.
This brief walks through the five pillars of the FleetOS platform, its expansion modules, and the two-mode Fuel Dispensing Management System. Each pillar is shown with its technical foundation, the data it produces, and the business event you can act on.
No key, no crank. The vehicle will not turn over until the driver's personal credential — an RFID card or ruggedised iButton — is presented to the in-cab module. Ignition is physically interlocked through a relay on the starter line.
Every cranking event now carries a signed driver identity. Fuel economy, harsh braking, violations, on-time departures — all bind to a person, not a number plate.
When every trip is signed by who started it, driver performance stops being anecdotal. After 60 days of keyed attribution, the spread between best and worst driver fuel economy typically narrows by 22%.
A capacitive fuel-level probe is installed directly in the tank, wired to the FleetOS module independent of the OEM gauge. Samples at 1 Hz, smoothed with a 15-sample moving median, reconciled against distance and engine-on time.
Three separate flows get their own event streams: legitimate consumption, refuelling, and pilferage.
FleetOS speaks the language of any vehicle. BS-VI trucks are read via J1939 / OBD-II CAN with full PGN decoding. BS-IV/V without rich CAN get an identical telemetry record via discrete sensors (inline fuel flow, magnetic pickup RPM, GPS speed, accelerometer harsh-event signature).
Upstream, the dashboard doesn't care which generation produced the data.
| PGN | Signal | Value | Unit |
|---|---|---|---|
| 65262 | Coolant temp | 87 | °C |
| 65263 | Oil pressure | 412 | kPa |
| 61444 | Engine RPM | 1,820 | rpm |
| 65276 | Fuel level | 64 | % |
| 65266 | Fuel rate | 18.4 | L/hr |
| 64892 | AdBlue level | 58 | % |
| 64777 | DPF soot load | 32 | % |
| 65132 | Seat occupancy | TRUE | bool |
One spatial engine powers four disciplines. Polygon fences mark depots, customer sites and no-go zones. Proposed routes are plotted next to the actual trace — deviation is obvious. Driver–vehicle mapping is enforced through key-auth. Duty allocation encodes shift, break and max-drive policies.
When perimeter, route or duty is breached, the platform escalates through tiered alerts: SMS → siren → engine immobilise.
Raw telemetry is noisy. FleetOS correlates signals that individually look normal but together tell a story — fuel dropping while engine is off, truck moving with no ignition event, mileage this week 28% worse than last month on the same route.
Every alert carries a playbook: who is notified, over which channel, what evidence to inspect. Adaptive thresholding manages fatigue.
The five pillars rarely deploy alone. Operations teams layer in modules for safety, maintenance, load integrity and compliance — all on the same asset model and permission framework.
Engine hours, vibration signature and fault codes rolled into RUL estimates — scheduled against the next depot visit.
Dual-lens with on-device inference for distraction, fatigue, phone use, tailgating. 4G stream + event-clip upload.
TPMS per wheel, retrofittable. Under-inflation costs 3–5% fuel. Real-time alerts and retread scheduling.
Cargo-bay temperature and humidity logs, door-open events with GPS. Evidence-grade for pharma and food SLAs.
Concealed button + voice-triggered distress. Silent alarm to control room with live GPS and optional cabin audio.
Auto-generated trip summaries, e-sign POD, and billable-km reconciliation with accounting systems.
Battery SoC, SoH, pack temperature, charge sessions, regen efficiency. Mixed ICE/EV fleets unified.
Air-suspension pressure → payload estimate. Prevents overload fines, tracks empty return-trip running.
Where fuel enters the tank is where most of the leak happens. FDMS wraps any standard in-premise pump with authentication, metering, and per-vehicle policy — so every drop is attributed to a driver, a vehicle, and a reason.
FDMS sits between the pump's flow sensor and its dispensing valve. Nothing flows without an authenticated session. Every session produces a tamper-evident record: who, what vehicle, how many litres, at what flow rate, against what policy cap.
Both the pump attendant and the vehicle driver must present their keys to open a dispensing session. Two signatures on every litre. Ideal for high-throughput depots where audit rigour is paramount.
For captive depots with no pump operator — night shifts, remote sites, private bowsers. The driver uses their own key. Caps enforce the policy: N litres per vehicle per day, only 05:00–22:00, only at Pump-2. Camera snapshot anchors every session.
| Dimension | Cap | Window |
|---|---|---|
| Per vehicle | 180 L | per day |
| Per driver | 240 L | per day |
| Per pump | 6,000 L | per shift |
| Per session | tank vol | auto-detect |
| Time window | 05:00–22:00 | configurable |
| Flow rate | 50 L/min max | anti-spill |
Average observed improvements across 12 FleetOS reference deployments (42–380 vehicles each), 90 days post-deployment.
Every competing product can show you where the truck is. The difference with FleetOS is that every signal — a litre dispensed, a kilometre driven, a braking event, a detour — terminates in an accountable human and a contractual outcome. That's why reference fleets recover their capital in under four months.
Public-cloud SaaS · customer-VPC single-tenant · fully on-prem. Identical data model and dashboard across all three.
REST & GraphQL APIs, webhooks, MCP server for conversational analytics, connectors for SAP TM, Oracle TMS, Zoho, Tally, SAP B1.
AIS-140 hardware. GDPR / DPDP data handling. ISO 27001 controls. Evidence-grade trails for pharma and explosives transport.
Reach out for a pilot scoping call, hardware sample kit, or a reference customer introduction. Typical pilot runs 4 weeks across 10–20 vehicles with full commercial rollout options thereafter.