AVEVA PI WORLD

AVEVA ENTERPRISE LICENSING

60 Tips in 60 Minutes
Presented By: J. Aldan, D. Gardner, S. Hong, P. Karthikeyan, S. Nagaria

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
 Javier Aldan
GCS Technical Account Manager
• AVEVA
• [email protected]

David Gardner
GCS Sr. Technical Account Manager
• AVEVA
• [email protected]

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
 Spark Hong
Technical Account Manager
• AVEVA
• [email protected]

Piriya Karthikeyan
Sr. Principal Technical Support Engineer
• AVEVA
• [email protected]

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
 Siddharth Nagaria
Sr. Application Consultant

• AVEVA
• [email protected]

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Agenda

• General Information
• Commonly Used Features
• Troubleshooting Tips
• Frequently Asked Questions
• Tech Notes/ Tech Alerts/ HF
• Q&A

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
General Information

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Licensing Services

• License Core Service. Stores, tracks, and distributes license rights as requested by clients and backends.
• License Server Agent. Tracks and controls the Local License Server.
• License Manager Service. Windows Service hosted web application for the LM HTML5 Application.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Licensing Services

* Authentication/Authorization – Must be Admin User or belong to AELicMgr group.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Issues when licensing services are not running

• License Manager shows License Server as disconnected.

• A client (Backend or Connection Client) can not acquire a license.
• Uploaded Entitlement(s) can not be activated (Offline Activation).
• On-line Activation fails.
• Ensure LS Agent and LS Core Service are Running.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Online Activation

• Following website should not be blocked - https://aveva.compliance.flexnetoperations.com/

• Ports required for AVEVA Enterprise Licensing:

• Web Manager :80
• Core Service :55555
• Agent : 59200
• License Manager to Activation server: 443
• Disable Enhanced Internet security option from Server Manager
• Disable Proxy from Internet options

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Offline Activation

• Offline activation URL - http://licenseactivation.wonderware.com

• It can also be reached from https://softwaresupport.aveva.com then click on the License Activation link.
• If offline activation is not successful, new send/receive file must be generated. The files cannot be reused.
• Start License Manager Web Service, License Server Agent Service, License Server Core Service and make sure
License Server is Running in License Manager.
• Make sure captcha in offline activation site is 5 characters. If not refresh page for new captcha.
• Try a different browser. Sometimes browser could have security settings causing offline activation to fail.
• Send/Receive files may be blocked. Unblock it (like zip files)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Server Redundancy Issues

• License Manager Web Service may be using local system account. Across workgroups this does not translate well
for security. Need to reconfigure the License Manager Webservice to use the local admin account instead.
• Deactivate licenses and undo redundancy from License Manager -> Maintenance. Reset License Server ID on
Primary and Backup License Server. Configure redundancy.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Commonly Used Features

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License vs Feature

• Each product will look for feature to enable individual functionality.

• A license is made up of a set of features to allow multiple products to work.
• In License Manager -> License Summary, select Details to see features,
quantity, number of IOs and version information.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License XML file (Entitlement)

• Multiple licenses can be provided in a single XML file identified with an Entitlement ID.
• The contents of the XML has the information required by License Server to proceed with the activation
process.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI - DEV license

• Each IT DEV license comes with 3 IT Runtime licenses – a ReadWrite license, a ReadOnly license and a
ReadOnlyRDS license. Also features for InTouch Client for Tag Server ReadWrite/ReadOnly and InTouch HMI
Web Server.

• Since this is a bundle of licenses instead of just a single license, each license can be used individually. An
InTouch machine cannot distinguish between an IT runtime license that came with a DEV license and any
other IT Runtime license, so the license that should be used as part of the DEV bundle is available to be
grabbed by any machine on which InTouch is launched.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Supervisory Server vs Supervisory Client feature

• SupervisoryServer
• License for unlimited InTouch for sysPlatform and unlimited OMI.
• SupervisoryClient
• License for one InTouch for sysPlatform and unlimited OMI.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI Features

• WindowViewer acquires different license depending on RDS

environment and InTouchView Application type settings.

• InTouch Workstation (Runtime) with IO

• InTouch Wrkst 60K Tags (InTouch-group60K)
• InTouch RT Tag Count (InTouch-tagcount)
• Communication Drivers Standard (oiserver-level1)
• MXAccess (wsp-i-mxaccess)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI Features

• InTouch Supervisory Client (ViewApp)

• Historian Client Desktop (historian-i-client)
• MXAccess (wsp-i-mxaccess)
• Supervisory Client Read Only (wsp-i-supclientro)

• InTouch Client (Tag Server)

• InTouch HMI Client for Tag Server
ReadWrite (it-i-hmiclientrw)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI Features

• WindowViewer acquires different license dependent on RDS environment, Remote Application Type, and
InTouchView Application type settings.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI License Parameters

• TagCount – Max tag count allowed

• Windows – Max window count allowed (65,535 for all sizes of Intouch)
• ReadOnly – Ability to write to IO data
1 = ReadOnly, 0 = ReadWrite
• Language – Support for Chinese OS
1 = Chinese, 0 = all others
• Timeout – How long WindowViewer runs before exiting (set to “0” for AVEVA Enterprise Licensing model. This
was used in legacy licensing for Demo mode timeout.)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Incremental Licenses

• Whenever a new version of same license is ordered, the old license will have an expiration date. This is to give
customers 6 months time to upgrade to new version.
• You can identify this in License Manager > License tab and sort by Serial number. You will see two similar
serial number with difference at the end.
• Example
• T17082203-0
• T17082203-1

• In the above example, T17082203-0 will have an expiration date 6 months from the date T17082203-1 was
created. T17082203-1 will be a permanent license.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Consignment License

• An SI’s consignment license can be activated five times (5 different LS’s) - “AVEVA AdvDev Studio 2020 Unlimited,
Subscrip Demo Consign”.
• Some features in a consignment license have a quantity of one, but others can have a higher number. This allows
the use of different features on different computers with a single consignment license.

• For example, a single license can enable multiple instances of InTouch WindowMaker on different computers.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA InTouch HMI Web Client Licensing

• Single Web Session Mode. If no web client license, then first web session is free. Subsequent web session will
be denied and will show an Invalid License page.
• Multiple sessions. Web “session” is per browser type per machine. Example: If one Chrome browser is
granted with valid license, then on the same machine, other Chrome browser will also be granted with valid
license status. After closing all browsers that had obtained valid license status, you need to wait 15 minutes
for another browser type to claim this license status.
• Unlimited Web Session Mode. For example if feature “InTouch HMI 2020 Web Server, Unlim RW Clients” is
acquired, then unlimited client connections are enabled for the InTouch Web server. Internal name of this
feature is “it-i-webclientunlimrw”.
• Release of License. Unlimited web session license will be released from license server when the “InTouch
Web” is stopped.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA System Platform - GR License

• Galaxy Repository service consumes feature “Application Server <number> IO”. For
example, a galaxy can consume feature “Application Server 1M IO” (internally called
wspruntime-group 1M).

• This feature can be consumed from an Application Server license, for example a
production environment with no Development Studio license.

• Alternatively, this feature can be consumed from a Development License, for

example in a development environment where production licenses are not installed.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA System Platform - IDE License

• Application Server IDE consumes feature “Application Server Dev <number> IO”.
• For example a Development Studio 2020 Unlimited license provides feature “Application Server DEV 1M IO” with
internal name “wspdevstudio-iocount”.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA System Platform - MxAccess Feature

• MxAccess license is used for MxAccess Applications running on a deployed platform.

• Customers can use MxAccess toolkit to write application to access attribute values on any deployed platform.
• MxAccess App accesses attributes via a NET wrapper. This wrapper needs to have MxAccess License.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA OI Servers and Communication Drivers License

License Feature Display Name Feature Internal Name

OI Servers Standard G-2.0 OI Server Standard oiserver-level1

OI Servers Professional G-2.0 OI Server Professional oiserver-level2

OI Server Multi-Instance oiserver-instance

Communication Drivers
Communication Drivers Standard oiserver-level1
Standard 2020

Communication Drivers
Communication Drivers Professional oiserver-level2
Professional 2020

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA Historian Server License
AVEVA Historian Server 2020, Standard 5K tags

• Historian Standard 5000 Tags (historian-groupStd5K)

• Historian Tag Count (historian-tagcount)
• Historian Client Web (historian-i-insight)
• Communication Drivers Standard (oiserver-level1)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA Work Task 2020 License (formerly Workflow/Skelta)

• Work Tasks Concurrent Workflow Count (bpm-concworkflow)

• Workflow Management - DevStudio Edition (bpm-group01)
• AVEVA Work Tasks Client Connection (bpm-i-connection)
• AVEVA Work Tasks - Forms (bpm-i-forms)
• AVEVA Work Tasks - Quickflow Engine (bpm-i-quickflow)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA System Monitor 2020 License

• Sentinel All Features Subscription (sentinel-groupall)

• sentinel-base

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Troubleshooting Tips

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Activation
Delete Trusted Storage
• The AVEVA license activation process binds activated licenses to the computer
from which the license was activated using the computer’s MAC address for
identification. This information is stored in Trusted storage.
• When to use?
• MAC address changed
• Virtual machine or image copy
• NIC change
• FNE errors during activation
• Procedure for deleting trusted storage
• In the License Manager(LM), Cancel the pending activations/Deactivate licenses
• Close License Manager
• Stop the License Core Service
• Delete the three trusted storage files from:
C:\ProgramData\FNE Server folder (do not delete the folder!)
• Start the core service
• Open LM → Manage and reset the License Server ID under Maintenance section

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Activation
Error When Activating License
• The FNE Server encountered an error: Response is out of order with previous responses
• Stop the License Server Core Service.
• Delete Trusted Storage.
• Reset License Server ID.
• Start the License Server Core Service, which will create 3 new files in the FNEServer folder.
• In the License Manager press Sync so that it is synched with FNO.
• Then you can do your normal actions in License Manager.
• Object reference not set to an instance
• Reset the License Server ID.
• May need to re-install License Server and License Manager.
• Activated license successfully and then deleted/formatted/or renamed License Server prior to deactivate the license. The
license can no longer be activated.
• Contact AVEVA Technical Support to release the license for activation.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Acquisition
Unable to Acquire License
• After renaming License Server, products are not able to acquire license.
• Re-run the Configurator on product nodes to point to new License Server.

• License is checked out to a node, but the node is unable to acquire

license.
• Could be due to corrupted checked out license.
• Check LocalAcquireInfo.xml at C:\ProgramData\AVEVA\Licensing\License API2\Data\.
Delete the file and try again. (Take a backup prior to deleting)

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Acquisition
Deleting Client Trusted Storage
• On the Client/Product node delete the contents of Backendmodule1 folder (C:\ProgramData\AVEVA\Licensing\Backendmodule1).
• Contents get recreated next time product requests license.

** Deleting Client Trusted Storage does not affect running products.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Read-Only License Acquisition

• For AVEVA OMI Application, how do we restrict a user to ONLY be able to launch an app in READ-ONLY mode?
• Feature is not available. Enhancement Request - L00147301.
• Workaround is to restrict access to graphics or set up Navigation security for ViewApps so that users are
restricted to certain windows.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Reservation vs. Checkout

License Reservation License Checkout

Concept The reserved license model ensures that specific Checkout is the process in which the licenses get
devices or users are assigned a license. permanently acquired on a node. After checkout
process, these licenses do not require the LS.
When to • User reservation is only for client license - ex - • Takes the license out to the node.
Use InTouch runtime. • Think of it like creating a lic file and copies it
• User reservation cannot be done for DEV over to the node.
license - ex - InTouch DEV, App server Dev. • Once checkout is done, you can shutdown LS
• The only thing dev licenses recognize is device. and still node will get license.
Key The license is returned back to License Server The license remains in the checked out node until
Difference when product is shutdown. checkout is undone regardless of whether it’s in
use or not.
Where to From License Manager, in the Servers Details page, Launch command prompt on checked out node
Check click the Device Reservation tab. and run as admin.
AELiccheckout checkedoutlist
© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Reservation & Checkout
Important Notes
• Reservation
• Reserving a license that is currently acquired by a device other than the device assigned in the reservation does
not release the license from the device.
• The reservation takes effect the next time the license is released, and the assigned device acquires the license.
• The device and user identifiers entered when reserving licenses must match the device and user identifiers
known to the relevant computer or domain.

• Checkout
• When a license is checked out to a node, then the same license cannot be acquired from License Server even if
the sufficient count is not available in checkout store.
• Only one source is supported for a node for a license checkout store or License Server.
• If the customer knows the maximum no. of sessions possible for the terminal server and can dedicate those no.
of licenses to that terminal server, they can go with checkout approach. Otherwise, advise them not to
configure checkout.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
License Reservation & Checkout

• Determine what features are checked out on a Client node

• In the Client node, open Command Prompt as an Administrator.
• Type AELiccheckout checkedoutlist
• Press Enter. A list of checked out licenses is displayed, with details such as Serial Number, Product Name,
Component Name, Version, and Count.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Non-activated License
BIN & LOC License File
• What is a BIN/LOC file?
• Bypasses activated licenses. When a BIN/LOC file is on a client node, the
product by passes activated licenses and will look in the BIN/LOC file.
• Demo licenses are available in BIN/LOC file format.
• BIN file for version 2017 generation and LOC file for version 2020 above.

• Where is it located?
• Trial License Pool - C:\ProgramData\Schneider
Electric\Licensing\TrialLicensePool.
• Local License pool - C:\ProgramData\AVEVA\Licensing\LocalLicensePool.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Non-activated License
BIN & LOC License File
• LOC file not acquiring license
• Check C:\ProgramData\AVEVA\Licensing\License
API2\Data\LocalBackEndAcquireInfo.xml. If its empty then LOC file wont work, try
deleting the xml file.

• LOC/BIN Viewer
• Located in C:\Program Files (x86)\Common Files\ArchestrA\Licensing
Framework\License Utilities.
• Can view BIN file and LOC file.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
View Activated Features

• In the License Server open a new browser tab -

http://localhost:55555/fne/xml/features?detailed=true
• Do this for the Primary and for the backup in another
tab replace the localhost with the backup server name.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Log Files for Licensing

• SMC Log Flags

• LicAPI - AELicensing, AELicAcquire, AELicTiming, Info-Licensing
• ProductLicenseService – AELicensing, CheckOutLog

• License Log
• Under C:\ProgramData\AVEVA\Licensing\License Server. File name: fne-error, fne-access.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• How is a software license released?

• In normal conditions, license released when software closed normally. IE, close IDE, close View.exe, etc.
• Force release by pointing client to a different license server in Configurator.

• If I get a message saying Activation ID already used, what do I need to do?

• If you know what server is using that Activation ID, just deactivate it from that server so it can be used elsewhere.
• If you do not know, Tech Support can look it up and get you the server's name.
• If that server is no longer available, Tech Support can also make that server obsolete in the license activation server, or release
individual Activation ID’s from it, which would allow them to be activated by another server.
• If the License Server (customer side) was renamed, or has a new License Server ID, then it will need to be made obsolete by Tech
Support.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• When would I need to use the AE Workgroup Licensing Utility?

• If you are using the AVEVA Enterprise Licensing on a set of computers that are not part of a Domain.
• Run the utility at C:\Program Files (x86)\Common Files\ArchestrA\Licensing Framework\Licensing Utilities\AELicWorkgroup.exe
as an Administrator, and follow the steps to Configure.
• If you have redundant license servers, and an install / repair is performed after you’ve begun using users under a workgroup, you
will need to re-run the AE Workgroup Licensing Utility.

• What nodes require Configurator to run?

• Every node that has products that need a license will need to run Configurator to point it to the appropriate License Server.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• What is a Failover license?

• The FLB or Failover Load Balance license is a license that allows you to have problems with one Thin Client connecting to one
terminal server, and then needed to switch to a second Terminal Server. The license may get tied up based on how the Thin
Client closed. FLB license allows it to get one on the second Terminal Server without issue. If/When it needs to go back to
Terminal Server 1, it could re-use that first license if still there, or get a new one if the prior license is released.

• How does the license work on RDS with multiple Remote Desktop Server’s?
• If you are using InTouch, and have multiple Remote Desktop Servers, you should make use of the FLB (Failover/Load Balance)
license so that there is a license whether your one client is running on a Primary or backup Remote Desktop Server.
• If you have fewer licenses than you have Thin Clients, you need to gracefully shutdown View.exe on one Thin Client to free up
the license. Simply closing the session is not a graceful shutdown and license will get stuck till it’s released.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• Why does a License Server go into Grace Period?

• If License Server VM is moved to a different host, or if the VM is cloned/copied, or VM is exported/imported to another
environment.
• If networking for VM has changed since licenses activated. (Different MAC ID)
• License Server versions prior to 3.5.1 would also sometimes go into Grace Period for unknown reasons.

• How do you get a License Server out of Grace Period or Grace Period Expired?
• You can deactivate all the licenses on a license server, and then re-activate them to clear Grace Period.
• You can contact Tech Support and get a Grace Period Exit code that can be used to get out of Grace Period and leave the existing
licenses Activated.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• What is a temp license? How can I get one?

• A temp license will allow the software to run for about 30 days, depending on when the temp license was created. The file will
come in two forms.
• XML – This one will activate like the standard license but has an expiration date that will show in the License Manager.
• BIN/LOC – These are pre-activated files that would be placed on each system that needs the license. They do not show up in License Manager.
BIN is for pre 3.6 License server, and LOC is for 3.6+ versions. Specific instructions will come with the file.
• You can contact Tech Support or your local distributor for a temp license. They are used to help bridge from development to
production, or from pre-sales testing to when you get the full license.

• How is a Panel PC licensed?

• Panel PC’s are delivered with a special LOC file, which can be found in C:\ProgramData\AVEVA\Licensing\LocalLicensePool.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Frequently Asked Questions

• How are Integration Studio VM’s licensed?

• These systems are automatically licensed via BIN/LOC files.

• Who has permission to view or make modifications in License Manager?

• On the computer that has the license server installed, there will be a user group called “AELicMgr”. Any users placed in that
group will be able to open, view, and modify things using the License Manager.

• What is Borrow time?

• If a node does not or cannot communicate with the Licenses Server to renew the license, then it will expire after certain time.
This time duration is called borrowed time.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Tech Notes/ Tech Alerts/ HF

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Tech Notes
Support Site - https://softwaresupportsp.aveva.com/
• TN 1395 - Schneider Electric Licensing - Activate License Using ONLINE Activation
• TN 1396 - Schneider Electric Licensing - Activate License Using OFFLINE Activation
• TN 1397 - Schneider Electric Licensing - Helpful Information
• TN 2868 - Configuring Schneider Electric Licensing for Wonderware Historian Server 2017 and remote Historian Client 2017
• TN 2907 - Schneider Electric Licensing – Best Practices
• TN 2908 - Resolving Historian Server Unable to Return License to the License Server
• TN 3019 - Working With License Server Redundancy
• TN 10268 - License Activations with hundreds of Feature Lines take many minutes
• TN 10333 - What causes a License Grace period and how to end it
• TN 10475 - Galaxy Repository Flex and Non-Flex Licensing in System Platform 2020
• TN10600 - Recovering a broken License Server Redundancy pair

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Tech Alerts

• TA 271 - Installing 2017 Software or License Server on the Same Computer on which a 2014 License Server (released with Recipe
Manager Plus, Intelligence or Alarm Adviser) is Installed Will Orphan Activated Licenses
• TA 274 - Communication failure between Wonderware products and a License Server can result in product shutdown
• TA 280 - Improper Shutdown of InTouch from within an InTouch RDS/TSE Session May Result in the License Used by that Session
Becoming Unavailable to a New Session
• TA 281 - Do NOT Rename the License Server Computer when Licenses are Activated
• TA 297 - Issue with 2017 Licensing - Reserve License Capability For Supervisory Client and InTouch Web Client issue
• TA 358 - The Backup License Server fails to serve licenses when the Primary License Server is down for more than three days
• TA 367 - License Server Limitation of Number of Production Activation IDs
• TA 388 - Upgrading to Licensing 3.5.1 to Resolve License Server Redundancy Issues
• TA 491 - Online Activation with Licensing 3.5 or Licensing 3.5.1 Requires a License Manager File Change

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
Hot Fixes
AVEVA Enterprise Licensing 3.7.2
• AELicensingPlatform-HotFix-1283685
• Only apply to Client nodes (Platform component)
• Issue resolved - Trend embedded within OMI does not acquire the license although OMI itself could acquire it successfully

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
This presentation may include predictions, estimates, intentions, beliefs and other statements that
are or may be construed as being forward-looking. While these forward-looking statements
represent our current judgment on what the future holds, they are subject to risks and uncertainties
that could result in actual outcomes differing materially from those projected in these statements.
No statement contained herein constitutes a commitment by AVEVA to perform any particular action
or to deliver any particular product or product features. Readers are cautioned not to place undue
reliance on these forward-looking statements, which reflect our opinions only as of the date of this
presentation.
The Company shall not be obliged to disclose any revision to these forward-looking statements to
reflect events or circumstances occurring after the date on which they are made or to reflect the
occurrence of future events.

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.
 linkedin.com/company/aveva
@avevagroup

ABOUT AVEVA
AVEVA, a global leader in industrial software, drives digital transformation for industrial organizations
managing complex operational processes. Through Performance Intelligence, AVEVA connects the
power of information and artificial intelligence (AI) with human insight, to enable faster and more
precise decision making, helping industries to boost operational delivery and sustainability. Our
cloud-enabled data platform, combined with software that spans design, engineering and operations,
asset performance, monitoring and control solutions delivers proven business value and outcomes to
over 20,000 customers worldwide, supported by the largest industrial software ecosystem, including
5,500 partners and 5,700 certified developers. AVEVA is headquartered in Cambridge, UK, with over
6,000 employees at 90 locations in more than 40 countries. For more details visit: www.aveva.com

© 2021 AVEVA Group plc and its subsidiaries. All rights reserved.