New features and enhancements
- Last UpdatedSep 29, 2025
- 7 minute read
General features and enhancements
-
Support for AVEVA Production Management on-premises event data curation for CONNECT
AVEVA Production Management facilitates cloud-based publishing of event data to CONNECT data services, leveraging the full potential of CONNECT capabilities such as data visualization. AVEVA Production Management delivers a data curator component that takes care of the curation process. For more information, see the Deployment and installation section. See also AVEVA Production Management CONNECT integration in the AVEVA Production Management Installation Guide.
-
Support for requestOrigin parameter in Web API and Web services
The following methods now include an optional requestOrigin parameter:
Web API
-
SubmitRecord, SubmitRecords
-
UpdateRecordStatus
-
SplitRecord
Web services
-
UpdateRecordStatus
-
SplitRecords
The requestOrigin parameter prevents infinite loops in requests by determining the original caller. For information on using requestOrigin, see the following documentation:
-
Web API Reference through this URL: http://<computername>/Ampla/Help/APIWeb/webframedesktop.html#Introduction.html, where the computername is the name of the computer hosting the AVEVA Production Management server.
-
Administrator (Studio) Help: SplitRecords request message, UpdateRecordStatus request message
-
-
-
Configurable standard ports
You now have the option to modify these port numbers if necessary.
-
8889 - WCF web service endpoint.
-
1235 - Internal WCF service used to communicate with Production Analyst.
You can modify port numbers 8889 and 1235 during installation or through AmplaUtil command. For more information, see New AmplaUtil parameters section.
-
8001 - .NET remoting is using this port number for communication between Studio and Ampla service. You can modify this port number through these XML configuration files:
-
ServerRemoting.config
-
SE.SPO.AmplaStudio.exe.config
For detailed configuration steps, see the following topics in Administrator (Studio) Help:
-
-
-
New AmplaUtil parameters
The AmplaUtil command line utility is enhanced to support the following parameters:
-
/rabbitmqcredentialupdate /rabbitmqusername:<username> or /q /rabbitmqusername:<username> - These parameters update the default service account credentials for the RabbitMQ service connection.
-
/wcfPort:<port number> - This parameter updates the port number configured for WCF service to the newly specified port.
-
/paWcfPort:<port number> - This parameter updates the port number configured for Production Analyst WCF service to the newly specified port.
For detailed steps in using the parameters for RabbitMQ and WCF service ports, see the following topics in Administrator (Studio) Help:
-
Update Production Analyst WCF service port with AmplaUtil
You can also update the RabbitMQ default credentials, WCF service, and Production Analyst WCF service ports during the AVEVA Production Management installation. For more information, see New and updated installer screens in Deployment and installation section.
-
-
WCF web services defaults to HTTPS
HTTPS and NetTcpBinding are now enabled by default for WCF web services. The Net.TCP ports allow the application to internally use the web services for normal operation without any SSL certificates. However, if you want to use the web services through HTTPS, you need to register the SSL certificate.
For more information about this feature, see WCF web services port HTTP support in the AVEVA Production Management Installation Guide. See also 9.1.0 upgrade notes.
-
Net.TCP Port Sharing
Starting with AVEVA Production Management version 9.1.0, Port Sharing is enabled by default. So, ensure that the Net.Tcp Port Sharing Service is enabled and running in the Services window before you start the AVEVA Production Management service manager.
-
Code enhancement to prevent automated lowercase formatting of HostURL property value
A minor code modification is implemented to prevent AVEVA Production Management from automatically formatting the HostURL property value to lowercase. This change addresses issues with case-sensitive parameters.
-
AVEVA Production Management documentation on docs.aveva.com
The product documentation set is now available on the AVEVA documentation portal at https://docs.aveva.com. This site hosts the latest versions of product documentation.
Features in Studio
These are the new or changed features in this release of Studio.
-
Limit on number of Production custom fields
The limits on the number of custom fields for Production reporting points has changed from 3072 to 4000. While you have the option to create up to 4000 custom field entries, we recommend using them sparingly to avoid potential configuration issues. For more information on custom field limits, see Limits on custom fields in Administrator (Studio) Help.
-
Changes to Period definition
Note: Period names must be unique to the projects.
-
Multiple-level period folders
You can now add period folders at multiple levels, allowing you to effectively organize period definitions. For information on creating period folders, see Add period folder in Administrator (Studio) Help.
Note: The DefaultPeriod property is no longer located in the Periods folder. This property has been moved to the user group and basic user levels. However, basic users do not have configurable periods.
-
PeriodHierarchy and DefaultPeriod properties
These properties are added to the Client Display Options category for UserGroup under System Configuration. For BasicUser, only the DefaultPeriod property is added. These changes provide the ability to set period definition visibility per user in Production Analyst and Web Client. For information on how these changes affect the Production Analyst and Web Client, see Features in Production Analyst section and What's new in AVEVA Production Management Web Client? at docs.aveva.com respectively.
For upgrade information, see 9.1.0 upgrade notes.
-
Features in Production Analyst
These are the new or changed features in this release of Production Analyst.
-
Enhancements to Filter Builder
-
Default period filter
The value for the default period filter is now determined by the DefaultPeriod property configured for a basic user or user group in the project. This means that if you are a member of a user group configured in Studio and its DefaultPeriod property is set to Hour, in Production Analyst, you should see Hour as the default period filter.

-
Filter window for a specific field
The period definitions available for selection in the following window is determined by the PeriodHierarchy property configuration in Studio for the user groups associated to a user. This means that only period definitions to which the logged-in user has access are shown in the period list.

Notes
-
If you log in as a basic user, all the period definitions in the project are shown, except for those with their ShowInFilter property set to false.
-
If you log in as an integrated user, all combined period definitions of the user groups you are associated to are shown, except for those with their ShowInFilter property set to false.
-
If there are any favorites with non-related period filter for the logged-in user, they are loaded as usual with the same filters.
-
If you are a member of multiple user groups, the setting for the first one is used.
-
-
For more information in using period definitions in Production Analyst, see Create a data query with Filter in Production Analyst (User) Help.
Deployment and installation
Changes to deployment and installation of AVEVA™ Production Management.
-
Production Management Curation Services
To support CONNECT integration, a data curator component called Production Management Curation Services is included in the application installer. When you install AVEVA Production Management using the full installation option, the data curator is installed by default. If you already have AVEVA Production Management, you can install the data curator using the custom installation option. For detailed installation steps, see Install the data curator component in AVEVA Production Management Installation Guide.
Note: If you don't want to install the data curator component, you can also use the custom install option to exclude it from the product installation.
-
Product installer in Windows Installer format
The product installer is now delivered in Microsoft Software Installer (MSI) format.
Note: If you are a domain user, use an admin command prompt window with administrator privileges when running the installer.
-
Support for Change install option
The product installer now supports the Change install option from the Control Panel's Program and Features window to accommodate installation of the data curator component if you already have an existing AVEVA Production Management setup.
When using this option for data curator installation, the Service Account screen auto populates with the same user account name used for running the AVEVA Production Management service and you must then reenter the password.
-
New and updated installer screens
-
RabbitMQ account - This screen is added to allow creation of an alternate user account other than the default service account credentials for the RabbitMQ service connection.

-
Port Configuration - This screen is updated to support the configuration of the default WCF service and Production Analyst WCF service port numbers (8889, 1235).

If you keep the default and don't change anything during installation, you can still modify the default RabbitMQ account and port numbers using AmplaUtil. For detailed steps related to RabbitMQ account and port configuration, see the following topics in Administrator (Studio) Help:
-
-
Microsoft .NET SDK version change
AVEVA™ Production Management now requires Microsoft .NET SDK version 8.0.
Deprecated and discontinued features
Deprecated feature
The Master Data Management excluding B2MML web service feature is deprecated in AVEVA™ Production Management software and is no longer under development. Functionality is marked as deprecated when a specific function or feature is still supported in the current release, but might be removed in a future release. We advise that you phase the feature out of your projects and begin to use alternative features.