When Eventframe Batches are created by a Batch Interface, the used Unit in the plant is created as Element in AF and linked to the Unitprocedure EventFrame. Unfortunately it is not linked to the parent Procedure Event, leaving the "referenced Element" list of procedure event empty.
If a user wants to create a report over all Procedures a certain unit was involved, he has to download all Procedure Events and Unitprocedures via Datalink and do the filtering there.
With PI Batch it was possible to search for PI Batches using PI UnitBatch criteria like Unitname. We need this feature in Eventframes as well and could achive this by linking the referenced Elements of the child Unitprocedures to the Procedure Event or by creating a new filter mechanism in the eventsearch. I would prefer the referenced elements though.

The current EFGen interface "Status" health tag displays a value of "Good" if it is connected to the data source but does not factor in if it is writing Event Frame data to PI. There is not currently a straightforward way to drive a PI Notification to alert that there may be an interface issue in the scenario that the interface is connected to the data source but can not write event frames. Either the criteria for what results in a status of "Good" needs to be revisited to include both connectivity to the source data as well as actively writing Event Frames, or a new parameter should exist to allow end users to see when the last successful Event Frame was written. That would allow users to send notifications if new event frames have not been written for a certain number of hours or days, so that a PI Administrator may inspect the interface to ensure it is operating as expected.

Hello,
the PI Event Frames Interface Manager application must be run in the same machine that hosts the PIEFGen interface. This is an issue regarding our security rules because, the PIEFgen interface runs in secured machines and we don't want to allow users to RDP to these machines only for setting batch configuration (triggers, batch nr...) .

This issue did not exist with PIBatchgen as the setting of batch configuration (triggers, batch nr ...) was available inside PI SMT.

It would be great to either be able to run PI Event Frames Interface Manager in a different computer or to be able to set up the batches through PI SMT.

Using EFGen, currently an EF can only be triggered based on the zeroth state of the Active Point. This makes is impossible to trigger different events based on specific values of a single PI Tag.

I am trying to implement a batch structure using Event Frames with production run as the parent and different phases of the run as children. I have a single PI Tag that lists the current phase of the run in real time. It would be nice to be able to trigger the phase child events based on the specific string values of this tag.

PI System Explorer has the ability to trigger EF's using Tag values/logic/calculation, but it lacks the EF structure capability.

There are workarounds for this issue, but they are too messy to realistically implement with ease.

Currently the interface creates PI UnitBatches or Event Frames associated to Units (PI Units or AF Elements) determined by some placeholders specified at the "Unit Procedure" level; the default is "[AREA][PROCESSCELL][UNIT]".
Moreover the interface properly created a PI MDB or AF structure under an alternate module path, specified in "Batch Setup" section (/SMP parameter).

It would be useful to have a way to specify different Units instead of the one determined by the [UNIT] placeholder (at least).
As an example, suppose we want to register unit batches for a PI Unit called Reactor1" when the [UNIT] placeholder values "U6-K54100", and unit batches for a PI Unit called "Reactor2" when the [UNIT] placeholder values "U6-K54200".

a lot of your existing Batch Interfaces are based on RDBMS (Simatic Batch, DeltaV, ABB). But there will always be some Batchstorage solutions based on a relational database which are not included in your source system list. For now Honeywell Procedure Analyst or ABB Workflowmanager are such systems.
If we users had a generic RDBMS to Eventframe Batch Interface where we could do the mapping between relationale database rows and your typical Batch Interface placeholders by our own and define triggers for different batch levels just like we can define triggers now for additional batchinformation, we could connect to a much wider range of batchstorages to transmitt data to Eventframes.