Industrial IoT, described as engineering rather than adjectives.
What the platform connects to, why the edge-server split sits where it does, what scales cleanly, and what genuinely needs design.
Industrial IoT is a term that has survived a decade of overuse, and Indian manufacturers have reason to be sceptical of it. A large number of IIoT projects in this market produced a proof of concept, a dashboard nobody opened and an invoice. The pattern is consistent enough to be worth naming: the projects that failed were IT projects, and the ones that worked were maintenance and production projects that happened to use software.
This page describes the platform as an engineering artefact — what it connects to, how it moves and stores data, where it runs and what it secures — so it can be evaluated on architecture rather than on adjectives.
What the platform speaks.
| Layer | Supported | Notes |
|---|---|---|
| CNC controls | FANUC, Siemens SINUMERIK, Mitsubishi, Haas | Read over the plant network using the control's own interface. Read-only. |
| PLCs | Allen-Bradley, plus any device exposing Modbus or OPC-UA | Tag or register level, nominated during commissioning. |
| Fieldbus and serial | Modbus RTU over RS-485, Modbus TCP | Common on energy meters, drives and older process equipment. |
| Discrete and analogue I/O | MachineWise Gateway, optically isolated inputs | For machines with no readable control, and for added sensors. |
| Sensors | Tri-axial vibration, temperature, current, pressure, flow | Wired to the Gateway; sampling configured per machine class. |
| Uplink | Ethernet, Wi-Fi, 4G | Chosen per machine, because structured cabling rarely reaches every corner of a plant. |
Architecture with a reason behind it.
Acquisition happens at the edge, close to the machine, because that is where timestamps are trustworthy. A reading stamped at the machine survives a network interruption intact; a reading stamped when it arrives at a server produces a timeline that looks plausible and is wrong after every reconnection.
Aggregation, storage, computation and presentation happen on a server inside your plant. Practically, that means the system continues working during an internet outage — recording, dashboards, TV screens and local alerts all carry on. It also means your production data does not reside on infrastructure you cannot inspect, which is a recurring concern for manufacturers supplying defence, aerospace and customers with their own data clauses.
Multi-site groups keep a server per plant with a rollup that reads across them, so site-level resilience and group-level comparison are not in conflict.
Being specific about limits.
Machine count within a site
Adding machines is configuration, not a project. Dynamic nodes mean a new machine, sensor or computed data point can be added without a vendor visit or a release.
Data volume over years
Time-series storage sized for second-level data over multi-year retention, on hardware you own, with no per-gigabyte charge growing in the background.
Very high-frequency sensing
Continuous raw vibration streaming from many points is a different data-volume problem from state and count monitoring. It is handled by processing spectra at the edge rather than shipping waveforms, and it needs planning rather than assumption.
Sites with no reliable power
A monitoring system cannot outlive its own power supply. Where supply is unstable, the Gateway's real-time clock protects the timeline, but the server needs the same protection as any other business system.
The risks that actually occur.
The realistic risk in manufacturing software is not an external attacker. It is the wrong people seeing commercially sensitive figures, and nobody being able to establish afterwards who saw what. Role-based access control is therefore granular by module, machine, cell and plant, with read-only viewer roles for customers or auditors, and access is logged with user attribution.
Integration with machines is read-only by design: no control parameter is modified and nothing is written to a machine. Where a plant requires a completely isolated deployment with no outbound connection, that is supported at the cost of remote support and automatic updates — a trade some defence-linked suppliers rightly choose to make.