What connectivity is genuinely for
It is worth being precise about what the network buys, because the answer is substantial and it is not detection.
Connectivity buys history, and history is what makes trend analysis and baselines possible at all - a device holding minutes of readings cannot tell you what normal looked like last month. It buys visibility for people who are not standing next to the machine. It buys correlation across multiple nodes and multiple sites. It buys a record good enough to investigate an incident afterwards. And it buys the ability to reach a model, or a colleague, or a maintenance queue.
Every one of those is valuable. None of them is the alarm.
Edge versus cloud, stated as a decision
Cloud-first designs are common because they are easier to build and easier to update: put a thin sensor in the field, do the thinking centrally, ship improvements without touching hardware. For most IoT categories this is straightforwardly the right trade.
For safety it inverts, because the failure modes are asymmetric. A dashboard that is unavailable for an hour is an inconvenience. An alarm that is unavailable for an hour is the entire product failing during precisely the window it existed for - and there is no way to know in advance whether that hour contains an incident.
So the rule is narrow rather than absolute: the decision to sound an alarm belongs on the device. Everything else can and should live centrally, where it has more data and can be improved without a site visit.
Why industrial networks are worse than office ones
Plant Wi-Fi contends with metal structures, machinery that generates broadband electrical noise, and buildings that were not designed with propagation in mind. Coverage is patchy in exactly the corners where a hazard node is most useful. Power events take switches down along with everything else.
This is not a reason to avoid connecting things. It is a reason to assume the connection is intermittent and design so that intermittency is survivable - readings that buffer and resend, a device that behaves correctly while disconnected, and no silent degradation of the safety function when the link drops.
How Alfa HazardX splits the responsibility
The node samples, evaluates thresholds, drives its own display and buzzer, and only then attempts to publish. Publishing is deliberately the last step in the loop, because it is the only one permitted to fail without consequence for detection.
The cloud receives readings over an authenticated ingest path, stores them, evaluates them again with more history than the node holds, runs trend and baseline analysis, matches behaviour signatures, and pushes updates to the dashboard in realtime rather than by polling. It can also open an incident and instruct the node to raise its reporting rate to 1 Hz for a forensic recording.
That last capability is the clearest illustration of the split: the cloud can ask the node to behave differently, and cannot prevent it from alarming.
Field devices are physically accessible
A security consideration specific to industrial IoT, and one that is regularly overlooked: a node on a factory wall is reachable by anyone who is in the building. It can be opened, removed, or read.
That leads to a practical rule - a field device should hold the minimum credential that lets it do its job, and nothing broader. In Alfa HazardX the node authenticates to an ingest endpoint with a per-device key that can be revoked individually, and camera uploads are routed through the application server precisely so the device does not need object-storage credentials of its own. A stolen node yields its own revocable ingest key and nothing else.
What an IoT safety deployment involves
Mount, power, and the node registers itself the first time it reaches the ingest endpoint - there is no per-device configuration ceremony. The work that actually takes time is deciding where nodes go, which is a survey question about airflow and gas density rather than a networking one, and tuning thresholds against the plant's real process baseline so that alarms mean something.
A system that is easy to install and badly placed is worse than no system, because it produces confident silence.
