On-site collector
Run Enurgen's collector inside your network to read plant data locally and send it to DUET over outbound HTTPS.
In this option, Enurgen installs a software collector on a server inside your network. The collector reads from your plant systems locally, and sends the data to DUET over outbound HTTPS. Your network accepts no inbound connections.
Choose this option for plant networks that can't be reached from the cloud, such as networks under NERC CIP, and when you need data in near real time.
What it reads
- OPC UA servers, including Ignition and other SCADA systems that serve OPC UA.
- MQTT brokers using Sparkplug B.
- To fill in history from before the collector was installed, it can also read an Ignition tag historian database on MySQL or SQL Server.
The collector only reads. It never writes values to your OPC UA server or SCADA system.
What you provide
- A Linux server or virtual machine on a network that can reach your plant systems, with Docker installed. Your account manager confirms the size for your sites.
- Read-only access to each source, such as an OPC UA endpoint and user, or MQTT credentials.
- Outbound HTTPS on port 443 to
*.enurgen.comand to Enurgen's storage endpoint, which your account manager gives you. The collector can send traffic through your HTTP proxy. - Remote access for Enurgen to install and update the collector, agreed with your security team.
How data reaches DUET
- The collector reads your sources, and stores each reading on the server.
- It rolls readings up to 1-minute values, and writes them to compressed files.
- It sends each file to DUET over HTTPS.
Network outages
The collector keeps reading and storing data while the connection to DUET is down. When the connection returns, it sends everything it stored since the last successful delivery, so outages don't leave gaps in DUET.