Mining runs 12-hour shifts on remote sites. At crew change, the outgoing foreman transfers knowledge in five minutes or not at all. The incoming foreman reconstructs for 45 minutes before any decision is made. Opsima captures shift state from radio and WhatsApp and delivers the brief before the incoming shift boards. Personalized software to run your mine.
THE CREW-CHANGE GAP
We lose the first 45 minutes of every shift to equipment verification. In remote ops, that's two production cycles gone.
How the night actually went
Where the work goes
Night-shift repairs, drill status changes, and deferred items never reach SAP and the fleet system before crew change. The incoming foreman inherits a stale picture and rebuilds it from radio calls, not from data.
45 minutes of reconstruction before a single production decisionYour fleet system still shows the broken haul truck as active because the status was never updated after the night breakdown. Dispatch allocates loads to it. The correction comes from the operator, not from the system.
Two production cycles lost before the pit picture is accurateWhen the CMMS has no record of a deferred service from last shift, the PM schedule treats the machine as on track. Deferred work accumulates across crew changes and surfaces as the next unplanned breakdown during a peak production window.
Deferred maintenance compounds invisibly across 12-hour shiftsHow we build it with you
We integrate with the systems your mine already runs. CMMS (SAP PM, Maximo, MainPac, Pronto), your fleet or dispatch system (Modular Mining DISPATCH, Wenco, Hexagon), WhatsApp, Teams, and your radio transcript source. Nothing for operators, fitters, or foremen to install. Nothing in the crew-change routine changes.
Your shift foreman, maintenance planner, and IT walk us through one real crew change. We capture what the incoming foreman needs to know: haul truck and drill states, in-progress repairs, parts on order, deferred maintenance, and the SAP and fleet-system fields that need to reflect reality before the bus arrives. The workflow is sketched in their words, then turned into a structured spec and a mockup you can read before any code is written.
The crew-change workflow is built end to end in a staging environment connected to your real systems. Ingest, classification, SAP write, fleet system status update, and crew-change brief generation. Your IT reads the codebase, the integrations, and the risk report before anything touches production. No black box.
IT promotes the workflow to production. We run it with you on real shifts until it produces what we agreed on: captures the crew-change state, updates SAP and the fleet system, and delivers the brief before the incoming foreman boards the bus. You pay only after it goes live and the crew-change brief on real shifts matches the spec.
Before & After
From the field
The conversations we hear
It was very difficult to get the real operational picture. It used to feel like the weather. Some months better, some months worse. Before, I felt it. Now, I know.
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.
No one needs to feed the system. It feeds itself.
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.