Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
An oil and gas distributor operating a fleet of over 150 tankers. Safety performance mattered commercially and legally.
The available picture of driver behaviour was coarse: a general speed policy applied uniformly, with no reference to the limit actually in force on the stretch of road being driven.
The problem
- Speed compliance was assessed against a blanket policy rather than the posted limit.
- Route-specific restrictions — the ones that exist for a reason on a tanker route — could not be enforced at all.
- Position and speed data were not being captured at a frequency that made behaviour visible.
- There was no basis on which to reward good driving, only to react to incidents.
What we built
An on-vehicle capture device
Single-board computers programmed and installed across the fleet, reporting position and speed every five seconds.
A data path
Pushing that telemetry into telematics and speed-reference services, so each reading could be compared against the limit applicable at that location.
Geofencing for route-specific restrictions
So a lower limit on a particular stretch is enforced as such rather than being invisible.
A dashboard
Presenting driver and vehicle behaviour in a form the operations team could act on.
How we delivered it
- 1
Frame the question first
What “unsafe” means in measurable terms, agreed before any hardware was fitted.
- 2
Prototype on a small number of vehicles
In a lab arrangement with the client's own operations team.
- 3
Prove the data path
Capture frequency, transmission reliability, and the accuracy of limit matching.
- 4
Fit the fleet in stages
With a check that the data from each stage was sound before the next.
- 5
Build the reporting layer
Once the data was trusted, not before.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The device configuration and firmware
- The data pipeline and integration code in their own repository
- The geofence definitions
- The dashboard