Skip to content
Nexus Observatory

/

Public safety

/

Specialized fields

/

Incident response and deployable networks

Incident response, with a network that arrives with the crews.

When a disaster takes down local networks, responders need their own. A cell on wheels, satellite backhaul, drones, thermal cameras and gas detectors deploy with the crews and report to one picture that incident command, the agencies and the coordination centre share.

Plan a deploymentHow it worksStation Builder
Industry
Public safety
Measurements
5
Sources cited
5
  1. Public safety · Incident response and deployable networks

    When the local network is gone

    A flood, an earthquake or a large fire takes down masts and power just when responders need them. Crews arrive with radios that may not reach each other, and command has no picture of the scene. A network that arrives with the crews gives them voice, data and a shared view from the first hour.

  2. What is measured

    Gas, heat, the view from above and the crews

    Portable and fixed detectors read gas and toxic atmospheres at the scene and the cordon. Thermal cameras on crews and drones find heat and people in smoke or darkness, drones give the view from above, a portable station reads the weather, and every crew’s position is on the network.

    Instruments
    Gas detectors · Thermal cameras · Drones · Portable weather · Crew positions
  3. The base node

    A command post that keeps working

    The command post’s edge node fuses gas readings, imagery and crew positions into one picture, raises gas and heat alarms at once and keeps working when the satellite link drops, syncing the record when it returns. Crews keep their local picture even when the backhaul is gone.

  4. Radio and links

    Cell on wheels, satellite and mesh

    A cell on wheels gives the incident its own mobile network for voice and data, with mission-critical push to talk. Satellite backhaul connects the command post to the agencies when local networks are down, and mesh radios reach crews inside buildings.

    Links
    Private LTE · Satellite · Mesh
  5. How it works

    From a gas reading to a pulled-back crew

    A crew’s detector reads a toxic gas rising near a collapsed building. The reading reaches the command post over the incident network, the node raises the alarm, and command pulls the crew back and widens the cordon. Partner agencies see the change, and the record keeps it.

  6. From order to operation · Order

    Scope the agency’s incidents

    The scope reads the agency’s incident types, command structure, current radio and the agencies it works with. Nexus Observatory Inc. returns the kit list, the network and spectrum design, the training plan and a price per kit and per service.

    Plan a deployment
  7. From order to operation · Survey

    Exercise before buying

    Crews deploy a demonstration kit in an exercise with the agency: setup time, coverage at a typical scene, satellite performance and how the picture fits the command structure. Findings shape the kit, not the other way round. The exercise is repeated with partner agencies.

  8. From order to operation · Permits

    Spectrum, aviation and agreements

    The cell on wheels uses spectrum the agency holds or is lent under national rules; drones fly under aviation rules for emergency operations. Data sharing between agencies is agreed in advance, so nothing waits on paperwork at the scene. Every agreement is kept with the kit records.

  9. From order to operation · Build

    Build kits that deploy fast

    Detectors, cameras, drones, the cell on wheels, nodes and satellite terminals are built into cases, tested together and enrolled with their identities. Every case is labelled, charged and loaded with the agency’s configuration and maps. Setup steps are printed inside each case lid for crews under pressure.

    Open the Station Builder
  10. From order to operation · Install

    Deploy at the scene

    At the incident, the team raises the mast, starts the cell on wheels and the satellite terminal, hands detectors and radios to crews and launches the drone. The command post shows the picture as each part comes up, in the order the team trained.

  11. From order to operation · Commission

    Readiness, not ceremony

    Kits are commissioned at handover with a full deployment exercise: setup time, voice, data, detectors checked with reference gas, drone flights and the picture shared with a partner agency. After that, readiness is tested on schedule. Results are kept with each kit’s record.

  12. From order to operation · Operate

    Command with a shared picture

    Incident command sees crew positions, gas and heat alarms, drone imagery and weather on one picture, talks to crews over the incident network, and shares the picture with partner agencies and the coordination centre. Every alarm and decision is kept on the record.

  13. From order to operation · Maintain

    Ready for the next call

    After every deployment, kits are cleaned, recharged, restocked and updated. Detectors are bump-tested and calibrated on schedule, batteries cycled and software updated in rings. Every change is recorded, so each kit is ready for the next call. A kit returns to service only when its checks pass.

    Book field services
  14. Data products

    For commanders, crews and partners

    Incident commanders and partner agencies receive the shared picture; crews and safety officers receive gas and heat alarms; commanders and search teams receive drone and thermal imagery; agencies and reviewers receive incident records. Each product carries its time and source.

    See the data products
  15. Evidence

    An incident you can review

    Every alarm, decision and message is signed and kept with its time and place. Command follows the incident management system, search and rescue follows the international guidelines, voice follows the mission-critical standard and alerts travel in the Common Alerting Protocol, so every incident can be reviewed and learned from.

    Drawn against
    National Incident Management System · INSARAG Guidelines · 3GPP MCPTT · Common Alerting Protocol
  16. What you get

    Deployable connectivity and sensing kits

    A cell on wheels with satellite backhaul, mesh telemetry and environment nodes for incident bases and events. Delivered as rental and managed service, for emergency agencies, humanitarian logistics, event operators. Scale: Pre-positioned fleets. Service levels are written as numbers you can measure on your own dashboard.

    Talk to sales
  17. Next step

    Plan incident response and deployable networks with us

    Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for incident response and deployable networks. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.

    Plan a deploymentOpen the Station BuilderOpen the Studio

01The place and its hazards

Where it runs, and what can go wrong.

Operating contextFire, rescue, police, medical and civil protection agencies work under an incident command system at major incidents and disasters. Local networks may be damaged or overloaded; teams need voice and data, a shared picture of the scene and measurements of hazards such as gas and heat. International search and rescue teams follow common guidelines.

Hazards

  • Local networks down or overloaded
  • Responders exposed to gas, heat and collapse
  • No shared picture between agencies
  • Crews out of contact in the field
  • Kit that takes too long to set up

02What must be measured

What, where, how often, and under which rules.

Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.

MeasurementWhereCadenceSources
Gas and toxic atmospheresPortable and fixed detectors at the scene and the cordonContinuous1
Heat and people in smoke or darknessThermal cameras on crews and dronesContinuous during operations2
Aerial view of the sceneDrones over the incidentOn tasking23
Weather at the sceneA portable station at the command postContinuous4
Crew positions and voiceEvery crew on the incident networkContinuous5

03The observation stack

From one base unit to a network.

The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.

  1. 01

    Base unit

    A deployable kit: gas detectors, thermal cameras and a drone with an edge node in a rugged case.

    Build a station →
  2. 02

    Site

    An incident: a cell on wheels, satellite backhaul and mesh to the crews, with a command post.

    Plan a site →
  3. 03

    Fleet

    Every kit of an agency ready as one fleet, charged, updated and tested.

    Managed offers →
  4. 04

    Network

    Agencies and coordination centres exchange incident pictures and alerts through open standards.

    The open protocol →
  • 01Gas detector (industrial)
  • 02Thermal camera
  • 03Drone (UAS)
  • 04Cell on wheels (deployable)
  • 05Edge node (Wedge)
  • 06LEO flat-panel terminal
  • 07Generator
  • 08Telescopic mast

Radio and links

Private LTE

A cell on wheels gives the incident its own mobile network for voice and data, with mission-critical push to talk.

Radio and links

Satellite

Satellite backhaul connects the command post to the agencies when local networks are down.

Radio and links

Mesh network

Mesh radios reach crews inside buildings and beyond the cell’s coverage.

Edge computeThe command post’s node fuses gas readings, thermal and drone imagery and crew positions into one picture, raises gas and heat alarms at once and keeps working when the satellite link drops.

PowerA generator and batteries power the command post and the cell on wheels; detectors and cameras run on their own batteries with spares charged at the post.

04How it works

From the instrument to the product.

One observation’s path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.

Incident response and deployable networks: data path

– of 08

01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Radio access 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products Common Alerting Protocol3GPP Mission Critical Push To TalkOGC SensorThings API 09 Power and structure Supplies AC mains to the field equipment 01 Gas detector (industrial) Analogue I/O · RS-485 · Ethernet 02 Thermal camera Ethernet 03 Drone (UAS) USB · Video Subscriber phones and modems Not in the reference kit Drone ground control station Not in the reference kit 04 Cell on wheels (deployable) Ethernet · Fibre 05 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 06 LEO flat-panel terminal Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Shared incident picture Gas and heat alarms Drone and thermal imagery Incident records 07 Generator RS-485 · Ethernet 08 Telescopic mast MAVLink LTE/NR RS-485 Ethernet · RTSP/ONVIF Ethernet Ethernet Ethernet Satellite IP
From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation.
Bill of materials
ItemEquipmentData portsProtocolsPower in
01Gas detector (industrial)Fixed detector for flammable or toxic gas in industrial areas, with alarm outputs.Analogue I/ORS-485EthernetModbus, OPC UA, MQTT 524 V DC
02Thermal cameraLong-wave infrared camera for fire detection, equipment hot spots and night monitoring.EthernetRTSP with ONVIF profiles, MQTT 5PoE
03Drone (UAS)Uncrewed aircraft carrying sensors or a radio relay, operated within airspace rules.USBVideoMAVLinkInternal battery
04Cell on wheels (deployable)Trailer or vehicle carrying a telescopic mast, RAN, local core, backhaul and power to stand up a cell quickly.EthernetFibre3GPP NR air interface, 3GPP E-UTRA air interface, 3GPP 5G core service-based interfacesFuel, AC mains
05Edge node (Wedge)Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure.EthernetFibreUSBRS-485BMCMQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA12 V DC, 24 V DC, 48 V DC, AC mains
06LEO flat-panel terminalElectronically steered flat-panel user terminal for low-Earth-orbit broadband constellations.Ethernet—PoE, 48 V DC, AC mains
07GeneratorFuel generator with automatic start for backup or primary site power.RS-485EthernetModbusFuel
08Telescopic mastPneumatic or winch telescopic mast on a trailer, vehicle or base.———

How it scales

01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces.

SITE

Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality.

CLUSTER

×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites.

FLEET

Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts.

TRUST DOMAIN

TRUST DOMAIN

TRUST DOMAIN

×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange
The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding.
Data in the field
MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
Telemetry
OpenTelemetry OTLP.
Control
TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
Data upstream
At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
Evidence
DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
Events
Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
Exchange
OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.

05From order to operation

Every step, from the first call to a running site.

The same crew and the same record carry the work from scope to maintenance.

  1. 01 Order

    Scope the agency’s incidents

    The scope reads the agency’s incident types, command structure, current radio and the agencies it works with. Nexus Observatory Inc. returns the kit list, the network and spectrum design, the training plan and a price per kit and per service. 1

  2. 02 Survey

    Exercise before buying

    Crews deploy a demonstration kit in an exercise with the agency: setup time, coverage at a typical scene, satellite performance and how the picture fits the command structure. Findings shape the kit, not the other way round. The exercise is repeated with partner agencies.

  3. 03 Permits

    Spectrum, aviation and agreements

    The cell on wheels uses spectrum the agency holds or is lent under national rules; drones fly under aviation rules for emergency operations. Data sharing between agencies is agreed in advance, so nothing waits on paperwork at the scene. Every agreement is kept with the kit records.

  4. 04 Build

    Build kits that deploy fast

    Detectors, cameras, drones, the cell on wheels, nodes and satellite terminals are built into cases, tested together and enrolled with their identities. Every case is labelled, charged and loaded with the agency’s configuration and maps. Setup steps are printed inside each case lid for crews under pressure.

  5. 05 Install

    Deploy at the scene

    At the incident, the team raises the mast, starts the cell on wheels and the satellite terminal, hands detectors and radios to crews and launches the drone. The command post shows the picture as each part comes up, in the order the team trained.

  6. 06 Commission

    Readiness, not ceremony

    Kits are commissioned at handover with a full deployment exercise: setup time, voice, data, detectors checked with reference gas, drone flights and the picture shared with a partner agency. After that, readiness is tested on schedule. Results are kept with each kit’s record. 5

  7. 07 Operate

    Command with a shared picture

    Incident command sees crew positions, gas and heat alarms, drone imagery and weather on one picture, talks to crews over the incident network, and shares the picture with partner agencies and the coordination centre. Every alarm and decision is kept on the record. 21

  8. 08 Maintain

    Ready for the next call

    After every deployment, kits are cleaned, recharged, restocked and updated. Detectors are bump-tested and calibrated on schedule, batteries cycled and software updated in rings. Every change is recorded, so each kit is ready for the next call. A kit returns to service only when its checks pass.

06Data products and integration

What it delivers, to whom, and into which systems.

Data products

  • Shared incident pictureIncident commanders and partner agencies
  • Gas and heat alarmsCrews and safety officers
  • Drone and thermal imageryCommanders and search teams
  • Incident recordsAgencies and reviewers

Integration

  • Agency dispatchIncident pictures and alarms are shared with dispatch through its own interfaces.
  • Partner agenciesPictures and alerts are exchanged in the Common Alerting Protocol and open map formats.
  • Coordination centresSituation data is shared with coordination centres and satellite mapping services.

Exchanged through Common Alerting Protocol, 3GPP Mission Critical Push To Talk, OGC SensorThings API.

07Questions buyers ask

Before you scope it.

How fast does it deploy?

As fast as the team trains it; setup is exercised and timed before handover.

Does it work with our radios?

Yes, through gateways to the agency’s existing radio, with mission-critical push to talk on the cell.

What if the satellite link drops?

The command post keeps working locally and syncs when the link returns.

Who flies the drones?

The agency’s trained pilots, under aviation rules.

08Resources

The sources behind this page.

Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.

  1. 1National Incident Management SystemUnited States Federal Emergency Management Agency · 2017
  2. 2INSARAG GuidelinesInternational Search and Rescue Advisory Group, United Nations OCHA
  3. 3Copernicus Emergency Management ServiceEuropean Commission
  4. 4Guide to Instruments and Methods of Observation (WMO-No. 8)World Meteorological Organization
  5. 5Mission Critical Push To Talk (3GPP TS 22.179)3rd Generation Partnership Project

09Related

Use cases and solutions.

Use case

Deployable incident observatory

A trailer or vehicle with a cell on wheels, satellite backhaul, a mesh kit, a drone and weather and air-quality nodes for an incident base.The full use case →
Solution

Deployable connectivity and sensing kits

A cell on wheels with satellite backhaul, mesh telemetry and environment nodes for incident bases and events.Solutions for public safety →
Solution

Private Wireless as a Service

Standalone private 5G or LTE for a site, campus, port or mine: radios, core, SIMs, spectrum route and operations.Solutions for public safety →
Solution

Satellite and non-terrestrial backhaul

LEO and GEO backhaul, 3GPP non-terrestrial integration and direct-to-device fallbacks for remote sites.Solutions for public safety →

10Public safety: specialized fields

Other fields of this industry.

Specialized field

Wildfire detection and response

Smoke detection from towers, fire weather and danger, thermal confirmation and satellite hotspots, on microwave and satellite to the fire agency’s dispatch, so a start is seen in minutes.The full field →
Specialized field

Flash and urban floods

Rain and water depth in streets, culverts and small streams, with cameras at known flood points, on LoRaWAN and cellular, so warnings reach people in the minutes a flash flood allows.The full field →
Specialized field

Landslides and debris flows

Ground movement by GNSS, pore pressure and rainfall thresholds, ground vibration for debris flows, on LoRaWAN and satellite from unstable slopes to the agency that warns and closes roads.The full field →
Specialized field

Earthquakes and early warning

Strong-motion and broadband seismometers, GNSS for large events, structural response in key buildings, on fibre and cellular with timing that lets a warning outrun the shaking.The full field →
Specialized field

Avalanches and mountain roads

Snow and weather on the slopes, avalanche detection by radar and infrasound, cameras on the paths, on microwave and satellite to the road and the avalanche service, so roads close before the snow comes down.The full field →

Bring us the site.

Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.

Plan a deploymentStation BuilderOpen the StudioTalk to salesRequest a quote