FAQ Index

How this FAQ is used: This is the centralized FAQs document.

Define which sections to go documentation site, or marketing site, or both.


Getting started



What is ProView DS?

ProView DS is a software platform, to deliver industrial-grade real-time data applications, for SCADA/IIoT/UNS and Enterprise integration.

Core pillars (overview):

All-included modules · One Designer (.NET & WebAssembly) · UNS-native (built-in MQTT broker & client with Sparkplug B) · OPC UA server & client · .NET & Python 3 scripting · 100+connectors;


Technology & runtimes



Do I have to design twice for desktop and web?

No. One Designer outputs to .NET desktop and WebAssembly (web/mobile); the same displays run in both.


What is Dynamic Binding?

An advanced pattern that lets you bind UI/logic directly to MQTT/Sparkplug B or OPC UA paths, or other external data sources, without creating local tags first—ideal for rapid onboarding and diagnostics. For production, you can promote bindings into a local UNS/tag model, when local governance is required.


What is MCP Server?

A built-in API layer for solution-specific tools/automations (e.g., generate a UNS from OPC UA, orchestrate analytics, data prep).


Is ProView DS 100% .NET?

Yes—100% .NET, green-field architecture; extend with C#/VB and Python 3.



Connectivity & data

Which drivers/connectors are included?

100+ connectors . See complete list at Connectivity Hub.


How do I use Edge SQL?

Use EdgeConnect to read/write local SQL and access remote SQL from the edge node. Try the Edge SQL Loggersample.


Does ProView DS include an MQTT broker?

Yes. Built-in MQTT broker, Sparkplug B client—no add-on required. It will includes a MQTT spa

publisher simulator, and connectors to Azure-Iot and AWS.


UNS & tag modes (choosing the right approach)


What are Linked Tags (UNS)?

Local UNS tags with a DataLink pointing to an external path (MQTT/Sparkplug, OPC UA, or supported drivers). At runtime, ProView DS auto-manages communications based on demand (screens/scripts). You keep local names and get intellisense/cross-refs.


How do modes differ?


  • Devices/Tags: pre-map channels/nodes/points; you manage groups.

  • inked Tags: keep a local model; the platform’s dynamic provider auto-manages comms via the Source link.

  • Dynamic Tags—bind straight to external paths;


Do Linked Tags work offline?

Yes. The tag exists locally and updates when the source is available.


When should I use Linked Tags?

When you want a durable tag model with names/governance while the platform auto-manages runtime comms—also improves startup vs importing thousands of points.


Can I mix modes?

Per measurement, pick one mode. Across a plant, mixing by area/use case is fine.


Security & performance notes

Same connector credentials/certs and RBAC apply. Comms are on-demand and grouped by protocol constraints → fewer idle subscriptions and faster startup.



Deployment & HA


Supported deployment targets?

Server runtime for .NET desktop; browsers/mobile via WebAssembly;


How do I set up HA?

All editions are hot-standby capable. For licensing, purchase a primary and a -HA standby (50% of primary); follow the HA guide for sync, health checks, and a failover drill.


How do I back up and move solutions?

Export/import the solution and back up the repository. Keep historian/SQL strings handy; test on a lab VM before cutover.



Troubleshooting (quick fixes)



MQTT broker won’t start.

Check port conflicts/permissions; service rights; firewall rules.


WebAssembly page is blank.

Enable WebAssembly runtime; hard refresh cache; confirm HTTPS and allowed origins.


OPC UA won’t connect.

Trust certificates both ways; align security policies/endpoints; confirm URL/port.


Edge SQL fails to insert.

Check connection strings; ensure schema exists; verify credentials/TLS; firewall to remote DB.


Clients drop during failover.

Validate HA sync, heartbeat timeouts, client reconnect settings; plan a drill.


Where are logs?

See Logging & Diagnostics in docs (runtime & designer logs).



Governance, security & privacy


Authentication/authorization?

See the Security guide for identity patterns and RBAC.


Audit & change control?

Runtime audit logs and change tracking are available; recommended dev → staging → prod workflow is documented.


Data privacy?

Follow organizational policies. MQTT broker/SQL/connector endpoints and credentials are stored securely per configuration best practices.