ConTrack · Northern Corridor console

12in transit
91%on time
5h 12mavg border dwell
3open alerts
AO
A. Onyango · Ops
MSKU 4028SEAL LOCKED
Mombasa → Kampala · Electronics, Memebox Inc.
PositionNear Naivasha, A104
Next checkpointMalaba OSBP · ETA 21:30
DriverMartin Otieno · ★ 4.9
Last ping2 min ago
On time · sealed At border / dwell Alert
⌕
Tamper
CMAU 2183 · Seal opened outside geofence
12 km past Eldoret weighbridge · 14:22 · GPS + lock event captured for evidence
Dwell SLA
TGHU 7719 · Malaba dwell at 4h 10m of 6h SLA
Customs docs in progress · escalation to clearing agent suggested at 5h
Route
HLXU 5546 · 4 km off planned route near Jinja
Likely diversion at roadworks · rejoining corridor · no seal events

About this prototype

A tracking console concept for ConTrack, the IoT container-security venture I validated with port and customs authorities in Kenya, Egypt and Uganda. It shows how the problems we heard in discovery become product decisions.

  1. No visibility → live seal + GPS telemetry. Every container pings position and lock state on a real map of the corridor; "last ping" is on every card because trust in the data was the first buying question.
  2. Border delays → dwell SLAs, not just dots on a map. Malaba dwell is tracked against a 6-hour SLA with escalation before breach, because authorities buy SLA visibility, not hardware.
  3. Theft → tamper events with geofence context. A seal opened inside a customs geofence is routine; outside one, it is a first-class alert with a dispatch action.
  4. Disputes → an immutable event log. Each consignment carries its gate-out, weighbridge and customs timeline, exportable as evidence, the digital record buyers asked for.
  5. Sell the dashboard, not the lock. The console is the product; the CyLock-style device is the data source underneath, which is how the pitch landed in the real venture.
Read the ConTrack case study → Back to portfolio →