EQUIPMENT TRACKING · HEAVY EQUIPMENT RENTAL

Count says 90 available units. Real number is 74.

A unit shows on-rent but was returned two days ago and is on the lot. Another shows available but is in the shop with a hydraulic fault. Your utilization KPIs run against a number nobody stands behind. We capture real state from drivers, field techs, and telematics, and write it back to your rental system. Personalized software to run your rental operation.

Runs on Point of Rental, RentalMan, Wynne, MCSExcavators, loaders, aerial lifts, generatorsTrackunit, TrimbleWorks, WhatsApp capturePay only after go-live

THE DISPATCH READINESS GAP

We put an excavator on a truck to a site two hours away that had an open service note from two days prior. The tech messaged it, but nobody connected that message to the dispatch board.

How the night actually went

Day 1 16:30 Field tech messages workshop: EX-50T has a hydraulic fault at Riverside site. Repair pending parts.
Day 1 17:00 Workshop acknowledges on WhatsApp. Rental system still shows EX-50T as Available.
Day 2 08:00 Operations coordinator books EX-50T for a mobilization. Customer contract raised.
Day 2 10:30 Transport truck arrives at yard to collect EX-50T. Driver flags the open service tag.
Day 2 11:15 Coordinator scrambles for a replacement unit. Customer is now waiting. Two-hour delay minimum.
Day 2 14:00 Work order entered from memory. Utilization report for the month still includes EX-50T in available fleet.

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

The off-system gap

Every field fault and return that does not reach your rental management system in real time becomes a hole in the data your branch runs on. Utilization KPIs, hire eligibility, and dispatch readiness are all computed on records filled in hours later, from memory.

Utilization KPIs run against a count nobody can verify

Dispatch runs blind

Your rental system still shows the faulted unit as Available. The coordinator books it for mobilization. The discrepancy surfaces when the transport truck arrives, not when the fault was messaged two days ago.

Customer delay and reputational cost on every mis-dispatch

PM drifts into corrective

When field faults and return inspections are captured as WhatsApp messages instead of structured records, PM schedules drift. Machines go back out with open notes. You pay corrective rates on equipment you should have maintained before it hit the customer site.

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 the channels your branch and field techs already use.

We integrate with the systems you already run. Rental management system (Point of Rental, RentalMan, Wynne, MCS), CMMS (Maximo, SAP PM), telematics (Trackunit, TrimbleWorks), WhatsApp Business, Teams, and your radio transcript source. Nothing for field techs or depot staff to install. Nothing in their workflow changes.

Rental system asset-status update (Point of Rental, RentalMan, Wynne, MCS)
CMMS work-order creation (Maximo, SAP PM, others)
Telematics integration (Trackunit, TrimbleWorks, Cat Product Link)
WhatsApp Business, Teams, radio transcription API
Phase output
LISTEN · DELIVERABLE
Rental system asset-status update (Point of Rental, RentalMan, Wynne, MCS)
LISTEN · ARTIFACT
CMMS work-order creation (Maximo, SAP PM, others)
2
Spec

A working session with the people who run the branch.

Your General Manager, workshop coordinator, and IT walk us through one real dispatch failure. We capture asset classes (excavators, loaders, aerial lifts, generators, compressors), return inspection rules, field fault categories, and the rental system 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 rental system 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, rental system write, CMMS work order, return inspection capture. 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 rental system 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 rental system and CMMS
4
Go-live

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

IT promotes the workflow to production. We run it with you on real dispatches until it produces what we agreed on: captures every field fault and return, updates the rental system, opens the work orders, and keeps hire eligibility honest. You pay only after it goes live and the available count matches the yard.

One-click production deploy, one-click rollback
Run-with-you period on real dispatches
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 dispatches

Rental fleet tracking, on your existing rental management system.

Without Opsima
  • Rental system shows on-rent units that were returned two days ago
  • Available units dispatched with open fault notes from WhatsApp
  • Return inspection faults sit as messages, machine re-booked with pending fault
  • Workshop coordinator manages three simultaneous breakdown calls by phone
  • Utilization KPIs compiled monthly from hire contracts only
  • MTTR per machine class unknown, benchmarking impossible
With Opsima
  • Rental system updated from field tech WhatsApp the moment status changes
  • Open faults visible on fleet board, dispatch flagged until cleared
  • Return inspection captured from technician messages, logged against asset immediately
  • All active field breakdowns visible on one board: tech, location, fault, parts
  • Actual productive hours and downtime tracked from field communication in real time
  • MTTR calculated per asset class continuously from repair communication
<2 min
Rental system updated after field event
0
Manual steps for availability update
100%
Field faults captured before next dispatch

Numbers we have actually measured.

Industry-typical
~60%
Share of fleet status changes in rental operations that never reach the rental system through normal updates
Off-system operational reality observed across heavy equipment rental branches
Industry-typical
2-4 days
Typical lag between a field fault being messaged and a structured record in the rental system
Industry-observed across rental operations with field technician teams
Field-observed
<2 min
Rental system and CMMS updated after a field fault or return is messaged
Field-observed across Opsima rental deployments
Field-observed
0
Manual steps the coordinator takes to update fleet status after a field event
Field-observed across Opsima deployments

Before, and after.

We put an excavator on a truck to a site two hours away that had an open service note from two days prior. The tech messaged it, but nobody connected that message to the dispatch board.

R
Rental Operations Manager
Heavy equipment rental branch

It used to feel like the weather. Some months better, some months worse. Before, I felt it. Now, I know.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving

I'm running three breakdown calls simultaneously on my phone, all different machines, all different customers. There's no board. There's no system. It's all in my head.

W
Workshop Coordinator
Heavy equipment rental operator
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