BREAKDOWN RESPONSE · MARINE PORTS & TERMINALS

Breakdown response that runs at yard speed.

When an STS, RTG, or reach stacker stops mid-shift, the status lives on a radio channel and a WhatsApp thread for hours before Navis and your CMMS know. We capture it the moment it happens, on your existing TOS and SAP, and run the response with you. Personalized software to run your terminal, built and run for you.

Runs on Navis, Mainsail, OPUSSAP PM, Maximo, AMOSSTS · RTG · RMG · RS · TT capturePay only after go-live

THE VESSEL WINDOW

A crane goes down mid-vessel and only the repair crew knows what is happening. I find out when it comes back online.

How the night actually went

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

Up to 40-60% of shift 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 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 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.

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 terminal already runs on.

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

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

A working session with the people who run the terminal.

Your maintenance lead, gang planner, and IT walk us through one real crane breakdown. We capture equipment classes (STS, RTG, RMG, RS, TT), 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 terminal's own language
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 terminal'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 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 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

Breakdown response, on your existing TOS and CMMS.

Without Opsima
  • Radio and WhatsApp reports captured by nobody until shift end
  • SAP PM order created hours later, from memory
  • Navis shows the broken crane as Available, slot chaos follows
  • M&R team tracked down via phone chain, sixty-plus minutes
  • No reserve unit allocated, vessel window slips
  • 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 timestamps and fault code
  • Navis unit status set to Under Maintenance within sixty seconds
  • M&R team dispatched in Teams with ETA confirmed
  • Reserve unit pre-allocated before gang planning re-runs
  • 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.

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

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.

T
Terminal Operations Manager
Container terminal

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
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