Port Delay Intelligence
Dashboard
What's Next

Path to decision-grade use.

The current dashboard is a high-signal demonstration. The next build tightens operational semantics, source rights, calibration, and route context before broader customer-facing use.

Validation Agenda

Questions for maritime operators and domain experts.

Terminology Fit

Confirm whether anchorage pressure, arrival surge, berth-adjacent occupancy, and net accumulation match how operators describe congestion.

Counterexamples

Identify cases where vessels are slow, stationary, or berth-adjacent for reasons unrelated to congestion.

Action Categories

Stress-test monitor, notify, and commercial-review language against real executive workflows.

Route Narrative

Validate the Singapore transshipment scenario against real lane dependencies and exception handling.

Use Boundaries

What this dashboard does not claim.

No Inbound Vessel Coordinates

The due-to-arrive feed supports arrival surge, but it does not provide live inbound positions. Future enrichment can cross-reference IMO values with the position snapshot.

Berth Geometry Needs Review

OSM wharf edges and candidate DBSCAN slots are useful but not authoritative. Curated berth geometry remains the right target for operational confidence.

Calibration Is Provisional

The headline signal accepts empirical calibration only after sufficient valid history and freshness. Sparse or stale history is intentionally exposed through score status and confidence.

Route Overlay Is Static

The route overlay uses demo route weights. It does not yet ingest licensed route geometry, live voyage plans, distance, duration, ETA, or cargo economics.

No Goods Or Value Source

Current sources do not expose shipment value, goods onboard, freight value at risk, pricing, payouts, or underwriting context.

Event Context Is Separate

Dataminr, weather, cyclone, and schedule feeds belong in a future event-pressure layer. They remain separate from the current congestion score until the design is explicit.

Suggested Next Build

Next build sequence.

  1. 01
    Secure a maritime SME review.

    Validate field semantics, berth assumptions, route story, and customer-facing language.

  2. 02
    Keep polling long enough for calibration.

    Maintain server-side vessel, event, forecast, and metric jobs so time-series gaps do not reset confidence.

  3. 03
    Curate berth and terminal geometry.

    Replace seed OSM coverage where it misses visible berth stretches or operational berth boundaries.

  4. 04
    Confirm licensed route data.

    Lock provider access, display rights, cache rules, route geometry, distance, duration, and ETA semantics.

  5. 05
    Add event pressure as a separate layer.

    Filter noisy event feeds aggressively and show provenance before connecting them to headline views.