BREAKDOWN RESPONSE · CRANES · PORTS & TERMINALS

Crane breakdown response, captured at the moment it happens.

STS, RMG, RTG, and mobile harbour cranes. When one stops mid-move, only the repair crew knows the status for hours. We capture it the moment it happens, on your existing SAP PM and Navis, and run the response with you. Personalized software to run your crane fleet, built and run for you.

STS, RMG, RTG, mobile harbourRuns on Navis, Mainsail, OPUSSAP PM, Maximo, AMOSPay only after go-live

MID-VESSEL, MID-MOVE

A crane goes down mid-vessel. The mechanic radios the status and starts hunting parts. For the next four to twelve hours, only the repair crew knows what is happening.

How the night actually went

14:00 STS 2 stops mid-move during vessel ops. Operator radios: spreader fault.
14:03 Mechanic radios status, opens a WhatsApp thread with stores, starts hunting parts.
14:14 Navis still shows STS 2 as Available. Gang planner allocates the next move to it.
14:30 Move queues behind a crane that is not moving. Reach-stackers idle.
16:45 Vessel window slips. Demurrage clock starts. SAP PM still empty.
18:00 Shift handover. 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 crane breakdown that does not reach SAP and Navis in real time becomes a hole in the data the terminal runs on. Crane MTBF, fleet availability, and PM scheduling are all computed on records filled in hours later, from memory.

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

Slot planning runs blind

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

Cascading vessel delay until status is corrected manually

Preventive maintenance turns corrective

PM on cranes only works on time. When breakdowns log hours late, the PM plan drifts behind schedule and deferred work slips into the next breakdown. You pay corrective rates on cranes you should have maintained.

Crane 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 crane team already uses.

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 crane operators or mechanics to install. Nothing in their workflow changes.

CMMS crane work-order creation (SAP PM, Maximo, AMOS)
TOS crane-unit status update (Navis N4, Mainsail, OPUS)
WhatsApp Business, Teams, Slack, SMS ingest
Radio transcription API
Phase output
LISTEN · DELIVERABLE
CMMS crane work-order creation (SAP PM, Maximo, AMOS)
LISTEN · ARTIFACT
TOS crane-unit status update (Navis N4, Mainsail, OPUS)
2
Spec

A working session with the people who run the crane fleet.

Your maintenance lead, gang planner, and IT walk us through one real crane breakdown. We capture crane classes (STS, RMG, RTG, MHC), severity rules, escalation paths, and the SAP and Navis 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 crane team's own language
Crane severity rules, escalation rules, and SAP + Navis field map captured
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
Spec + mockup written from your crane 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, crane-ID 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 and TOS
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 and TOS
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 crane breakdowns, opens the SAP work orders, updates Navis, and dispatches the M&R team. 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

Crane breakdown response, on your existing TOS and CMMS.

Without Opsima
  • Radio and WhatsApp captured by nobody until the crane comes back online
  • SAP PM order created hours later, from memory
  • Navis shows the broken crane as Available, slot chaos follows
  • M&R crew tracked down via phone chain, sixty-plus minutes
  • No reserve crane allocated, vessel window slips
  • Crane MTBF and MTTR 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 crane fault code and timestamps
  • Navis crane status set to Under Maintenance within sixty seconds
  • M&R team dispatched in Teams with ETA confirmed
  • Reserve crane pre-allocated before gang planning re-runs
  • Crane MTBF and MTTR computed on complete, timestamped data
+5%
Fleet availability
+15%
Reliability
14×
Status changes 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 have no single place where I can see what is broken, who is working on it, and what is blocking the repair. I find out when the crane comes back online.

M
Maintenance Manager
Container terminal

It wasn't like we had to spend a lot of time educating you on our industry.

C
Charlie Ferlisi
Director of Engineering & Equipment Services, PNCT

Opsima eliminated the disconnect between our maintenance and operations teams. We went from Excel chaos to real-time clarity in weeks. The availability increase paid for itself in the first quarter.

D
Director of Equipment Services
Major US Container Terminal
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