LICENSEWARE
Contribute

AVEVA System Platform and InTouch licensing

From the LICENSEWARE WikiLast edited 12 ReferencesCited

This article is about licensing AVEVA's operations software (System Platform, InTouch HMI, Historian, Plant SCADA, MES and related products) under the P&O APM M&C Software Schedule, AVEVA Enterprise Licensing and the AVEVA Operations Control subscription.

On This Page

AVEVA System Platform (formerly Wonderware System Platform) and AVEVA InTouch HMI belong to AVEVA’s operations software, together with AVEVA Historian, Plant SCADA, Manufacturing Execution System (MES), Edge, Work Tasks and BI Gateway. These products are licensed under the AVEVA Software Schedule P&O APM M&C, the schedule for production and operations, asset performance management, and monitoring and control software. Version 6.0 is dated June 2026, and the schedule prevails over conflicting terms in the GTCs for the software it covers.[1] The installed products can run in one of three license modes: Perpetual (a specific product licence bought for use in perpetuity), Flex (an “a la carte” subscription paid with Flex credits) or AVEVA Operations Control (a subscription to the Edge or Supervisory package with unlimited use of its products for a defined set of users).[2][4] For the general models, see concurrent and device licensing.

Editions

Commercial form Unit Source 
Product licences on a License File (Perpetual mode, or term) Capacity (I/O Count, Tag Count, Platform Count, Session Count) and CALs per the schedule P&O APM M&C schedule[1] 
Flex Flex credits per product rate plan License Mode help[4] 
AVEVA Operations Control, Supervisory Edition and Edge Edition Per Named User, no additional Tag Count or instance limit Schedule s.9.24[1]; license modes[2] 

AVEVA markets Operations Control as a single licence for Edge, HMI, SCADA, data capture and enterprise visualization tools, “with no caps on tags, I/O, servers, or client connections”. The subscription includes CONNECT allowances: 200 daily data streams accessed through CONNECT data services, five monthly active users of CONNECT visualization and 50 units of AVEVA Advanced Analytics.[3] Catalog: AVEVA Operations Control (Edge and Supervisory packages); Operations Control editions licensed per named user without tag limits. Cloud products in the suite, such as AVEVA Development Studio, Integration Studio, Teamwork and Insight, are governed by their Service Descriptions.[1]

Metrics

The schedule defines many units; the ones most used for System Platform and InTouch are below.[1]

Schedule term Catalog row Definition (summary) 
Capacity I/O Count Licensed size criteria on the License Certificate, such as I/O Count, Tag Count, Platform Count, Session Count, Data Sources, Equipment and Site counts 
I/O Count I/O Count Maximum number of unique external data points the Software may monitor at any given time 
Platform Count Platform Count Number of Devices licensed to host the Platform, the software a Device needs to run Application Server software 
Client Access License (CAL) CAL Usage licence for each Client that directly or indirectly uses Software running on a Server 
Per Device Use (Per Seat) Per Device Use A Device licensed to use the Server Software on an unlimited number of Servers; installed locally on the Device 
Named User Named User A specified individual person; not a logon name, group or other non-person entity 
Per Server Use (concurrent use) Per Server Use Software on unlimited Devices, but the number of Devices using the Server Software is limited by the access licences bought 
Per Core Use Per Core Use A licence for each core on the Server; a Core is a physical or virtual processor unit as detected by the operating system 
Per Processor, Per Session Count, Runtime Report, Single Facility/Single Device  Further models for specific Server Software 

The schedule names two control documents. The License File enables the Software and may specify the Device, the Named Users, the location and the Capacity. The License Certificate records the Capacity, the licensee, the location and any Named Users.[1] A licence position for these products is built from those documents, not from installation counts alone.

Counting / floors

System Platform. A System Platform licence is limited in three ways: by the size of the Application Name Space (governed by the I/O Count), by the Platform Count and by the TS Session Count. Its components may be installed on several computers. They cannot be separated or upgraded separately, and the licence must be used within a single Application Name Space.[1] Catalog: System Platform limited by I/O Count, Platform Count and TS Session Count. Non-AVEVA clients may use the Galaxy Repository Access interface only on the device where the AVEVA Development Studio licence is located.[1]

InTouch HMI. Some InTouch components are licensed by Equipment count. A “Runtime” licence may run only its specific application. It cannot be used to develop new applications, databases or tables, although queries and reports on existing tables are allowed.[1] Catalog: InTouch Runtime licence runs only its specific application. Capacity upgrades work by replacement. The schedule’s own example is an InTouch 3,000 Tag Count licence replaced by a 60,000 Tag Count licence.[1]

Historian, MES and Plant SCADA.

CALs and access. A Device or user that runs concurrent sessions needs one CAL or session per session.[1] A Per Named User allocation must stay on file for at least 30 days before it can move to another person.[1] Catalog: Per Named User CAL moves only after 30 days. Software licensed Per Server Use that accesses a database or data source needs an access licence for each one. Failing to buy it is a material breach.[1] Catalog: Per Server software needs a licence for each database accessed. Using an application programming interface with other software requires a separate licence, such as the appropriate CAL or Client Connection.[1]

Multiplexing. For System Platform, Historian, MES, Batch Management, Recipe Management, Work Tasks, BI Gateway, Enterprise Integration and QI Analyst, multiplexing or pooling does not reduce the CALs or Seats required. The number needed equals the distinct inputs to the multiplexing “front end”.[1] Catalog: Multiplexing does not reduce CALs or Seats. This is the schedule’s indirect-access rule: users behind middleware, a web portal or an integration layer still count.

Versions and replacement. Depending on the product, the customer may install only the version on the Order Form, or that version or a lower one. A “6.5” licence never covers “6.6”.[1] Catalog: Install only the licensed version (or lower where permitted). A licence replaced by an upgrade, a replacement key or a keyed-to-keyless change must be removed. Its original License File, CD or certificate must be destroyed or archived and marked “Inactivated”.[1] Catalog: Replaced licences must be removed and marked Inactivated.

Transfers. InTouch HMI, System Platform, Development Studio, Historian, Edge, MES and the other products listed in s.7 may move from one Device or Application Name Space to another. The Software and License Files must first be completely removed from the original, and the identification data in the License File must stay accurate. The Software may be used on only one Device or Application Name Space at a time.[1] Catalog: Transfer between Devices only after complete removal.

Enterprise and Site licences. Enterprise and Site Licenses are agreed case by case in a written authorization signed by AVEVA and countersigned by the customer. The authorization sets the duration, scope, fees and support commitments.[1] Catalog: Enterprise License. Educational licences require a qualified educational user.[1]

Virtualization & partitioning

  • Remote Desktop. If Remote Desktop Server Edition or similar technology runs two or more instances of InTouch HMI (or Development Studio) on one Server or Device, each instance needs its own licence.[1] Catalog: InTouch: separate licence per instance under Remote Desktop. Per Session Count Use limits the number of Remote Desktop client sessions on a Server.[1]
  • Cores. A Core is a physical or virtual processor unit as the operating system detects it, so virtual machines are licensed by their visible cores where Per Core Use applies.[1]
  • License Files. Copying a License File using virtualization technology is prohibited unless AVEVA authorizes it in writing.[1] Catalog: No copying of a License File using virtualization technology.
  • Cloned licence servers. If the image of a License Server is cloned or copied, the server enters a 15-day grace period. After that it stops serving licences until they are updated.[8] Catalog: Cloned or copied License Server gets a 15-day grace period.

AVEVA Enterprise Licensing

System Platform has used a server-based licensing subsystem since System Platform 2017, replacing the earlier file-based system. Licences must be activated before use.[6] The AVEVA Enterprise License Server and License Manager are installed automatically with Application Server, InTouch or any role that includes the Galaxy Repository, by default on the Galaxy Repository node.[5] The system has three parts. The License Server hosts and serves the licences. The browser-based License Manager administers them. The Activation Server, hosted by AVEVA in the cloud, activates licences, and the License Manager connects to it only during activation.[7]

The workflow runs as follows:[9]

  1. The customer receives an entitlement file (zipped XML) with each order.
  2. The file is imported into the License Manager.
  3. The licences are activated onto a chosen License Server.
  4. Installed products acquire licences from the server while running and release them afterwards.

Online activation locks the licence to the License Server node. Offline activation exchanges request and response files.[12][8] Licences can be reserved for particular devices or left unreserved. When all unreserved licences are in use, new requests are denied.[8] The server listens on port 55559 by default, and port 55555 is used by License Servers older than version 4.0.[10] A licence change can take up to 30 minutes to be picked up unless the product is restarted.[5] Because the License Server tracks acquisitions, its usage data is the best inventory source for these products.

Cloud / BYOL

Under the Operations Control connected experience, subscriptions and users are managed in CONNECT, and products sign in through CONNECT single sign-on. A License Server is still needed for some server and non-user-facing applications.[5][4] Operations Control passively tracks which products are used, by whom and on which machine.[2] Catalog: Operations Control use is passively tracked. Changing the license mode takes effect only after the computer restarts, and a matching licence must be active on the configured License Server.[2] AVEVA publishes no public-cloud BYOL rule for these products.

Programs

  • AVEVA Operations Control: an unlimited-use subscription per defined set of users.[2]
  • Flex: credits-based subscription; see AVEVA Flex credits and CONNECT licensing.
  • Customer FIRST: Premium and Elite include License Assurance and a discount on test and offline development system licences. The discount applies to systems that mirror production for testing, simulation or emergency back-up.[11] Such non-production systems still need their own licences; the GTC forbids using back-up copies for testing or hot standby.

Out of scope

  • AVEVA Work Tasks, BI Gateway (with its OEM Tableau restrictions), InduSoft Web Studio, Enterprise SCADA, Production Management and the other product-specific sections of the schedule, beyond the rules cited above.
  • Legacy Wonderware licence agreements and the older file-based licensing used before System Platform 2017.
  • Prices and part numbers, which AVEVA does not publish.

References

  1. AVEVA Software Schedule P&O APM M&C (Excluding Process Optimization and Unified Supply Chain)-v6.0-June 2026Dated June 2026 (no day). Catalog: AVEVA Software Schedule P&O APM M&C v6.0Retrieved 2026-10-02.
  2. Operations Control license modesUpdated 2024-08-19. Catalog: Operations Control license modesEffective 2024-08-19. Retrieved 2026-10-02.
  3. AVEVA Operations Control Software | AVEVAUndated product page. Catalog: AVEVA Operations Control product pageRetrieved 2026-10-02.
  4. License Mode (System Platform help)Updated 2024-12-19Effective 2024-12-19. Retrieved 2026-10-02.
  5. License installation and activation (System Platform help)Updated 2024-12-19. Catalog: System Platform license installation and activationEffective 2024-12-19. Retrieved 2026-10-02.
  6. Server-based license (System Platform help)Updated 2024-12-09Effective 2024-12-09. Retrieved 2026-10-02.
  7. About Enterprise Licensing (AVEVA Enterprise Licensing help)Updated 2025-05-20Effective 2025-05-20. Retrieved 2026-10-02.
  8. Key terms and concepts (AVEVA Enterprise Licensing help)Updated 2025-09-01. Catalog: AVEVA Enterprise Licensing key terms and conceptsEffective 2025-09-01. Retrieved 2026-10-02.
  9. Licensing workflow (AVEVA Enterprise Licensing help)Updated 2024-12-04. Catalog: AVEVA Enterprise Licensing workflowEffective 2024-12-04. Retrieved 2026-10-02.
  10. Select License Sever (System Platform help)Updated 2023-10-11; title as publishedEffective 2023-10-11. Retrieved 2026-10-02.
  11. AVEVA Customer FIRST Program User Guide, Version 2.2, February 2026Dated February 2026. Catalog: AVEVA Customer FIRST Program User Guide v2.2Retrieved 2026-10-02.
  12. Activate licenses in online mode (AVEVA Enterprise Licensing help)Updated 2025-03-17Effective 2025-03-17. Retrieved 2026-10-02.

See also

Catalog Rows Cited

4Programs1SKUs15Rules7Metrics

Esc