Integrations
How IRIS connects to your plant
Machines reach IRIS through Data Bridge over MQTT. Other software connects through the API, webhooks and file import.
- IRIS event
- Telemetry
- Unit
- °C
- IRIS event
- Station pass
- Delivery
- Delivered
A gateway reads the machine and forwards the data over MQTT.
What we connect to
Each connection falls into one of three kinds.
Works in IRIS today. You set it up in the app.
IRIS does not poll it. A gateway forwards the data over MQTT.
We set it up with you for your systems.
Shop floor
Machines, devices and vehicles
Data Bridge connects shop-floor hardware. Readings reach the IoT module over MQTT bridges or HTTP.
- Built in
MQTT bridges
Connect your MQTT broker. Mappings turn each topic into an IRIS event, which reaches IoT as a reading.
- Built in
Device registry
Each device creates its own private key and gets a certificate signed by the plant's certificate authority. The key never passes through the server.
- Built in
Firmware updates
Campaigns roll out in stages: a canary group, then 25%, 50% and 100% of the devices. Firmware files need a configured file store.
- Built in
AGVs over VDA 5050
See vehicle status and send transport orders from the fleet screen. "Sent" means the broker accepted the order, not that the vehicle finished.
- Through a gateway
PLCs, OPC UA, Modbus, BACnet
IRIS keeps a registry of OPC UA servers and Sparkplug B nodes, and holds Modbus and BACnet register maps. A gateway reads the machine and forwards the data over MQTT.
Business systems
ERP and other software
IRIS works alongside your existing systems. You keep your ERP.
- Built in
API tokens
An outside system uses a token to report output, scrap and downtime to MES.
- Built in
Webhooks
MES sends station pass, scrap, downtime and Andon events to your URL. It keeps a delivery history and retries failed deliveries.
- Built in
File import
Load production orders from CSV or XLSX. A saved column mapping and a preview come before the import.
- Built in
Report export
Reporting builds reports from module data, runs them on a schedule and exports them to XLSX, CSV and PDF.
- Set up per project
ERP link
There is no ready-made ERP connector. We build the link for your ERP with the API, webhooks and order import.
Notifications
Alerts and messages
Alerts and messages reach people inside IRIS.
- Built in
KPI alerts
A rule on a metric (threshold, deviation or anomaly) notifies the whole plant in IRIS and emails the addresses set on the rule.
- Built in
Communicator
Channels, direct messages and announcements by role, with read confirmation. Messages stay in IRIS and do not go to email, SMS, Slack or Teams.
- Built in
Tasks
Events from MES, QMS, CMMS and other modules become tasks. Routing rules decide who gets each one.
Deployment
Where IRIS runs
Choose the setup that fits your data rules.
SaaS
IRIS is a web application. People open it in a browser and install nothing on their computers.
Private cloud
IRIS can run in a dedicated private cloud for plants with strict data rules.
On-premise
IRIS can run in your own data center.
What IRIS does not do
- IRIS does not poll OPC UA, Modbus or BACnet itself. A gateway forwards the data over MQTT.
- Data Bridge keeps the last device state and message logs. History and charts are in IoT.
- A command sent to a vehicle or device goes over an integration channel. IRIS does not control machine safety.
Plan your integration
Leave your email and tell us which machines and systems you use, and we will get back to you.
Plan your integration
Tell us which machines and systems you use, and we will show you how they connect to IRIS.