How do you calculate OPC UA tag coverage?

Divide the number of tags published through OPC UA by the total tags in your in-scope tag dictionary and multiply by 100. With 3,200 of 4,000 tags published, coverage is 3,200 / 4,000 x 100 = 80%.

What is a good OPC UA tag coverage percentage?

Most integration teams target 90% or higher of the in-scope dictionary so historians and analytics have the process variables they need. The example sits at 80%, a 10-point gap meaning 400 of 4,000 tags are still unmapped.

What does the coverage gap to target mean?

It is the target coverage minus actual coverage in points. Here 90% minus 80% is a 10-point gap, so 400 more tags from the 4,000-tag dictionary need to be published to reach target.

Does published mean the tag data is correct?

No. Coverage confirms a tag is exposed through OPC UA, not that its engineering units, scaling, data type, or update rate are right. Always follow tag coverage with a tag-quality or commissioning validation pass.

What belongs in the in-scope tag dictionary?

The set of process variables, statuses, setpoints, and alarms that downstream systems actually need, agreed during scoping. Excluding internal diagnostic or vendor housekeeping tags keeps the denominator meaningful and the metric honest.

How does tag coverage relate to asset connectivity?

Asset connectivity tells you a machine is online; tag coverage tells you how much of that machine's data is actually exposed. You can be 100% connected at the asset level yet only 80% covered at the tag level, as in this example.

IIoT, SCADA & Edge Connectivity calculator

OPC UA Tag Coverage Calculator

OPC UA tag coverage is the percentage of your in-scope tag dictionary that is actually published and accessible through an OPC UA server, the standardized interface most modern SCADA, historian, and IIoT consumers read from. Controls and integration engineers track it to measure how complete their standardized data interface is, because a connected machine still delivers nothing useful if its tags are not mapped and exposed. It is the depth metric that complements asset-level connectivity: an asset can be online while half its process variables remain invisible to downstream systems. The gap-to-target quantifies how many tags still need mapping before analytics and historian capture are complete.

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 computes the share of the in-scope tag dictionary published through OPC UA and the point gap to your 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:
Total tags in the in-scope tag dictionary:
OPC UA tag coverage target:

How to use the result

Use it during integration and commissioning to confirm tag mapping depth, not just whether assets are connected.
It measures whether tags are published, not whether they are correctly named, scaled, typed, or updating at the right rate.

Current U.S. benchmarks

Global copper trades at $13,484 per tonne (IMF via FRED, May 2026), up 41.5% in a year, and U.S. industrial electricity averages 8.66 cents per kWh. Both feed electrified-hardware unit economics.

Common questions

How do you calculate OPC UA tag coverage? Divide the number of tags published through OPC UA by the total tags in your in-scope tag dictionary and multiply by 100. With 3,200 of 4,000 tags published, coverage is 3,200 / 4,000 x 100 = 80%.
What is a good OPC UA tag coverage percentage? Most integration teams target 90% or higher of the in-scope dictionary so historians and analytics have the process variables they need. The example sits at 80%, a 10-point gap meaning 400 of 4,000 tags are still unmapped.
What does the coverage gap to target mean? It is the target coverage minus actual coverage in points. Here 90% minus 80% is a 10-point gap, so 400 more tags from the 4,000-tag dictionary need to be published to reach target.
Does published mean the tag data is correct? No. Coverage confirms a tag is exposed through OPC UA, not that its engineering units, scaling, data type, or update rate are right. Always follow tag coverage with a tag-quality or commissioning validation pass.
What belongs in the in-scope tag dictionary? The set of process variables, statuses, setpoints, and alarms that downstream systems actually need, agreed during scoping. Excluding internal diagnostic or vendor housekeeping tags keeps the denominator meaningful and the metric honest.

Last reviewed 2026-05-12.