Skip to main content
LIOMO

In-house platform

LIOMO Fleet: a fleet platform built and operated end to end

How LIOMO designed, built and runs its own fleet platform, from the tracker protocol and gateway to alerts, remote commands and monthly reports.

LIOMO Fleet · system architecture

Challenge

The challenge

Companies that run vehicles need more than dots on a map. They need to trust what they see: whether a vehicle is really moving, whether a temperature alarm is real, whether a command reached the vehicle. And they need it priced so that a delivery van and a refrigerated truck do not pay for the same features.

LIOMO set out to build a platform that it could stand behind completely, because it would also be the one operating it: installing the hardware, onboarding clients and answering their questions.

Approach

What we built

  • 01

    A gateway that speaks the tracker protocol

    A Node.js TCP server decodes Teltonika Codec 8 messages, stores positions in PostgreSQL and raises alerts, events and geofence warnings as data arrives.

  • 02

    A platform for daily operations

    A web platform for live maps, trips, geofences, alerts, vehicle data, sensors, drivers, fuel, costs, income and reports, with main-user and read-only roles.

  • 03

    An operator console

    A private console where LIOMO creates clients, registers trackers, switches packages on per vehicle and records payments.

  • 04

    Remote commands with layered safety

    Position requests, restarts, reporting intervals, accessories and immobilization, each checked against what the tracker reports before and when it is sent.

Architecture

How it fits together

Two applications meet in one database. Shared logic is pure and tested, with no network or database access.
  1. 01

    Trackers and sensors

    GPS trackers in each vehicle, with optional wiring to vehicle electronics, probes, door switches, fuel sensors and relays.

  2. 02

    Gateway

    TCP server that decodes, validates and stores messages, raises alerts and sends queued commands when a tracker connects.

  3. 03

    Database

    PostgreSQL with versioned migrations, daily clean-up of old positions, and backup and restore scripts.

  4. 04

    Shared logic

    Distance, trips, fuel, costs, billing rules, alerts, driver scores and access rules, used by both applications.

  5. 05

    Web platform

    Client platform and operator console, with per-client and per-vehicle feature packages.

What it shows

What it demonstrates

  • End-to-end ownership

    One team responsible from the device protocol to the invoice, with no gap between hardware, data and software.

  • Careful automation

    Commands that can stop a vehicle are designed to fail safe: refused when conditions are not right, confirmed by the device, and taken back automatically if confirmation does not arrive.

  • Honest data

    Missing signals, stale readings and uncalibrated sensors are labelled as such, so people can trust what they see.

See a LIOMO system working on your use case

Tell us about your vehicles, sites or equipment. For fleets, we show you LIOMO Fleet itself. For other solutions, we walk you through how a system would be designed for your operation and answer the technical questions.