The Rockwell RSLinx OPC Server may discard advise groups when there are too many bad quality tags or incorrect ItemIDs added to the group. The PI Interface for OPC DA should automatically recreate advise groups after it has determined that the group has been discarded from the OPC server.

Define more explicit system requirements for PI Interfaces. According to a customer, despite the Buffer and Bandwidth Calculation Spreadsheet, currently available information does not allow for accurate hardware sizing.

We have encountered a situation where we were unable to write out-of-order data to PI through the buffer subsystem from an interface, apparently because the buffer subsystem was not yet fully initialized when the interface connected to it. Please implement an appropriate wait cycle at interface startup, to ensure that the buffer subsystem (on which the interface is dependent) is fully initialized and available before permitting the interface to complete its connection and initialization.

Note the case in question arose when the interface service was configured with a dependency on the PI Buffer Subsystem service.

Ability to clamp or ignore values outside a threshold.
Example would be to clamp the low value to 'zero' attribute and/or a high value at 'span' - many xmtrs read erratically when at limit (e.g., an empty flow transmitter often reads negative)

Allow the Event Frame Templates to be fully customizable. This will give the flexibility to remove attributes like Product from the PIBatch and Procedure, as it is represented in the lower levels of Event Frames.

In PI Event Frames Interface Manager, there needs to be a 'Are you sure?' pop up after clicking "Remove Interface" button to prevent accidental deletion of interfaces.

PI ICU rejects options IGNORE5TH and IGNOREFLDMSEC at the same time. When modeling teams change MEAS fields often, IGNORE5TH is extremely useful to keep data history contiguous. When using field time that is stamped by the EMS, milliseconds are not useful.

Please remove the constraint on having both options.

Add OMF health function to Citect interface.

When a phase end event is received at the same time as a phase start event, the WWInBatch interface currently creates batches/event frames of zero duration despite there being phase state events under the phase event.
It would be helpful if the interface logic is updated so that either:
the phase end time is updated to the timestamp of the most current phase end event
or ignore phase end events that happen at the same time as phase start events.

We are using this interface to capture meter attributes and measurements. However, the voltage comes in the XML files as an "instrumentation value", which is not currently supported. We would like to bring the voltage into a tag for the meter to use in PI analytics.

When our EEAMAS Interface was originally implemented, the HeadEnd parameter was set to "Elster", the vendor name for our meters. So all of our meters from that interface are named Elsterxxx. Elster was purchased by Honeywell, so the name no longer makes sense. We would like to change our prefix for the elements to something more generic like "MTR", since the element name is something that is exposed regularly to end users.

When using a single PI tag, the fields are delimited by the pipe (|) symbol by default.
It would be useful to change it to another delimiter or a combination of others. There could be messages containing this pipe (|) symbol, which would make it difficult to split the fields afterwards.

the ability to disable the timezone adjustment.

currently we are calculating daily kpis on our global pi server. with PItoPI we are sharing it to the site pi-servers.
so the daily kpi for e.g. 1st januar 2019 00:00AM sould alwas have that timestamp. Because if the forward it to e.g. britain, it has the timestamp 31st decemper 2019 11:00PM (adjusted -1h to austrian time)

plz make it possible to disable it via Location2.

The PI SDK writes required for setting annotation values with the exdesc and RDBMS interface are not compatible with Full Synchronization.

Make this compatible.

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.

Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp).
Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair source time stamp to the pi time stamp (precision and rounding issue in SQL).
I request to add support for sql datetime2 into the ODBC connection, or an option to read the time from the snapshot in seconds since 1.1.1970

The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

I have a scan-based output point writing multiple PI values to the relational database as described here:
https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.