Protocol connectivity
OPC UA SCADA Software and 3D Visualization
Kingfisher 3D SCADA uses OPC UA to browse structured information models and bind secure, standards-based industrial data into 3D operations views.
* Representative project visualization
Protocol overview and design intent
OPC UA is the modern interoperability layer for industrial systems. It provides typed information models, sessions, subscriptions and optional certificate-based security—far beyond classic OPC DA.
Buyers searching “OPC UA SCADA software”, “OPC UA dashboard” and “OPC UA visualization” want secure connectivity to PLCs, historians and gateways without brittle proprietary drivers. Kingfisher focuses on client-side browsing and tag binding for visualization.
Where Modbus is register-oriented, OPC UA is node-oriented: you navigate namespaces and select NodeIds that represent sensors, setpoints and equipment objects.
Kingfisher's OPC UA path is aimed at plants that already standardized on information models from machine builders or enterprise gateways. Instead of rebuilding flat register maps, engineers browse nodes and bind them into 3D equipment objects so operators see structure that matches the real process.
How Kingfisher connects
Configure an OPC UA client channel with the endpoint URL, security policy and authentication mode required by the server, then browse or import the nodes you need as Kingfisher tags.
- Obtain the server endpoint URL and required security mode from the controls team.
- Trust or reject certificates per your OT PKI policy, and confirm whether mutual application certificates are mandatory in your deployment.
- Browse the address space or import a curated node list.
- Create subscriptions for high-change signals; poll slower nodes as needed.
- Bind nodes to 3D properties and alarm rules, then validate session reconnect behavior.
Data types and addressing
OPC UA exposes built-in types (Boolean, Int32, Float, Double, String, DateTime, arrays and structures). Browse names and NodeIds must be stable across server restarts—coordinate naming with the PLC/export toolchain.
Subscriptions deliver change-based updates, which is more efficient than blind polling for bursty signals.
For OPC UA SCADA dashboard work, prefer curated node lists over browsing the entire address space into production. Large servers can expose tens of thousands of nodes; importing only what the HMI needs keeps subscriptions lean and documentation clear for auditors.
- Endpoint URL and security policy selection
- NodeId / browse-path mapping into tags
- Subscription publishing intervals and monitored item queues
- Session keepalive and reconnect strategy
Industries that rely on this protocol
Automotive and electronics factories standardize on OPC UA for machine builders. Energy and process industries use it for multi-vendor gateways. Building systems increasingly expose OPC UA alongside BACnet.
Discrete manufacturing often mixes OPC UA on new cells with Modbus or S7 on legacy lines. Kingfisher lets both appear in one scene so supervisors do not jump between tools. That single-pane OPC UA visualization story is a common reason teams shortlist modern 3D SCADA platforms.
- Discrete and process manufacturing
- Multi-vendor machine cells
- Enterprise-to-OT gateway layers
Known limits and engineering notes
Kingfisher operates as an OPC UA client only (southbound / field connectivity). It does not act as an OPC UA server for northbound publishing.
Certificate mismanagement is the top field issue—clock skew, untrusted CAs and expired application certificates break sessions even when networking is fine.
- Security policy must match server expectations
- Large address spaces need curated imports
- Firewall rules must allow OPC UA ports/sessions