TISvia
000
Web · AI · Automation
Web & AI Studio
← Projects

VVV-Trans

A bot that continuously checks whether Poland’s SENT / RMPD system can see each truck’s tracker — and raises the alarm before a signal gap turns into a fine.

Case
01
Field
Automation · Telegram bot
Format
Internal tool for the client
Link
Private project
01 — VVV-Trans

Private client tool — the interface and trip data are not published.

Challenge

VVV-Trans is a carrier whose trucks regularly travel through Poland. Every such trip by a foreign carrier must be registered in RMPD — Poland’s register of international road transport in the SENT system — and up-to-date GPS data must be sent there for the entire route.

The problem is that a tracker can “disappear” unnoticed: the battery dies, the mobile network drops, data gets stuck between the tracker provider and the government server. The driver keeps going, the dispatcher sees the truck in their own monitoring system — but RMPD no longer does.

Polish courts are clear in such cases: the carrier is responsible for uninterrupted data transmission regardless of the cause. The fine is 10,000–12,000 PLN per trip, plus a ticket for the driver. And the official tools don’t warn the dispatcher: the status is only visible in the driver’s app or after manually checking each trip on the PUESC portal.

Solution

We didn’t wait for a convenient API and built a layer on top of what already exists. The bot checks every active trip in RMPD in a loop — just as a dispatcher would via the RMPD406 form (declaration number, vehicle plate, tracker ID) — and compares the time of the last recorded position with the current time.

As soon as the data stops updating, the dispatcher and the driver get a Telegram notification — a messenger that’s already open on everyone’s phone. No new apps, passwords or training.

How it works

  1. 01

    Trip

    The dispatcher adds a trip to the bot: RMPD declaration number, truck plate and tracker ID.

  2. 02

    Monitoring

    Every few minutes the bot checks the last position RMPD received and how much time has passed since it was recorded.

  3. 03

    Signal

    Over 10 minutes without an update — a warning. Approaching an hour — an alarm: under SENT rules, after an hour of malfunction the driver must stop at the nearest parking area.

  4. 04

    Response

    A notification with the truck plate and the time of the last point arrives in Telegram — the tracker can be restarted while the gap is still short.

Features

  • All active trips monitored in one chat
  • Two-level alerts: warning and alarm
  • Automatic notice when the signal is back
  • Fleet-wide summary with a single command
  • Gap log — evidence if a fine has to be appealed

Results

  • Signal gaps are spotted within minutes, not after a fine
  • The dispatcher no longer checks every trip on PUESC by hand
  • The driver gets clear instructions while still on the road

Stack

  • Telegram Bot API
  • SENT / RMPD (PUESC)
  • RMPD406
  • Check scheduler
Discuss a similar project →
Next caseEcowood →