Allow a way to bulk edit EFGen configuration, preferably in a spreadsheet format.

Unlike other PI interfaces, the Batch Framework Interfaces do not use buffering. If the interface loses connection to the PI Data Archive, the interface continues collecting data and stores it in its local cache. The PI Batch Database is primary-only so it did not make sense to fan data to other PI Collective members. However, this is no longer a consideration if Event Frames are being written. There should be an officially tested and supported way to fan tag data to a PI Collective.

When my EFGen Active Point tags have a null value, the interface should be able to designate this as a Zeroth State.

The interface can automatically create an element at each level of event frames, but the elements do not derive from a template and there is no way to specify any attributes on the element. The enhancement request is to create elements that are based off of different templates for different Event Frame levels it would allow categories, default attributes, etc. to be assigned to the elements associated with the Event Frames.

When run in delete mode for WWInBatch interface, it uses the data source as the system of record--any open batch in SQL will be deleted. However, as abandoned or done  batches are open in WonderWare but closed in PI, the interface may delete batches in PI that are still open in the source. It would be helpful if the interface gave the option of using PI as the system of record regarding batch end times.

When my EFGen Active Point tags have a type of digital, the interface should allow certain digital states to be designated as a Zeroth State.

As a PI Admin, I may have already created a AF Element Hierarchy corresponding to my BES or MES source data. Therefore I have no need for the interface to create a new AF Elements and I would like to suppress this completely.

To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running  in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.

119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
119363 - Consecutive subbatches can get merged incorrectly

Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.

PI EMDVB Interface - Rename Parsed Files.  Files that get renamed to .999 is no longer available with PI EMDVB.  This file renaming feature was very useful from a system maintenance perspective.  We would easily remove .999 from the active EVT folder and move to an offline directory.  Currently with PI EMDVB, there is no obvious visual indication that the EVT file was parsed completely.

As a PI System Admin, I would like to see a confirmation window (acceptation pop-up message), when deleting Interface instances in PI Event Frames Interface Manager. This would minimize the deletion of the instances by error.

Some of the fields incoming from the DCS are user entered and prone to errors. Please allow for the option to include slightly different logics to be able to filter out those user errors (such as empty spaces at the end of the string, etc).

PI EMDVB interface stops because of time difference between SQL and PI servers:

"Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

Currently UserID (DoneBy_User_ID) and ReviewerID (CheckBy_User_ID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

Currently, Batch Interface Framework interfaces implement tag template triggers that can trigger whenever a placeholder has any value. These interfaces should also support triggering when a placeholder does not have a value. For example, our SISBatch data source has separate columns for Operation and Phase information. We would like to record the value of the [DESCRIPT] column in a tag only for non-phase batch events (i.e. trigger the tag template only when the [PHASE] placeholder is blank).

The BES/MES sometimes contains recipes with no Procedure, or even Unit Procedure. The Batch Framework Interfaces should allow the creation of only the Event Frame levels that exist on the data source. This would need to be enabled with an interface configuration parameter so the default behavior is not changed on upgrades to existing systems. This enhancement would not be possible when writing to the PI Batch Database.

As a Batch Framework Interface user, I would like to filter my batch data by whitelisting. Currently the only option is blacklisting. This is inconvenient, for example, if data is only desired from a few units. Each time a new unit is added to the data source, the interface configuration must be updated.

in order to eliminate unwanted or noise event which be triggered and recovered in a short period.

Batch Framework Interfaces - [TIME] and [TIMESTAMP] placeholders should consider whether TS=LCL is configured (meaning the interface is processing incoming events as Local Time). Currently, values of these placeholders always show up as GMT timestamps.