Concept Design

Ports & terminals

For cargo owners, terminal operators and inland carriers coordinating cut-offs, verified cargo information and changing vessel calls.

Resolving conflicting container weights before the vessel cut-off

The shipper may submit a verified gross mass before a container is repacked. The forwarder, carrier and terminal can hold different revisions as the loading cut-off approaches.

Workflow at a glance
  1. Source recordsPacking, weighing and booking
  2. ProcessingVersion declaration by voyage
  3. Decision ownerShipper and terminal liaison
  4. Operational outputAccepted declaration evidence

Implementation approach

Connect the verified declaration to container identity, shipper authority, weighing evidence, booking and voyage. Track the current revision and acknowledgements from each recipient so the operator can see where an obsolete version persists.

Exceptions and operating controls

Authorised parties decide whether the evidence meets requirements. A booking change or amended declaration triggers review. An unverified estimate cannot substitute for a valid declaration.

Illustrative operating scenario

A container moves to a later vessel after a repack. The terminal message for the first voyage was accepted, but the revised declaration for the new booking is still outstanding.

Acceptance test and handover

Test a roll to another voyage, a duplicate declaration and a corrected weight after initial transmission. Check the version received by the carrier and terminal at cut-off.

Industry evidence

AMSA explains container weight verification and the part played by the shipper and declaration. AMSA on verified container mass

Avoiding a failed truck slot when the container is unavailable

A haulier can book a collection slot while a container is unavailable for release or has changed terminals. The slot platform and cargo status feed can each be accurate at different times.

Workflow at a glance
  1. Source recordsSlot, release and discharge events
  2. ProcessingCheck dispatch prerequisites
  3. Decision ownerTransport allocator
  4. Operational outputFeasible collection instruction

Implementation approach

Join the road appointment, terminal availability, release references and transport order. Recheck prerequisite states at the dispatch decision, route conflicts to the planner and confirm any slot change back to the driver workflow.

Exceptions and operating controls

Keep border or commercial release decisions with their respective authorities. Show the timestamp and source of each status. A stale feed must not be interpreted as authority to collect.

Illustrative operating scenario

A scheduled truck has a valid slot but the discharge event has slipped. The dispatcher can reassign the truck and request a new slot before it joins the terminal queue.

Acceptance test and handover

Replay failed collections and changed slots. Measure avoidable truck turns, notice available to dispatch and cases in which the system presented a stale status as current.

Industry evidence

The ACCC examines Australian container terminal operations, including the landside interface with road and rail carriers. ACCC container stevedoring monitoring report

Synchronising shore services after a vessel ETA changes

A revised arrival can affect berth windows, cargo labour and service bookings. A published ETA update does not prove that the port agent, terminal planner and service providers have accepted the same revision.

Workflow at a glance
  1. Source recordsPort-call and service bookings
  2. ProcessingFind impacted commitments
  3. Decision ownerPort agent and terminal planner
  4. Operational outputAcknowledged shore-service plan

Implementation approach

Map port call, vessel, berth nomination and service orders to a shared revision history. Notify the responsible coordinator of impacted bookings and record explicit acceptance or rejection by each party.

Exceptions and operating controls

Harbour and terminal authorities retain movement and safety decisions. The integration coordinates planning information and cannot authorise a vessel movement. Keep estimates separate from confirmed service arrangements.

Illustrative operating scenario

An inbound call moves into a different shift. Labour is available but a required shore service still holds the original booking. The agent sees the outstanding dependency before confirming the updated plan.

Acceptance test and handover

Test an amended call, a cancellation and late updates received out of order. Verify which partners accepted the latest revision and which services still need a manual decision.

Industry evidence

The port authority publishes a vessel arrivals data model. A movement estimate is one input to the coordination of shore services. Port Authority of NSW · Vessel arrivals data model

Discuss a workflow All case studies