OPC-UA integration
OPC-UA bridges packaged plant, CHP, and industrial HVAC skids into the same analytics layer as BACnet. Configure certificates carefully — OPC security is stricter than Modbus TCP.
Connection parameters
- Endpoint URL (
opc.tcp://host:4840) - Security policy: None (lab only), Basic256Sha256, or Aes256_Sha256_RsaPss
- Authentication: anonymous, username/password, or certificate
- Trust store: import server certificate or GDS-issued chain
Browse and subscribe
Browse from the Objects folder, select node IDs for temperatures, flows, and alarms. Use monitored items with sampling intervals aligned to SCADA expectations (250ms–1s for fast loops, 1–5s for building plant).
Certificate rotation
# After updating certs, restart the web container
docker-compose restart web
docker-compose logs -f web | grep -i opcMapping to dashboards
OPC points alias to the canonical model alongside Modbus registers. Use the dashboard builder to bind skid-level KPIs without exposing raw node IDs to end users.
Compliance
When exporting data to tenants, confirm contractual rights to OPC tags. Open modules are covered on licensing; OEM skids may impose additional restrictions.
Next steps
Explore a running stack, review the open source repositories, estimate ROI for a deployment, or talk with the CONTEXUS team about integration and licensing.
Module licensing details are summarised on /licensing. Browse reference dashboards in the gallery.