Skip to content
Warehouse, shipping & traceabilityLogistics & Ports

Prepare a vessel call: lists, dangerous goods, equipment

demi joins load lists, bay plan and dangerous goods declarations per vessel call, finds gaps and proposes cranes, reach stackers and staff.

Today

Before every vessel call, load list, discharge list and bay plan arrive from shipping line and agent, together with dangerous goods declarations, lists of reefers and out-of-gauge cargo and a stream of updated arrival times, as EDI messages, spreadsheet attachments, PDFs or in portals. Vessel planning merges them by hand and checks them against what is in the terminal and which equipment is ready. If a dangerous goods declaration is missing, a weight does not match or the heavy reach stacker is in the workshop, it often shows only once the ship is alongside. Then the ship waits, trucks queue at the gate and paid gangs stand idle.

An example

For Thursday's night shift Nordhanse expects a feeder vessel with 412 moves, 236 containers to discharge and 176 to load, plus two flat racks with out-of-gauge cargo. On Tuesday evening the agent has matched load list, bay plan, seven dangerous goods declarations and the reefer list and reports four points: a container with UN 1263, paint, is on the load list but in no declaration. Two containers differ by more than four tonnes from their verified gross mass. 31 reefers need power, but only 26 plugs are free. And according to maintenance one of the two RS 45 t reach stackers is in the workshop until Friday, while the spreader of crane 2 is due for inspection on Thursday. The agent proposes to deliver five reefers straight from the ship onto trucks, to move the spreader inspection to Wednesday morning and to plan a second gang. The vessel planner releases the queries to the shipping line's agent, and by Wednesday noon all four points are settled.
Fictional company, typical workflow.

Your data, wherever it lives

Today load lists, bay plans and dangerous goods declarations arrive by EDI, as spreadsheets or PDFs in the mailbox and from the portals of shipping lines and port; the stock sits in the terminal system's database, the condition of cranes and reach stackers in the maintenance system. demi reads, understands and links it per vessel call and container, with your access rights. AI finds gaps and contradictions in minutes and proposes equipment and staff per shift, and your vessel planning releases.

Where the data lives today

  • E-mails
  • PDFs
  • Office files
  • Web & portals
  • Databases
  • Machines & sensors
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: the terminal system with containers, yard positions and gate events, the mailbox and portals with the lists from shipping lines and agents, dangerous goods declarations as PDFs or records, and the maintenance system with the condition of cranes, spreaders and reach stackers. demi replaces nothing and links, per vessel call, every container on the lists with booking, weight, dangerous goods, reefer needs, out-of-gauge dimensions and yard position. One record then shows what comes, what goes and what moves it.

  2. 2 · PermitPermission Layer

    Vessel planning, shift management and the dangerous goods officer see the whole call; shipping lines and agents see only their own containers, hauliers only their pick-ups. Queries to the line, notifications to the port authority and the deployment plan go out only after release, and every release is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads every list, matches them container by container and reports gaps and contradictions: dangerous goods without a declaration, differing UN numbers or weights, reefers without a free plug, out-of-gauge cargo without suitable gear, export containers not yet in the terminal. From moves, weights, special cargo and equipment status it proposes cranes, reach stackers and staff per shift. Lifting capacities and segregation rules come from fixed tables, not estimates.

How it runs

  1. 1

    Load list, discharge list, bay plan and dangerous goods declarations come in by EDI, e-mail or portal and land with the right vessel call.

  2. 2

    demi matches every container on the lists with booking, terminal stock, verified gross mass and declarations.

  3. 3

    The agent reports gaps and contradictions with their source and drafts the queries to shipping line or agent.

  4. 4

    From moves, weights, special cargo and equipment status it proposes cranes, reach stackers and staff per shift.

  5. 5

    Vessel planning checks, adjusts and releases; queries, notifications and the shift plan go out after that.

What changes

  • Gaps in lists and declarations surface before the call, not at the quay

  • Equipment and staff planned to match cargo and time window

  • Less waiting for ship, trucks and gangs

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+315 hfreed per year

Assumptions and calculation

demi matches lists, declarations and equipment per call and drafts the plan; your planners release it.

2.5 h → 1.75 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

35 vessel calls × 2.5 h × 30% × 1.0 (manual) × 12 months = 315 h

Value per year, before demi costs

Freed per year+315 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€20,475

gained per year

315 h ÷ 1,760 h per role = 0.2 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Which formats does demi read for load lists and bay plans?

EDI messages from shipping lines, such as BAPLIE for the bay plan, spreadsheet attachments, PDFs and portal exports. Columns and codes that every line names differently are mapped once; after that the agent reads each new list from the same line by itself. Whatever it cannot assign with certainty is shown with the line from the source.

Does demi check the dangerous goods rules?

demi checks against the rules your dangerous goods officer sets: UN number, class and packing group from the declaration against the load list, the IMDG Code segregation rules for yard positions in the terminal and the deadlines for declarations. The agent reports every contradiction with its source; the assessment and the notification to the authority are released by the dangerous goods officer.

How does demi know which equipment is ready?

From your maintenance system and, where available, the machines' operating data: work orders, inspection dates, faults and operating hours. If a reach stacker is in the workshop or a spreader inspection is due, the agent plans without it and shows what that means for the call.

What happens when the vessel's arrival time changes?

The agent reads every new arrival time from shipping line, agent or portal and recalculates shifts and equipment. If something important changes, such as the call slipping into the night shift, shift management gets a new proposal for release. demi never changes a released plan on its own.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases