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 Interface for OPC AE Instrument tag any attibute should work
As now it is just Source and Area event attributes that work for the instrument tag. It should be possible for any attribute to work as a filter in instrument tag. It is not every OPC AE server that supports Source and Area.
23 votes -
PI Interface for Foxboro I/A 70 Series should support Windows 2016 and I/A Version 9.4
The PI Foxboro Interface should support the new Foxboro platform on Windows Server 2016 and I/A Version 9.4.
21 votes -
Support float64 point type in PI Interface for China Network Isolator
China Network Isolator interface does not support float64 point type, which is required by many customers in China. Right now, they have to change the point type to string first and then to float64 by analytics, this will consume two times of license number.
19 votes -
OPC Alarms&Events interface should natively support event frame creation
As a PI Interface for OPC Alarms & Events user that would like to leverage AF Event Frames for more advanced analysis, I would like for the OPC AE interface to have an option to natively create event frames that open when a Status = Active message is received and close when the corresponding Status = Inactive message is received. This could be similar to the existing Batch Framework Interfaces.
Currently it is very difficult to use the Analysis Service to correctly open/close event frames because the OPC AE interface writes different alarms to the same tags and multiple alarms…
17 votes -
Store bad quality from OPC XML DA Server
Enhance the OPC XML DA Interface to store bad quality values from its OPC XML DA Server in PI, so that the values, timestamp and status from bad quality data are saved in PI.
Note: This is work item 21742OSI8 - Add support of data quality.
15 votes -
Update the CA ISO interface in preparation for the upcoming API V8 deployment
CA ISO is planning to upgrade its ADS (automated dispatch system) to version 8. This upgrade introduces breaking changes from the current system, API version 7.
The CA ISO interface should be updated to account for these changes.
14 votesAdminAllison Muraski (Admin, OSIsoft) responded
The current information available from CA ISO indicates the go-live of ADS API V8 and the decommissioning of ADS API V6. We have confirmed with CA ISO technical support that ADS API V7 will continue to be supported. The PI Interface for CA ISO ADS Web Service is compatible with ADS API V7, so at this time we do not plan to make any changes to the OSIsoft Interface.
-
PI Interface for SNMP accounting for Dynamic OIDs
Certain MIB files use dynamic indices which make dynamic OIDs. As the interface uses OIDs in the instrument tag manual action is needed to repair it should the OID change. This is particularly prevalent when using the HOST-RESOURCES-MIB, which uses process ID as its index.
12 votes -
Encrypt trafic between interfaces/connectors and the Data Archive
Add an option to encrypt trafic between interfaces/connectors and the PI Data Archive
10 votes -
PI BACnet interface: add support for BACnet Setpoint object
Add support for BACnet Setpoint objects in the PI BACnet interface.
10 votes -
Enhance WMI interface to verify that ACE Class Libraries are running
PI-ACE Manager looks at the PI-Module Database to see if the individual modules are running. The Class Library sub-processes updates the PI-MDB when it starts & stops. If the process dies, it does not always update the PI-MDB values. So, there is no supported way to verify if the Class Library sub-process is running.
The PerfMon interface can't monitor the existence of the process. I have found that I can use the OSIWMI interface to find the Class Library process based on the Command Line of the process.
The WMI interface will only update the PI tag if the process…
9 votes -
PI AMI Itron Interface support for TLS1.3
PI AMI Itron Interface currently supports TLS1.1. Microsoft ended support for TLS1.1 in March 2020. To keep the PI AMI Itron Interface usable with latest browsers, please update to support TLS1.3.
6 votesWe are currently evaluating the work necessary to update the PI AMI Itron Interface to offer support for TLS 1.3.
-
OPC AE: add history recovery feature
There is a stronger market demand to have more alarm data in PI so that the alarms can be analysed together with the process data. Existing (as of Oct 2019) PI OPC AE Interface does not support history recovery. Without the history recovery feature (automatic or manual), the interface is less reliable in terms of data loss possibility, especially in highly regulated industries such as Pharmaceuticals. On the control system side, OPC Historical Alarm and Events data access (OPC H A&E) is already available, for example for Siemens PCS7 with their product OpenPCS7. Requesting OSIsoft to look into adding this…
6 votes -
DeltaV Smart Connector configurability
Smart Connector foo DeltaV should let user configure some default attributes for tags created:
- User should be able to define what the default point security should be
- User should be able to decide if tags should be created as Poll or Advise6 votes -
PI Interface for IEEE C37.118 support for Analog data Signed and Unsigned 16-bit Integers
The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface
6 votes -
Update GE iFix interface compatibility information
As an interfaces user, I would like to know which versions of iFIX and Windows Server OS are compatible with the PI Interface for GE iFix so that I can determine whether this interface is suitable for my use case.
The last update for this interface was in 2014, so there has been no testing on compatibility since iFIX 5.5, but I am looking to use versions 5.8, 5.9, and 6.0 and Windows Server 2016.
5 votes -
Add a Trace Route feature to PI Ping interface
Add ping -i feature to the interface and allow for either the output of the ping time or destination in the PI tag.
Case: This will allow for IT to monitor the network path taken in communication from one site to another. If the route has changed in the communication of devices, we will be able to track it in PI and know exactly when the route changed.
5 votes -
CA ISO Interface - Allow conversion of timestamp values (i.e. InstructionStart) from UTC to local time
Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences. Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives.
Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.
5 votes -
5 votes
-
Allow PI APS to rename PI Points
PI APS is now not able to rename a PI Point name. If the item name is changed on the Datasource side we wish that APS rename the Pi Point.
5 votes -
DNP3: store data as "bad"
Add functionality to treat the data as "bad" and send a digital state instead, when status flags are sent with the event and status bits are set to TRUE. Right now, the data is sent to PI and marked as "questionable".
Note: This was previously Enhancement 125605.
5 votes
- Don't see your idea?