Gallery
The challenge
A fleet risk platform produces a steady stream of driving events. Harsh acceleration, hard braking and speeding are useful signals, but on their own they are just rows in a list. When an operator or a fleet customer needs to look properly at what happened on one trip, someone has to go back into the tracking data, find the right vehicle and time window, pull the positions and events around it, and put them together by hand. On a Traccar-based platform, that raw material is all there: positions and events for every device. What Traccar does not provide is a way to say "this event matters, keep the evidence around it together" and come back to it later. GeoLox, a fleet tracking and risk platform, needed that step inside its back office, alongside the driving scores it already calculates.
Architecture
We built GeoLox Admin end to end, the super-admin panel of the GeoLox platform, in Laravel 12, MySQL and Bootstrap 5, synced with Traccar. Incident extraction is one of the parts we built. This case study looks only at that feature. The full GeoLox Admin panel, from client and device management to Stripe billing and the scoring engine, is covered in our main GeoLox Admin case study.
Solution
Incident extraction sits in the Risk & Safety section of the admin, next to Driving Scores, and works in two steps. Suspicious Events. Driving events that need attention are listed in one table with the event type, the vehicle, a severity label such as Critical or High, the detail of the event (for harsh acceleration, the change in speed), the time and the location. Operators filter the list by event type, vehicle and date range, so they can go straight to one vehicle or one day. Every row has an Extract action. Incident Packages. Extracting an event creates an incident package. The packages table records a title, the vehicle, the period covered, the positions and events included, a status and when it was created, with actions per package. Operators filter packages by status and vehicle, and can also start a New Extraction directly from this screen. Sold as an add-on. Incident Extraction is switched on per device as part of the device's subscription, next to the Risk Scoring add-on, each with its own status, expiry date and days remaining. That lets GeoLox offer incident extraction as an upgrade on the devices that need it, rather than bundling it into every plan. Because the admin is synced with Traccar, the positions and events in a package come from the same tracking data the rest of the platform uses, and the feature sits beside the scoring engine and scoring policies rather than in a separate tool.
Results
What incident extraction gives the GeoLox operator: - Harsh-driving events are triaged in one list by severity, vehicle and date, instead of being found by digging through raw tracking data - One Extract action turns an event into a package with the vehicle, period, positions and events kept together - Each package carries a status and creation date, so the operator can follow every incident from one table - Incident extraction is a per-device add-on GeoLox can sell, next to Risk Scoring - Driving scores, suspicious events and incident packages live in the same Risk & Safety section of one admin Next step Running a telematics or fleet risk platform where driving events still end up as screenshots and spreadsheets? Talk to us at https://techmania.solutions
Related project
GeoLox Admin
Super-admin panel for GeoLox: client onboarding, Traccar device provisioning, subscription lifecycle, alerts, and mileage exports.
View project in portfolio