GW Automation builds self-contained Windows software interfaces for industrial control systems. No cloud accounts, no per-tag pricing model, security prioritsed — install an MSI on the PC that hosts your information, and extract history, reports and dashboards out of it, through secure encrypted communication.
Plant data is usually stuck — locked behind a proprietary historian, or behind a twenty-year-old DCOM interface nobody wants to touch. One product gets history out. The other gets legacy servers onto a modern protocol.
Connects as an OPC UA client to a plant historian — Siemens Process Historian, WinCC, or any compliant UA server — and turns its archive into something you can actually use. Browse the tag tree, pull raw history, resample it, and export to Excel or CSV with real quality codes attached.
Sits in front of a legacy OPC DA server, connects to it as a DA client over DCOM, and re-publishes the whole address space as a modern OPC UA server. Point UaExpert, a new SCADA package, or HistorianLink at the UA endpoint and leave the old server exactly as it is.
┌──────────────┐ DCOM ┌────────────────────────────────────┐ opc.tcp ┌────────────┐
│ OPC DA │◄──────────►│ OpcDaLink service │◄───────────►│ UA client │
│ server │ │ ┌──────────┐ ┌──────────────┐ │ │ UaExpert, │
│ (COM/Win32) │ │ │ DA client│──►│ UA server │ │ │ SCADA, │
└──────────────┘ │ │ STA pump │◄──│ address space│ │ │ Historian- │
│ └──────────┘ └──────────────┘ │ │ Link │
│ │ │ └────────────┘
│ ┌────▼─────┐ http ┌──────────┐
│ │ admin UI │◄───────────────►│ browser │
│ └──────────┘ └──────────┘
└────────────────────────────────────┘
Same installer, same service model, same licensing, same security posture. Learn one, you know both.
Runs headless as a service and survives reboots. A tray icon gives operators start, stop and status without opening the admin UI or needing a login.
No client to roll out. The service hosts its own UI on a local port — the same dark, dense, keyboard-friendly interface shown in the screenshots above.
Credentials and connection settings are encrypted with Windows DPAPI, tied to the machine. Nothing sensitive sits in plain text on disk.
Network-facing endpoints run HTTPS with a minimum of TLS 1.2. Admin stays on loopback, where encrypting the traffic would buy nothing.
A key tied to your customer ID, validated on the machine. No activation server, no internet, no phone-home — designed for air-gapped plant networks.
A standard MSI your IT team can review, deploy and uninstall cleanly. Silent install supported for managed rollouts.
| HistorianLink | OpcDaLink | |
|---|---|---|
| Role | OPC UA client | OPC DA client + OPC UA server |
| Talks to | Process Historian, WinCC, any compliant UA server | Any OPC DA 2.0 / 3.0 server |
| UA security | Basic256Sha256, Sign or SignAndEncrypt | Configurable; opens with security disabled for first run |
| Data out | .xlsx, .csv, live dashboard tiles, scheduled reports | Live UA address space, read and write |
| Alarms | WinCC message archive via OLE DB satellite agent | Not supported — DA carries no alarm interface |
| User roles | Admin, engineer, viewer | Single admin account |
| Licence prefix | HLNK-XXXX-XXXX-XXXX-XXXX | DALK-XXXX-XXXX-XXXX-XXXX |
| Platform | Windows Server 2016+ / Windows 10+ | Windows Server 2016+ / Windows 10+ |
| Footprint | Self-contained; no database server required | Self-contained; no database server required |
Both products install in minutes on a spare VM. Tell me what historian or DA server you are running and I will send a time-limited key and a short setup note for your specific stack.