Some SCADA products charge you not by how many people use the system but by how big the system is - specifically, how many tags or I/O points it monitors. That single pricing decision ripples through everything from budget to architecture, because suddenly every point you add has a cost and every tier boundary is a wall you can hit. This guide explains tag-based, or point-count, licensing: how the tiers work, what counts against the limit and what does not, and how licensing by tags rather than by clients changes the way engineers design and consolidate systems.
Tag-based SCADA license in one line: A tag-based SCADA license prices the software by the number of tags or I/O points configured, so cost scales with the size of the monitored system rather than the number of users. It is usually sold in tiers, such as 150, 500, 1500, or unlimited points, and the license enforces a ceiling on how many tags may be configured. Because every point counts toward the limit, tag-based pricing directly shapes how engineers scope, consolidate, and grow a system.
Tag-based licensing sells capacity in bands rather than one point at a time. A product might offer tiers at a small count for a compact skid or single site, a mid count for a larger facility, a high count for a substantial plant, and an unlimited tier for the biggest deployments. You buy the tier that covers your point count, and the software enforces that ceiling - once you reach the limit, you cannot configure additional tags until you move up a tier. The bands exist because it would be unwieldy to price and license every single point individually, so vendors group capacity into round numbers that map to typical project sizes.
The tier structure creates hard boundaries that matter more than the smooth cost curve might suggest. A system sitting just under a tier ceiling has no room to grow without a tier jump, so adding even a handful of points can force a purchase far larger than the marginal need, because the next tier is priced for a much bigger system. This step-change behaviour is a defining feature of tag-based licensing: cost does not rise gently with each point but jumps at the boundaries, which makes knowing where you sit relative to the next ceiling an important planning input.
The unlimited tier removes the ceiling entirely and is aimed at large or fast-growing systems where counting and managing against a fixed limit stops being worthwhile. For a big plant that will keep adding points, an unlimited license trades a higher fixed cost for freedom from tier boundaries and from the recurring exercise of proving you are still under the limit. Choosing between a bounded tier and unlimited is a judgement about how large and how volatile the tag count will be over the system's life, not just where it stands today.
The single most important detail in a tag-based license is which tags actually count, because that determines how quickly you consume your tier. The intuitive answer is that device tags - the real I/O points read from field devices, PLCs, and RTUs - count, and they usually do. The subtler question is whether internal tags, the ones created purely inside the SCADA for calculations, intermediate results, status flags, or scripting, also count against the limit. Products differ here, and the difference is not academic: a system that packs its logic into many internal tags can burn through a tier surprisingly fast if those internal tags are counted.
This ambiguity means the licensed limit and the field point count are not always the same number. A plant with a modest number of physical I/O points can still push against a tag limit if it builds extensive derived and calculated tags on top of them, and conversely a design that keeps internal tags lean stays closer to its raw device count. Before committing to a tier, engineers need to understand exactly how a given product defines a counted tag, because guessing wrong can leave a system unexpectedly at its ceiling with no obvious field expansion to explain it.
The definition of a counted tag also interacts with how tags are structured. Some products count structured or complex tags differently from simple scalar points, so a single instrument that expands into many sub-elements might consume more of the limit than its physical presence implies. Reading the licensing rules for how structures, arrays, and internal points are tallied is therefore part of scoping the license, not an afterthought, because the tier you need depends on the counted total, not on the number of instruments in the field.
When every tag has a cost, architecture starts optimising for tag efficiency in ways that client-based licensing never provokes. Engineers become deliberate about which points are actually brought into the SCADA versus left in the controller, about reusing calculated logic rather than spawning redundant internal tags, and about whether marginal points earn their place against the tier they push toward. This discipline can be healthy, trimming clutter, but it can also distort design if the cheapest-tag choice wins over the clearest one, so the pricing model quietly influences engineering decisions that on their face have nothing to do with licensing.
Tag-based pricing also drives consolidation-versus-distribution decisions. A single large system that pools everything under one unlimited or high tier can be cheaper per point than several small systems each buying its own bounded tier and each wasting the gap between its real count and its tier ceiling. That pull toward consolidation has to be weighed against the operational reasons for keeping systems separate, but the licensing math is a real input: fragmenting a deployment across many small tiered licenses often costs more in total tags than gathering them together, because each small system pays for headroom it does not use.
Cloud SCADA changes where this pressure lands. A platform such as Merobix aggregates tags from a fleet of remote sites into one system, so the licensing question becomes about the total point count across the whole operation rather than a separate tier bought and managed at every wellpad or station. For a distributed oil and gas operator, consolidating tag entitlement centrally avoids the waste of many small per-site licenses each stranded below their ceiling, and it makes growth a matter of expanding one total rather than repeatedly bumping individual sites into their next tier. The result aligns the cost of tags with the real size of the monitored estate instead of with how it happens to be split up.
It depends on the product, and it is the detail that catches people out. Device tags read from field equipment almost always count, but whether internal tags used for calculations, intermediate results, or scripting also count varies by vendor. A system that builds extensive derived logic can consume its tier much faster than its physical I/O count suggests if those internal tags are counted, so you must confirm exactly how a given product defines a counted tag before choosing a tier.
The software enforces the ceiling, so once you reach the limit of your tier you cannot configure additional tags until you upgrade to a higher tier. Because tiers jump in large bands, adding even a few points beyond a boundary can force a purchase sized for a much larger system. This step-change behaviour is why knowing how close you sit to the next ceiling is an important planning input, especially for systems expected to grow.
An unlimited tier makes sense for large or fast-growing systems where a fixed ceiling would either be repeatedly hit or would demand constant effort to prove you remain under the limit. It trades a higher fixed cost for freedom from tier boundaries and from managing against a count. The decision hinges on how large and how volatile the tag count will be over the system's life, not just where it stands the day you buy it.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.