Plans

Run the terminal you have. Compare the TOS you want.

We do not take a card on this page. You tell us the terminal, the question, and which plan fits. We call you.

Call Us — +1 (888) 528-4445 Request a callback
Container terminal overview: berth, yard, gate road, and on-dock rail linked as one operating system

Berth, yard, gate, and rail — the four work areas a TOS has to keep in one picture.

Base

Operations

One operating scenario at a time. A vessel call, a yard shift, or a gate peak — against a modeled terminal with the same physical rules a planner already lives with.

Call Us

Priced for a single terminal and a defined use.

  • ✓Vessel planning scenarios — berth window, quay crane work sequence, discharge and load lists (COPRAR-shaped).
  • ✓Yard operations — stack accessibility, rehandles (TIC Rehandle: dig the target out of the tier below), housekeeping, reefer plugs, block utilization.
  • ✓Gate & landside — truck appointments (COPINO), gate-in / gate-out (CODECO), truck turn time.
  • ✓On-dock rail — cutoff, block build, load to rail within the acceptance window.
  • ✓One controller — conventional dispatch on a reproducible, replayable run.
  • ✓Shift reports — gross crane rate, dwell, rehandle ratio, reservations refused. Mapped to TIC 4.0 / BSI PAS 4000 where a mapping exists.
Call Us about Operations

For planning & TOS evaluation

Enterprise

Enterprise

Same terminal. Same workload. Same disruptions. Two (or more) ways of deciding — compared so you can tell a better policy from a luckier run.

Call Us

Priced for A/B work, custom fixtures, and TOS mapping.

  • ✓Everything in Operations.
  • ✓A/B scenario testing — paired replications. Controller A and Controller B face the identical world-state. The assumptions cancel; the decision difference remains.
  • ✓Policy what-ifs — berth window vs QC assignment vs yard allocation vs appointment strategy, without changing the physics.
  • ✓Intention-based coordination — container and resource agents against a conventional TOS baseline (greedy / look-ahead dispatch).
  • ✓EDI-shaped inputs — COPARN bookings, COPRAR load/discharge, BAPLIE stowage, COARRI confirmations, COREOR release. Not a live EDI gateway; a faithful planning surface.
  • ✓Shadow operation — map observation and action interfaces to your production TOS. Agents change how decisions are made. They do not change the world’s rules.
  • ✓Authority & holds — customs, custody, and safety are precedence, not weights in a score.
  • ✓Intended-use sign-off — model card, scenario set, and remaining accommodations. A yard-dispatch finding supports a yard-dispatch decision. Nothing more is claimed.
Call Us about Enterprise

What you are actually comparing

Capability Operations Enterprise
Single-scenario run (vessel / yard / gate / rail)YesYes
Replay, event log, schematic animationYesYes
TIC-aligned counters (move, lift, rehandle, terminal move)YesYes
A/B (and A/B/n) on an identical worldNoYes
Paired replicationsNoYes
Controller bake-off (dispatch vs intention)NoYes
Custom terminal fixture / multi-string callArchetype onlyYes
TOS interface mapping / shadow operationNoYes

A move is one completed CHE cycle on one payload. A lift is a spreader engagement. A terminal move crosses the boundary (gate, rail, or vessel) — rehandles and internal transfers do not count. We keep those words apart because TOS reports that mix them cannot be compared.

A single container as the object every party references: line, trucker, rail, customs, terminal

The unit of work is the box, not the task list

A TOS already knows the identity: booking (COPARN), stow (BAPLIE), load/discharge order (COPRAR), gate confirmation (CODECO), release (COREOR). PortSim.ai keeps that identity, then asks what each party intends for it — and whether those intentions still have a feasible intersection.

Sign up

Call Us. We will call you back.

No self-serve checkout. A terminal is not a seat license. Tell us who you are and we will schedule a conversation.

+1 (888) 528-4445
Or call +1 (888) 528-4445 now
Quay-to-yard and yard-to-rail flows: ship-to-shore cranes, yard gantries, internal trucks, on-dock rail

Discharge, stack, rehandle, transfer, load. Enterprise A/B keeps this sequence identical and changes only how the next job is chosen.