🚢 Maritime, Ports & Shipping · C4 Architecture · Pro
Port Community System
A port community system that connects shipping lines, terminals, customs, freight forwarders and truckers on one platform, so documents are shared once instead of emailed many times.
C4 Architecture diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
What this diagram shows
- One platform for every party in the port
- Customs clearance status is visible to all
- Truck appointments reduce queues at the gate
Prompt used
Port community system: shipping agents file vessel calls and cargo manifests; terminal operators publish berth plans and container status; freight forwarders file shipping bills and track clearance; customs systems exchange messages through an integration hub; truckers book gate appointments. Services: vessel call, cargo manifest, document exchange, gate appointment, and a tracking API. Data stored in PostgreSQL.
Mermaid code
C4Container
title Port Community System
Person(agent, "Shipping Agent", "Vessel calls and manifests")
Person(ff, "Freight Forwarder", "Documents and tracking")
Person(truck, "Transporter", "Gate appointments")
System_Boundary(pcs, "Port Community System") {
Container(portal, "Web Portal", "Angular", "All parties log in here")
Container(vc, "Vessel Call Service", "Java", "Arrivals and berths")
Container(man, "Manifest Service", "Java", "Cargo manifests")
Container(doc, "Document Exchange", "Java", "Shipping bills, delivery orders")
Container(gate, "Gate Appointment Service", "Node.js", "Truck slots")
Container(hub, "Integration Hub", "MuleSoft", "EDI and API messages")
ContainerDb(db, "PCS DB", "PostgreSQL", "Calls, cargo, documents")
}
System_Ext(tos, "Terminal Operating Systems", "Container terminals")
System_Ext(cus, "Customs System", "Clearance")
Rel(agent, portal, "Uses")
Rel(ff, portal, "Uses")
Rel(truck, portal, "Books slots")
Rel(portal, vc, "Calls")
Rel(portal, man, "Calls")
Rel(portal, doc, "Calls")
Rel(portal, gate, "Calls")
Rel(hub, tos, "Container status")
Rel(hub, cus, "Clearance messages")
Rel(doc, hub, "Sends documents")
Rel(vc, db, "Reads/writes")Related templates
Import Container Clearance Sequence
The journey of an import container from unloading to leaving the port: discharge, customs filing, duty payment, delivery order and gate out.
Shipping Container States
The states a shipping container goes through in an export journey, from empty pick-up to delivery at the destination.
Vessel Tracking with AIS
How ships are tracked worldwide: AIS signals picked up by coastal stations and satellites, cleaned, matched to voyages and used for arrival predictions.
Container Terminal Operating System
Where a container terminal's systems run: the terminal operating system in the data centre, equipment control on cranes and yard vehicles, and gates with automation.
Ocean Freight Booking Schema
Tables for an ocean freight booking platform: shippers, bookings, containers, voyages, bills of lading and tracking events.
Vessel Arrival and Berthing
How a port handles an arriving ship: pre-arrival notice, berth allocation, pilot boarding, tug assistance and berthing.