Currently UserID (DoneBy_User_ID) and ReviewerID (CheckBy_User_ID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

Currently, Batch Interface Framework interfaces implement tag template triggers that can trigger whenever a placeholder has any value. These interfaces should also support triggering when a placeholder does not have a value. For example, our SISBatch data source has separate columns for Operation and Phase information. We would like to record the value of the [DESCRIPT] column in a tag only for non-phase batch events (i.e. trigger the tag template only when the [PHASE] placeholder is blank).

I have been working with a customer who works with oil rigs and satellite networks and they requested that more external resources be available for how to efficiently operate PItoPI in a high latency environment. Currently there is only one internal document that may be out of date.

In the PI Interface of UFL we would like the option to suppress the message: "exception attributes corrected through the SDK read" for values of excmax larger then 9hrs.

Can you remove the restriction to use only an IP address in the BACnet Network Discovery Tool?  The interface will correctly load and poll tags to a network device referenced by name instead of IP, however the Discovery Tool has the limitation of being IP only.

OSIsoft's migration from PI Interfaces to PI Connectors is very slow. Even after the migration is complete, many PI Interfaces will not be upgraded to PI Connectors, so users will continue to use the PI Interfaces and the PI ICU to configure them.

Please consider upgrading the PI ICU to a responsive web-based user interface, much like the PI Connector administration pages. The PI ICU is currently very cramped, very grey, not resizable, and a bit hard to navigate.

It is currently possible to debug one tag, or all tags. Logging timestamp and data for all tags is expensive and make logs harder to read, so one one would like to select an arbitrary number of tags.

For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK.

Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.

For instance, cyrillic characters are not rendered correctly in spite of appropriate regional settings.

As a PI OPC Interface user I would like to get step-like trends whenever that the Trend Advise parameter is enabled (even with having large exception and compression deviations that filter some of the events) so that I don't need to enable the step attribute for each PI tag.

Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

Please allow the option to offset data sent by the interface. This will enhance the ability to compare time stamps between data sources and the PI Server  in different timezones.

DNP3 - add functionality to allow outputs for binary and possibly other object groups/variations.

Can you please add a DAYOFWEEK function to the available functions in the UFL interface.

This will greatly assist with the handling of daylight savings transitions (e.g. first sunday in April) as there is currently no easy way of determining the current day of week.

Function should take a DateTime and return an integer (i.e. Monday=1, Tues=2 etc)

Most of the problems appear in the FIELD, MSG, and message sections of the INI file. Note the difference in clarity, readability, and length between the current and proposed syntaxes below.

Current syntax:

[FIELD]
FIELD(1).NAME="Tag"
FIELD(1).TYPE="String"
FIELD(2).NAME="Date"
FIELD(2).TYPE="DateTime"
FIELD(2).FORMAT="yyyy-MM-dd"

[MSG]
MSG(1).NAME="MessageSection1"
MSG(2).NAME="MessageSection2"

[MessageSection1]
MessageSection1.FILTER = (MessageSection1 message filter)
(MessageSection1 code)

[MessageSection2]
MessageSection2.FILTER = (MessageSection2 message filter)
(MessageSection2 code)

Proposed syntax:

[Variables]
Tag String
Date DateTime("yyyy-MM-dd")

[Messages]

<(MessageSection1 message filter)>
(MessageSection1 code)

<(MessageSection2 message filter)>
(MessageSection2 code)

The BES/MES sometimes contains recipes with no Procedure, or even Unit Procedure. The Batch Framework Interfaces should allow the creation of only the Event Frame levels that exist on the data source. This would need to be enabled with an interface configuration parameter so the default behavior is not changed on upgrades to existing systems. This enhancement would not be possible when writing to the PI Batch Database.

This is the interface from the Siemens Power TG EMS system. The problem is with the saving of Alarm and Event text messages. There are instances when the data files are produced out of order. When data is sent out of order the interface seems to go into arc_noreplace mode and our data is lost.
To store Alarm and Event messages, the duplicate record check is turned off so there is no way to overwrite data, therefore the arc_noreplace is a meaningless protection. Data will never be over written.

Customer noticed that tags can be created automatically, but he does not want to create all of the tags autmatically, but select which tags will be created. He wants to be able to select which tags will be created and which won't.

Need to trigger failover when a watchdog tag is stale for a configurable duration.