OBSERVATION
August 31, 2026
The pitch for edge computing in industrial IoT is clean: process sensor data locally instead of shipping everything to the cloud, cut latency, cut bandwidth cost, keep operating even if connectivity drops. All of that is true. What gets left out of the pitch is what actually deploying edge compute on a real, decades-old factory floor involves.
Most industrial facilities running this kind of rollout are not starting from a clean slate. They are working with a mix of sensor hardware from different eras, some of it decades old, communicating over a mix of protocols that were never designed to talk to each other, in physical environments — heat, vibration, dust — that consumer-grade edge hardware was not built for.
The architecture diagram for an edge deployment is the easy part. The actual work is protocol translation, hardware that survives the plant floor, and a rollout plan that does not require shutting down a production line to install it.
The most common failure point is not the edge hardware itself — it is underestimating how much legacy sensor and PLC integration work sits between “we bought edge devices” and “we have usable real-time data.” Facilities that treat this as primarily a hardware purchase consistently underestimate the integration timeline, sometimes by a wide margin.
The second common failure is deploying edge compute without a clear answer to what happens to the data locally versus what still needs to go to a central system. Edge compute that processes everything locally and reports nothing upward just creates 40 disconnected local views instead of one central blind spot — a different problem, not a solved one.
The facilities that get this right start with one production line or one class of equipment, build the protocol translation and integration layer for that specific case, and prove out both the local processing and the upward reporting before expanding. It is slower than the vendor pitch suggests, and it is also the version that actually survives contact with a real factory floor.
In professional services firms, a surprising share of senior time goes to status updates a well-built client portal would answer without a call. What we have seen when firms fix it.
Most delays we trace in logistics engagements are not transport failures. They are five systems disagreeing about where a shipment was, noticed only when the customer asked.
Firms treat unbilled time as a partner-discipline issue. In practice it is the predictable result of time capture that depends on someone remembering to log it after the work is done.
Across energy and utilities engagements, the root cause behind preventable outages is rarely the asset. It is the gap between the systems that each knew part of the story.
Edge computing in industrial settings gets pitched as a clean architecture upgrade. The reality on most factory floors is messier, and that mess is exactly what determines whether a rollout succeeds.
Travel and hospitality personalization used to mean a tailored homepage. The interesting shift now is happening in the parts of the journey nobody used to bother personalizing.