Fleet Tracking and Vehicle Telematics

Eurisko X builds fleet tracking and telematics platforms: the back end that takes in positions from thousands of devices, the rules that turn those positions into events and the web and mobile applications dispatchers and managers work in.

The reference is the Vehicle Tracking System Eurisko engineered for Navleb, a company specialised in GPS navigation, tracking and fleet management.

The problem

The fleet has trackers. What it lacks is one platform that understands all of them.

Vehicles are bought over years and fitted with whatever tracker was current, so a fleet ends up with devices from several manufacturers, each speaking its own protocol and each with its own portal. The operations room switches between screens, and nobody can answer a simple question, such as which vehicle is nearest, without a phone call.

An off-the-shelf tracking service solves that until the business needs something it does not offer: a rule specific to the operation, a link to the dispatch or maintenance system, a scoring method the insurer accepts, or data kept under your own control. That is the point at which an organisation, or a tracking provider serving many customers, needs a platform of its own.

Who it is for

Fleet operators and the companies that sell tracking to them.

Both need the same engine. One runs it for itself, the other for its customers.

Logistics, delivery and field service

Operators who need live positions, trip history and dispatch in one place, tied to their orders and jobs.

Government and municipal fleets

Public bodies tracking service vehicles, waste collection or buses, with reporting on use and compliance.

Tracking and telematics providers

Companies offering tracking as a service that need a multi-account platform under their own brand.

How it works

A message from the device becomes an event a person can act on.

Each tracker sends its position and status over the mobile network. A device-communication layer speaks the protocol of each manufacturer and turns every message into one common format. From there a stream of positions becomes meaning: a trip that started and ended, a geo-zone entered or left, a speed limit broken, a harsh brake, an engine idling.

A rule engine applies the logic of the operation to those events (this vehicle may not leave this zone after this hour) and raises a notification by push, email or SMS. The same data feeds driver scoring, reports and maintenance reminders. The back end is made of microservices on an auto-scaling architecture, so that adding devices means adding capacity, not redesigning the system.

What Eurisko X builds

Back end, web application and mobile apps.

Exposed through clean APIs, so your own team can build on it too.

Device and fleet services

Identity and access management, communication with devices from many manufacturers, and management of accounts, vehicles and drivers.

Rules and events engine

Trips, geo-zones, violations and driver scoring, with a rule engine for the logic particular to your operation.

Reporting and notifications

Prebuilt and custom reports, scheduled maintenance reminders and notifications by push, email and SMS.

Dispatch and monitoring apps

Dispatching services and a monitoring app with live maps, tracking history and alerts, on web and mobile.

Nearest published proof

Navleb: a tracking platform that follows thousands of devices.

Navleb specialises in map development, GPS navigation and tracking, and fleet management systems. Eurisko engineered its Vehicle Tracking System: a complete solution for monitoring, managing and tracking fleets and assets, spanning a back-end system, a web application and several mobile apps. The platform had to track devices from many different manufacturers, process large volumes of telemetry and expose everything through clean APIs, for the web channel built by Navleb’s own team and the monitoring app built by Eurisko.

The case study states the result: a complete tracking platform that follows thousands of devices and serves thousands of active users on an auto-scaling serverless, microservice architecture. The engagement also introduced the Navleb team to agile delivery and Scrum. For telemetry from fixed sensors in harsh terrain, see Smart Forest.

FAQ

Frequently asked questions.

Can the platform work with the trackers we already have?

In most cases, yes. The device-communication layer is built to speak to devices from different manufacturers, as the Navleb platform does, so a mixed fleet appears on one map. We review your device list at the start and add the protocols that are missing.

Why build a platform when tracking services exist?

A subscription service is the right choice for many fleets. Building makes sense when you need rules and integrations the service does not offer, when you want the data under your own control, or when tracking is itself the product you sell to customers, as it is for Navleb.

Can it connect to our dispatch, maintenance or ERP system?

Yes. Everything the platform does is exposed through APIs, so jobs can arrive from your dispatch system, mileage can feed maintenance planning and trip data can reach finance or billing. Navleb’s own team built its web channel on the same APIs.

How does driver scoring work?

Scores are calculated from recorded events such as speeding, harsh braking and acceleration, idling and geo-zone violations, weighted by rules you set. The method is transparent to drivers and managers, which matters if the score is used for coaching or incentives.

Does it track assets other than vehicles?

Yes. The Navleb system monitors fleets and assets. Trailers, containers, generators and equipment can carry trackers and appear on the same map, with rules suited to things that should stay still as well as things that move.

Let’s build

Ready to build with Eurisko X?

Tell us about your project. We’ll come back within one business day with the right team and a clear next step.

Start a project →

Popular searches

Jump to