Release Notes
- Last UpdatedJan 17, 2025
- 5 minute read
PI Interface for AVEVA Batch Management
Version 5.1.5.5
Overview
PI Interface for AVEVA Batch Management (formerly PI Interface for WonderWare InBatch) collects data from an AVEVA Batch Management Batch Execution System. The interface supports AVEVA Batch Management versions 8.1 SP1 and above. This interface creates Event Frames in PI AF based on data from AVEVA Batch Management. PI Tags and an AF Hierarchy are automatically created to capture additional context around your process data.
The 5.1.5.5 release of PI Interface for AVEVA Batch Management internally replaces PI SDK with AF SDK - this improves the security, robustness, and communication capabilities of the interface. As a result, this interface only writes Event Frames to a PI AF Server, and disallows creating PI Batches in the PI Batch Database.
Users creating PI Batches in the PI Batch Database need to migrate to Event Frames in order to utilize this version of the interface.
Enhancements
There are no enhancements for this release.
Fixes
This section lists items that were resolved or added in this release of PI Interface for AVEVA Batch Management.
|
Work Item |
Description |
|---|---|
|
22133 |
Attribute values referencing other event frames are captured regardless of the order event frames are created. |
|
22140 |
Unirecord data sources are now included in unirecord imports and exports. |
|
22156 |
Cache start and end times can no longer be permanently altered by arbitration events. |
|
22163 |
SQL Native client print message was disabled for Oracle based interfaces. |
|
22172 |
When removing an interface from PI Event Frames Interface Manager, it will also remove any associated services. |
|
22181 |
When adding an interface to PI Event Frames Interface Manager, the instance ID will be initialized as the same value of interface ID. |
|
22209 |
Interface will no longer have a delay in processing a batch when the local time is greater than GMT. |
|
22211 |
MONITORTAGWINDOW now defaults to 0, meaning monitor tag counts don't get trimmed to the most recent days of activity and roll over at INT_MAX unless MONITORTAGWINDOW is deliberately set. |
|
22216 |
Interface ID has been added to the message logs in order to uniquely identify log message. |
|
22218 |
All generated unirecords will have the placeholder [TIMESTAMP] have the format "YYYY-MM-DD" for a SQL source and "YYYY/MM/DD" for non SQL source like EVT files. |
|
22221 |
Monitor tags now accurately reflect the number of batches and their child events. |
|
22224 |
Bifconfig properly creates new default virtual user service without errors. |
|
22235 |
Interface configuration for RST and RET reads UnitedStates format standard. |
|
22245 |
The unit procedure batch id attribute is controlled by the unit procedure recipe template batchid. |
|
22246 |
BifConfig does not allow older interfaces to edit health tags. |
|
22249 |
All batch interfaces remove passwords from INI file regardless of parameter capitalization. |
|
22250 |
Merging issue causes unit procedure and operation not to close. |
|
22260 |
Batch event frames no longer merge event frames when merging is disabled and unique ids don't match. |
|
22268 |
All RST and RET within the configuration will be parsed as US format. Fix in current development branch and in 4.3.x.x Branch. |
|
22275 |
A check that verifies that a Procedure Event Frame and a Unit Procedure Event Frame are both generated by the same interface instance before linking them together. |
|
22283 |
The Event log source is created during the interface install step. |
|
22464 |
For interfaces with a version 5.0.0 or greater, PI Event Frames Interface manager nows tail the windows event viewer instead of PI Message log. |
|
23177 |
BifConfig now stores RST and RET as UTC Note that they can be edited in a local friendly time string and read into the interface correctly. When written by the configuration program, they will write the times out as UTC and a local time string as a comment. |
|
23747 |
A delay (/DELAYBUFFER) was added so the source data is available at the time of query. This helps event start times. |
|
23793 |
The Event log source will be created as part of the setup process. |
|
23794 |
PI Interface for Wonderware InBatch is now AVEVA Batch Management. |
|
24781 |
The interface setup kit is using the same GUID for all the interface. This causes trouble when installing another batch interface on the same machine. Fixed to use different GUID for each interface. |
|
24847 |
SQL Native Client is no longer supported, and is now replaced with OLEDB for all supported batch interfaces. |
|
49860 |
Configuration "USECLOSEEVENTSONLY" when checked in the PI Event Frame Manager will work properly. |
|
67289 |
UniRecord exports now include all UniRecord fields. |
|
67650 |
Event sorting is faster and memory consumption is better managed during event queuing. |
|
67926 |
Interface will not allow Batch events with a zero start time. |
|
68207 |
BifConfig will now store SCAN values as low as one second without complaint. |
|
68907 |
Default account to setup interface service is now Default Virtual User (NT Service/). |
|
70398 |
Float tag values are now evaluated correctly. |
|
70403 |
Message logging now includes exception data. |
|
70471 |
Very long log messages are successfully logged. |
|
72522 |
Interface stability improvements have been completed. |
|
73489 |
Interface no longer hangs due to locale thread lock issue. |
|
73498 |
Setup kit creates the event source name under application logs to match with Interface application name which is used by logging framework. |
|
75880 |
Procedure level recipe events are processed correctly and have no missing end times. |
Known Issues
There are no known issues for this release.
System Requirements
Operating Systems
This interface is a 64-bit application.
|
Platform |
64-bit Application |
|---|---|
|
Windows Server 2022 (64-bit) |
Yes |
|
Windows Server 2019 (64-bit) |
Yes |
|
Windows Server 2016 (64-bit) |
Yes |
|
Windows 11 (64-bit) |
Yes |
|
Windows 10 (64-bit) |
Yes |
Distribution Kit Files
|
Product |
Software Version |
|---|---|
|
Microsoft Visual C++ 2015-2019 Redistributable (x86) |
14.21.27702 |
|
Microsoft Visual C++ 2015-2019 Redistributable (x64) |
14.21.27702 |
|
PI AF Client 2018 SP3 Patch 4 |
2.10.10.2539 |
|
AVEVA Batch Management (AVEVABatchManagement) |
5.1.5.5 |
|
PI Network Subsystem Support (PINS)* |
3.4.435.538 |
*The PI Network Subsystem Support (PINS) component is not displayed on the installation welcome screen if the PI Data Archive is installed already.
Installation and Upgrade
The PI Interface for AVEVA Batch Management can be installed or upgraded using the AVEVA Batch Management installation kit, AVEVABatchManagement_5.1.5.5_.exe. This installation kit can be obtained by using the How to Download Products link listed in the AVEVA Customer Portal How To's list. This list is located on the AVEVA Customer Portal.
For additional information regarding the PI Interface for AVEVA Batch Management installation, please see the Installation instructions portion of the PI Interface for AVEVA Batch Management (PIBatchGuide) User Guide. This user guide is available for download from the AVEVA Customer Portal.
Uninstalling PI Web API
The PI Interface for AVEVA Batch Management can be uninstalled using the Programs and Features list accessible from the Windows Control Panel. After accessing the Programs and Features list, select the entry named AVEVA Batch Management (AVEVABatchManagement) and then select Uninstall from the menu.
Security information and guidance
We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.
We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release. The tables below provide an overview of security issues addressed and their relative severity based on standard scoring.
There are no security vulnerabilities in this release.