Signal Run
Start free
[INDUSTRY / LOGISTICS]

Decision-grade ontology for ports, terminals, and the networks between them.

From vessel approach to gate-out, every object and every action is typed, governed, and traceable. Signal Run ships a pre-built maritime ontology so your team deploys in weeks.

40+
PORTS MODELED
2.3M
CONTAINERS / MONTH
180+
BERTHS MANAGED
32ms
P99 DECISION LATENCY
01CHALLENGES

Three decisions that move tonnage.

[ACTION TYPE]

Berth allocation under draft

ReserveBerth

Draft constraints, tidal windows, and vessel LOA must converge on a single allocation decision. Signal Run models all three as ontology predicates so the action type can enforce feasibility before write-back.

[ACTION TYPE]

Customs unification across terminals

CustomsDeclaration

Multi-terminal ports speak different customs dialects. Signal Run normalizes HS codes, importer IDs, and value declarations into a single governed object type — so a clearance decision spans the entire port.

[ACTION TYPE]

Yard and dwell-time optimization

OptimizeYard

Container dwell time is the hidden cost of port operations. Signal Run tracks slot reservations, gate-in events, and vessel load plans as linked objects — enabling yard-optimization actions that cut average dwell by 18%.

02ONTOLOGY

The ontology that runs the network.

Eight object types model the full port lifecycle — from vessel approach through customs clearance and gate-out.

VesselOBJECT TYPE
imo · draft_m · beam_m · loa_m · flag
BerthOBJECT TYPE
id · terminal · length_m · max_draft_m
PortCallOBJECT TYPE
id · vessel · berth · direction · eta
SlotOBJECT TYPE
id · window · berth · reserved_by · status
TugOBJECT TYPE
id · operator · class · station · status
CustomsDeclarationOBJECT TYPE
id · hs_code · value_usd · importer_id
ContainerOBJECT TYPE
iso · vessel · slot · weight_kg · seal
BillOfLadingOBJECT TYPE
id · shipper · consignee · containers
callsreservesberths_atassisted_bydeclarescontainsshipped_viaVesselPortCallBerthSlotTugCustomsDeclContainerBoL
FIG 3A · Logistics ontology graph — 8 object types, 7 link types
03DASHBOARD

Port-ops in one pane.

A live console built on the logistics ontology — berth status, vessel calls, KPIs, and saved views in a single governed workspace.

signal-console · port-ops · sandbox tenant
LIVE
CALLS/24H
38calls
AVG DRAFT
13.84m
ON-WINDOW
92%
PILOT-WAIT P95
14min
CUSTOMS REJECT
0.7%
BERTHS
Berth AACTIVE
Berth BACTIVE
Berth CLOADING
Berth DIDLE
Berth EACTIVE
SAVED VIEWS
All active calls
Draft > 14m
Pending customs
CALL IDVESSELDRAFTTEUBERTHDIRETASTATUS
PC-4471MAERSK EDINBURGH14.2m8,240AIN06:15PILOT
PC-4472MSC LUNA13.1m6,800BIN07:40ON-WINDOW
PC-4473CMA CGM THALASSA15.0m12,100CIN08:20PENDING
PC-4474COSCO VENUS12.8m5,400DOUT09:00CLEARED
PC-4475ONE HARMONY14.6m9,100AIN10:30PILOT-WAIT
PC-4476EVERGREEN ARIA13.9m7,200EIN11:15ON-WINDOW
PC-4477HAPAG BREMEN14.1m8,800BOUT12:00CLEARED
PC-4478ZIM ATLANTIC12.5m4,600CIN13:45PENDING
FIG 3B · Port-ops console — sandbox tenant, sample data, 38 active calls
04PRODUCTS

Five modules in a typical logistics deployment.

01Ontology ConsoleModel vessel, berth, and cargo object types.02Signal StudioBuild AIS ingest pipelines and transform chains.03Decision LoopGovern berth allocation and customs actions.04Pulse AINatural-language queries over the port ontology.05Signal AtlasLineage from AIS feed to berth decision.
[CONTACT / LOGISTICS]

Talk to our logistics team about your network.

Build your subscriptionTalk to our team