Vessel, gate, yard, billing, customs — twelve dashboards held as one operation. End-of-shift reconciliation becomes real-time.
The terminal as one operating model — vessel at center, every surface connected.
Vessel arrives. Gate operations begin. Demurrage clock starts. Reefer alarms fire. Customs holds cascade. Billing reconciles end of shift. Twelve dashboards. Seven vendors. Three time zones. AI-BOS sees it as one operation.
Customs holds do more than pause one container. When CBP places a hold on a box in row 4, every box stacked above it in rows 5, 6, 7 — none of them held themselves — all of them sit on the demurrage clock. The cascade is predictable from the topology of the stack, the customs status flows, and the demurrage rules. Invisible until it costs you.
When the clock starts varies by shipping line and by beneficial cargo owner. Free-time conventions differ by contract; the exception classes that pause the clock — customs, weather, labor, equipment — compound differently per agreement. Recovered demurrage is real money; the calculation rules are the choke point. Most operators write off demurrage they should be recovering because the rules are buried in three systems and a spreadsheet.
Imports drop chassis, exports pick them up. When the pool drifts out of balance, yard density rises and gate turn time stretches. Resetting the pool at end of shift is operational tax that nobody owns until the bias is already crushing throughput. Most operators know this happens. None of them can predict it before it happens.
When a vessel turn slips, attribution is messy and retrospective — labor short, weather hold, customs delay, equipment down, planning miss. The shift report names what happened the next day. Real-time attribution as the slip happens is what changes the operation.
Worker-class rules per crane operation are governed by whichever labor contract applies — ILWU on the west coast, ILA on the east and Gulf, non-union at some southern ports. Gang composition shapes productivity, substitution rules, and overtime exposure. The contract details are the operational reality, not background.
Now imagine asking the right side a question.
Once the picture is one operation, you can ask it questions. The customs hold cascade you just saw rendered — your operations director asks why demurrage is up this week and gets the cascade explained: which containers, which BCOs, which holds, which dollars. The chassis bias forming in west yard — AI-BOS surfaces it before the gate queue starts building. Vessel productivity slipping — attribution lands as the slip happens, not in tomorrow's shift report. The model that gave you credibility in Act 1 becomes the model that gives you advice in Act 2.
You have the data. It lives in twelve systems. The customs hold blocking your demurrage clock — that's in CBP records, your TOS, your billing engine, but no one has it together until the spreadsheet at end of shift. The chassis bias eating your yard density — that emerges from gate transactions, yard inventory, and your chassis provider's portal, all live but nowhere connected. The vessel productivity miss — attribution gets reconstructed from shift reports the next day, when the next vessel is already arriving.
AI-BOS surfaces the answer in operator language, drawn from systems that don't talk to each other. Three customs holds in stack rows 4–6 cascading to thirty-seven adjacent containers — none of those adjacent ones held themselves, all of them on the demurrage clock because of stack position. Two of the holds traceable to BCO contract terms where the free-time conversion is shorter than your default. One reefer alarm last Thursday that went to the vendor portal but never to billing — the PTI charge wasn't applied. Total exposure on the table this week: $84,000. Recovery path: file the demurrage claim for the cascade-impacted containers, escalate the BCO contract review, push the reefer PTI charge through.
AI-BOS sits above the TOS, the billing engine, the reefer monitoring vendors, and the gate appointment system. Each system holds the same data named differently, reconciled never. AI-BOS reads them as one operational graph. When a chassis-pool imbalance starts forming in west yard, AI-BOS sees the gate transactions and the yard inventory and the chassis provider's allocations as connected facts, not three separate dashboards reconciled at month-end. The reconciliation that took your team forty hours a month happens continuously, in the background. Operations and finance see the same numbers, in real time, because there's only one set of numbers.
Vessel productivity slips happen — attribution is messy and retrospective. AI-BOS watches the same factors your shift report reconstructs the next day — labor short, weather, customs delay, equipment, planning miss — but as they're happening. Three weeks in, AI-BOS surfaces a pattern: gangs assigned to ships above 8,000 TEU on Monday morning shifts run productivity 12% below target, traceable to specific gang compositions and a recurring TWIC verification delay at the workforce gate. Nobody saw the pattern; everyone felt it. Now you can fix it.
Today, AI-BOS surfaces patterns and answers questions and reconciles systems and runs rules you can edit in plain English. Your operations director, your CFO, and your terminal president each get the same operational truth in their language, in real time, while your existing systems keep running. When you're ready — vertical by vertical, on your timeline — AI-BOS can do more than advise. The demurrage exception rule AI-BOS surfaces and your director edits can become the demurrage routing AI-BOS executes. The chassis bias AI-BOS spots can become the chassis allocation AI-BOS optimizes. The picture becomes the system, one vertical at a time.
Imagine the demurrage exception rule your director edited in Act 2 — AI-BOS doesn't just surface it, it executes it. The chassis bias your operating model sees forming — AI-BOS rebalances the pool before the bias hits the yard. The vessel productivity attribution that arrived in tomorrow's shift report — now landing as the slip happens. Worker screens aren't built once and used everywhere; they generate per role and per moment, showing the gate clerk what the gate clerk needs, the M&R supervisor what the M&R supervisor needs, the customs liaison what the customs liaison needs. Business logic isn't buried in code that takes IT three quarters to change; it's text the operations director edits, deploys, and adjusts as the operation evolves. The translation chain — leadership decision to consultant proposal to IT spec to development sprint to deployment to training — collapses to a single editable rule.
Finance reconciliation goes first for most operators — lowest-risk migration with the highest immediate cost recovery, and the demurrage and billing-leakage upside funds the rest. Gate operations follows when the appointment system, the OCR feed, and the chassis allocations can run as one orchestrated flow rather than three coordinated systems. Reefer monitoring and PTI charging consolidate next as the integrated picture proves the multi-vendor advantage. Labor and gang scheduling typically stay at Act 2's advisory layer rather than migrating to runtime — contract politics and worker relations are the right place to keep human authority, not the right place for AI to act unilaterally. Each vertical migrates on your timeline; the verticals you keep on legacy keep running through their existing systems while AI-BOS reads from them and reconciles continuously.
The full picture of your operation — parties, processes, entities, deployment — rendered as a navigable graph you own. Under NDA. Accessible inside AI-BOS. Yours to read, edit, and use.
We'll build it through a Discovery process that combines public-source ingestion (your filings, your systems' external APIs, industry data) with stakeholder interviews (your ops director, your CFO, your IT lead — the people who know the operation). You'll own the artifact; you'll decide what happens next.
The operating model is a complete value transaction in itself — ready for board reporting, AI-readiness preparation, acquisition due diligence, or simply seeing your operation clearly for the first time. No obligation to move beyond Stage 1.