CLIENT: Namib Reach Ports🇳🇦Namibia

Berthplan - Port Call Planning Console with a Rule-Checked Berth Board

Port Call Planning for a Namibian Multipurpose Port

Designed and built a clickable port call planning console for a multipurpose port at Walvis Bay: every call from pre-arrival notification to departure, a berth planning board that refuses windows breaking length, draft, cargo or dangerous goods rules, and an anchorage queue that records why each ship is waiting.

Scope of Work
Product design, UI build and clickable demo
Industry
Maritime & Ports / Port Call Planning
Enterprise
Compliance & Certifications
IMO FAL ConventionSOLAS and ISPS CodeIMDG CodeMARPOLNamibian Ports Authority Act 1994

Most of our work is under NDA. Per agreement, we can share the work but not the company details - all names and identifying information shown here have been changed.

Impact

5 Screens
Clickable end to end

Port control dashboard, calls list with table and timeline views, port call detail with 5 tabs, the berth planning board and the anchorage queue. Every one of the 27 demo calls opens its own detail page.

5 Rules
Checked on every berth window

Length against the berth limit, arrival draft plus 10% under-keel clearance against depth and predicted tide, vessel type, dangerous goods class, and overlap with other windows and blocks. A failing drop is refused with the reason.

11 Milestones
On every port call

From notified, documents complete and berth confirmed through pilot on board, all fast and cargo operations to clearance granted, last line off and departed, each with the time it was reached.

27 Calls
Realistic demo data

27 vessels with valid IMO check digits, 9 berths on 4 quays, 7 shipping agents, 4 berth blocks, 5 pilots, 4 tugs, 3 mooring gangs and 6 staff roles to switch between.

The Problem

Namib Reach Ports planned berths on a whiteboard and a shared spreadsheet. Agents emailed scanned pre-arrival forms that port control re-typed into three places, ETAs were whatever the agent last said, pilots and tugs were booked by phone, and dangerous goods and security declarations sat in an inbox. Ships waited at anchor about 14 hours on average and nobody could say why.

Our Solution

Berthplan takes a call from the agent's first notification to departure: FAL documents and declarations checked in one place, declared ETAs shown beside the AIS estimate, a berth board that checks every window against the berth's rules and the tide, an anchorage queue with a reason for every wait, and port dues built from the published tariff.

The Challenge: One Port, Many Constraints

Walvis Bay handles about 3,200 calls a year: container ships, dry bulk carriers, tankers at a small jetty, fishing and reefer vessels and seasonal cruise ships. Each berth has its own length, depth, cargo and dangerous goods limits, and every call depends on agents, terminals, pilots, tugs and the harbour master at once.

A Berth Plan Checked by Memory

Whether a ship fits depends on its length against the berth, its draft plus the under-keel clearance against depth and the tide at berthing time, its cargo type and the dangerous goods classes the berth permits. On a whiteboard, none of that was checked until someone noticed.

Documents Re-Typed Three Times

The IMO FAL Convention sets the arrival set: General Declaration, Cargo Declaration, Ship's Stores, Crew's Effects, Crew List, Passenger List and the Dangerous Goods manifest. Agents sent them as scanned forms, often late and in different versions, and port control typed them in again.

ETAs Nobody Trusted

Ships arrived hours early and sat at anchor while a berth was still occupied, then the pilot and tugs were booked by phone. Waiting averaged about 14 hours with no record of whether the cause was the berth, the cargo, the tide, documents or services.

Declarations Without Proof

Under SOLAS and the ISPS Code the security officer reviews pre-arrival security information, and IMDG Code declarations have to be checked against each berth. With both in an inbox, nobody could prove they had been reviewed before a ship came alongside.

Our Approach: From Port Rules to a Clickable Console

01

Spec and Rules Research

Mapped 12 user roles from port control to shipping agents, pilots and terminal planners, 36 screens across staff, agent portal and service provider views, and the data model for vessels, berths, port calls, berth windows and plan versions, FAL documents, declarations, service jobs, tariffs and an append-only audit log. Wrote down the rules the design follows: the Namibian Ports Authority Act, FAL forms, SOLAS and ISPS, the IMDG Code, MARPOL waste notification and AIS as a hint, not a record.

02

Clickable Demo on a Production UI Kit

Built 5 key screens on a production dashboard kit: the dashboard with KPIs, a port picture of every berth and the anchorage, needs attention and the next 48 hours; the calls list; the call detail with documents, constraint checks, declarations, tariff charges and activity; the berth board with zoom, tide band, drag and drop, Check plan and Publish plan; and the anchorage queue with reorder and call forward. All actions run on shared local state.

03

What a Production Build Adds

AIS feeds from Spire Maritime or MarineTraffic, vessel particulars from Sea-web, StormGeo weather, the regional port state control database, a national maritime single window where one is live, DCSA just-in-time messages, SAP Business One or Sage, and EFT in NAD through a Namibian bank. Staff auth by role, the full audit log, the agent portal, crew and terminal views, marine services schedules, declarations queues, departure clearance and billing.

Why It Works: Rules on the Board, Reasons on Record

The Board Refuses What Cannot Work

Each bar carries red badges for failed rules, such as a dangerous goods class a berth does not permit, and amber for warnings, such as a draft that needs high water. Hard failures stop the drop, warnings need a reason, and a plan with an exception needs harbour master approval before it is published.

AIS as a Hint, the Agent's ETA as the Record

The calls list shows the declared ETA beside the AIS estimate and the difference, the board draws the expected slip as a lighter tail on each bar, and positions older than 3 hours are greyed out on the anchorage map.

Every Wait Has a Reason

The anchorage queue records why each ship is waiting, from berth occupied to cargo not ready, draft or tide, documents or pilot and tug availability, and totals waiting hours by reason. Reorders are logged, and moving a ship ahead of an earlier arrival needs harbour master approval.

Checks Visible Before Alongside

Each call's checklist shows FAL documents, security review, dangerous goods review, waste notification, berth and services as done, pending or blocked. Crew and passenger lists show counts only, and opening names is logged. Charges are built line by line from the published tariff.

Related case studies

View all: Maritime & ports
Logo
Oceanlab

Enterprise Software Engineering - Human + AI

Languages

Locations

Global Headquarters

21 Merchant Road, 3rd Floor, Singapore 058267

Main corporate office and leadership operations

North America Office

548 Market Street, PMB 12345, San Francisco, CA 94104

Client operations and business development

India Office

402 Shivalik Shilp II, SG Highway, Ahmedabad 380015

Engineering and delivery center

© 2026 - Copyright. All Rights reserved Oceanlab