EQUIPMENT TRACKING · LOGISTICS AND TRANSPORTATION

Dispatch assigns loads to tractors that broke down an hour ago.

Your TMS shows a tractor as available. Your dispatcher assigns a load. The tractor broke down 40 minutes ago and the radio call never reached the system. Trailer returns go through night yard radio and the count is 12 off. We capture the real state from radio, WhatsApp, and telematics, and write it back to your TMS. Personalized software to run your fleet.

Runs on your existing TMS and YMSTractors, trailers, chassis, containersSamsara, Motive, radio, WhatsApp capturePay only after go-live

THE MORNING DISPATCH CHAOS

The biggest source of morning chaos is equipment that broke down overnight and never made it into the dispatch board. The radio call existed. The record did not.

How the night actually went

23:00 Yard truck YT-04 breaks down on the back row. Operator radios in: left air bag blown.
23:09 Night yard tech acknowledges on radio. Starts to source parts. No update reaches the TMS.
07:00 Morning dispatcher opens the board. YT-04 still shows as Available. Load assigned.
07:20 Driver walks to YT-04. Finds it tagged out at the back row. Returns to dispatch.
07:35 Load delayed. Dispatcher scrambles for an alternative power unit. Customer clock starts.
08:10 Work order eventually entered from memory. Parts ETA unknown. Fleet manager finds out in the stand-up.

What slips when the radio knows and SAP doesn't.

The off-system gap

Every breakdown and return check-in that does not reach your TMS in real time becomes a hole in the data your dispatch team runs on. Available tractors, trailer counts, and chassis status are all computed on records that are hours out of date.

Dispatch runs on a count nobody can verify at 07:00

Dispatch runs blind

Your TMS still shows the broken tractor as Available. The dispatcher assigns the next load to it. The discrepancy surfaces when a driver walks back empty-handed, not when the tractor went down.

Load delay and customer impact before the dispatcher knows

The trailer count is always wrong

Return check-ins happen over yard radio and driver WhatsApp. They never reach the TMS until someone manually enters them. The trailer pool count your dispatch board shows is never the number sitting in the yard.

12-plus trailer discrepancy typical on busy return yards

From radio call to live in your system, without a 14-month IT project.

1
Listen

Connect to the channels your yard and fleet already use.

We integrate with the systems you already run. TMS (Manhattan TMS, Oracle TMS, MercuryGate), your YMS (Kaleris, Navis eModal), CMMS (Maximo, SAP PM), telematics (Samsara, Motive), WhatsApp Business, Teams, and your radio transcript source. Nothing for drivers or yard operators to install. Nothing in their workflow changes.

TMS and YMS asset-status update (Manhattan, Oracle, MercuryGate, Kaleris)
CMMS work-order creation (Maximo, SAP PM, others)
Telematics integration (Samsara, Motive, and others)
WhatsApp Business, Teams, driver SMS, radio transcription API
Phase output
LISTEN · DELIVERABLE
TMS and YMS asset-status update (Manhattan, Oracle, MercuryGate, Kaleris)
LISTEN · ARTIFACT
CMMS work-order creation (Maximo, SAP PM, others)
2
Spec

A working session with the people who run the yard.

Your fleet manager, head of dispatch, and IT walk us through one real overnight breakdown. We capture asset classes (tractors, trailers, chassis, yard trucks), fault categories, return check-in rules, and the TMS fields you need updated. The workflow is sketched in their words, then turned into a structured spec and a mockup you can read before any code is written.

Structured working session, no IT ticket required
Spec + mockup written from your team's own language
Asset classification, return rules, and TMS field map captured
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
Spec + mockup written from your team's own language
3
Build

Real code, in staging, on your data.

The workflow is built end to end in a staging environment connected to your real systems. Ingest, classification, TMS write, CMMS work order, trailer count reconciliation. Your IT reads the codebase, the integrations, and the risk report before anything touches production. No black box.

Real code, any language, no complexity ceiling
Staging connected to your real TMS and CMMS
Codebase, risk report, and rollback handed to IT to review
Phase output
BUILD · DELIVERABLE
Real code, any language, no complexity ceiling
BUILD · ARTIFACT
Staging connected to your real TMS and CMMS
4
Go-live

IT deploys. We run it with you on real shifts.

IT promotes the workflow to production. We run it with you on real shifts until it produces what we agreed on: captures overnight breakdowns, updates the TMS before the morning dispatcher opens the board, reconciles trailer returns, and keeps the count accurate. You pay only after it goes live and the dispatch board matches reality.

One-click production deploy, one-click rollback
Run-with-you period on real shifts
Payment after the workflow produces the agreed outcome
Phase output
GO-LIVE · DELIVERABLE
One-click production deploy, one-click rollback
GO-LIVE · ARTIFACT
Run-with-you period on real shifts

Fleet equipment tracking, on your existing TMS and CMMS.

Without Opsima
  • TMS shows broken tractors as Available at 07:00 dispatch start
  • Overnight breakdowns surface when a driver walks back empty-handed
  • Trailer return check-ins via radio, count is 10-15 off by morning
  • CMMS work orders entered manually, hours after the event
  • Chassis deferred for brake inspection still in available pool
  • Fleet manager finds out at the stand-up, not at the breakdown
With Opsima
  • TMS updated from radio and WhatsApp the moment a breakdown is called
  • Morning dispatcher opens a board that matches the real yard at shift start
  • Trailer return check-ins captured in real time, pool count always current
  • CMMS work order opened automatically with correct timestamps and fault
  • Chassis with open defects flagged out of available pool immediately
  • Fleet manager sees every breakdown, every open repair, on one screen
<4 min
TMS updated after breakdown
0
Manual steps for dispatch board update
100%
Overnight events visible at shift start

Numbers we have actually measured.

Industry-typical
~60%
Share of fleet status changes that never reach the TMS through normal system updates
Off-system operational reality observed across logistics and transportation yards
Industry-typical
8-12 hrs
Typical gap between an overnight breakdown and a structured work order in the CMMS
Industry-observed across transportation and logistics fleet operations
Field-observed
<4 min
TMS power unit status updated after a breakdown is radioed or messaged
Field-observed across Opsima fleet deployments
Field-observed
0
Manual steps the dispatcher takes to keep the board current after a field event
Field-observed across Opsima deployments

Before, and after.

The biggest source of morning chaos is equipment that broke down overnight and never made it into the dispatch board. The radio call existed. The record didn't.

F
Fleet Manager
Logistics operator

We sent a driver 40 miles to pick up a chassis that was deferred for a brake inspection. Nobody updated the system. The radio call was the system.

Y
Yard Operations Manager
Regional freight yard

One person tells me 90 tractors are ready. Another says 100. I'm making dispatch allocations on a number nobody can verify in real time.

T
Terminal Operations Manager
Container terminal
Working session

Your operation.
Your real data.
Software built for it.

Tell us one process you have given up on fixing. We build it on your actual systems and run it with you. You pay only after it goes live.

On your existing stack
Live in weeks, not quarters
Pay only after go-live
Built and run for you