Live operations
Fleet teams depend on continually updating vehicle positions, statuses and operational information throughout the working day.
Tracklog Web Platform
Rebuilding a legacy telematics platform for modern fleet operations.
Tracklog Web Platform
Rebuilding a legacy telematics platform for modern fleet operations.
Tracklog had developed over many years into a capable and highly specialised telematics platform.
Its existing systems supported a wide range of fleet-management workflows, but the underlying technology and user experience were becoming increasingly difficult to evolve.
The challenge was not simply to create a newer interface. The platform needed a modern technical foundation capable of supporting continued development while remaining compatible with established devices, integrations, customer workflows and significant volumes of live vehicle data.
Jublo worked with Tracklog to progressively rebuild the web platform and supporting APIs while preserving the operational depth customers already relied on.
hero
The challenge
Replacing technology is straightforward. Replacing years of operational knowledge is not.
A mature enterprise platform contains far more behaviour than is immediately visible in its interface. Tracklog had accumulated specialist functionality around real fleet operations over many years.
Complex historical data
Reporting and journey analysis depend on significant volumes of telematics data accumulated over long periods.
Established customer workflows
Areas, routes, alerts, reporting and vehicle-management processes could not simply disappear during redevelopment.
Multiple integrations
The platform connects with telematics hardware, third-party systems and services with different protocols and behaviours.
Product dependencies
The web platform sits within a wider ecosystem of mobile applications and operational services.
Continuous operation
Modernisation had to happen while the existing platform continued supporting live customers.
Our role
More than a frontend rebuild.
Jublo’s involvement spans the wider Tracklog platform rather than being limited to the interface.
We worked across product thinking, user experience, software architecture, frontend and backend engineering, APIs, live-data delivery, integration and infrastructure.
That broader involvement meant decisions in one part of the product could be considered in the context of the wider system. Instead of simply reproducing the structure of the legacy application, the work created clearer boundaries between the user experience, APIs, operational services and underlying data.
Our approach
Modernise progressively rather than attempt a disruptive rewrite.
Every engagement begins with understanding the organisation, the people involved and the outcome that matters. From there, we challenge assumptions, make deliberate decisions and engineer technology that can continue to evolve.
01
Separate
Create a new web application that could evolve independently from the structure of the previous interface.
02
Establish
Introduce clearer API boundaries between the user experience, operational services and underlying data.
03
Preserve
Understand which existing behaviours represented genuine customer and operational requirements rather than assuming legacy automatically meant unnecessary.
04
Improve
Continue strengthening architecture, infrastructure, deployment and performance as the platform evolved.
05
Extend
Use the new foundations to support additional products, integrations and applications without repeatedly rebuilding the same capabilities.
Capabilities
Enterprise platform modernisation
Web application engineering
API architecture
Real-time data systems
Telematics integration
Event-driven services
Historical data processing
Reporting platforms
Mapping & geospatial workflows
Cloud infrastructure
Performance engineering
Legacy system migration
What we delivered
Software used in the field behaves differently from software designed in isolation.
Tracklog operates within a physical environment involving vehicles, drivers, mobile devices, telematics hardware and networks.
The platform has to deal with intermittent connectivity, delayed or duplicated device messages, continuously updating interfaces, multiple hardware manufacturers, long-running journeys and vehicles operating across different countries and time zones.
Those realities influence everything from API and caching strategies to data processing and user experience. The platform has therefore been developed around how fleet operations actually behave, not solely around ideal technical conditions.
Ongoing partnership
Modernisation is not a finish line.
Jublo continues to work across the Tracklog platform as customer requirements, products and infrastructure evolve.
That includes developing new capabilities, improving existing services and responding to the realities uncovered through day-to-day operation.
The relationship reflects the way we approach enterprise technology more broadly: not as a one-off implementation, but as software that needs to keep adapting alongside the organisation it supports.