According to https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=3645819457236571808-241124 , any number larger than 99 can NOT be specified for PI UFL Service ID. It would be better for us if the larger number such as 300 could be specified.

Hi,

Existing EFGEN does not seem to support multi language (Double bytes characters) inputs for Event frame name. This result in the event frames names are being recorded in English char only.

Would it be possible to implement the multi-language (Double bytes characters) into EFGEN Event frame name?

PI Interface for CA ISO ADS can extract data from XML fields. Under the Instruction Detail field, there are multiple MW, serviceType, and segNo fields. Presently, retrieving those values in a PI tag (for example, instrument tag "MW,ResID") returns values for all of the particular field under that resource ID.

It would be beneficial to be able to extract MW values for only one segNo or serviceType under the particular Resource ID, as getting all of the values at once does not make sense in a PI tag.

PI OPCClient able to sort List of all structure instances. Currently: Chronologically is pretty annoying.

While listing the content of opc server structure, the folders are not listed alphabetically.

While there are many items, export is not possible - pi opc client crashes

This could enhance the user experience and be more user friendly.

Searching takes a long time.

We currently use the Cybectec interface to relay information into our PI system. It is our understanding that the latest certified OS is Windows Server 2012 R2. We are currently going through a upgrade of our PI system and our standard OS for deployment is Windows 2019. We would like to request that the Cybectec interface is certified with Windows 2019 (or at least 2016) to ensure that we are supported in our environment. Using Windows Server 2012 R2 will require us to complete another upgrade (server) in 2023 as the OS will be end of life.

Allow the PI Interface for Werum PAS-X Batch to create event frames for Interface Basic Function created by the Message Based Shopfloor Integration (MSI) feature package for Werum PAS-X. The Interface Basic Function describe the communication between PAS-X and the ordering system e.g. DCS, with order parameters for workflows, status and exceptions etc.

Allow EFGen to use a Mix of PITAG + Text for the Creation of event frame names . Concatenate a Text + PITAG for example

Release a new version of the interface where it does not depend on the 1.x version of log4j rather the most recent and secure version of log4j. This is to improve security.

Note: The Log4j 1.x version installed with the interface is not a part of the security vulnerabilities found in 2021.

Update PI Interface for GE HABConnect codebase to 64bit to make use of latest Habconnect API v5.11.

Up to PI EFGen 4.0, we were able to backfill OOO Event Frames by simply inputting the start and end time of the corresponding period. Since 4.1, this must be done in a per-event basis, since larger time ranges are modified so that RST matches the start of the latest active event and OOO EFs are missed.

PI Interfaces for Batch allow source batches to be merged into one merge batch and then store the source batch properties as extended properties on the event frame. There should be an option to show source batches of merged batches as child event frames rather than extended properties.

The interface can retrieves Report events [Event,value="Report"].
Within these events, [Descript] - parameter returning "category" from SQL database.
We could not retrieve "description" column contents from the SQL DB [BReportEvent] table.
See case 00902899.

Have the functionality to change the Point Type from the PSSS, because it cannot edit Point Type for existing PI Points.

We are in need of a PI Batch/AF Events Interface to store data from Honeywell Experion Batch or Honeywell Procedure Analyst into PI Asset Framework.

Add a feature that performs a verification check of the data in PI against data in the DeltaV Historian and provide a report of any missing or mismatched data.

Add a feature that performs a verification check of the data in PI against data in the DeltaV Historian and provide a report of any missing or mismatched data.