SCADA Client
Finds the server, and keeps the terminal in step with it
Registers a terminal with its SCADA server, keeps it configured, and tells the operator when the connection is lost.
Server discovery
DHCP options first, then mDNS, so a terminal finds its server on a network it was not configured for.
Configuration from the server
Pages, application type, station name and whether the terminal is secure, all decided centrally and applied without a visit.
State everything else reads
Connection state, station name, last contact and the server URLs are published for the browser, the web interface and the notifier.
Visible when it matters
A tray indicator and an on-screen notifier show the operator the connection state, and a reboot requested by the server is announced rather than sprung.
Survives a server that is not there
The last known configuration is kept on disk, so a terminal that reboots without a server still comes up as itself.
A terminal is installed by plugging it in. This finds the SCADA server on its own — by DHCP option or by mDNS — registers the terminal, and receives its configuration: which pages it shows, which application it runs, whether it is a secure terminal, and what it is called.
It then stays in touch. The server’s decisions reach the terminal without anyone visiting it, and the state it publishes is what the browser, the web interface and the desktop notifier all read — so every part of the terminal agrees about which server it belongs to and whether that server is answering.