One AI platform for the whole port city: terminals, trucks, depots, rail and authorities.
Less congestion, less CO₂, faster ROI — for every actor of the chain.
One AI platform for the port city
AI stowage & bay-plan intelligence

Plan it. Optimize it. Prove it.

Bayplan AI — the stowage plan, matched to what really moved

Import the vessel BAPLIE, read the bay plan, let the AI tighten the stowage and crane sequence, then reconcile every planned move against what was really loaded and discharged — per vessel call, with proof.

See how it worksBook a 30-min demo
Container terminal and vessel berth seen from above, with bays, crane rails and yard stacks

Built for terminals that plan vessels every day

From the BAPLIE handshake to the quay, one shared view for planners, foremen and the shipping line.

What Bayplan AI does

One plan, end to end

Six tasks the planning desk does by hand today, done once and shared.

Import any BAPLIE
EDIFACT 3.1 and 2.x or Excel — the vessel profile, bays, tiers and rows load in seconds.
Live bay view
A readable bay plan on screen — by bay, row and tier, colour-coded by weight, port and reefer.
AI stowage optimization
The engine proposes a tighter stow that respects stability, rotation and special cargo rules.
Crane sequence builder
A work queue per crane that cuts gantry travel and keeps the hook moving.
Rehandle reduction
Fewer unproductive moves: the AI flags and removes avoidable re-stows before the call.
Planned vs done, with proof
Every call reconciled — what was planned, loaded, discharged, missing or unexpected.

From the EDIFACT message to the hook

Bayplan AI sits between the shipping line’s stowage message and your terminal operations. It reads the plan, checks it against the real vessel profile, and hands your team a stow and a crane sequence they can work — then watches reality come back move by move.

Reads the real vessel
Bay, row, tier, reefer plugs, dangerous goods and out-of-gauge slots — matched to the actual ship, not a template.
Keeps the stow legal
Stability, stack weights and segregation rules are checked as the plan changes.
Learns your terminal
Every reconciled call feeds the next prediction — the stow gets sharper over time.
See the capabilities
Isometric illustration of a data-driven stowage plan
Crane sequence, not a guess
The hook order is built from the stow, so the gantry travels less and the vessel sails sooner.
How it works

Five steps, one shared plan

No new tool for the gang to learn — it starts from the message you already receive.

1 · Import
2 · Bay view
3 · Optimize
4 · Execute
5 · Reconcile
Import the BAPLIE

Drop the stowage message (EDIFACT 3.1/2.x) or an Excel plan. The vessel profile and bays load at once.

Read the bay plan

See the stow by bay, row and tier, colour-coded by weight, discharge port and reefer.

AI optimizes

The engine proposes a tighter stow and a crane sequence that respect stability and rotation.

Work the call

Foremen work the sequence; every load and discharge is captured move by move.

Reconcile & report

Planned versus done per call, with exceptions flagged and a report your line can trust.

Talk to a planner[/vc_column][/vc_row]
Example of results

What a tighter plan returns

Indicative ranges from stowage reconciliation on container vessel calls — your mix will differ.

0%
Fewer rehandles
+0
More crane moves / hour
0′
Minutes to check a plan
0%
Vessel calls reconciled
Shorter berth time
A cleaner sequence keeps the hook moving, so the vessel sails sooner.
One version of truth
Planners, foremen and the line read the same plan and the same result.
Evidence, not debate
Exceptions are shown with proof, so claims are settled fast.
[/vc_column][/vc_row]

Fewer rehandles, lower emissions

Every avoided re-stow is a crane move that never burns fuel, and a gantry that travels less. A tighter stow and a shorter berth stay cut the terminal’s energy per box — measurably.

Less idle, less diesel
A moving hook and shorter calls mean fewer idle hours on the quay.
0
kg CO₂ / avoided rehandle
−0%
Lower energy per box
Isometric cargo vessel, lower-emission call
[/vc_column][/vc_row]
Capabilities

Everything the planning desk needs

Five modules, one plan — from the BAPLIE handshake to the report your line signs off.

Any plan, validated on the way in

Any plan, validated on the way in

The message is parsed and checked against the real vessel — wrong slots, over-stacks and missing reefer plugs surface before the call.

Supports EDIFACT BAPLIE 3.1 and 2.x, MOVINS and Excel, so the plan you receive is the plan you work.

A tighter, legal stow

A tighter, legal stow

The engine proposes a stow that respects stability, stack weights and segregation while packing the ship for its rotation.

Special cargo — reefers, DG, out-of-gauge — keeps its rules while the rest of the plan tightens around it.

Keep the hook moving

Keep the hook moving

A work queue per crane minimises gantry travel and removes avoidable re-stows before they reach the quay.

Foremen get a sequence they can work, not a spreadsheet — and the vessel sails sooner.

Proof, per vessel call

Proof, per vessel call

Every load and discharge is matched to the plan: what moved, what is missing, what was unexpected.

The result is evidence both the terminal and the line can trust, captured as the call runs.

Plugs into what you run

Plugs into what you run

One API plus EDI, EIR and file exchange push the reconciled plan back to your TOS and the line.

Scheduled reports and a shareable view close the loop for operations and commercial alike.

Why it is different

Manual planning vs Bayplan AI

Same vessel call — one side is memory and spreadsheets, the other is a shared, checked plan.

Today / manual
With Bayplan AI
Plan import

Read the vessel BAPLIE automatically

Manual re-keying
Included
Bay view

A readable, colour-coded stow on screen

Static printout
Included
Stowage optimization

AI tightens the stow for the rotation

By hand, best effort
Included
Crane sequence

Work queue per crane, less gantry travel

Foreman’s head
Included
Rehandle control

Avoidable re-stows flagged early

Found on the quay
Included
Reconciliation

Planned vs done, per call

Spreadsheet after the fact
Included
Proof & reports

Exceptions with evidence

Email threads
Included
API & EDI

Push back to TOS and the line

Re-typing
Included
How teams start

Start with one vessel, scale to the berth

No list price on a page — scope first, then a clean proposal. Every tier includes import, bay view and reconciliation.

On request

Pilot

BAPLIE & Excel import
Live bay view
Planned vs done reconciliation
Shared read-only view

On request

Terminal

Everything in Pilot
AI stowage optimization
Crane sequence builder
Scheduled reports

On request

Enterprise

Everything in Terminal
API, EDI, EIR & FTP
Multi-terminal dashboard
Priority onboarding
No seat you do not use
Onboard on your next call
Your data stays yours
Get a scoped quote
[/vc_column][/vc_row]
Rollout

Live on your next vessel call, not next quarter

A four-week path from your first imported plan to reconciled reports.

Week 1 · Connect

We ingest a real BAPLIE from one of your lines and render the bay plan.

Week 2 · Shadow

Bayplan AI runs beside your planners on live calls — no change to operations.

Week 3 · Optimize

The AI stow and crane sequence go to the foremen on a first supervised call.

Week 4 · Reconcile

Planned-vs-done reports land for operations and the line; we tune the rules.

Start from the message you already receive — no new data to collect.

From plan to proof in one call

From plan to proof in one call

See how it works
[/vc_column][/vc_row]

Your formats, your languages

Bayplan AI speaks the standards your lines already send, and the languages your teams work in.

Standards
EDIFACT BAPLIE 3.1 & 2.x, MOVINS, plus Excel import.
Languages
Interface in English, French and Spanish.
[/vc_column][/vc_row]

Why we built it

We kept seeing the same gap — a beautiful stowage plan on one side, and what the cranes really did on the other, never reconciled. Bayplan AI closes that gap on every call, so planners stop arguing and start trusting the plan.

Co-Founder & CTO, DMSLOG.Ai
Olivier Raveau
Co-Founder & CTO, DMSLOG.Ai

Olivier Raveau

[/vc_column][/vc_row]
Olivier Raveau

Olivier Raveau

Co-Founder & CTO, DMSLOG.Ai

A word from the founder

“DMSLOG builds the quiet software that terminals run on. Bayplan AI is the piece that finally lets the plan and reality meet — one import, one optimized stow, one honest reconciliation. Built with the people who work the quay, for the people who work the quay.”

Talk to the team
[/vc_column][/vc_row]
FAQ

Straight answers

The questions planners and line managers ask first.

Isometric AI analytics illustration
No. Bayplan AI reads the BAPLIE you already receive and pushes results back by API, EDI or file — it sits beside your TOS. See the Terminal Operating Systems mesh for how it connects.
EDIFACT BAPLIE 3.1 and 2.x, MOVINS, and Excel. The message is validated against the real vessel on the way in.
No — it is a proposal. Planners stay in control; the engine suggests a tighter, legal stow and a crane sequence you can accept, edit or ignore.
Move by move. Every load and discharge is matched to the plan, and exceptions — missing, extra or wrong-slot boxes — are flagged with proof per vessel call.
Yes. One network view spans every call; see VBS Multi Terminals for the multi-site pattern.

Bring your next vessel call into Bayplan AI

Send us one BAPLIE and we will render the bay plan, propose the stow, and show you the reconciliation — on a live demo.

Book a 30-min demoBrowse the App Store