Skip to content
Published on

Industrial IoT (IIoT) 2026 Complete Guide - Siemens Insights Hub, AWS IoT, Azure Digital Twins, PTC ThingWorx, Litmus, Balena, Particle, GE Vernova Deep Dive

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

Introduction: May 2026, IIoT Has Entered the "OT/IT Convergence Era"

In the early 2020s, IIoT was a simple slogan: "send sensor data to the cloud." By May 2026 the story is far more nuanced. The boundary between OT (Operational Technology, factory automation) and IT (Information Technology, enterprise IT) has dissolved, and predictive maintenance, digital twins, and edge AI inference are simultaneously standard requirements.

This article is not a marketing slide. It honestly maps the IIoT stack going into actual factories, power plants, and logistics warehouses as of May 2026 — how Siemens rebranded MindSphere as Insights Hub, where Predix went after GE's 2024 split into GE Aerospace / Vernova / HealthCare, how Azure IoT Operations and AWS IoT TwinMaker filled the gap left when Google Cloud IoT shut down in August 2023, and how far open source projects like EdgeX Foundry and Eclipse Hono have come.

IIoT Stack: Decomposed Into 7 Layers

The standard IIoT stack in 2026 splits into the following 7 layers.

  1. Field devices: sensors, PLCs, motors, drives
  2. Edge gateway: protocol conversion, local buffering, edge inference
  3. OT network: PROFINET, EtherCAT, EtherNet/IP, OPC UA, MQTT
  4. Cloud gateway: MQTT brokers, IoT Hub, message queues
  5. Data platform: time-series DB, data lake, digital twin
  6. Analytics + AI: predictive maintenance, quality inspection, optimization
  7. Apps + UI: SCADA, MES, ERP integration, AR work instructions

As inter-layer interfaces standardize, mixed-vendor stacks have become the norm. Combinations like Siemens PLC + AWS IoT Core + Azure Digital Twins + PTC ThingWorx apps are common in the wild.

Siemens Industrial Edge + Insights Hub: "MindSphere" Is Gone and Reorganized

Siemens rebranded its cloud IoT platform MindSphere as Insights Hub in 2023, and simultaneously split out the edge track as Industrial Edge and the AI track as Industrial AI Suite. As of May 2026, the lineup is:

  • Industrial Edge: container-based edge platform deployed on the factory floor. Runs on Siemens IPCs or third-party industrial PCs. An app marketplace ships OPC UA, data acquisition, and vision AI apps.
  • Insights Hub (formerly MindSphere): SaaS hosted on AWS or Alibaba Cloud. Asset modeling, time-series data, predictive maintenance analytics.
  • Industrial AI Suite: in-house AI model lifecycle. Integrates Siemens Senseye Predictive Maintenance.
  • Xcelerator: a digital business platform that bundles the above with SIMATIC, TIA Portal, NX, and Teamcenter.

A typical Insights Hub API call looks like this.

import requests

tenant = "mycompany"
token = "<oauth_token>"
asset_id = "asset-123"

resp = requests.get(
    f"https://gateway.eu1.mindsphere.io/api/iottimeseries/v3/timeseries/{asset_id}/Temperature",
    headers={"Authorization": f"Bearer {token}"},
    params={"from": "2026-05-15T00:00:00Z", "to": "2026-05-16T00:00:00Z"},
)
for point in resp.json():
    print(point["_time"], point["temperature"])

The strength of Industrial Edge is its deep integration with Siemens PLCs. Data from SIMATIC S7-1500/1200 and ET 200SP distributed IO is standardized via OPC UA and shipped to the cloud. The downside is vendor lock-in — Insights Hub forces its own time-series model on you.

GE Vernova / GE Digital Predix: The Landscape After the 2024 GE Split

GE officially split into GE Aerospace (aircraft engines), GE Vernova (power/energy), and GE HealthCare (medical) in April 2024. The IIoT assets mostly went to GE Vernova.

  • GE Digital Predix: moved under GE Vernova. An industrial OS for power generation, wind, and gas turbines.
  • APM (Asset Performance Management): power plant asset management SaaS.
  • GridOS: transmission/distribution grid operational digital twin.
  • Proficy: HMI/SCADA line — iFIX, Cimplicity, Historian.

GE Vernova is now positioned as an IIoT vendor specialized in power plants and utilities. The era when Predix was advertised as the "Android of industry" is over. In general manufacturing, Siemens Insights Hub, PTC ThingWorx, and AWS/Azure took its seat.

PTC ThingWorx + Vuforia + Kepware: Industrial Data Platform + AR

PTC's IIoT portfolio rests on three pillars.

  • ThingWorx: industrial data modeling + app platform. Build low-code apps in Composer.
  • Kepware: an OPC UA / 200+ industrial protocol gateway. Bridges PLCs, DCS, and RTUs to the cloud.
  • Vuforia: industrial AR. Overlays step-by-step work instructions on a 3D model for the operator.

The strength of ThingWorx is that, paired with Kepware, it absorbs nearly every industrial protocol. Modbus, PROFINET, EtherNet/IP, S7, Allen-Bradley, Honeywell Experion, DNP3 — all unified to OPC UA from a single gateway.

PTC also pushes the digital thread narrative by combining with PTC FlexPLM (product lifecycle management). The picture is a single line of data from design through manufacturing through service.

Hitachi Lumada: Strong IIoT Player in Asia

Hitachi Lumada has a strong presence in Japan and the wider Asian IIoT market. As of May 2026 its components are:

  • Lumada Data Hub: data integration + catalog.
  • Lumada Manufacturing Insights: manufacturing data analytics SaaS.
  • Lumada Energy Insights: energy / utilities.
  • Lumada Industrial DataOps: data pipelines + AI training.

Hitachi reinforced its digital engineering capability with the 2023 GlobalLogic acquisition, and is expanding grid-side IIoT around Hitachi Energy through 2025. Major customers include Nippon Steel, JFE, and Kawasaki Heavy Industries.

Schneider EcoStruxure: Unified Energy + Building + Industry Platform

Schneider Electric's EcoStruxure is an IIoT platform that layers three tiers (Connected Products, Edge Control, Apps/Analytics) on top of four domains (Building, Data Center, Industry, Power).

  • EcoStruxure Machine Advisor: remote monitoring for machine OEMs.
  • EcoStruxure Plant: integrated operations for process industries (petrochemicals, mining).
  • EcoStruxure Power Monitoring Expert: power quality management.
  • AVEVA System Platform: after Schneider's 2023 acquisition, SCADA + HMI + Historian unified.

With the AVEVA acquisition, Schneider brought OSIsoft PI System (the de-facto time-series data standard) into its camp. PI System is the de facto standard in power plants, oil fields, and mines.

ABB Ability + Honeywell Forge + Rockwell FactoryTalk

Each of these three vendors put a cloud IIoT track on top of its existing DCS/SCADA line.

  • ABB Ability: a full stack of 800xA DCS + Edge + Cloud. Strong in power, mining, chemicals.
  • Honeywell Forge: Experion DCS + Forge cloud. Strong in refining, gas, power generation.
  • Rockwell FactoryTalk: Allen-Bradley PLCs + FactoryTalk Hub + Plex MES (after Plex Systems acquisition in 2021).

Rockwell strengthened the OT cybersecurity track via the 2023 Verve Industrial Protection acquisition, and extended into the AMR (autonomous mobile robot) space via the 2024 Clearpath Robotics acquisition.

Bosch IoT Hub + Bosch Phantom Edge: IIoT From an Automotive OEM Heritage

Bosch's IIoT story starts in automotive OEM parts supply chains.

  • Bosch IoT Suite: device management + message routing + twin. Built on Eclipse Hono / Ditto / Hawkbit.
  • Bosch Phantom Edge: edge computing platform announced in 2024. Container-based + ML inference.
  • Bosch Connected Industry: a self-developed manufacturing execution software line called Nexeed.

Bosch open-sourced a large part of its IoT code into the Eclipse Foundation. This is the origin of Eclipse Hono (IoT messaging protocol adapter), Eclipse Ditto (digital twin), Eclipse Hawkbit (OTA update), and Eclipse Kura (Java-based edge gateway).

AWS IoT Core / SiteWise / TwinMaker / Greengrass: Hyperscaler Number One

AWS IoT is built from five services.

  • AWS IoT Core: device message broker over MQTT/HTTPS. Scales to billions of devices.
  • AWS IoT SiteWise: industrial asset modeling + time-series data. Native time-series DB + statistical transformations.
  • AWS IoT TwinMaker: digital twin. 3D model + real-time data + business logic.
  • AWS IoT Greengrass: edge runtime. Deploys Lambda functions and ML models to the edge.
  • AWS IoT FleetWise: vehicle data collection (automotive OEM focused).

A SiteWise asset model definition looks like this.

{
  "assetModelName": "TurbineModel",
  "assetModelProperties": [
    {
      "name": "Temperature",
      "dataType": "DOUBLE",
      "type": {
        "measurement": {}
      }
    },
    {
      "name": "AvgTemperature15min",
      "dataType": "DOUBLE",
      "type": {
        "metric": {
          "expression": "avg(temp)",
          "variables": [
            {"name": "temp", "value": {"propertyId": "Temperature"}}
          ],
          "window": {"tumbling": {"interval": "15m"}}
        }
      }
    }
  ]
}

The strength of AWS IoT is integration with the wider AWS ecosystem. The flows SiteWise → S3 → Athena/QuickSight and Greengrass → SageMaker Edge Manager (phased out in 2024, replaced by Greengrass ML Component) just work end to end.

Azure IoT Hub / Digital Twins / IoT Operations: New K8s-Based Line in 2024

Azure IoT's core is:

  • Azure IoT Hub: device broker over MQTT/AMQP/HTTPS. Classic.
  • Azure Digital Twins: digital twin based on DTDL (Digital Twin Definition Language).
  • Azure IoT Operations (GA 2024): K8s/Arc-based edge platform. Integrates MQTT broker + OPC UA + Akri + Dapr.
  • Azure IoT Edge: classic edge runtime. Gradually migrating to IoT Operations.
  • Azure Sphere: secure microcontroller + OS (end-of-life announced for September 2027).

The arrival of IoT Operations is a big shift. Kubernetes (managed via Azure Arc) is installed at the edge, and on top of it, an MQTT broker (EMQX-based), OPC UA Connector, Data Processor, and Akri (edge device discovery) are deployed as containers.

A DTDL digital twin definition looks like this.

{
  "@context": "dtmi:dtdl:context;3",
  "@id": "dtmi:com:example:Turbine;1",
  "@type": "Interface",
  "displayName": "Wind Turbine",
  "contents": [
    {
      "@type": "Property",
      "name": "model",
      "schema": "string"
    },
    {
      "@type": "Telemetry",
      "name": "rotationSpeed",
      "schema": "double"
    },
    {
      "@type": "Relationship",
      "name": "rel_has_blades",
      "target": "dtmi:com:example:Blade;1"
    }
  ]
}

Azure's differentiator is the DTDL standard. The spec influenced ISO/IEC 30173 and stands alongside AAS (Asset Administration Shell) as one of the digital twin standardization axes.

Google Cloud IoT Shut Down in August 2023: The Vacuum Since

Google announced the end of Google Cloud IoT Core in August 2022, and the service was fully terminated on August 16, 2023. Existing customers were guided to migrate to ClearBlade, EMQX Cloud, or HiveMQ Cloud.

As of May 2026, Google Cloud does not directly provide an IoT device gateway SaaS. Instead it recommends:

  • Pub/Sub + Cloud IoT partners: ClearBlade IoT Core is the first-choice alternative in the Google Cloud Marketplace.
  • Self-hosted MQTT brokers on GKE + Anthos: deploy HiveMQ, EMQX, or Mosquitto to GKE.
  • Vertex AI: continue using it for device training and inference.

With Google exiting the IoT device gateway market, the AWS-vs-Azure duopoly has strengthened. That said, Google's BigQuery + Vertex AI track is still frequently used as an IIoT analytics backend.

EdgeX Foundry: LF Edge's Open Edge Platform

EdgeX Foundry is the open-source IoT/IIoT edge platform under LF Edge. Starting in 2017 from code Dell contributed, the stable line as of May 2026 is Odessa (3.1).

  • Device Service: device adapters for Modbus, MQTT, OPC UA, SNMP, REST, and more.
  • Core Services: Command, Data, Metadata microservices.
  • Application Services: export data to cloud / MQTT / HTTPS.
  • Support Services: scheduler, notifications, logging.
  • Security Services: Vault-based secrets management.

The strength of EdgeX is vendor-neutral open source. While AWS Greengrass and Azure IoT Edge bind you to a specific cloud, EdgeX can send data anywhere.

Bringing up EdgeX with Docker Compose goes like this.

git clone https://github.com/edgexfoundry/edgex-compose
cd edgex-compose/compose-builder
make run no-secty
curl http://localhost:59880/api/v3/ping
curl http://localhost:59881/api/v3/reading/all

Besides EdgeX, LF Edge also hosts Akraino (telco edge), Project EVE (edge virtualization), and Fledge (industrial data OS).

Eclipse Hono · Ditto · Hawkbit · Kura · Kapua

The Eclipse Foundation hosts the core IIoT infrastructure as open source.

  • Eclipse Hono: a unified message broker for MQTT/AMQP/HTTP/CoAP/LwM2M. Kubernetes-native.
  • Eclipse Ditto: a digital twin backend. Thing/Feature model with WebSocket/HTTP/MQTT interfaces.
  • Eclipse Hawkbit: OTA (Over-The-Air) update management for devices, with rollback and campaign control.
  • Eclipse Kura: a Java-based edge gateway runtime. OSGi-modular.
  • Eclipse Kapua: device management + data + telemetry.
  • Eclipse Leshan: an LwM2M server implementation.
  • Eclipse Tahu: a Sparkplug B reference implementation.

Bosch IoT Suite is a commercial SaaS layered on Hono + Ditto + Hawkbit, and VMware Tanzu's IoT track is also built on the Eclipse stack.

Apache PLC4X · StreamPipes · OpenEMS: The Apache Foundation Industrial Track

The Apache Foundation also hosts growing IIoT projects.

  • Apache PLC4X: an industrial PLC protocol library. Modbus, S7, OPC UA, EtherNet/IP, ADS, KNX, and more — usable from Java / Go / Python / C.
  • Apache StreamPipes: industrial data stream processing + visualization. A low-code pipeline builder.
  • Apache OpenEMS: energy management system. Battery, PV, grid monitoring and control.
  • Apache Iceberg, Apache Druid, Apache Pinot: commonly used as analytics backends for industrial time-series data.

PLC4X Modbus read example.

PlcConnectionManager mgr = PlcConnectionManager.getDefault();
try (PlcConnection conn = mgr.getConnection("modbus-tcp:tcp://192.168.1.10:502")) {
    PlcReadRequest req = conn.readRequestBuilder()
        .addItem("temperature", "holding-register:100:UINT")
        .addItem("pressure", "holding-register:101:UINT")
        .build();
    PlcReadResponse resp = req.execute().get();
    System.out.println("temp=" + resp.getInteger("temperature"));
    System.out.println("pressure=" + resp.getInteger("pressure"));
}

PLC4X is the friendliest entry point for developers unfamiliar with industrial protocols.

OPC UA: IEC 62541, the De Facto Standard of Industrial Automation

OPC UA (Open Platform Communications Unified Architecture) is an industrial automation communications protocol standardized as IEC 62541. As of May 2026, OPC UA has become the lingua franca of IIoT.

Its key characteristics are:

  • Vendor-neutral: Siemens, Rockwell, Schneider, and ABB all support OPC UA.
  • Object-oriented information model: type system and node graph.
  • Built-in security: X.509 certificates, user tokens, message signing and encryption.
  • Client/Server + Pub/Sub: since 2018 a Pub/Sub mode over MQTT/AMQP has been added.
  • Companion Specifications: industry-specific information model standards (PackML, EUROMAP, Robotics, Machinery, and more).

An OPC UA Python client (open62541 or asyncua) example.

import asyncio
from asyncua import Client

async def main():
    url = "opc.tcp://192.168.1.20:4840"
    async with Client(url=url) as client:
        root = client.get_root_node()
        temp_node = await client.nodes.objects.get_child(["2:Plant", "2:Reactor1", "2:Temperature"])
        value = await temp_node.read_value()
        print(f"temperature={value} C")

asyncio.run(main())

OPC UA Pub/Sub mode layers OPC UA messages on top of MQTT 5.0 and has become the primary field-to-cloud communication protocol.

MQTT 5.0 + Sparkplug B: The IIoT Message Layer

MQTT is the simplest option for an IoT message protocol. MQTT 5.0 (2019) added properties, reason codes, shared subscriptions, and request/response, and from there it became a serious option for industrial use too.

Sparkplug B is an Eclipse Foundation standard that defines industrial message semantics on top of MQTT.

  • NBIRTH/NDEATH/DBIRTH/DDEATH: node/device birth-and-death signals.
  • NDATA/DDATA: data change notifications.
  • NCMD/DCMD: command messages.
  • State model: the STATE topic tells you whether a node is alive.

Sparkplug B is supported by Inductive Automation Ignition, HiveMQ Sparkplug Edition, AWS IoT Sparkplug Adapter, and Cirrus Link IoT Bridge. The standard line as of May 2026 is Sparkplug B 3.0.

An MQTT 5.0 + Sparkplug B publish in Python (paho-mqtt with a simplified payload).

import paho.mqtt.client as mqtt
import json
from datetime import datetime

client = mqtt.Client(client_id="edge-01", protocol=mqtt.MQTTv5)
client.username_pw_set("plant-user", "secret")
client.connect("broker.factory.local", 1883)

payload = {
    "timestamp": int(datetime.now().timestamp() * 1000),
    "metrics": [
        {"name": "Temperature", "value": 75.3, "type": "Double"},
        {"name": "Pressure", "value": 1.04, "type": "Double"},
    ],
    "seq": 42,
}
client.publish("spBv1.0/Plant1/DDATA/EdgeNode01/Reactor1", json.dumps(payload), qos=1)

In real Sparkplug B you use Protobuf encoding, but the JSON above shows the semantic model in a simplified form.

Modbus / PROFINET / EtherCAT / EtherNet/IP / DDS / LwM2M

Before OPC UA and MQTT — and still today alongside them — there are the industrial protocols.

  • Modbus RTU/TCP: a simple protocol Modicon created in 1979. Serial or TCP. The most widely deployed legacy.
  • PROFINET: Siemens-centric. Standard Ethernet plus real-time extensions (IRT). The de facto standard in automotive factories.
  • EtherCAT: Beckhoff. Microsecond-class real-time. Strong in motion control.
  • EtherNet/IP: ODVA plus Rockwell. Based on CIP (Common Industrial Protocol).
  • DNP3: standard for power plant and transmission line operations.
  • DDS (Data Distribution Service): an OMG standard. Core to autonomous driving, defense, medical. RTI Connext, Eclipse Cyclone DDS.
  • LwM2M (OMA Lightweight M2M): device management protocol for low-power devices.
  • CoAP (Constrained Application Protocol): REST-style but UDP-based lightweight protocol.

Gateways typically translate these to OPC UA or MQTT using products like Kepware, HMS Anybus, Moxa MGate, Red Lion, and WAGO PFC.

Embedded + Gateway Hardware: Simatic IPC, Advantech, Beckhoff

Hardware that goes into an industrial site is different from a regular PC. IP65/67 dust/water sealing, -40 to +70 C operation, vibration resistance, and 100,000-hour MTBF are baseline.

  • Siemens SIMATIC IPC: industrial PC line. Industrial Edge compatible.
  • Advantech: a Taiwanese industrial PC + gateway powerhouse. UNO, EKI series.
  • Beckhoff: PC-based automation. TwinCAT software PLC.
  • B&R Automation: ABB Group. APROL DCS + X20 PLC.
  • Phoenix Contact: terminal blocks + industrial PCs + 5G routers.
  • WAGO: distributed IO + PFC controllers. A Linux-based PLC.
  • Cradlepoint (Ericsson Enterprise Wireless), Sierra Wireless (acquired by Semtech): cellular IoT gateways.

The 5G + industrial PC combination has entered factories in earnest since 2024. 5G NR-Reduced Capability (RedCap) and 5G Advanced (Release 18) are the new circuit options for industrial IoT.

Balena · Particle.io · Golioth · Memfault: Device-to-Cloud SaaS

Beyond enterprise IIoT, there is a SaaS layer that targets OEM device makers.

  • Balena (balena.io): Linux device fleet management. balenaOS + balenaCloud + balenaEngine (Docker-compatible).
  • Particle.io: cellular IoT microcontrollers (Photon 2, Boron, Tracker) + cloud + Pub/Sub.
  • Golioth: device management for Zephyr-RTOS-based microcontrollers.
  • Memfault: observability for embedded devices — crash reporting, OTA, metrics.
  • Toit: containers and a custom language for microcontrollers.
  • Mongoose OS: an IoT framework for embedded devices.

Creating a Balena fleet and adding a device looks like this.

balena login
balena fleet create my-fleet --type raspberrypi4-64
balena os download raspberrypi4-64 -v default -o resin.img
balena os configure resin.img --fleet my-fleet
balena push my-fleet

Memfault has become the de facto standard for firmware crash reporting. Zephyr, FreeRTOS, and Linux are all supported, and firmware updates plus boot logs plus metrics live in one view.

Litmus Edge · HiveMQ · EMQX: MQTT Brokers + Industrial Data OS

MQTT brokers are the heart of IIoT message infrastructure.

  • Litmus Edge: an industrial DataOps platform. OPC UA, Modbus, MQTT, REST — 50+ protocols + data transformations + ML inference.
  • HiveMQ: enterprise MQTT broker. Clustering, Kafka bridge, Sparkplug support. Self-hosted or Cloud.
  • EMQX: open-source MQTT broker. Erlang-based, distributed clustering. EMQ X Enterprise Edition + Cloud.
  • Mosquitto: the single-node open-source MQTT broker under the Eclipse Foundation. De facto standard for small and edge cases.
  • VerneMQ: Erlang-based distributed MQTT broker.
  • NanoMQ: ultra-lightweight MQTT broker for edge / embedded.

Deploying an EMQX cluster on Kubernetes goes like this.

apiVersion: apps.emqx.io/v2beta1
kind: EMQX
metadata:
  name: emqx-cluster
spec:
  image: emqx/emqx:5.7.0
  coreTemplate:
    spec:
      replicas: 3
      resources:
        limits:
          cpu: "2"
          memory: 4Gi
  replicantTemplate:
    spec:
      replicas: 2
  listenersServiceTemplate:
    spec:
      type: LoadBalancer

Litmus Edge has grown quickly by carving out the industrial data standardization niche. The company drew attention with Snowflake's failed acquisition attempt in 2024.

NVIDIA Jetson + Metropolis + Omniverse: Edge AI + Digital Twin

NVIDIA has a foot in both IIoT axes.

  • Jetson Orin/Thor: edge AI computers. Orin Nano/NX (low power), Orin AGX (high performance), Thor (released in 2026).
  • Metropolis: vision AI platform. DeepStream + NIM (NVIDIA Inference Microservices).
  • Omniverse Industrial: industrial digital twin based on USD (Universal Scene Description).
  • Isaac: robotics. Isaac Sim, Isaac ROS.
  • Project GR00T: humanoid robot foundation models (announced 2024).

Omniverse + USD has emerged since 2024 as a candidate standard for industrial digital twins. The picture is to standardize models built in Siemens NX, PTC Creo, and Autodesk Inventor as USD and merge them in Omniverse.

Jetson edge inference is typically structured as NVIDIA TensorRT + DeepStream + Triton. Compile an ONNX model with TensorRT, then run vision inference in a DeepStream pipeline (GStreamer-based).

Intel OpenVINO + TinyML + Edge Impulse: Non-NVIDIA Edge AI

There is also a non-NVIDIA edge AI track.

  • Intel OpenVINO: ML inference on Intel CPU/GPU/VPU and ARM. OpenVINO Model Server.
  • TensorFlow Lite + LiteRT (the new name for TFLite as of 2024): TF runtime for mobile and edge.
  • TensorFlow Lite Micro: for microcontrollers (Cortex-M, ESP32).
  • Edge Impulse: TinyML training SaaS. Integrated with Arduino, Nordic, and ST chips.
  • ONNX Runtime: model format standard + runtime.
  • Apache TVM: model compiler with multi-backend support.
  • Glow (PyTorch), MLIR: compiler infrastructure.

OpenVINO often appears in Intel NUC + industrial vision inspection. GPU performance is weaker than Jetson, but the CPU + iGPU + Movidius VPU combination delivers low power and reasonable performance.

ISA-95 · IEC 62443 · NAMUR · OPC UA Companion Specs: Industrial Standards

IIoT sits on top of standards.

  • ISA-95 (IEC 62264): enterprise/control integration. 5-level model (L0 sensor → L4 ERP). Defines the MES-ERP interface.
  • ISA-88 (IEC 61512): batch control standard.
  • ISA-99 / IEC 62443: OT cybersecurity. Defines security levels (SL 1-4).
  • IEC 61131-3: PLC programming language standard (LD, ST, FBD, IL, SFC).
  • IEC 61499: distributed automation function blocks.
  • NAMUR Open Architecture (NOA): reference IIoT architecture for the chemical / process industries.
  • OPC UA Companion Specifications: industry-specific information models. AutoML, PackML, EUROMAP, Robotics, Machinery, Weihenstephan Standards, and more.
  • Asset Administration Shell (AAS, IEC 63278): the asset administration shell — the digital twin standard for Industrie 4.0.

ISA-95 is cited almost always in ERP-MES-PLC integration projects. As of May 2026, the three axes AAS + DTDL + OPC UA are competing side by side as the digital twin standardization.

OT Cybersecurity: Claroty · Dragos · Nozomi · Armis · TXOne

As IIoT spreads, OT cybersecurity has become a market in its own right. As of May 2026 the top five are:

  • Claroty: xDome + xDome Secure Access + Medigate (medical IoT). Schneider Electric is a shareholder.
  • Dragos: ICS/OT threat intelligence + platform. Strong in power and petrochemicals.
  • Nozomi Networks: Guardian + Vantage. Industrial network visibility.
  • Armis: unified asset intelligence across IT/OT/IoT/IoMT.
  • TXOne Networks: Trend Micro and Moxa JV. OT endpoint + network.

IEC 62443 is the consistency baseline for these tools. An assurance that layers SOC 2 + ISO 27001 with IEC 62443 is now the standard requirement in OT security RFPs.

The core of OT security is passive monitoring. Active scans can knock out PLCs, so the standard approach is to read traffic from a network mirror port and infer assets and vulnerabilities from there.

Korean IIoT: Posco, Hyundai, CJ Logistics, LG CNS, Samsung SDS

The Korean IIoT ecosystem is built around the following:

  • Posco DX (formerly Posco ICT): IIoT for POSCO steel. Their in-house PosFrame platform.
  • Hyundai Motor + Kia: HMG smart factory. E-FOREST, Singapore EVI digital twin cases.
  • Hyundai Steel: own IoT platform mixed with AWS IoT.
  • CJ Logistics TES: logistics IIoT. Unified operations of autonomous forklifts and AGVs.
  • LG CNS: own Cityhub IoT platform + AWS / Azure adoption.
  • Samsung SDS: Brightics IoT + custom device security.
  • Doosan Enerbility, Hanwha Aerospace, KT + the three Korean telcos in 5G B2B: 5G-based smart factory cases.

LS ELECTRIC (formerly LS Industrial Systems), with its LG Industrial Systems heritage in PLCs and HMIs, is also a notable axis of Korean IIoT. They own the XGB PLC series and their own SCADA (XGI Studio).

Japanese IIoT: Mitsubishi Connected Industries, Yokogawa, NTT Com

The Japanese IIoT ecosystem stands out for:

  • Mitsubishi Electric e-F@ctory + Connected Industries: MELSEC PLC + iQ Platform + EDGECROSS.
  • Yokogawa SushiSensor + OpreX: wireless vibration / temperature sensors. CENTUM VP DCS.
  • NTT Communications Smart Factory + Sky Hub: carrier-led IIoT.
  • Hitachi Lumada: the group-level IIoT covered above.
  • Toshiba IoT Reference Architecture (TIRA): power and infrastructure.
  • Fujitsu COLMINA: manufacturing + IoT data integration.
  • OMRON i-Automation!: Sysmac controllers + AI controllers.
  • Toyota Production System AI + TPS Digital: Toyota's own IIoT.
  • EDGECROSS Consortium: a consortium of Japanese manufacturers for industrial edge standards.

Japan has its own EDGECROSS standard complementing OPC UA, and OPC UA / Sparkplug B Japanese tutorials on Qiita and Zenn have proliferated rapidly through 2026.

Adoption Roadmap: From Zero to IIoT Production

The safest order when starting an IIoT project from scratch is:

  1. Data acquisition first. Pull data from one PLC over OPC UA. 1-2 weeks.
  2. Time-series DB for storage. AWS Timestream, Azure Time Series Insights, InfluxDB, TimescaleDB.
  3. Simple dashboard. Grafana or Power BI. Line charts and alarms.
  4. Edge gateway. EdgeX, Eclipse Kura, AWS Greengrass, Azure IoT Edge.
  5. MQTT broker. HiveMQ/EMQX or a managed IoT Hub.
  6. Digital twin. Azure Digital Twins, AWS IoT TwinMaker, Eclipse Ditto.
  7. AI/ML. Last. Train a predictive maintenance model after 6 months or more of data.

Installing all seven from day one is a recipe for failure. The settled wisdom is to start with one PLC + one metric + one dashboard, then expand.

Frequently Asked Questions (FAQ)

Q1. Is MindSphere gone?

A. It was rebranded. Siemens renamed MindSphere as Insights Hub in 2023, and simultaneously split off Industrial Edge (edge) and Industrial AI Suite (AI). Existing MindSphere customers were migrated to Insights Hub.

Q2. Why did Google Cloud IoT Core shut down?

A. The stated rationale in Google's August 2022 announcement was that "customers' IoT needs can be met by our core cloud data analytics and ML services." The service was fully terminated on August 16, 2023. As a result, the AWS-vs-Azure duopoly in IoT has strengthened.

Q3. Where did GE Predix go?

A. After the 2024 GE split, Predix moved under GE Vernova (power/energy). In the general manufacturing IIoT market, Siemens Insights Hub, PTC ThingWorx, and AWS/Azure took its place.

Q4. OPC UA or MQTT — which should I choose?

A. Use both. OPC UA is typically used in field communications (PLC to gateway), and MQTT is typically used for gateway-to-cloud communications. OPC UA Pub/Sub mode layers OPC UA messages on MQTT and lets you use both at once. Sparkplug B is the industrial-semantic standard on top of MQTT.

Q5. Industrial Edge vs Greengrass vs Azure IoT Operations — which is best?

A. It depends on your preferred cloud. If AWS, go with Greengrass; if Azure, IoT Operations (K8s-based) or IoT Edge (classic); if you live in the Siemens world, Industrial Edge. They all integrate deeply with their respective clouds, but you can reduce lock-in by abstracting data through a neutral layer like EdgeX.

Closing: May 2026, IIoT Cannot Be Finished With One Vendor

The conclusion of this article is simple. IIoT cannot be finished with a single vendor. Mixed stacks like Siemens PLC + AWS IoT Core + Azure Digital Twins + PTC ThingWorx are the new normal, and standards (OPC UA, MQTT, Sparkplug B, DTDL, AAS, ISA-95, IEC 62443) are what make that mixing possible.

The biggest shift is the acceleration of edge computing. During 2024-2025, NVIDIA Jetson, Azure IoT Operations (K8s), and AWS Greengrass all firmed up their edge tracks simultaneously. The era of shipping everything to the cloud is over; the standard pattern is to run ML inference at the edge and send only the result.

Don't get stuck on tool selection. Just by starting with "one PLC + OPC UA + a time-series DB + one dashboard", you've solved 80% of the problem. The rest is a question of priorities and security requirements.

References

Discuss on Twitter • View on GitHub