SHIFT HANDOVER · HEAVY INDUSTRY

The incoming shift knows before they clock in.

Shift handover is a 5-minute verbal briefing, a WhatsApp thread, and whatever the supervisor remembers. The incoming shift spends 30-60 minutes rediscovering state. Opsima captures open exceptions, in-progress jobs, and equipment status into your CMMS and delivers the brief before the crew arrives. Personalized software to run your operations.

Runs on your existing CMMSWhatsApp + Teams + radio captureLive in weeks, not quartersPay only after go-live

THE FIRST THIRTY MINUTES

The first 30 minutes of every shift are decisions made on assumptions. I don't know what's actually available until I've walked the floor.

How the night actually went

06:00 Incoming supervisor clocks in. Outgoing supervisor is already heading to the car park.
06:05 WhatsApp thread has 47 messages from the night shift. Three separate issues, partially resolved. No summary.
06:12 Ops system shows 12 units as Available. The supervisor knows from experience that two are not.
06:20 Work order for Unit 204 is not in the CMMS yet. Repair started at 03:00, parts on order.
06:35 Dispatch allocates a load to Unit 204. Operator calls it in. Supervisor now knows.
06:55 Planning re-runs with accurate state. Fifty-five minutes after shift start, the supervisor has the full picture.

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

The off-system gap

About 60% of operational reality never reaches the system of record. In-progress repairs, parts on order, deferred jobs, and equipment quirks live in WhatsApp threads and the outgoing supervisor's head, not in your CMMS.

The incoming shift starts blind every single handover

Dispatch runs blind

Your ops system shows units as Available because the status was never updated during the night shift. Dispatch allocates work to equipment that is waiting on parts. The correction happens by phone call, not by system.

30-60 minutes of reactive firefighting at every shift start

PM drifts into corrective

Deferred maintenance from one shift accumulates invisibly into the next. When the CMMS has no record of the deferral, PM schedules drift and untracked deferred work becomes the next unplanned breakdown.

Deferred work compounds silently across shifts

From radio call to live in your system, without a 14-month IT project.

1
Listen

Connect to the channels your shift already uses.

We integrate with the systems you already run. CMMS (SAP PM, Maximo, HxGN EAM, or your own), your ops system, WhatsApp, Teams, and your radio transcript source. Nothing for operators or supervisors to install. Nothing in their handover routine changes.

CMMS work-order and status read/write (SAP PM, Maximo, HxGN EAM, others)
Ops system unit-status update
WhatsApp Business, Teams, Slack, SMS ingest
Radio transcription API
Phase output
LISTEN · DELIVERABLE
CMMS work-order and status read/write (SAP PM, Maximo, HxGN EAM, others)
LISTEN · ARTIFACT
Ops system unit-status update
2
Spec

A working session with the people who run the shift.

Your shift superintendent, maintenance planner, and IT walk us through one real handover. We capture what the incoming supervisor needs to know: equipment states, open exceptions, in-progress jobs, deferred items, and parts on order. 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
Handover data model, escalation rules, and CMMS 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 handover workflow is built end to end in a staging environment connected to your real systems. Ingest, classification, CMMS write, ops status update, and shift brief generation. 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 ops system
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 ops system
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 it produces what we agreed on: captures the handover state, updates the CMMS, and delivers the shift brief before the incoming supervisor clocks in. You pay only after it goes live and the handover brief on real shifts matches the spec.

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

Shift handover, on your existing stack.

Without Opsima
  • Outgoing supervisor debrief is verbal, partial, and already walking out the door
  • Night-shift WhatsApp threads have 30-50 messages with no structured summary
  • In-progress repairs not in the CMMS, ops system shows wrong unit status
  • Incoming supervisor spends 30-60 minutes reconstructing actual fleet state
  • Dispatch allocates to unavailable units, corrections handled by phone
  • Deferred maintenance accumulates silently across shifts with no CMMS record
With Opsima
  • Structured shift brief delivered before incoming supervisor clocks in
  • Open exceptions, in-progress jobs, and parts-on-order captured from WhatsApp and radio
  • CMMS work orders updated with correct timestamps and status before shift start
  • Ops system unit status reflects actual state before dispatch re-runs
  • Incoming supervisor starts the shift with the full picture, not a reconstruction
  • Deferred maintenance tracked in CMMS with reason and deferral timestamp
<3 min
Full handover brief generated
0
Knowledge gaps at shift start
100%
Open exceptions captured

Numbers we have actually measured.

Industry-typical
30-60 min
Typical time an incoming supervisor spends reconstructing shift state before making decisions
Observed across heavy-industry shift handover operations
Industry-typical
~60%
Share of operational reality that never reaches the system of record after a shift
Off-system pain wedge, observed across heavy-industry operations
Field-observed
<3 min
Time to deliver a structured shift brief to the incoming supervisor, on the agreed spec
Field-observed across Opsima deployments
Field-observed
0
Manual steps the outgoing supervisor takes to generate the handover brief
Field-observed across Opsima deployments

Before, and after.

It was very difficult to get the real operational picture. Before, I felt it. Now, I know.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving

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.

C
COO
Container Terminal

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

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