Selection guide
Plant SCADA 2023 R2 AEL license tiers and included historian tags
Short answer
Plant SCADA 2023 R2 (v8.5) AEL server licenses bundle a Historian 2023 R2 Server (Standard) and a Reports for Operations 2023 R2 Server: 500 historian tags and 500 reporting tags at the 1,000- and 2,500-tag tiers, and 5,000 of each from the 10,000-tag tier through Unlimited. Existing enterprise licenses pick the entitlements up with a sync rather than a repurchase; legacy USB keys exchange through the distributor; and Flex shows existing enterprise customers only the 100,000-tag and Unlimited packages.
On this page
Plant SCADA 2023 R2 (v8.5) AEL server licenses bundle a Historian 2023 R2 Server (Standard) and a Reports for Operations 2023 R2 Server with the SCADA tier. The 1,000- and 2,500-tag tiers carry 500 historian tags and 500 reporting tags; the 10,000- and 100,000-tag tiers and Unlimited carry 5,000 of each. Existing enterprise licenses that already contain the Historian and Reports capability pick up the updated entitlements with a sync in the AVEVA Enterprise License Server, not a repurchase. Legacy USB keys move across through a distributor exchange, and on Flex, existing enterprise customers see only the 100,000-tag and Unlimited packages, with the smaller tiers tied to that USB-key exchange path. Pick the tier from the SCADA tag count first, then check the bundled historian capacity separately, because the two counts are independent.
What each server tier bundles #
The published AEL schedule for Plant SCADA 2023 R2 (v8.5) pairs each server tier with a Historian 2023 R2 Server, identified as the Standard edition, and a Reports for Operations 2023 R2 Server:
| Plant SCADA 2023 R2 server tier | Bundled Historian 2023 R2 Server tags | Bundled Reports for Operations 2023 R2 Server tags |
|---|---|---|
| 1,000 tags | 500 tags | 500 tags |
| 2,500 tags | 500 tags | 500 tags |
| 10,000 tags | 5,000 tags | 5,000 tags |
| 100,000 tags | 5,000 tags | 5,000 tags |
| Unlimited tags | 5,000 tags | 5,000 tags |
Every server tier, at any size, also bundles one Historian Client Web, one Historian Client Desktop, one Reports for Operations Development and one Reports for Operations Web Client. Those seats do not grow with the tier: an Unlimited server license carries the same four client entitlements as a 1,000-tag license.
Read the two capacity columns independently of the SCADA column. The SCADA tag allowance never becomes the historian or reporting allowance, and the bundled historian tags are counted under the historian's own licensing rule, which is not the SCADA tag count. If the plant already runs an earlier historian release, settle AVEVA Historian 2023 R2 license backward compatibility before treating the bundled server as its replacement.
The 500-to-5,000 breakpoint #
The only capacity step in the schedule sits between the 2,500- and 10,000-tag tiers: bundled historian and reporting tags go from 500 to 5,000 and stay there. At the 10,000-tag tier the bundle covers half the SCADA tag count (5,000 ÷ 10,000 = 0.50). At the 100,000-tag tier the same 5,000 tags are 5% of the SCADA count (5,000 ÷ 100,000 = 0.05), and an Unlimited SCADA license still stops at 5,000. Above the 10,000-tag tier, extra logged points are always a separate historian purchase, never a bigger SCADA tier.
Worked example: two plants, two decisions #
Illustrative tag counts, with the arithmetic shown.
Line A: 3,200 SCADA tags, 2,600 to log #
The smallest tier at or above 3,200 SCADA tags is the 10,000-tag tier, because 2,500 < 3,200. Bundled historian capacity = 5,000 tags. Logging plan = 2,600 tags. Headroom = 5,000 − 2,600 = 2,400 tags. Decision: buy the 10,000-tag server tier and nothing further; the bundle covers the logging plan with 2,400 tags to grow into.
Line B: 2,300 SCADA tags, 900 to log #
The smallest tier at or above 2,300 SCADA tags is the 2,500-tag tier. Bundled historian capacity = 500 tags. Shortfall = 900 − 500 = 400 historian tags. Decision: with a stable SCADA count near 2,300, keep the 2,500-tag tier and buy historian capacity as a separate entitlement covering at least 400 tags. Step up to the 10,000-tag tier only when growth past 2,500 SCADA tags is already planned, because that step lifts the bundled historian to 5,000 tags as a side effect.
Client licenses and companion seats #
Control Clients come in the same 1,000 / 2,500 / 10,000 / 100,000 / Unlimited tag tiers; the View Only Client is Unlimited tags. Each client license bundles the same companion seats:
| Client license | Tag tiers | Bundled clients |
|---|---|---|
| Control Client | 1,000 / 2,500 / 10,000 / 100,000 / Unlimited | 1 Historian Client Web, 1 Historian Client Desktop, 1 Reports for Operations Web Client |
| View Only Client | Unlimited | 1 Historian Client Web, 1 Historian Client Desktop, 1 Reports for Operations Web Client |
Client bundles carry access seats, not server capacity, and they do not include a Reports for Operations Development entitlement; that arrives only with the server bundle. Choose Control versus View Only by the SCADA access the workstation needs, then count the companion seats against the engineers and operators who will use them concurrently, because each additional seat is another client license.
Sync, exchange and Flex availability #
Three paths, chosen by what the plant already holds:
- An existing enterprise license that already contains the Historian and Reports capability, purchased before the change: sync. The documented sync action regenerates the activated licenses on the License Server from the record on the Activation Server, so the updated entitlements appear without a repurchase. Record the inventory before and after, and compare it against the tier table above. If the capability is absent after a successful sync, the license never contained it; that is an entitlement question for the distributor, not a sync to repeat.
- A legacy USB key: exchange. The swap to an AEL software license runs through the local distributor, and on the Flex purchasing site the smaller packages, reported as 1k, 5k and 10k, are visible only on that exchange path. Activation of the new license can arrive as an XML file applied through the Enterprise License Manager. Agree the replacement entitlement and the activation sequence before giving up the key.
- Quoting: the availability discussion names 1k, 5k and 10k packages, while the published schedule lists 1,000, 2,500 and 10,000 tags. A quote naming a 5k package names something the schedule does not contain, so identify the tier and its bundled capacities against part numbers before ordering.
If the exchange lands mid-project, for example while migrating Modicon SCADA libraries to Plant SCADA 2023, keep the license change on its own track from the application migration so a later fault traces to the right change.
The tier decision, step by step #
- Count SCADA tags and historian points separately, each under its own licensing rule.
- Take the smallest server tier at or above the SCADA count: 1,000, 2,500, 10,000, 100,000 or Unlimited tags.
- Compare the historian plan with the bundle: 500 tags below the 10,000-tag tier, 5,000 tags from it upward. If the plan fits, the SCADA tier is the whole decision.
- If the plan does not fit, buy historian capacity separately; the step up to the 10,000-tag tier pays off only when SCADA growth past 2,500 tags is real. When no tier's bundle covers the logging plan, size the standalone purchase with plant historian selection by scale and support needs.
- Add client licenses per concurrent seat; the four bundled server seats are the same at every tier.
- With an existing enterprise license, sync before buying anything. With a USB key, exchange through the distributor, and expect the smaller Flex packages on that path only.
- After any sync or exchange, verify the inventory in the AVEVA Enterprise License Server shows the products, capacities and client seats expected, then stop blaming licensing: a present entitlement with values not flowing is a data-path fault, and the pattern where a Plant SCADA Connector shows connected but historian tags are NULL is diagnosed at the connector and driver, not at the license server.
Questions asked
Does the Unlimited Plant SCADA tier include unlimited historian tags?
No. Unlimited applies to the SCADA tag count only. The Unlimited server bundle carries 5,000 Historian 2023 R2 Server tags and 5,000 Reports for Operations tags, the same as the 10,000- and 100,000-tag tiers. A plant logging more than 5,000 historian points needs separate historian capacity whatever SCADA tier it buys.
Why does Flex only show the 100,000-tag and Unlimited packages?
Reported Flex behavior limits existing enterprise-license customers to the 100,000-tag and Unlimited packages, with the smaller packages tied to exchanging a legacy USB key. Note the naming gap: availability discussions name 1k, 5k and 10k packages while the published schedule lists 1,000, 2,500 and 10,000 tags, so confirm the exact tier behind any quote before ordering.
Can one bundled client seat serve the whole engineering team?
Each server bundle includes one Historian Client Web, one Historian Client Desktop, one Reports for Operations Development and one Reports Web Client, and each Control or View Only client adds one Historian Web, one Historian Desktop and one Reports Web seat. More engineers or operators working concurrently than there are seats requires additional client licenses.