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.
-
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 -
Ability to wait successful connection to PI Data Archive and download PI point information during startup
(Posted on behalf of our customer)
It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.
3 votes -
PI Interface for GE HABConnect FLDTIME Support for COUNT Objects
Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.
3 votes -
PI Buffer subsystem - management tool + robustness improvement
- Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
- Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.
3 votes -
Parameter for restarting the interface if no connection to the OPC server can be established after a defined period of time
We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.
3 votes -
Double check window required when deleting an instance in PI Event Frames Interface Manager
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.
3 votes -
PI UFL Interface can read input files from non-UNC paths such as Azure File share
I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.
3 votes -
UNIINT Interfaces and Connectors should be able to retry an output event if output write fails
When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on. User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.
3 votes -
PI-SNMPTrap interface request support for SNMPv3 trap
PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.
Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.
3 votes -
PI PerfMon tags to support Timestamp DataType
There are some performance counters that are Date and Time based.
PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.
3 votes -
Option for PI Interface for UFL to purge read-only files
Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.
3 votes -
PI ICU should not allow PItoPI COLD failover configuration
As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, the PI Interface configuration utility still allows COLD failover to be selected. This leads to an invalid configuration and the interface refuses to start.
PI ICU should not allow the selection of COLD failover as it does not allow HOT failover, both of which are not supported by the interface.
3 votes -
DNP3: handle invalid timestamps from the RTU
If the RTU provides a timestamp of 0 when using RTU provided timestamps, which does not conform to the DNP3 spec, allow the option to timestamp the event with PI time or drop the event altogether.
Note: This was previously Enhancement 123208.
3 votes -
PI Interface for CA ISO ADS - Allow retrieval of individual items under the Instruction Details xml field
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.
2 votes -
Upgrade Cybectec PI Interface to work with Windows Server 2016/2019
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.
2 votes -
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 -
Migrate the PI Universal Interface (UniInt) Framework to use PI AF SDK
Most PI Interfaces are based on the PI Universal Interface (UniInt) Framework and rely on PI API and its successor, PI SDK. PI SDK has, in turn, been superseded by PI AF SDK. PI SDK also relies on the deprecated and insecure ActiveX technology, which PI AF SDK does not use. I don't know or want to think about how insecure PI API is, even when the Windows Integrated Security version is used.
For many data sources, the only OSIsoft-supported option to get data from the data source to PI is a PI Interface, partly because an equivalent PI Connector…
2 votes -
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
- Don't see your idea?