PI EMDVB interface stops because of time difference between SQL and PI servers:

"Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.

Currently UserID (DoneByUserID) and ReviewerID (CheckByUserID) 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.

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.

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.

The PI Interface for RDBMS currently accepts the format dd-mmm-yy but not the format dd-mmm-yyyy for history recovery start and end times.

The former format lacks the century, so the year is ambiguous. The latter format solves this problem and so should also be accepted as a valid time format.

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.

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)

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 arcnoreplace 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 arcnoreplace 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.

If you use IntrumentTag for the query, it has to be a file containing the query, not the query itself.
You can specify the actual query in Exdesc.

Allow the user to specify an output file path for the processed files that is different than the input file path, moving the files to this "output" path after they are processed.

Note: This was previously Enhancement 100038.

Create a new function indicating if the string can be turned into a number. For example, IsNumber() function could return 1 if the string can be turned into a number 0 if not.