All Technical Articles
SensingAlgorithmsDetection

How Are Thermal Hotspots Detected on Cargo Decks?

By Engineering — Sensing · May 8, 2026 · 8 min read

The detection problem on a cargo deck is not measurement — IR sensors are commodity. It is deciding which delta in which cell at which time is real.

Asking how thermal hotspots are detected is really asking three questions in sequence: how is temperature measured, how is anomaly distinguished from noise, and how is anomaly distinguished from a real thermal event. The first is solved engineering. The other two are where products differ.

Three families of measurement

Ceiling-mounted spot sensors

The legacy approach: a few dozen IR or smoke detectors on the deckhead, sampling a deck-wide volume. Trip on absolute threshold. Cheap, certified, and almost useless against the per-vehicle anomalies that matter on EV-mixed cargo.

Line-of-sight thermal cameras

A small number of high-resolution thermal imagers covering long view paths down a deck. Excellent angular resolution where the line of sight is clear; blind everywhere it is not. On a cargo deck this is most places.

Distributed sensor cell arrays

Many small IR sensor cells distributed across the overhead at vehicle-pitch density. Each cell has a narrow field of view scoped to one or two vehicles. Coverage is per-vehicle by design.

Anomaly versus noise

Once the measurement architecture is chosen, the algorithm question is the same: what crosses the threshold? A static temperature trip is the simplest possible decision rule and the worst-performing one. Engine bays cool unevenly. Solar gain through deck openings adds 10–15 °C on coastal sailings. Ambient varies 30 °C across a single voyage.

The approach we use is a per-cell rolling baseline (EWMA over recent samples) and trip on sustained delta-from-baseline rather than absolute temperature. The threshold becomes a relative quantity, robust to ambient drift.

Anomaly versus real event

A true delta in a single cell is still not enough. The most common nuisance source is solar gain on a sun-exposed cell — and it is shared by neighbouring cells. We add a coherence check: if the neighbouring cells share the delta, suppress; if the delta is local to one cell, escalate.

A useful framing: detection is the inverse of suppression. Cell-level triggers identify candidate events; cross-cell coherence suppresses the ones that are environmental.

Latency budget

< 8 ms
Sensor → segment master poll
~3 s
Coherence confirmation window
< 4 s
End-to-end measurement → bridge red-state
18–25 min
Lead time vs ceiling smoke (bench data)

What this implies for system design

  • Per-vehicle field of view, not per-deck volume.
  • Relative thresholds, not absolute.
  • Multi-cell coherence as the suppression layer, not as the detection layer.
  • Deterministic latency end-to-end so the confirmation window is bounded.

Sources

  • IMO — SOLAS Chapter II-2 and the FSS Code Chapter 9 (fixed fire detection and alarm systems): the regulatory baseline for ceiling-mounted deck detection.
  • IMO MSC.1/Circ.1638 — interim guidelines for minimising the incidence and consequences of fires in ro-ro spaces, including electric-vehicle considerations.
  • DNV — class guidance and research on fire detection for car carriers and ro-ro vessels.
  • [VERIFY: per-cell EWMA-baseline lead-time figures (18–25 min vs ceiling smoke) are RoRoSafe bench-rig data, not externally published.]
Related reading

Continue the thread