Equipment status capture
Voice capture from operators and technicians, structured against your asset register and written into maintenance records. The breakdown report that currently travels by radio becomes data.
AI agents for ports, rail and terminals
In one line: berth planning, crane scheduling and yard optimisation are well served by established vendors. The gap is the dark data — a substantial share of what determines equipment availability travels by VHF radio, WhatsApp and verbal handover and never reaches the TOS.
Last updated:
The gap in your existing stack
Your terminal operating system knows what it was told. It doesn’t know the reefer plug that’s been intermittent for a week, the crane operator’s note about the spreader, or the verbal agreement with the haulier about tomorrow’s slot.
That information exists. It just isn’t anywhere queryable, which means planning runs on an incomplete picture and every handover loses a little more.
Workflows we automate
Gate operations and appointment management
Slot booking, appointment changes, driver comms and gate refusal handling. Hauliers get answers instantly; your gate team stops answering the phone.
Exception handling
Missed slots, equipment unavailability, documentation gaps and rehandle decisions — assembled with full context, resolved where delegated, escalated where not.
Shift handover
What one shift knows, the next shift gets — searchable months later when an investigation asks.
Documentation and customs coordination
Chasing incomplete documentation before it becomes a gate problem.
Traditional vs agent-augmented
| Today | With an agent | |
|---|---|---|
| Equipment fault report | Radio, then maybe a log | Captured, structured, in the CMMS |
| Haulier slot query | Phone call to the gate office | Answered instantly |
| Missed slot | Discovered at the gate | Detected, rebooked, notified |
| Shift handover | Verbal, unrecorded | Structured and searchable |
| Rehandle decision | Operator judgement, unlogged | Logged with reasoning |
What we integrate with
- TOS: major terminal operating systems with API access
- Maintenance: SAP PM, Maximo, Fiix
- Rail: scheduling and consist systems
- Customs and documentation: national single-window and customs APIs
- Comms: SMS, WhatsApp, portal messaging, radio-to-text gateways where deployed
- Agents overlay existing cranes, gates and control systems rather than replacing them.
How we de-risk it
- No writes to control systems. Crane, gate and automated equipment control is out of scope by design.
- Shadow mode against live operations before anything is authorised to act.
- Connectivity tolerance. Yards drop out. Capture queues and reconciles.
- Your infrastructure, your data. Terminal data is commercially sensitive and stays in accounts you control.
Related use cases
The same workflows, described by the job rather than the sector.
Frequently asked questions
Do we have to replace our TOS?
No. Agents act through its API and capture the operational reality it never receives.
Will this work with automated equipment?
It reads status and coordinates around it. It does not control it.
What about the multilingual driver population at the gate?
Handled natively across languages without separate builds.
How long to first deployment?
Typically 6–10 weeks from audit sign-off, with the TOS integration usually the longest pole.
Not sure this is your operation
Every sector page describes the workflows we’d expect to find. Yours will differ in ways that matter, and the audit is designed for exactly that — you get evidence about your own business rather than someone else’s.