Know where the fleet is. Understand what needs attention.
Visit the productThe context
A map answers where a vehicle is. Fleet operations also need to explain what happened, who was driving, whether an event needs review, and what maintenance or cost is coming next.
Compass connects live GPS tracking with trips, alerts, drivers, maintenance, fuel, documents, and fleet-scoped assistance. I work across the product interface, backend services, data model, and the integration of live telemetry into those daily workflows.
My work spans operator dashboards and fleet-management modules, telemetry integration, partner tooling, multi-tenant access, and an assistant grounded in operational data.
Inside Compass Solutions
The key workflows, up close.
Current partner-workspace screens captured in September 2026. Counts, distances, and costs are a snapshot of that workspace, not portfolio performance claims. Fuel estimates remain explicitly labeled in the product.
The live map connects fleet status with the vehicles themselves. Operators can move from the overview into a specific vehicle, inspect its current context, and continue into its recorded activity.
The overview brings distance, alerts, fuel, recent trips, and fleet activity together. The map becomes an entry point into operational work, rather than an isolated display of markers.
The new alert workspace separates items to review, items being handled, completed work, and history. Selecting an incident brings its measured value, rule threshold, time, driver context, and map evidence into a dedicated detail panel.
Taking ownership and resolving an alert are distinct actions. Event-time evidence is also separated from the latest vehicle information, so a current position is not mistaken for the location at the time of the incident.
Maintenance groups work by vehicle and intervention type, with overdue or upcoming thresholds visible in the same row. Operators can move between work to handle, appointments, history and costs, and vehicle service records.
The interface distinguishes a missing starting history from an established service baseline. Dates estimated from recent GPS use remain labeled, and planning actions stay attached to the relevant vehicle.
Fuel review brings consumption, cost, covered distance, and data coverage into one view. The vehicle table supports comparison and drill-down to daily figures, trips, and the map.
A source label explains whether consumption is estimated. That distinction matters: an estimate based on vehicle activity should never be presented as a direct sensor measurement.
The current assistant has a mission workspace for reviewing findings and following their progress. Objectives such as reducing unnecessary idling or understanding prolonged site visits provide a concrete reason to inspect the data.
Coverage and baseline state are visible. An empty queue does not claim that everything is healthy; the interface explains that recent evidence may still be insufficient. Findings retain their source context.
The conversation workspace offers questions about current fleet state, moving vehicles, distance, critical alerts, and comparisons between periods. It gives operators a language-based entry point into the same product domains.
The engineering model uses fleet-specific tools and scoped data access. Answers should come from the operational record, with useful links back into the product, rather than unverified model output.
Behind the interface
Live positions and historical reports have different access patterns. Buffered telemetry and aggregated records support the product without treating every redraw as a full historical query.
Vehicles, drivers, rules, reports, and team actions carry ownership context. Operator and partner surfaces respect that scope at the application and query layers.
Fleet-specific tools connect the assistant to vehicles, trips, alerts, fuel, and maintenance. Source and coverage information make the limits of an answer inspectable.
My work on Compass Solutions
Invoicing & Billing SaaS
Have a product
that needs this kind of care?