PortCalls — Coastal Voyage, Cargo & Port-Call Management Documentation
Coastal shipping operations, executed end to end — commercial contracts and voyage plans; the fleet, ports, terminals, berths and routes; cargo bookings, consignments, transport units, dangerous goods and readiness; stowage plans and cargo-securing inspections; port calls with declarations, service requests, berth windows and milestones; loading operations, tallies and statements of facts; voyage legs, readiness, positions, operational events and delays; and the performance reconciliation, evidence and notifications that close a voyage out.
This section covers the PortCalls application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.
In This Section
- Application Overview — what the app models and why
- Quick Reference — menu map, demo codes and statuses
- System Diagram — the data model mapped, with an interactive pan/zoom viewer
The Application in One Paragraph
PortCalls runs the operational execution of a coastal shipping service from the commercial commitment to the reconciled voyage. A service contract authorises a voyage, which sails a route with a nominated vessel and master, carries its parties (owner, operator, charterer, shipper, consignee, agent, terminal, stevedore) and breaks into one or more legs. Cargo enters as a booking, decomposes into consignments and their transport units, and carries its dangerous-goods declarations, documents and a readiness assessment that gates loading. How the cargo rides is set by a versioned stowage plan with its positions and proven by cargo-securing inspections using the ship's and terminal's handling equipment. At each port the voyage makes a port call — at a port, terminal and berth — carrying its declarations, requested port services (pilotage, towage, mooring, stevedoring, bunkering), berth windows and a milestone timeline. The physical move is a loading operation built up unit by unit in the tally and agreed in a statement of facts. Running underneath are the voyage readiness gate, position reports, the operational events that disrupt a voyage and the delays they cause — each with a responsible party and a demurrage flag — and finally the voyage-performance reconciliation (planned vs actual distance and transit, port and delay hours, capacity utilisation, cargo tonne-nm, schedule variance), the evidence register and the operational notifications. The demonstration boundary is deliberate: this is the operational layer and it references rather than duplicates the coastal-trading licence system, vessel safety-management and crewing, navigation/ECDIS, terminal operating systems, financial and charter-party accounting, and customs reporting. It is a prototype data and workflow model, not legal advice.