EQUIPMENT TRACKING · CONSTRUCTION

The lift plan is built on availability confirmed the night before.

A crane develops a hydraulic fault at 08:45. The lift programme was built around it the prior evening. The site manager finds out when the pick fails. Equipment moves between sites with no manifest. Plant utilization is guessed. We capture real state from radio, WhatsApp, and telematics, and write it back to Procore. Personalized software to run your site.

Runs on Procore, Autodesk Build, P6Cranes, excavators, telehandlers, generatorsCat VisionLink, KOMTRAX, WhatsApp capturePay only after go-live

THE LIFT PROGRAMME AT RISK

We had a 14-tonne pick scheduled for 09:00 and found out the mobile crane had a hydraulic snag at 08:45, when the operator radioed the banksman. That pick went to 13:30.

How the night actually went

Day before 18:00 Lift programme built. MC-100T confirmed available verbally at the 17:00 toolbox.
08:30 MC-100T develops a hydraulic fault during warm-up. Operator radios the banksman.
08:45 Banksman calls the site manager. Procore and P6 still show MC-100T as Available.
09:00 Structural steel crew arrives for the scheduled 09:00 pick. Crane is not ready.
09:30 Fitter assessed but the hydraulic part needs to be sourced. ETA unknown. Crew stands down.
13:30 Pick rescheduled. Half-day programme delay. Plant utilization recorded from memory at week end.

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

The off-system gap

Every plant fault and site move that does not reach Procore and your scheduling system in real time becomes a hole in the data your programme runs on. Plant availability, cost-code utilization, and PM scheduling are computed on records filled in hours or days later, from memory.

Programme delay before the site manager hears from a banksman

Dispatch runs blind

Your scheduling system still shows the faulted crane as Available. The programme team allocates resources around an asset that cannot deliver. The impact on the programme is discovered at the lift, not at the fault.

Cascading programme delay and subcontractor standing-down costs

PM drifts into corrective

Pre-use inspection defects captured as WhatsApp photos never become structured records. Machines return to work with unresolved faults. PM schedules drift and deferred work turns into the next breakdown on a critical lift day.

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 site already runs on.

We integrate with the systems you already run. Procore, Autodesk Build, your scheduling system (P6, MS Project), CMMS (Maximo, SAP PM), telematics (Cat VisionLink, Komatsu KOMTRAX), WhatsApp Business, Teams, and your radio transcript source. Nothing for foremen or plant operators to install. Nothing in their workflow changes.

Procore and Autodesk Build plant record update
CMMS work-order creation (Maximo, SAP PM, others)
Telematics integration (Cat VisionLink, KOMTRAX, Volvo Active Care)
WhatsApp Business, foreman Teams, radio transcription API
Phase output
LISTEN · DELIVERABLE
Procore and Autodesk Build plant record update
LISTEN · ARTIFACT
CMMS work-order creation (Maximo, SAP PM, others)
2
Spec

A working session with the people who run the site.

Your Construction Superintendent, plant manager, and IT walk us through one real programme-impacting breakdown. We capture asset classes (cranes, excavators, telehandlers, concrete pumps, generators), pre-use inspection rules, multi-site transfer rules, and the Procore 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, inspection rules, and Procore 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, Procore write, CMMS work order, multi-site plant tracking. 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 Procore 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 Procore 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 site shifts until it produces what we agreed on: captures every plant fault and site move, updates Procore and the schedule, opens the work orders, and keeps cost-code utilization honest. You pay only after it goes live and the programme team can see plant reality before the morning stand-up.

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

Plant equipment tracking, on your existing Procore and CMMS.

Without Opsima
  • Lift programme built on plant availability confirmed verbally the night before
  • Crane fault discovered when the pick is already scheduled and crew standing by
  • Equipment moves site-to-site with no manifest update in Procore
  • Pre-use inspection defects as photos in a WhatsApp group, never actioned
  • Plant utilization for cost-code reporting guessed from hire invoices
  • Maintenance records entered at week end from memory and paper forms
With Opsima
  • Procore plant records updated from radio and foreman WhatsApp in real time
  • Programme team sees fault the moment it is radioed, before the crew assembles
  • Every site-to-site move captured with status and open faults following the machine
  • Inspection defects captured as structured records, tracked and signed off
  • Actual productive hours and downtime tracked from field communication continuously
  • Work orders structured from plant operator and fitter messages at time of event
<2 min
Procore updated after plant fault
0
Manual steps for programme team
100%
Site plant events captured with timestamp

Numbers we have actually measured.

Industry-typical
~60%
Share of plant status changes on construction sites that never reach the project management system in real time
Off-system operational reality observed across construction site operations
Industry-typical
Half-day
Typical programme impact when a crane or excavator fault is not communicated to the scheduling team before crew mobilization
Industry-observed across construction operations with lift-critical plant
Field-observed
<2 min
Procore and CMMS updated after a plant fault is radioed or messaged from site
Field-observed across Opsima construction deployments
Field-observed
0
Manual steps the site manager takes to update plant status after a field event
Field-observed across Opsima deployments

Before, and after.

We had a 14-tonne pick scheduled for 09:00 and found out the mobile crane had a hydraulic snag at 08:45, when the operator radioed the banksman. That pick went to 13:30.

S
Site Manager
Construction project

We redeployed an excavator from Site A to Site B and found out on arrival it had been waiting on a replacement track adjuster since Tuesday. Nobody told us.

P
Project Director
Construction programme

Since launching, I no longer tell the site manager last week you were missing 30 hours of output. I tell him yesterday you were missing half an hour of output.

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