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.
-
Support interfaces on Windows IoT operating system
Allow interfaces and connectors to run on the Windows IoT operating system (formerly Windows Embedded)
21 votes -
Add an option to receive real-time data in client during buffer recovery
Add an option to receive real-time data in the client during recovery of buffered data:
The default behaviour of our interfaces / buffering is that after a connection failure the buffer will be flushed and data will be sent in it’s original order (which is correct behaviour). During that time, there is no view on the realtime (snapshot) data for end users.
Customer is asking for an option to not have to wait for the ‘new’ snapshot data.
It is clear that this would produce many OOO events, which will influence PI Data Archive performance and most probably will influence…
14 votes -
Customize UniInt Failover Sync File Permissions
Prior to UniInt v4.6.0.60, UFO sync files created during interface startup would inherit file permissions from their parent folder (assuming child inheritance had been enabled on the folder).
With UniInt v4.6.0.60, this behavior changed and now sync files created by the interface do not respect inheritance. Instead, they are created with a standard ACL containing only the local "Administrators" and "Users" security groups.
For users with complex file permission schemas, this change introduces additional, unnecessary configuration efforts that scale as interface numbers grow beyond the site-level.
8 votes -
Uni-Int to write to scan-class health tags on startup
We've noticed this particularly with the RDBMS-PI interface when configured for failover: Health tags that are only written to when the interface becomes primary or has completed its first scan (eg Point Count, Scan Class I/O Rate etc.) say 'Intf Shut' when the instance is actually in 'Backup' mode. Even when changing to Primary status, many of these tags don't get a value till after the first scan, which could be quite a long wait.
I would like UnitInt interfaces, on startup, to post an 'Initialising' or 'Awaiting 1st Scan' or some such digital state to all health tags that…
6 votes -
Add a watchdog counter to API shared memory
Add a watchdog counter or something similar into the shared memory header. If the counter fails to update, initiate UFO.
If PIBufSS crashes, data loss can occur. implement something that allows UniInt to know that the Buffer Subsystem is not responding and initiate failover if available.
This was previously enhancement 119481.
5 votes -
Allow PItoPI APS connector to sync "Point Type" changes
Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual).
Please make this possible in a future release.
4 votes -
DeltaV Smart Connector Enhancement
I think it would be a good idea to allow exception settings to be created. The DeltaV history collection settings only allow for compression. Since many/most users use 1/2 compression for their exception value then perhaps we could have a check box on install of the smart connector to turn a general exception rule on. The point of the smart connector is so that a user shouldn't have to modify tags after they are created from DeltaV.
The other enhancement that would be great is if we didn't have hard-coded security groups (DeltaV and Deltavadmin user) but could put in…
4 votes -
SNMP Interface to support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.
SNMP Interface should support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.
4 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 -
Support data collection across data diodes or similar technology
Regulatory and/or security requirement to separate data collection from data storage using a one-way data flow. Could apply to Interfaces or Connectors, for example PI Interface for Emerson Ovation.
PI Interface/Connector -> one-way data flow -> PI Server/EDS/OCS3 votes -
Assure changes made to any configuration of an interface are audit trailed
We noticed that changes to the configuration of newer interfaces / connectors like
- PI EMDVBCS interface 4.0
- PI inbatch interface
- PI Connector Wonderware Historian
are no longer recorded in the PI Audit trail. (see also TechSupport Case # 937205)
This is a compliance issue for the regulated industries.3 votes -
UniInt should include a test mode for all interfaces that collects data but does not send it to PI.
This functionality would allow users to test the connection to the data source and inspect the data that is retrieved without sending it to PI. That data might be written to a text file, for example.
This would allow users to verify settings and data integrity without needing to delete archived values, for example. Potentially, this functionality would also have some type of PI point selection so that user would be able to select which tags the interface should use for this test mode, rather than using all tags (The interface would essentially assume that all other tags have scan…
3 votes -
Improved handling of PI Write failures
Provide a configuration option in UniInt interfaces, to enable shutdown of the interface if it consistently receives error messages when attempting to write to PI. Recently had an interface successfully connect to PI but not achieve write access to its tags; would've been nice to have this interface gracefully shut down or restart, and allow its UFO failover partner to serve the data flow
2 votes -
Remotely view logs
I understand that you can remotely view logs using pigetmsg. However this solution does not work for me as the interface is on a controlled network that only allows outbound traffic. I would like a way for the interface node to be able to push out interface logs somewhere such as to my DA, that way I could use SMT to view my interface logs.
2 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.
2 votes -
Allow Buffer to communicate with other buffer
Currently the PI Buffer Subsystem only has the capability to speak directly with the Data Archive. This setup can have a negative impact on your Cyber Security setup as you are not able to leverage the DMZ between the IT/OT networks as it is designed.
This request is to allow the PI Buffer Subsystem to communicate with another buffer subsystem to act as a relay to the data archive and would allow all cyber security requirements to be met.
1 vote -
Managing loss of connectivity - local data
For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.
1 vote -
1 vote
-
Replace pipc.log and PI Message logs with the Event Viewer
PI Connectors already use the Event Viewer to log messages. It is time for PI Interfaces to do the same.
0 votes
- Don't see your idea?