Where each piece runs.
Draw this with your OT team before the pilot. Nothing is installed on PLCs, Site Runtimes only open outbound connections, and process history stays in the plant.
Control Plane (optional)
Fleet health and license for multi-plant companies. Runs in our cloud or your data centre. Never receives process data.
Nothing installed
Engineers' Claude or Cursor and your ERP, MES or data platform connect to the plant hub from here over HTTPS.
Plant hub, one per plant
Console, plant model, historian, trends, alarms, Rules and the MCP server. mii Lite on one Windows PC, Linux server or single-node k3s; or the Enterprise stack on Kubernetes.
Site Runtime, one or more
Polls PLCs and buffers four hours on disk. Built into mii Lite; on Enterprise, one per area or line on a Linux edge box or industrial PC. Outbound to the hub only.
Nothing installed
SCADA and HMIs stay as they are. The Site Runtime can read the same tags over OPC UA or Modbus where allowed.
Nothing installed
No agents or firmware changes on PLCs, CNCs or robots. They are read over S7, Modbus, EtherNet/IP or OPC UA.
Small site
mii Lite
The hub and a built-in Site Runtime as one service: a Windows service, a Linux systemd service or one k3s pod. Same package, same steps.
Typical plant
Enterprise on Kubernetes
Each part scales on its own: a hub in the DMZ with ClickHouse history and a Site Runtime per area or line.
Several plants
One hub per plant
Each plant keeps its own hub and history. The optional Control Plane shows them all in one place.