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.
-
Retire 32-bit versions of PI Interfaces that have a 64-bit version
These days, 32-bit operating systems are used for 1 of 2 reasons:
• Somebody accidentally installed the 32-bit version instead of the 64-bit version, which is a mistake that OSIsoft has no obligation to accommodate.
• The computer is very old, in which case it is due for an upgrade. If companies want to keep their operating systems up to date, they will need to replace their computers because of the minimum hardware requirements of Windows 11 and because Windows 11 does not have a 32-bit version. The replacement computers will be able to run the 64-bit versions of PI…
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.
3 votes -
PI interface for OPC .. UA
it would be useful to have an interface that can connect and retrieve data from OPC UA server. it will help to avoid using any additional software for "downgrading" the protocol to OPC at client side.
3 votes -
MV90 interface
We see some value in getting a read/write interface with Itron's MV90 billing system database. Being able to see billing interval billing data in PI would be valuable as well as being able to transfer billing data between other partners via PI to PI interface would solve a rather complex data exchange issue going on in the utility space.
3 votes -
Add support for workgroups for PI Interface for Emerson DeltaV Syncade
Add support for workgroups for PI Interface for Emerson DeltaV Syncade
3 votes -
PI Interface for GSE D/3 Compatibility Testing With Latest D/3 DBA Software
As of writing, the current version of the PI Interface for GSE D/3 (v 4.32.0.50) supports versions of D/3 up to 14.1-2 (consult the latest user guide for more details). It has not yet been tested for compatibility against more recent versions of NovaTech D/3 (versions 15 and 16). However, users and NovaTech have reported successful deployments of this interface against versions 15 and 16, most likely due to a lack of database changes between versions 14.1-2 -> 15, and 15 -> 16. Can the interface officially support compatibility for use with more recent versions of NovaTech D/3 DCS (versions…
3 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.
3 votes -
Allowing output point with source tag to keep working even after switching to secondary server
When primary server is down, secondary server is accessed instead of primary server, which is good. However, in the case of output point with source tag, it stops working, then restarting the interface instance of interest is needed. Of course, if we set up UniInt Failover that backup instance keeps its session with secondary server, this issue can be prevented. But, it will be better if source tag is also switched to secondary server.
3 votes -
Add a configuration option to UniInt so that the user can adjust the minimum wait time for checking for new events from the Update Manager
This affects the delay in Event\Trigger tags. KCS: Delay in Event Points.
The largest and most variable delay seems to come from the time the event is written to the PI Server and the time the interface (UniInt) picks, which is between 0ms-1,000ms from my testing. This seems to be due to a built-in, hard-coded, delay in how often UniInt checks for events from the PI Server update manager. The serviceeventsx function that is part of the main UniInt loop only checks for new events once a second; this means that sometimes there is no delay if the…
3 votes -
Add a configuration option to the OPC DA Interface so that the user can adjust the maximum advise tag exception delay for Event/Trigger tags
This affect to delay in Event\Trigger points. KCS: Delay in Event Points.
When using Event Points, we purposefully do have a delay (if excMax is > 2 s then 2 s else 0.9*excMax) for advise tags (Trigger Point) before they're sent to the PI Server if the event value has not changed since the last scan.
3 votes -
Manage interface names with service ID
As a PI system administrator, I would like to use the service ID to define the interface name so that I can organize and manage my interfaces more efficiently. I am currently able to do this with PItoPI but not UFL x64.
Ideally, I would like to define my service ID with a descriptor (e.g. <pointsource>-<instance ID>) so that my interface is named with this descriptor in PI ICU, PI SMT, Windows Services, and the PIHOME Interfaces directory. With this naming parameter:
– The interface would be listed in PI ICU & PI SMT as PIUFL<pointsource>-<instance ID>
–…3 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 -
PI UFL Interface to extract data from csv files from multiple sub-folders within the main folder.
In case of csv files in subfolders within Main Path for UFl, PI UFL Interface should be able to search the csv files with placeholder and extract data from csv files from multiple sub-folders within the main folder.
3 votes -
Interface TCP\IP para Data-Logger Davis (WeatherlinkIP)
Se recomienda agregar funcionalidad para adquiquirir datos de un DataLogger WeatherlinkIP, ya que actualmente solo se soporta conexiones seriales con este data Logger:
Davis Vantage Pro / Pro Plus Weather Station (NTI)
Davis Weather Station (NTI)Tener en cuenta que actualmente todas tecnología se basa en conexiones TCP\IP.
https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/
3 votes -
PI Interface for ABB Web Imaging System via ABB CNI
CNI interface should support message 25. Currently, we do not support any message beyond 22.
3 votes -
Preferring a primary interface failover member
hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.
https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector
3 votes -
Buffering Manager - add metrics for each buffered interface
When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.
3 votes -
Monthly scans
Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".
3 votes
- Don't see your idea?