EQUIPMENT TRACKING · MINING & QUARRY

Available on paper, idle on the ground.

Your system says the excavator is available. The site manager knows it has been waiting on a fuel truck for thirty minutes. That gap, repeated every shift, is where output disappears. We capture real fleet state from WhatsApp, radio, and your GPS, and write it back to your CMMS. No new forms for the field. Personalized software to run your operations.

Runs on your existing CMMSWhatsApp + radio + GPS captureNo new forms for the fieldPay only after go-live

THE IDLE MACHINE

It used to feel like the weather. Some months better, some months worse. I couldn't tell you why.

How the night actually went

07:00 Shift plan shows all 14 excavators operating. CMMS availability: 100%.
07:10 EX-07 waiting on fuel at Bench 3. Operator messages the supervisor on WhatsApp.
07:30 CMMS still shows EX-07 as Operating. Shift output figure looks normal.
09:00 Shift review: production is down. Nobody knows exactly when it dropped or which machines contributed.
16:00 End of day. Site manager fills in CMMS utilization from memory. Idle events not logged.
16:30 Deputy CEO reviews monthly report. Availability looks fine. Output is missing. No explanation in the data.

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

The off-system gap

Machine state changes on the bench every few minutes. WhatsApp and radio know. The CMMS finds out at shift end, if at all. Every utilization figure and PM schedule is built on data that is hours out of date.

Utilization figures filled in from memory, not from events

Dispatch runs blind

Your ops system shows machines as Available that are waiting on fuel, a parts delivery, or an operator. Shift planners route work to them, then handle the exception by phone. Output loss accumulates silently.

Idle time invisible until the output gap appears in the report

PM drifts into corrective

When operating hours are filled in from estimates, PM intervals drift. Machines hit corrective events before the scheduled service. You pay breakdown rates on equipment that was due for maintenance two weeks ago.

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 how your field already communicates.

We integrate with the systems your operation already runs. CMMS (SAP PM, Maximo, HxGN EAM, or your own), WhatsApp Business, Teams, radio transcript, and your existing GPS feeds. No new app for operators. No new form for the site manager. The field keeps working exactly as it does today.

CMMS state-event and work-order write (SAP PM, Maximo, HxGN EAM, others)
WhatsApp Business, Teams, radio transcript ingest
GPS/IoT feed integration for location-correlated state
Shift reporting feed
Phase output
LISTEN · DELIVERABLE
CMMS state-event and work-order write (SAP PM, Maximo, HxGN EAM, others)
LISTEN · ARTIFACT
WhatsApp Business, Teams, radio transcript ingest
2
Spec

A working session with the people who run the shift.

Your deputy CEO, site manager, and maintenance lead walk us through one real shift. We capture machine classes, state categories (Operating, Idle, Waiting, Under Maintenance, Out-of-Service), delay reason codes, and the CMMS fields that need to stay 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 delay-reason taxonomy captured
Spec + mockup written from your operation's own language
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
State-transition rules and delay-reason taxonomy 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 WhatsApp, radio, and GPS, state classification, CMMS write, and shift-output reporting. 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 GPS feeds
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 GPS feeds
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 availability figure in your CMMS matches what the site manager sees on the ground. You pay only after it goes live and the tracking produces what we agreed on.

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 comms.

Without Opsima
  • Machine state changes captured verbally, never written to the CMMS
  • Idle events invisible until the output gap appears in the weekly report
  • CMMS utilization figures filled in from memory at shift end
  • PM schedule runs on estimated hours, not actual operating time
  • Deputy CEO reviews availability figures that do not reflect what happened on the bench
  • Corrective breakdowns on machines that were due for service weeks ago
With Opsima
  • Real machine state captured from WhatsApp, radio, and GPS in real time
  • Idle events logged with reason code within minutes of occurrence
  • CMMS utilization figures built on timestamped state events, not memory
  • PM schedule runs on actual operating hours, zero manual entry
  • Deputy CEO sees today's availability, not last month's guess
  • All machines on-time PM, zero deferred until the next breakdown
Real-time
Fleet availability per machine
0
New forms for the field
Daily
Output gap visibility, not monthly

Numbers we have actually measured.

Taavura
Fifteen minutes of delay sounds like nothing
Over a year, that is hundreds of thousands of cubic meters of lost output
Taavura Earth Moving Division · Hagai Shenar, Deputy CEO
Taavura
Monthly to daily
Granularity of shift-start delay tracking, post-deployment at Taavura
Taavura Earth Moving Division · qualitative outcome
Industry-typical
~60%
Share of machine state changes that never reach the CMMS on the shift they happen
Off-system operational reality, observed across earth-moving operations
Field-observed
0
New forms or workflow changes required for field operators after go-live
Field-observed across Opsima equipment-tracking deployments

Before, and after.

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

Fifteen minutes of delay sounds like nothing, but over a year, that's hundreds of thousands of cubic meters.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving Division

No one needs to feed the system. It feeds itself.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving Division
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