IIoT, SCADA & Edge Connectivity calculator

OPC UA Tag Coverage Calculator

Estimate the share of plant tags exposed through OPC UA. Enter the count of tags currently published by all OPC UA servers, the total tags in the tag dictionary that the program intends to expose, and the coverage target. The calculator returns the coverage percent and the gap to target.

What this calculator does

  • Estimate the share of process tags exposed through OPC UA from the count of tags published by OPC UA servers against the total tags identified in the tag dictionary, against the program coverage target.
  • Use it when a controls engineer or integrator is tracking how much of the plant tag dictionary is actually addressable through OPC UA on the way to a unified namespace or MES integration.
  • It returns the share of in-scope plant tags currently exposed through OPC UA and the gap to the program coverage target.

Formula used

  • OPC UA tag coverage = tags published ÷ total in-scope tags × 100
  • Coverage gap to target = target coverage - actual coverage

Inputs explained

  • Tags published through OPC UA: Use the count of tags exposed by all OPC UA servers (Kepware, Ignition OPC UA, Siemens OPC UA, or vendor-embedded), browsable to the MES or historian.
  • Total tags in the in-scope tag dictionary: Use the count of tags the program intends to expose (process variables, setpoints, alarms, modes, and counters), from the tag dictionary.
  • OPC UA tag coverage target: Use the program coverage target (typical 80 to 95 percent at MES go-live; 100 percent rarely required because some legacy tags stay on direct PLC links).

How to use the result

  • Run it weekly during an OPC UA migration or unified namespace rollout, and any time the MES integration team asks for a tag-availability snapshot.
  • Coverage at the OPC UA layer does not guarantee data quality at the consumer (historian, MES, dashboard). Pair with OT data completeness and machine data capture rate for a downstream view.

Common questions

  • Should I include alarms in the tag count? Yes if your tag dictionary lists them. OPC UA exposes both process variables and alarm and condition objects. If your AC&E integration is separate, scope this calculator to PV tags only.
  • What about tags exposed through Modbus or DNP3 only? Do not count them in the numerator. They are addressable, but not through OPC UA. Use the protocol conversion cost calculator to size the work to bring them onto OPC UA.
  • Why is 100 percent coverage rare? Many programs intentionally leave low-value or noisy legacy tags off OPC UA to keep the namespace clean. The target should reflect the agreed scope, not every tag in every PLC.
  • How do I model a unified namespace cutover? Run the calculator at each cutover milestone (each line, area, or plant). The coverage rate climbs as more areas come on; the gap to target shows where the integration team needs to focus.

Last reviewed 2026-05-12.