MAINTENANCE MANAGEMENT · MARINE PORTS & TERMINALS

Keep your terminal fleet on schedule and on record.

When an STS, RTG, or straddle carrier completes a PM or goes down mid-shift, the status lives on a radio channel and a WhatsApp thread for hours before SAP knows. We capture it the moment it happens, on your existing CMMS and TOS, and run the workflow until the maintenance record is real. Personalized software to run your terminal.

Runs on SAP PM, Maximo, AMOSNavis, Mainsail, OPUS TerminalSTS · RTG · SC · RS capturePay only after go-live

THE MAINTENANCE RECORD THAT RUNS A SHIFT BEHIND

I can tell you what the SAP report says. I cannot tell you what the fleet looks like right now. Those are two different things.

How the night actually went

07:00 Three straddle carriers complete overnight PM. Technicians radio completion to supervisor and start next tasks. SAP not yet updated.
07:20 RTG-03 develops a spreader fault mid-shift. Mechanic sends a WhatsApp to the team group. No work order opened.
07:35 Navis still shows RTG-03 as Available. Gang planner allocates the next container move to it.
08:15 Berth operations stall behind an RTG that is not moving. Vessel window tightening.
10:00 Shift supervisor calls the SAP coordinator to open the work orders from memory. Timestamps are approximate.
16:00 End of shift. PM compliance report shows 92%. Three completions are backdated, two breakdowns have no structured record.

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

The off-system gap

Every PM completion and 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

PM drifts into corrective

PM only works on schedule. When completions log late and breakdowns are missed, the plan drifts and deferred work slips into the next crane failure. You pay corrective rates on equipment you should have maintained on time.

Corrective costs run several times planned maintenance

Slot planning runs blind

Navis or your TOS still shows equipment under repair as Available. Gang planners dispatch the next move to it. The planner handles exceptions by hand, without knowing the equipment is the exception.

Cascading yard delay until status is corrected manually

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 and PM update (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 and PM update (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 PM cycle and one crane breakdown. We capture equipment classes (STS, RTG, SC, RS, TT), PM task types, severity rules, and the SAP and Navis fields you need populated. The workflow is written 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
PM rules, severity 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. PM completion ingest, breakdown capture, SAP work order write, Navis status update, parts logging, and M&R dispatch. 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 PM 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 PM 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: PM completions captured with real timestamps, breakdowns logged and dispatched in real time, Navis updated within sixty seconds. You pay only after it goes live and the maintenance record 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

Maintenance management, on your existing TOS and CMMS.

Without Opsima
  • PM completions logged from memory at shift end, timestamps approximate
  • SAP PM orders created hours after the event, fault code best-guess
  • Navis shows equipment under repair as Available, slot chaos follows
  • M&R team tracked via phone chain, sixty-plus minutes
  • Parts usage not captured in real time, storeroom accuracy unreliable
  • MTBF and MTTR computed on incomplete, backdated records
With Opsima
  • PM completions captured the moment the technician radios in, with real timestamps
  • SAP PM order auto-created with correct fault code and parts used
  • Navis unit status set to Under Maintenance within sixty seconds
  • M&R team dispatched in Teams with ETA confirmed
  • Parts usage logged immediately, storeroom levels accurate in real time
  • MTBF and MTTR computed on complete, timestamped data
+5%
Fleet availability
+15 hrs
MTBF per straddle carrier per month
14x
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
14x
Increase in equipment status changes captured per month
~1,000 to ~14,000 per month · PNCT field deployment
PNCT
+5%
Fleet availability uplift after the maintenance 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