BREAKDOWN RESPONSE · PORTS & TERMINALS · NIGHT SHIFT

Crane breakdown response that starts at the radio call.

At 02:00, an STS crane stops mid-move. The status lives on a radio channel and a WhatsApp thread for three to five hours before a work order opens. We capture it the moment it happens, on your existing SAP PM and Navis, and run the response with you.

Runs on your SAP PMRuns on your Navis N4WhatsApp + Teams + radio capturePay only after go-live

THE NIGHT IT BROKE

The radio knew at 02:00. SAP knew at 05:30. In between, we kept dispatching boxes to a crane that wasn't there.

How the night actually went

02:00 STS 4 stops mid-move. Operator radios in: hydraulic warning, no boom.
02:03 Supervisor opens a WhatsApp thread with maintenance. Three people respond, two are off-shift.
02:14 TOS still shows STS 4 as Available. Slot planner dispatches the next move to it.
02:30 Yard jams as the move queues behind a crane that isn't moving. Reach-stackers idle.
03:45 On-call maintenance reached via phone chain. ETA 50 minutes.
05:30 Day-shift planner opens SAP. The work order is created from memory, fault code best-guess.

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

The off-system gap

Every night shift breakdown that doesn't reach SAP in real time becomes a hole in the data you run the terminal from. MTBF, availability, and PM scheduling are computed on records that were filled in hours later, from memory.

Up to 40-60% of night-shift events filled in from memory

Slot planning runs blind

Navis or your TOS still shows the broken crane as Available. The TOS dispatches the next move to it. The planner handles exceptions by hand, without knowing that the crane is the exception.

Cascading yard delay until status is corrected manually

Preventive maintenance turns corrective

PM only works on time. When breakdowns are logged hours late, the PM plan drifts behind schedule and deferred work slips into the next breakdown. Now you are paying corrective rates on a machine you should have been maintaining.

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 shift already uses.

We integrate with the systems your terminal already runs on: SAP PM, Navis N4, WhatsApp Business, Microsoft Teams, and your radio transcript source. Nothing for operators or mechanics to install. Nothing in their workflow changes.

SAP PM / IBM Maximo work-order creation
Navis N4 unit-status update
WhatsApp Business, Teams, Slack, SMS ingest
Radio transcription API
Phase output
LISTEN · DELIVERABLE
SAP PM / IBM Maximo work-order creation
LISTEN · ARTIFACT
Navis N4 unit-status update
2
Spec

A working session with the people who run the shift.

Your night-shift supervisor, maintenance planner, and IT lead walk us through one real breakdown. We capture equipment classes, severity rules, escalation paths, and the SAP fields you need populated. 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 shift's own language
Severity rules, escalation rules, and SAP field map captured
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
Spec + mockup written from your shift'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, SAP write, Navis status, dispatch logic. 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 SAP + Navis
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 SAP + Navis
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 breakdowns, opens the work orders, updates the TOS, and dispatches the crews. You pay only after it goes live and the response time 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

Night-shift breakdown response, on your existing stack.

Without Opsima
  • Radio and WhatsApp report captured by nobody until day shift
  • SAP PM order created three to five hours later, from memory
  • Navis shows the broken crane as Available, slot chaos follows
  • Maintenance crew tracked down via phone chain, sixty-plus minutes
  • No reserve allocated, the next move waits on a dead unit
  • MTBF and MTTR data corrupted by missing records
With Opsima
  • Radio, WhatsApp, and Teams reports captured and parsed in real time
  • SAP PM order auto-created with the correct timestamps and fault code
  • Navis unit status set to Under Maintenance within sixty seconds
  • On-call crew dispatched in Teams with ETA confirmed
  • Reserve unit pre-allocated before slot planning re-runs
  • MTBF and MTTR computed on complete, timestamped data
<4 min
Full response time
0
Manual steps
100%
Shift events captured

Numbers we have actually measured.

PNCT
+15 hrs
Extra MTBF per straddle carrier per month, post-deployment
PNCT · container terminal field deployment
PNCT
14×
Increase in equipment status changes captured per month
~1,000 → ~14,000 / month · PNCT field deployment
PNCT
+5%
Fleet availability uplift after the response workflow went live
PNCT · fleet of straddle carriers and STS cranes
PNCT
~15%
Fewer breakdowns on the maintained fleet, post-deployment
PNCT · reliability uplift on monitored units

Before, and after.

We were managing everything in WhatsApp. The night handover was a ten-minute voice note nobody could search. Now the night-shift data flows straight into SAP, on the same systems we already run.

I
Ido S.
Director of Engineering, major container terminal

Our KPI reports never matched what the team knew was true, because the night-shift data was being filled in from memory. The first month it was live, the availability number on the board was the availability number on the ground.

V
VP Operations
Container terminal network, three facilities

What sold us was that we didn't pay until it ran on real shifts. IT got the codebase, ran it in staging on our SAP, and then we turned it on for one shift. After that, it was just how the terminal worked.

O
Ops Director
Bulk terminal, 800K+ moves per year
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