PI Interfaces
Welcome to the
PI Interfaces feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
PI Werum PAS-X Batch Interface - Event frame creation for Interface Basic Functions
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.
1 vote -
Create event frames from DeltaV Alarms & Events (EMDVB)
Alarm tags created by EMDVB can be difficult to analyze at scale. Event frames are a natural format for alarms because they have start and end times, durations, and can have different severities. PI client tools allow simple querying of event frames and let us to easily view our alarms in context of process data. Additionally it is easier to analyze EFs at scale using BI tools.
It would be valuable if EMDVB could automatically generate event frames from the DeltaV Event Chronicle and associate it with elements in AF. For example, we may want to specify the event frame…
2 votes -
efgen
Allow EFGen to use a Mix of PITAG + Text for the Creation of event frame names . Concatenate a Text + PITAG for example
5 votes -
PI EFGen 4.1+ has limited recovery capabilities
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.
6 votes -
Provide an option to show source batches of merged batches as child event frames
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.
1 vote -
PI EMDVB Interface - Allow to retrieve "description" column content from SQL DB
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.2 votes -
Batch Interface for Honeywell Experion
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.
4 votes -
Data Verification for the PI Interface for Emerson DeltaV Batch
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.
3 votes -
Data Verification for the PI Interface for Emerson DeltaV Batch
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.
1 vote -
Add support for workgroups for PI Interface for Emerson DeltaV Syncade
Add support for workgroups for PI Interface for Emerson DeltaV Syncade
3 votes -
Allow using SQL as a data source for FactoryTalk Batch
Rockwell FactoryTalk Batch v12.01 allows to output batch data to a SQL database as well as EVT files. Just like with EMDVB, the PI Interface for FTBatch should be able to use both data sources.
7 votes -
Capture data from ABB 800xA that doesn't follow ISA88
ABB 800xA offers a batch capture mode that is more flexible than ISA88 since it doesn't match all unit procedures to units, but rather acquires them at the beginning of the batch. Currently the interface is designed to only retrieve batches that follow the ISA88 model.
4 votes -
Support Werum PAS|X 3.2 and PAS|X Data Access (PDA)
Werum has recently released the next version of their PAS|X Database, and it bolsters a new method of Data Access. OSIsoft will need to release an re-tooled version of their PI Interface for Werum PAS|X to support this latest Werum version and the new data access method.
8 votes -
Improve the recovery process for long EFGEN batches
Currently if EFGEN is configured to evaluate PI Points at the event end, long batches require recovery start time to be set before the start of the batch. This leads to a long recovery process as many completed batches will be evaluated again.
2 votes -
Fix MAXSTOPTIME parameter for batch interfaces
The MAXSTOPTIME parameter for batch interfaces does not kill the interface process when the limit is exceeded, however the parameter does work for UniInt based interfaces. Please fix the batch interfaces so that the interface process is killed once the MAXSTOPTIME has elapsed.
3 votes -
Enhance how batch interfaces write to the message logs
Batch interfaces should write their messages to the message logs using the Source1 and Source2 fields just like UniInt based interfaces. Currently, batch interfaces leave these 2 fields blank. Source1 should contain the process name or similar and Source2 should contain a string in the format of "<PointSource> | <Location1/ID> | <FailoverID>". Having this will greatly help PI administrators filter the logs based on point source, especially when there are 20+ interfaces running on a server.
3 votes -
Allow diagnostic tags per failover node for batch interfaces
Batch interfaces should allow for diagnostic tags per failover node, just like UniInt based interfaces. Currently, there is no differentiation between the diagnostic tags for the primary failover node versus the backup failover node. The Location3 field is used to hold the failover ID of UniInt based interfaces so that there is a unique set of tags per failover node, however for some bizarre reason the Location3 field for batch interfaces stores the diagnostic tag index even though the diagnostic tag pointer exists in the ExDesc field. While not all diagnostics tags may be of interest for the backup node,…
3 votes -
Allow renaming of diagnostic tags for batch interfaces
Batch interfaces should follow a similar approach to UniInt based interfaces to retrieve the diagnostic tags. That is to say they should pull the diagnostic tags based on the PointSource, Location1, and ExDesc, not a hardcoded name based purely on EXE name and Location1. This would allow the PI admin to name tags to their organization's naming convention and also avoid naming conflicts between interface instances of the same type running on another interface node.
4 votes -
Add the ability to create custom Performance tag names for the PI Batch Interfaces
Add the ability to create custom Performance tag names for the PI Batch Interfaces.
For systems with numerous batch interfaces the Performance tag naming convention does not intuitively distinguish between interface instances since the Interface ID is the only unique text in the tag name.
1 vote -
Change sequencing in PI Interface for Emerson DeltaV Syncade Batch for improved data analytics
Please view attached PDF
1 vote
- Don't see your idea?