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.
-
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 -
Add SOAP 1.2 support to the PI Interface for OPC XML-DA
The current version of the PI Interface for OPC XML-DA seems to only support SOAP 1.1. All recent OPC XML-DA servers are developed following SOAP 1.2 standards, meaning the PI interface will not connect. Please enhance the interface to also support servers using the newer SOAP 1.2 standards.
This also relates to tech support case 00857284
33 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 -
64bit PI Interface for GE HABConnect
Update PI Interface for GE HABConnect codebase to 64bit to make use of latest Habconnect API v5.11.
5 votes -
Allow PI-ICU to Create/Edit Stored Credentials in Credential Manager
An issue we run into often is that most of the accounts that are used to run our interfaces (mostly OPC DA) are different from accounts we use to configure the interfaces. Because these interfaces run on different domains, we have to store an account that can authenticate with the PI server in Credential Manager. This is easy to update for the logged in user but much more difficult for the service that runs the interface. Lots of times these accounts are not able to log in interactively and also are admin type accounts that the control systems personnel want…
5 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.
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 -
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 -
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 -
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 -
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 -
Update PI AMI Interface for OpenWay Collection Engine v1.8.1.124
Release a new version of the interface where it does not depend on the 1.x version of log4j rather the most recent and secure version of log4j. This is to improve security.
Note: The Log4j 1.x version installed with the interface is not a part of the security vulnerabilities found in 2021.
1 vote -
PI OPCtoCSV tool to continue running and skip branches in error
The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. When the tool is run into error with certain branches, the tool will stop and disconnected from the OPC server/tunneller. For example: “GetItemProperties(“xxx”) error 0x800706be. The remote procedure call failed. pEnumleaves Next() returned 0x800706ba”
If we could specify an option for the tool to skip those branches in error and also attempt to reconnect to the OPC server/tunneller, for automation purpose for the tool to continue running instead of exiting.9 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 -
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 Point Sync for Siemens Spectrum
Have the functionality to change the Point Type from the PSSS, because it cannot edit Point Type for existing PI Points.
2 votes -
PI Interface for Foxboro I/A 70 Series should support Windows 10
On PI Interface for Foxboro I/A 70 series version 2.4.2.12, the supported operational System are Windows 2008 R2, Windows 7, Windows 8 and 8.1, Windows 2012 Server.
Can we also test the interface against Windows 10, to included it as a supported OS?5 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 -
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 -
Avoid reloading tags after edits of non-key PI Point attributes
Currently, UniInt-based interfaces will reload a tag if edits are detected on any of the PI Point attributes. This is not ideal as edits to non-key attributes (such as EngUnits) will still cause a tag to be reloaded, potentially leading to data source issues if large numbers of edits are made.
Requesting to add the option to filter out edits to PI Point attributes that are not used by the interface to avoid unnecessary reloads.5 votes
- Don't see your idea?