A plant's direct VPN connection that is up but no longer carrying traffic can now be restarted from the plant's "Remote Access" tab, through "Restart VPN service" in that connection's menu. Only that one connection restarts, while the plant's other VPN connections and its data collection keep running.
The "Connections" page now has a "Topology" tab that draws each plant as a ring chart: its link to Mirox, its on-site agent, the VPN it is reached through, the devices on its network and the data loggers behind them. When a plant goes quiet, the chart shows which link broke.
Before a subnet is added or removed, the page shows how many of the plant's devices sit inside a subnet being removed, and that the plant's on-site agent restarts with the new settings. A warning appears if a subnet overlaps another plant's subnet on the same VPN, or the plant's own direct connection.
A plant's network is now scanned on a schedule: hourly for small networks, daily for larger ones, and not automatically when the network is too large. While a scan runs, the Networking page shows which step it is on, how much of the network it has checked and how many devices it has found.
On a plant's Dataflow page, the address of a device found on the plant network now opens the device's own web interface through Mirox. That access can be switched off for a single device with "Web UI Proxy".
Each plant now has a "Networking" page listing its network devices, with whether each was reachable, how fast it answered and how many checks got no reply over the last hour, 24 hours or 30 days. "Discover" starts a scan, "Add Device" takes an IP address, and the on-site agent adds devices it finds.
A "Connections" entry in the main menu lists an organization's VPN services, plants and data loggers with their availability. Its "Live" tab shows everything that has been offline for more than 15 minutes, and which plants, loggers and components are affected.