Definition
IIoT (Industrial Internet of Things) applies IoT technology to industrial manufacturing, energy, process control, and other fields. Through industrial gateways, Modbus , OPC UA and other protocols, PLCs, instruments, and CNC machines can be connected to achieve equipment data collection, cloud upload, and factory digitization.
Technical architecture
IIoT usually includes the device layer (PLC, sensors, instruments, CNC machines), edge layer (industrial gateways, RTU , edge computing), network layer (wired/wireless, 4G/5G, LPWAN ), and platform layer (cloud platforms, MES , SCADA ). Edge gateways are responsible for protocol conversion (Modbus, OPC UA , Profibus , etc.), data preprocessing, local storage, and offline data forwarding. The platform side realizes device management, data analysis, predictive maintenance, energy management, and other functions.
Typical Applications
Remote device monitoring and predictive maintenance; production data collection and MES integration; energy monitoring and EMS optimization; quality traceability and process optimization; digital twin and simulation. IIoT is closely related to Industry 4.0 and smart manufacturing, emphasizing data-driven, flexible production, and full lifecycle management.
Protocols and standards
Common device access includes Modbus, OPC UA, Profibus, EtherNet/IP, etc.; common methods for uploading data to the cloud include MQTT, HTTP, OPC UA. OPC UA is an important standard for industrial connectivity, supporting information models and security mechanisms. Edge computing can run inference engines such as ONNX, TensorRT to achieve local AI analysis.
Edge preprocessing and how fine the upload is
The technical boundary of the industrial Internet of things is this: the field controller keeps interlocks and real-time loops, the edge gateway keeps protocol, buffering, and what to drop, and the platform keeps records and analysis across devices. How fine the upload is should follow the use. Status monitoring can use a value that changes on the order of a second or slower. If a vibration or current waveform is for diagnosis, compute the features at the edge and upload those, and send the raw waveform back only when it is asked for. Uploading everything at the fastest period fills the link and the storage with points that do not matter, and the alarm that does matter is delayed instead. While the gateway is offline it should keep timestamped data, and after the link returns it should send the backlog in time order. The platform stores by timestamp, not by arrival order.
The condition is a point list with an owner and an engineering meaning. Every point knows which address of which device it came from, its unit, its range, and whether it may be written. Clocks on the gateway, the controller, and the platform have to agree, or the order of events in a report that crosses systems is wrong. For security, remote access needs an identity and the smallest rights that will do, and there has to be a defined crossing between the production network, the office network, and the outside network. If an edge model takes part in alarming, a model that produces no result has to fall back to a threshold alarm. No result must not mean no fault.
Clock alignment and the boundary of a write
Mapping a read-only monitor point straight to a writable control point is the most serious configuration error at this layer. When a remote write sets a setpoint or forces an output by mistake, the field interlock may not know the write came from outside. A write needs at least rights, a range, a rate of change, and an operation record. A critical output should stay in the local controller, confirmed by a person on site. Another error is a sample period slower than an alarm pulse inside the controller. The platform never sees that edge, and it still shows communication as normal.
A Chinese description may be used as a point name only while debugging. Once the system is running steadily, use an identifier that does not change with the graphic, or one rename breaks the history. Byte order, word order, and analog scale differ between devices. After a gateway template is copied, the value is exactly double or the sign is reversed, and the checksum is still correct. If backlog data overwrites a record a person has already confirmed, the shift report changes. Change the model revision and the point-list revision together. Upgrading only the parser and not the point list writes a new device's points into an old device's history. What the site is allowed to do is decided by the protection in the controller. A success receipt on the platform only means the message arrived. It does not mean the device has moved safely.
Point-list revisions and the write receipt
A point's stable identifier does not follow a rename of the Chinese caption on a graphic. A rename breaks the history, and the new name looks like a new device. Byte order and scale change with the device model. After a template is copied, check it against one known instrument. A value that is double, or reversed in sign, can still have healthy communication. Store a backlog by timestamp. Do not overwrite a record a person has already confirmed, or the shift report changes after the fact.
A receipt on a write only means the message reached the gateway or the controller. It does not mean the field has moved safely. Leave a critical output in the local logic. A remote system only sends a request. A writable point needs a range, a rate of change, and an operator. A monitor point is not writable by default. When a model or a parser is upgraded, the point-list revision changes with it. Upgrading only the program writes a new address into an old point's history. Decide in advance how large the offline buffer is and which data it drops. Data after recovery carries the time it was sampled. The platform does not rebuild the order from arrival time. When the edge calculation has no result, fall back to a simple threshold. No result must not be treated as no abnormality.
Set the sample period from how the signal changes, not from the fastest rate the gateway can manage. Upload a slow variable on change. For a fast variable, compute the peak, the mean, or the features at the edge, then send them on a fixed period. Open a raw waveform only for a short time when a diagnosis needs it. Leaving it open fills the link, and alarms get slower. Data from a gateway whose clock sync has failed should be marked time-not-trusted. It cannot be placed in the same sequence as data that is already synchronized. Limit a write's range again at the gateway. Even if the platform sends a value outside the range, do not pass it through to the controller unchanged. An operation record includes the operator, the point identifier, the old value, and the new value. If the receipt fails, record which layer it stopped at. Change the point list, the parser, and the edge model together. Missing any one revision number makes it impossible later to reproduce what the number meant at the time.