English 
Français 
Español 
Deutsch 
Português 
Italiano 
العربية Connect · OPC UA
OPC UA factory data, streamed into one platform
Most factory equipment already exposes its data over OPC UA. An OPC-UA-to-MQTT bridge subscribes to the nodes you care about and publishes them as JSON over MQTT into Kilo — no changes to PLC programs, no touching the control network.
Connect · OPC UA
How OPC UA data reaches Kilo
Bridge OPC UA to MQTT
Bridge software — OPC Router, FactoryStudio, or a Sparkplug B edge node — subscribes to OPC UA nodes on the plant network.
Publish JSON to a broker
Values publish as JSON to your own broker or a Cloud MQTT endpoint. Sparkplug B Protocol Buffers must be translated to JSON at the edge — the platform’s connector consumes JSON.
Map machines to devices
Each machine or line becomes a device; cycle times, temperatures, counters, and states map to normalized metrics for dashboards, rules, and alarms.
Connect · OPC UA
OPC UA integration specs
- Brownfield-friendly
- No PLC reprogramming. The bridge subscribes to the OPC UA server your equipment already runs — the control layer stays untouched.
- Bridge options
- OPC Router, FactoryStudio, and Sparkplug B edge nodes such as Ignition Edge or Cirrus Link gateways are the established choices.
- JSON at the edge
- The MQTT connector does not decode Sparkplug B Protocol Buffers — the edge gateway must translate them to JSON, a standard option in most commercial gateways.
- Topic conventions
- Hierarchical shapes like plant/line/machine/data keep registration pattern-friendly: one topic pattern covers every machine on a line.
- Reliability
- QoS 1 delivery, last-will status messages, and local buffering during broker outages are standard features of commercial edge gateways.
Connect · OPC UA
What your OPC UA data feeds
Connect · OPC UA
OPC UA integration FAQ
Does Kilo connect to OPC UA servers directly?
No. Kilo’s native connectors are LoRaWAN/mioty, MQTT, and vehicle trackers. OPC UA data reaches the platform through an OPC-UA-to-MQTT bridge on the plant network — the established pattern for brownfield cloud integration.
Do I need to change my PLC programs?
No. The bridge subscribes to nodes on the existing OPC UA server. Nothing in the control logic changes, and the bridge can be scoped to read-only access.
Does Kilo support Sparkplug B?
The MQTT connector consumes JSON. Sparkplug B payloads are Protocol Buffers, so the edge gateway must translate them to JSON before publishing — Ignition Edge, Cirrus Link modules, and OPC Router all offer this as a standard configuration option.
What can I do with the data once it’s in?
Live dashboards per line, rules that catch abnormal cycle times or temperatures, alarms that escalate to the right shift, and an AI assistant you can ask about any machine’s history — all on the same platform as your other sites and sensors.
Get your lines on one screen
Start free and bridge your first OPC UA nodes — or book a call and we’ll plan the bridge and topic design with your automation team.