Navis says 90 tractors available. Your gang planner puts it at 74. RTGs, reach stackers, and straddle carriers change state all shift via radio and WhatsApp, and none of it reaches Navis or SAP in time for planning. We capture real unit state the moment it changes and write it back to your TOS and CMMS. Personalized software to run your terminal.
THE YARD COUNT PROBLEM
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.
How the night actually went
Where the work goes
Every state change that does not reach Navis and SAP in real time becomes a hole in the data the terminal runs on. Fleet availability, MTBF, and PM scheduling are all computed on records filled in hours later, from memory.
Up to 40-60% of shift state changes filled in from memoryNavis shows units as Available that are in the workshop or sitting idle in a corner of the yard. The gang planner dispatches moves to them, handles exceptions by hand, and the real fleet count stays wrong until someone corrects it.
Cascading yard delay every time status lags behind realityPM only works on time. When straddle carrier and crane hours are filled in from shift notes, the PM plan drifts and deferred work slips into the next breakdown. You pay corrective rates on equipment you should have maintained.
Corrective costs run several times planned maintenanceHow we build it with you
We integrate with the systems your terminal already runs. CMMS (SAP PM, Maximo, AMOS), your TOS (Navis N4, Mainsail, OPUS Terminal), WhatsApp Business, Teams, radio transcript, and your existing GPS feeds. Nothing for operators or yard mechanics to install. The yard keeps working exactly as it does today.
Your maintenance lead, gang planner, and IT walk us through one real unit state change. We capture equipment classes (STS, RTG, SC, RS, TT), state-transition rules, the Navis and SAP fields that need to stay current, and how the gang plan reacts when availability changes. The workflow is sketched in their words, then turned into a structured spec and a mockup you can read before any code is written.
The tracking workflow is built end to end in a staging environment connected to your real TOS and CMMS. Ingest, state classification, Navis write, SAP work-order creation, and gang-planning notification. Your IT reads the codebase, the integrations, and the risk report before anything touches production. No black box.
IT promotes the workflow to production. We run it with you on real shifts until the Navis count matches the yard count. You pay only after it goes live and the fleet availability numbers on real shifts match the spec.
Before & After
From the field
The conversations we hear
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.
It wasn't like we had to spend a lot of time educating you on our industry.
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.
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.