S·05 · ISR & Fire Detection

Early detection. Coordinated containment.

Persistent thermal and visual ISR across critical industrial sites and protected ecosystems. Anomalies caught at the first ΔT excursion, classified across modalities, and pushed into a coordinated response chain — ISR overwatch, suppression, evacuation — under one operator's view.

<60s
Anomaly → confirmed event
93%
False alarm reduction
1
Operator per sector
0
Process upset on test fires
The problem

First ΔT to confirmed event takes too long.

Industrial sites, energy infrastructure, and protected reserves all share the same problem: the first temperature or visual anomaly is real, but the path from "sensor noticed" to "operator acts" is full of friction. By the time someone confirms, the window for cheap action has closed.

P · 01

Thermal cameras alarm constantly.

Sun on a manifold, hot exhaust, equipment cycles — every site has a baseline of false thermal events. Operators learn to mute the camera that cried wolf.

P · 02

SCADA and CCTV don't talk.

Pressure spikes and visual smoke happen simultaneously, on different systems. Confirmation requires an operator to switch panes during the most time-critical minute.

P · 03

ISR drones launch by phone call.

When a confirmed event triggers ISR overwatch, the dispatcher calls a UAV operator on a different floor. Minutes evaporate before the first orbit.

P · 04

Suppression and evac are separate tools.

The team that suppresses talks on one channel; the team that evacuates is on another. The shell that should coordinate both is a clipboard.

The incident · BRG-4

Manifold 3, 412°C surface temp.

A composite drawn from confirmed industrial-site ignition events: a single manifold thermal excursion, dual-sensor confirmation, ISR overwatch in 3 minutes, suppression mission authorized, no process upset, no personnel injury.

REC · 1430:00 LT · BRG-4 · MANIFOLD 3
8 events · 11m elapsed · zero injuries · zero shutdown
1430:00bslΔT baseline nominal · 14 sensors · ambient 38°Cdetect
1430:42thFIRE-038 · THERM-01 + 02 dual confirm, 412°Cdetect
1431:18scaPressure +18% in 40s · upstream of Manifold 3fuse
1431:55cmdCmd AI drafts · ISR overwatch + evac orderdecide
1432:20evc14 personnel cleared to Muster 2act
1433:04isrUD EV-30A on-station · 4m flame, no secondaryfuse
1435:40opSuppression authorized. UD FH-35 launchedact
1441:00aarEvent closed. Manifold integrity preservedclose
The shift

From muted alarms to closed events.

MESH OS does not add another camera or another suppression drone. It collapses the time and tools between the first ΔT excursion and a closed, audited event — by fusing the channels and pre-staging the response.

Before · Legacy

Muted cameras. Phone-call dispatch.

  • Thermal cameras alarm on every sun-warmed pipe.
  • SCADA pressure data lives elsewhere.
  • ISR launch is a phone call.
  • Suppression and evac on separate channels.
  • Confirmed event takes 8–15 minutes.
  • No replayable record of the response.
After · MESH OS

Multi-modal confirm. In-shell response.

  • Dual-sensor thermal + SCADA correlation per event.
  • Pressure, temperature, visual fused per asset.
  • ISR drone auto-cued on confirmation.
  • Evac, suppression, ISR in one operator's view.
  • Confirmed event in under 60 seconds.
  • Full event timeline replayable, exportable.
Run the scenario

The same excursion, inside the shell.

The simulator below renders a BRG-4 thermal event in the operator's view. Watch dual-sensor confirm, SCADA correlation, ISR auto-cue and authorized suppression — all under one seat.

00–6s
PHASE 01
Detect
ΔT baseline nominal across 14 sensors. THERM-01 and THERM-02 dual-confirm a 412°C surface event on Manifold 3. SCADA pressure spike correlates within 40 seconds.
06–18s
PHASE 02
Decide
Command AI drafts ISR overwatch and evacuation. UD EV-30A dispatched. 14 personnel cleared to muster point. Visual on-station inside three minutes.
18–28s
PHASE 03
Act
Operator authorizes suppression. UD FH-35 launched on suppression mission. Manifold integrity preserved. Event closed at 11 minutes — no injuries, no shutdown.
PHASE · DETECT  ·  14:30 · BRG-4 sector · ambient 38°C · ΔT baseline nominal.
SCENARIO · BRG-4
Operational impact

What measurably changes.

Operator-measured deltas from a brownfield onshore-energy pilot, instrumented against the legacy alarm baseline on the same thermal and SCADA footprint.

<60s
Anomaly → confirmed event
First ΔT excursion to dual-sensor confirm.
93%
False alarm reduction
Multi-modal fusion vs. raw thermal alarms.
1
Operator per sector
Single seat covers thermal, SCADA, ISR, evac.
0
Process upset on test fires
Suppression contained within manifold envelope.
Why it works

Four MESH OS capabilities, composed.

Fire and ISR is a perception-first solution that depends on the rest of the chain to actually close events. The four MESH OS capabilities turn alarms into closed actions.

01Perception

Thermal + visual + SCADA, fused.

Dual-sensor thermal confirmation cross-checked against SCADA pressure and visual ISR. False alarms collapse; real events surface in under a minute.

02Command AI

Drafts evac, ISR, suppression — under doctrine.

Command AI proposes the response sequence — who evacuates, which UAV launches, when suppression authorizes — and cites the SOP clause for each step.

03Edge-first

Local nodes per sector.

Each sector runs its own perception and decision node. Thermal events confirm and ISR cues even when the centre is offline. Reconciles on reconnect.

04Sovereign

On-prem at the site.

Models and event logs stay inside the operator's regulatory boundary. Air-gap-capable for sensitive industrial sites and protected ecosystems.

Deployment

Eight weeks. One sector. Brownfield.

MESH OS deploys against the thermal cameras, SCADA tags and ISR drones already on site. We do not replace your detection layer — we replace the layer between detection and response.

D · 01Weeks 1–3

Sensor and SCADA ingest.

MESH ingests existing thermal feeds and SCADA tags. Baseline ΔT and pressure profiles built per asset. Historical alarm log replayed against the new fusion layer.

D · 02Weeks 4–6

Shadow operations.

Operators run their current workflow; MESH runs in shadow. We tune dual-confirm thresholds and SOP-cited drafts against the site's incident log and SOP binder.

D · 03Weeks 7–8

Single-sector cutover.

Crew transitions to the MESH shell on one sector. ISR cueing live. Suppression authorization remains with the operator. Authority widens sector-by-sector.

Pilot request

Bring detection and response under one shell.

Run an eight-week pilot on one sector. We integrate against the thermal, SCADA and ISR fleet you already operate. The crew keeps their workflow. We prove the delta against your incident log — alarm-to-confirm, confirm-to-action, action-to-close.

Next · S·01
Border Surveillance