Oriental Nippon Development
Back to portfolio
Case studyOil & gas distributor

Edge Telematics and Speed-Limit-Aware Safety Scoring for 150+ Tankers

Driver speed was judged against a blanket policy, not the road's posted limit. We fitted on-vehicle edge devices reporting every five seconds and matched every reading against the limit in force at that place and time.

Industry
Transportation & Logistics
Region
United States
Engagement
R&D Lab (joint innovation)

Outcomes

  • 150+ tankers instrumented
  • 5-second telemetry
  • Recognition for safe drivers

Stack

Raspberry Pi · Python · Telematics APIs · Geofencing · Dashboards

Written byOriental Nippon Team

A US oil and gas distributor runs a fleet of more than 150 tankers. Safety matters to it commercially and legally, but its picture of driver behaviour was coarse: one general speed policy, with no reference to the limit on the road actually being driven.

It wanted to hold drivers to real road limits, and to be able to recognise good driving, not just react to incidents.

The problem

  • Blanket policy. Speed was judged against a general rule, not the posted limit.
  • No route rules. Lower limits on specific stretches could not be enforced.
  • Low-resolution data. Position and speed were not captured often enough to see behaviour.
  • Punish-only. There was no basis for rewarding good driving.
BeforeAfter
Fleet covered150+ tankers150+ tankers, fitted
Data frequencyCoarsePosition and speed every 5 seconds
Speed referenceOne general policyLimit in force at that location
Route restrictionsNot enforceableGeofenced

What we built

  • On-vehicle devices

    Raspberry Pi units across the fleet, reporting position and speed every five seconds.

  • A data path

    Telemetry pushed into telematics and speed-reference services, so each reading is compared with the limit at that exact location.

  • Geofencing

    Route-specific restrictions enforced as their own limits.

  • A dashboard

    Driver and vehicle behaviour in a form operations can act on.

Every five seconds, for every tanker:

Technology and the role it played

TechnologyRole in this project
Raspberry PiOn-vehicle capture devices
PythonDevice software and the data pipeline
Telematics and speed-reference APIsMatching each reading to the posted limit
GeofencingRoute-specific restrictions
DashboardsDriver, vehicle and route views for operations

How we delivered it

Our R&D lab worked with the client's operations team to define "unsafe" in measurable terms before any hardware was fitted.

  1. Frame the question. Measures and success threshold.
  2. Prototype. Devices on a handful of vehicles.
  3. Prove the data path. Capture frequency, transmission reliability and accuracy of limit matching.
  4. Fit the fleet in stages. Validating each stage's data before the next.
  5. Build reporting. Only once the data was trusted.
Delivery timelineIndicative total: 15–23 weeks
  1. 01Framing

    1–2 wks

    Definition of the measures, success threshold

  2. 02Prototype

    3–4 wks

    Devices on a handful of vehicles, data path proven

  3. 03Geofencing and limit matching

    2–3 wks

    Route restrictions, reference-data integration

  4. 04Fleet fitting

    6–10 wks

    Staged installation with per-stage data validation

  5. 05Dashboard

    3–4 wks

    Operations reporting, driver and route views

Risks and how we handled them

RiskHow we handled it
Unclear definition of unsafeMeasures and thresholds agreed before fitting hardware
Unreliable data from the roadData path proven on a handful of vehicles first
Problems multiplied across 150+ vehiclesStaged fitting with data validated at each stage
A system drivers resentDesigned to recognise good driving as well as poor

Outcome

The distributor can measure safety against the limit that actually applied at that time and place, including route restrictions, and use the same basis to recognise good driving as well as address poor driving.

Recognising good driving is what the client wanted the system for. A monitoring system that can only punish rarely survives contact with a workforce.

What the client keeps

  • Device configuration and firmware
  • Pipeline and integration code, in their own repository
  • Geofence definitions
  • The dashboard

Sources and further reading

  1. Speeding, NHTSA
  2. Raspberry Pi documentation, Raspberry Pi

Facing something similar? This is the kind of work our Software Engineering & Cloud team delivers every day. Talk to us about your stack.