Atlas Logistics, 2024
Atlas Fleet
Atlas ran their operation across six browser tabs and a whiteboard. The controllers were brilliant; the tooling was not. This was a project about respecting expertise and getting out of its way.
- Client
- Atlas Logistics
- Year
- 2024
- Discipline
- Internal tooling
- Duration
- 11 weeks
- Role
- Product design, Frontend, Data visualisation
- 240
- Vehicles tracked live
- 2.7m
- Mean time to acknowledge
- 6 → 1
- Tabs per controller
- 40ms
- Telemetry render budget
Telemetry arrived from three incompatible providers at different intervals. Controllers needed one truthful picture, updating live, on screens that stay open for a twelve-hour shift.
How the work was actually done.
Three decisions that shaped the outcome more than anything else on the project.
- 01
Normalise the feed first
An ingestion layer reconciles three telemetry formats into one event stream, with explicit staleness rather than silent gaps. A controller can always tell the difference between 'stopped' and 'not reporting'.
- 02
Design for a twelve-hour stare
Dark by default, low-chroma palette, motion reserved exclusively for genuine state changes. Nothing animates for decoration on a screen someone watches all night.
- 03
Escalate, do not alert
Instead of a wall of notifications, events accumulate into a ranked queue with a clear owner. Alert fatigue was the real bug.
Controllers work from a single screen. Mean time to acknowledge an incident dropped from just over eleven minutes to under three, and the whiteboard came down.
Building something like Atlas Fleet?
Tell me where you are: an idea, a half-finished build, or a product that has outgrown its foundations. The first conversation is free and usually clarifies more than it costs.
- info@angelmaile.com
- Phone
- +27 (0) 71 000 0000
- Studio
- Studio 04, Bree Street, Cape Town
- Hours
- Mon – Fri, 08:30 – 17:30 · SAST (UTC+2)
Replies within one business day. Cape Town, South Africa, SAST (UTC+2).