Solution

Ports & Coastal

Connect airspace understanding across coastal and logistics environments.

Operating context

Coasts and ports are where the air picture and the surface picture meet: cranes and ships, low-flying craft over water, and sea haze that changes what sensors see.

Questions asked here

  • What is flying over the water, the quay or the yard, and how does it relate to what moves on the surface?
  • Where does the sea or the shore limit what the sources can see?
  • Which of these views can be shared with the harbour, the terminal and the authorities without losing its meaning?

What is difficult today

Air and surface are watched by different teams with different tools. A low-flying object near a berth is a question for both, and neither side has the other's picture.

Operational flow

Where the weight falls in this environment

  1. Observe
  2. Correlate
  3. Verify
  4. Track
  5. Understand
  6. Prioritise review
  7. Alert
  8. Record
  9. Review
  10. Improve

The weight falls on understanding and delivering: the air picture is set beside the surface context and handed on with its sources and conditions attached.

A worked environment state

Three moments from a synthetic scenario, in relative terms.

A worked environment state Synthetic example
MomentWhat is seenWhat is stated
1A small craft flies low along the quayIt is shown against the surface context of the berth
2Sea haze reduces what one source can seeThe environment layer says so and lowers the stated confidence
3The harbour office and the terminal ask for the same viewEach receives the same state with the same sources and the same limits
Environment: Data table
ItemValue
WindExample state
VisibilityExample state
CloudExample state
Environment RD10Data status: Synthetic dataEvidence level: E0 · ConceptQuestion answered: What environmental context surrounds the scene?Soft contours for wind, visibility and cloud drift very slowly behind the scene, at low opacity. They give context only and can be paused at any time.Limitation: Contours are drawn examples and are not a weather service or a forecast.
Claims and conditions: Data table
ItemClear conditionsBusy conditionsDegraded sources
Claim AHoldsHolds in partNot supported
Claim BHoldsHoldsHolds in part
Claim CHolds in partHolds in partNot supported
Claims and conditions CH16Data status: IllustrativeEvidence level: E0 · ConceptQuestion answered: Which claims hold under which conditions?A grid sets three abstract claims against three classes of conditions and marks where each one holds, holds in part or is not supported, so limits are visible next to claims.Limitation: Claims and conditions are abstract classes with no real values behind them.

Twin and context view

The same state can be opened in the digital twin, where its layers, its sources and its record sit side by side.

Open the digital twin

What we can show today

This page claims nothing above the level of the projects it rests on.

What this does not claim

  • The page describes a design for joining air and surface context; it does not describe vessel tracking or port security.
  • Coastal conditions limit what sources can see; the design records this and does not remove it.
  • One project supports this environment and its evidence level is shown below; it is a design, not a validated service.

Responsible positioning

AIR NEXUS contributes the air side of a coastal picture. It does not direct vessels, cargo or personnel, and it does not replace the port's own systems.

Projects behind this