EQUIPMENT TRACKING · HEAVY INDUSTRY

The count in your system is never the real number.

Your CMMS says 90 units available. The real number is 74. Available units are in the shop, in-use units are idle, and GPS gives location but not state. We capture real asset state from radio, WhatsApp, mechanic reports, and your GPS and RFID feeds, and write it back to your CMMS and ops system. Personalized software to run your operations.

Runs on your existing CMMSRadio + WhatsApp + GPS + RFIDLive in weeks, not quartersPay only after go-live

THE COUNT PROBLEM

One person tells me 90 units are ready. Another says 74. I'm allocating equipment on a number nobody can verify in real time.

How the night actually went

06:00 Shift starts. Planner pulls up fleet count in CMMS: 90 units available.
06:15 Unit 22 pulled to workshop, left rear axle fault. Mechanic tells the supervisor verbally.
06:22 CMMS still shows Unit 22 as Available. Planner dispatches two more loads to it.
07:00 Three units waiting on a machine that is not moving. Output gap starts accumulating.
08:30 Supervisor notices the backlog, calls workshop. Unit 22 has been in the shop since 06:15.
09:00 Planner corrects the CMMS manually. Real fleet count: 74. Morning plan reruns from scratch.

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

The off-system gap

When a unit changes state, the radio and WhatsApp know first. The CMMS finds out hours later, if at all. Every availability figure, MTBF calculation, and PM schedule is built on a count that lags reality.

Availability figures computed on data that is hours out of date

Dispatch runs blind

Your ops system shows units as Available that are in the shop or sitting idle. Dispatch routes work to them, the planner handles exceptions by hand, and nobody corrects the record until the next shift review.

Cascading delay every time status lags behind reality

PM drifts into corrective

When unit hours and condition data are filled in from memory at shift end, the PM schedule runs on bad inputs. Deferred work accumulates silently until the next breakdown. You pay corrective rates on units you should have maintained.

Corrective costs run several times planned maintenance

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

1
Listen

Connect to every channel that knows the real unit state.

We integrate with the systems you already run. CMMS (SAP PM, Maximo, HxGN EAM, or your own), your ops system, WhatsApp, Teams, radio transcript, and your existing GPS and RFID feeds. Nothing for operators or mechanics to install. The field keeps working exactly as it does today.

CMMS status and work-order write (SAP PM, Maximo, HxGN EAM, others)
Ops system availability count update
WhatsApp Business, Teams, radio transcript ingest
GPS/IoT and RFID feed integration
Phase output
LISTEN · DELIVERABLE
CMMS status and work-order write (SAP PM, Maximo, HxGN EAM, others)
LISTEN · ARTIFACT
Ops system availability count update
2
Spec

A working session with the people who run the fleet.

Your fleet manager, maintenance lead, and planner walk us through one real unit status change. We capture equipment classes, state transitions, the rules for Available vs. In-Use vs. Under-Maintenance vs. Out-of-Service, and the CMMS and ops fields that need to be kept current. 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
State-transition rules and CMMS field map captured
Spec + mockup written from your team's own language
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
State-transition rules and CMMS field map captured
3
Build

Real code, in staging, on your data.

The tracking workflow is built end to end in a staging environment connected to your real systems. Ingest from every channel, state classification, CMMS write, ops system count update, and alert routing. 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 CMMS and ops system
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 CMMS and ops system
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 the fleet count in your system matches the count on the ground. You pay only after it goes live and the availability numbers on real shifts match the spec.

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

Equipment tracking, on your existing CMMS and ops system.

Without Opsima
  • Fleet count in CMMS lags reality by hours every shift
  • Unit state changes captured verbally, never written back to the system
  • Dispatch routes work to units that are in the shop or idle
  • Availability figures built on memory and manual corrections
  • PM schedule runs on unit hours filled in from shift notes
  • MTBF and MTTR corrupted by late and missing records
With Opsima
  • Real unit state captured from radio, WhatsApp, GPS, and RFID in real time
  • CMMS status updated automatically within minutes of a state change
  • Ops system fleet count matches the ground count at all times
  • Planner allocates to real availability, not last-shift memory
  • PM schedule runs on actual unit hours, zero manual entry
  • MTBF and MTTR computed on complete, timestamped records
Real-time
Fleet availability count
0
Manual status corrections
100%
State changes captured

Numbers we have actually measured.

Industry-typical
~60%
Share of unit state changes that never reach the CMMS on the shift they happen
Off-system operational reality, observed across heavy-industry fleet operations
Industry-typical
3-5 hrs
Typical lag between a unit going offline and a CMMS record being created
Industry-observed across heavy-industry shift operations
PNCT
Count says 90, real number is 74
Live fleet count vs. what the system of record shows, on a real shift
PNCT container terminal field deployment
Field-observed
0
Manual steps the planner takes to correct the fleet count after go-live
Field-observed across Opsima equipment-tracking deployments

Before, and after.

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

T
Terminal Operations Manager
Container terminal

It's not enough that a machine is available. It's important to me that it's actually working.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving Division

Opsima eliminated the disconnect between our maintenance and operations teams. We went from Excel chaos to real-time clarity in weeks. The availability increase paid for itself in the first quarter.

D
Director of Equipment Services
Major US 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