FleetMind

TJL FleetMind · Vehicle and fleet intelligence

Every kilometre, accounted for.

A tracker in the vehicle and one screen for everything it tells you: where it is, how it was driven, what it cost and what is wearing out. For one car or a whole fleet, in Arabic and English, built and hosted in the Kingdom.

November 2026

Who we are

One Saudi team, from the plug in the car to the screen in your hand.

TJL is a Saudi deep-tech company working in energy, mobility and defence. We write the algorithms and run the servers ourselves, here in the Kingdom. FleetMind is our mobility product: the tracker, the protocol that reads it, the platform and the screens are all ours.

+60companies advisedTJL
+20implementations deliveredTJL
  • We read the hardware ourselvesBoth tracker protocols are decoded in our own code and checked against frames from our own cars, not taken on trust from a supplier's document.
  • Hosted in RiyadhPositions, readings and accounts stay on a server in the Kingdom. Nothing is sent to a tracker vendor's cloud.
  • Arabic first, English tooEvery screen, every export and every message in both, with a right-to-left layout that is drawn, not translated.
From the vehicle to youA reading
Every reading takes this path, a few seconds apart while the vehicle movesIllustration

What every owner asks

Four questions, one screen.

Whether you run one car or two hundred, the questions are the same. FleetMind answers them from what the vehicle itself reports, and the rest of this presentation follows one working day to show how.

  • Where is it now?Position, speed and whether the tracker is really talking to us. Live tracking
  • How was it driven?Trips cut from movement, distance, speeds, harsh events. Trips · Behaviour
  • What did it cost?Fuel receipts from the driver's phone, maintenance records, cost per kilometre from the road. Fuel and maintenance
  • What is about to fail?Engine readings while it runs, and a date for when a component reaches its limit. Engine data · Fault prediction
One working day, as FleetMind records it06:00
Click a moment to open its sheetIllustration

07:40 · Live tracking

Where it is now, and whether the tracker is really talking.

Every vehicle on one map, refreshed every few seconds. FleetMind judges the connection from any packet at all, heartbeats included, so a parked vehicle whose tracker is awake is never called offline, and a tracker that has gone quiet is never shown as moving.

  • Offline after five silent minutesThree to five missed heartbeats. The vehicle may be off, out of coverage or unplugged; the map says stale, never moving.
  • Weak signal, flagged earlyMobile signal at 0–1 of 4 is marked before readings start arriving late or go missing.
  • On the phone tooThe same live screen on a phone, in Arabic or English, with the map and the cards drawn from one feed so they cannot disagree.
Live monitoring · four vehiclesOnlineWeak signalOffline
Online–
Weak–
Offline–
07:40
Click a vehicle for its cardIllustration with example values · time runs 30× faster

08:50 · Trips

Trips cut themselves. Nobody presses start.

FleetMind reads trips out of the positions alone. A trip begins on the first moving fix and ends after five minutes without one, whether the vehicle was parked or the tracker fell silent, so a stop at a traffic light stays inside the trip and a real stop closes it.

  • Distance, duration, top and average speedMeasured along the road from the fixes, with GPS drift under 200 metres discarded and impossible jumps left out.
  • Tap a trip, see its roadEach finished trip is kept with its route; the one in progress is shown live and never stored half-done.
  • Statistics that always agreeDistance, top speed and trip count on the home page are summed from the same trips the list shows.
One morning · the trips as they close07:35
Trips
5 min still
Move the rule and the morning is re-cut from the same fixesIllustration with example values · time runs 240× faster

10:10 · Fuel and maintenance

Receipts from the driver's phone. Cost per kilometre from the road.

Each account has a fuel link. The driver opens it on any phone, with no account and no app, picks the vehicle, types the amount and photographs the receipt. You approve or reject it on your side, and FleetMind works out what the vehicle really costs per kilometre from the receipts and the distance the tracker measured.

  • A figure only when there is evidenceCost per kilometre needs at least two receipts and 100 km of GPS distance between the first and the last. Until then the page says so, rather than guessing.
  • Maintenance records with their paperworkEach service keeps up to twenty photos or PDFs, 5 MB each, previewed in place. The date is the only field you must fill: a photo of the invoice can stand in for the rest.
  • Drivers, typed onceA list of drivers per account; the fuel form offers them beside the vehicles, and the usual driver of each vehicle is preselected.
The fuel link, and what it feeds
Fuel invoices · RYD-12340 receipts
GPS km since first fill–
Cost per km–
0 km
Add receipts and move the distance: the figure appears only when the rule is metIllustration with example values

11:30 · Route planning · business accounts

Nine stops, the best order, on real roads.

Type the stops as place names or paste coordinates, pick the vehicle, choose round trip or one way, and FleetMind orders them. Up to thirteen stops the order is the proven optimum, checked against every other order; above that, a near-best one. Distances and times come from our own road router in Riyadh, never a straight line.

  • Every leg, measuredRoad distance and drive time for each leg, under each stop and in the export. Ten minutes per stop unless you say otherwise.
  • Fuel from the vehicle's own evidenceA route's fuel cost uses that vehicle's receipts, or its engine tracker's rate labelled as an estimate. With neither, the page says what is missing instead of inventing a rate.
  • Stops never leave our serverThe road router runs on TJL's own machine in Riyadh; no third-party routing service sees your customers' addresses.
Delivery run from the depot
Stops, in the order they were typed
As typed–
Optimised–
Saved–
Click the map to add a stop, then optimise. The order is computed in this pageIllustrative district · real ordering, example times

13:30 · Engine data · premium accounts

What the engine says, while it is running.

The premium tracker plugs into the OBD port and reports the engine itself: revolutions, charging voltage, load, coolant temperature and fault codes, with every position. FleetMind shows them live while the engine runs, and when it stops the panel says "last seen readings" with the time, never pretending a parked car is live.

  • Charging voltage only while runningA parked battery at 12.5 V is normal; the same figure with the engine on is a warning. Readings are gated on the engine actually turning.
  • Estimates say soThe fuel rate this hardware reports is labelled an estimate until its maker confirms the source. We would rather show a labelled figure than an unlabelled guess.
  • In every reportTrip, status and history exports gain engine and fuel columns on premium accounts; a basic account's files keep their shape.
Engine data · RYD-1234Live
13:30
One trip from ignition on to engine off, then the panel holds the last readingIllustration with example values · time runs 60× faster

16:00 · Fault prediction · premium accounts

Not a fault today. A date to book the workshop.

Every engine day is reduced to a few numbers: the median charging voltage, the hottest coolant, how long the engine ran, how long it strained. FleetMind fits a trend through those days and projects it to the same warning limits the fault engine uses: 13.0 volts, 107 degrees. The answer is a date, or an honest "not enough history yet".

  • Seven days before it will say anythingUnder seven days of data, or when the daily values disagree about the direction, the component reads "collecting", not a guess.
  • Ninety days ahead, no furtherA crossing more than ninety days out reads "stable". Trends that far are noise dressed as foresight.
  • Today's risk, with evidence capsThe same page scores today's cooling, engine and electrical risk. No signal caps a score at 40, one spike at 75: a component cannot reach "critical" by accident.
Where the component is heading
5 days
Collecting Illustration with example values · real trend fit

Driving behaviour · premium accounts

How it was driven, day by day and driver by driver.

From the same positions, FleetMind counts harsh braking, harsh acceleration and speeding, per vehicle and per day, and rolls them up into a daily score. The counts are honest about their limits: an event can only be judged between two fixes close enough in time to see it.

  • Events per 100 km, not per tripRates are comparable between a delivery van and a long-haul truck; raw counts are not.
  • The fix interval decides what can be seenA basic tracker reports every two to three seconds while moving and sees a hard stop. An engine tracker left at its twelve-second default misses most of them, so its counts run low until the interval is shortened. The page says which it is.
  • Two implementations, one answerThe daily rollup is computed in the database and again in plain code, and the two are checked against each other on real drives.
One trip, two ways of driving it
Harsh braking–
Harsh acceleration–
Speeding–
Day score–
100 km/h
Illustration with example values · real detection

Packages

One car or a whole fleet. Basic or premium.

Two choices, made once when the account is created. Customer accounts are for a person with one vehicle: the same platform, worded for one car. Business accounts run a fleet with drivers and dispatch. Basic is tracking, trips, fuel and maintenance; premium adds the engine tracker and everything it makes possible.

4modules in basic: fleet, live map, exports, settings
9in premium: plus route planning, behaviour, fault prediction, traffic density, data logs
2trackers: a basic unit for position and speed, an engine unit for the premium modules

Modules are enforced on the server, per request, so an account sees and receives exactly what it bought. Switching package later is one setting.

Pick an account
Choose, and the menu shows what that account getsThe real module lists · names as they appear in the product

Your data

Your vehicles' data stays yours, in the Kingdom.

Readings are stored on TJL's server in Riyadh, kept apart per account and checked on every request. If you would rather hold them yourself, FleetMind can send every reading to your own API as it arrives and keep nothing, or keep a copy and send one. You choose per account; the vehicle never knows the difference.

  • Apart, per accountEvery read and write is scoped to the account that owns the vehicle. Modules and exports are enforced on the server, not hidden in a menu.
  • Backed up nightly, archived continuouslyA nightly dump that is read back before it is kept, plus a continuous archive, so a failure loses at most about a minute.
  • Yours to take outGPS history, fleet snapshots, trips, deliveries and maintenance as CSV, JSON, Excel or PDF, with engine columns where the account has them.

What leaves our server: map tiles are fetched from OpenStreetMap by your browser, and the engine tracker contacts its maker's assistance server once at a cold start for a faster first fix, a point we have asked the maker to remove.

Where a reading goes
Choose where the readings go; the counters show what is keptIllustration · the three modes as the product offers them

Getting started

Plug in. Claim. Assign. Watch it move.

No installer, no app to download. The tracker plugs into the vehicle's diagnostic port and dials our server on its own; we attach it to your account, you attach it to a vehicle, and you choose your own password from a link that works once. On a phone or a laptop, in Arabic or English.

  • The tracker, not a technicianBoth units are plug-in. The basic unit sits on the OBD port for power and position; the engine unit reads the engine through the same port.
  • Nobody sees your passwordThe account is created with a password nobody knows, and you set yours through a one-time link that expires in seven days.
  • An account manager at TJLTell us the plate, the time and what you saw; a screenshot helps. A short guide to every page comes with the account.
From the box to the map
Click a stepIllustration

Every kilometre, accounted for.

FleetMind by TJL: the tracker, the platform and the screens, designed, built and hosted in the Kingdom.

future@tjl-ksa.org+966 59 051 0662www.tjl-ksa.org