Inputs
Anchorage pressure, 6-hour and 12-hour arrival surge, positive net accumulation, and vessel dwell pressure. Terminal occupancy and purpose-of-call remain visible context, not headline-score drivers.
How the signal works.
Live port data becomes a concise operating signal, with source freshness and route context kept visible.
Headline Layer
Congestion Signal
Anchorage pressure 30%
+
Arrival surge 30%
+
Flow imbalance 20%
+
Dwell pressure 20%
=
0-100 signal
Fresh source feeds are required before the dashboard publishes the headline score.
Scoring
Each component is normalized against current calibration bands before the weighted score is published.
Calibration Status
Empirical bands are accepted only after enough valid samples, covered days, and no large metric-history gaps. Until then, the dashboard exposes provisional calibration provenance.
Implemented Metrics
Signals by operating question.
Route Overlay
How transshipment context is represented.
Congestion signal
x
Singapore route weight
=
Delay exposure
The route layer is a demo overlay, not a cargo-value or payout calculation.
Dashboard Rows
The latest congestion row is duplicated across selectable route scenarios in the metrics service's latest layer. That makes route switching fast without changing the route-neutral time-series archive.
Exposure Formula
Route delay exposure equals the Singapore congestion signal multiplied by the selected static route weight. The result is a monitoring/commercial-review signal, not real cargo-value exposure.
Displayed Context
Route ID, origin, Singapore transshipment port, destination, cargo archetype, primary user, driver, caveat, category, and recommended action are persisted for each scenario.
Future Upgrade
A real route layer should use licensed route geometry, ETA, distance, display rights, and cache rules. The current route overlay is deliberately static until those decisions are explicit.