Why this environment matters
A container terminal links shipping-line messages, customs status, yard planning and equipment dispatch. A compromised business interface can be disruptive even without reaching crane control directly: a false release or misplaced container record can halt cargo movement. This concept protects the authority to change those operational records and issue work orders.
The security challenge
A shipment message might request a pickup, change a destination or update a vessel schedule. The proposed intake service would parse it as untrusted business data and associate it with an authenticated trading partner. A separate workflow service would check the terminal’s current record and required approvals before creating an executable work order.
How the capsule model could help
NØNOS capsules could isolate partner-specific message parsers from yard-state storage and dispatch adapters. Each work order would name the container, location, permitted operation and relevant release state. Equipment safety controllers would continue to decide whether physical movement is permissible. A cleanly parsed instruction could still be wrong because a source organisation supplied false information. After a destructive incident, a terminal needs to reconcile what actually moved with what its database says moved. A restartable runtime could help rebuild the application environment, but it cannot reconstruct a container’s position from memory isolation alone. Durable movement receipts, independent checks and operator reconciliation remain essential. The initial pilot would use a shadow dispatch feed, comparing proposed authorisations with recorded operations without controlling equipment. Particular attention would go to duplicate partner messages, reversed work orders and customs holds arriving after a pickup has already been scheduled.
Deployment requirements
The proposed boundary does not resolve fraudulent source documents, physical cargo theft or unsafe equipment logic. Integration would require terminal-specific workflows, event storage and equipment interfaces, with operational owners approving every control path. Evaluation requirements: Replay the same container-release message and verify that it cannot create duplicate pickup authority. Apply a hold after planning but before dispatch; the dispatch decision should use the current hold. Recover from a simulated application loss and reconcile a set of movements completed during the outage.
Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.
An external booking must not become an equipment instruction
A shipment message might request a pickup, change a destination or update a vessel schedule. The proposed intake service would parse it as untrusted business data and associate it with an authenticated trading partner. A separate workflow service would check the terminal’s current record and required approvals before creating an executable work order.
NØNOS capsules could isolate partner-specific message parsers from yard-state storage and dispatch adapters. Each work order would name the container, location, permitted operation and relevant release state. Equipment safety controllers would continue to decide whether physical movement is permissible. A cleanly parsed instruction could still be wrong because a source organisation supplied false information.
Restore the yard, not just the server
After a destructive incident, a terminal needs to reconcile what actually moved with what its database says moved. A restartable runtime could help rebuild the application environment, but it cannot reconstruct a container’s position from memory isolation alone. Durable movement receipts, independent checks and operator reconciliation remain essential.
The initial pilot would use a shadow dispatch feed, comparing proposed authorisations with recorded operations without controlling equipment. Particular attention would go to duplicate partner messages, reversed work orders and customs holds arriving after a pickup has already been scheduled.
Who could buy or integrate it?
- Terminal operators purchasing operational software platforms
- TOS vendors integrating execution and messaging layers
- Port automation integrators connecting business and equipment systems
Industry examples: Kaleris, Tideworks Technology. Organisations shown illustrate the industry. No NONOS customer, partner or endorsement relationship is implied.