IT and data connectivity
Choose a connectivity option
Compare the three ways your sites' operational data can reach DUET, and pick the one that fits your network.
The right option depends on where your data lives, your network and security requirements, and how fresh the data needs to be. Your account manager works through the choice with you, and you can use different options for different sites.
| Enurgen-managed | Customer push | On-site collector | |
|---|---|---|---|
| How it works | Enurgen reads from your cloud platform, historian, or monitoring system. | Your systems send data to the DUET ingest API. | Enurgen software on a server at your site reads the plant network and sends data out. |
| IT effort | Low: credentials and network access. | High: you build and run the pipeline. | Medium: provide a server, and allow outbound traffic. |
| Data freshness | Typically hourly. | Your schedule. | Near real time, at 1-minute resolution. |
| During a WAN outage | Data is read when the connection returns, if your source keeps it. | Depends on your pipeline. | Buffered on site, and sent when the connection returns. |
| Network exposure | None for cloud sources. A site-to-site VPN for on-premises sources. | None. | Outbound HTTPS only. |
| Best fit | Cloud platforms, historians, and monitoring systems. | Teams that want to own the integration. | OPC UA and MQTT plant networks, and restricted networks such as NERC CIP. |
To check that your platform is supported, see Data sources. If your requirements don't fit any of these options, contact your account manager.
Data stays read-only
Every option only reads from your systems. DUET doesn't write to your SCADA or control systems. To send DUET's issues, work orders, and alarms to your own systems, use webhooks.