At handover, the outgoing supervisor knows which cranes are mid-repair, which parts are on order, and which deferrals need watching. The incoming shift finds out by walking the yard. Opsima captures terminal state and delivers the brief before the crew clocks in, on your existing Navis, SAP, and CMMS. Personalized software to run your terminal.
THE SHIFT CHANGE GAP
The incoming shift supervisor spends the first 30 minutes of every shift figuring out what's actually available. That's 30 minutes of decisions made on assumptions.
How the night actually went
Where the work goes
Night-shift repairs, deferred maintenance, and parts-on-order events never reach SAP or Navis before the day shift starts. The incoming superintendent inherits a false picture of terminal availability and spends the first 30 minutes correcting it.
Up to 40-60% of shift events filled in from memory, hours laterNavis shows the RTG or STS as Available because the status was never updated during the night repair. The gang planner allocates the next move to it. The correction arrives via radio call, not via TOS.
Yard delay cascades until status is corrected manuallyDeferred maintenance from one shift accumulates without a CMMS record. When the PM plan does not know a service was deferred three shifts ago, it schedules the next PM against stale data and the crane fails before the next planned maintenance window.
Deferred items compound silently, corrective rates followHow we build it with you
We integrate with the systems your terminal already runs. CMMS (SAP PM, Maximo, AMOS, MainPac), your TOS (Navis N4, Mainsail, OPUS Terminal), WhatsApp Business, Teams, and your radio transcript source. Nothing for operators, mechanics, or supervisors to install. Nothing in the handover routine changes.
Your shift superintendent, gang planner, and IT walk us through one real handover. We capture what the incoming supervisor needs: crane states, in-progress repairs, parts on order, deferred maintenance, and the Navis and SAP fields that need to reflect reality before the day shift starts. 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 handover workflow is built end to end in a staging environment connected to your real systems. Ingest, classification, SAP write, Navis status update, and shift 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 terminal handover state, updates SAP and Navis, and delivers the shift brief before the superintendent clocks in. You pay only after it goes live and the handover brief on real shifts matches the spec.
Before & After
From the field
The conversations we hear
It wasn't like we had to spend a lot of time educating you on our industry.
The incoming shift supervisor spends the first 30 minutes of every shift figuring out what's actually available. That's 30 minutes of decisions made on assumptions.
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.
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.