Vehicle tracking
Live vehicle position, trip history, geofencing and driver behaviour, ingested from GPS trackers and OBD devices and turned into reports a fleet manager acts on.
- Year
- 2018–present
- Timeline
- Multiple engagements
- Team
- Symphony Apps
- Stack
- 6 technologies
Live
Position updates
Millions
Points ingested / day
Geofence
Alerts & rules
Offline
Buffered telemetry
GPS telematics and fleet visibility. Figures measured against the process this platform replaced, twelve weeks after full rollout.
The problem
Trackers send noisy, out-of-order, sometimes duplicated data over unreliable mobile networks. A naive ingest produces maps with vehicles teleporting across the country and trip reports nobody trusts.
The approach
Treat telemetry as a time-series problem: idempotent ingest, device-clock reconciliation, map-matching and smoothing before anything is shown, and raw data kept so a disputed trip can be re-derived.
Alert rules — geofence entry and exit, speeding, idling, harsh braking, unauthorised night use — are evaluated on the stream rather than by polling a database.
The build
MQTT and TCP listeners for the common tracker protocols, a normalising layer per device type, PostGIS for spatial queries and TimescaleDB for history, WebSockets for the live map, and scheduled reports for fuel, mileage and utilisation.
The stack
Node.js and C# .NET ingest services, PostgreSQL with PostGIS and TimescaleDB, Redis for hot state, and a React operations console with a live map.
Technologies
- Node.js
- C# .NET
- PostgreSQL + PostGIS
- TimescaleDB
- MQTT
- WebSockets
Tell us what you’re trying to ship
A first call is thirty minutes and costs nothing. Bring the problem, not a spec — working out what to build is the part we are good at.
Or email office@symphonyapps.ro. We reply within one business day, in English or Romanian.