Integrations
We read from and write to the TOS you already run. We do not ask you to replace it.
Overview
Anchora maintains its own adapters against the major terminal operating systems. The adapters are ours, they are versioned with the platform, and they are covered by the same SLA as the rest of the service.
Where a TOS exposes a write API, Anchora writes the agreed berth and yard plan back and tracks the acknowledgement. Where it does not, Anchora produces the file or message the TOS already accepts, and flags the write as manual so nobody assumes it landed.
Coverage
If your system is not listed, it is a scoped integration, not a refusal.
| System | Read | Write | Notes |
|---|---|---|---|
| Navis N4 | Yes | Yes | Vessel visit, berth plan, yard moves via N4 web services |
| Tideworks Mainsail | Yes | Yes | Vessel and yard; gate events read-only |
| CyberLogitec OPUS | Yes | Partial | Berth write supported; yard write by file exchange |
| Kaleris (Navis legacy) | Yes | Partial | Read via database view, write by EDIFACT |
| In-house TOS | Case by case | Case by case | Scoped during Week 1–2 discovery |
Next step
Your first call is with an engineer, not a sales-development representative.