Container Movements Documentation

Coastal container-line operations — voyages, container movements, cargo manifests, demurrage and invoicing on the Port Meridian ↔ Halcyon service

This section covers the Container Movements 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

Container Movements runs a coastal container line end to end: vessels work a scheduled service between the mainland hub of Port Meridian and the island port of Halcyon, each voyage carrying its master, port of loading and discharge and estimated timings; every box in the fleet — owned outright or on hire — moves through a lifecycle of receive, load, discharge and return, recorded as dated actions against its container history and attached to the voyage it sails on; the full containers loaded for a voyage are grouped into container, breakbulk and LCL manifests by shipper, consignee and commodity; when a full box is discharged its storage clock starts and runs until it is loaded out again, accruing tiered storage and detention charges once the free days set for the depot are used up; those charges roll up into demurrage periods by client, are bundled into invoices and chased with email notifications; and delivery, release and receival dockets, de-duplicated client and owner registers, a commodity taxonomy and a full change log sit underneath.