AVEVA Pipeline Operations for Liquids

AVEVA Pipeline Operations for Liquids 2025 Patch 1 release notes

Save PDF

AVEVA Pipeline Operations for Liquids 2025 Patch 1 release notes

Save PDF

Last UpdatedApr 30, 2026
12 minute read

The AVEVA Pipeline Operations for Liquids 2025 Patch 1 release is focused on reliability and stability. This update rolls up the hotfixes released since the AVEVA Pipeline Operations for Liquids 2025 release into a single, streamlined version for easier deployment and support.

The AVEVA Pipeline Operations for Liquids 2025 Patch 1 release notes describe the software, installation steps, and the fixed issues and changes that we have made since the AVEVA Pipeline Operations for Liquids 2025 release.

Note: As standard practice, projects and customers should make sure to install the latest patches for these product versions.

Note: This release is compatible with JSON serialization.

Prerequisite software

Before installing AVEVA Pipeline Operations for Liquids 2025 Patch 1, ensure that the following is already installed on the system:

AVEVA Pipeline Operations for Liquids 2025

Microsoft Installer (MSI)

Software Prerequisite MSI File(s)

To ensure a fully operational and supported system, the previously released product components (and all contents) for AVEVA Pipeline Operations for Liquids 2025 must be installed from the associated MSI file(s) prior to applying this patch.

Notes: The MSI version numbers should match the versions listed in the table; however, version numbers may be higher if you have hotfixes installed.

For more information on previously released patches, refer to the applicable set of release notes. If you do not have access to the release notes, contact the AVEVA Knowledge & Support Center.

Product Component (Microsoft Windows Program Name)	MSI File name	MSI Version	Release Version
AVEVA Enterprise SCADA ADE Client	ADE.Client.msi	10.4.0.443	AVEVA Enterprise SCADA 2025
AVEVA Enterprise SCADA ADE Extensions	ADE.Extensions.msi	10.4.0.504
AVEVA Enterprise SCADA Historical Datapump	Historical.Datapump.msi	10.4.0.481
AVEVA Enterprise SCADA RealTime ADE	RealTime.ADE.msi	10.4.0.158
AVEVA Enterprise SCADA RealTime Displays	RealTime.ezXOS.msi	10.4.0.242
AVEVA Enterprise SCADA RealTime Service	RealTime.service.msi	10.4.0.1875
AVEVA Enterprise SCADA Applications VirtualRTU Player	Applications.VirtualRTU.Player.msi	10.4.0.309
AVEVA Enterprise SCADA Historical Base Infrastructure	Historical.Common.Base.msi	10.4.0.447
AVEVA Enterprise SCADA Infrastructure Common Tools	Infrastructure.Tools.Common.msi	10.4.0.781
AVEVA Enterprise SCADA Infrastructure Administration Tools	Infrastructure.Tools.Administrationn.msi	10.4.0.796
AVEVA Enterprise SCADA Management Of Change ServiceBase	ManagementOfChange.ServiceBase.msi	10.4.0.458
AVEVA Enterprise SCADA Management Of Change RealTime	ManagementOfChange.RealTime.msi	10.4.0.1013
AVEVA Enterprise SCADA OPC DA Server	OPC.DAServer.msi	10.4.0.828
AVEVA Enterprise SCADA SystemServices Common	SystemServices.Common.msi	10.4.0.707
AVEVA Enterprise SCADA SystemServices ISPS	SystemServices.ISPS.msi	10.4.0.640
AVEVA Enterprise SCADA SystemServices RCS	SystemServices.RCS.msi	10.4.0.643
AVEVA Pipeline Operations for Liquids ADE	LMS.ADE.msi	10.4.0.1184
AVEVA Pipeline Operations for Liquids RealTime	LMS.RealTime.msi	10.4.0.3365
AVEVA Pipeline Operations for Liquids Displays	LMS.ezXOS.msi	10.4.0.377

Software Patch MSI File(s) Included in this Release

Product Component (Microsoft Windows Program Name)	MSI File name	MSI Version	Release Version
AVEVA Enterprise SCADA ADE Client	ADE.Client.msi	10.4.0.504	AVEVA Enterprise SCADA 2025 Patch 1
AVEVA Enterprise SCADA ADE Extensions	ADE.Extensions.msi	10.4.0.523
AVEVA Enterprise SCADA Historical Datapump	Historical.Datapump.msi	10.4.0.493
AVEVA Enterprise SCADA RealTime ADE	RealTime.ADE.msi	10.4.0.174
AVEVA Enterprise SCADA RealTime Displays	RealTime.ezXOS.msi	10.4.0.271
AVEVA Enterprise SCADA RealTime Service	RealTime.service.msi	10.4.0.1986
AVEVA Enterprise SCADA Applications VirtualRTU Player	Applications.VirtualRTU.Player.msi	10.4.0.323
AVEVA Enterprise SCADA Historical Base Infrastructure	Historical.Common.Base.msi	10.4.0.464
AVEVA Enterprise SCADA Infrastructure Common Tools	Infrastructure.Tools.Common.msi	10.4.0.825
AVEVA Enterprise SCADA Infrastructure Administration Tools	Infrastructure.Tools.Administrationn.msi	10.4.0.839
AVEVA Enterprise SCADA Management Of Change ServiceBase	ManagementOfChange.ServiceBase.msi	10.4.0.470
AVEVA Enterprise SCADA Management Of Change RealTime	ManagementOfChange.RealTime.msi	10.4.0.1025
AVEVA Enterprise SCADA OPC DA Server	OPC.DAServer.msi	10.4.0.841
AVEVA Enterprise SCADA SystemServices Common	SystemServices.Common.msi	10.4.0.722
AVEVA Enterprise SCADA SystemServices ISPS	SystemServices.ISPS.msi	10.4.0.655
AVEVA Enterprise SCADA SystemServices RCS	SystemServices.RCS.msi	10.4.0.664
AVEVA Pipeline Operations for Liquids ADE	LMS.ADE.msi	10.4.0.1226
AVEVA Pipeline Operations for Liquids RealTime	LMS.RealTime.msi	10.4.0.3484
AVEVA Pipeline Operations for Liquids Displays	LMS.ezXOS.msi	10.4.0.410

Pre-installation configuration

There are no pre-installation configuration requirements for this release.

Installation

To install AVEVA Pipeline Operations for Liquids 2025 Patch 1

Sign in to the computer as a member of DNA Installers.
Shut down all AVEVA Enterprise SCADA services.
Copy the 2025 Patch 1 MSI files to an accessible location on any computer running the MSI files listed under Software Patch MSI File(s) in Prerequisite software.
Run the individual 2025 Patch 1 MSI files.
Apply the post-installation configuration procedures

Post-installation configuration

Update ezXOS elements in the data root

The following procedure details how to update easy eXtended Operator Station (ezXOS) elements in the data directory (that is, %DNADataRoot%) on either the display source or the Display Edit Station (DES).

Sign in as a member of DNAInstaller.
On the desktop, right-click the Windows Powershell for DNA shortcut, and then select Run as administrator.

Windows PowerShell for DNA opens.
Run the following commands:

Set-silo ezxos

pdt -fo BLT_TANKALARMLIMIT.xec

pdt -fo CNTL_PIPELINE.XEM

Important: The signature of the Tankalarmlimitvalidation Business Logic Tier (BLT) has been changed as part of this release. As a result, the BLT_TANKALARMLIMIT composite has also been updated. In addition to performing the rebuild procedure above, if you have custom displays or other code that utilizes the Tankalarmlimitvalidation BLT, the updated signature must be used.

Notes: Updated XEM files are located in the %DNAInstallRoot%\Shared\elements\displays\lms directory.

The updated XEC file is located in the  %DNAInstallRoot%\Shared\elements\composites\lms directory.

Fixed issues

The following issues were fixed.

Description

Case–N/A

(Defect–4221923)

This defect fix addresses an issue where the Weighted Average Corrected Density for Accumulator and Virtual Flow Computer (VFC) records could be inaccurate because the calculation was based on Gross Volume (GV) as opposed to Gross Standard Volume (GSV). Now, the Weighted Average Corrected Density calculation is updated to use GSV.

For more information, refer to "Weighted Average Calculations for Accumulators" and "Weighted Average Calculations for VFCs" in the AVEVA Pipeline Operations for Liquids Administrator documentation.

Case–N/A

(Defect–4413715)

This defect fix addresses an issue where an error occurred when the Controller tried to validate the tank limit from the Advanced Database Editor (ADE) and easy eXtended Operator Station (ezXOS) applications. Now, a solution is applied to the TankalarmlimitValidation Business Logic Tier (BLT) and BLT_TANKALARMLIMIT.xec display to support ADE and ezXOS validation.

Case–960496417

(Defect–3691534)

This defect fix addresses an issue where a term alarm would not be re-announced if that term's holding period ended while the term was still in an alarm state but never returned to normal during the holding period. Now, a term that is in alarm at the end of its holding period has its alarm re-announced regardless of the Return-to-Normal history.

Case–960570418

(Defect–3917007)

This defect fix addresses an issue where the monitorBatchTransfer process generated multiple messages in the oasErrLog.log at Top-of-Day (TOD), Top-of-Week (TOW), and Top-of-Month (TOM). Now, unnecessary log entries are removed to prevent log flooding for an hour as the corresponding ticket action has already been completed.

Case–960572029

(Defect–3874077)

This defect fix addresses an issue where a Pipeline Monitor (PLM) record stopped calculating and alarming when a linepack PLM device was stale regardless of whether the Disable PLM due to Linepack Stale checkbox was selected or cleared. Now, when the Disable PLM due to Linepack Stale checkbox is unchecked, the PLM continues to calculate and alarm if needed.

Case–960574567

(Defect–3871388)

This defect fix addresses an issue where there was no mechanism to reset the volume fields on a Virtual Flow Computer (VFC) that stopped accumulating new volume deltas (because it had reached a huge value). Now, a reset mechanism is available to handle this situation. To apply the reset, the virtualflowcomputer.[vfc].flag.rtu_qsd can be set to Yes. On the next processing cycle, the VFC will recognize this as a signal to reset the IV and GSV fields to zero, and then it will automatically switch the rtu_qsd value back to No.

Notes: Resetting volume fields on a VFC could result in unexpected behavior if the VFC is used as an input into an active countdown or PLM record.

The use of rtu_qsd is an interim solution for this version of the product. Beginning with AVEVA Pipeline Operations for Liquids 2027, a more appropriate reset mechanism that aligns with other design improvements of the VFC application will be available.

Case–960581503

(Defect–3874122)

This defect fix addresses an issue with accumulators that are configured to support Positive and Negative accumulation mode, where a negative flow rate correctly caused the accumulator volume to decrement, but the volume of the parent Virtual Flow Computer (VFC) incorrectly remained unchanged. Now, the parent VFC will also observe the negative flow rate and apply the expected negative deltas to the volume.

Case–960586008

(Defect–3890747)

This defect fix addresses an issue where transitioning from a Drag Reducing Agent (DRA)-compatible product group to a DRA-incompatible product group and then back to the same DRA-compatible product group could result in the DRA pump not starting automatically. This behavior occurred when an additional violation check was configured in which, due to a race condition, prevented the DRA product group from being updated. Now, the DRA product group is always updated correctly and the pump will automatically start for DRA-compatible products.

Case–960587401

(Defect–3907061)

This defect fix addresses an issue where the Administrator was not able to use a status or multistate point in the Tank Idle configuration tab in ADE if the record name contained a hyphen (-). Now, the validation process no longer has this restriction.

Case–960587455

(Defect–3976595)

This defect fix addresses an issue where the Pipeline Monitor (PLM) application incorrectly reported that it had detected an invalid increment for a PLM device. This occurred when the PLM unit profile was changed to use a higher precision, which caused the comparison between the old value and the new value to use different rounding precisions and produce a negative delta. Now, the comparison uses the updated unit profile rounding precision for both old and new values before calculating the delta.

Case–960591783

(Defect–3917035)

This defect fix addresses an issue where, when the Correct for Roof option was enabled on a tank and the tank level exceeded the specified High Float Point, tank calculations did not use a correct unit for density. This caused gross observed volume calculations to stop and a calculation error alarm to be raised. Now, the correct strapping table density unit Application Programming Interface (API) is used to perform the calculations.

Case–960614761 

(Defect–4277365)

This defect fix addresses an issue where entries were missing from the Historical PLMCollect table due to intermittent connectivity issues with the Historical database. Now, the robustness of PLMCollect has been enhanced so that short term outages of the Historical service no longer cause the collection process to be abandoned. Error logging has also been improved so that persistent connection failures leading to abandoned collections are clearly logged as errors. In addition, the fix ensures that long connection times to Historical do not delay the reading of RealTime PLM records or affect the timestamp used to indicate the time of collection.

Case–960596640

(Defect–3951081)

This defect fix addresses an issue where PLM reset alarms that were raised even though the Inhibit Alarm on Changes To Normal option was selected. Now, reset actions will raise the Return-To-Normal (RTN) alarm only if the RTN alarms are not inhibited, or if the RTN alarms are inhibited but the original alarm was never acknowledged.

Case–960615622

(Defect–4000285)

This defect fix addresses an issue where, when a pipe segment was configured to apply smoothing (that is, Linepack Filter Constant < 1.0) and a change in pressure or temperature occurred, the linepack delta observed by PLM kept fluctuating between zero and non-zero values until the smoothing converged to a stable linepack value. Now, the delta linepack calculations have been corrected to prevent the fluctuations.

Case–960618323

(Defect–4280398)

This defect fix addresses an issue where the Tank Management application was experiencing a major delay when replicating data between sites. There is a shared memory queue that transfers data between the CMX replication server and the Tank Management application. When adding items to this queue, there was an unnecessary pause after each addition. Now, this pause has been removed.

Case–960618628

(Defect–3998100)

This defect fix addresses an issue where functional replication messages for Liquids Management System Pipeline Monitor (LMSPLM) and Batch Tracking (LMSPIPE) were not being passed on to the receiving site using the store and forward configuration. Now, the XFR_PATHINFO* ppathInfo output parameter is populated to ensure that PLM and Batch Tracking messages are stored and forwarded successfully to the receiving site.

Case–960642186

(Defect–4065620)

This defect fix addresses an issue where the Advanced Logic Processor (ALP) application did not process a field (status.*.cmded) that was added to ALPTypesAllowlist.json, reporting an unsupported numeric type error. Now, all numeric types are correctly evaluated by ALP.

Case–960646373

(Defect–4221266)

This defect fix addresses an issue where the connectivity record was being write locked before a lock was taken on the table, creating a scenario where a process following the normal lock order (table first, then record) could trigger a deadlock. Now, the lock order has been corrected to prevent such conflicts. The update also resolves a condition where inconsistent pipeline connectivity could previously lead to an infinite loop; the logic now terminates safely if the next connectivity item cannot be found. In addition, if the reversal of a connectivity record is unsuccessful, the system logs the specific record that encountered the failure.

Case–960658531

(Defect–4286507)

This defect fix addresses an issue where the Action Sequence designer did not persist connections between false ports and subsequent sequence steps as expected. Now, the Action Sequence designer ensures that all connections are persisted successfully.

Case–962606235

(Defect–4369877)

This defect addresses an issue where a nuisance Estimated Time of Arrival (ETA) batch alarm and event were raised against the node where the batch injection originated from. This was more commonly observed when the pipeline was reversed. Now, ETA alarms and events—for normal and reverse flow—will no longer be raised against nodes where the injection is originating from.

Case–962623052

(Defect–4361267)

This defect addresses an issue where Administrators could not configure a Flow Total as a flow input into a Pressmon record. Now, Administrators can use the following fields:

Flowtotalconfig.*.totalblocks[0].curval
Flowtotalconfig.*.totalblocks[1].curval
Flowtotalconfig.*.totalblocks[2].curval
Flowtotalconfig.*.totalblocks[3].curval

Case–962626940

(Defect–4286540)

This defect fix addresses an issue where an Administrator was unable to create a Batch Transfer or a Tank record on a non-owning system even if it had configuration privileges. Now, an unnecessary restriction is removed that required control privileges for the configuration change to be successful.

Case–962626940

(Defect–4367037)

This defect fix addresses an issue with the configuration of the Pressmon application where the acceptable range for pressure and flowrate deadbands was too restrictive. Now, the range has been expanded from 99 to 10,000.

Case–962666973

(Defect–4431848)

This defect fix resolves an issue where, when attempting to create an accumulator for a Virtual Flow Computer (VFC) with a name that exceeded the maximum allowed length, ADE correctly reported an error message but incorrectly created an accumulator with an invalid name. Now, ADE will not create the accumulator record if the name length validation fails.

Case–962719004

(User Story–4572057)

This fix addresses a limitation for remote ticketing plugins that do not receive an indication from the Flow Computer in the field to advance the pending queue. Now, the JSON configuration HostAlwaysAdvancesPendingQueue can be set to true to override the default behavior and instruct the host to always advance the pending queue, even if Batch Schedule Management is set to Field Device. For more information, see "Understand HostAlwaysAdvancesPendingQueue configuration" in the AVEVA Pipeline Operations for Liquids Administrator documentation.

Note: By default, this property is set to false. Only set this property to true after confirming that the remote ticketing plugin does not advance the pending queue. Otherwise, multiple queue advancements might take place.

Known issues

The following known issues were open at the time of this release.

Description	Workaround (If Applicable)
On initial start up of RealTime, unhandled exceptions in ReflexSubscribeCallback may be observed. This behavior does not prevent the normal functioning of the Reflex application.	None.
When associated with a Valve object, RealTime failover may log a CompareFieldTypes Business Logic Tier (BLT) failure error while evaluating an Advanced Logic Processor (ALP) expression. This is an intermittent failure and can be observed in the new Standby system after a failover. The error is logged when a BLT call is made while the RealTime service is in a premature state and unable to process the PubSub request. This behavior does not prevent the normal evaluation of the ALP expression.	None.
If Batch Tracking Compiler (BTC) changes are made to a pipeline while replication to the non-owning site is down, referential issues can cause system alarms to appear on the backup site when the connectivity is restored.	None.
A very high flow rate is observed at the accumulator when the associated rate point provides a negative flow rate reading. This known issue results from selecting the following values when configuring a Batch Transfer: When configuring the rate record (the record feeding the Accumulator), the record is specified as a telemetered pulse rate that does not have software accumulation enabled. When configuring the Accumulator (the record feeding the Virtual Flow Computer [VFC]), the record is specified with the previous pulse counter (rate) capable of going backwards, a volume accumulation mode that allows positive and negative flow, and a maximum reasonable reverse flow rate (vol/h) that allows backwards flow. When configuring the Batch Transfer, the record is configured using the VFC specified above as a source. If the above conditions are true, it is possible for the VFC to interpret a backwards moving pulse rate as negative flow. In addition, because the VFC is attached to a Batch Transfer, it is possible for the Batch Transfer to accumulate a negative volume from an individual device. This will cause the Batch Transfer to show a large value in the following fields: Flowrate, Volume To Go, Measured GSV, and NSV. This is most likely to occur if the negative movement in the pulse rate is observed immediately after a ticket split.	Ensure that each Accumulator is configured as Positive Only Volume Accumulation Mode to prevent the Accumulator from being able to roll backwards.

User documentation

For the AVEVA Pipeline Operations for Liquids 2025 Patch 1 release, only documentation that was directly affected by a defect fix is included. User documentation addendums are no longer included as part of patch deliverables.

If a document is not listed as updated in these notes, the existing AVEVA Pipeline Operations for Liquids 2025 documentation is still applicable.

The following AVEVA Pipeline Operations for Liquids documents contain updates and are included with this patch:

AVEVA Pipeline Operations for Liquids Release Notes (this document) (PDF)
AVEVA Pipeline Operations for Liquids Administrator documentation

The latest versions of all the documentation are available on the AVEVA Documentation Portal and on AVEVA Knowledge & Support Center.

To view the AVEVA Pipeline Operations for Liquids user documentation on the AVEVA Documentation Portal, sign in using your AVEVA product-support credentials (the same ones used for the AVEVA Knowledge & Support Center).