Platform

One truck, one ecosystem

FleetRan is not a tracker with features bolted on. It is one chain from the engine to the owner’s screen, where each part knows what the others are doing. That is the whole product: everything understands everything else.

The chain

Data moves in one direction, through parts that each have a job. Nothing in this chain depends on a phone, a pairing or a driver remembering to open an app.

  1. Driver

    Signs in on the terminal. Identity follows the person, not the truck.

  2. Fleet Driver Terminal

    The one screen in the cab. Locked down, offline-capable.

  3. Fleet Gateway

    Wired to the vehicle. Reads CAN and J1939, buffers when offline.

  4. Truck

    Engine, transmission, aftertreatment, faults, odometer, position.

  5. Fleet Cloud

    Ingestion, event platform, domain services, operational history.

  6. Fleet Command Center

    Where the owner, dispatcher, safety and maintenance work.

How the data actually travels

  1. TruckCAN / J1939
  2. Fleet GatewayRead-only telemetry
  3. Driver TerminalHardwired USB
  4. Fleet CloudSecure ingestion
  5. Command CenterFleet operations

Telemetry becomes

  • GPS
  • HOS
  • Health
  • Load
  • Maintenance
  • Alerts

Dispatch instructions and load assignments travel back down to the terminal — never to the vehicle. FleetRan reads the truck; it does not command it.

DriverTruckTrailerLoadLocationCompany

What converges on it

Each of these is a system a fleet buys separately today. The value is not in any one of them — it is in the fact that they share the same context.

Trailer

Automatic pairing, independent tracking when detached.

Cameras

Modular. Local recording, event capture, authorised live view.

Documents

BOL and POD captured from the load workflow, not from a folder.

Loads

One lifecycle from assigned to completed, with the paperwork attached.

ELD / HOS

A module inside the ecosystem, never the centre of the product.

Navigation

Truck-safe routing — height, weight, axle and restriction aware.

Maintenance

Faults, history, cases and repairs tied to the vehicle record.

Communications

Driver, dispatch and maintenance, over the truck connection.

Economics

Settlements, fuel, tolls and cost per mile, from operational data.

The hardware, with its real status

Nothing below is production hardware. Each component carries the status it actually has, because a fleet that discovers the truth at installation is a fleet you never get back.

Vehicle

  1. Truck CAN / J1939
  2. Fleet Gateway
  3. Hardwired Terminal
  4. Fleet Cloud

Cameras

  1. Cameras
  2. Local network
  3. Terminal / Gateway

Detached trailer

  1. Trailer Node
  2. Independent IoT link
  3. Fleet Cloud

Explore the hardware

Go deeper